[Tagging] How to tag recreational route with multiple route types?

[Tod Fitch]

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.

--
Sent from my phone, please forgive my brevity.

> On Monday, Aug 16, 2021 at 10:01 AM, Zeke Farwell <ezekielf at gmail.com (mailto:ezekielf at gmail.com)> wrote:
> 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: https://hiking.waymarkedtrails.org/#?map=13!44.3046!-71.2961
>
>
> On Mon, Aug 16, 2021 at 10:24 AM Dave F <davefoxfac63 at btinternet.com (mailto:davefoxfac63 at btinternet.com)> wrote:
> > "named paths" are not route relations.
> >
> > The physical path can have a name & have numerous route relations run over it.
> > A route relation isn't required to indicate that a certain transport mode is designated.
> >
> > The correct tagging:
> > highway= footway/cycleway/bridleway etc
> > surface=*
> > foot= yes/no/designated
> > bicycle= yes/no/designated
> > horse= yes/no/designated
> > etc
> >
> > Then add any officially authorized route relations to this way.
> >
> > DaveF.
> >
> >
> > On 14/08/2021 17:04, Zeke Farwell wrote:
> > > On Thu, Aug 12, 2021 at 10:11 AM Sarah Hoffmann <lonvia at denofr.de (mailto:lonvia at denofr.de)> wrote:
> > > > waymarkedtrails expects semicolon-separated values in
> > > > the route tag, to be precise, e.g. route=hiking;bicycle;horse
> > >
> > > 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?
> > >
> > >
> > >
> > >
> > >
> > > _______________________________________________ Tagging mailing list Tagging at openstreetmap.org (mailto:Tagging at openstreetmap.org) https://lists.openstreetmap.org/listinfo/tagging
> _______________________________________________
> Tagging mailing list
> Tagging at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20210816/2f2836e6/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 868 bytes
Desc: not available
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20210816/2f2836e6/attachment-0001.sig>