Tags vehicle=no + bicycle:conditional=yes@… should trigger warning instead of failing to route in cycle profiles
hungerburg opened this issue · comments
Graphhopper should route along the waymarked route (or close) - https://graphhopper.com/maps/?point=47.169217%2C11.465069&point=47.174048%2C11.480668&point=47.176764%2C11.502712&profile=mtb&layer=TF+Cycle
Instead it routes around. Probably something similar to #2863 would give better results, i.e. a warning.
Tagging there looks correct: The more specific key overrides the less specific one. If anything is wrong with the tagging, it is that the detour is lacking the correct tagging.
PS: The dotted line in the end is fine, but the dotted line in the middle makes me ache, there is some steep terrain there:
Context: https://www.openstreetmap.org/way/1216602928#map=17/47.17239/11.47752
I think this is already solved with #2863 being merged.
Yes, this is a bug and was introduced with #2863. The problem is that opening up a road via conditional access is trickier because of oneway roads. Will have to think about how to properly fix this, because I also don't want to have conditional restrictions like it was before.
Should be fixed and will be deployed on GraphHopper Maps in ~2 days. Thanks for reporting @hungerburg !