How to Navigate Route as a Track?
-
@Martin-Kjell, Yes that's expected behaviour, if you keep being stubborn and don't follow the suggestion...
What you need to do in such a case, is long-press your own chosen point of re-entry. Then it will guide you to there, insead of back to a point you obviously don't want.@Con-Hennekens Ok Thanks! But reading the manual states that shaping points will be ingored during "route as a track". And Waypoint (via points) is never ignored. A bit contradictaional to me, or (trying to be humble) I'm probably misinterpreting the instructions. In other words, route as a track does not seem to ignore shaping points.
E.g. I would like to point out a route with say for instance 10 shaping points. But circumstances like weather, change of mind, road work etc. makes me pick another route and needed to ignore shaping point #4. Since Ive passed it I would no longer be interested in that one since it's just a shaping point. But MRA "Route as a track" tries to guide me back and after a few tries gives up. For me, theres no difference from normal route. What am I missing? Eager to learn and understand. -
@Con-Hennekens Ok Thanks! But reading the manual states that shaping points will be ingored during "route as a track". And Waypoint (via points) is never ignored. A bit contradictaional to me, or (trying to be humble) I'm probably misinterpreting the instructions. In other words, route as a track does not seem to ignore shaping points.
E.g. I would like to point out a route with say for instance 10 shaping points. But circumstances like weather, change of mind, road work etc. makes me pick another route and needed to ignore shaping point #4. Since Ive passed it I would no longer be interested in that one since it's just a shaping point. But MRA "Route as a track" tries to guide me back and after a few tries gives up. For me, theres no difference from normal route. What am I missing? Eager to learn and understand.route as a track does not seem to ignore shaping points.
But it does. Instead of leading you back to a shaping point, it leads you back to the track. Depending on the density of your shaping points and the layout of the roads, the difference can sometimes be not so obvious.
The way you describe sound perfectly logical. Navigation will lead you back to the track, sometimes that can be through a previous route point, but that does not mean it took it into consideration. Since MRA is a scenic navigation app, it tries to have you drive as much of the preplanned route as possible and only skipps parts of it after multiple redirections.
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
-
MRA prioritizes points over the track (or route), also if the point is (just) a shaping point and you have specified that you want to use all points. So it sends you back if you missed one, even if you are already back on the track.
Corjan wrote this about the release following 5.1 (and I hope that a solution for the issue above will be found, as it is my biggest issue):
-
Rework some internal algorithms such as searching for fuel stations and skipping waypoints
-
Generic track navigation improvements
-
-
route as a track does not seem to ignore shaping points.
But it does. Instead of leading you back to a shaping point, it leads you back to the track. Depending on the density of your shaping points and the layout of the roads, the difference can sometimes be not so obvious.
The way you describe sound perfectly logical. Navigation will lead you back to the track, sometimes that can be through a previous route point, but that does not mean it took it into consideration. Since MRA is a scenic navigation app, it tries to have you drive as much of the preplanned route as possible and only skipps parts of it after multiple redirections.
@Con-Hennekens said:
Since MRA is a scenic navigation app, it tries to have you drive as much of the preplanned route as possible and only skipps parts of it after multiple redirections.This is inherently wrong. Back on track, is back on track and no sending back to missed shapingpoints. This is very confusing for users.
You are deviating and you're guided back to the track/route. When you're near the route you see the blue routeline on the crossing ahead but it goes in both directions (left and right). The navigation tells you to go right. But why is the blue routeline also going left?
But okay, I turn right and after a mile I reached a shappingpoint. Then the navigation tells me to turn around and go back. So taking the left direction was the right one after all. What was the point to send me back to that point?
Did i miss something, besides a shapping point?
A must see?A basic principle of a shapping point it shapes the route nothing more and because of that it is allowed to be missed. The navigation should use this principle and not sending me back to a missed shapping point.
(I use MRA Next only on Android Auto. Every comment, suggestion, etc will be based on my usage with Android Auto)
-
@Con-Hennekens said:
Since MRA is a scenic navigation app, it tries to have you drive as much of the preplanned route as possible and only skipps parts of it after multiple redirections.This is inherently wrong. Back on track, is back on track and no sending back to missed shapingpoints. This is very confusing for users.
You are deviating and you're guided back to the track/route. When you're near the route you see the blue routeline on the crossing ahead but it goes in both directions (left and right). The navigation tells you to go right. But why is the blue routeline also going left?
But okay, I turn right and after a mile I reached a shappingpoint. Then the navigation tells me to turn around and go back. So taking the left direction was the right one after all. What was the point to send me back to that point?
Did i miss something, besides a shapping point?
A must see?A basic principle of a shapping point it shapes the route nothing more and because of that it is allowed to be missed. The navigation should use this principle and not sending me back to a missed shapping point.
@M.-Schrijver, we are not starting that discussion again.
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
-
I think at this point there is still no clarity in understanding the process and setting the expectations. Maybe a good detailed write up from the mothership is in order to cover all the questions asked and clarifying misunderstandings.
I navigate route as a track and have had situations where my next way point is North of me, so I should turn left at the intersection, but the Nav sends me to the Right (South) just to do a U-turn a mile down the road (at the SHAPING POINT I MISSED) and then head North to the next way point. That is wrong no matter how you look at it. A Shaping Point should not be forced so hard, right?
Of course I can long press the next way point and get around the issue, or skip the one I missed, but should I have to do that?
Using Navigation should make my life easier, not to be second guessing every instruction it gives me to see if it still makes sense.
Agree / DIsagree?
Thank you!Positive emotions are worth every penny ;)
-
@Con-Hennekens said:
Since MRA is a scenic navigation app, it tries to have you drive as much of the preplanned route as possible and only skipps parts of it after multiple redirections.This is inherently wrong. Back on track, is back on track and no sending back to missed shapingpoints. This is very confusing for users.
You are deviating and you're guided back to the track/route. When you're near the route you see the blue routeline on the crossing ahead but it goes in both directions (left and right). The navigation tells you to go right. But why is the blue routeline also going left?
But okay, I turn right and after a mile I reached a shappingpoint. Then the navigation tells me to turn around and go back. So taking the left direction was the right one after all. What was the point to send me back to that point?
Did i miss something, besides a shapping point?
A must see?A basic principle of a shapping point it shapes the route nothing more and because of that it is allowed to be missed. The navigation should use this principle and not sending me back to a missed shapping point.
@M.-Schrijver I completely agree with you... we're talking about the same issue repeatedly in several different posts on this forum, and they all boil down to the same question from users... why does it redirect to previous points that are just passing through (not mandatory stops)...?
(As you mentioned, hopefully these things will be fixed in the next update)... it's essential that a navigation system takes you forward on your route as a general rule... and only as an exception should you select to be taken to a previous point on the route you've planned...
-
I think at this point there is still no clarity in understanding the process and setting the expectations. Maybe a good detailed write up from the mothership is in order to cover all the questions asked and clarifying misunderstandings.
I navigate route as a track and have had situations where my next way point is North of me, so I should turn left at the intersection, but the Nav sends me to the Right (South) just to do a U-turn a mile down the road (at the SHAPING POINT I MISSED) and then head North to the next way point. That is wrong no matter how you look at it. A Shaping Point should not be forced so hard, right?
Of course I can long press the next way point and get around the issue, or skip the one I missed, but should I have to do that?
Using Navigation should make my life easier, not to be second guessing every instruction it gives me to see if it still makes sense.
Agree / DIsagree?
Thank you!@Lenny-O I completely agree with what you're saying... it's not normal to be using a browser and constantly be asked... (should I zoom out and press skip points) or wait?? I'm sorry, that solution could be much better
-
@M.-Schrijver, we are not starting that discussion again.
@Con-Hennekens When several users in different posts keep bringing up this discussion again, it's for a reason... it's not just a coincidence... perhaps there are things that can be improved...
-
These discussions are a valuable tool for the development crew to get information.
All in all the product is the BEST on the market hands down, but we still need to appreciate the fact that it is a living and developing product, unlike most others who produce it and never improve it. There will be growing pains and they will eventually get resolved. Corjan an the whole crew are working very hard on the next release, which will be BIG! And, of course, priorities, priorities, priorities.
Coming from 40 years of IT back office programming servicing Wall Street I can totally relate. So, yes, some issues are frustrating at times, but let's all keep the positive attitude and feed constructive criticism down the pipe!
Ride on and smile inside your helmets, folks! -
I think the same as you... that we, the end users, can use this forum to give suggestions and contributions so that they can continue improving the best navigation app. With what we've discussed about starting the route forward here and in other posts, plus what other people on the forum have suggested for improvements in how speed camera notifications are handled, I would honestly be satisfied...
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
-
3523.9k
-
018298
-
1292.6k
-
18492.7k
-
1303.0k
-
113259
-
112261
-
0436
