<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">On my last holiday I took a detour to re-check the Apsley Gorge track.<div><br></div><div>The asphalt path ends at a lookout <a href="https://www.openstreetmap.org/node/324186826">https://www.openstreetmap.org/node/324186826</a></div><div><br></div><div>The ‘controversial’ path is still present south of here - I followed it some of the way (about 350m), but didn’t follow it all the way to the end.</div><div><br></div><div>There is a sign just south of the lookout - Google Maps street view shows the sign (the small yellow object near the southern end of the safety rail!)</div><div><a href="https://maps.app.goo.gl/9mDecm2GKpXxM48k6">https://maps.app.goo.gl/9mDecm2GKpXxM48k6</a></div><div><br></div><div>On the left side of the sign, there’s a warning icon (exclamation mark), then “No safety rail”, another warning icon (man falling off edge of crumbling cliff), then “Unstable edges”</div><div><br></div><div>On the right side of the sign is the text “End of track, no safety rail beyond this point”</div><div><br></div><div>The sign is there to discourage walkers venturing further south, but it’s not technically a “do not enter” sign.</div><div><br></div><div>Does that help with what to do with this particular example?</div><div><br></div><div>Mark P.</div><div>
<br><div><blockquote type="cite"><div><div dir="ltr"><div class="gmail_quote"><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 3 Oct 2023 at 23:33, Mark Pulley <<a href="mailto:mrpulley@iinet.net.au">mrpulley@iinet.net.au</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>A brief summary of the options for this type of situation (not just this particular edit, but similar edits in the past and probably future):<div><br></div><div>1. Revert the change sets (in the absence of more information)</div><div>2. Partial revert, with a change in tags</div><div>3. Leave the deletion as it is.<div><div style="font-family: Helvetica; font-size: 12px;"><br></div><div style="font-family: Helvetica; font-size: 12px;">For this particular example, the results would be:</div><div style="font-family: Helvetica; font-size: 12px;">1. Full revert - way will be marked informal=yes, but without access tags</div><div style="font-family: Helvetica; font-size: 12px;">2. Partial revert - could add access=no, or alternatively abandoned:highway=* or disused:highway=*</div><div style="font-family: Helvetica; font-size: 12px;">3. No reversion</div></div></div></div></blockquote><div><br></div><div>I would opt for 2, leave the way in place, but with access=no, a lifecycle prefix on the highway tag like abandoned:highway=* or rehabilitated:highway=*.</div><div><br></div><div>If there is signage that says closed for rehabilitation, we should capture the closure reason somewhere, so OSM data consumers can present that reason for the closure to users, whether that be via rehabilitated:highway=* or something like, access:reason=rehabilitation.</div><div><br></div></div></div></div></div></div></blockquote></div><br></div></body></html>