navigation: incorrect course path when using "do course in reverse"

There is a bug in the navigation / courses feature in Fenix, that i have experienced with several different units.

If you make a course/route for navigation e.g. during you run and you choose "Do course in reverse" you path will not be entirely accurate. Instead the course will be straightened out between course points, potentially sending you through mountains, swamps, or buildings etc. The only workaround is to always choose the normal "Do Course" feature and follow the path backwards or to draw the course in the other direction and save a s a copy.

The entire course will not be wrong, but after a while it stops being accurate. The image below is showing km 25-30 in a 50k course: left is course as drawn in Garmin Connect, middle is how the course loads in normal mode (correct) and right side shows how course loads when using "Do Course in Reverse". I experienced this with several courses and it took a while to figure out in which exact context this problem occurs. NB the course is well within the limit of the maximum allowed course points.

This should be easy to bug fix?

  • After a while of using Fenix in various conditions, I think that this bug can be actually life threatening.

    After some time of using the gpx + gps based navigation I can imagine users get sense of how much they can trust it. Not aware of the bug with the reverse navigation they may put themselves in a pretty nasty spot, unaware that the watch misleads them.

  • No, that’s not it. What happens is that it actually deviates from obvious paths, trails and popularity routes, and instead makes straight lines without any justifiable logic. 

    I didn't disagree with that. I used this feature and ran in the same bug, and I know that it makes straight lines. I think I could even find my other post about this issue where I complained that it made finding the right turns really difficult. 

    What I said was an attempt to explain why this bug exists in the first place. Fenix has two navigation modes - "follow course", which is a dumb following of a track, and "use map", which is a more elaborate routing through a series of waypoints that uses on device map. I think most users use the "follow course" mode because that is the default setting. The other mode is what handheld navigation devices users are more used to. I think the reason Garmin limits the number of points when reversing a course is because the implementation of the feature has to work with "use map" navigation mode, even though the vast majority of users don't use that mode. When routing using on-device map, attempting to route through a large number of points would take an extremely long time, and may not work at all. 

    I don't say what Garmin has done it's right and I think that this bug absolutely has to be fixed. When "follow course" navigation is used reversing a course should be super trivial - it should simply use all track points from the original course in the reverse order with no loss in details. 

    As of now the feature is simply unusable for a course of a reasonable length. I tried this on a course that was about 14-15 miles long, and the reversed course was impossible to follow - extremely confusing and even misleading on the watch screen.

    Also, the issue exists in Fenix 7, Epix 2, and likely all other Garmin watches that support on-device routing. 

    FYI 

  • Yes - I know :)  This is the same issue I have. My point was that whilst some of the features of navigation might be harder for the device to plot in reverse (like climb pro and race pro), getting the route accurate should not be difficult. Every Garmin I have had struggles with doing routes in reverse and misses all the detail and reduces it to basic straight lines.

  • Sorry, then I misunderstood you. But i agree, it makes the feature more/less unusable e.g. for ultrarunners. The workaround is using normal navigation and just follow it backwards - but this then renders a lot of other features unusable, such as ETA, Waypoints etc.