Re: [Tagging] Feature Proposal - RFC - (changing_table:location)
I step back from my proposal https://wiki.openstreetmap.org/wiki/Proposed_features/Subkey:changing_table:location which is totally fine because of less work. The webapp "Babykarte" by the way supports semicolons as seperators so I do not have problems of having semicolons in values. 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 - (changing_table:location) Date: Thu, 05 Dec 2019 14:39:27 +0100 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_features/Subkey:changing_table:location Definition: Tagging of the location of the nappy changing facility in a POI Reason: Someone pointed to the wikipage Semi-colon value separator as part of a discussion of using semicolons as seperator of key values. In my previous successful proposal the subkey `changing_table:location' allows to seperate the values by a semicolon. While the support of a semicolon as seperator for this subkey falls under the three exceptions ( https://wiki.openstreetmap.org/wiki/Semi-colon_value_separator ), I want to give here the chance to change that because the subkey changing_table:location is still not in widespread use. Cheers Sören Reinecke alias Valor Naram ___Tagging mailing listtagg...@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Feature Proposal - RFC - (changing_table:location)
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 things) and adding the property to them rather than the bigger, containing feature (museum, shopping mall etc.), also because even at the proposed level of detail there would be room for ambiguity (e.g. several distant ladies bathrooms in the same feature), or, map the changing table as a feature on its own rather than a property of something else. Cheers Martin ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Feature Proposal - RFC - (changing_table:location)
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 used more easily by data users (see this discussion [1] and its continuation [2]). The wiki page on Semi-colon value separator [3], which you referred to, seems to be overly strict when it says that "avoid ';' separated values whenever possible". [1]: https://lists.openstreetmap.org/pipermail/tagging/2018-December/041650.html [2]: https://lists.openstreetmap.org/pipermail/tagging/2019-January/041884.html [3]: https://wiki.openstreetmap.org/wiki/Semi-colon_value_separator Regards Markus ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Feature Proposal - RFC - (changing_table:location)
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 of information is (at least to me) an absolute overkill. Jan On 05.12.19 14:39, Sören Reinecke via Tagging wrote: 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_features/Subkey:changing_table:location Definition: Tagging of the location of the nappy changing facility in a POI ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
[Tagging] Feature Proposal - RFC - (changing_table:location)
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_features/Subkey:changing_table:location Definition: Tagging of the location of the nappy changing facility in a POI Reason: Someone pointed to the wikipage Semi-colon value separator as part of a discussion of using semicolons as seperator of key values. In my previous successful proposal the subkey `changing_table:location' allows to seperate the values by a semicolon. While the support of a semicolon as seperator for this subkey falls under the three exceptions ( https://wiki.openstreetmap.org/wiki/Semi-colon_value_separator ), I want to give here the chance to change that because the subkey changing_table:location is still not in widespread use. Cheers S??ren Reinecke alias Valor Naram ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
