
Hi Andrzej, as I said, I found no problems with the new patch, with the previous versions bicycle routing did not work (large detours avoiding the cycle ways). I don't see a new problem in your example. When you plan a route that starts and ends on the same arc, Garmins algo doesn't care about access restrictions. You can see that as well on footways. If I got you right, you fear that one selects the wrong way when planning a route. Or will also the device select the wrong way ? For example, if I configure car routing and start at the place shown in your picture, will the device chose the bicycle arc instead of the car arc? Gerd popej wrote
Hi Gerd,
so actually what problems are solved when mkgmap creates the cycleway first?
IMO the only difference will be at cases like in my example. "Cycleway first" makes problem for car routing while "original first" makes problem for bicycle routing. I would prefer proper car routing.
-- Best regards, Andrzej _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/Patch-v5-correct-make-cycleways-tp5800981p580... Sent from the Mkgmap Development mailing list archive at Nabble.com.