#12502 closed enhancement (fixed)
Warn about using leisure=park on nodes
Reported by: | mdk | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | 16.02 |
Component: | Core validator | Version: | latest |
Keywords: | Cc: |
Description (last modified by )
According to the wiki, leisure=park
should not be used on nodes (and ways, only on closed ways). JOSM shows (correctly) the "unknown" icon. But the validator shows no warning or info.
In fact it is used over 55'000 times on nodes. But if you take a closer look at these nodes, you will find typical patterns. I looked around Zürich and found (and fixed):
8 x leisure=park
for mapping a single tree --> natural=tree
(examples: node 3828157717, node 3927588215, node 3927588217, node 3927588213, node 3927588210, node 3927588211)
1 x leisure=park
& name=Spielplatz
--> create new area with leisure=playground
(and without name)
8 x leisure=park
& name=*
inside an area (leisure=park
or landuse=meadow
) without name --> put tags on area
Special during #MapLesotho I found hundreds of single trees mapped with (simple to find with overpass)
leisure=park
leisure=park
&natural=tree
- and my favourite:
leisure=park
&name=tree
If the node has no other tags, I only saw it as mapping for a tree. All I saw are created with ID. I try ID and found the following (misleading) behaviour:
- Start editing with ID.
- Set a new node.
- On the left side appears potential tags. The top key is
park
and the icon shows a tree. - this adds a node with
leisure=park
- Because these "trees" are not rendered, some mappers start to add additional tags like
natural=tree
orname=tree
to get something shown on map.
We should at least warn about using leisure=park
on a node.
We also could offer a fix for replacing the three most used cases (see above) with natural=tree
Last but not least ID shouldn’t offer leisure=park
on nodes! (But instead natural=tree
)
Attachments (0)
Change History (6)
comment:1 by , 9 years ago
Description: | modified (diff) |
---|---|
Summary: | Warn about using leise=park on nodes → Warn about using leisure=park on nodes |
comment:2 by , 9 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:3 by , 9 years ago
Replying to mdk:
If the node has no other tags, I only saw it as mapping for a tree. All I saw are created with ID. I try ID and found the following (misleading) behaviour:
- Start editing with ID.
- Set a new node.
- On the left side appears potential tags. The top key is
park
and the icon shows a tree.- this adds a node with
leisure=park
- Because these "trees" are not rendered, some mappers start to add additional tags like
natural=tree
orname=tree
to get something shown on map.We should at least warn about using
leisure=park
on a node.
We also could offer a fix for replacing the three most used cases (see above) withnatural=tree
Last but not least ID shouldn’t offer
leisure=park
on nodes! (But insteadnatural=tree
)
You should report problems with ID there not here :)
comment:4 by , 9 years ago
Milestone: | → 16.02 |
---|
comment:5 by , 9 years ago
I report this for ID on GitHub (https://github.com/openstreetmap/iD/issues/2974).
comment:6 by , 9 years ago
The issue on GitHub was closed with the comment, that the wiki is wrong at this part. Even if leisure=park
is allowed on nodes (which is reasonable for me) this don't solve the problem, that mappers are using ID in a wrong way. And this is in my oppinion caused by the misleading behavior of the editor.
Can anybody run a query to count
leisure=park
as the only tag on a nodeleisure=park
only together withnatural=tree
on a nodeleisure=park
only together withname=tree
on a node
and perhaps find out the used editors?
By the way, here is an Overpass query which find over 2000 trees mapped as park: http://overpass-turbo.eu/s/efR (see the 20kB XML data)
In 9745/josm: