this post was submitted on 25 Jun 2024
268 points (98.9% liked)
Open Source
31133 readers
507 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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