[Tagging] Clarification on the role link in route relations

Peter Elderson pelderson at gmail.com
Sat Jan 8 23:06:03 UTC 2022


A "link" role is not defined for recreational routes for cycling, hiking,
walking, paddling, motorboat, inline skating and horse riding. Skiing, I
don't know.
I think this link role may have had some use for signed motorway routes,
but not for connectivity, since the ways in the route are (should be)
themselves connected and in the relation.

Another discussion with hiking routes is that hikers can often simply cross
a separation to step from one way to another, where the ways are not
connected for vehicles and there is no actual path. Crossing a field,
linking a mapped cycleway to a way, linking a mapped sidepath to a way
where the sidepath stops. This discussion was not about roles but about how
to tag the ways added just for connectivity, not representing visible
paths. I have seen highway=link, path=link, link=yes, but not "link" roles
in relations for that.



Vr gr Peter Elderson


Op za 8 jan. 2022 om 23:38 schreef Dave F via Tagging <
tagging at openstreetmap.org>:

> On 08/01/2022 21:02, Minh Nguyen wrote:
> > This is a high enough number that it can't be dismissed as a mere
> > tagging mistake, yet it falls far short of the 766,473
> > highway=motorway_link ways, let alone other highway=*_link ways. [8]
>
> I think there maybe a misunderstanding of the difference between route
> relations & ways upon which route relations are placed.
>
> The link role of a route relation can be placed on *any* way. It's
> commonly used as an indicator for 'this is the way to go to get to the
> route' and not just connections between different routes.
> In the UK National Cycle Routes have signs for this with the ref number
> in brackets. (Roads also have this scheme, but IMO roads determined by
> their reference numbers are not valid route relations)
>
> > Meanwhile, the inclusion of "link" members causes problems for any
> > editor, QA tool, or data consumer that lacks support for this role
> > when determining the linear progression of a route.
>
> If they 'lack support' for the route role, how can it  causes problems'
> for them?
> The OSM database is 'as is'. If there's a problem in data consuming
> software using the database then you need to contact the software's
> developers to let them know about /their/ problem.
>
> > For example, iD has a known issue...
>
> iD editor has many known inaccuracies. It's very frustrating having to
> fix incorrect data added by it, especially it's validation system
>
>
> DaveF
>
> _______________________________________________
> 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/20220109/ce2efddd/attachment-0001.htm>


More information about the Tagging mailing list