Totally agree, Eugene.
Much better with consistent data, with one way to tag a certain thing, than to
have different processes adapt to incorrect tags, regardless of how frequent.
Besides, anyone calling McDonalds a *restaurant* clearly needs to get out more! :)
Ronny.
On 25/05/14 04:44, Eugene Alvin Villar wrote:
Hi Mark,
I think it would be better for all users of the data in the long run that
the inconsistent name field is the one corrected instead of your system
adjusting for it.
Let's say that you have a "rule" that says that that name=McDonald's with
amenity=fast_food gets the Golden Arches icon.
Now let's say you have other rules that detect stuff that are probably
McDonald's: name=McDonalds amenity=restaurant
Instead of tagging stuff like this with an additional tag
icon:ph=mcdonalds.png, it would be better to correct those POIs that don't
follow the correct tagging. If you have a system that detects such
near-misses, then I'm sure the community would like to get a list of them so
that they can be corrected.
I hope other mappers and users can chime in with their ideas.
On Thu, May 22, 2014 at 6:32 PM, Mark Cupitt <[email protected]
<mailto:[email protected]>> wrote:
Folks, have been thinking about how we specify Icons for POI's in the
Philippines OSM Map. I have Icons for most of the PH specific
businesses, like Jollibee, Banks, and so on and would like to use them
At the moment, the only way to do this is to run through the database
checking the name tag and seeing if it starts with jollibee, BDO mcdo,
etc. This is a very intensive effort on a million+ points. I am doing
the code for it now and it has to be run on a very regular basis to pick
up new POI'S from the daily diff updates. It also suffers form spelling
errors, and fomat errors, for example "the jollibee" will to be
identified as the name has to start with "jollibee" (in text string
searches in postgres do not use indexes, and are too expensive on the
database, so we have to assume that the name starts with the search text.
I will publish the icons we have at some stage very soon where they can
be viewed by anyone.
To make it very easy to have granular control over icon display, I
propose that we do the following:
Add an icon:ph tag to nodes as they are created that contains the
filename of the icon to display (from the list published)
For example, a node of a Mcdonalds might have a tag amenity="fast_food"
name="Mcdonalds Quezon City" and a icon:ph="mcdonalds.png"
The system will first check if the icon:ph exists and use the icon
specified in that. if not, it will fall back to database determined
value done on a weekly or monthly basis, with all the inherent pitfalls
in the use of the name field. If that does not work, it will display a
generic icon which is a Red Dot.
One big advantage of this proposal is that people can submit their own
logos in icon form, they are easy to add to the system, them specify
them for specific businesses, leisure, bars, etc. on the actual poi ..so
the value added to the map will be tremendous in the future.
Thoughts, flames, thumbs up, thumbs down, rounds of applause on this
proposal very much appreciated ..
Regards
Mark Cupitt
"If we change the world, let it bear the mark of our intelligence"
See me on Open StreetMap <https://www.openstreetmap.org/user/Mark_Cupitt>
See me on LinkedIn <http://ph.linkedin.com/in/markcupitt>
*
See me on StackExchange <http://gis.stackexchange.com/users/17846/mark-c>*
===============================================================================================
The contents of this email are intended only for the individual(s) to
whom it is addressed and may contain
confidential or privileged information. If you are not the intended
recipient, you must not disclose, copy, distribute,
or use the contents of this email. If you have received this email in
error, please notify the sender immediately and
delete the email and any attachments.
===============================================================================================
_______________________________________________
talk-ph mailing list
[email protected] <mailto:[email protected]>
https://lists.openstreetmap.org/listinfo/talk-ph
_______________________________________________
talk-ph mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/talk-ph
_______________________________________________
talk-ph mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/talk-ph
