In the end, what will be left in the name tag exactly? Polyglot
On Sat, May 23, 2020 at 5:53 PM Peter Elderson <[email protected]> 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 > [email protected] > https://lists.openstreetmap.org/listinfo/tagging >
_______________________________________________ Tagging mailing list [email protected] https://lists.openstreetmap.org/listinfo/tagging
