Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't suggest capacity for amenity=parking_space #278

Merged
merged 1 commit into from
Nov 24, 2021

Commits on Nov 24, 2021

  1. 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.
    jdhoek committed Nov 24, 2021
    Configuration menu
    Copy the full SHA
    2913d69 View commit details
    Browse the repository at this point in the history