An offer well worth taking up.If you’d like some more assistance, just shout.
Five minutes or so spent now, might save an hour or more shouting at a dumb (and very deaf) device.
Converting a Detecht Nav route to Garmin
- Thread starter G&T
- Start date
Indeed. I’ve learned with years of listening, playing and learning on here what to look for.
Your original file opened AOK in Kurviger. Just sayin'.
Only a warning about the number of Waypoints
Only a warning about the number of Waypoints
Right fellas, I deep dived the files v the actual route on the Detecht App. There were some differences so I used the download as a template, followed the route in Detecht and redrew in Basecamp adding lots of ‘via points.’ My brain is buzzin.’
My question
The route options are now customised, in various ways per route - not consistent, in Basecamp. I had to to avoid seasonal road closures, tolls, etc and match the Detecht route. When I download the routes to the Nav Vl, will it try to reconfigure to how my Nav options are set up or can I tell it to leave customised so it is exactly the same as what I have in Basecamp?
Thanks
@Wapping @Mzokk @wessie @Paul G (BHT)
My question
The route options are now customised, in various ways per route - not consistent, in Basecamp. I had to to avoid seasonal road closures, tolls, etc and match the Detecht route. When I download the routes to the Nav Vl, will it try to reconfigure to how my Nav options are set up or can I tell it to leave customised so it is exactly the same as what I have in Basecamp?
Thanks
@Wapping @Mzokk @wessie @Paul G (BHT)
If you find the device alters the route significantly, try:
A. Setting the preferences and map on your device to match those you set in BaseCamp. You’ll lose any waypoints the route contains but that maybe doesn’t matter, unless the route(s) contained some vital point(s) that you must go through.
B. Save the route you created in BaseCamp as a track. Then import the track to your device. Next, instruct your device to convert the track to a route.
C. Try inserting more shaping points, to better pin the route down.
But first, just try importing the route and see what happens. Does the route the device displays, match what you created in BaseCamp? It’s best practice to always do this anyway, irrespective. Why? Because it’s much easier to correct faults whist sitting comfortably at home, as opposed to at the side of the road.
PS See this thread and the excellent advice contained in post #5
A. Setting the preferences and map on your device to match those you set in BaseCamp. You’ll lose any waypoints the route contains but that maybe doesn’t matter, unless the route(s) contained some vital point(s) that you must go through.
B. Save the route you created in BaseCamp as a track. Then import the track to your device. Next, instruct your device to convert the track to a route.
C. Try inserting more shaping points, to better pin the route down.
But first, just try importing the route and see what happens. Does the route the device displays, match what you created in BaseCamp? It’s best practice to always do this anyway, irrespective. Why? Because it’s much easier to correct faults whist sitting comfortably at home, as opposed to at the side of the road.
PS See this thread and the excellent advice contained in post #5
Last edited:
I shall be hunting for that ‘match’ button as mentioned by. @stirtloeIf you find the device alters the route significantly, try:
A. Setting the preferences and map on your device to match those you set in BaseCamp. You’ll lose any waypoints the route contains but that maybe doesn’t matter, unless the route(s) contained some vital point(s) that you must go through.
B. Save the route you created in BaseCamp as a track. Then import the track to your device. Next, instruct your device to convert the track to a route.
C. Try inserting more shaping points, to better pin the route down.
But first, just try importing the route and see what happens. Does the route the device displays, match what you created in BaseCamp? It’s best practice to always do this anyway, irrespective. Why? Because it’s much easier to correct faults whist sitting comfortably at home, as opposed to at the side of the road.
PS See this thread and the excellent advice contained in post #5
Will report back.
I have imported all routes from Basecamp to Nav Vl. For context I added lots and lots of via points, so the route is quite locked in.
Findings
There are some discrepancies in distance. Largest about 9 miles over 400 mile distance. I duplicated the route in Basecamp, changed an avoidance feature & sent to Nav. This next bit is important. With your Nav connected, look at the Nav routes list. Change the route colour of your duplicated route. Now you can see any discrepancies. It’s a sort of overlay.
Note
‘Always match the route to the device when transferring’ feature as mentioned above.
From my previous experience. This is fine if you have created a route on the same map as that in the Nav. If an older route created in an older version map, I suggest unchecking box as this will try to reroute to the new map and make changes.
Enough now, I think this whole exercise is unusual as I’m trying to match a route someone has done in an APP. You would normally be creating your own map, with known avoidances etc and then transfer to your Nav with same avoidances ticked. Like for like.
Happy holidays everyone.
Findings
There are some discrepancies in distance. Largest about 9 miles over 400 mile distance. I duplicated the route in Basecamp, changed an avoidance feature & sent to Nav. This next bit is important. With your Nav connected, look at the Nav routes list. Change the route colour of your duplicated route. Now you can see any discrepancies. It’s a sort of overlay.
Note
‘Always match the route to the device when transferring’ feature as mentioned above.
From my previous experience. This is fine if you have created a route on the same map as that in the Nav. If an older route created in an older version map, I suggest unchecking box as this will try to reroute to the new map and make changes.
Enough now, I think this whole exercise is unusual as I’m trying to match a route someone has done in an APP. You would normally be creating your own map, with known avoidances etc and then transfer to your Nav with same avoidances ticked. Like for like.
Happy holidays everyone.
I don't want to piss on your strawberries G&T but that "Match" setting won't match the route on your Nav VI with the route Basecamp produces. It's there to ensure that if a map is produced on one mapset, it can be calculated in another. So say you have NTU 2026.10 maps on Basecamp and NTU 2027.10 on your device (or visa versa) and there have been alterations to the map in either case (new roundabout one way system by-pass). Then the transferred route can be calculated on the alternate map (it might take a bit longer). If you have the settings matched on your unit and Basecamp as stated you have the best chance of the navigation matching. I use "Faster Time" and only offroad avoidance as the settings on Basecamp and the Zumo unit. If the Nav VI uses the old Garmin routing logic like my Zumo 390 then what is produced in basecamp should match the Nav IV pretty well. If it uses the XT logic lots of shaping points will be required to get the route to stay where you want it.
Don’t worry about that.
I had a scenario before a trip whereby I had created routes in Basecamp on say NTU 2026.10. As I was about to download to the Nav a message popped up. New map available 2027.10 (example), I clicked ‘yes’.
When downloading the route to the Nav, it stated ‘Maps were created on an older map, do you want to update route? Something like that.
Well, on the Nav it looked nothing like that which I had created. So I unchecked that match button and then it did look similar. You are right, it took forever to download.
I do think the latest generation of APPs has a lot to offer in terms of removing the whole transfer issue. What you see is what you get.
Thanks for your help Mzokk
