<div dir="ltr">Hi Kevin, <div><br></div><div>No, no, I am not saying it's always wrong and I am not going to "correct" any routes I don't know! </div><div><br></div><div>Where I am tagging and maintaining routes, I have done a lot of tagging I know for sure is wrong, because I have walked them myself, I know the operators and the facebook groups for nearly all the hiking trails in Nederland, and I do a lot of maintenance on the relations. I also know for a fact that OSM communities and hiking operators in other countries also (ab)use the name tag for all kinds of extra information, to get nice and ordered lists.</div><div><br></div><div>I would like to help improve that, but only if alternatives are developed for the (IMO) legitimate reasons why people do this!</div><div><br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">Peter Elderson</div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Op zo 27 jun. 2021 om 22:09 schreef Kevin Kenny <<a href="mailto:kevin.b.kenny@gmail.com">kevin.b.kenny@gmail.com</a>>:<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 dir="ltr">Also, don't assume that start and end points can't be part of a trail name. Names like "Ramapo-Dunderberg Trail", "Neversink-Hardenbergh Trail", or "Mount Van Hoevenberg Trail to Marcy", where the trail is named for its endpoints, are quite common where I hike. Some of these, like the 220-km Northville-Placid Trail, are quite regionally significant. (Most of these trail names are unsigned or signed very infrequently, because excessive signage in a wilderness area is frowned upon. But pretty much all the trail maps, whether from the hiking clubs or publishers like National Geographic, show the names, and the hikers know them.) So, Peter, please don't assume that `name` tags in my part of the world are mistagged!<div><div><br></div><div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Jun 27, 2021 at 3:00 PM Peter Elderson <<a href="mailto:pelderson@gmail.com" target="_blank">pelderson@gmail.com</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 dir="ltr"><div dir="ltr"><br clear="all"><div><div dir="ltr">Vr gr Peter Elderson</div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Op vr 25 jun. 2021 om 22:26 schreef michael spreng </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
But knowing the start and end of each segment (which was used as the<br>
name) helps maintaining the hiking network. So the change will add the<br>
from=* and to=* tags to the Swiss wiki page to map the start and end<br>
place. That way, the name tag does not get misused, and the data is<br>
still there for mappers to use for maintenance.</blockquote><div><br></div><div> How are these basic segments used by data users / end users? I mean, not on the road but the information in OSM? Is there a router for it, or a planning application, or a special map visualising the basic network, anything available to the non-OSM savvy public to help with their hiking trips?</div></div></div>
_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org" target="_blank">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging" rel="noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr">73 de ke9tv/2, Kevin</div>
_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org" target="_blank">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging" rel="noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</blockquote></div>