best practice in adding address info for enhancing POI address search in Garmin units
Hi, Perhaps not entirely appropriate here, but just the same here goes. I am planning to finally incorporate address search in my Philippine garmin map. Currently, I always use --no-poi-address switch because we lack address info in our data for the Phil. There are several ways to add this for mkgmap, Karlsruche schema and the is_in tag. What would be the best and more efficient way to enable address info in the POIs? My previous attempts to use the is_in tag as a proxy to address info yield showed inaccurate results. My guess would be the full Karlsruche schema in liue of the is_in tags. -- cheers, maning ------------------------------------------------------ "Freedom is still the most radical idea of all" -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ ------------------------------------------------------
On Thu, Aug 13, 2009 at 10:47:07AM +0800, maning sambale wrote:
What would be the best and more efficient way to enable address info in the POIs?
I've been assigning the addr:* tags to all POIs recently. And phone, url, opening_hours, name, name:* (for multilingual names) where applicable and available. The url might not be translated into Garmin images, but the addresses and phone numbers are. opening_hours is probably ignored in the translation, and I'm only filling it in for bigger shops, not for one-man-operations that can have flexible or irregular hours. The URL might be handy for a phone-GPS-type device later on. For example, the URL of a bus stop (where available) shows the time table of passing buses.
My previous attempts to use the is_in tag as a proxy to address info yield showed inaccurate results.
My guess would be the full Karlsruche schema in liue of the is_in tags.
The is_in looks too informal for me. One thing that is missing from the Karlsruhe schema is i18n, though. Street and place names are bilingual around here, but there's only one addr:street and addr:city. I've been using the major language then, as with name. Marko
Marko, Thanks! These are very helpful. On 8/13/09, Marko Mäkelä <marko.makela@iki.fi> wrote:
On Thu, Aug 13, 2009 at 10:47:07AM +0800, maning sambale wrote:
What would be the best and more efficient way to enable address info in the POIs?
I've been assigning the addr:* tags to all POIs recently. And phone, url, opening_hours, name, name:* (for multilingual names) where applicable and available. The url might not be translated into Garmin images, but the addresses and phone numbers are. opening_hours is probably ignored in the translation, and I'm only filling it in for bigger shops, not for one-man-operations that can have flexible or irregular hours.
The URL might be handy for a phone-GPS-type device later on. For example, the URL of a bus stop (where available) shows the time table of passing buses.
My previous attempts to use the is_in tag as a proxy to address info yield showed inaccurate results.
My guess would be the full Karlsruche schema in liue of the is_in tags.
The is_in looks too informal for me. One thing that is missing from the Karlsruhe schema is i18n, though. Street and place names are bilingual around here, but there's only one addr:street and addr:city. I've been using the major language then, as with name.
Marko _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- cheers, maning ------------------------------------------------------ "Freedom is still the most radical idea of all" -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ ------------------------------------------------------
participants (2)
-
maning sambale -
Marko Mäkelä