usually, the purpose of visiting a playground is to, um, visit the playground.
The purpose of a play area is (AFIK) a place to deposit the kids while (one of) the adults do something else, or as a amenity to a more serious or boring place place where the kids can have their attention taken away. I know there is a place like this in large facilities that have groups of parents who need to park or placate a kid for a while (while adults rest or eat), so knowing where the amenity is sounds good. Some of them are supervised by the employees, so the parents can shop (like ikea does), though I don’t know if that’s considered daycare or babysitting or whatever. And whoever suggested the kindergarten tag, I hope they were being sarcastic. If there was a new amenity tag, and the data customers ignored it, we wouldn’t be losing any kindergartens or playgrounds, so that’s a good thing, right? I don’t want playgrounds or kindergartens popping up in what turns out to be a corner of the mall filled with bright vinyl cubes and a loop of Pokemon playing on a TV. Javbw > On Dec 18, 2014, at 6:41 AM, Andreas Goss <[email protected]> wrote: > >> I don't see a need for a new key here. >> The properties can be easily modelled with sub-tagging of playground: >> >> leisure=playground >> playground:supervised=yes/no >> playground:outdoor=yes/no >> playground:indoor=yes/no > > I agree in general, but the main issue with tagging like this is that I bet > most data consumers will just look for leisure=playground and that's it. > __________ > openstreetmap.org/user/AndiG88 > wiki.openstreetmap.org/wiki/User:AndiG88 > > > _______________________________________________ > Tagging mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/tagging _______________________________________________ Tagging mailing list [email protected] https://lists.openstreetmap.org/listinfo/tagging
