From 2913d690b85add4f4e651fb52d86f4e38421c7da Mon Sep 17 00:00:00 2001 From: Jeroen Hoek Date: Wed, 24 Nov 2021 19:02:15 +0100 Subject: [PATCH] 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. --- data/presets/amenity/parking_space.json | 4 ---- 1 file changed, 4 deletions(-) diff --git a/data/presets/amenity/parking_space.json b/data/presets/amenity/parking_space.json index a53c9ded..bf9007aa 100644 --- a/data/presets/amenity/parking_space.json +++ b/data/presets/amenity/parking_space.json @@ -12,10 +12,6 @@ "tags": { "amenity": "parking_space" }, - "addTags": { - "amenity": "parking_space", - "capacity": "1" - }, "terms": [ "parking spot", "parking stall"