@nicemicro@organicmaps that’s correct. I’m actually looking into how Valhalla does it on this case right now. Curiously the public FOSSGIS instance (what you see on the OSM website when you select pedestrian Valhalla routing) is a bit different from what our current APIs as well as the Valhalla master branch running locally compute. The public instance routes foot traffic on the major road which is absurd. The more correct routes cross the street and it MIGHT to minimize crossings.
@nicemicro@organicmaps for OSRM I’m less familiar with the internals but I’d expect somewhat similar logic.
This actually catches me at a very good time to pursue this rabbit trail since I’m in the process of submitting a new profile for Valhalla and in the process I built some debugging tools last week 😂 I’ll let you know if I find anything interesting.
@ianthetechie@organicmaps I at least would expect the use of crossings to be minimized with some type of expected time penalty on those, but I know nothing about routing engines, so idk.
@nicemicro@organicmaps funny enough, I live nearby and noticed similar issues with Valhalla-based routing a few months ago when working on Ferrostar (new FOSS mobile navigation SDK). I think Organic Maps uses OSRM, which means it’s a clear issue with the routing tags but I never got around to looking into it.
hi @organicmaps, I have mapped the sidewalks (with bike paths) around one of the largest avenues in Seoul, Songpa-daero in #openStreetMap
When I plan a cycle route along this road however, the app makes some weird decisions, like crossing from left to right side multiple times, sometimes not even on the crosswalks.
Did I use an improper tagging scheme? or did I create some edge case the app is not prepared for?