Open dabreegster opened 1 week ago
95982c2e4fe64e6369e8df21ab5a80be3839f86b started this. But there's more work to do to initially clean up the graph of possibly editable roads:
highway=footway
, like https://www.openstreetmap.org/way/400692851. Ideally we'd prune.highway=path
in a golf course, https://www.openstreetmap.org/way/909112247In case of use/interest, we remove irrelevant ways with the the get_cycling_network()
function early in the process.
"abandoned|bridleway|bus_guideway|byway|construction|corridor|disused|elevator|emergency|escalator|escap",
"|far|fixme|gallop|historic|motorway|no|planned|platform|proposed|raceway|rest|road|services|steps|track"
"mtb|discouraged|unknown|no"
It could be beneficial to align these and I think the function is imperfect, so any issues with the outputs let us know. You can see the results here: https://nptscot.github.io/#/clos/#11.15/55.939/-3.2132
Or ideas for improvement..
Thanks, I was referring to that filtering. It'll be something to iterate on. For NPW, we're not just trying to reason about existing infrastructure, but also let people quickly select roads to consider improvements. If we filter out too much, then somebody has to draw freehand. What if there's a very poor surface track
and someone's proposal is to pave it and make a proper rural shared use path?
What if there's a very poor surface
track
and someone's proposal is to pave it and make a proper rural shared use path?
Oh yes, so there are different filtering requirements for the 'currently cyclable network' data that osmactive gets and the 'potentially cyclable network after interventions' network.
Footways and things are currently included. Need to do the
graph
refactor to have a customizable mode, and use it here