Hi Gerd, Interesting to hear because on Sicily there are hardly any cycle routes, if any, on OSM, so it could be also associated with something else. Can you give just the location of that particular roundabout on the osm.org map so I can see if there are similarities with other roundabouts? I think about too many OSM nodes, the roundabouts on the mkgmap maps are sometimes distorted if drawn with a lot of nodes. Maybe this could cause crashing of the device? Another more likely cause could be that I use an invisible line type for 0x0c: junction=roundabout [0x0c road_class=1 road_speed=1 resolution 24 continue with_actions] junction=roundabout {set access=no} The line that is rendered on my map is not accessible, for instance an unclassified 'white' road with 0x06 is drawn on top of this invisible 0x0c. Possible problem is that it still has routable parameters (road_class and road_speed), maybe this causes the crashes? A solution would be to replace all highway=* & junction=roundabout with a non routable line type on top of this 0x0c for rendering the correct line type. In the default mkgmap style this problem does not occur because all roundabouts are rendered with the same style and just one line (0x0c).

Thanks Gerd, I can't open your track but both roundabouts don't look too complicated with too many nodes and I don't render bus routes, so I think it could be caused with the two routable lines on top of each other in my styles. In the NL's many roundabouts have cycle routes on them I thought at first it was only caused by this routable cycle route line (0x02). After that I have removed this 0x02 I got some positive feedbacks, but now you and someone else also reported it could happen with other roundabouts as well I think other routable lines like 0x06, 0x05 etc on top of 0x0c could crash some devices (not all, at least not mine, which makes it very complicated to reproduce) too...Workaround is to remove all routable lines on top of each other or at least remove the routing parameters (but in the past this lead to other issues with routing via address search). Gerd wrote I looked at the recorded GPX tracks now and noticed that the 1st crash happened while I was approaching one roundabout, I stopped after the rb to switch the device on again and the 2nd crash happened maybe ten m later aproaching the next rb. I am not sure about the timing, I just noticed that the device was off again. I've uploaded the part of the recorded track http://files.mkgmap.org.uk/download/298/2016-06-29%2006.49.55%20Tag.gpx The related rb ways: https://www.openstreetmap.org/way/274709979 and east of it https://www.openstreetmap.org/way/179620014 Both ways are part of a bus route. Hope this helps. Gerd

I think that was solved later, however those issues proof it would be better not use more routable lines on top of each other. With some workarounds I have fixed it mostly I hope, but it would be better to use transparent route lines. Which means rebuilding my whole line style and typ file from scratch... Henning wrote:

Hi Minko,

I#m not completly sure, but I remember, there were long time ago problems with 2 routable lines on same position. So in my map I changed all routeable lines to transparent and used for showing highways etc. non-routable lines. But maybe this particular problem was solved later.

Henning

_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Thanks Bernd, I think your method of "every routable ways is an invisible line with overlay" will prevent those crashes. With my style I have used in case of roundabouts two routable lines on top of each other that might have caused those occasional crashes. The same with bike routes on top of other roads, I am using line type 0x02 to render dashed lines in all cases on top of other routable lines. Until now I haven't found any non-routable line type that displays on top of every other line. I can make 0x02 unroutable by removing the road parameters but this leads to another issue: When searching for a specific address on that particular road, the device will draw a straight line to that address without using roads. So I either have to accept an occaisonal crash or bad address routing. Don't know what is worse?