[Tagging] ref:forward and ref:backward?

Jo winfixit at gmail.com
Thu Jan 12 14:55:34 UTC 2017

The 2 or more relations for each variation is the way to go for Public
Transport routes. Walking and bicycle routes use the forward and backward
roles to describe both directions in one route relation.


2017-01-12 15:01 GMT+01:00 Martin Koppenhoefer <dieterdreist at gmail.com>:

> 2017-01-12 6:40 GMT+01:00 <roadsguy99 at gmail.com>:
>> I certainly use route relations, and since ref is only really used for
>> the renderer, I don’t know what I was thinking ref:forward and ref:backward
>> would be useful for…
> Tagging considerations are not "for the renderer", it's about how the
> world can be abstracted to be stored in such a way that the information you
> are interested in can be found in the data.
> Regarding the "forward" and "backward" roles for way members of routes:
> they refer to the direction of the way (member), not to the direction of
> the relation. If you want to map a route which goes from A to B it will
> typically be different from a route that goes from B to A (because of dual
> carriage ways and other (even short) oneway roads (like links, ramps) ,
> etc.), and the solution is to map 2 routes and eventually connect them with
> a route master.
> https://wiki.openstreetmap.org/wiki/Relation:route_master
> Cheers,
> Martin
> _______________________________________________
> 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/20170112/ec1b4b7c/attachment-0001.html>

More information about the Tagging mailing list