I understand you use third party services to handle your maps and routing, I just wanted to highlight Strava frequently suggests routes that are dangerous. Strava has the capability to flag segments as dangerous, but not if Strava built routes are.
Here is the route strava suggests I take from Great Cross Hall Street to Hunter Street (Liverpool UK)
This is an illegal turn turning through a busy intersection on a major A road through the city. There is ample bicycle tracks around this area, however Strava routes across 4 lanes of traffic with each lane heading in a different direction.
I understand the map makes it look semi-possible to cross, but due to the lights and the (unsigned) right turn only in the middle, it is not possible.
Here is how google routes it:
and bing (as a car)
Just trying to make our city a little safer. I would appreciate if you could flag this with your map/route providers and consider in-app ways of flagging this information.
The static maps in the Strava feed and on the activity details page are provided by Mapbox, with the data for roads, places, parks, points of interest, and trails sourced from OpenStreetMap.
You can learn more about the Maps used on Strava, and how to make contributions, within our support article here: https://support.strava.com/hc/en-us/articles/216917717-About-Strava-Maps
If you believe there is data that could benefit from an update, we encourage you to visit OpenStreetMap to share your insights.
Hi Scout thank you for the reply.
The OSM is correct. However the OSRM pathfinding is not.
Here is OSRM pathfinding that strava seems to use
and here is the Bicycle(Valhalla), the legal and safe route on OSM
May I ask why Strava is using OSRM rather than Valhalla?