Routing issue between Freiburg and Hinterzarten (Germany)
-
B31 seems to be treated as one-way road, when you want to drive eastwards. E.g start at 47.919423, 8.061918 and navigate to a point a bit eastwards on the B31. You will be sent back and routed all around via L128, B500. Routing westwards works fine.
-
13 Comments sorted by
-
Btw. map version germany osm 44-201408250. However the previous version had the same issue.
-
Can you be more specific about the endpoint?
When I create a route from the mentioned coordinate towards the B500 it works fine.
I have the same map dates.
edit: There are quite some turn restrictions on that road with regard to ramps and exits and parking places. I don't want to check them all to see which one might be wrong.
-
The endpoint does not matter actually. Just try to navigate the B31 from west to east, e.g. from Freiburg -> Titisee (and one should use the B31 for this route).
-
I've narrowed it down, it's probably the red part of the B31 in this region. Try to navigate from 47.923242, 8.041735 to 47.919417, 8.061862.
-
This issue should be resolved.
Refere to https://www.openstreetmap.org/changeset/24764672.
In cases like this you can create a note directly on openstreetmap.org.
-
Actually it is this split in the road: http://www.openstreetmap.org/#map=19/47.92213/8.05067
and it has to do with the turn restrictions for the change:lanes. It is not the "opening" of the split but the "closing" of the split.
It really is an error in the OSM data. Other nav apps calculate the same route around it.
The change:lanes and change:lanes:forward and change:lanes:backwards setting is something I have never used myself. I have to examine it first.
If someone else knows the solution please adapt it.
-
Thanks rab. Now I understand. It was already corrected. That's why I didn't see the error.
I should have checked the history.
-
Right. I'll recheck after the next map update.
-
I checked restriction of one node:and it looks ok,It was added long time ago:but routing goes wrong:For me, there may be problem not only with OSM data.
-
It is an OSM error and it has been resolved some 20 days ago. This is AFTER the last navigator map creation.
I also checked with OsmAnd, first with the August map and it has the same issue. The new OsmAnd map was released on 2 September and that one did it correct.
The OSRM project uses new map data as well (regenerated every 2-3 days or so) and does it also correct. See http://osrm.at/9kJ
I have full confidence that Navigator will do it correct as well once the new map has been created.
-
If you are interested in resolving such kind of errors, then try this links
Based on live data - you can customize this page by clicking on the gear icon. This page is also very usefull for checking your own edits.
http://map.comlu.com/
~weekly updated, select your region - uncheck all except "geometry glitches" and "restrictions"
http://keepright.ipax.at/
There is constantly a lot of work to do
-
keepright is weekly updated when it comes to data, but the scripts haven't been updated for some time and contain errors (at least so I'm told by a few insiders).
Better use OSM Inspector: http://tools.geofabrik.de/osmi/
-
OSM Inspector has no routines for turn restrictions.
For unconnected roads its ok. It is always your decision, if an error report is correct, and the data needs to be fixed.
Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Categories
- All Discussions3,246
- Feature Requests1,264
- Bugs555
- General376
- Navigator FREE1,029
- Vehicle Tracking5
- Navigator 1017
In this Discussion
- b3nmore September 2014
- hvdwolf September 2014
- PrzemekSupak September 2014
- rab September 2014