`information=guidepost` and `information=route_marker` on same pole

How do you tag information=guidepost and information=route_marker hanging on the same pole?

Example:

Above is a classic hiking guidepost for my region, directly below it is a bicycle route marker on the same metal post.
I often find myself pondering how to correctly represent such cases.

In other cases, two guidepost for cycling and hiking separated are also hanging on the same pole, and the two signs have different refs and directions.

In principle, it may work to add bicycle=yes and hiking=yes to the same node and then possibly something like ref:bicycle and ref:hiking. But with the direction values, it gets tricky.

Let’s take the following example:

tourism=information
information=guidepost
bicycle=yes
ref=ABCD
direction_north=Appletown
direction_south=Orangetown
operator=Olive Disctrict

and

tourism=information
information=guidepost
hiking=yes
ref=1234
direction_north=Cherrytown
direction_south=Plumtown
operator=Tomato Municipality

Hence my questions on this:

  1. How do you tag the case in the example image if the value for information is already different?
  2. How do you tag two guideposts on one pole with different values on one pole?

Thanks!

1 Like

Two different guideposts/route markers → two nodes.

3 Likes
  1. While they are different sign plates here here, the info of a =route_marker could be seen as related to the =guidepost , which is more varied and detailed. It’s similar to ref= / destination:ref= (but for continuation) vs destination , which won’t be separated.
  2. There are ~1k destination:bicycle*= vs ~50 destination:foot*= , which would be usable on a type=destination_sign as well. Although I don’t like them, it could be direction_*:bicycle= + direction_*:hiking= similarly. Certainly they might be considered as 2 objects, but besides how they are physically overlapping, they refer to the same junction functionally, only differing by mode. If a pole or gantry has sign plates different vehicles, they can still be represented by the same object. To the extreme, a supplementary exception or condition plate to the main sign won’t be separated functionally, despite their physical separation. The more decisive factor here might be the operator= , which is functionally and data-wise more awkward to be combined by suffixing by mode,but I wonder who is the operator= of the pole itself.