Hello,
Thanks for those comments! I see that it is not useful to modify the "to" of the relation.
But for my own control tools, I will still add all the paths between the guidepost and the destination. I added them with the "route" tag. I make a first test :
https://www.openstreetmap.org/relation/13659646
And, who knows, these information may be used by other engines in the future.
Best regards
Raphaël
Le dim. 9 janv. 2022 à 17:22, Raphael dafadllyn@gmail.com a écrit :
On Sun, 9 Jan 2022 at 12:01, Sarah Hoffmann lonvia@denofr.de wrote:
https://commons.wikimedia.org/wiki/File:Chemin_p%C3%A9destre_-_Poteau_induct...
The destination_sing relation documents a via point to use for that.
Correct URL: https://commons.wikimedia.org/wiki/File:Chemin_p%C3%A9destre_-_Poteau_indica...
A `via` role isn't needed in the above example because Col de la Forclaz points to the same direction three times. The guidepost indicates three possibilities to reach Col de la Forclaz and gives their hiking time. That is, the three possible routes to reach Col de la Forclaz begin with the same path and branch off at another place (that certainly has another guidepost).
By the way, the `via` role isn't supported by both [Waymarked Trails](https://waymarkedtrails.org/) and Mueschelsoft's [destination sign tool](https://osm.mueschelsoft.de/destinationsign/). However, even in situations where a guidepost doesn't point in the direction of a path that begins at the intersection next to the guidepost – like in the example below –, it's direction can correctly be represented by adding a node with the role `to` of the more distant path to the `destination_sign` relation. Thus, there is no need for `via` role.
https://www.openstreetmap.org/relation/13347671
Best regards
Raphael _______________________________________________ talk-ch mailing list talk-ch@openstreetmap.ch http://lists.openstreetmap.ch/mailman/listinfo/talk-ch