I’ve made some testroutes with Kurviger Tourer for my Garmin Zumo XT (NTU Garmin cards) and must say the result isn’t quite what I hoped it would be. First of all: the (extra) curvy routes/tracks made by Kurviger are excellent and what I was looking for. Now the problems start while transferring them to the XT. I always export the tracks, show the track on the XT and convert to a route. In more than the half of the testroutes I made, there were problems. These were eg: long straight lines to certain points, no turn instructions till the last ca 2 km, recalculation didn’t work correctly (was on automatic as it’s said this should work on the XT). After some investigation I believe the problems were mostly due to eg unpaved roads (which are already avoided max), shaping- or viapoints which were not exactly on the route, little unknown roads, … So basically most of the problems are because of differences in the Kurviger maps vs the NTU-maps used by the XT. I know it’s possible to use Basecamp to get this right, but that’s a lot of extra work and what I just wanted to avoid (import track in BC, make direct route with extra viapoints, change to motorcycle profile, check if each (!) viapoint is exactly on the route, make a track, export route and track to XT …). So Kurviger has no real advantages for me when I have to do this for each route. There’s a shortweek trip planned shortly, and I want to avoid that I can’t ride most of my planned routes because of this problems.
Sorry for the long text above, but I wanted to be clear. Now my principle question: can anybody help me on how to get a track to my XT which won’t cause any (or close to any) problems because of differences in the used maps (used by Kurviger vs the NTU-Garminmaps)? I know how to export, import, … so that’s not the question. I’ve also read the different docs concerning OSM & possible problems in route calculation, issues with turn instructions, … but I’m looking for some tips&tricks to avoid as many problems as possible (without having to use Basecamp).
I would say the problem is that when you import the GPX file to your gps it recalculates the route according to the maps or routing data and obviously it does so according to the information on your gps.
If you look at the TRACK of your file you will see that it is really what you have generated from Kurviger.
I always import the track (no route), and converting to a route mostly looks ok, until I start riding.
Acording to the doc. the best solution is to use Basecamp, right? Only: importing track and make a route in BC also gave problems (unpaved road, waypoint not on the route and missing turn indication for 90% of the route).
In order to create a .gpx file for co-riders with as little effort as possible (because I use the Kurviger app on my smartphone), I “developed” the following procedure:
create the route in Kurviger Tourer,
set all waypoints on the road,
look for u-turns in turn instruction
export the route in .kurviger format
then switch to gpxshaping.de and import this .kurviger file
this website inserts enough shaping points to force Garmin to follow the track
Thanks, but what exactly do I have to do after importing the .kurviger file? Export as .gpx? And with which settings? (sorry, as I’m not familiar with this website/tool).
Only I’m afraid this won’t solve my problem on the differences between the kurvigermaps and the garmin NTUmaps, or am I wrong?
Yes! (There is a excellent helpfile in this website)
Sure there are differences between the maps (therefore I use kurviger app). The “trick” is, to provide a route with enough waypoints and not Garmin let define the waypoints based on just the track.
Okay - even with my procedure there isn’t a 100 % guarantee to get the exact route - but it’s close!
Ok, I’ll give that a try (can’t test right now), does the .gpx contain the route, track and/or waypoints?
To be honest, in most cases - although it would we nice - there’s no need that the routes follows the track 100% (when I ride alone or in front, I’ll find my way).
My main issue is that there occur problems while riding (like straight lines, missing turn instructions, …) and that’s very frustrating, due to map differences. So only check in Basecamp would be 100% sure?
PS: I don’t think adding waypoints will solve my problem.
Bart,
no idea - I never used BaseCamp and never had a Garmin device. But friends said with “fastest route” and “recalculation off” it’s okay.
I didn’t hear of “straight lines” or “missing turn instructions” on my tours.
Wer kennt diese Probleme: meine Routen verarbeitet mein XT nicht . Immer hängt sich das XT auf und fängt neu zu laden. Dann bleibt dies bei 78% oder 99% hängen, muß das XT ausschalten und beim neuen Laden ist die Route dann wieder zu sehen. Auch weichen die Routen oft ab, z.B. eine zusätzliche Straße ist zugefügt worden. Oder die Route wird auf " Karte" richtig angezeigt, wenn es los geht wird es dann doch nicht richtig angezeit. Ist Kurviger mit dem XT nicht kompatibel ?
Ich sage schon mal Danke im Voraus für euer Feedback.
I had a look at Kurviger generated GPX, and they always include <trp:CalculationMode>ShorterTime</trp:CalculationMode> .
So make sure to modify your Garmin settings to Shorter Distance before calculating the road, or update the GPX with a proper editor like VS Code.
Also you MUST change the “out of road recalculation” from “automatic” to “ask” (probably another text, sorry, mine is in French).
You could also edit the GPX (it’s just a specific XML file) and update all “FasterTime” to “ShorterDistance”.
As others said, if you export a Track, you will have the choice to follow the pink line whatever happens.
Do NOT convert to road.
The best solution for me is to have a reinforced phone/tablet instead of a Garmin. They program with their feet and are still living in the last century with USB Mini. One of those brands where you buy products you hate.
and