<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 19/07/2018 12:21, Peter Elderson wrote:<br>
<blockquote type="cite"
cite="mid:CAKf=P+vvf-BcSzQ7VXMtNff5s4uTBsNP7P6u-eAuFk2ms2bPpg@mail.gmail.com">
<div dir="ltr">All of those are survey goals. </div>
</blockquote>
<br>
A proposal like this comes along every few years & never really
gets off the ground. "Long hiking & cycling routes" by their
nature of being long are rarely traversed completely; people hop
on-off of them in short sections. So a "systematic survey" is highly
unlikely.<br>
<br>
Most of what's been listed here I would describe as every day
mapping. I'm unsure what benefit adding another tag, which will soon
be inaccurate, will bring.<br>
<br>
There are a few validation tools to keep an eye on the integrity of
relations:<br>
<a class="moz-txt-link-freetext" href="http://ra.osmsurround.org/">http://ra.osmsurround.org/</a><br>
<a class="moz-txt-link-freetext" href="https://osmlab.github.io/osm-deep-history/">https://osmlab.github.io/osm-deep-history/</a> <br>
<a class="moz-txt-link-freetext" href="http://overpass-turbo.eu/">http://overpass-turbo.eu/</a><br>
<br>
Can anyone recommend some others?<br>
<br>
Historic GPX traces remain relevant. Individually they are not that
accurate. Having a collection allows a mapper to iron out
inaccuracies & estimate a mean average route.<br>
<br>
If you want to register a path being physically non navigable, an
email to the authority responsible produces better results than
marking it in OSM.<br>
<br>
Cheers<br>
DaveF <br>
<br>
<br>
<blockquote type="cite"
cite="mid:CAKf=P+vvf-BcSzQ7VXMtNff5s4uTBsNP7P6u-eAuFk2ms2bPpg@mail.gmail.com">
<div dir="ltr">The result of the survey may be that the route
relation in OSM needs to be adapted to reflect the situation in
the field. That's what I meant by maintenance of the route
relation in OSM.
<div><br>
</div>
<div>The goal of the idea is to tag the date of the last reality
check. The best thing I have now is the date of the last edit,
which most of the time results from e.g. a mapper's action
(cut or remove) on a way that's part of the route relation.</div>
<div><br>
</div>
<div>I want to ensure that the route in the field and the route
relation stay in sync, and when they don't (which is a 100%
certainty) that you can tell at what point in time it did
match. </div>
<div><br>
</div>
<div>Information older than that date (e.g. gpx-tracks) can be
discarded, newer information can be entered, and edits after
the survey date are new info which should be kept. </div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2018-07-19 12:14 GMT+02:00 Andy
Townsend <span dir="ltr"><<a
href="mailto:ajt1047@gmail.com" target="_blank"
moz-do-not-send="true">ajt1047@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class="">On 19/07/2018 07:50, Peter Elderson wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
I would like some thoughts on the idea of tagging route
maintenance. Long hiking & cycling routes need
regular maintenance. On the road, of course, which is
not our problem, but as a consequence they need
re-surveying and adapting the route relations to
reality.<br>
</blockquote>
<br>
</span>
What do you mean by "maintenance" here? It could mean many
things:<br>
<br>
o Making sure that the route in OSM still matches the route
on the ground (diversions etc.).<br>
<br>
o Making sure that the route on the ground is actually
navigable (e.g. a section of a walking route near me has
suffered a landslip).<br>
<br>
o Making sure that the route markers on the ground are
mapped in OSM (and updating OSM where they have disappeared)<br>
<br>
o Making sure that the route is still contiguous in OSM
(sometimes if someone deletes and remaps an area they'll
forget to readd a way to the route)<br>
<br>
Best Regards,<br>
<br>
Andy
<div class="HOEnZb">
<div class="h5"><br>
<br>
<br>
______________________________<wbr>_________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org"
target="_blank" moz-do-not-send="true">Tagging@openstreetmap.org</a><br>
<a
href="https://lists.openstreetmap.org/listinfo/tagging"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://lists.openstreetmap.or<wbr>g/listinfo/tagging</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature" data-smartmail="gmail_signature">Vr
gr Peter Elderson</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Tagging mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Tagging@openstreetmap.org">Tagging@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/tagging">https://lists.openstreetmap.org/listinfo/tagging</a>
</pre>
</blockquote>
<br>
</body>
</html>