From Route to Track?
-
I wouldn't know why but if you really want it you could save the route as GPX 1.1. using the "save as" menu item and then import it again.
Ik zou niet weten waarom maar als je het echt wilt dan zou je de route als GPX 1.1. kunnen opslaan via het menu item "opslaan als" en daarna weer importeren.
-
Can I do this, if yes - how?
Let's say I created a Route in the Route Planner on my
Windows 11 Comp.
Now I want to create a Track from it.Is there a way to easily do it without saving the Route as a Track, saving it in some library and then uploading it back to the Route Planner?
Thanks!@Lenny-O as @white-mouse wrote: if you have planned a route in MRA-Routeplaner, it's a route and not a track. You can't transform it directly in MRA-Routeplaner from route to track.
The only way is: save it as gpx 1.1 (Track, POI) locally, and upload it again to MRA-Routeplaner.
One more hint, becaus we don't understand your intention: if you have also purchased MyRoute-App for navigation - and your route has been synched - you can use the option: navigate the route as a track.
-
I get the question because sometimes i want the same.
Why?
A route is flexible between the routepoints. A track is fixed. This makes a track more suitable maybe even perfect for comparing and changing a route -
Can I do this, if yes - how?
Let's say I created a Route in the Route Planner on my
Windows 11 Comp.
Now I want to create a Track from it.Is there a way to easily do it without saving the Route as a Track, saving it in some library and then uploading it back to the Route Planner?
Thanks!@Lenny-O said in From Route to Track?:
without saving the Route as a Track, saving it in some library and then uploading it back to the Route Planner?
It is a pita that some people come up with this workaround that you already came up with yourself. I have to presume good intentions...
@Guzzist said in From Route to Track?:
you can use the option: navigate the route as a track.
That option does not necessarily reflect the track as it was at the time of planning. It calculates the track from the route at the moment of the start of your navigation...
Having a fixed route-track available in your library is the ONLY way to ensure a route stil reflects the route as it was at the time of planning it. It is an utterly logical thing to ask for, especially now that navigating tracks made a big step forward!
I would really like an option in the planner to "snapshot" a route in the form of an embedded track, that is automagically shown underneath the route line.
- It would show if a route has been changed immediately after opening
- it would negate the need of calculating a track at the moment of starting navigation (in route-as-track mode)
- tracks of a route could be integrated in the syncing features
- I think it would be a tremendous tool for maintaining RX routes.
I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Streetpilot 2610/Zumo 660/Zumo 395/ CAT S52 + MRA app -
@Lenny-O said in From Route to Track?:
without saving the Route as a Track, saving it in some library and then uploading it back to the Route Planner?
It is a pita that some people come up with this workaround that you already came up with yourself. I have to presume good intentions...
@Guzzist said in From Route to Track?:
you can use the option: navigate the route as a track.
That option does not necessarily reflect the track as it was at the time of planning. It calculates the track from the route at the moment of the start of your navigation...
Having a fixed route-track available in your library is the ONLY way to ensure a route stil reflects the route as it was at the time of planning it. It is an utterly logical thing to ask for, especially now that navigating tracks made a big step forward!
I would really like an option in the planner to "snapshot" a route in the form of an embedded track, that is automagically shown underneath the route line.
- It would show if a route has been changed immediately after opening
- it would negate the need of calculating a track at the moment of starting navigation (in route-as-track mode)
- tracks of a route could be integrated in the syncing features
- I think it would be a tremendous tool for maintaining RX routes.
@Con-Hennekens said in From Route to Track?:
.......
It calculates the track from the route at the moment of the start of your navigation...Isn't it the otherway? Calculates a Route from the Track.
That is what i expect when you select "Ride as track"(I use MRA Next only on Android Auto. Every comment, suggestion, etc will be based on my usage with Android Auto)
-
@Con-Hennekens said in From Route to Track?:
.......
It calculates the track from the route at the moment of the start of your navigation...Isn't it the otherway? Calculates a Route from the Track.
That is what i expect when you select "Ride as track"@M-Schrijver, no, navigating "route-as-track" converts a route into a track (on the fly), and navigates that as a track.
-
I'm totally confused with this. Why create a track from a route when you have a proper route. Please explain.
As you know i use TomTom (Rider and Go) for a decade now. This system takes a track and converts it to a route when selecting it in the navigation. The result is a route which is strict to track as possible (it needs roads). But when you need to re-route from the original route it brings you back to the original route at the closest point possible. When you have traffic info enabled. It uses this info also during conversion and recalculations.
So the benefits of a track (stays strick to the original as possible). And takes care of you along the way (recalculations and traffic info).(I use MRA Next only on Android Auto. Every comment, suggestion, etc will be based on my usage with Android Auto)
-
I'm totally confused with this. Why create a track from a route when you have a proper route. Please explain.
As you know i use TomTom (Rider and Go) for a decade now. This system takes a track and converts it to a route when selecting it in the navigation. The result is a route which is strict to track as possible (it needs roads). But when you need to re-route from the original route it brings you back to the original route at the closest point possible. When you have traffic info enabled. It uses this info also during conversion and recalculations.
So the benefits of a track (stays strick to the original as possible). And takes care of you along the way (recalculations and traffic info).@M-Schrijver said in From Route to Track?:
Why create a track from a route when you have a proper route. Please explain.
Track navigation has been the defacto method of guaranteeing equal routes among different platforms for many years. Whether a route is proper or not you cannot tell in advance when someone else made it (for many people that also counts when they made it themselves
)So, MRA developed a method in which you can ride a route as track, which keeps VIA points and Shaping Points (you can choose!) in your track. This circumvents possible detours due to traffic or differences in recalculation, and ensures that you can re-enter the track at any desired point. You should try it, it works amazingly!
Although I agree that a proper route does not need this, it is fact that opinions on "proper routes" differ greatly... check this MRA video about this:
https://youtu.be/71e_-oX4V48?si=SkNeQH-fZ8LflMUsI am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Streetpilot 2610/Zumo 660/Zumo 395/ CAT S52 + MRA app -
I'm totally confused with this. Why create a track from a route when you have a proper route. Please explain.
As you know i use TomTom (Rider and Go) for a decade now. This system takes a track and converts it to a route when selecting it in the navigation. The result is a route which is strict to track as possible (it needs roads). But when you need to re-route from the original route it brings you back to the original route at the closest point possible. When you have traffic info enabled. It uses this info also during conversion and recalculations.
So the benefits of a track (stays strick to the original as possible). And takes care of you along the way (recalculations and traffic info).@M.-Schrijver said in From Route to Track?:
I'm totally confused with this. Why create a track from a route when you have a proper route. Please explain.
This is actually one of the features that I like in Garmin's Basecamp. Within Basecamp, I can "click" on a route and "Create Track from Selected Route".
Why would I want to do that? Well, I would like to have a "record" of my actual route. It's possible that over time, the software that calculates the route changes, or the underlying map changes hence, the calculated route may change over time. By having a saved copy of the route as a track, I know exactly the path that was taken and can tell over time (says years later) if the route has changed.
MRA should also implement a simple and convenient way to convert a route to a track!.
-
@M-Schrijver said in From Route to Track?:
Why create a track from a route when you have a proper route. Please explain.
Track navigation has been the defacto method of guaranteeing equal routes among different platforms for many years. Whether a route is proper or not you cannot tell in advance when someone else made it (for many people that also counts when they made it themselves
)So, MRA developed a method in which you can ride a route as track, which keeps VIA points and Shaping Points (you can choose!) in your track. This circumvents possible detours due to traffic or differences in recalculation, and ensures that you can re-enter the track at any desired point. You should try it, it works amazingly!
Although I agree that a proper route does not need this, it is fact that opinions on "proper routes" differ greatly... check this MRA video about this:
https://youtu.be/71e_-oX4V48?si=SkNeQH-fZ8LflMUs@Con-Hennekens thanks for the video link
I thought I knew a bit about MRA but that was extremely informative
don't know how I missed all the details about the changes to track navigation
thanks again -
@Brian-McG and @Brett-Bartick and @M.-Schrijver, to add to the confusion
I recently learned that since some recent version low resolution tracks are being included to routes. So, my previous claim from about half a year a go is not really valid anymore. Fact is that nowadays, when navigating "track-as-route", you indeed get a track that should look like it was originally planned, instead of being calculated at the time of starting it in navigation.Personally I indeed saw an increase of sync-time that could be explained by this, but I have no clue as to when that started.
