How to import gpx - via Route or Route-Track?
-
I'm a new user on MRA, but I have many years of experience with BC.
When I import a Google Maps *.gpx file with via points into MRA - what's the best way to do it?- If I import it as a Route-Track and generate a route from the track using MRA:
MRA generates many waypoints but no longer indicates the via points (which isn’t a problem since we can easily convert the few necessary waypoints into via points). - If I import it as a Route:
MRA imports the GPX file correctly and displays the via points correctly, but I don’t see any waypoints that define the exact path of the route.
My question is:
What is the best way to then - safely - follow the route using MRA Navigation Next (on android)?
What happens if the route needs to be recalculated during navigation and there aren’t enough waypoints set?
Will MRA Navigation Next calculate to the next Via point as there are no visible waypoints???
To be on the safe side, should I manually set additional waypoints along the route when importing as a route?Many thanks for your feedback
- If I import it as a Route-Track and generate a route from the track using MRA:
-
I'm a new user on MRA, but I have many years of experience with BC.
When I import a Google Maps *.gpx file with via points into MRA - what's the best way to do it?- If I import it as a Route-Track and generate a route from the track using MRA:
MRA generates many waypoints but no longer indicates the via points (which isn’t a problem since we can easily convert the few necessary waypoints into via points). - If I import it as a Route:
MRA imports the GPX file correctly and displays the via points correctly, but I don’t see any waypoints that define the exact path of the route.
My question is:
What is the best way to then - safely - follow the route using MRA Navigation Next (on android)?
What happens if the route needs to be recalculated during navigation and there aren’t enough waypoints set?
Will MRA Navigation Next calculate to the next Via point as there are no visible waypoints???
To be on the safe side, should I manually set additional waypoints along the route when importing as a route?Many thanks for your feedback
@KaTo6668, Importing as route imports only the routepoints. The actual route is then calculated according to the settings (quickest/shortest, avoid options etc.) so the shape of your route can be different after import.
Importing as route track imports only the track (if available in the sourcefile) so you will lose any route points, but your track is shaped like the original route.
It all depends on your own preferences. I usually import both, and shape the route according to the track manually by adding shaping points. That way you do not lose routepoints, and you can add a lot of information to the route that can be handy while navigating. If you are not interested in such thing, navigating the track is perfectly fine.
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.
Check out RideSleepRepeat.eu, a biker community for sharing stays across Europe
- If I import it as a Route-Track and generate a route from the track using MRA:
-
@KaTo6668, Importing as route imports only the routepoints. The actual route is then calculated according to the settings (quickest/shortest, avoid options etc.) so the shape of your route can be different after import.
Importing as route track imports only the track (if available in the sourcefile) so you will lose any route points, but your track is shaped like the original route.
It all depends on your own preferences. I usually import both, and shape the route according to the track manually by adding shaping points. That way you do not lose routepoints, and you can add a lot of information to the route that can be handy while navigating. If you are not interested in such thing, navigating the track is perfectly fine.
@Con-Hennekens Thank you very much for your fast reply.
Your approach is exactly what I had in mind.
Import route and track, compare them, and then finalize/shape the route with additional shaping points.Maybe you can also answer the following question for me:
Unfortunately, shaping points in the MRA Routeplanner are displayed just as large as route points (via points), just with a different marker.
I believe I can hide shaping points during navigation with MRA Navigation Next?
Is that also possible in the MRA Routeplanner, or at least to display the waypoints much smaller? There may be reasons for the size of the waypoints, but for me, their size makes route planning confusing...
Thank you. -
@Con-Hennekens Thank you very much for your fast reply.
Your approach is exactly what I had in mind.
Import route and track, compare them, and then finalize/shape the route with additional shaping points.Maybe you can also answer the following question for me:
Unfortunately, shaping points in the MRA Routeplanner are displayed just as large as route points (via points), just with a different marker.
I believe I can hide shaping points during navigation with MRA Navigation Next?
Is that also possible in the MRA Routeplanner, or at least to display the waypoints much smaller? There may be reasons for the size of the waypoints, but for me, their size makes route planning confusing...
Thank you.
@KaTo6668, No there is no method for differentiating the size of shaping- and via points. Not in the planner and not in the app. To be honest I don't see a reason for them to be different in size. They both have the same purpose: define a route. If it is bothersome for you, you probably use too many routepoints to begin with
Also there is no way of hiding shapingpoints of a route while navigating. In the current public version there is an option to hide shaping points when the feature "navigate route as track" is enabled. But I need to warn you that in the upcoming V6 version things considering track navigation will be different.
Please uphold the the correct terminology:
- Routepoints are waypoints that define a route
- Shaping points are routepoints that can be skipped automatically when missed
- Via points are routepoints that cannot be skipped automatically when missed
-
@KaTo6668, No there is no method for differentiating the size of shaping- and via points. Not in the planner and not in the app. To be honest I don't see a reason for them to be different in size. They both have the same purpose: define a route. If it is bothersome for you, you probably use too many routepoints to begin with
Also there is no way of hiding shapingpoints of a route while navigating. In the current public version there is an option to hide shaping points when the feature "navigate route as track" is enabled. But I need to warn you that in the upcoming V6 version things considering track navigation will be different.
Please uphold the the correct terminology:
- Routepoints are waypoints that define a route
- Shaping points are routepoints that can be skipped automatically when missed
- Via points are routepoints that cannot be skipped automatically when missed
@Con-Hennekens sagte:
in the upcoming V6 version things considering track navigation will be different.In which way?
-
@KaTo6668, No there is no method for differentiating the size of shaping- and via points. Not in the planner and not in the app. To be honest I don't see a reason for them to be different in size. They both have the same purpose: define a route. If it is bothersome for you, you probably use too many routepoints to begin with
Also there is no way of hiding shapingpoints of a route while navigating. In the current public version there is an option to hide shaping points when the feature "navigate route as track" is enabled. But I need to warn you that in the upcoming V6 version things considering track navigation will be different.
Please uphold the the correct terminology:
- Routepoints are waypoints that define a route
- Shaping points are routepoints that can be skipped automatically when missed
- Via points are routepoints that cannot be skipped automatically when missed
@Con-Hennekens Thanks again for your fast reply.
You're absolutely right; shaping points and via points define a route and are equivalent within the route definition.
But beside of the route definition, they are not equivalent.A shaping point should simply defines the route's path. Even though you can add additional information to it in the MRA Routeplanner (color/text/icon, etc.) - for whatever reason. And since it’s really only meant to define the route’s path, there is a reason you can set the option in the MRA Navigator that it can be skipped automatically which -in my opinion- should be the default setting. That’s why I also don’t see a benefit why a shaping point appears at all during MRA navigation in the upper right corner.
A via point must or should be visited because it’s important to the planner for whatever reason (break, coffee, refueling, hotel, etc.).
That’s why I asked about different icon sizes in the MRA Routeplanner - because they aren’t all equally important.And yes, maybe I sometimes use too many shaping points, but sometimes it’s necessary to define the exact route - and then things get confusing.
But that’s just my opinion, and I’d love to learn more about the benefit why you can assign additional information to a shaping point in the MRA Routeplanner - information that, in my opinion, is only relevant for a via point.
Even though I’m new to MRA and certainly don’t know many of its features yet, I really like the program
-
@Con-Hennekens Thanks again for your fast reply.
You're absolutely right; shaping points and via points define a route and are equivalent within the route definition.
But beside of the route definition, they are not equivalent.A shaping point should simply defines the route's path. Even though you can add additional information to it in the MRA Routeplanner (color/text/icon, etc.) - for whatever reason. And since it’s really only meant to define the route’s path, there is a reason you can set the option in the MRA Navigator that it can be skipped automatically which -in my opinion- should be the default setting. That’s why I also don’t see a benefit why a shaping point appears at all during MRA navigation in the upper right corner.
A via point must or should be visited because it’s important to the planner for whatever reason (break, coffee, refueling, hotel, etc.).
That’s why I asked about different icon sizes in the MRA Routeplanner - because they aren’t all equally important.And yes, maybe I sometimes use too many shaping points, but sometimes it’s necessary to define the exact route - and then things get confusing.
But that’s just my opinion, and I’d love to learn more about the benefit why you can assign additional information to a shaping point in the MRA Routeplanner - information that, in my opinion, is only relevant for a via point.
Even though I’m new to MRA and certainly don’t know many of its features yet, I really like the program
I’d love to learn more about the benefit why you can assign additional information to a shaping point in the MRA Routeplanner - information that, in my opinion, is only relevant for a via poin
For instance if you want to add some spoken information about that shapingpoint, or the place where you've placed it. If you add tekst in the textfield of a shapingpoint that will be spoken, if you've activated that in your settings. Like "a beautifull statue on your right"
-
@Con-Hennekens Thanks again for your fast reply.
You're absolutely right; shaping points and via points define a route and are equivalent within the route definition.
But beside of the route definition, they are not equivalent.A shaping point should simply defines the route's path. Even though you can add additional information to it in the MRA Routeplanner (color/text/icon, etc.) - for whatever reason. And since it’s really only meant to define the route’s path, there is a reason you can set the option in the MRA Navigator that it can be skipped automatically which -in my opinion- should be the default setting. That’s why I also don’t see a benefit why a shaping point appears at all during MRA navigation in the upper right corner.
A via point must or should be visited because it’s important to the planner for whatever reason (break, coffee, refueling, hotel, etc.).
That’s why I asked about different icon sizes in the MRA Routeplanner - because they aren’t all equally important.And yes, maybe I sometimes use too many shaping points, but sometimes it’s necessary to define the exact route - and then things get confusing.
But that’s just my opinion, and I’d love to learn more about the benefit why you can assign additional information to a shaping point in the MRA Routeplanner - information that, in my opinion, is only relevant for a via point.
Even though I’m new to MRA and certainly don’t know many of its features yet, I really like the program
@KaTo6668 I think having the shaping point appear in the upper right is excellent, for me it is really useful as I colour code my shaping points
if there is some information about the road ahead I will colour code that shaping point pink & add text either into the point name or notes
it could be something like "Warning tarmac end - road turns to gravel ahead" or "Warning sharp right bend after blind crest"
seeing the colour coded point well in advance means I am well aware of the that a hazard is coming up aheadI don't want these points t be Via points as it is not necessary for me to pass them, but if I am on the correct path I would like the warning
if your only interested in times/distances to Via points just toggle through the 3 settings of the large ETA button at the bottom centre of the screen
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login-
08200
-
04103
-
1422
-
0483.7k
-
028230
-
07496
-
011300