[talk-au] Should a "trail" route relation be one-way?

[Warin]

On 5/9/22 15:52, stevea wrote:
> BTW, I very much recommend using JOSM as your preferred editor when editing relations, especially route relations.  IMO, the route relation editor in JOSM is superior to all others.  Don't forget to click the "sort relation" button as a last step in the relation editor window before you close it, that "neatens up" the elements so they connect with each other as best they can (the set of elements that are in the relation when you click it), and identifies any remaining gaps visually and readily.  JOSM's relation editor also pays attention to forward and backward directional role tags, presenting them (after a click of the sort button) in a visually clear way.  With practice, once you "get it," you won't go back to any other way of editing (especially route) relations!



Be careful with the automated tool .. you can end up with the route 
comprising some 'north bound' bits with some 'south bound bits'.


Roles 'forwards' and 'backwards' refer to the direction of travel with 
respect to the direction of the way - not 'north', 'south' 'east nor 
'west'.


Route roles are

'main'

'excursion'

'approach'

'connection'

'alternate'

See https://wiki.openstreetmap.org/wiki/Tag:route=hiking?uselang=en#Roles


You may find that the renders of hiking/bicycle and horse routes will 
take no notice of 'forwards' and 'backwards'.


--------------------------------

Thinking about this .. and coming from 'public transport' routes ...

Use 2 relations

One from 'x' to 'y' (and public transports uses keys 'from' and 'to')

The other from 'y' to 'x'.

So you'd have 2 Munda Biddi Trail route relations.. similar to the India 
Pacific train - one from Perth the other from Sydney.

This would make clear the north only and south only routes...