Skipping future waypoints

[RetiredWingMan]

I have been using MRA for several years now and the Navigation Next app since its release. I use the app for routes several times a week normally 300 to 500 Kms. In general the app works entirely as expected with te occasional glitch. The other day I started out and deviated from the planned route early due to traffic. The app recalculated a couple of times and then it skipped a future waypoint. I find this strange because it was still on the planned route and had not been bypassed. Why should it be skipped?

Once when stopped and I had stopped Navigation, when I restarted the route restarted from WP 1. Once I noticed the error I simply displayed the route and restarted from the next WP. This may have been caused by something I did.

I am very happy with MyRoute-app and MyRouteApp.com. looking forward to a revamp of the web site. GREAT WORK!

[Brian McG]

Hi @RetiredWingMan
@Con-Hennekens can probably explain this better & will correct my errors

my understanding is that if you deviate from the route, MRA will attempt to get you back on your route by recalculating a path back to your route
if you do get back on the original route all is good & you can continue on your merry way

the issue you are seeing occurs when you fail to get back on the original route
I believe the auto Skip point function is activated after 3 recalculation attempts have failed or are ignored
i.e. your not back on the original route after MRA has tried to get you there by 3 recalculations,
MRA will then Skip a point & recalculate to the next point

If you are still off route & it continues to keep doing recalculations it also starts Skipping further future waypoints
stay off route & more & more future shaping waypoints are Skipped, it wont skip a Via point

IMO it is a very crude & clunky method for handling deviations from the route but it is what it is

[RetiredWingMan]

I understand what your saying but I don't think it should skip a future waypoint that is on the recalculated route. It makes no sense to skip it.

[Rainer Treichel]

Workaround:
Skip waypoints OFF
But you have to skip skipped waypoints manually.
RT

[Brian McG]

@RetiredWingMan I am agreeing with you
On other threads it has been suggested that instead of this crude & clunky skip method they adopt a scheme similar to the TomTom where after a deviation instead of trying to route back to a waypoint, it routes back to the closest point on the original path
Only after your back on the original path then worry about where you are in relation to waypoints & implement a skip for those that have been passed

This TomTom re-routing requires a more complex algorithm to calculate back to the path compared to just routing to the next known waypoint (plus tomtom has the advantage that it is also navigating a track so has a lot more points to choose from)
It appears to me MRA have opted for the simplest option of routing to the next waypoint instead of the path & the consequence of this is they have to implement this clunky skip routine which we all occasional see as a pain

[Marinus van Deudekom]

It Sometimes happens when you diviate from a planned route that in the process of recalculating the route some future shapingpoints are skipped, even when they’re on the planned route. Don’t worry about that MRA Will guide you past those shapingpoints. Turing Off recalculating is not a good idea as far as I’m concerned because you would have to skipp points manualy.

[Con Hennekens]

@Brian-McG, You put a lot of trust in me... Actually I don't think you are that far off with your explanation.

@RetiredWingMan said in Skipping future waypoints:

The app recalculated a couple of times and then it skipped a future waypoint. I find this strange because it was still on the planned route and had not been bypassed. Why should it be skipped?

I do not find that strange at all.. If multiple recalculations need to be made, it is not that far fetched to conclude that the next waypoint cannot be reached. Therefore it gets skipped. That's what auto-skip is for, isn't it?

Once when stopped and I had stopped Navigation, when I restarted the route restarted from WP 1. Once I noticed the error I simply displayed the route and restarted from the next WP.

This depends... If you stop a route, and use the navigate button to get it started again, it should start where you left off. But in case you go back in the app and restart through the routes menu, it will restart from WP1 or from the closest point, according to the slider position in that window.

I don't think it should skip a future waypoint that is on the recalculated route.

If a waypoints is not skipped, it will always be on the recalculated route. But I see your point. If the app decides to skip WP10, calculates to WP11 and still hits WP10, it could as well decide to not skip to 11. I am not sure if there is a detection mechanism for this in the HERE platform, but it is interesting.

@Brian-McG said in Skipping future waypoints:

On other threads it has been suggested that instead of this crude & clunky skip method they adopt a scheme similar to the TomTom where after a deviation instead of trying to route back to a waypoint, it routes back to the closest point on the original path

Well that's because TT works with tracks, and the MRA app works quite the same if you enable the "Navigate routes as tracks" feature.