>
> To summarize, this just a demonstrates a deficiency in the routing algorithm
> of the Edge 705. It is probably impossible to get bicycle routing work right
> by tweaking the maps alone. Generally, I have found the route suggestions
> useful for bicycle rides up to 30 km in urban areas.
>
Hi Mark, Chris, all,
Sorry, I was wrong about the bicycle=no. I removed the bicycle=no, foot=no
in a local copy of the tile, and it did not affect the suggested routes.
This is within a single map tile. mkgmap spits out some "zero length arc"
warnings, but none should be on this route. java -e
Marko Mäkelä schrieb:
> http://wiki.openstreetmap.org/wiki/Mkgmap/routing/issues#Bad_bicycle_routing
>
> with an example where the bicycle route from A to C is much longer than the
> routes from A to B and B to C. I guess but have not verified that this is
> because of an access restriction that
Just a thought, is it related to the zoom level of the cycleway as set
in the style file? What happens if you make the cycleway have the same
zoom level as the road next to it?
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgma
Hi all,
I just updated
http://wiki.openstreetmap.org/wiki/Mkgmap/routing/issues#Bad_bicycle_routing
with an example where the bicycle route from A to C is much longer than the
routes from A to B and B to C. I guess but have not verified that this is
because of an access restriction that I added