New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Router confusion due to area sharing border with highway #640
Comments
Hmm, apparently the routing via this "area" is profile-dependent. With the |
Ja, known problem that BRouter cannot handle "2-node-loops" I don't remember the exact reason for this technical constraints. But I remember that I spent some effort to mostly mitigate this, if I can resolve 2-node-loops by "promoting" a transfer-node to a network-node. See the method "checkDuplicateTargets" in https://github.com/abrensch/brouter/blob/master/brouter-map-creator/src/main/java/btools/mapcreator/OsmNodeP.java But in this case the 2-node loops do not have any transfer-nodes to promote. So just bad luck here... |
See https://bikerouter.de/#map=19/51.21989/12.52168/osm-mapnik-german_style,Waymarked_Trails-Cycling&lonlats=12.522542,51.219508;12.521635,51.219685&profile=shortest
I was surprised that BRouter reports this short bit of road as a
highway=service
with unknown surface and smoothness. The reason seems to be that there is anarea=yes
tagged as ahighway=service
using thehighway=tertiary
as its southern border:IMHO BRouter should try to ignore this area and keep the route on the continuous
highway=tertiary
.The text was updated successfully, but these errors were encountered: