But you have to admit: it’s definitely more winding than the D23… 
@zaphod_42 Yes. Technically correct 
. But I selected “Fast & Curvy” setting.
What I could have ridden:
What Kurviger provided:
Ne, das ist Mist. Für 300m von der Hauptstraße runtergeführt werden ist indiskutabel. In diesem Beispiel könnte man noch diskutieren, aber Kurviger führt einen bei “schnell und kurvig” regelmäßig über Ausfahrten zurück zur Hauptstraße, das ist ein Albtraum, und somit als Einstellung unbrauchbar. Scroll mal in dem thread weiter hoch, da sind zahllose Beispiele wie du von der Hauptstraße runtergeführt wirst um gleich wieder auf die Hauptstraße zu kommen.
da bin ich bei dir , auch diese Touren durch das Industriegebiet oder einer 30er Wohnsiedlung 400m um 50m weiter wieder auf der “selben” Straße weiter zu fahren ist mehr als blöd.
Well - in purely mathematical terms, the detour is both: faster and curvier. Unlike the D23, the speed limit on it is 90 km/h the entire distance.
This is a overview route (using curvy settings) - this is a straight round with one roundabout (point 1) and then the second nera the end.
The error is related to route calculation on roundabouts - left picture is with “fastest” setting and the right one - “curvy”
When set to “fastest” - rout goes through roundabout and then suddenly reverse and goes back to the paraller street (Mrówcza in the first picutre). Similar situation is on the second roundabout (top picutre - curvy, bottom - fastest):
I have observed similar error also in other places. In fact sometimes “curvy” road i fastes that the “fastes” one, and on “curvy” setting I got the smaller number of effors.
The points used in the route callculation are:
It is easier for us, when you share the link to the route. Upper right menu > Share > Button Copy Link. Typing numbers from screenshot on mobile is hard.
Thanks.
To me it seems that in OSM it is allowed to turn at these points.
What do you think, turn allowed or not - or least unusual? Same for the other one? We could set a restriction in OSM-data, to disallow this.
Seems the time calculated in both cases is smaller though making stupid turns.
Your tour: kurv.gr-Link
First roundabout.
Just place the SP more towards destination, at least after the splitted road so it gets “more expensive” or impossible to turn (you may not reverse on oneways). kurv.gr-Link.
Second roundabout. This is a strange one. Faster with stupid turns? From road markings in satellite view it is definetely forbidden to turn. I see no obvious reason in OSM, why Kueviger should prefer this.
@boldtrn / before I change in OSM.
These are quite good examples of obviously unnecessary turns, nearly 180 degrees.
Same as some days ago from @Thoka, when turning on a crossing.
It would be great, if you have some minutes to check this. On these few meters the time can only differ in a few seconds or fractions. A turn of nearly 180 should be “more expensive” or how you call it.
Link with the route: https://kurv.gr/DbVnE
“What do you think, turn allowed or not - or least unusual? Same for the other one? We could set a restriction in OSM-data, to disallow this.” - I know these streets very well, and you cannot turn there (a sharp turn instead of using roundabout) like kurviger suggested - it is not allowed, there is a double solid line. Moreover, it also makes no sense, because it is much simpler to just use roundabout.
“Just place the SP more towards destination, at least after the splitted road so it gets “more expensive” or impossible to turn (you may not reverse on oneways).” - I did it on purpose just to show kurviger’s erratic behaviour. Normally I don’t place waypoints like this.