GPX Versions 1.1 vs 1.2 for Garmin Visually Explained

[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.

[Steve Jarrell]

@John-S-Parry I figured that the recalculation was going to happen and screw up the route. I agree completely with your conclusions including that restarting the route and selecting the closest point as the starting point would have probably put you back on your intended route.

The Garmin has a LOT of gps coordinates in the track that's embedded in the route section of the 1.2 gpx file so it should be able to take you to the closest coordinate to where you are without recalculating the route.

If you test it let us know, and I'll do the same. Thanks a lot for the update!

[Simon James Hancock]

Great thread and great work by all.
What colour do you use to show your track and thickness? I have difficulty seeing mine.

[Mzokk]

Tracks can be set at various widths on the Garmin Unit for the XT at least (the XT2/3 might be similar) the maximum track width is too thin to be seen beneath the route unless the route diverges. To change the displayed track width you need to edit a Theme file. These files are stored on the XT and can be accessed and changed here on the unit. I created a theme called Widetrack which means that the track is always wider than the magenta route line and easily seen. By default this is not the case.

There are several themes available on the unit and the default for UK units is unsurprisingly United Kingdom.

To change the Default width of the track I copied the United Kingdom theme on the unit these are .kmtf files and can be read and edited by a text editor such as Notepad.

They are accessed by connecting your unit to a computer.

This is a list of the themes onthe UK units and there might be a layout you like more than the one you are using. I copied the uk theme and changed the name to Widetrack.kmtf.

to Edit the >kmtf files open in notepad

And scroll down to the track width parameter in the text file. The default for the parameter of track width is "1.00" by default I changed this by trial and error to "2.50" you can fiddle with this yourself to devise a width that suits.

For comparison this is the same parameter in the original file. You can mess with all of the parameters and as long as its with a named file of your own making you can't break anything.

Don't forget to change the name of the theme at the top of the file in the text editor so that you can select it in the menu on the unit and it does not overwrite the theme file you altered.

With the wider track in the theme you can have it look like this during navigation.

I usually select yellow but you can pick whatever track colour you prefer.

[Carl Lee]

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.

[Simon James Hancock]

I am trying to avoid using tread. I do al my planning in MRA and save to the garmin sd card.

[Steve Jarrell]

@Simon-James-Hancock On my XT3 I use black and set it to the widest width and I can see it just fine. I had forgotten all about the Theme file that @mzokk detailed but I had to create one for my XT in order to see my track as well

[Steve Jarrell]

@Carl-Lee said:

"And if you are using Tread, the track must be put in a collection that is visible."

Note that it doesn't matter if you're using the Tread app or not. I normally don't use Tread. I place my .gpx files in the /gpx folder using a USB connection.

When the Garmin XT3 imports them it asks me which collection to put them in. If the visibility of that collection isn't turned I will see the route when you select it, but I won't see the track.

[Steve Jarrell]

@Simon-James-Hancock I don't like using Tread either. I use a USB C to C cable directly from my Macbook Pro to my XT3 and use the free OpenMTP app to manually place my .gpx files in the /gpx folder. It's VERY fast and works 100% of the time.

If I do have the Tread app connected to my XT3, Tread (and the Explore website) will automatically synch with collections, routes and tracks that I manually put on the Garmin.

(Geek overload section follows)

Here's a screenshot of what the OpenMTP app looks like on my Macbook (this would look basically the same if I was using File Explorer on a PC) when I've copied my .gpx files into the \gpx folder before the XT3 has imported them into its internal memory.

The interesting thing that I've discovered is once the XT3 imports the .gpx files, it deletes the Track section from the file but leaves the route information (which in the 1.2 format contains a copy of the track) in the file and does not delete the file. The result of this is that even if you delete the route in the Garmin's internal memory a copy of it is still in the \gpx folder, and it can be imported again and again.

If you've manually uploaded a gpx file into the \gpx folder it's up to you to delete it manually which is fine with me. Tread skips the \gpx folder and loads the gpx information directly into the devices internal memory.