[mkgmap-dev] Implications of mkgmap style processor bug
From Felix Hartmann extremecarver at gmail.com on Wed Oct 16 13:26:05 BST 2013
On 16.10.2013 14:16, Steve Ratcliffe wrote: > On 16/10/13 13:01, Felix Hartmann wrote: >> Will this be handled correctly or not (points file)? >> amenity=toilet {set amenity=toilets} >> amenity=toilets {set name='toilets ${name}'|'toilets'} >> [0x10903 resolution 24 continue] > > That should work fine, it is only tag=* that is affected. > > The following would fail assuming toilets= is not a proper tag. > > amenity=toilet {set toilets=yes} > toilets=* {set name='toilets ${name}'|'toilets'} > [0x10903 resolution 24 continue] > > I will fix it, but we need to get some tests working again first. > > ..Steve okay, what about if something was set via relations file? Will it be affected by the bug too? -- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
- Previous message: [mkgmap-dev] Implications of mkgmap style processor bug
- Next message: [mkgmap-dev] Implications of mkgmap style processor bug
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list