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

Yves ycai at mailbox.org
Thu Aug 12 20:47:28 UTC 2021


I would tend to think that the 3rd option is preferable, because sooner or later I'm afraid a mapper will face a dead-end with the need for another tag on the route that is valid for hiking but not cycling, for instance.

Now, my experience shows that Joe mapper takes any direction allowed technically by the OSM data model. As a consequence, already for a long time, when dealing with routes, you have to take care of relations sharing the same ways, semicolons in relations, semicolons in ways, overlapping ways and side-by-side ways if you want to make the most of our data. 
This is not always easy to reconciliate the various way people map for proposing a nice rendering or a sensible routing, but a serious data consumer has to. 

Regards, 
Yves 


Le 12 août 2021 22:10:17 GMT+02:00, Peter Elderson <pelderson at gmail.com> a écrit :
>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?
>
>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
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20210812/7b26fa08/attachment-0001.htm>


More information about the Tagging mailing list