GPX Versions 1.1 vs 1.2 for Garmin Visually Explained
-
@steve-jarrell that was a huge typo on my part. It was meant to read “and even if you are not using Tread”. I must have been tired. I’m all Zumo’d out.
-
@steve-jarrell that was a huge typo on my part. It was meant to read “and even if you are not using Tread”. I must have been tired. I’m all Zumo’d out.
@Carl-Lee Been there. Done that. Have the t-shirt!
-
I'd like to add something about recalculation. I haven't played with 'Up Ahead' places by inserting them into my route but on a normal deviation from a 1.2 route with recalculation left on, I've found there is a recalculation but it logically puts you back on your intended route - maybe with a u-turn or merging with it a little further along.
@simon-james-hancock, which Zumo do you have? On the XT2, you can change the colour in Tread or the Zumo but the width is done on the Zumo. And if you are using Tread, the track must be put in a collection that is visible. I've found red on the widest to be very visible on the XT2. If you don't see the track underneath when zoomed in, just zoom out a little and you'll see it. I wouldn't want it any wider as otherwise it would obscure junctions etc.
" I'd like to add something about recalculation. I haven't played with 'Up Ahead' places by inserting them into my route but on a normal deviation from a 1.2 route with recalculation left on, I've found there is a recalculation but it logically puts you back on your intended route - maybe with a u-turn or merging with it a little further along."
This got me thinking about recalculation to get the Zumo to return you to the route. So I had to go out and check.
You're correct that going off route, with recalculation left on, will simply attempt to return you to the route. It does not recalculate the whole route and trash your custom shaping up ahead. I performed conscious off-route deviations at least three separate times, and they all did nothing other than try to return me to the route. A few of the Zumo decisions on returning me were head scratchers, but they worked, and the route continued as normal.
The recalculations that are a NO-NO are actions that modify the route itself. As discussed, that can be through using "Up Ahead" and inserting a new via point as the next stop. Using Search to find a POI and inserting that via point as the next stop is equally disastrous. In short, don't do anything that modifies your route and triggers a recalculation.
From my perspective, using 1.2 GPX files in the Zumo works very well if you understand the behavior.
-
" I'd like to add something about recalculation. I haven't played with 'Up Ahead' places by inserting them into my route but on a normal deviation from a 1.2 route with recalculation left on, I've found there is a recalculation but it logically puts you back on your intended route - maybe with a u-turn or merging with it a little further along."
This got me thinking about recalculation to get the Zumo to return you to the route. So I had to go out and check.
You're correct that going off route, with recalculation left on, will simply attempt to return you to the route. It does not recalculate the whole route and trash your custom shaping up ahead. I performed conscious off-route deviations at least three separate times, and they all did nothing other than try to return me to the route. A few of the Zumo decisions on returning me were head scratchers, but they worked, and the route continued as normal.
The recalculations that are a NO-NO are actions that modify the route itself. As discussed, that can be through using "Up Ahead" and inserting a new via point as the next stop. Using Search to find a POI and inserting that via point as the next stop is equally disastrous. In short, don't do anything that modifies your route and triggers a recalculation.
From my perspective, using 1.2 GPX files in the Zumo works very well if you understand the behavior.
@John-S-Parry "In short, don't do anything that modifies your route and triggers a recalculation."
I think that sums it up perfectly!
I leave auto-recalculation turned off just from habit using so many different versions of the Garmin, and I'd rather just get back on the route by myself, but off-route re-calculation does not seem to trigger the dreaded "ok, you changed the route manually so that gives me (the Garmin) permission to do whatever I want to to your route".
Steve Jarrell
Western North Carolina USLifetime Routeplanner Gold & Navigation Next
2025 BMW R1200GS
2025 Can-Am Spyder
DMD T865-X 8" Tablet
Garmin XT3 -
Still some more testing to be done I think. I’m wondering if “shaping” the route on the Zumo just by adding some more shaping points (not vias) will damage it. In reality, this is something I would rarely, if ever, do but it would be nice to know.
When I get chance……And anyway, even leaving auto recalculation off, if you’re struggling to get back on the route (it happens!), stopping it and restarting with CEP is a fine and still won’t destroy the route.
-
Still some more testing to be done I think. I’m wondering if “shaping” the route on the Zumo just by adding some more shaping points (not vias) will damage it. In reality, this is something I would rarely, if ever, do but it would be nice to know.
When I get chance……And anyway, even leaving auto recalculation off, if you’re struggling to get back on the route (it happens!), stopping it and restarting with CEP is a fine and still won’t destroy the route.
@Carl-Lee Yep, you're right. Restarting the route from any point is FAR better than doing ANYTHING that signals the Garmin that it's ok to change your route as it sees fit.
As far as adding the shaping points goes I really don't know. I've never done that as I've never had the need to do so. For that matter I've never created a route directly on the Garmin either, so for me there are still a lot of unturned stones!
-
@John-S-Parry "In short, don't do anything that modifies your route and triggers a recalculation."
I think that sums it up perfectly!
I leave auto-recalculation turned off just from habit using so many different versions of the Garmin, and I'd rather just get back on the route by myself, but off-route re-calculation does not seem to trigger the dreaded "ok, you changed the route manually so that gives me (the Garmin) permission to do whatever I want to to your route".
@Steve-Jarrell Yes, it seems with a high degree of confidence, that 1.2 off-route recalculation does not seem to trigger a complete recalculation of the route. It's simply a re-calculation to get you back to the route. I don't think there is an overt amount of intelligence within the Zumo. In each case where I intentionally went off-route to trigger auto recalculation, it tried to turn me around back to the off-route spot for route re-entry. Even when there was a shorter re-entry point a little further up. In a way it makes sense, because it wants you hit all points on the route. But it's not always optimal if all you want is to get back to a point on the route as quickly as possible.
To the last observations made by @carl-lee, I don't know for sure if adding shaping points on the Zumo will destroy the route. But my best guess is that it will. I think that playing with the track sections of a 1.2 route, with adding either Shaping points or Vias, will communicate to the Zumo that all bets are off and trigger a total route recalculation.
Why do I say this? It's not 100% apples-to-apples, but when I export the track of a MRA route as a GPX and then import it into Garmin Basecamp, everything is fine after converting the Track to a Route. If at that point I try to make any modifications, either Shaping or Via, I get a BC warning message to the effect that a total recalculation will take place. I'm guessing this logic also applies to 1.2 routes on the Zumo. An example of Garmin being Garmin.
It might be an interesting experiment to conduct, but someone else will have to pick up that torch. -
Adding shaping points to the route on the Zumo will likely destroy the route as the complete route is recalculated to include the applied shaping point. When you convert a track to a route in Basecamp it gives a start and finish and includes any Via points. But on the XT at least if you go route and haven't switched off automatic recalculation it will recalculate the route on the zumo according to the preferences set. There is a way round this on Basecamp to force a track to create a load of shaping points but its not really relevant to an MRA discussion.
-
Adding shaping points to the route on the Zumo will likely destroy the route as the complete route is recalculated to include the applied shaping point. When you convert a track to a route in Basecamp it gives a start and finish and includes any Via points. But on the XT at least if you go route and haven't switched off automatic recalculation it will recalculate the route on the zumo according to the preferences set. There is a way round this on Basecamp to force a track to create a load of shaping points but its not really relevant to an MRA discussion.
@Mzokk Thanks for the confirmation. I'm a simple man who doesn't want to get bogged down in the nuances of possible exceptions to what happens most of the time. In my short period of testing and use of 1.2 GPX routes, my firm conclusion is not to make any modifications that would trigger a route recalculation. Off-route recalculation for re-entry is OK, because the base route itself is not modified. My first instinct will still be to reenter a route under my own control, but the option for the Zumo to do that for you is clearly there.
Everybody has their own approach to route planning/creation/execution. At a high level, my separation of duties is that all route modifications happen at the MRA Routeplanner level. If I want to make any Shaping/Via point changes, I go back to Routeplanner, perform the updates, and then re-copy the route back to the Zumo. In other words, Routeplanner is the repository for managing my routes. I have my own folder system for keeping everything sorted out. I view the Zumo as the execution layer. Similar in concept to the old IT Client/Server model. It's just one way of doing things, but it's a simple separation of duties and it works for me.
As a side note, in being active on this forum, it seems like many members view routes as a "suggestion" that should be flexible to change through repeated skipping of waypoints. That seems to me where a lot of people get tripped up. I guess different views on things are what makes the world go around.
-
I'm new to MRA but I've been working to understand gpx and zumo for a long time. I think I can offer a bit of clarification here.
From a zumo perspective, the key difference between MRA's 1.1 and 1.2 is not that shaping points are eliminated, but that route point extensions are included. They are essentially track points, just formatted and handled differently.
If a route is transferred into the zumo without route point extensions (e.g. MRA's gpx 1.1), it will be calculated based on all available route points, both via and shaping. If the route does include route point extensions (e.g. MRA's gpx 1.2), it will not be recalculated unless the route is subsequently changed.
If a route is fully recalculated by the zumo, the route point extensions are discarded, the route is calculated based on all available route points, both via and shaping. New route point extensions will be generated. Route point extensions are the result of route calculation, never an input to the calculation.
When using CEP, or going off-route with recalculation allowed, the zumo will indicate that it is calculating, but is is not recalculating the entire route. It is only calculating a small route segment. Route point extensions are preserved.
Adding or removing a route point, via or shaping, will result in a full route recalculation, discarding all previous route point extensions. Since MRA's 1.2 discards shaping points, only the via points are available to recalculate the route.
This implies that it would be better to import a route which includes via, shaping, and route point extensions.
I should also note that recent firmware version 6.60 for the zumo XT2 improved off-route recalculation behavior.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
-
71126.3k
-
026410
-
1215264
-
018446
-
0344
-
19555
-
0242
