In the route:
https://cycle.travel/map/journey/332594
between viapoints 3 and 4 is a path, but is not on OSM. For some unclear reason cycle.travel makes a detour here, partly on a path, partly through the forest.
Become a supporter
cycle.travel now has Ordnance Survey maps
Plan multi-day adventures easily
Thanks to Swaledale Outdoor Club!
We’re now in Australia and New Zealand too
Stick to tarmac with our new routing option
cycle.travel expands to Scandinavia and Eastern Europe
Smart Turns – new on cycle.travel's route-planner
In the route:
https://cycle.travel/map/journey/332594
between viapoints 3 and 4 is a path, but is not on OSM. For some unclear reason cycle.travel makes a detour here, partly on a path, partly through the forest.
Log in with your cycle.travel account:
Password |
Or simply use your account on:
Comments
It’s a current limitation of the straight-line feature – it generally doesn’t start from the exact via point, but the nearest junction (e.g. with another path). It’s something I’d like to improve at some point, but it has always been the case – it hasn’t changed.
I remember using it at on not mapped bridges. That's indeed a simple task.
Thanks for the very fast answer.
For now, I have to live with it.
Peter
It’s a limitation deep in the bowels of the routing engine. It will be fixable but I haven’t worked out how yet!
Another strange result: cycle.travel/map/journey/369810
Notice unexpected direct line connection between via 1 and 2.