In most cases this is not a problem, as such a route proposal can be ignored, but perhaps it creates unnecessary confusion. Maybe it is possible to introduce some kind of filter that would eliminate such behaviour?
Ja, es ist besser. Soweit mich mein Browser nicht wieder ärgert liegt es bei beiden Stellen an der Option “Vermeide Hauptstraßen” sobald man diese ausschaltet wird der “Umweg” nicht mehr genommen.
Yeah, it’s better. As far as my browser doesn’t annoy me again, it is in both places at the option “Avoid main roads” as soon as you switch it off, the “detour” is no longer taken.
Truth. That’s the reason. But I will never turn off this option in my life because it gives a real fun of navigation with Kurviger!
So if the change of the algorithm would spoil the navigation in other locations - it’s safer not to change anything here. As they say with us: “Better is the enemy of good”
That’s your right. But: if there are start/finish or waypoints on main roads, the algorithm will leave the main road at the next opportunity - and that is its right!
Of course, the examples given are only a part of a longer route mapped by Kurviger (but with the same parameters as in the examples). I put these start/finish points here because Kurviger suggested crossing them.
Then it could helpful to see the “longer route” …
For my opinion the algorithm doesn’t use main roads, except you place a waypoint on it. And then this main road will be left as soon as possible.
I agree with it. Overall, I like the algorithm very much (except for the occasional unpaved road drive, which is partly the result of incomplete OSM data).
I drew attention to the problem of short detours because of motorcyclists driving only „by ear”. If it is possible to look at the screen, that’s not a problem.
I would be afraid of excluding the desired intersections. Too much to lose
Maybe something like „avoid the detour if you return to the same route in less than 100 meters”?
This also happens on regular turns, not only sharp turns.
There are quite a few discussions about this behavior in the forum here. The routing is already pretty tuned to avoid these. There is more to come in the future