A to B Routing incorrect behavior

[Peter Zehentreiter]

On Saturday, we noticed the following issue.

We searched for a destination in the app and were then presented with a choice of three different routes.

We selected a route and set off. At some point (we don’t know when), the app switched to one of the other routes without any notification.

When we realised this after a while, we drove manually in the direction of the white line of the route we had originally selected in order to get back to the chosen route.

When we reached the white line and wanted to continue along it, the app tried three times to deviate from the white line and use one of the other routes.

What did we do wrong??

[Marinus van Deudekom]

Is trafic information enabled. That could cause a detour

[Con Hennekens]

@Peter-Zehentreiter, in an AB route, the white line represents the originally calculated route, but is by no means leading. If you deviate from the the original route, new calculations can find a quicker or shorter route at that moment. The white line being shown clearly indicates a recalculation. That is never done without any notification, but it can be missed easily.

[Peter Zehentreiter]

@Marinus van Deudekom Yes, the traffic information was enabled, but as the name suggests – ‘information’ – to me that means it should provide updates on upcoming traffic incidents, not automatically choose a different route.

In any case, there were no traffic updates!"

@Con-Hennekens

@Con-Hennekens said in A to B Routing incorrect behavior:

in an AB route, the white line represents the originally calculated route,

I realise that... we did choose this route during the preliminary selection.

@Con-Hennekens said in A to B Routing incorrect behavior:

but is by no means leading.

Why shouldn’t this route be set as the default route? I’m specifically choosing this route because I want to take it.

@Con-Hennekens said in A to B Routing incorrect behavior:

The white line being shown clearly indicates a recalculation

I understand that, which is why we went back to the white line – because we wanted to stick to that route. The question is, why is the app doing this?

We did NOT deviate from the route; there were two of us driving with identical settings and following the same route (one iPhone, one Pixel 9), both devices had a good internet connection, and neither of us received a notification that we were leaving the originally selected route.

As I have already mentioned, we drove back to the route (the white line), and when we were back on the line, the app tried three times to steer us away from the white line using turn-by-turn directions (no traffic jams in sight, no alerts regarding traffic disruption). Only after these three attempts to divert us from the white route (which we ignored) did the route continue along the white line... There was no excessive traffic, no traffic jams, or any other restrictions visible all the way to our destination.

[Con Hennekens]

@Peter-Zehentreiter, The app does not recalculate without a cause. If you think you did not deviate, it might be a glitch in GPS reception for example. It changes the route because it thinks there is a quicker way, just like any normal A2B navigation unit. You could try "Navigate route as track", at least that will continue the track at your reentry point. But to be honest I am not sure if that works for A2B routes.

[Peter Zehentreiter]

@Con-Hennekens said in A to B Routing incorrect behavior:

It changes the route because it thinks there is a quicker way, just like any normal A2B navigation unit.

But then it doesn’t make sense to me to offer three different routes if the app then tries to choose the quickest route on its own whilst navigating.

Never mind, I now know it doesn’t work the way I’d imagined; in future, I’ll mark a few points along my chosen route, which will force the app to navigate more closely to the direction I’ve specified.

I don’t think driving the A-B route as a track is a good idea either.

[Corjan Meijerink]

Track navigation is not possible for AB routes.

Based on user feedback this is the behavior. We used to send you back exactly to the selected route but if you were driving away from it to another option you would be sent back the entire time until it really started to be weird. Users were even less happy with that

So yeah….this kinda makes sense unfortunately.
I’ll investigate a possible solution somewhere.