Key:baby
Jump to navigation
Jump to search
 baby
|
 |
| Description |
|---|
Specifies whether an item, such as a playground, is baby-friendly. 
|
| Group: leisure |
| Used on these elements |
    |
| Useful combination |
| Status: in use |
| Tools for this tag |
|
Tag that specifies whether an item is baby-friendly, such as a Key:playground.
Examples
| Usage with Tag | Comment | Photo |
|---|---|---|
| playground=swing | Baby swings are swings with a bucket shape with holes for the child's legs, or a half-bucket shape and a safety belt, that is intended to reduce the likelihood of a very young child from falling out. |  |
Possible issues
It has been noted (e.g. SC#3174) that while usage of baby=no is clear; usage of baby=yes is ambiguous. For examples, if there is playground=swing + baby=yes mapped, does that mean that the only swings available are for babies (i.e. none of the swings are usable for older children), or does it mean that only some of the swings available are designated for babies?
Proposed solutions (see this community forum discussion for details):
- instead tag as playground=baby_swing (most popular choice)
- instead of using playground=swing + baby=yes, tag playground=swing + capacity=* + capacity:baby=*, thus resolving the ambiguity.
- some people have also used baby=only, but that only helps the case when there are only baby swings available; while more popular baby=yes still remain ambiguous (it might be that the mapper knew of that originally documented value and the only swings available are for babies, or it might be that the mapper checked and wants to indicate that there are mixed baby and non-baby swings, There is no way to know with currently documented tagging)
- Another solution for a duo swing with one baby seat: capacity=2, baby=1