The major June update and a follow-up OSM data-only update (with a hotfix for the iOS app hanging) were successfully published and are available in all app stor…
That’s good advice. I updated the route in OSM and it now recommends a better path, but still not what I’d consider the safest/still not what Strava recommends. It seems like it prefers shorter distances with painted bike lanes over having a protected bike lane at all points of the journey. It’d be a neat option – prefer protected lanes even at expense of more distance.
@something_random_tho The pathfinding algorithm is in the client app (like Organic Maps) and the data are in openstreetmap. Different apps can find different paths and there is not much we can do about it, because changing the pathfinding algorithm could break it for many other places. That’s why I would rather modify the data, such as marking roads unsuitable for bikes, or making sure the nodes are properly connected, adding speed limits, road surface types… nudge the algo into the right path
That’s good advice. I updated the route in OSM and it now recommends a better path, but still not what I’d consider the safest/still not what Strava recommends. It seems like it prefers shorter distances with painted bike lanes over having a protected bike lane at all points of the journey. It’d be a neat option – prefer protected lanes even at expense of more distance.
@something_random_tho The pathfinding algorithm is in the client app (like Organic Maps) and the data are in openstreetmap. Different apps can find different paths and there is not much we can do about it, because changing the pathfinding algorithm could break it for many other places. That’s why I would rather modify the data, such as marking roads unsuitable for bikes, or making sure the nodes are properly connected, adding speed limits, road surface types… nudge the algo into the right path