Route to track convertion

[Jack van Tilburg]

@Guzt said in Route to track convertion:

saved automaticaly in the track logs

I like your idea. But the created route track should then be saved in the personal library. Not with the track logs, because as the name suggests, they are logs. So from routes driven.

[Guzt]

@Jack-van-Tilburg I thought that that was obvious that the track should than be saved in one's personal library of tracklogs.
Routes imported from or driven or just made makes no difference.
I normally use basecamp and there it much easier: just 2 clicks.

[Con Hennekens]

@Guzt, What @Jack-van-Tilburg means it that it is not a tracklog (recorded breadcrumb trail) but a routetrack (a breadcrumb generated from a planned route). These are stored at different locations. A tracklog will be found in the tracklog folder, a routetrack will be found between the routes. Basecamp probably does not distinguish between these formats.

[Jack van Tilburg]

@Guzt
It's clear what you mean! And it's a good suggestion!
It's just the terminology used.

[Hans van de Ven MR.MRA]

@Guzt

When you save or export the route the track is included

[Jack van Tilburg]

@Hans-van-de-Ven-MRA-Master
I am pretty sure @Guzt knows that.
And I am pretty sure he means this function in Mapsource
Just right click and choose convert to track in the contextmenu. The result is a track in the same folder as the route.

[Hans van de Ven MR.MRA]

@Jack-van-Tilburg

I know that fuction. Also that you can edit a track in Basecamp.

[Guzt]

@Hans-van-de-Ven-MRA-Master Your answer is besides the point I'm addressing.
When e.g. a standard member makes a route in OSM and you import it into your routes and you change the map set, the route will change. In order to have a reference you need the track for comparising. So before changing the map set, you need to save the track first and then import it again in your tracklogs folder before you can use it as an underlay in the mapset suitable for your gps. Even when one uses the same mapset you need the track before you can optimize the route (fastet to shortest and drag the route to the track). When you do this and send the route as a gpx1.1 (route, track, POI) to any one they will ride the same route for 99.99% (calculating algorithms in the gps differ from those in the route planner) after recalculation of the direct route in the gps (I hate track to route convertion in the gps as one loses the waypoints in the route and is only handy for large driving events where the route is split up in sections from stop to stop and one doesn't have to care about what gps is used).
Another advantage of recalculating routes in both fastest time and shorter distance is that a garmin user can leave the recalculation mode in the gps on 'on". Even the XT users I know whom uses MRA prefer this method i.s.o. using the gpx1.2
I have been using this same principle in basecamp for years now and even when I import an optimized BC route in MRA I still have to make changes just due to different calculating algorithms or small map set differences.

[Mike Walker]

Hi all - just to add I agree with the OP. It seems counter-intuitive to have to export and import from MRA to save the track. I also use the same functionality in Basecamp but am keen to see about moving to MRA because the cloud functionality is so much better.

[Con Hennekens]

@Mike-Walker, Actually, I expect such a function when the web planner gets it's overhaul sometime this year (hopefully!)

[Mike Walker]

@Con-Hennekens and do we think the functionality to display a track whilst navigating a route might also make an appearance at some point soon?

[Con Hennekens]

@Mike-Walker, I really don't know. I would welcome that, but given the fact that the app already shows the initial route line the use case for showing tracks (that are not the route) is rather limited. I doubt that it will get priority, bu I also know it will make some people happy