Loading BC GPX files into XT3

[jfheath]

Yes.

I didn't want to write another lengthy essay because I already documented it pretty well - here, for the XT1, but still relevant. app.php/ZXT-P25

I would normally Export a selection for BC as a gpx file, rather than let BC transfer it, which was the point of my comment. Give it a filename of my choosing and then use file explorer (PC) to drop it onto the SD card.

With the XT2, Waypoints can be imported more than once, but only one version is kept. None are duplicated.
Tracks and routes can both be imported more than once - and they are given the same name with a suffix.

With the XT2, tracks are imported automatically at start up, and the code for the track is stripped out of the gpx file so that it cannot be imported again.

Behaviour with the XT2 I documented here - and subsequent pages. app.php/XT2-P336

Just information. As you say - whatever works best, is best. But for me, having been a long time advocate of exporting to Internal Storage (faster access) - I now use the SD card - for the reasons that I describe in those links.

[louiseravot]

Yeah, you can load BaseCamp GPX files onto the XT3, but sometimes it’s not as straightforward as expected. For me, the easiest way is to export your routes as GPX, then transfer them via USB into the device’s GPX folder or use Garmin Drive to import them. One thing to watch out for is how the XT3 interprets routes vs tracks. I say this because converting routes to tracks in BaseCamp first gives more reliable results when following them on the device.

[FrankB]

or use Garmin Drive to import them.

Garmin Drive App is not compatible with the XT3!
For the XT3 you must use Tread App. And that app has it's own rules, quirks and bugs.
I recommend using TripManager viewtopic.php?t=3150 if you transfer your routes using a US cable. (But I'm biased)
For the XT3 be sure to get the most recent version. https://github.com/FrankBijnen/TripMana ... V1.7.0.382

[jfheath]

One thing to watch out for is how the XT3 interprets routes vs tracks. I say this because converting routes to tracks in BaseCamp first gives more reliable results when following them on the device.

Hi @louiseravot

Do you mean that you load the track and then convert it to a route on the XT3, and follow that ? Or does the XT3 have a different way of using a track. ( I don't have an XT3 - but the XT2 has a number of ways of using tracks:

i) Loading the track and selecting Go. No instructions given, the track never changes - but your position is the focus of the screen - and if you have strayed away it plots a dotted magenta line indicting where the closest point of the track ahead is. The display shows how far away that is. It is a very relaxing way of navigating, putting you in control and never changign where the route is. But no good if you want instructions and the route recalculate if you have to go a different way.

ii) You can use the Zumo screen to convert the track to a Route. You can load this and it gives instructions and if you stray away from the route it plots the roads to take to get you to the closest point of the route ahead (the same point as indictaed in the method above). This method has an issue - if you have to deviate from the route in such a way that the closest point is where you left the route, rather than ahead - it gets stuck in an infinite loop - because the way that it recalculates ensures that the closest point is always behind you ! So it is more flawed than following a route.

iii) You can use track and routes both drawn on the same map. The route gives instructions. The track showing your original intention remains fixed and becomes visible when the route recalculates. This is the most foolproof method for unknown areas.

But by far the best method is to use Trip Manager (as FrankB has just said) and display the track for reassurance. Route produced by TripManager do not have any of the issues that are present using the traditional transfer of method of routes to the Zumo. That is because it by-passes Garmin's and Tread's habit of changing routes and route points.

If you want more info on any of the above then take a look at my sequence of pages describing 6 ways of using the Zumo to navigate here:
app.php/ZXT-P45
It was written for the XT1, but applies equally to the XT2 - and probably to the XT3 as well. If it doesn't match what you see on the XT3, then I would love to know.

[raza]

Planned route created in BC and saved in GPX on local disk.

Premmik BC.JPG (68.58 KiB) Viewed 509 times

Using TripManager GPX transferred to SD in XT3. After import and calculation in XT3, shape points on AC are moved to the oncoming lane...

2026-04-24_145853_23313.png (611.09 KiB) Viewed 509 times

I haven't noticed these shifts on local roads.

2026-04-24_150055_35476.png (1.37 MiB) Viewed 509 times

[smfollen]

One thought @raza Do you have route points at intersections? For example, a point at the intersection of the highway on-ramp and the road crossing the A2? Basecamp may take the point as on the road and the zumo may take it as on the ramp which leads to the A2. It is best to avoid placing points at intersections.

Also the zumo takes the "faster time" routing preference to mean faster roads so it tends to route onto the nearby A2, even if it takes longer.

[raza]

The intersection has no connection for moving points. Another design point has been placed on this AC, which has branches quite far away. The point is moved parallel to the opposite lane of the AC.
BC:

ZS.JPG (64.6 KiB) Viewed 497 times

XT:

2026-04-24_180856_10365.png (1.36 MiB) Viewed 497 times

2026-04-24_180932_13989.png (633.8 KiB) Viewed 497 times

[danham]

The only time I have seen this happen (XT1) is when the map I used in BC and the one in the XT are not the exact same version. You probably know this, but thought I'd ask just in case.

-dan

[raza]

Everything updated to the latest versions.

[smfollen]

Sorry, I'm out of ideas. Hopefully somebody else can figure this out.