he wiki
>
> 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ö
nal 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 - (Unifying playground
equipment tagging)
Date: Mon, 30
Sören Reinecke via Tagging wrote:
> Proposal:
> I propose the key playground to be deprecated and the use of key
> playground:* instead. That would mean that on both playground and
> playground equipment objects in OSM the key playground:* applies. This
> then would also allow to map playgrounds
> 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
> Well the equipment in this case is playground=sandpit.
As the outline of the sandpit is identical with the outline of the
leisure=playground, why would
this be wrong?
Theoretically you need to create an object for the playground itself
and another object for the playground equipment. Both then
sent from a phone
> On 30. Mar 2020, at 20:03, Sören Reinecke via Tagging
> wrote:
>
> For example: https://www.openstreetmap.org/way/137931618 . In this case
> Key:playground was used to tag playground equipment on the playground
> object itself. But for such cases we use Key:playground:* .
On 30.03.2020 20:02, Sören Reinecke via Tagging wrote:
>> How will that help? What errors are you commonly finding?
>
> For example: https://www.openstreetmap.org/way/137931618 . In this case
> Key:playground was used to tag playground equipment on the playground
> object itself. But for such
On 30.03.2020 20:02, Sören Reinecke via Tagging wrote:
>> How will that help? What errors are you commonly finding?
>
> For example: https://www.openstreetmap.org/way/137931618 . In this case
> Key:playground was used to tag playground equipment on the playground
> object itself. But for such
> The current system seems to make sense.
It makes sense but it seems that it is also much error-prone because it
is easy to oversee one sentence in the wiki of Key:playground:* and
Key:playground that makes the difference (pointing the case where the
key should be applied)
> If you have a
Am Mo., 30. März 2020 um 16:45 Uhr schrieb Sören Reinecke via Tagging <
tagging@openstreetmap.org>:
>
> https://wiki.openstreetmap.org/wiki/Proposed_features/Unifying-playground-equipment-tagging
>
>
> Proposal:
> I propose the key playground to be deprecated and the use of key
> playground:*
The current system seems to make sense.
If you have a leisure=playground feature, probably mapped as an area,
you can tag it with a list of tags like "playground:slide=yes",
"playground:swing=yes", to show what equipment is available.
If you want to map a slide or a swing as a separate feature,
Hey,
a new RFC for
https://wiki.openstreetmap.org/wiki/Proposed_features/Unifying-playground-equipment-tagging
Purpose:
Simplified tagging of playground equipment on the playground itself or
as separate object. Both schemes already exist and I want to combine
them to help to decrease tagging
12 matches
Mail list logo
