[mkgmap-dev] bollards should not have 0x660f
From Daniela Duerbeck daniela.duerbeck at gmx.de on Sat Jul 10 15:11:38 BST 2010
Hi! In the default style I find: barrier=bollard | barrier=bus_trap {add access = no; add bicycle = yes; add foot = yes} [0x660f resolution 21] My Garmin Oregon translates this to "Säule" In the German Garmin text file, I find: <str> <tag>TXT_Pillar_STR</tag> <txt>Säule</txt> </str> So Garmin means with 0x660f a column and not a bollard: http://en.wikipedia.org/wiki/Pillar vs. http://en.wikipedia.org/wiki/Bollard In the Oregon menu I can find the bollard under Geographical points - landuse. Summa summarum: I think we should use a different number for bollards. Dani
- Previous message: [mkgmap-dev] New cmdline switch for splitter.jar
- Next message: [mkgmap-dev] bollards should not have 0x660f
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list