Creating a Route from a Track

No. Basecamp will create the route based on the settings it has and on the map used. It should though be easy enough to insert shaping points so that the route does mimic the track. Just keep both visible in Basecamp and adjust so that they match.

Yes, I can and do that.

I want BaseCamp NOT to recalculate, but just convert what I've given it.
If I've got to check and correct what it has done, I may as well have created the route in BaseCamp in the first place.

I have been given a GPX track for a bicycle ride, and I wish to convert it into a route with turn-by-turn directions. The track is 101miles long in and out of the lanes in the midlands of England.

My other option is to just transfer the GPX as it is into my Montana and follow the pink line on the map.
To be honest, that's a foolproof and simple system and I don't have to bother with any "re-calculating" in BaseCamp or on the Montana.

When I have created a route in BaseCamp and transferred it to my Montana, I have sometimes had problems.
The route is good and accurate when it leaves BaseCamp, but when I go to Route Planner in the Montana and select the route and "View on Map", then press Go, the Montana then re-calculates again. Sometimes the route isn't shown exactly the same as I created, especially if the route is a circular one ie finishing back where I started and perhaps coming back along the same roads.

Ho hum.
No matter.
I can manage!

Regards,
Mick.

Along with sussamb's good advice, I'd add that having the same exact waypoint for the start and finish of a route is asking for trouble. Though it seems logical enough to us, the GPS just does not like it and will often get confused. Creating a new start or finish waypoint just a short distance away can sometimes clear up perplexing route issues such as mystery loops and odd detours. It also prevents the frustrating error of a route refusing to begin navigating because it thinks you have already reached the end.

-dan

Yes Dan, you are exactly right.
I have a problem with Garmin's navigation generally because it doesn't like an "out and back" route.
Even if I create a route for a large circular bike ride, I still have to come along the same lanes back home. Some routes can be three or four miles on the same road I went out on.

The only way out of this, is to start the route further out and finish somewhere else. Maybe another alternative is to divide the route into pieces so nothing is the same on each piece.

BaseCamp and Garmin devices are great for doing an A to B route, but if you want them to follow a pre-determined route, you have a great deal of a problem.

I have an Audax to do in May. I've never done one before, and TBH I probably won't do one again, but the idea is fun for now. It's just over 100miles on a pre-determined route and I have to follow it faithfully and stop at checkpoints along the way to qualify and prove I've done it. All I have is a very basic GPX and a PDF version of a route sheet.

BaseCamp would be wonderful if it would produce a turn-by-turn route for uploading into my Montana. Except it won't do if FAITHFULLY unless I can look at the original and make the new route correct and adjust it to be faithful ............. but I'm sure when I upload it into my Montana, it will recalculate it again! By the time I'm actually riding this Audax, I won't KNOW I'm on the correct route.

I don't think I can win on this, so I'll stick with the basic GPX and follow the pink line on the map. At least I know that it will be correct.

Regards,
Mick.

In your situation I'd do that also ... Stick to a track so you know it'll be 100% correct.

Yeah,
it's the only way.

Pity really, as Mr Garmin could convert a track to a route if he wanted.

A little story from my ride yesterday ..........
I devised a route along roads I knew well. I didn't need a map or a satnav or anything technical. It was 53miles up to North Cornwall and back over Davidstow Moor. I left home at 0845 and was home again by 1300.

I'm trying to get to grips with my Montana having previously had a 705 and before that a 305. The Montana has a large screen and my tired old eyes can see it easily. Therefore I'm at last exploring the Garmin navigation experience. I created a route for my ride in BaseCamp and transferred it to the Montana. The route I created was exactly what I wanted.

Some time into the ride, I noticed that Monty wasn't showing the correct route, but I carried on the way I wanted to go. Monty then re-calculated. Trouble is, he re-calculated the whole ride! Whereas I had (say) 40 more miles to ride, I suddenly had 60. I carried on regardless and watched as Monty tried to cope.

He wanted me to go down roads I had no intention of riding on. Still he re-calculated. Eventually, the far point where I was turning for home he showed as a dog-leg and wanted me to double back the way I had come. Still he re-calculated, and each time he did, the result was further than the route I had left to ride! I eventually gave up with the experiment and stopped navigation and followed my nose home.

I know I could turn re-calculation off and let Monty carry on regardless. Maybe that's what I should have done? Trouble was, the route that I gave Monty from BaseCamp wasn't the route he calculated and showed on his map. There were differences from the start.

I feel that Garmin's navigation programs are great for finding your way, but if all you want is confirmation that you are where you want to be and on the road you wanted to be on, they are found wanting.

Thanks for letting me rant.
Mick

Doesn't the Montana have a 'do not recalculate' setting :confused:

Yes, that's what I said in my penultimate paragraph.

The route you load from BaseCamp isn't necessarily what ends up on the screen on the Montana.

Mick.

... I have a problem with Garmin's navigation generally because it doesn't like an "out and back" route.
Even if I create a route for a large circular bike ride, I still have to come along the same lanes back home. Some routes can be three or four miles on the same road I went out on.

The only way out of this, is to start the route further out and finish somewhere else. Maybe another alternative is to divide the route into pieces so nothing is the same on each piece...

Mick,

This has not been my experience. I've done a lot of pre-planned routes, including 10 days of back roads from coast to coast in the US for the Scooter Cannonball in 2005. The "out and bacK' problem is pretty much restricted to identical start/finish points. I have had many successful "loop" routes that re-use a particular road. You may want to experiment by first making sure the start and finish are far enough apart to prevent problems when it recalcs -- and I'd recommend forcing BaseCamp to recalc to see how it will behave later in your GPS. And force it to recalc in your GPS too, before you use it on the road and discover horrors like the one you described above. By the way, when one gets past you and recalc does wreck the rest of your route, just cancel and re-import the route.

Examine every via and turn to see if placement errors have crept in and caused bad loops. Yes, this is tedious compared to importing a track, but the more you do it, the more you will learn to spot potential pitfalls that can ruin a route during recalc and it will take less time to create subsequent routes. On my motorcycle I need voice directions, so tracks are not an option and so I've learned to make routes that are "recalc-proof."

Hope this helps,

-dan

Sorry to joint this discussion late but, I've been making Routes from Tracks since the beta-BC offered the feature and I've been sending those Tracks and Routes to my Montana since v3.90 added the ability to navigate saved Routes without recalculating them. From the above discussion it is difficult for me to determine why your track2route conversion is going so poorly. The whole idea of creating a route from a track is that portions of the converted route may not be on routable roads.

The Route created is a Direct Route in BaseCamp. You need to also make sure you do not exceed 250 via points in the Direct Route. If you change that to Driving, then yes, it's going to recalculate the route and screw it up. If you send that Direct Route to the Montana it will not recalculate it if you are in Direct mode or unless your have not updated your Montana's software in a very long time or you exceeded the 250 via point limit. With Direct Routes, out-n-backs are not an issue.

If you want your Route to be a Mixed-Travel Route, then you will need to edit the Direct Route in BC to convert (recalculate) some of the route segments to Driving mode. This will also produce a route that the Montana will not recalculate but a Mixed-Travel Route cannot exceed 50 via points on the Montana.