My EDGE 1050 seems to have benefited from improved behavior for these two metrics. I use these to inform the rider of their ETA at the end of the ride, and to alert them if they went off course and how far off they are. These have had a bunch of scenarios that confused the device and caused errant data to be returned. But at least in the EDGE 1050, it has gotten a lot better.
There are still some issues. On one particular route I do often, a 130 miler in which the return to the start has a 15 mile sector in which I ride back along the same route i left. Invariably with about 10 miles left, it thinks I started again and shows I have 120 miles to go. I'm not sure why it gets confused there.
I have my nav/recalculate settings set to not auto-recalculate the route, but rather prompt me. I want to keep my actual route intact.
The frustrating thing, on the EDGE 1050 at least, is there are two responses to going off course. I haven't figured out what causes it to select from these two.
- Sometimes it'll pop up two choices: PAUSE NAVIGATION or RECALCUALTE. There is no way to DISMISS and just keep your original route and watch on the map where you are and how to get back. If you hit PAUSE, then the distanceToDestination D2D) and the offCourseDistance (OCD) both go to zero. Not helpful. If you hit recalculate, your OCD goes to zero - which isn't true to your original route. I can internally keep my own versions and keep the last known D2D which will be updated once I'm back on course.
- Sometimes it'll retain D2D and the OCD will increment as you ride away from the route, and it won't prompt me to recalculate. This is my desired behavior. But I'm not sure how to get it to do this.