Hi everyone, I am new to the forum. This is not an official proposal because I know that is a more complicated process, I just want to hear some other opinions about this topic.
Current splash pad tagging:
The current way to tag splash pads, as described in the wiki, is tagging an object with playground=splash_pad within a leisure=playground area.
Why I think this isn’t ideal:
Splash pads are usually distinct elements that I would not consider to be part of the playground. Therefore I do not think it makes sense to have them wrapped within a leisure=playground area. The other playground= tags are for small elements within a playground, for example slides and swings. These elements describe individual objects that can’t be mapped in more detail, which is not the case for splash pads, which contain many smaller elements that could be micromapped. Taginfo reflects this, showing that most splash pads are mapped as ways, which is not typical for other playground= tags which are mostly mapped as nodes. The only two exceptions to this which I found are sand boxes and zip lines, both of which I’d still consider individual playground features. This is in contrast to splash pads, which are not individual playground features, they are distinct areas that contain their own splash pad features.
For those reasons, I think that splash_pad does not really fit in with the other playground= objects.
What I propose:
Use leisure=playground to map playground areas, and playground=* to map individual features within the playground (nothing changes).
Use leisure=splash_pad to map splash pad areas, and splash_pad=* to map individual features within the splash pad. The splash_pad= tags would require some more thought, but just for example, here are some potential ideas: ground_jet, dump_bucket, mist_arch
playground=splash_pad should be deprecated but no automated edits should take place, existing objects (3800) can be handled over time on a case by case basis.
That’s not the only way to tag a splash pad, that’s just a way to tag a splash pad that’s part of a bigger playground.
It’s also fine to tag one object (preferably an area) with leisure=playground and playground=splash_pad, which descriptively tells that it’s a playground and specifically a splash pad playground.
I recommended this kind of tagging on the wiki page for Canadian tagging guidelines in November 2019, no one’s really objected since. It would not occur to me to limit splash pad tagging to being within a separate leisure=playground area…
Thanks, you are correct, I did not read the second line of the wiki page:
“If a play equipment takes up the whole space of the playground’s area leisure=playground, then tag it on the playground area itself with this key.”
How I have mapped splash pads in the past is just with the playground=splash_pad tag, no leisure=playground on the object or surrounding the object. This is what happens when you make a splash pad in iD. Me writing this was sparked by noticing that none of my splash pads were being rendered. If the consensus is that my idea is bad, I would suggest that when you make a splash pad in iD, the default tagging should include leisure=playground on the object.
At first glance this sounds fine to me. I’ve mapped other standalone pieces of play equipment the same way (e.g. a swing set that isn’t part of a larger playground).
Perhaps the real problem here is just a lack of support in renderers for splash pads? Dual tagging them all with leisure=playground will get them displayed of course (as generic playgrounds?), but feels a bit like “tagging for the renderer”.
All the wiki says describing splash pads (Tag:playground=splash_pad - OpenStreetMap Wiki) is “Area with ground nozzles or other water features that spray water upwards out of the splash pad’s raindeck”, so no buckets or water guns necessary. I’ve definitely been tagging simple splash pads that just have water jets and no toys as bare playground=splash_pad, no further tags needed. I don’t see a strong need for a change to the tagging, playground is well established as a top-level tag even for objects that aren’t within a leisure=playground area. And I’ve often seen splash pads within playgrounds in areas I’m familiar with.
I was referring to Martin’s reference to fountain=splash_pad
I guess a playground=splash_pad and a fountain=splash_pad can look similar in terms of what water features they have.
The distinction I would draw between them is more in terms of urban context. A fountain=splash_pad would usually be part of a public square or another notable public space, and the water jets serve to cool off, to look nice, perhaps to help clean the air, and can be used to play. A playground=splash_pad’s primary purpose is for play, and it would usually be located near residential areas or in parks. I would usually not expect to see adults not accompanying children at a playground=splash_pad, especially during daytime.
I’m sure there’s edge cases but they’re probably few.
Maybe the wiki should be updated to say this? I’ve also mapped swings that aren’t part of playgrounds that way, and it makes sense that not everything will be part of a playground. I do think playground=splash_pad on its own makes more sense than adding leisure=playground as well.
I think you are right about it just being a lack of support from renderers. Looking at taginfo, none of the services I use use the playground=splash_pad tag, so you are right that they would just be displayed as normal playgrounds. I was surprised by how few splash pads are on the map so I guess it makes sense that not many peolpe have put in the effort to render them.
I don’t have any pictures, but I guess it is just a difference of opinion because I would not consider the picture you sent to be a playground.
Where I live, splash pads are usually fenced off in their own separate area away from the playground, so I don’t consider them to be part of the playground. I guess it is similar to how I wouldn’t consider an outdoor fitness station or a pool to be part of a playground.
Here are some splash pads near me so you can see what I mean when I say they are separate areas:
