[Tagging] water parks and swimming pools

[Martin Vonwald]

Hi!

2013/1/15 Ronnie Soak <chaoschaos0909 at googlemail.com>:
> Best solution I could come up with: tag the whole thing as
> leisure=water_park [1] (even if it is not that fancy as in the wiki
> definition), tag the water features as leisure=swimming_pool[2](even if you
> can't swim in some) and sport=swimming for those you actually can (e.g. not
> for the childrens basin).

I agree with you there.

> (I may also add landuse=basin, but this may be overkill.)

I don't think it's overkill I think it's wrong. Although a swimming
pool is "An area of land artificially graded to hold water." it
doesn't feel right. Have a look at the subkey "basin" and its values.


> Tag the playing fields as e.g. leisure=pitch, sport=volleyball,
> surface=sand,
> further features as amenity = playground, amenity=showers, amenity=toilets,
> amenity=fast_food etc, mostly attached to a building=yes if appropriate.
> The green around would be a leisure=park, landcover=grass.

Hm... is leisure=park really useful/correct here. You already tagged
the whole area with leisure=water_park and in my understanding this
means that everything that's not tagged as a specific feature or
building is green.


> Now the question is where to put the name, opening_hours etc. I did put it
> on the leisure=water_park border, because it is the overall thing. I briefly
> toyed with the idea to create a site relation with all those things inside
> and place it there, but then I realized that in a spatial database, there is
> no need to artifically group things based on their position inside a
> boundary. You can do a 'is in?' query to such a database.

Fully agree. Especially about the site-relation - we don't need that here.


> So, can we discuss if this is a good approach or what can be made better and
> then document that in the wiki? At the moment, there are various examples on
> how to tag single-building swimming pools but bigger places are not
> mentioned.

I think the best place for some additional documentation would be the
article about leisure=water_park. We should add there a list of
related features with examples and links to the keys.


> Worst I've seen in the wild was a leisure=swimming_pool on a multipolygon
> cutting out the actual water areas. wtf?

Call it creativity ;-)


regards,
Martin