Automatically skip waypoint
-
Thank you.
I would normally use far fewer waypoints. I only filled it with more points (using Gold’s ‘Expand’ feature) as I read on the forum, the advice to expand the number of waypoints to something like one every 5 km. I did it as any experiment, as much as anything else.
Unlike a complex route on conventional or smaller roads, where It would be easy (either accidentally or on purpose) to miss a waypoint, I would have thought it was very difficult or even impossible, to miss a waypoint on a motorway. I am sure (or I am as sure as I can be) that I went through the waypoints, but for some reason, the app thought I hadn’t and the automatic skip function didn’t seem to work.
Like you, I am at a loss to understand why the automatic skip function didn’t work. Seemingly, nobody has an answer.
PS I’d be interested if you could identify for me please, which waypoints you spotted that are off the route.
@Richard-18 said in Automatically skip waypoint:
PS I’d be interested if you could identify for me please, which waypoints you spotted that are off the route.
Nr's: 2, 20, 38 and 45. As I said before, I can't imagine that these points really should give a problem. For myself, I place them spot on the black line as you did with the others.
-
@Richard-18 said in Automatically skip waypoint:
PS I’d be interested if you could identify for me please, which waypoints you spotted that are off the route.
Nr's: 2, 20, 38 and 45. As I said before, I can't imagine that these points really should give a problem. For myself, I place them spot on the black line as you did with the others.
Thank you, Rob
Whilst those were not points that caused me a problem, I agree that their proximity to the black route line should not cause a problem. In a way it’s no different to being on a four lane motorway in lane four, when the black line happens to be along lane one.
Even if it were the problem, surely the app should still automatically skip the ‘missed’ way point and not recalculate to take you back?
-
Thank you, Rob
Whilst those were not points that caused me a problem, I agree that their proximity to the black route line should not cause a problem. In a way it’s no different to being on a four lane motorway in lane four, when the black line happens to be along lane one.
Even if it were the problem, surely the app should still automatically skip the ‘missed’ way point and not recalculate to take you back?
@Richard-18 Agreed.
-
@Richard-18, check this thread from here, to gain insight on how auto-skipping works:
https://forum.myrouteapp.com/post/25536 -
@Richard-18, check this thread from here, to gain insight on how auto-skipping works:
https://forum.myrouteapp.com/post/25536Thank you, Con.
I am not sure that driving along a simple motorway, as opposed to a relatively complex non-motorway route, matches the example in the link.
As I explained, I am sure that:
A. The waypoints were placed accurately on the motorway carriageway. This has been confirmed independently.
B. As I did not leave the motorway, I must have gone through the waypoints, surely.
Why then:
-
Did the app think that I had missed the motorway waypoints?
-
Did the app then recalculate, to take me off at the next junction, send me back down the other carriage way, to the junction behind me and then come back up the carriageway, to pass through the waypoints again? This happened more than once.
-
Didn’t the app automatically skip the waypoints it thought I had missed?
If someone can give me a simple answer to these three questions, that would be great.
-
-
Thank you, Con.
I am not sure that driving along a simple motorway, as opposed to a relatively complex non-motorway route, matches the example in the link.
As I explained, I am sure that:
A. The waypoints were placed accurately on the motorway carriageway. This has been confirmed independently.
B. As I did not leave the motorway, I must have gone through the waypoints, surely.
Why then:
-
Did the app think that I had missed the motorway waypoints?
-
Did the app then recalculate, to take me off at the next junction, send me back down the other carriage way, to the junction behind me and then come back up the carriageway, to pass through the waypoints again? This happened more than once.
-
Didn’t the app automatically skip the waypoints it thought I had missed?
If someone can give me a simple answer to these three questions, that would be great.
I guess nobody can?
-
-
I guess nobody can?
@Richard-18 Sorry for the delay.
- Missing waypoints can occur if GPS signal wasn't available or inaccurate for a longer period while approaching the waypoint.
- Skipping waypoints automatically is only triggered at the second (or more) deviation. Then the first next nearest waypoint is chosen but that can very well be the waypoint that's behind you. If you seem to continuously ignore it, the app will skip it anyway after 6 recalculations. On highways it takes quite a long time before you can turn around (which you ignore) and thus before a recalculation is triggered. It might indeed then be a good suggestion to alter the algorithm to be more aggressive in skipping waypoints on the highway.
- See above
Hope this helps!
-
Also see this post https://forum.myrouteapp.com/post/25536
Together with my explanation below. -
@Richard-18 Sorry for the delay.
- Missing waypoints can occur if GPS signal wasn't available or inaccurate for a longer period while approaching the waypoint.
- Skipping waypoints automatically is only triggered at the second (or more) deviation. Then the first next nearest waypoint is chosen but that can very well be the waypoint that's behind you. If you seem to continuously ignore it, the app will skip it anyway after 6 recalculations. On highways it takes quite a long time before you can turn around (which you ignore) and thus before a recalculation is triggered. It might indeed then be a good suggestion to alter the algorithm to be more aggressive in skipping waypoints on the highway.
- See above
Hope this helps!
@Corjan-Meijerink said in Automatically skip waypoint:
On highways it takes quite a long time before you can turn around (which you ignore) and thus before a recalculation is triggered. It might indeed then be a good suggestion to alter the algorithm to be more aggressive in skipping waypoints on the highway.
This is exactly what I sometime earlier mentioned regarding the old nav app's algorithm being triggered by ignoring instructions on long stretches of road, instead of actual distance from the previous and to the next waypoint :). You were able to word it better haha :).
-
@Richard-18 Sorry for the delay.
- Missing waypoints can occur if GPS signal wasn't available or inaccurate for a longer period while approaching the waypoint.
- Skipping waypoints automatically is only triggered at the second (or more) deviation. Then the first next nearest waypoint is chosen but that can very well be the waypoint that's behind you. If you seem to continuously ignore it, the app will skip it anyway after 6 recalculations. On highways it takes quite a long time before you can turn around (which you ignore) and thus before a recalculation is triggered. It might indeed then be a good suggestion to alter the algorithm to be more aggressive in skipping waypoints on the highway.
- See above
Hope this helps!
Corjan, many thanks. I now understand it.
I agree that an alteration to a more aggressive skipping of waypoints on the highway would be beneficial.
I had the advantage as I was in a car, riding as a passenger. I was therefore able to watch the display on the phone, whilst the car drove up the motorway. I knew that it would make no sense to leave the motorway, drive back down the other carriage way and rejoin. I just couldn’t understand why the app would tell me to. As I was a passenger in a car, it was easy to ignore the app’s instructions.
On a motorbike, on unfamiliar roads (even a motorway) it might not be so easy, especially if the user of the app was following the instructions blindly. That is why I agree with you, about making the algorithm more aggressive on highways would be a good idea.
Your explanation answers my question. Thank you.
Richard