[Tagging] hiking route from= and to= tags

Peter Elderson pelderson at gmail.com
Thu Jul 1 07:37:50 UTC 2021


Looks good!
I think for recreational routes (for hiking, cycling, horse riding, skiing,
paddling, motorboat, skating), it is also an improvement, but these are
much more varied in labeling than PT and road routes. Especially when
considering heavily sectioned routes; hierarchically ordered routes;
two-directional routes where the two directions are in one route relation;
node network routes using numbered, coded and named nodes as start/end
points which are reflected in the labeling of the routes; and combinations
of these types.
Even when not considering 'pretty print'-wishes, it would be very hard to
design a single labeling format that contains all the elements that mappers
have stacked into (combinations of) the name, ref, note, network,
description and other tags of the recreational route relations.

So, well done and it is an improvement, but, while it does apply to all
routes, I would not say it solves the labeling problem for all routes,
especially considering current tagging practices.

At the moment, I think only a personalized adaptable template, allowing
free placement of text, punctuation and data elements in one display
string, would solve the route labeling issue for all routes.

Peter Elderson


Op do 1 jul. 2021 om 02:15 schreef Minh Nguyen <minh at nguyen.cincinnati.oh.us
>:

> Vào lúc 02:43 2021-06-26, Mateusz Konieczny via Tagging đã viết:
> >
> >
> >
> > Jun 25, 2021, 22:24 by ml at osm.datendelphin.net:
> >
> >     But knowing the start and end of each segment (which was used as the
> >     name) helps maintaining the hiking network. So the change will add
> the
> >     from=* and to=* tags to the Swiss wiki page to map the start and end
> >     place. That way, the name tag does not get misused, and the data is
> >     still there for mappers to use for maintenance.
> >
> > Seems good alternative to using fictional name as form of
> > mistagging for the renderer.
> >
> > Once such tags become clearly used it may make sense to propose
> > supporting them in JOSM, iD, Vespucci etc in relation listings
> > (if name tag is missing then show "{from} - {to} hiking route" in
> > the name field)
>
> Non-name-based labeling has been implemented in iD for all kinds of
> route relations. [1] It'll be in the next release of iD, but you can try
> it out in the latest development mirror: try deleting the name=* tags
> from the relations that contain the selected way in [2], then reselect
> the way and look at the list of parent relations. The exact format
> depends on the localization you're using, but regardless it no longer
> relies on ASCII art. ;-)
>
> There's also a request to label a route's ref=* tag even if it has a
> name=* tag. [3]
>
> [1] https://github.com/openstreetmap/iD/pull/8276
> [2]
>
> https://ideditor.netlify.app/#background=Bing&id=w316900907&map=19.00/37.33024/-121.90173
> [3] https://github.com/openstreetmap/iD/issues/8559
>
> --
> minh at nguyen.cincinnati.oh.us
>
>
> _______________________________________________
> 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/20210701/e2215670/attachment-0001.htm>


More information about the Tagging mailing list