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

On Device Course Creation Problems

Just been on a cycling trip with the Edge 820 and have had problems with creating courses on the device.

The Edge 820 seems to plot extraordinary long routes extending a journey by many miles whereas Garmin Connect and Google Maps will route via the quickest available cycling routes.

Any ideas on what's going on here? I'd be pretty miffed if I cycled more than I needed to.

This is on the Edge 820 and its calculating the 2 points as 2.41 miles. The activity and routing is set to Mounting Biking. It seems the Edge 820 can't see this linking trail to the road.

The same route on Garmin Connect with Mountain Biking, custom and popularity routing chosen but the route is only 0.4 miles.

Google Maps

  • The activity doesn't matter (the routing mode does matter).

    Try turning off "popularity routing".

    Also try "mixed surface".

    ===================

    I used recent OSM maps (from a non-Garmin source) on Garmin BaseCamp.

    "Mountain Biking" and "Cycle Touring" (roughly equivalent to "mixed surface") both produced the short route in BaseCamp.

    "Bicycling" produced a long route (about 2 miles but exactly what you saw).

  • Hmm, only Pedestrian routing will replicate Garmin Connect and Google Maps calculation.

    Looking at Open Cycling Map it shows that connecting link as a footpath not a cycle path so that explains why a bike setting will ignore it. 

  • That could be it. I added bicycles=yes to it. You should see it in the Garmin maps in (maybe) 6 months.