`amenity=youth_centre` -> `amenity=community_centre` + `community_centre=youth_centre`
`community_centre:for` specifies actually rather a property of a community centre/youth centre, while `community_centre` specifies the type of community centre, i.e. is part of the map feature. See PR #83
* Add capacity:* tags for tourism=camp_site.
* Use capacity:caravans for tourism=caravan_site.
* Use distinct capacity tags for tourism=camp_site.
* upgrade capacity fields to regular fields
Co-authored-by: Martin Raifer <martin@raifer.tech>
* Added a preset for amenity=ticket_validator
amenity=ticket_validator (https://wiki.openstreetmap.org/wiki/Tag%3Aamenity%3Dticket_validator) has increased by over 2300 uses by this time, but it din't have a preset yet. I did not open an issue for that, but I can if necessary. So as the usage for this tag seems very clear to me, I thought it would be worth adding preset for it. I used the icon from vending_machine, maybe when you're not okay with it, you can remove it. I hope everything fits.
* Added some terms to amenity=ticket_validator preset
* added aliases to amenity=ticket_validator preset
* Add fields to building=construction preset
Add opening_date and check_date fields to the building=construction preset
* Fixed commas
* Add "construction" field
* add preset and icon for signal controlled pedestrian crossings (crossings with traffic lights)
Co-authored-by: Martin Koppenhöfer <martin@23maps.it>
Co-authored-by: Minh Nguyễn <mxn@1ec5.org>
* add highchair field to cafe,fast_food,restaurant
* Update data/fields/highchair.json
Co-authored-by: Martin Raifer <martin@raifer.tech>
* Rename highchair.json to high_chair.json
* Rename high_chair.json to highchair.json
* remove fields which don't do anything for type=check
Co-authored-by: Martin Raifer <martin@raifer.tech>
With `amenity=parking_space` it is possible to map separate parking
spaces in a parking area. It can be used with `capacity` in case the
space is used for more than one vehicle, but this is an exception. By
default, `capacity=1` is implied, and many mappers omit the capacity tag
when its value would be `1`, only using it when it deviates from the
default.
By suggesting adding `capacity=1` to parking spaces lacking the capacity
tag, the editor stimulates adding a tag which is not needed in the vast
majority of the cases, and novice users make edits containing many
of these changes where they are not needed. I find that this sugggestion
is causing more noise than useful contributions.
Canada and the United States generally post only an advisory speed limit and avoid posting a legal speed limit on highway ramps. Other countries differ. This change splits the maxspeed field into two as a workaround for the inability to limit the default inclusion of a field to a particular location set.
