I just looked at the custom POI for Malls of America. When I looked at the cvs spreadsheet I wanted to see where the malls were so I could plan some trips before I downloaded the file. I saw the latitude, longitude, mall name and street address but did not see the city and state. Therefore, without going to another source I have no idea where these are or if they are somewhat close to me.
Don't you think it would be a good idea to develop and communicate some standards that listed all the information necessary to be a complete custome POI? Standards that will tell the developer exactly what information to include in each field. Then, when the custom POI is loaded it will work properly and display addresses and phone numbers all in a uniform manner.
Perhaps, Miss POI has already done this and I am unaware but if not then this might be an opportunity to begin to pull together all custom POI's in a uniform format.
I'm sorry if I offended you too. The way your previous post was formatted looked like you were only adding the "This discussion is pointless" subject line but saying nothing else. I didn't see until later that you did add to the discussion, everything else was included in a quote block and it looked like you were only quoting me and previous discussion.
There have been more than one person who stated this "you can't please everyone" thinking. But I just don't see why that should be a reason to not try to improve the system. I didn't start the discussion, but I agree with the sentiments of the person who did. And I have a good professional database background and would be willing to offer my time to help come up with a cleaner system. I'm having trouble understanding why there is opposition to that. No one seems to be telling anyone that they have to do things a certain way, just trying to provide a system that can help make data cleaner and better organized.
I think the issue is confused by the fact that we are really discussing several things at once, without clearly separating them.
1- The file content meeting/not meeting a user's expectation.
2- Trying to define what exactly that expectation is.
3- How to best capture, organize, and store as many bits of info as possible to be most flexible.
4- How to create a method for easily & quickly matching the user's expectation.
All I'm saying is that excluding an individual mfr's extended data, they all use gpx to get the info in and out of the units, and there are 4 to 7 key data fields in that spec- 9 if you count lat & lon. Only 3 of which [name], [cmt] and [desc] hold the items that make up the majority of info presented to the end user. Yes, it can be argued that [sym] and [link] are important but I think the name, comment, and desc items are the ones that individuals have the most differing expectations over.
Having said that, this simply leaves us to find a way to consistently deliver these 3 data fields so that an end user can use them as-is or parse them as they desire.
Displaying the files on the site so they can be quickly & comprehensively searched, and so the user has an understanding of their completeness or simplicity is another issue, as is capturing enough data to be flexible and forward looking.
The way your previous post was formatted looked like you were only adding the "This discussion is pointless" subject line but saying nothing else. I didn't see until later that you did add to the discussion, everything else was included in a quote block and it looked like you were only quoting me and previous discussion.
That's the way I read it, but after you pointed that out, I had to go back and read it again.
I noticed that you included email address. I suggest that you also have website included. That would be handy if you are trying to verify something about the poi.
Looking at the OP's issue & the 189 posts in 60 days, I have to think this is getting a little bit over engineered.
At first it was entertaining.
Now it is just booring.
I hope the 2 "engineers" are having fun with their exchanges.
I'm pretty sure that the rest of us AREN'T.
I absolutely agree.
And before someone says that I can choose to just skip this thread, believe me I'm already doing that 99% of the time. I just peek in occasionally to see if there's anything actually worth reading.
Since I have family arriving this evening and staying until Saturday this topic will be tabled until next week.
This item is still tabled, Jon and I are focused on other things right now.
We appreciate all the suggestions and ideas. I am locking this thread for now because we already know what we will be doing.
Once this is set up it will require a lot of my time a focus to manage it and right now I don't have that time to dedicate to it.
Other systems have to be in place first.
terms | privacy | contactCopyright © 2006-2023