Ah, I was unfamiliar with the tag - I definitely should've double-checked that one. Thank you for the link and fixing it!

*Missing! Apologies for the typo in the changeset title.

Fair point, I'll reinstate the way segment with access=no. Thanks for the help!

It's a steel gate in a tall fence which is now permanently locked, so I am not sure on the best representation of ground truth. The paths within the site are already access=private so do you think access=no is a clear enough indication? It doesn't render any differently (I know we shouldn't tag for the renderer but it does impact usability)

Ah no worries! I was able to fix it, that's ok. Must have been an accident, my apologies. Yes, I've been here for a few years, love it!

Hello, why did you delete the parking aisle I added in the Civic Centre car park? This breaks pedestrian connectivity in Wotton, as there is a small cut-through from Bradley St to Gloucester St that was left disconnected. Thanks

Hello! Thanks for adding this footpath - it needs to be connected to the roads at either end too, that way navigation apps can see it and use it to give walking directions! I've edited it slightly to join the roads - it's very easy to do. Cheers!

Thanks Phil - you are correct, there is no signage explicitly outlawing pedestrian access, I just wanted to indicate that it's discouraged as this is a fast road with no pavements. I'll edit now to revert my mistake and use sidewalk=none instead. Thanks for the correction, I appreciate it!

Hello! Thanks for adding the footpath here! But since Green Lane has already been traced, re-drawing the footpath over the top is quite cluttered - it looks like two paths next to each other.
Luckily it's much easier to do this: if you click on the existing segments of Green Lane, you can change the "foot" tag to "designated". That means the existing alleyway is shown as a legally-recognised footpath. I went ahead and did this for you - hope that helps!

It's a motorway-style crash barrier between the road and the woods below, with no break - you'd have to step over it. There's a narrow, steep dirt path unsuitable for anything but foot traffic, but as the crash barrier suggests, there's no pavement on this side of the road - as soon as you hop it you're in a busy, fast traffic lane. In my opinion it's not a decent link at all and is very dangerous for pedestrians, especially compared to the proper path north of the road and under the bridge - but it's clearly a desire path shortcut in some local use however ill advised, so I am reluctant to delete the path from the map altogether. The barrier=fence should have access tags something like foot=discouraged, bicycle=no, wheelchair=no. Last night my cycle routing app tried to send me down there hence the update!

That sounds like a more accurate description, thanks! Will update now.