This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

bug - EE2 routing avoids paved minor roads for no reason when set to "road cycling"

I found the routing on the EE2 to be terrible, always coming up with routes twice as long as they should be even with all avoidance settings and popularity routing turned off.

I finally found out that I can work around the problem by setting the routing mode to "mixed surface cycling" but this then introduces the problem of sending me down gravel and dirt paths.

If I put in the start and end point on the Connect website to create a road bike course, then it works fine. But using the same points on the EE2 it will refuse to take the most direct route when set to "road cycling", turning a 14km route into a 19km route. When set to "road cycling" it would rather send me down a 3 lane very busy carriageway instead of the direct country road route.

Software Version is 26.18 and maps were updated a few days ago

I am guessing this is a bug, since the Garmin website doesn't have the same problem.

eg this is a route created by the website, 13.5km long and as direct as it can be

It is hard to really see from the EE2 screenshots but the same route by the EE2 with all avoidance off sends me on the A14 which is very busy and not safe for cycling, also 15.5km long which is 2km longer than it should be:

If I tell it to avoid major highways it gives me an 18.5km route:

This has been a problem from a few different locations, not just this 1 route.

  • I'm also solving the same problem, it either takes me to a busy road or a very long way away

  • Glad I'm not the only one :) I have only had the edge for a few days but on the 2 days I tried to use it to plot me a route home it gave me extra long routes. 

    I don't know if Garmin uses openstreetmap for data, but after some playing around last night I found that the part it avoids is of type "minor road" on a 3km section, but the rest of that road is "tertiary road". It may be possible to fix it by editing openstreetmap, but I can't go around editing every minor road for the world Slight smile

    Since the routing on the Garmin website is correct I would expect to see the same on the Edge.

  • I am using the 'OpenFietsMap' which too is based on OSM data. If I use the setting 'Avoid Tollroads' the routing on the device gives preference to cycle routes. Maybe you can try this setting to see if it makes any difference? Also play with shortest time or shortest distance. Play with the avoidance settings by setting each one by one and see the effect. If you have all avoidances marked you never know which one is causing weird effects.

  • I've had it for half a year and it does it almost every other route...it even guided me off the busy road for a while...but on a shaky and dangerous bridge over the river

  • I have tried with tollroads off and on but that makes no difference, we have no tollroads around here so that makes sense. I just tested minimizing time instead of distance and that gives a slightly longer route than the minimize distance setting, that is also expected but it was worth testing Slight smile