Talk:Key:playground

From OpenStreetMap Wiki
Jump to: navigation, search

The sensory tags lack parallelism. If we use visual and tactile, I believe we should use auditory and olfactory. 'Audible' would be more similar to 'visible' and 'touchable' and likewise 'smell' would be consistent with 'sight' and 'touch'. I think the values should be:

Thoughts? Scottyc 20:29, 19 August 2011 (BST)


Missing equipment

I find I'm missing the following equipment while trying to tag a newly developed playground:

playground=platform (covered=yes)

playground=climbing_pole (or beam)

playground=excavator (metal contraption with seat and two levers that move a sort of shovel)

playground=tree_house (they built as very beautiful tree house around a tree that was already there)

playground=firefighter_pole (height 5m, not for the faint of heart :-)

playground=chain_ladder

playground=climbing_rope

playground=hammock

playground=tunnel_tube

playground=peak (small hill, often artificial)

There is some artwork (wooden animals) on the Weleda style equipment. It's the first thing the 1,5 year old noticed. Does it make sense to mention them?

Yes, an artificial hill for climbing is common on almost all Japanese playgrounds. Sometimes it is dirt, grass, or covered in concrete with stones embedded for climbing, but it is certainly not something I'd like to tag with a "peak" tag - it is clearly a "peice of equipment" for the playground. Also, if you feel it is necessary, you can tag the artwork with the artwork tag in some fashion. Javbw (talk) 08:44, 19 February 2015 (UTC)
The extra values can of course be used, though the preference in the existing definitions and usage pattern is to avoid the underscore '_' character. I agree that hill is better than peak in this situation. The firefighter thing is a bit ambiguous, is that a pole to climb up or a vertical bar to slide down? --Polarbear w (talk) 10:16, 17 August 2015 (UTC)

Is there a less military but good picture for a climbing rope? US Navy 110714-N-OA833-003 Plebes in the U.S. Naval Academy Class of 2015 receive rope climbing instruction at the school's obstacle course.jpg

Multi-Purpose Equipment

playground:swing=yes style tagging (similar to recycling:*=yes) would have better allowed to cover multipurpose equipment such as climbingframe that includes slides (or possibly even more verbose playground:equipment:swing=yes). In addition, that would have made it reasonable to include all equipment available to the playground object if the physical positions of the equipment are not individually mapped for some reason (now it would require rather long semicoloned value). --Ij (talk) 13:29, 19 December 2014 (UTC)

The multipurpose device has meanwhile been identified as playground=structure, which can have further devices attached. While I agree that the playground:swing=yes style would have been better when introduced, the current practise of micromapping shows that having nodes for individual devices is now common practice, with only a few summary tags on whole grounds showing up in taginfo. --Polarbear w (talk) 10:09, 17 August 2015 (UTC)

Deprecating playground=zipwire in favor of aerialway=zip_line

I am proposing to deprecate playground=zipwire for the reasons specified here: Proposed_feature/aerialway=zip_line#Reasons_for_deprecating_playground=zipwire RicoZ (talk) 23:20, 17 February 2015 (UTC)

material=rope

"Rope" is not a material. A "rope" itself consists of material like metal (wire rope), nature fiber or synthetic fiber. The latter is probably the most usual kind for spider web climbing frames. MarkusHD (talk) 07:26, 17 August 2015 (UTC)

"Material" can have different definitions. The meaning can range from the matter over constituent or component to necessities for a task. In this sense I would not see a need to limit the definition to the chemical compound, and rather prefer to name the real-world categories used in equipment construction. For example for climbing frames, I observe a transition from stiff bars to soft ropes, since the latter are soft when fallen on and the head is less likely to get stuck in a gap. If you prefer to specify the matter in a chemical sense, you can of course introduce a sub-tag, such as rope=polyamide (Nylon) or rope=hemp. --Polarbear w (talk) 09:57, 17 August 2015 (UTC)
On the one hand this is pretty detailled mapping, on the other hand this might be inaccurate usage or misuse of the "material" key. That doesn't fit together. I see it the other way around: "rope" (as well as stiff bars) should be a value of another key, something like "composition". I understand your intention, but don't agree with your conclusion. But I don't want to bikeshed. MarkusHD (talk) 10:50, 17 August 2015 (UTC)
For being used 300000 times, of which 50% are wood, the material=* key itself has a very poor definition in the wiki, thus it has accumulated a wide mixture of values. However rope is being used only 7 times so far, thus if you have a better idea for the typical distinction in the playground situation you are welcome.

Springy

playground=springy originally defines "a seat on a helical spring", also known as Spring Riders. The problem with the tag is firstly, "springy" is in the dictionaries only as an adjective, describing the property of a spring, and rarely used as a noun. Secondly, there are other bouncing devices that use a spring that is not necessarily helical, such as the example below, or spring platforms, i.e. a board supported by several helical springs.

Sprungwippe Oberderdingen Hinter dem Hof.jpg

Question is, should we widen the definition of playground=springy, which keeps the currently tagged 920 devices included, or should we find more precise definitions for the different devices, potentially retagging the existing springies. --Polarbear w (talk) 11:03, 16 October 2015 (UTC)

We should definitely be able to distinguish these different kind of spring-based devices because you can use them in completely different ways. I find it similar to the differentiation between swing and basket_swing or even roundabout and aerialrotator. MarkusHD (talk) 07:19, 20 October 2015 (UTC)