App: Recalculate route in case of reverse direction

[devemux86]

Provide an option to recalculate route in case of reverse direction.

Currently this is enabled, comparing GPS and route direction (within ±75° range).
GPS direction is examined when there is speed > 10 km/h.

However that can lead to problems, because of route geometry and GPS quality.

[linux-user]

What do you mean with “provide an option”?
In my experience recalculation is triggered if you ride the route in reverse direction.

What is not always working to users expectation, is the recalculated route.

Navigation announcement incorrect when driving the wrong way

[image] I can confirm the described behavior: If you drive along the red arrow, than a rerouting would happen. After new route is calculated, the announcement would be: “In 100m turn right”. But this announcement only fits, if you drive in the green direction. If you continue driving in the red direction then another recalculation happens: Then the resulting announcement would be: “In 200m turn right”. And so on, until eventually a new route towards the red direction would be found.

[devemux86]

@linux-user

What do you mean with “provide an option”?

Make that optional as it depends on route geometry and GPS sensor,
so it can have a lot of false positives…

@linux-user

What is not always working to users expectation, is the recalculated route.

The latest Pro version no longer announces voice instructions immediately after rerouting.

The route quality depends on the routing service and we can discuss it better elsewhere.

[linux-user]

I think, such an option is not intuitive for the user.
If you would ask me: “do you want a recalculation if you ride the route in reverse direction?”
I would intuitively say “yes I want a recalculation”.

If the user wants to avoid unintended recalculations, the intuitive way is to deactivate automatic recalculation.
Any extra option that basically has the same intention (avoid unwanted recalculations) is IMHO superfluous.

[devemux86]

The settings exist for those willing to change them.
Most users can stay with the sane default settings.

Nobody ever asked if “reverse direction” is even reliable.
Its calculation can never be, so an option could be useful.

If it turns out to be wrong, it can be changed again.
The app is not implemented in stone…

[rumbrummer]

Perhaps it would be useful to change the title to “App: Recalculate route in case of riding / driving on route in reverse direction” (or similar).
But I might be the only one who misunderstood in the 1st moment: I thought it concerned the function “Long tap on route ¦ reverse route” .
(Of course meanwhile I understood - better late than never )

[devemux86]

@devemux86

Currently this is enabled, comparing GPS and route direction (within ±75° range).
GPS direction is examined when there is speed > 10 km/h.

Additionally, maybe the current default values need improvements?

[0709]

Does this mean the auto recalculate trigger moment? As it seems current is fine.

@linux-user

What is not always working to users expectation, is the recalculated route.

Many identical recalculate msg’s are annoying before a real alternative comes up.
(Speed up an alternative calculation by “manually” blocking the reversed trajectory)
Reject an alternative by continuing to drive and than hope the ‘bleating’ ever stops.

If you don’t want this annoying actual behaviour next is recommended.

@linux-user

to avoid unintended recalculations, the intuitive way is to deactivate automatic recalculation.

[devemux86]

Available for testing in Kurviger 2.0.11 (Beta).

[devemux86]

Implemented in Kurviger 2.0.14.