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

[Sarah Hoffmann]

On Thu, Aug 12, 2021 at 10:10:17PM +0200, Peter Elderson wrote:
> Probably my lack of searching skills, but I can't really find where this is
> documented as a regular practice.
> WMT supports it and documents that, so I could have known that if I had
> paid attention, but do other renderers/routers/apps?

It's not documented anywhere and I don't think any other renderer
supports it. It's a bit of an easter egg that has been sitting quietly
in the waymarkedtrails website for something like 8 years now because
it's a bit of a niche thing anyway. There are only a couple of hundred
multi-use routes tagged at the moment.

Note that I think this tagging is only valid if a route is officially
designated as a multi-use route. The Pennine Bridleway is a well known
example. It is officially designated for horses and MTB. (That it is
currently tagged as route=mtb;horse;hiking is already a stretch imo but
the British will know better.) Tagging such a route with two relations
violates the one feature - one OSM object rule.

The semicolon tagging  certainly shouldn't be used just because a hiking
and cycling route share the same ways. Also by definition all modes must
share exactly the same properties to qualify as being the same route.
Different names? Use two separete relations. Different routing along the
route for the different modes? Not the same relation. It's a route
designated for one mode but usable with others? Use one relation with the
designated mode and put the accessibility/usability for the other mode
somewhere else.

In any case, it's not a tagging schema, I'm particularly attached to.
It is clumsy. I just haven't seen any less clumsy suggestions for the
situation. https://www.openstreetmap.org/relation/916331
has route=multiaccess and then the usual bicycle/foot/horse=yes.
That might be a solution to make the situation more explicit. Maybe
using the more general route=recreational that was also suggested in
this thread. But we'd still have the mess of the network tag that
needs to be different for each mode for historical reasons.

Sarah

> 
> Peter Elderson
> 
> 
> Op do 12 aug. 2021 om 21:40 schreef Sarah Hoffmann <lonvia at denofr.de>:
> 
> > On Thu, Aug 12, 2021 at 06:49:05PM +0200, Peter Elderson wrote:
> > > Right! Good to know. And network=...;...;... to go with it? Or just the
> > scope indicator l, r, n, i?
> >
> > The network needs the semi-colon notation, too, to get you
> > the national/regional/local classification for each of the modes.
> > But the route tag is the one that needs to be present to make
> > the route show up at all.
> >
> > The network tag is one of the bigger mistakes we made in
> > the early days of OSM. But that's a different topic.
> >
> > Sarah
> >
> > > > Op 12 aug. 2021 om 16:11 heeft Sarah Hoffmann <lonvia at denofr.de> het
> > volgende geschreven:
> > > >
> > > > On Thu, Aug 12, 2021 at 02:19:41PM +0100, Andy Townsend wrote:
> > > >>> On 12/08/2021 11:52, Peter Elderson wrote:
> > > >>>
> > > >>> I can think of three options:
> > > >>> ...
> > > >>>
> > > >>> 2. multiple values for network: network=nwn;ncn
> > > >>> This would work, but requires adapting tools and applications. Maybe
> > induces name "localization", because it may be the same route but the name
> > could differ, e.g.: "Limes hiking trail" vs "Limes cycling trail".
> > > >>> ...
> > > >>
> > > >>
> > > >> There are a few examples in the UK, so I added support for things like
> > > >> "network=ncn;nhn;nwn" to map.atownsend.org.uk :
> > https://map.atownsend.org.uk/maps/map/map.html#zoom=15&lat=54.07759&lon=-2.19974
> > > >> .
> > > >>
> > > >> Waymarked trails also supports it - see e.g.
> > > >> https://riding.waymarkedtrails.org/#?map=13!54.0752!-2.2093 .
> > > >
> > > > waymarkedtrails expects semicolon-separated values in
> > > > the route tag, to be precise, e.g. route=hiking;bicycle;horse
> > > >
> > > > Sarah
> > > >
> > > > _______________________________________________
> > > > Tagging mailing list
> > > > Tagging at openstreetmap.org
> > > > https://lists.openstreetmap.org/listinfo/tagging
> > >
> > > _______________________________________________
> > > Tagging mailing list
> > > Tagging at openstreetmap.org
> > > https://lists.openstreetmap.org/listinfo/tagging
> >
> > _______________________________________________
> > Tagging mailing list
> > Tagging at openstreetmap.org
> > https://lists.openstreetmap.org/listinfo/tagging
> >

> _______________________________________________
> Tagging mailing list
> Tagging at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging