Backward role in relation not honored

[dcesari]

It seems that the "backward" role in relation for one-way cross country piste segments is not honored and these segments are rendered in the opposite direction. For example this segment coincides with a (two way) road originally mapped towards the south but, as a piste, it has the piste:oneway=yes tag and it has a role=backward in the relation, meaning that it can be run one-way towards the north (and this is the case on the field, it's a shortcut for the "Panorama" piste). In my view this is a correct way to tag, but on openskimap.org it is oriented towards the south and this also partly breaks the navigation in the profile.
Could this be fixed?

[russellporter]

In general, relations support is very limited, the relation data is only used to supplement a segment's metadata (how the name got added to the segment in this case). Roles are not used at all at the moment.

That said, in this case the problem with the direction of the segment is not related to the relation. Imagine we didn't have the relation at all, we'd still have a oneway piste that was in the wrong direction. The tagging of the way implies that the piste is oneway in the direction of the way. The simplest solution is to reverse the way.

If you couldn't reverse the way for some reason due to side effects (imagine the case of a oneway road that becomes a oneway ski trail in the opposite direction in winter), you can also use piste:oneway=-1 to indicate the piste is in the opposite direction of the way. That said, OpenSkiMap does not currently support that tagging value, I have created a separate issue for that #151.

The use of roles in relations will come when adding proper support for routes in #80

[dcesari]

Thank you for the reaction, that was exactly the point, in most cases I could probably reverse the way, but in general I do not know the side effects and maybe there was a good reason for orienting it like that.