Image and wikidata as combination
- image=* and wikidata=* really should not be listed as combination. This two tags can apply to every single object in the OSM database. 12:16, 15 January 2020 (UTC)
- I disagree with the first part, we could instead add them by bot to all items where they make sense. It is really useful for beginners to see which tags belong together no matter if they are general or specific.--PangoSE (talk) 12:36, 15 January 2020 (UTC)
Capacity for sleeping persons
It is useful to know for a shelter how many can sleep in it. At the moment capacity= is in use in sweden but I don't think it is clear that this only refers to sleeping. I propose to change to capacity:sleeping= and in conjunction with beds= this gives a quite clear picture of how big the feature is. E.g. capacity:sleeping=5 + beds=3 means there are space for 2 people on the floor. WDYT?--PangoSE (talk) 12:56, 15 January 2020 (UTC)
- Note that you are very unlikely to get feedback here, tagging mailing list is a good place to get plenty of feedback. On topic of tag itself - it seems OK, but note that it would not be documented on this page but elsewhere (we do not put tags with basically 0 use into combination listing) Mateusz Konieczny (talk) 13:09, 15 January 2020 (UTC)
The wiki (and I suppose these data items too) are designed to document how tags are commonly used. It is unhelpful to add rare tags to these lists. For example, "locked" is undocumented, "matress" has only been used 19 times (and is amenity=shelter the right tag in this case? The page suggests alpine_hut or wildnerness_hut - https://wiki.openstreetmap.org/wiki/Key:mattress), "water_source" has only been used 19 times and seems to be used inappropriately here, "table" should be "picnic_table", "distance_from_road" is new and rare, and so on.
My recommendation is to only add tags to the lists of "combination" if they are widely used. This isn't really the place to introduce brand-new tags or combinations. --Jeisenbe (talk) 12:59, 15 January 2020 (UTC)
- I wholeheartedly disagree. The combination property is for tags that are USEFUL to add to a feature. Think from a beginners perspective. I'm tagging a shelter, what information should I collect? Only the shelter_type? (this was the only combination until a few days ago).
- I suggest you bring this discussion to the talk of the property so we can establish how to do this wiki-wide. I'm surprised that you have reverted again without giving me time to reply?
- These are all IMO valid and useful tags in combination with amenity=shelter.
- To be totally clear some of these tags like floor:material are most useful on the lean_to type, others like beds= are only sensible for the type basic_hut. I found no way with our current properties to model that. I'm considering proposing a property "of" that can be used as a qualifier.
- When writing wiki-pages I would like to give the less experienced mappers an idea of how we best model the world into the database, this means adding more tags to the item is better than less.
- I find it troublesome that you try to restrict the combination property to some arbitrary subjective "most used" tags. This is not a good idea IMO. What about a hard limit instead? You are only allowed to add a combination if it is used in at least 0.001% of the nodes? This would in this case mean that I would easier add combinations to less used items like shelter_type=lean_to (~7300) that means that if 8 of them have floor:material=* it is ok to add it to combinations on the shelter_type=lean_to-item but not on amenity=shelter-item because there are 277,963 of those (mostly public_transport shelters).--PangoSE (talk) 14:30, 15 January 2020 (UTC)