Problems Converting Tracks to Routes in 4.3.3

Since updating to 4.3.3, some significant functionality appears to have gone. What I could do in previous versions was convert a track to a route, and specify how many waypoints to insert. Now it just takes the start and end and calculates a route between them. This is not what I want.

Has this functionality been removed, and if not, where is it now. If it has been removed, is the previous version available somewhere please.

0 SUSSAMB over 11 years ago

Still there ... right click track and select Convert to route, up pops the box asking for no of waypoints

0 keffs99 over 11 years ago

Thanks for the reply, but not on mine. It just starts calculating the route. And now it's giving an error and can't calculate the route. I am going to uninstall, and reinstall again.

0 SUSSAMB over 11 years ago

Good idea. Sounds like it's not installed correctly.

0 keffs99 over 11 years ago

Done that, and no difference. Also, when right clicking a route or track, there used to be an advanced menu, which is not there anymore. Is there a link to a previous version, because this was all working fine before updating to 4.3.3.

0 SUSSAMB over 11 years ago

Latest is 4.3.4 ... Try that

0 keffs99 over 11 years ago

I have done. No luck.

0 SUSSAMB over 11 years ago

Very strange then as mine is all working perfectly, as was 4.3.3 etc

0 Former Member over 11 years ago

I found a workaround last week; if I choose Direct activity in the taskbar of BaseCamp and then create route from track I get the route, with the designated amount of via-points. After that I change the routing activity within the route and recalculate the route with the needed activity.

There are reports that with some tracks it does function.

The function itself is changed, because during the conversion the shaping points are removed from the route. Which means you cannot change the route anymore, every change lets the route recalculate and the route is not correct any more. The only thing you can do with this route is send it to a device and use it.

If you use the direct activity approach, then the route will be usable for further editing.

0 Former Member over 11 years ago

It appears from the various posts about this topic that the track to route is actually working as expected, however some users would still prefer that their routes be editable after the initial calculation.

I have opened a case for this although I am not sure what kind of traction it will get or when. It is now on the radar though.

Thanks for all the feedback.

0 Former Member over 11 years ago

It appears from the various posts about this topic that the track to route is actually working as expected, however some users would still prefer that their routes be editable after the initial calculation.

It's not always working correct. In the case you have older tracks and/or track points not place close to a road (which also is often the case with older tracks), the track to route calculation fails. I have done some tests and with me the conversion often fails with errors like; can't calculate a route.

For consideration, what is the purpose of a route in BaseCamp if you may not edit it anymore? The most confusing part is the communication around feature changes like this, it works correct and without any warning or clear notification in BaseCamp the function is changed in in my eyes a useless feature.

This function used by transferring routes/tracks to devices I can understand, but also with these added features, communication from Garmin to users is not clear, lots of users have problems with loading routes to devices, only because in BaseCamp the options for device transfer a enabled by default.

Communication about changes is the key! Please put communication to the top of the Case list!
(of every case and todo list at Garmin please!).

We need more explanation about changing functionality and not just let the users find out there self (throwing it over the wall, without even saying: good luck ;) )