[mkgmap-dev] oneway=reverse handling broken.
From Felix Hartmann extremecarver at googlemail.com on Fri Jan 22 16:01:07 GMT 2010
On 22.01.2010 16:56, Torsten Leistikow wrote: > Felix Hartmann schrieb am 22.01.2010 16:30: > >> highway=*& copy=99& mtb:scale:uphill!=5& mtb:scale:uphill!=4 { >> set dontadd=yes; set taxi=no; set dontadd=oneway; set mkgmap:unpaved=1 >> } [0x10711 resolution 21 continue with_actions] *output* >> > Actually, what is the difference between "continue with_actions" and "continue"? > I think I have never really understood, which version must be used in what case. > Can you provide an easy example, wich demonstrates the different results, > whether the with_actions flag is used or not? > > auxiliary tags can only set by [continue with_actions] if you did (until 1498 it was working well) something like highway=primary & oneway=yes & cycleway=opposite_lane & route=bicycle {set oneway=-1} [0x... continue] then all actions inside {} are only applied to the current way, and not forwarded. In order to keep {oneway=-1} one had to use [continue with_actions]. > Gruss > Torsten > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev at lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev >
- Previous message: [mkgmap-dev] oneway=reverse handling broken.
- Next message: [mkgmap-dev] oneway=reverse handling broken.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list