How should destinations on hiking guideposts be mapped?

Help and support
1

While recording image sequences for Panoramax, I’ve been stopping at hiking guideposts and taking detailed photos of them and uploading the photo, as the information on them seems potentially useful for OSM.

image
image952×629 114 KB

When I edit the map, I add the guidepost itself with its name and elevation.

Is there also a possiblity to map the destinations indicated by the individual arrows?

For example, this guidepost at Kulmhütte has an arrow pointing to “Goldau”. Would it make sense to represent this with relation connecting the guidepost to the destination/path towards Goldau?

2

You could use direction_* tags, e.g. direction_north=Goldau;Daechli;..., direction_south=Rigi Kulm.

Another option is a destination_sign relation.

3

Ein paar sind in der Gegend schon erfasst, z.B.
Node: ‪Rigi Staffel‬ (‪3794227524‬) | OpenStreetMap

Und eine minimalistische Darstellung gibt es auch:
OSM Destination Signs

4

In Italy we use the CAI guidelines: IT:CAI - OpenStreetMap Wiki

We use the destination tag, with ; to separate destinations and | to separate arrows.

5

I mapped some destinations as “destination=;…”, that way a router could e.g. instruct a user to “follow the table pointing xy” - no idea if full blown “direction:=” or even relations necessary for that. It is just wishful thinking any ways.

6

The problem with simple destination tags on guideposts is that nobody knows where they point which makes

mostly impossible because it could be the entry pointing in the opposite of the intended direction.

7

Ich glaub, das einzige was Router je auswerten werden, wenn überhaupt irgendwas, dann sind das Relationen. Nur dann geht das, ohne dass Wissen von außerhalb eingebracht werden muss, seien das nun Ziele am Weg oder Himmelsrichtungen.