18 Jul 2024, 20:30

@Con-Hennekens that could very well be the case. I don't know enough about the internals of a GPX file to say one way or another.

What makes me suspicious is the following:

  1. Before I made a lot of last-minute changes to the MRA route, as far as I remember, it looked fine on the XT side.

  2. After the series of MRA changes, I transferred to the XT for my ride, and I got lazy and didn't do my normal detailed XT route verification. I didn't know anything was wrong until I got towards the end of the ride.

  3. After returning home and investigating, no matter what changes I made to the route on MRA, a correct transfer to the XT didn't work. The XT always created the end point wherever the last shaping point was located.

  4. I Finally deciding to start from a clean slate and recreate the route from scratch. Everything then worked correctly. The MRA route recalculated in the XT as created.

This all tells me that the MRA created GPX file is the culprit. The XT only works with what it's given. Garbage in, garbage out. Again, I'm not trying to find fault here -- just a logical answer. In Google Maps, I'll sometimes create a route and then proceed to make a bunch of stopping point changes. At some point, the calculated route is all messed up and the resulting map is a mess. At that point, there is no other choice but to start over. I believe a similar thing happened here.

My lesson is to assume nothing and always check the re-calculated route on the XT. A lesson that's easy to forget when things generally go well. I've had rare, strange results when creating routes in Garmin Basecamp and transferring to the XT. None of this is usual, but the minute you let your guard down, surprises can happen.