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

[Alan Mackie]

Route relations are for set signposted routes that follow multiple paths,
roads etc.

Named paths are treated like any other highway=* with a name: add a name=*
to the path. As with other highway tags it is down to the data consumer to
recognise that several ways laid end to end with the same name=* are parts
of the same road with differing properties.

On Mon, 16 Aug 2021 at 13:01, Zeke Farwell <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>
> 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> 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 listTagging at openstreetmap.orghttps://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/680683ae/attachment.htm>