I’ve run into a similar issue with a building I was in, supported multiple connection types. So it’s wlan and wired. From the above discussion I understand that one could use semi-colon to add multiple entries. However, I’ve heard that this is not an established and documented method and may result in ignorance of such entries by data consumers. I’ve been told this in the StreetComplete discussion forum.
The question now is, how can this be changed to have it as established and documented method to have multiple entries for internet_access ? Is it by simply document it in the wiki or is there more to it?
I would say it makes sense to have this as an established method because people may be interested to know which internet access methods there are. A wired internet connection is more stable than WLAN and for this reason (amongst others) some people may be interested in this information.
There are some limitations mentioned in the semi-colon separator help , so maybe there are other methods to have multiple value’s added in OSM.
True. There are just a few of those, and internet_access=* wiki does mark them as potential tagging mistakes.
But that wiki does not mention semi-colon separated multi-values as on option for that key either, so it is possible (and even likely) that data consumers will not handle those undocumented multi-values, especially as the usage of all such multi-values combined are less than 0.1% of all internet_access=* values
If I was consuming values for that key, I’d probably ignore tags with combined usage of 0.1%, especially if they are undocumented. Unless that one key was sole reason for existence of my data consuming app, of course
It is usually the effort vs. gain math in my case… Anyway, that being said, those values do seem to be used (even if in not-so-noticable numbers), they do make sense, and they do follow existing popular scheme, so I see no harm in documenting that behaviour on the wiki.
In general, ‘one key, one value’ is the rule. - Key:name
When you need to write multiple values, it is better to use keys of different properties. - Multiple names
Nevertheless, use a ‘semi-colon’ if you need to use multiple names. - Semi-colon value separator
Excuse me, but then let me ask you something I’ve always been curious about.
How do you put the key value in the part that is part of ‘OO road’ and ‘XX bridge’?
Is it okay if I write ‘OO road;XX bridge’ only for that leg part?
On the chance of getting your question wrong for a bridge
name=abc (for the name of the road
When mapping a bridge area the bridge:name of the way becomes name=def which actually renders in Carto standard and often only when the bridge has a semi vertical posture on the map.
Somehow I’ve never gotten to the 2 names in one name=* tag line, not needed as there are so many ‘alt’ name tags available alt_ official_ old_, short_ full_, local_. On orchards though with mixed trees or farmland with mixed crop I do the *=apple;peer or olive_trees;peach_trees. No complaints from data consumers or QA progs, Works btw also well on e.g. phone/mobile numbers. Makes a POI lots friendlier to read.
Oh, QA cant handle the “/”. It assumes there’s 2 names…