This is clearly a park. It was marked as such over 4 years ago (in 2013). However, the following query, when done with said park in view, does not highlight it:
Is there any reason for that? It seems that asked 25 Apr '18, 09:54 moriakaice |
One Answer:
Hello, In your Overpass query you are searching for way with leisure=park tag, but the park you have linked is not a way it's a relation, a multipolygon type relation used to describe a complex area. You should add relation to your Overpass query by adding answered 25 Apr '18, 10:05 Kazing showing 5 of 7 show 2 more comments |
Thank you for the answer.
What does make an area a
relation
and not away
? We've got other parks (like Hyde Park) that areways
.The relation is used when the area you want to describe is complex, it has holes for examples. See the wiki page for more details/examples https://wiki.openstreetmap.org/wiki/Relation:multipolygon
For Brockwell Park I don't see why it is describe with a relation, but i'm not an expert of multipolygon. And there is nothing that forbids using multipolygon if you think it's more convenient.
So on the page you've provided, the examples are having both way and relation, while Brockwell Park seems to be only having a relation, which is very strange for me and, if possible, I'd love to have a
way
there as well.The Brockwell Park, also have ways, the ways are all included in the relation that describe the park area, ways can have the role of "outer" perimeter or "inner" perimeter See this way, it describes a part of the park's external perimeter and its included inside the multipolygon relation: https://www.openstreetmap.org/way/232229963#map=17/51.44733/-0.10696
Thanks for pointing it out. Does it mean that, due to the fact those are not marked with
leisure=park
, the whole thing doesn't get highlighted with my original filter?Would recreating it/adding appropriate tags fix the problem?
No, there is no problem in the data. The tags belong on the multipolygon and not on the individual ways (see the first point at multipolygon#Usage). Otherwise you are creating an old-style multipolygon which has lead to several problems in the past and should be avoided. You have to fix your query, not the data.
That's a shame. The query itself was rev-eng to cover for what Niantic, developer of Pokemon GO, is likely using for one of the in-game features. Not sure how exactly the data-mining was done to establish the query, but it's sad that only some parks that are marked in OSM will enjoy the feature, while others will miss it (Hyde Park vs Brockwell Park).