* Readme: Expand translations section
Readme: Add section about how translations work
Closes https://github.com/openstreetmap/id-tagging-schema/issues/55
Readme: Improve section about translations
- Change the order of the bullets to clarify which goes where.
- Update the primary Transifex link based on feedback in https://github.com/openstreetmap/id-tagging-schema/pull/245#discussion_r741621759
- Add a section about how to find a translation in Transifex
* fix typo and bind to specific version
Co-authored-by: Minh Nguyễn <mxn@1ec5.org>
* tweak wording very slightly
Co-authored-by: Martin Raifer <martin@raifer.tech>
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.
