Zumo User Forums

It looks like routes and GPX files from Kurviger https://kurviger.com/ can be transferred with TripManager also

At least in principle; I have currently tested it with my Tread 2 device.

But i noticed that only the option with recalculation actually makes sense.
The other options i didn'd testet, because i didn't found ghost points in the GPX Files from Kurviger and require recalculation.
In my opinion, it probably also makes sense to have routes from other sources recalculated in the device

I would recommend checking the calculation mode for route in the device, because although I used “Fast” in Kurviger, but “Adventurous” (without the second additional attribute) i found in the GPX file.

Then I noticed a "suboptimal feature".
Kurviger can also export the track in addition to the route in the GPX file.
However, the track then has the same name as the route.
If I now select the route and track from the GPX file during TM transfer and I want to transfer both the stripped route and the track, “only” the track of the route (which unfortunately is not a track due to missing waypoints) is transferred and the “real” track with the same name is missing.
Here is my question for @FrankB:
Could an option be added to TripManager so that if the “real” track name in the destination GPX “Tracks_*.gpx” is already used by the ‘route’ track name, the real track will saved with a suffix (e.g., may ” 2") in the GPX olso?
By the way, same Names for Route and Trip can be content from BC also
Here is an example of what a GPX file looks like when saved from Kurviger.

proofresistant wrote: Fri Jan 09, 2026 10:08 pm Here is my question for @FrankB:

I will look into it. I agree that it is not useful to send a track with no <trkpt>, while there is a complete track in the original GPX.
In this case I would also prefer the track, and not the route. Would that be a solution, if TM also prefers the track?
Btw: For stripped routes the route is always taken.

An alternative, that can only be used when sending to the device, is to send the Complete GPX.

Yes, if so, preferably send the track, that would also be OK.

Then, I don't really use/need the complete route as GPX.
When I import GPX into the device, I somehow prefer the stripped route, I mean stripped routes are imported faster and have to/should be recalculated in the device anyway.

@proofresistant

I have fixed TripManager, to prefer the track of the original GPX, if there is also a route in it.

If you care to test it, you can find the pre-rel in the usual place

Now you were almost too fast But I think that's better than before, even for BC routes with tracks of the same name.

I'll test it out.


So, now for the reason why you were almost too fast.
I took a closer look at “Kurviger” (and I like it more and more).
But then I also saw that you can export GPX specifically for the Zumo XT2.
Then, with the export for the XT2, the routes also have ghost points, and these are of course also used by TM in the generated track.
Last but not least regarding my statement: "I would recommend checking the calculation mode for route in the device, because although I used “Fast” in Kurviger, but “Adventurous” (without the second additional attribute) i found in the GPX file."
If you use the zumo XT2 Export Option, there is also the second additional attribute like "<trp:AdventurousLevel>Adventurous</trp:AdventurousLevel>"


Here's an example – Kurviger export for XT2:

So the German's are also pretty good at planning software!

I would have done the TripManager fix anyway, because it didn't make sense to create an empty track.

I belive this TM 1.7.0.365 works verry well now with this situationn

I testet track exports following with my Tread 2:

• if gpx with eq name for track and route and route with ghostpoints,
  TM export the track (fine)

• if gpx with different name for track and route and route with ghostpoints,
  TM export both, the route ghostpoints as track and the track also (fine)

• if gpx with route and route with ghostpoints,
  TM export the route ghostpoints as track (fine)

• if gpx with track,
  TM export the track (fine)

I will observe it more in future, but for the moment it is ok

Thanks for testing.

Forgot to mention. The same logic applies when creating KML, HTML and FIT files
Even 'Add to Map' is affected, when you look at the legend at the right there are less options.

I played with Kurviger a little bit yesterday using the free access without creating an account. I created an 83 mi (133 km) route picking a spot on the map near my home as the Start, a restaurant POI as the End, and adding two interim shaping points. I then exported it three times using each of the export options and then tried to import each one into Basecamp to see if I could figure out the differences. Only the export that did not contain embedded Garmin route points imported; the others failed with an error. Basecamp did not show the start and end points as waypoints, they were only visible when looking at the route details. The Basecamp component is important to me because I frequently share routes with other riders who may modify them using Basecamp. Is the Kurviger-to-Basecamp desire a deal breaker for using Kurviger? Perhaps I missed something in my process, or the Kurviger free access is limited? Advice would be appreciated.

Also, which export option should be used for TripManager-to-XT transfer?

Peobody wrote: Tue Jan 13, 2026 1:25 pm Only the export that did not contain embedded Garmin route points imported; the others failed with an error. Basecamp did not show the start and end points as waypoints, they were only visible when looking at the route details.

Try for testing may the export options:
File Format: GPX Advanced
Content: Export waypoints

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

I myself had only tried Kurviger out in the last few days.
Help in gaining experience is welcome.

I'm currently leaning towards:
GPX Advanced with Route and Waypoints
or
zumo XT2 (pure, although I couldn't import route points into BC with it)