We have only a few people contributing to this discussion, therefore a personal preference is good, but we should objectify the decission. Multiple persons have statet that chain_change_area
feels awkward, which is for sure enougth to have another look at it.
Nevertheless we need something that will work as tag both for simple cases, occasional mappers, and complicated situations. It should be robust enough for that.
Keys and values are codes and mnemonics, but not exact descriptions. Code means that in other contexts it could mean something different, but here in OSM something very specific, well understood and documented. We could just use numbers for that purpose. Mnemonic means it’s easy to remember (better than numbers…). highway=path
seems paradox but works great for OSM. At the same time it should not collide with some common meaning of a term and lead to misunderstandings. to chain down seems to spark associations with to bolt down, not helpfull here.
For this snow chain manipulation places, different countries have different names. Moreover they come in different flavours, from lanes that can be dedicated to that purpose, sections of road shoulder, bays, and separate areas. Size can vary from suitable for a single vehicle and very short up to dozen of vehicles and stretching for several hundred meters.
Usually, we would use the British English term, but I have the very strong feeling that there are no such places in the UK, even in Scotland snow seems to last not long enough for people to bother evena about snow chains.
Some things have different names for complementing aspects of the same thing, like entry
and exit
. It would be preferrable to have a key that combines that in a generic way that does not preclude one of the aspects. Then we can establish more tags that resolve that to more specific aspects, providing a better structure and more flexibility. Most of the proposed names include area, which is most of the time fine, but also leads to colissions and less flexibility.
It would be nice if related tags can be identified/assigned by their name. Here, chain
seems not enough, as this could mean many different types of chains.
Finally, it should not be too long and complicated, or it gets awkward again.
Requirements:
- Not entirely awkward
- Mnemonic: Ease to understand and remember
- Generic, not necessarily an exact description or regular used term.
- No collision with different denotation
- Relatable to then main topic.
Something that a former Californian proposed to me in a personal discussion is snow chain stop
. It sounds strange at first, but I like it for many reasons:
- the connection to snow chains,
- being not a used term and thus not favouring anything,
- being generic,
- not denoting an element type (node, way, area),
- and including something that you have to do anyway, that is stop.
It parallels to bus stop
and rest stop
.
Including the Wiki Discussions Chain down area and Object type to use we have the following proposals:
proposal |
awkwardness |
mnemonic |
generic |
colission |
assignable |
amenity=chain_up_area |
- |
+ |
- |
+ |
~ |
amenity=chain_up_area , amenity=chain_down_area
|
- |
+ |
- |
- |
~ |
amenity=chain_up_area, amenity=chain_off_area |
~ |
+ |
- |
+ |
~ |
amenity=chain_change_area , chain_change_area=* , chain_change_area:lanes=*
|
- |
+ |
- |
- |
~ |
amenity=chain_up/chain_down, chain_up=only/designated/yes/no |
- |
+ |
- |
- |
~ |
amenity=chain_install_area |
+ |
~ |
- |
+ |
~ |
amenity=chain_mounting_place |
- |
~ |
- |
+ |
~ |
amenity=chain_station |
~ |
~ |
~ |
~ |
~ |
amenity=chain_fitting |
~ |
~ |
- |
- |
~ |
amenity=snow_chain_stop |
~ |
+ |
+ |
+ |
+ |
For voting, I do not want people to start the discussion over again, so let’s find something agreeable, the thing where the least number of people could identify serious problems.