It seems the automatic routing takes road type into account and does not allow routing along roads that are not suitable for foot traffic (e.g. UK motorways). This makes automatic routing for 'closed road' running routes problematic. Although manual routing can be used as a work-around, this can cause problems with elevation data being calculated incorrectly (e.g. where the desired route crosses a river over a bridge).
Is it possible to add an option to enable the auto-routing engine to acknowledge the road as a route to follow, but to disregard the road classification?
The issue is clear in the example of this route I created for the Great North 10k in Newcastle upon Tyne:
https://www.strava.com/routes/3110090670538068632
The route crosses the River Tyne via the Tyne Bridge, but the profile suggests Strava is taking its elevation data from river level rather that road level over the bridge (the big sudden dip when the river crossing is reached).
The entire route has had to be manually routed, as Strava will not auto-route along the desired path - presumably because most of the outward leg is on road classified as UK motorway (i.e. no pedestrian access). If I could choose for the road classification to be ignored by the routing engine, this problem would presumably disappear.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.