GPX Versions 1.1 vs 1.2 for Garmin Visually Explained

[John S Parry]

@Steve-Jarrell said:

Thanks very much for the update. You clearly showed the HUGE advantage that 1.2 has over 1.1. Quite simply the route is forced to follow the track.

It's been fun learning about 1.2, and understanding the pros/cons vs. 1.1

To your point, the advantages are many. Developing a route using MRA Routeplanner, and literally being guaranteed that it will import as designed into an XT device is gold. Much has been said about the Sync function in MRA providing WYSIWYG on the app. But that's not 100% true. Depending on off-line or on-line execution in the app, the route can recalculate differently. Ask me how I know.

If there is a notable downside to 1.2, it's that you no longer have shaping waypoints available for skipping during route execution. It seems many here are constantly skipping to change the original route during execution. And there are many posts about how users get in trouble using that function. It's not a downside for me personally, but for others.....

The other issue I've encountered is that 1.2 doesn't seem to be supported in Basecamp. Meaning, if I create a 1.2 GPX and import it into BC, it gets munched up. At least that was my early experience. I'll have to go back and try it again to be 100% sure.

Otherwise, 1.2 ahead....

[Mzokk]

It has been an interesting discussion, and thanks John for the good wishes.

Anyhow with regard to Garmin devices one thing I will say "and why I keep my XT mounted as a backup" is that the hardware itself is well made robust and reliable. These are all mine since 2004 and they are all in working order and all have been through some horrendously wet weather. Its unlikely that any of us will have a functional phone for that long.

The main reason I've ended up here is the disappointing software provided for the XT (Explore) by Garmin and the change to its routing algorithm which meant, that compared to the old devices, what you produced on Basecamp bears little relation to what you get on the XT unless you "pin" the route with lots of shaping points. I'm pretty happy with the MyRoute app routing program and navigation app with the exception of POI and track handling capabilities. But at least with phone based navigation you are not restricted to Garmin's poor software offering. A lesson I hope they learn before its too late.

[Steve Jarrell]

@John-S-Parry "It's been fun learning about 1.2, and understanding the pros/cons vs. 1.1".

I agree completely. I think it's been a valuable learning experience for all of us that use MRA in conjunction with a Garmin device.

[John S Parry]

@Mzokk said:

The main reason I've ended up here is the disappointing software provided for the XT (Explore) by Garmin and the change to its routing algorithm which meant, that compared to the old devices, what you produced on Basecamp bears little relation to what you get on the XT unless you "pin" the route with lots of shaping points. I'm pretty happy with the MyRoute app routing program and navigation app with the exception of POI and track handling capabilities. But at least with phone based navigation you are not restricted to Garmin's poor software offering. A lesson I hope they learn before its too late.

Wow, that's quite a collection of devices. Very nice.

Overall, your reasoning is fair. I personally did not enable Explore for either my XT or XT3 due to the disaster it creates for most users. It does nothing for you unless you want to buy into Garmin being an ecosystem across its devices. "Pinning" lots of shaping points is something I'm used to anyway since I lead rides and distribute GPX files to the other riders. You never know the routing preferences set up on other devices, so overloading shaping points is an absolute requirement.

MRA Routeplanner is the best route creation SW out there. I'm OK with BC, and it's remarkably capable for what it is. But Web based technology makes BC largely obsolete. The MRA Phone navigation piece?? I've tried to like it, but it doesn't speak to me the way an XT device does. It's another subject, but for me, phone HW isn't built for reliability in hot climates. I live/ride in the USA southwest, where phone overheating while running navigation is almost guaranteed 3-4 months of the year. Aside from phone HW limitations, an XT device is more capable than phone navigation SW at many levels. Again, another subject. What struck me most when going from my XT to an XT3 are the improvements to 3D Terrain map. The rendering is eye popping. It's looks like viewing from a Drone when riding through mountains and canyons. It's hard going back to the XT much less the MRA phone map.

Having said all this, I get that we all have different criteria and therefore end up with different setups. And there is nothing wrong with that.

[Simon James Hancock]

Question for John.
when you create your routes in MRA do you save as 1.2 or 1.1 ?
As well as many shaping points do you add and via points?

[John S Parry]

@Simon-James-Hancock said:

Question for John.
when you create your routes in MRA do you save as 1.2 or 1.1 ?
As well as many shaping points do you add and via points?

Prior to this topic explaining 1.2, I used 1.1 exclusively. Now that I understand 1.2, I'll be using 1.2 moving forward. The only exception being when I create routes for others. Many of my riding friends use Basecamp for importing GPX files, and then transferring them to their devices. Basecamp doesn't work correctly with 1.2, so I'll use 1.1 for compatibility.

As far as shaping points, I add as many as are needed for the route to calculate correctly in a Garmin. I've found that in general, a moderately complex MRA route requires fewer shaping points to create than are needed on the Garmin side. Sometimes it's an iterative process of going back-and-forth between MRA and Garmin to make adjustments to get both in sync.

Via points are different. Because they're essentially stopping points, your route intent will dictate how many you create.

[Mzokk]

@Steve-Jarrell said:

@John-S-Parry "It's been fun learning about 1.2, and understanding the pros/cons vs. 1.1".

I agree completely. I think it's been a valuable learning experience for all of us that use MRA in conjunction with a Garmin device.

Well, Well, Well. I wonder what sort of humble pie you'd recommend?

After having my right eye Cataract sorted last week and after several weeks without riding I thought I'd take a ride and try out my XT using GPX 1.2 without having alternative OSM maps loaded on the device (but not enabled). To my surprise, and delight, I was able to go off route and be routed back using prompted recalculation without the XT recalculating the remainder of the route, or recalculating the route to the next via point. As expected adding a detour to the route will force a recalculation to the next via point but a casual detour does not.

This makes the XT a bit more useful to me again as MRA routes will be displayed as designed rather than me having to check a GPX1.1 route against the track. Thanks folks for raising this subject and triggering me to revisit use of the XT.

[Steve Jarrell]

@Mzokk I have a LOT of favorites as I've had to eat a LOT of it over the years!

[John S Parry]

@Mzokk said:

To my surprise, and delight, I was able to go off route and be routed back using prompted recalculation without the XT recalculating the remainder of the route, or recalculating the route to the next via point. As expected adding a detour to the route will force a recalculation to the next via point but a casual detour does not.

Congratulations on getting back on the bike. I hope the Cataract surgery went as expected.

In my mind, prompted recalculation is one of the strengths of the XTs. I'm glad you were able to experience that yourself.

[Andy Beviere]

I am amazed that people are still persevering with Garmin’s!?

MRA to plan the route, put it straight on to my DMD tablet, never recalculated a route once… touch wood!!! I will never ever after so many ruined rides and too a certain extent holidays use Garmin again!

Great article though @steve-jarrell