Proposal:More Parking Spaces

The proposal More Parking Spaces was built without a vote and the tagging is widely established based on this proposal. The Feature Page for the proposal More Parking Spaces is located at Key:capacity:disabled.

The proposal More Parking Spaces was built without a vote and the tagging is widely established based on this proposal. The Feature Page for the proposal More Parking Spaces is located at Key:capacity:women.

The proposal More Parking Spaces was built without a vote and the tagging is widely established based on this proposal. The Feature Page for the proposal More Parking Spaces is located at Key:capacity:*.

More Parking Spaces
Proposal status:	Inactive (inactive)
Proposed by:	Lulu-Ann
Tagging:	capacity:*=yes capacity:*=no capacity:*=<number>
Applies to:
Definition:	There are more kinds of parking spaces than standard and disabled, this proposal addresses this problem!
Statistics:
Rendered as:	?
Draft started:	2009-07-31
RFC start:	Request For Comments, Not Set
Vote start:	Vote Date, Not Set
Vote end:	Vote Date, Not Set

There are more kinds of parking spaces than standard and disabled. These keys shall be used with amenity=parking:

• capacity:standard=yes/no/number (use this instead of "capacity", which includes all other types)
• capacity:disabled=yes/no/number (This replaces the already established disabled_spaces=yes/no/number)
• capacity:women=yes/no/number
• capacity:parent=yes/no/number for parent(s) with children (near entrances of supermarkets)
• capacity:short=yes/no/number for "smart" cars
• capacity:long=yes/no/number for long cars or cars with trailers
• capacity:hgv=yes/no/number for heavy goods vehicles (long and wide)
• capacity:bus=yes/no/number for busses and coaches
• capacity:motorcycle=yes/no/number
• capacity:horse=yes/no/number
• capacity:carriage=yes/no/number
• capacity:private=yes/no/number for private owners
• …

about the replacement of disabled_spaces=yes/no/number

• disabled_spaces=yes/no/number shall be replaced by capacity:disabled=yes/no/number

This shall be realized in several steps:

1. this proposal gets approved
2. a bot will add the new tag to all occurances of the old one, overtaking the value.
3. the bot will also add a note text "The tag disabled_spaces is no longer used, please use capacity:disabled instead in the future. The old tag will probably be removed automatically after (date 6 months in the future)." This will give developers a reasonable time to change their applications.
4. There will be another proposal 6 month later to delete the old tags with a bot, which will be checked with tagwatch and hopefully be approved.

How to map

• Map a node, a way (along a street) or an area with amenity=parking.
• Add the keys.

Note: It is new that you can use amenity=parking on a way. This is already often used if you are parking along a highway.

Rendering

^{[ dead link ]}

^{[ dead link ]}

^{[ dead link ]}

^{[ dead link ]}