[mkgmap-dev] bollards should not have 0x660f
From Daniela Duerbeck daniela.duerbeck at gmx.de on Mon Jul 12 17:42:54 BST 2010
Marko Mäkelä wrote: > This was added before "my time", but I would say it is close enough, for > want of a better code. What if you add a default_name "bollard"; would > it affect the display? > May be, but why should someone want to try to find the next bollard at all? Dani
- 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