Zumo User Forums

@Peobody

Agree with @proofresistant
There is a lot to discover

Peobody wrote: Tue Jan 13, 2026 1:25 pm Also, which export option should be used for TripManager-to-XT transfer?

To create trips directly from a GPX TripManage, will accept anything with routepoints in it. <rtept> If you find anything that doesn't work, while it should, I will be happy to take a look.
Of course you can just transfer the 'Complete route' to the GPX internal storage, or SD Card. How the XT(2) handles that remains to be seen.

But whatever format you choose. If the XT(2) has the chance to recalculate it, you can not be sure that the result will be the same. Given the fact that NO export I have seen will add the <subclass> (other than BaseCamp, or MapSource) you can expect that a recalc will happen on import.

If you want to be sure that the trip in the XT(2) is the same, there are only 2 options I know of:
- Calculate in BaseCamp, with the same maps, same transportmode, same calculatationmode and sent that to the XT(2). Using the standard BC functions, or TM.
- Transfer a track, and on the XT(2) convert that to a trip.
Note: I have bad experiences with Traffic Info. That is known to mess up routes. I disable that completely.

Kurviger, despite how good it looks, will not change that.

- You can have Kurviger, or Trk2Rt by @smfollen, create a lot of extra shaping points, that will minimize the chance of route differences, but it will also make it harder for the XT(2) to calculate a sensible alternative when you have to deviate.

You can have Kurviger, or Trk2Rt by @smfollen, create a lot of extra shaping points, that will minimize the chance of route differences, but it will also make it harder for the XT(2) to calculate a sensible alternative when you have to deviate.

Yes, that is exactly the way I see it. It is the nature of digital navigation rather than any particular route planning software or device. Routes are flexible but less stable because they are made up of a small number of points. Tracks are inflexible but very stable because they are made up of very large numbers of points. They are the two extremes of the spectrum. Adding shaping points to a route makes it more stable at the cost of making it less flexible. Trk2Rt, and Kruviger apparently, just let you dial in where you want to be along that spectrum.

Thanks @FrankB and @proofresistant. I have much more playing to do.

While you guys were responding, I looked in the .gpx files of the exports and only the ones exported with embedded Garmin route points also contained route point extension entries (a<gpxx:RoutePointExtension> section between each route point). BC wouldn't import those.

I haven't attempted to transfer any of the exports to my XT but I think I will copy them to the SD and them attempt imports just to see what happens.
I will continue watching the related discussion in the hopes of identifying what works for Kurvinger > Basecamp > TM > XT.

@Peobody

Did a small test with my XT (Still serves me well!) I had a route that I exported in Kurviger as:

- Gpx
- Gpx Advanced

- Zumo XT
- Zumo XT2

I see no advantage(s) in using anything other than GPX.
XT and XT2 just add a lot of gpxx:rpt that the XT does not use, it only takes long to recalculate.
In my test there was no difference between standard GPX and GPX advanced.

I would recommend to tick the checkbox to include the track, so you can show that on the map.
To have additional shaping points, set Additional waypoints to Interval.
(@jfheath Yes I know the term Waypoints is used incorrectly according to Garmin standards) In TripManager tick:
Trips (Recalc option doesn't matter, it will ALWAYS recalc, because there is no <subclass>)
Tracks

To verify the result after recalculating check out this document: https://frankbijnen.github.io/TripManag ... hagpx.html

I just took a quick look - For what its worth:
tM WK 3B Kurviger.gpx contains a common [uncalculated] route and a track.
tMo0-actDef- WK 3B Kurviger Shp 4tMo0 4Trd2 (2).gpx contains a calculated route (gpxx extension points) but without subclass, and a track.

Trk2Rt handles the first one, but only semi- handles the 2nd one. I'll fix that but it will be of limited use since Kurviger can add the additional shaping points itself. It might be helpful to someone who does not use Kurviger but gets a Kurviger route from a friend?

FrankB wrote: Tue Jan 13, 2026 3:57 pm I would recommend to tick the checkbox to include the track, so you can show that on the map.
To have additional shaping points, set Additional waypoints to Interval.

I did not include the track but my first export included additional waypoints set to Interval. BC errored on import attempt.

I have edited the route names in the exported gpx file so as to tell one from the other and now have them on the SD card. Grandbaby just arrived so I'm redirecting my "play". I'll be back later (hopefully during nap time).

Peobody wrote: Tue Jan 13, 2026 4:32 pm I did not include the track but my first export included additional waypoints set to Interval. BC errored on import attempt.

Choose "File Format", not "Navigation Device"
Set the type to *.GPX

My route imports in BC

Edit:
What BC does not like is the AventurousLevel that is emitted when exporting type: Navigation Device = XT TripManager has no problems with that, so you can send the GPX directly to the XT, without importing it in BC

FrankB wrote: Tue Jan 13, 2026 4:47 pm Choose "File Format", not "Navigation Device"
Set the type to *.GPX

I choosed "File Format" but i set type to GPX Advanced, with Waypoints
Route will imports in BC also, looks like: Then was AventurousLevel not included also.

Peobody wrote: Tue Jan 13, 2026 4:32 pm Grandbaby just arrived so I'm redirecting my "play". I'll be back later (hopefully during nap time).

A grandbaby who might be taking a nap, what a wonderful grandchild

FrankB wrote: Tue Jan 13, 2026 4:47 pm Choose "File Format", not "Navigation Device"
Set the type to *.GPX

Ahhh, I chose the XT device.

proofresistant wrote: Tue Jan 13, 2026 5:35 pm Then was AventurousLevel not included also.

Is this question specific to exporting from Kurviger as a .GPX?
FWIW, the two of mine (exported as device=XT) that would not import into BC contained this:

proofresistant wrote: Tue Jan 13, 2026 5:35 pm A grandbaby who might be taking a nap, what a wonderful grandchild

She's 15 months old. Nap time is my rejuvenate time, like taking a break at a job. She'll grow out of them too soon.

As for import into the XT, all three imported. The two that contained embedded Garmin route points look to have calculated as designed whereas the one without them did not. None of them show the name of the restaurant POI that is the end point, nor the restaurant POI chosen as an interim Via that I had forgotten about.
The naming of the route points is interesting. I wouldn't mind it if it wasn't for the missing POI names. The route with the Kurviger-added additional waypoints lists like this:
Start
Additional Waypoint
Shaping Point 1
Via Point 2
Shaping point 3
Additional Waypoint
Shaping point 4
Destination