I do realise that this is a strange edge case, but due to a building collapse on Kirkgate in Leeds, a small section of the road has been closed to through vehicular traffic (but the pavement is still open). This allows cyclists to dismount for a short distance, walk across the pavement and then remount back on the main carriageway.
The issue I'm facing is that cycle.travel seems to think that the entire road is closed, and plans around walking for a significantly longer distance, which causes some long diversions. I don't know if this is due to the data in OSM, or how cycle.travel is interpreting it.
Long walk example - https://cycle.travel/map/journey/640701
Long diversion example - https://cycle.travel/map/journey/640703
The road closure shown on Google Street View - https://www.google.com/maps/@53.796024,-1.53798,3a,75y,242.47h,87.64t/data=!3m7!1e1!3m5!1sK229XWewpZACET19bQEoag!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fpanoid%3DK229XWewpZACET19bQEoag%26cb_client%3Dmaps_sv.tactile.gps%26w%3D203%26h%3D100%26yaw%3D315.32864%26pitch%3D0%26thumbfov%3D100!7i16384!8i8192?coh=205409&entry=ttu
Comments
This is an OSM issue, I think. The road from Wharf Street to New York Street has been marked wholly “under construction” with no provision for pedestrians. Ideally I guess the pavement would be mapped separately so that c.t could route along it!
Either that, or as I imagine that c.t takes into account walking length when calculating routes, would a significantly smaller construction zone help improve routing?