Some thematic (hiking) routes have information boards at their stations that also include a map of the entire route. What is the convention for mapping these?
Semantically, for me the cleanest option would be having two nodes next to each other, one having information=board + relation_member_type=station, and another one having information=map + relation_member_type=information
Is this a usual pattern or is it preferred to map such a board as a single node? If the latter, which tagging scheme would you suggest?
I haven’t seen two nodes mapped in this situation in areas that I hike in, but I haven’t studied what is done elsewhere.
I tend to tag one or the other based on my gut feeling about whether the map is an important feature of the display or just a sketch to give context to the text - partly influenced by the proportion of the display space given to the map. It can be somewhat arbitrary but I feel it doesn’t matter that much - I’m likely to stop and look at any kind of information display about a route I am hiking.
I sometimes loosely indicate this in the description e.g. “map of stage 3 of the Geological Trail with information about the route”.
I didn’t follow your reference to relations, are you referring to roles in a hiking route relation? Why use “station” for only one of the two?
I don’t think that either of those relation roles are in use? According to taginfo, a role of map is fairly popular (sort by nodes to get the list in the order that you want). board and information are more popular, but less precise.
Thank you for your responses so far! For context: I am building a dataset of thematic routes. Here, it is relevant information where each route has its stations and what the title of each station is.
While collecting this data, I have run into some thematic routes, where the boards describing the stations were simply mapped as information=map and had a ref tag with the station’s number. In real life, these are boards carrying both a description of the current station and a map of the entire route. Therefore, I am wondering how we could make the tagging state more explicitly, that each of these represents a station of the thematic route, while not losing the information that these are route maps.
This is from an educational trail about a forest. Node ID: 9488777716, mapped as information=board, not yet added to the route relation ID 10164994 to which it belongs. It introduces a tree species while containing a map of the route.
This is from a pilgrimage route. Node ID: 10123968963, mapped as information=map, not yet added to the relation ID 14612740 to which it belongs. The stele contains a description about the monastery ruin next to which it stands, while also carrying a route map.
I guess this refers to board_type rather than with a colon. Does that necessarily imply there is a map, though, or just that it is of interest to hikers? I see there are also 1500 uses of hiking=yes on information=board which sounds like it means the same thing although neither is well documented as far a I can see.
According to this, I would gravitate towards the station member type, I wonder how many of the station member type usages represent public transport stations though.
As for tagging the board itself: I would assume that an information=board with hiking=yes usually contains some kind of a map, but this may as well be a map showing nearby POI-s instead of a route overview map. Is using information=board along with map_type and map_size an antipattern?
In the UK and IE, there are 4 hiking routes with station members and 2 foot routes. Globally I’m sure there are more (think “stations of the cross” in Catholic countries), but it’s still not “normal usage”.
People sometimes update the wiki with usage that isn’t common worldwide, or usage that they’d like to see.