[Tagging] Feature Proposal - RFC - (Unifying playground equipment tagging)

[Sören Reinecke]

> You are proposing to abandon the distinction between playgrounds and
implicit features on them (properties) and things on a playground
(explicitly mapped playground equipment as a feature).

Not really, playground equipment (tagged with 'playground:') on a
feature tagged with its main tag 'leisure=playground' indicates that
the feature is a playground. The key 'playground:' on that feature
describes just its properties. The distinction is being done by
'leisure=playground'.

> Wouldn't this move make it actually harder, rather than simpler, to
understand what is represented?

No because the keys 'playground' and 'playground:' are not describing
the feature itself but are describing what the feature has:

leisure=playground
playground:*= yes

as I suggest describes a playground with its properties (playground
equipment) on it. Playground equipment tagged as feature (separate
object) would then be tagged like this:

playground:*=yes
...
(not containing 'leisure=playground')

> Usually we are advocating for the contrary: using different keys for
features provided by other features (properties) and features mapped
explicitly. In this case, it is already like this, and you do not
provide (IMHO) sufficient arguments to change it.

I know and I love this way of handling. I can just give one example of
how people are using the 'playground' key wrongly on a feature tagged
as 'leisure=playground':

http://www.openstreetmap.org/node/6323927215
  leisure=playground
  playground=structure

correct would be

http://www.openstreetmap.org/node/6323927215
  leisure=playground
  playground:structure=yes

That's why I think the actual way is to confusing. I am personally
total fine with the situation as it is now because it makes *sense*.

> Redefining tags that are in use (properties for playgrounds then could
also represent explicit features) is generally problematic, why aren't
you proposing different tags as an attempt to avoid confusion?

Because the key 'playground' mapped on a playground equipment (explicit
feature) is also being used on playground features with
'leisure=playground'. This is wrong and leads also to confusion. That's
why I want to propose the other way around to hopefully solve the
problem of using semicolons on the 'playground' key to indicate
multiple equipment as it is here 
http://www.openstreetmap.org/way/166629582 . Normally I would run a
world wide Overpass Query for such cases and would convert it to the
'playground:*' scheme as a QA attempt.

> I do not understand why this would make mapping easier or less error
prone. You will find tags that are not used as documented for any
feature.

See my examples.

-- 
Sören Reinecke alias Valor Naram <tilmanreinecke at yahoo.de>