Navigation bug in Round-Trip GPX routing, when navigation is not exactly started at the beginning of the course.

There is a bug when riding round-trip tracks that have the same start and ending location, and the navigation is not exactly initiated at that location.

Let's say, you are a mile away from the start/end location and wish to "navigate to the beginning of the course" first. Since the beginning is also the finish location, the device stops navigating when the course start location is reached, even though the course was not ridden. As a consequence, the navigation must be started over manually.

Garmin should fix this so that the device does not end navigation after the "navigate to the beginning of the course" option was used and no miles were ridden.

  • Tis is a well known phenomenon. To fix it, you have to set the end point a 100 meters before the real end (away from start point).

  • be back later, editing 100 routes

  • I don’t think adding a gap will fix this. If this was the problem, you’d get the “course completed” message. If you don’t get the “course completed” message, the device was not using the course.

    ————————-

    The devices sometimes pick the end point when starting a loop course. (You don’t need to be using “navigate to start” for this to happen.)

    That issue is related to the device being able to start the course at any point along in (anywhere in the middle). The device does this by finding the nearest point on the course.

    With loop courses, people often put the end point at or very near the start point. Thus, you might happen to be closer to the end point when you start the course. 

    The idea when creating loop courses is to place the end point so you are closer to the start point when you start the course.

    ———————————

    If the course ends early, just go a little way along it and restart the course.

    If you don’t need it, don’t select “navigate to start”. (It’s often offered as an option even when you are fairly close to the start.)