[mkgmap-dev] bicycle=use_sidepath

Mon Aug 17 15:05:00 BST 2015

On Mon, Aug 17, 2015 at 03:34:26PM +0200, Felix Hartmann wrote:
>Definitely not I would say. It will just cause routing to break down 
>for cyclists IMHO. Too often such sidepathes won't be connected - or 
>maybe the sidepath is not even entered in OSM.

It might not even matter if the sidepaths have been entered and 
connected. For long-distance routing, I believe that the Garmin Edge 705 
completely ignores cycleways for the middle section of the route.  
Cycleways would only be considered for the first and last 5 kilometers 
or so.

So, if you have a 50-kilometer route that would involve riding on a 
cyclepath next to a highway=trunk, Garmin Edge 705 would send you on a 
200-kilometer detour using smaller roads. I had this happen to me a few 
years ago. Ways like http://www.openstreetmap.org/way/167517631 were 
being ignored, and http://www.openstreetmap.org/way/17065902 was tagged 
bicycle=no already then.

That said, I guess that treating more bicycle=* values in the same way 
as bicycle=no will not make the situation much worse. If you want proper 
long-distance bicycle routing, you have to use a precalculated route (or 
better routing software, such as Brouter).

	Marko