GPX Versions 1.1 vs 1.2 for Garmin Visually Explained
-
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.
@smfollen-0 "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."
Exactly! For the person who doesn't clearly understand this yet, this key difference is VERY important when the Garmin calculates the route. I'll illustrate here what happens during a 1.1 vs. 1.1 route import.
Let's take a route created with created in MRA that includes 4 via points (starting via point + ending via point + 2 more) and 6 shaping points for a total of 10 total reference points as an example:
In simple terms, a 1.1 route in the .gpx file looks like this:
starting via point 1 -> shaping point 1 -> shaping point 2 -> via point 2 -> shaping point 3 -> shaping point 4 -> via point 3 -> shaping point 5 -> shaping point 6 -> ending via point 4.
When this 1.1 route is imported into the Garmin it will calculates its own route using its own logic between each of these 10 shaping and via points based on its settings (fastest, shortest, etc). Many times that route doesn't go exactly where you planned or how it looked in MRA, and it does not match the track.
On the other hand, a 1.2 route in the .gpx file looks like this
(For simplicity's sake I'm going to refer to "route extensions" as "track points" as both of them are simply latitude/longitude pairs that are like breadcrumbs that precisely mark the desired path between two points.)
starting via point 1 -> track points -> via point 2 -> track points -> via point 3 -> track points -> ending via point 4.
When the route is imported there are no shaping points in the 1.2 .gpx format as you pointed out. Instead, the 1.2 route includes a large number (for a normal route many hundreds or even thousands) of track points that force the Garmin to calculate the route EXACTLY as you had planned and EXACTLY the same as your track file.
Good discussion. Thanks for the input!
Steve Jarrell
Western North Carolina USLifetime Routeplanner Gold & Navigation Next
2025 BMW R1200GS
2025 Can-Am Spyder
DMD T865-X 8" Tablet
Garmin XT3 -
@smfollen-0 "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."
Exactly! For the person who doesn't clearly understand this yet, this key difference is VERY important when the Garmin calculates the route. I'll illustrate here what happens during a 1.1 vs. 1.1 route import.
Let's take a route created with created in MRA that includes 4 via points (starting via point + ending via point + 2 more) and 6 shaping points for a total of 10 total reference points as an example:
In simple terms, a 1.1 route in the .gpx file looks like this:
starting via point 1 -> shaping point 1 -> shaping point 2 -> via point 2 -> shaping point 3 -> shaping point 4 -> via point 3 -> shaping point 5 -> shaping point 6 -> ending via point 4.
When this 1.1 route is imported into the Garmin it will calculates its own route using its own logic between each of these 10 shaping and via points based on its settings (fastest, shortest, etc). Many times that route doesn't go exactly where you planned or how it looked in MRA, and it does not match the track.
On the other hand, a 1.2 route in the .gpx file looks like this
(For simplicity's sake I'm going to refer to "route extensions" as "track points" as both of them are simply latitude/longitude pairs that are like breadcrumbs that precisely mark the desired path between two points.)
starting via point 1 -> track points -> via point 2 -> track points -> via point 3 -> track points -> ending via point 4.
When the route is imported there are no shaping points in the 1.2 .gpx format as you pointed out. Instead, the 1.2 route includes a large number (for a normal route many hundreds or even thousands) of track points that force the Garmin to calculate the route EXACTLY as you had planned and EXACTLY the same as your track file.
Good discussion. Thanks for the input!
Instead, the 1.2 route includes a large number (for a normal route many hundreds or even thousands) of track points that force the Garmin to calculate the route EXACTLY as you had planned ...
Actually, for 1.2 the Garmin does NOT calculate the route (on import and for [some] off-route or Closest Entry Point cases). It just uses what was imported without change, which is why it matches the original.
In cases where it does recalculate the 1.2 route, it would use only starting via point 1 -> via point 2 -> via point 3 ending via point 4. This is why, when a full route calculation occurs on the zumo, a 1.1 route with both via and shaping points would produce a result closer to the original than a 1.2 route.
Which is why
smfollen-0 said:
... it would be better to import a route which includes via, shaping, and route point extensions.
-
My input here is to agree with @steve-jarrell in that a quick revision of the route in MRA is probably the best way here (easy with Tread syncing). I’ve had some less than agreeable results adding shaping points to a GPX1.1 test route on the Zumo trying to revise it. I gave up on the idea, especially as I’ve never needed to do it in anger.
We’re still surmising what might happen here without a full test. In truth, I’ll probably never need to do it but it’ll be nice to know.
-
My input here is to agree with @steve-jarrell in that a quick revision of the route in MRA is probably the best way here (easy with Tread syncing). I’ve had some less than agreeable results adding shaping points to a GPX1.1 test route on the Zumo trying to revise it. I gave up on the idea, especially as I’ve never needed to do it in anger.
We’re still surmising what might happen here without a full test. In truth, I’ll probably never need to do it but it’ll be nice to know.
My input here is to agree with @steve-jarrell in that a quick revision of the route in MRA is probably the best way here (easy with Tread syncing)
I agree entirely. I was only trying to shed a little light on what the zumo is, and isn't, doing.
I'm new to MRA, but so far I'm impressed. -
Instead, the 1.2 route includes a large number (for a normal route many hundreds or even thousands) of track points that force the Garmin to calculate the route EXACTLY as you had planned ...
Actually, for 1.2 the Garmin does NOT calculate the route (on import and for [some] off-route or Closest Entry Point cases). It just uses what was imported without change, which is why it matches the original.
In cases where it does recalculate the 1.2 route, it would use only starting via point 1 -> via point 2 -> via point 3 ending via point 4. This is why, when a full route calculation occurs on the zumo, a 1.1 route with both via and shaping points would produce a result closer to the original than a 1.2 route.
Which is why
smfollen-0 said:
... it would be better to import a route which includes via, shaping, and route point extensions.
@smfollen-0 smfollen-0 said:
"... it would be better to import a route which includes via, shaping, and route point extensions."
I don't believe that's possible with our currently available .gpx file export options.
There simply isn't a .gpx format that includes via, shaping and route extensions (track points) all in the route section of the same .gpx file. They are mutually exclusive
The 1.1 .gpx format includes VIA and SHAPING POINTS embedded in the route section of the .gpx file. It does NOT include "route extensions" (track points) in the route section.
The 1.2 gpx format includes VIA and TRACK COORDINATES (route extensions) embedded in the route section It does NOT include shaping points in the route section.
Neither the 1.1 nor the 1.2 .gpx format contain BOTH shaping points AND track points (route extensions) in the route section of the .gpx file. If I'm wrong, I'll gladly admit it.
We are all here to learn, and I'm no exception!!
-
When I use my Garmin devices for navigation for navigation I tend to use GPX1.1 (plus a track of the route) because for me it's more flexible, as I often lead groups and want the option to use route recalculation and to be able to manually skip optional route loops which may or may not contain via points (when time becomes tight). For example, routes round Lochs, Loughs, Lakes or up and down valleys. If using my XT, or my Zumo 390/340 on the other bike, skipping a via point will force a route recalculation and destroy the rest of the route. If you have shaping points then the route is only altered to the next shaping point and the rest of the route is maintained.
This means that quite a few shaping points are required to pin the route to the intended roads. For the XT this is more important as its "Faster Time" routing algorithm now equals "faster roads" whereas the older Zumo 390/340 will route on any road that it determines is producing a "Faster Time" between points. I think this change has been effected as Garmin just use car navigation device firmware and software in their motorcycle units these days. To ensure that routes are pinned for use on my (Now Backup) XT these days I often use the MRA expand function to increase the number of shaping points on a route before I export it to the Zumo XT.
For me the easiest way to avoid all the faff with Garmin units is to use MRA for navigation on my Africa Twin screen then the routes are WYSIWYG. Bottom line is there are no right or wrong answers just find a strategy that gets you where you want to be. This was true even when we used maps some folk marked a line on the map and kept it in a clear pocket on the tank. I made a "tulip road book" with road numbers left and right turns and rough distances in between.......the map only came out when I got lost
-
When I use my Garmin devices for navigation for navigation I tend to use GPX1.1 (plus a track of the route) because for me it's more flexible, as I often lead groups and want the option to use route recalculation and to be able to manually skip optional route loops which may or may not contain via points (when time becomes tight). For example, routes round Lochs, Loughs, Lakes or up and down valleys. If using my XT, or my Zumo 390/340 on the other bike, skipping a via point will force a route recalculation and destroy the rest of the route. If you have shaping points then the route is only altered to the next shaping point and the rest of the route is maintained.
This means that quite a few shaping points are required to pin the route to the intended roads. For the XT this is more important as its "Faster Time" routing algorithm now equals "faster roads" whereas the older Zumo 390/340 will route on any road that it determines is producing a "Faster Time" between points. I think this change has been effected as Garmin just use car navigation device firmware and software in their motorcycle units these days. To ensure that routes are pinned for use on my (Now Backup) XT these days I often use the MRA expand function to increase the number of shaping points on a route before I export it to the Zumo XT.
For me the easiest way to avoid all the faff with Garmin units is to use MRA for navigation on my Africa Twin screen then the routes are WYSIWYG. Bottom line is there are no right or wrong answers just find a strategy that gets you where you want to be. This was true even when we used maps some folk marked a line on the map and kept it in a clear pocket on the tank. I made a "tulip road book" with road numbers left and right turns and rough distances in between.......the map only came out when I got lost
@Mzokk Excellent points. In an ideal world everyone on a group ride would have the exact same GPS with the current maps and most current sw version. Since that's never going to be the case the lowest common denominator is the track file and that's what I see being distributed most often for these rides.
If you're leading a ride I can see where your 1.1 gpx file route combined with the track file would be a better option than a 1.2 file. I hadn't thought of that before.
Thanks!!
-
Ok, I've been having another play.
I loaded my local GPX1.2 test route through Tread and with it syncing all the way. I then started a simulation and let it run a little. After a while, I edited the route by adding a couple of shaping points. I was issued with a warning that "editing will discard the route settings and calculate a standard route". Nevertheless, I did it to see what occurred.
This:
It both did and did not destroy the original route. Yes, it went by my new shaping point diversions and then headed for the next via point, discarding the rest of the planned convoluted route to get me there. But - both the original track (obviously) and the original route overlaying it are still there on the XT2 map screen. What I was unable to do on the simulation was to ignore the new route to the via point and rejoin my original just by riding to it. However, what I could do was to stop the route and restart with CEP. Success, the route was still there and it navigated me back to it and onto the rest of my original MRA planned route.I did try adding another shaping point after my diversion ones, this time back onto the original route but it still wanted to route around and back after it to take me to the next via point. Just a thought but it still gets you onto the route where you can restart with CEP.
I had to know as even though a quick replan with MRA on my iPhone would do the trick easily, there may be that time with no phone signal so it won't open. All worst-case scenario stuff that I've not needed before and it does prove that a replan on the Garmin stops your planned route but it's still there. Schrodinger's route!
-
@steve-jarrell I lead rides regularly. We're all on MRA so riders can load there route however they like on all the different Garmins that we have. So long as the track is available (which it is) and visible, everyone can see where we are going. None of this "my satnav says down there" anymore. The track don't lie.
If I'm leading, I'm keen to have the best and quickest option available. 1.2 routes load really quickly and don't make their own minds up.
Another con I had found when planning away from home is that plotting a shaping point exactly on the road on either a phone or tablet can be tricky and with GPX1.1 there must be many of them to pin your route. This can often lead to your track being sent over correctly but the route not calculating on the Zumo. The answer is to convert the track to a route but with all the pitfalls. 1.2 seems to calculate through Tread quite easily.
There's probably more to find out but so far, so reasonable.
-
@carl-lee Whether it's 1.1 or 1.2 if you realize their limitations AND you supplement them with the track (that never changes...) you're in good shape.
With 1.2 it is FAR easier to initially create a route in MRA that goes exactly where you intend for it to go on the Garmin. There's absolutely no question about that.
-
Ok, I've been having another play.
I loaded my local GPX1.2 test route through Tread and with it syncing all the way. I then started a simulation and let it run a little. After a while, I edited the route by adding a couple of shaping points. I was issued with a warning that "editing will discard the route settings and calculate a standard route". Nevertheless, I did it to see what occurred.
This:
It both did and did not destroy the original route. Yes, it went by my new shaping point diversions and then headed for the next via point, discarding the rest of the planned convoluted route to get me there. But - both the original track (obviously) and the original route overlaying it are still there on the XT2 map screen. What I was unable to do on the simulation was to ignore the new route to the via point and rejoin my original just by riding to it. However, what I could do was to stop the route and restart with CEP. Success, the route was still there and it navigated me back to it and onto the rest of my original MRA planned route.I did try adding another shaping point after my diversion ones, this time back onto the original route but it still wanted to route around and back after it to take me to the next via point. Just a thought but it still gets you onto the route where you can restart with CEP.
I had to know as even though a quick replan with MRA on my iPhone would do the trick easily, there may be that time with no phone signal so it won't open. All worst-case scenario stuff that I've not needed before and it does prove that a replan on the Garmin stops your planned route but it's still there. Schrodinger's route!
@Carl-Lee You are a real glutton for punishment!
I assume that it recalculated the entire route as well beyond the next via point. That's the behavior that I've notice while doing my testing.
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
-
71237.0k
-
19261
-
010356
-
021575
-
0259
-
091.3k
-
0374
