[mkgmap-dev] Serious mkgmap Bug - set unconnected type not respecting continue command!

Thu Aug 29 20:29:58 BST 2013

No comments or solution to this bug?
On Aug 26, 2013 9:37 PM, "Felix Hartmann" <extremecarver at gmail.com> wrote:

> Well the bug is quite serious and took me about 6 hours to find out why
> I'm missing roads in my maps.
> In case you have an "unconnected" type of a road that you set up a rule
> for, with " set mkgmap:set_unconnected_type=**none" and [continue] - all
> subsequent commands for the object will be lost, if the set:unconnected
> becomes true.
>
> Reproduce:
>
> lines file (only this content needed).
> highway=motorway & bridge=yes {set mkgmap:set_unconnected_type=**none}
> [0x13 road_class=1 road_speed=0 resolution 24 continue]
> highway=motorway [0x10001 resolution 24 continue]
>
> Now in all places that have a bridge, the motorway will be missing.
>
>
> If however the example is changed to the following, the bug is not present
> (as the unconnected type condition is not true):
> highway=motorway & bridge=yes {set mkgmap:set_unconnected_type=**none}
> [0x13 road_class=1 road_speed=0 resolution 24 continue]
> highway=motorway [0x01  road_class=1 road_speed=0 resolution 24 continue]
>
>
>
>
> I don't know if there are any other problems related to this bug. However
> it is really defeating the purpose of set unconnected type right now, if
> working with overlays for bridges, routes, and many other things!
>
> --
> keep on biking and discovering new trails
>
> Felix
> openmtbmap.org & www.velomap.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20130829/8433cb83/attachment.html 