Another day MyRoute-app screwed up My Route
-
@Marinus-van-Deudekom I select the route and then click Navigate.
@Ton-Machielsen and if you selecte navigate Do You see the hand sign (viapoint) nr 1 on your screen's right top
Honda Goldwing GL1500,
Honda Silverwing GL 650
DMD2 T865X 8 inch Android tablet using MRA next for navigation
Garmin XT (almost in the cupboard)
Samsung S20FE mounted on a Quadlock and using Android Auto in my car -
@Ton-Machielsen and if you selecte navigate Do You see the hand sign (viapoint) nr 1 on your screen's right top
@Marinus-van-Deudekom If I click on navigate your route I'm beeing directed to wapoint nr 4, witch is the clossest waypoint from the Netherlands. Therefore trying to let you see that navigating automatic chioses the nearest waypoint on the route
-
@Ton-Machielsen and if you selecte navigate Do You see the hand sign (viapoint) nr 1 on your screen's right top
-
@Ton-Machielsen Looking at your route itself raises a lot of issues. Only waypoint 14 and 17 are ON the route. The rest is of or even way of. That's a chance to get your route to get messed up.
Are You navigation with the Next app of are you using a dedicated device.
If you're navigating with the next app witch settings are you using. Did you select start navigating from the nearest waypoint. If you are in fact linvibng near waypoint 18 and you have that setting active it's by design that youy are routed home, since that's the nearest waypoint.
Add some screeshots of your settings@Marinus-van-Deudekom
Something to add to your comment.When waypoints are way off route/road and you're riding a route (not a track). How can MRA Navigation (or other navigation) hit those waypoints when they are not on the road or very close to the road.
Those waypoints causes recalculations just because the waypoints are too far off-road.(I use MRA Next only on Android Auto. Every comment, suggestion, etc will be based on my usage with Android Auto)
-
@Ton-Machielsen there you have it. The app is trying to get you to the nearest waypoint, that would be nr 18. Since you know where waypoint 1 is, you've driving towards that waypoint nr 1 and meanwhile the app tries to get you to go to waypoint 18.
The fact that your waypoints are not ON the route is not good but the aopp will disregard those of route waypoints and try to navigate as close as possible to thoes waypoints. Your problems lies in the fact that you didn't not selct waypoint 1 -
@Marinus-van-Deudekom
Something to add to your comment.When waypoints are way off route/road and you're riding a route (not a track). How can MRA Navigation (or other navigation) hit those waypoints when they are not on the road or very close to the road.
Those waypoints causes recalculations just because the waypoints are too far off-road.@M-Schrijver Understand. That’s why I am suggesting a radius for the waypoint hits. If you pass the waypoint within that distance the waypoint is considered as hit.
-
@Ton-Machielsen
Ahh cause found.
You've select "start at nearest waypoint" that is Waypoint 18 in your case. Unselect this option and try again.(I use MRA Next only on Android Auto. Every comment, suggestion, etc will be based on my usage with Android Auto)
-
@M-Schrijver Understand. That’s why I am suggesting a radius for the waypoint hits. If you pass the waypoint within that distance the waypoint is considered as hit.
@Ton-Machielsen when navigating with the nex app is will go OK. If you would use such a route in lets say an Garmin XT, you would be in great trouble.
That's why we have and use MRA next -
@M-Schrijver Understand. That’s why I am suggesting a radius for the waypoint hits. If you pass the waypoint within that distance the waypoint is considered as hit.
@Ton-Machielsen
There is already a radius. But this radius is limited for a reason. Point 7, 11, 12 and 16 on route shows why. It is normal practice that you do your best to place the waypoints on the road. -
@Ton-Machielsen
Ahh cause found.
You've select "start at nearest waypoint" that is Waypoint 18 in your case. Unselect this option and try again.This post is deleted! -
@Ton-Machielsen
Ahh cause found.
You've select "start at nearest waypoint" that is Waypoint 18 in your case. Unselect this option and try again.@M-Schrijver Where can I find this setting?
-
It is the first option below de "start" button
-
Ha! Never seen that menu before!! Thanks!
-
Any idea why I don’t get the waypoint hand and Skip Waypoint icon on the CarPlay? (see https://forum.myrouteapp.com/post/61333)
Remember I am on a bike. I have the phone in my pocket and am navigating through the CarPlay device.
-
Any idea why I don’t get the waypoint hand and Skip Waypoint icon on the CarPlay? (see https://forum.myrouteapp.com/post/61333)
Remember I am on a bike. I have the phone in my pocket and am navigating through the CarPlay device.
@Ton-Machielsen Due to restrictions by Apple and Google the viapoint sign is NOT on Androis Auto and Carplay
Honda Goldwing GL1500,
Honda Silverwing GL 650
DMD2 T865X 8 inch Android tablet using MRA next for navigation
Garmin XT (almost in the cupboard)
Samsung S20FE mounted on a Quadlock and using Android Auto in my car -
@Marinus-van-Deudekom
Something to add to your comment.When waypoints are way off route/road and you're riding a route (not a track). How can MRA Navigation (or other navigation) hit those waypoints when they are not on the road or very close to the road.
Those waypoints causes recalculations just because the waypoints are too far off-road.@M-Schrijver Is the “Navigate routes as tracks” option my solution?
-
@M-Schrijver Understand. That’s why I am suggesting a radius for the waypoint hits. If you pass the waypoint within that distance the waypoint is considered as hit.
@Ton-Machielsen said in Another day MyRoute-app screwed up My Route:
@M-Schrijver Understand. That’s why I am suggesting a radius for the waypoint hits. If you pass the waypoint within that distance the waypoint is considered as hit.
That is a sensible suggestion - agreed, but I suspect the radius must change depending on the circumstances. Roads that are close together will require a smaller radius to be drawn by MRA, so basically, the radius info would just be telling you what you know you need to do anyway - i.e. drop the waypoints 'accurately'!
-
@M-Schrijver Is the “Navigate routes as tracks” option my solution?
@Ton-Machielsen
No. If you want route to be riden reliable. The route itself should be made reliable. A navigation cannot fix a badly made route.(I use MRA Next only on Android Auto. Every comment, suggestion, etc will be based on my usage with Android Auto)
-
@M-Schrijver Where can I find this setting?
@Ton-Machielsen, I guess this thread gives some "food for thought"
Great thread, that shows the power of an "old-fashioned" forum!
-
@Ton-Machielsen
No. If you want route to be riden reliable. The route itself should be made reliable. A navigation cannot fix a badly made route.@M-Schrijver said in Another day MyRoute-app screwed up My Route:
@Ton-Machielsen
No. If you want route to be riden reliable. The route itself should be made reliable. A navigation cannot fix a badly made route.Ok, i'll bite. Define "a badly made route".
My take is that if the app shows the route i want to ride, the app should follow that route.
What's your take?
