[mkgmap-dev] bollards should not have 0x660f
From flabot at googlemail.com flabot at googlemail.com on Sun Jul 11 11:05:44 BST 2010
Yes great !!! Pse tell me the number to choose . Dirk 2010/7/10 Daniela Duerbeck <daniela.duerbeck at gmx.de>: > 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 > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev at lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > -- Wikipedia -- http://tools.wikimedia.de/~flacus/IWLC/ OSM -- http://osm.flacus.de/
- Previous message: [mkgmap-dev] bollards should not have 0x660f
- Next message: [mkgmap-dev] bollards should not have 0x660f
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list