Re: [Tagging] Feature Proposal - RFC - (changing_table:location)

2019-12-06 Thread Sören Reinecke via Tagging
s. Cheers Sören Reinecke alias Valor Naram -Original Message- From: Sören Reinecke via Tagging Reply-To: "Tag discussion, strategy and related tools" < tagging@openstreetmap.org> To: Tagging@openstreetmap.org Cc: Sören Reinecke Subject: [Tagging] Feature Proposal - RFC - (cha

Re: [Tagging] Feature Proposal - RFC - (changing_table:location)

2019-12-05 Thread Martin Koppenhoefer
sent from a phone > On 5. Dec 2019, at 21:41, Jan Michel wrote: > > Also, introducing another set of 7 tags for such a minor piece of information > is (at least to me) an absolute overkill. my suggestion if you want to map these in great detail would be mapping the bathrooms (or other thin

Re: [Tagging] Feature Proposal - RFC - (changing_table:location)

2019-12-05 Thread Markus
Hi Sören Multiple tags are only needed if each of them describes a different property, which is not the case for changing_table:location. I don't see a problem with adding two or more values separated by a semicolon in this case. In the contrary: a value list is clearer and it seems that it can be

Re: [Tagging] Feature Proposal - RFC - (changing_table:location)

2019-12-05 Thread Jan Michel
Hi, I very much prefer the already accepted version. There is nothing wrong with semicolon separated values. Searching for one key and splitting its value is so much faster than searching with wildcards in a huge database like ours. Also, introducing another set of 7 tags for such a minor piece

[Tagging] Feature Proposal - RFC - (changing_table:location)

2019-12-05 Thread Sören Reinecke via Tagging
Hey all, A new but small proposal to change the specification for subkey `changing_table:location` because of a discussion yesterday about using seperators in values. I totally agree that we should avoid using seperators when possible. Proposal: https://wiki.openstreetmap.org/wiki/Proposed_featur