index problem camp_site
Hi, On the OSM forum someone found out that on some Garmin devices tourism=camp_site and tourism=caravan_site [0x2b03] cannot be found. See http://forum.openstreetmap.org/viewtopic.php?id=31093 http://forums.gpsreview.net/discussion/29752/campsite-pois-do-not-show-on-gp... On the device's map they are rendered ok, in Basecamp and Mapsource as well and can also be found. But on an Oregon, Dakota and GPSmap 64 they are not listed. On my Openfietsmap I use 0x2b05 for camp_site, and this poi has not this issue (appears in the search menu of my Oregon). Is this a Garmin device bug or mkgmap index problem? Should we use 0x2b05 in the default style for camp sites/caravan sites?
may be there are different codes for oregon and others for the caravan site and camp site in tourism Stephen On Sat, May 16, 2015 at 7:20 PM, Minko <ligfietser@online.nl> wrote:
Hi, On the OSM forum someone found out that on some Garmin devices tourism=camp_site and tourism=caravan_site [0x2b03] cannot be found. See http://forum.openstreetmap.org/viewtopic.php?id=31093
http://forums.gpsreview.net/discussion/29752/campsite-pois-do-not-show-on-gp...
On the device's map they are rendered ok, in Basecamp and Mapsource as well and can also be found. But on an Oregon, Dakota and GPSmap 64 they are not listed. On my Openfietsmap I use 0x2b05 for camp_site, and this poi has not this issue (appears in the search menu of my Oregon).
Is this a Garmin device bug or mkgmap index problem? Should we use 0x2b05 in the default style for camp sites/caravan sites?
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
I found out that type 0x2b03 is not indexed on many devices, 0x2b05 is listed and rendered as campground too. So if this is not a mkgmap bug, it should be an easy fix to change this in the default style.
may be there are different codes for oregon and others for the caravan site and camp site in tourism
Stephen
If I search on google with "0x2b05 Garmin" it seems this issue appeared elsewhere too. It seems there is another alternative for campgrounds, poi range 4800 to 0x48ff, dont know how this is handled on the devices. 0x2b05 is already in use as tourism=lean_to [0x2b05 resolution 24 default_name 'lean-to']
I did some further testing with several devices 0x2b03 (camp and caravan site default style) renders on Dakota, Oregon 600 as tent symbol, but is not findable at all. On a Nuvi 310 it renders as tent and findable under lodging I adapted the default style and made a test map without typ file https://drive.google.com/file/d/0B5LoKTN293hkYWhQMXRYd0NXSmc/view?usp=sharin... 0x02b05 tourism=caravan_site 0x4800 tourism=camp_site 0x2b05 = renders on Dakota, Oregon 600 as tent symbol, and is findable under lodging/campgrounds. On the Nuvi it renders as "bed" (lodging) and findable under lodging 0x4800 = renders on Dakota, Oregon 600 as tent symbol, and is findable under lodging/campgrounds. On the Nuvi it renders as tent, but pois are not findable at all Please test it for other units.
I have tested more devices. old Etrex series, Monterra: 0x2b03 tent on the map 0x2b05 bed on the map, findable under lodging/campgrounds 0x4800 tent on the map, not findable My conclusion for now 2b03 renders as tent in all cases but is not findable anymore on most modern devices like Etrex new series, Dakota, Oregon and GPSmap 64 2b05 makes it findable on most (all?) units under lodging, but older devices (+ Monterra which behaves like a nuvi?) shows a "bed" as default symbol 4800 renders in all cases a tent but is not findable on nuvi, older Etrex and Monterra So what is better? A wrong symbol could be corrected with a typ file. Better than not findable at all. I would suggest to replace 0x2b03 for 0x2b05
Hi all, ligfietser wrote
So what is better? A wrong symbol could be corrected with a typ file. Better than not findable at all. I would suggest to replace 0x2b03 for 0x2b05
+1 Gerd -- View this message in context: http://gis.19327.n5.nabble.com/index-problem-camp-site-tp5844807p5844866.htm... Sent from the Mkgmap Development mailing list archive at Nabble.com.
Hi, I've almost forgotten this issue. I've changed the default style with r3608. Gerd GerdP wrote
Hi all, ligfietser wrote
So what is better? A wrong symbol could be corrected with a typ file. Better than not findable at all. I would suggest to replace 0x2b03 for 0x2b05 +1
Gerd
-- View this message in context: http://gis.19327.n5.nabble.com/index-problem-camp-site-tp5844807p5847271.htm... Sent from the Mkgmap Development mailing list archive at Nabble.com.
participants (3)
-
GerdP -
Minko -
Steve Sgalowski