[Tagging] Section numbers in hiking routes

[Tod Fitch]

I was under the impression that the consensus was that a route name should be in a route relation that holds all the segments and that the segment names, if different from the route name, were on the segment.

Has that consensus changed or has my impression been wrong?

Cheers!
Tod

> On May 23, 2020, at 9:41 AM, Peter Elderson <pelderson at gmail.com> wrote:
> 
> Hold on to your hat.... In the name tag I will store...The Name Of The Route!
> 
> Op za 23 mei 2020 om 18:18 schreef Jo <winfixit at gmail.com <mailto:winfixit at gmail.com>>:
> In the end, what will be left in the name tag exactly?
> 
> Polyglot
> 
> On Sat, May 23, 2020 at 5:53 PM Peter Elderson <pelderson at gmail.com <mailto:pelderson at gmail.com>> wrote:
> I am trying to improve on the name-tag mess in the many hiking/foot routes in Nederland. All kinds of information is packed in those names. I am not doing any cleaning (yet) until all this information can be stored in proper tags and is handled or scheduled by significant renderers/data users/tools. There must be reasons for this (ab)use, because it is done all over the globe.
> 
> It's very common to store <from>-<to> and sometimes <via> in the name tag. That's an easy one: we have from=*, via=*, to=*.
> 
> Sometimes a complete description, a comment or a note (.e.g. about a temporary detour) is added to the name. Easy: we have description=, note=*, comment=*.
> 
> A ref in the name: store in ref=*.
> 
> Another item is section number. This is often used when the route is split in sections, often according to the sectioning given by the operator/website. So firstly it's a sort of reference, secondly its an ordering and sorting mechanism.
> Sometimes sections have their own name. I see that a lot in international (super)routes.
> 
> Any ideas how to do this without (ab)using the name tag? Is there a proper tag that springs to mind, or should we invent one?
> 
> Peter Elderson
> _______________________________________________
> Tagging mailing list
> Tagging at openstreetmap.org <mailto:Tagging at openstreetmap.org>
> https://lists.openstreetmap.org/listinfo/tagging <https://lists.openstreetmap.org/listinfo/tagging>
> _______________________________________________
> Tagging mailing list
> Tagging at openstreetmap.org <mailto:Tagging at openstreetmap.org>
> https://lists.openstreetmap.org/listinfo/tagging <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/20200523/e2d1bc7e/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20200523/e2d1bc7e/attachment.sig>