<html xmlns="http://www.w3.org/1999/xhtml"><head> <title></title> <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=no"> </head> <body><div id="CanaryBody"> <div> I believe there is at least one hiking app/website that doesn’t show a trail unless it is in a route relation. I think this is a bad decision on their part and might be driving some mappers to use a route relation when not needed or appropriate.</div> <div><br></div> </div> <div id="CanarySig"> <div> <div style="font-family:Helvetica;"><div style="font-family:Helvetica;">--<br>Sent from my phone, please forgive my brevity.</div></div> <div><br></div> </div> </div> <div id="CanaryDropbox"> </div> <blockquote id="CanaryBlockquote"> <div> <div>On Monday, Aug 16, 2021 at 10:01 AM, Zeke Farwell <<a href="mailto:ezekielf@gmail.com">ezekielf@gmail.com</a>> wrote:<br></div> <div><div dir="ltr"><div>DaveF, if "named paths" are not route relations, then what exactly are the minimum requirements for route relations? At any rate it appears that many mappers do not share this view and happily add route relations for every named path. Take this popular hiking area for example: <a href="https://hiking.waymarkedtrails.org/#?map=13!44.3046!-71.2961">https://hiking.waymarkedtrails.org/#?map=13!44.3046!-71.2961</a><br></div><div><br></div><div><br></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Aug 16, 2021 at 10:24 AM Dave F <<a href="mailto:davefoxfac63@btinternet.com">davefoxfac63@btinternet.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> "named paths" are not route relations. <br> <br> The physical path can have a name & have numerous route relations run over it.<br> A route relation isn't required to indicate that a certain transport mode is designated. <br> <br> The correct tagging:<br> highway= footway/cycleway/bridleway etc<br> surface=*<br> foot= yes/no/designated<br> bicycle= yes/no/designated<br> horse= yes/no/designated<br> etc<br> <br> Then add any officially authorized route relations to this way.<br> <br> DaveF.<br> <br> <br> <div>On 14/08/2021 17:04, Zeke Farwell wrote:<br> </div> <blockquote type="cite"> <div dir="ltr"> <div dir="ltr" class="gmail_attr">On Thu, Aug 12, 2021 at 10:11 AM Sarah Hoffmann <<a href="mailto:lonvia@denofr.de" target="_blank">lonvia@denofr.de</a>> wrote:<br> </div> <div class="gmail_quote"> <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> waymarkedtrails expects semicolon-separated values in<br> the route tag, to be precise, e.g. route=hiking;bicycle;horse<br> </blockquote> <div><br> </div> <div>I'm glad to learn about this. There are many multi-purpose recreational routes in my area that will make sense to tag this way. The idea of creating five separate route relations for a single named path just because it is designated for five transport modes (walking, cycling, inline skating, horse riding, and skiing in the winter), feels wrong and in violation of the "one feature, one OSM element" principle. How many other data consumers are there that use route relations but don't handle semi-colon delimited values, though? Clearly a map that only shows route=bicycle is going to miss out on route=foot;bicycle, route=bicycle;horse;ski, etc. How can we get more data consumers to parse semi-colon delimited values in the route and network tags?<br> <br> </div> <div><br> </div> <div><br> <br> </div> </div> </div> <br> <fieldset></fieldset> <pre>_______________________________________________ Tagging mailing list <a href="mailto:Tagging@openstreetmap.org" target="_blank">Tagging@openstreetmap.org</a> <a href="https://lists.openstreetmap.org/listinfo/tagging" target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a> </pre> </blockquote> <br> </div> </blockquote></div></div> _______________________________________________ <br>Tagging mailing list <br>Tagging@openstreetmap.org <br>https://lists.openstreetmap.org/listinfo/tagging <br></div> </div> </blockquote> </body></html>