poutnikl
commented
1 year ago You are right.
Hiking-beta is more than 6 years obsolete and I am not sure why bikerouter still uses that.
But hiking profile releases have still this flaw, even the current and develop profile templates (the hiking profiles are all generated by script from the template by modifying tweakable parameters)
https://github.com/poutnikl/Brouter-profiles/tree/master/HikeProfiles https://github.com/poutnikl/Hiking-Poutnik/blob/master/Hiking.brf https://github.com/poutnikl/Hiking-Poutnik/blob/develop/Hiking.brf
It is obvious I have originally got rid of the oneway logic, as its vehicle traffic context does not apply to pedestrians. I have not realized at the moment it still applies on some challenging mountain trails.
I will try to modify profile and post the fix here, as releasing new one will take some time.
It seems that the hike profile does not care about the oneway=yes tag, as for example this way https://www.openstreetmap.org/way/30081724
Thus this route https://bikerouter.de/#map=18/50.91083/14.20804/osm-mapnik-german_style&lonlats=14.206159,50.912244;14.207221,50.910982&profile=hiking-beta should not pass via the above cited way but further east via https://www.openstreetmap.org/way/34037960 like this https://bikerouter.de/#map=18/50.91083/14.20804/osm-mapnik-german_style&lonlats=14.206159,50.912244;14.208584,50.910931;14.207221,50.910982&profile=hiking-beta