Auto skipping in next version (6)

[Herman Veldhuizen]

It has come to my attention that the auto skipping is being addressed in the next version. I am interested in how this is going to work. Would it be possible to share a glimpse here?

[Rob Verhoeff]

@Herman-Veldhuizen Version 6 is currently being tested by the beta users. I think the algorithm has been improved significantly. I don’t really care about the logic behind it, as long as what happens makes sense!

[Lluis Arasanz]

I’m also interested in logic behind autoskipping feature. Can any one share logic of how it works?

Regards

[Herman Veldhuizen]

My hope is that the app gets a mode in which the route gets priority over points.

[M. Schrijver]

How i like that idea very much. I do not thing it will be the case.
On a active route in the navigation. Zoom in on a waypoint. You'll see kind of two routelines overlapping eachother.
What this tells me. A route is a chain of mulitple miniroutes. Where every waypoint is both start and endoint. As long as the deviation stays with in the same miniroute. MRA is flexibel doesn't do strange things overall. But when the deviation causes to interact with two (or more) of these miniroutes (skipping waypoints). Things starting to be complicated. To start a new (mini)route, you need to end the previous one first.
It looks like this the basic structure how the Here platform works.

[Herman Veldhuizen]

well i will wait and see. one day it will be fixed i hope. I am clearly not the only one asking for route priority over point priority. The current behaviour is a hybrid between point and route priority. As long as you follow the route exactly as planned then all is good. but if you deviate from the route you dont know if you should follow the instructions from the app or not. It would be good if the app had a setting where you can say whether you want point priority or route priority (or a hybrid like today but when it is easy to skip both forwards and backwards then the hybrid version is probably not needed anymore).

many new features coming apparently. All good but resources are not unlimited and my concern is that these new features will consume the time needed to fix issues in the core. I like MRA very much and I just need to be a bit more patient i guess.

[Corjan Meijerink]

@Herman-Veldhuizen this comment is about what version?

[Herman Veldhuizen]

I am not a alfa or beta tester. i am using the latest version on google play (5.2.2).

[Corjan Meijerink]

Clear! This has been completely redesigned and I am positive you will enjoy it better

[Herman Veldhuizen]

@Corjan-Meijerink Sounds very good. thanks for the good work.

[a white mouse on the motorbike]

I'm a Beta tester and I can confirm that I'm very positiv about the new auto skipping!
But for it's still Beta I can not say much more. You will see.

[Marc Vanacoleyen]

Now that v6 is available to everyone, I'm still curious to learn how the new logic for automatic waypoint skipping actually works.
Understanding avoids irrelevant questions.
Thanks in advance.

[Herman Veldhuizen]

me too.
i did some testing today and noticed the following:

-i dont get notified anylonger when I have reached a shaping point (the setting for waypoint notification is "All"). I only get notified that a waypoint is coming.

-the app recalculates a route sometines even when the setting for automatic recalculation is off. That happened also in previous versions but that seems to have a side effect. see my next observation.

-when you deliberately don't visit a shaping point then the app skips the point more often then before. Wether it skips a point seems to depend on whether the recalculate kicks in or not. If you rejoin the route before the recalculate kicks in the missed point is skipped. if the recalculate kicks in before you rejoin the route the missed point is not skipped.