Hmmm... is it possible to place everything else without an explicit Garmin
hex code to a catch-all generic POI category? That would make everything
that has a name searchable in the Garmin map.
On Thu, Aug 12, 2010 at 11:03 AM, maning sambale emmanuel.samb...@gmail.com
wrote:
On Wed, Aug 11,
On Thu, Aug 12, 2010 at 10:21 PM, Eugene Alvin Villar sea...@gmail.com wrote:
Hmmm... is it possible to place everything else without an explicit Garmin
hex code to a catch-all generic POI category?
This is done on two features as well,
building=yes and shop=* for all those shops I can't find a
Yes that is correct and I am doing that for other POIs like
amenity=parking. The problem is that there is no direct poly hex
assignment for amenity=place_of_worship.
Suggestions welcome.
On Wed, Aug 11, 2010 at 1:18 AM, Eugene Alvin Villar sea...@gmail.com wrote:
Hmmm... doesn't mkgmap's
The user told me that the problem also includes named landuse=residential
polygons. For example: http://www.openstreetmap.org/browse/way/71376402
On Wed, Aug 11, 2010 at 1:18 AM, Eugene Alvin Villar sea...@gmail.comwrote:
Hmmm... doesn't mkgmap's --add-pois-to-area work around this limitation?
Hi guys,
I recently contacted a user who added a node for Santuario de San Antonio
even though a polygon exists for it:
http://www.openstreetmap.org/browse/way/39724055
He said that the church wasn't showing up in the Garmin map and that's why
he added that node.
Anybody else having problems
The official garmin codes doesn't support polygons for
amenity=place_of_worship. I'm still looking for a suitable code to
recycle.
On Tue, Aug 10, 2010 at 11:50 AM, Eugene Alvin Villar sea...@gmail.com wrote:
Hi guys,
I recently contacted a user who added a node for Santuario de San Antonio
