Jeroen Hoek 2913d690b8 Don't suggest capacity for amenity=parking_space ... 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.		2021-11-24 19:02:15 +01:00
..
fields	Add Via field to route relations (re: #104)	2021-01-05 10:18:33 -05:00
preset_categories	Add Playground Equipment preset category (close #56)	2020-12-01 15:00:28 -05:00
presets	Don't suggest capacity for amenity=parking_space	2021-11-24 19:02:15 +01:00
deprecated.json	Don't flag highway=no since people might use it intentionally (close #105)	2021-01-05 11:08:41 -05:00
discarded.json	Treat converted_by as discardable	2021-01-26 17:18:16 +01:00
preset_defaults.json	Initial commit	2020-11-05 11:30:34 -05:00