GPX Versions 1.1 vs 1.2 for Garmin Visually Explained

[Steve Jarrell]

@Carl-Lee For some reason my XT3 is no longer showing my track with my route even though I've done it MANY times in the past. I'm still trying to figure out what's going on. You're right though... that's the very best way to know that you're being routed the way that you intended to be!

[Carl Lee]

@steve-jarrell maybe as you are tied in to collections with Explore? This is how I am too and it’s a case of making the collection visible. A little more to it than that but I won’t blather on in case that’s not your issue.

[Steve Jarrell]

@John-S-Parry Good deal. Let us know what you find.

The best test would be just a starting via point and an ending via point with a lot of shaping points in between that are neither the fastest or shortest paths to the ending via point. I'll try it if I get a chance. It's very likely that the older Garmin units will act differently than the new ons.

[John S Parry]

@Steve-Jarrell Good approach. I was thinking along the same lines. I'll mix up the roads enough to trigger a different re-calculated route path if that's what it wants to do.

[Steve Jarrell]

@Carl-Lee No, I don't use Explore at all (I have another thread about the hoops that I had to go through to remove it when I did activate it) but I do use collections in the XT3.

You did put me on the right track though! Since I think this issue is unique to the XT3 I've created another thread to explain what's happening and a good work around as it's not documented at all in the user's manual.

Thanks!

p.s. When I said before that I've shown the track with the route many times I have..... but that's been with previous version of the Garmin units up to and including the XT.

[Simon James Hancock]

@Mzokk That is exactly what happened this afternoon in my test.
I purposly stopped along the route and turned both units off and then back on again.
The xt2 picked up the route again and the xt whent dorment untill much further down the route.

[Simon James Hancock]

Going off topic a bit.
If just using the MRA app on the phone, What is the best map to create the route and which format is the best to save the route for the MRA app?
How does the standalone MRA app deal with these situations?
I am asking this as my bike has carplay so therefore I also have the option of using the MRA app.

[Mzokk]

The best map to use for route creation is the Here map as this matches the mapping on Garmin devices. If you have the navigation app you can create routes on it and they can be synchronised to your phone. If you are using the route planner on your phone (not the app) then you can download the routes if you have mobile phone signal or Wifi. They don't need to be saved in any format to the route planner only when you download a route to send to your device.

I use the app for navigation and have my phone synced with the site so if I have signal or wifi my route library is also on my phone (GPX files do not take up much space)

[Simon James Hancock]

Do the routes perform in the same way as on the Garmin, ie when you go off route and recalculation?

[Mzokk]

Yes, but of course they are WYSIWYG between the planner and the app no messing with GPX types. I no longer use my XT for navigation I use it for track recording and proximity aware poi's. Mra poi handling is not as good as Garmin, Basecamp,Poi loader and track splitting and joining is easy in Basecamp.

[John S Parry]

@Steve-Jarrell Per our discussion, I created a 1.2 route with a starting via point, an ending via point, and a lot of shaping points in-between. About 7-miles from home, I used 'Up Ahead" to select an off-route destination, and directed my XT3 to insert it as the next destination in the route. That function worked. But in adding that next destination (via point), there was clearly a route re-calculation. The XT3 routed me home the fastest path possible, bypassing all the crazy turns/shaping points I had created in the original route.

I'm guessing that if I had stopped and restarted the route at the inserted destination, that I could have started the route up using the "Closest Entry Point" option, and all would have been good. I'd have to go back and test that to be sure. But if I'm understanding things correctly, it reinforced the lesson that with 1.2, don't do anything that's going to force a re-calculation -- your original subsequent route is going to be altered, and not in a way you want.

Even with 1.1, I avoid recalculations 99% of the time, so I'm good with continuing the strategy of deviating off a 1.2 route, and finding my way back to route line where I choose. To me, the advantages with 1.2 route creation out weight off-route recalculation capabilities.

[John S Parry]

Edit to above: The moment I inserted the up ahead destination via point, the route was altered and restating it from scratch wasn't going to fix anything. If I had the XT3 just create and start a route to the "up ahead" via point, my original route would not have been recalculated, and I think I could have started it up with the "Closest Entry Point" option.

It goes back to not doing anything that triggers a recalculation of the original 1.2 route.