In App-Routing-Error

[cepesko]

https://www.openstreetmap.org/#map=19/49.98531/9.15116

Routing should turn slight right into double lane shortpass. OSM Data seems to be ok, as other routers do it correctly. Best regards and thanks to developpers! Cepesko

Edit: Germany/Bavaria/standard_map 2017-01-01

[polarbearing]

I checked the OSM data including their history. While there were 2 edits in Jan 2017, however they did not affect routing, not affecting routing via the link, but the second edit will mask the routing error. So the loop is explicable with a turn restriction, it remains unclear why the link road is not used in the first place. The number of traffic lights is equal.

(Edit: made some fixes myself, again not affecting the routing / edit2: about masking)

[utack]

@polarbearing now turn restrictions are in places it seems

[polarbearing]

Those turn restrictions are wrong data, as turning is allowed on these junctions. No signposting restricting it.

The bad thing is that the restrictions were added an hour before midnight on Jan 31, that means they will be in the February OsmAnd extracts. Thus they will mask the routing error and make debugging it more difficult :-(

[utack]

yes mapillary makes it seem like you are allowed to do u turns here, they do not seem correct

[polarbearing]

I had commented the changeset already, https://www.openstreetmap.org/changeset/45698433 . Maybe the user intended to help with this error here, but it was counter-productive. Still I'd like to wait a day for a response before reverting.

[polarbearing]

The user has removed the misleading restrictions, however the bug should therefore been tested against the original 2017-Jan-01 map or a February map with OsmAnd Live applied.

[stephan75]

... maybe the online service http://extract.bbbike.org can provide daily (?) refreshed map extracts also in Osmand format ... for testing purposes on that street crossing.

[aceman444]

What is the assumed speed set in your routing.xml file for the primary and primary_link class of roads? Maybe it is faster in OsmAnd calculations to take the primary roads and make the loop.

Also, if you don't want to add a simple no_turn_left e.g. at node 2088253270 (as you say there is no such restriction), you could make a no_u_turn restriction with "from way 198732136, via way 470799544, to way 198732021" members so only disallow loops.

[cepesko]

Error gone with map Feb 1st