From OpenStreetMap Wiki
Jump to navigation Jump to search
Public-images-osm logo.svg amenity = parking
P3030027ParkingLot wb.jpg
A place for parking cars Edit or translate this description.
Rendering in OSM Carto
Rendering in OSM Carto area
Area parking.png
Group: Parking
Used on these elements
may be used on nodesshould not be used on waysmay be used on areasshould not be used on relations
Useful combination
See also
Status: de facto

Use amenity=parking to tag a facility used by the public, customers, or other authorised users for parking motor vehicles, such as cars and trucks, commonly known as a car park (British English) or parking lot (American English). See the Parking page for tags specific to parking for other types of vehicles and situations.

How to map

The most common way to map a car park is to draw an area and tag it with amenity=parking. If you are not sure of the actual parking area or don't have time to draw it out then just tag a node node (but never use both a node and an area for the same facility). Different types of car parks are available as a preset in most editors, such as "Parking Lot" or "Multilevel Parking Garage" in iD, and can be accessed via text autocompletion.

Roads and footways should connect to each other within the parking area. A common mistake is to connect roads and footways only to the edge of the amenity=parking area. Routers generally cannot route within an area unless roads and paths are mapped. [1] However, for multi-storey parking garages, it may not be possible to discern the parking aisles from aerial imagery. Connecting the roads to a node for amenity=parking_entrance is a good first step until someone can survey the inside of the garage.

Each parking area feature should be mapped as a contiguous area (see One feature, one OSM element) as much as possible. Include in the area parking aisles and footways between parking spaces. Any greenery such as grass strips or trees can also be included within the parking area. Individual parking rows should not be mapped as separate parking areas. Different parking sections may be mapped as separate parking areas with their respective name or ref=*.

Parking along the side of streets can be tagged with amenity=parking too — using parking=street_side or parking=lane — but a common alternative is to forego mapping the parking areas explicitly with amenity=parking, and to use parking:lane=* on the highway=* itself. Which approach to choose depends on personal preference, local conventions, and the desired level of detail.

You can use tag amenity=parking_space and area:highway=* to map areas covered by parking spaces and carriageways.

Additional tags

Key Default Value Element Comment
amenity N/A parking node area Tag either an area or a central node, but not both.
All sub-tags below are optional.
name None * node area The name of the car park.
ref None * node area
access N/A yes; customers; permissive; private node area Distinction between public car parks, customers car parks (such as at cinemas, etc.), and private car parks (such as for staff in a business park). In this case, yes denotes a public car park.
parking None surface node area A dedicated area for parking consisting of one level of parking on the ground.
multi-storey Two or more levels of parking decks in a building structure. Please consider adding the appropriate building=* tag, if it is purpose-built for this purpose, building=parking is the most popular value.
underground Underground parking.
rooftop One level of a parking deck on top of the building.
sheds Private hangars for vehicles, located close to owner's home. Usually constructed of profiled metal.
carports Structure used to offer limited protection to vehicles, primarily cars, from the elements (Carports on Wikipedia). Please consider adding building=carport.
garage_boxes One level buildings with individual boxes for one car, each, usually made of brick and metal. Usually, this area belong to garage cooperative with own name, chairman, budget, rules, security, etc.
street_side Area suitable or designated for parking, which is directly adjacent to the carriageway of a road (but not on the carriageway; in that case see parking:lane=* or parking=lane) and can be reached directly from the roadway without having to use an access way. parking:lane=* may be used instead if the street-side parking spaces are stretched over a longer section of the road and no micromapping of these areas is desired.
lane Parking on the carriageway, including partially on it. Frequently tagged with parking:lane=* instead.
layby A minimal parking facility alongside a major road where motorists can take a break en-route to their destination.
park_ride None yes; no; bus; train; tram; metro; ferry, etc node area Park and ride. Values of the key define connected means of transport. If unsure, use yes. (see Proposal)
fee no yes; no; interval node area Whether you have to pay a parking fee or not. If the fee must be paid only on certain hours, the same syntax can be used as for opening_hours=*. (See the discussion page.)
supervised no yes; no; interval node area Whether the cars are guarded to prevent car theft and vandalism. If a guard is only present on certain hours, the same syntax can be used as for opening_hours=*.
capacity None number node area The amount of available parking spaces, including all special parking spaces (e.g., disabled). Read talk page on this.
capacity:disabled None yes; no; number node area Defines whether or not dedicated disabled parking spaces are available, usually reserved only for holders of a disabled parking permit ('blue badge' in the UK). If known, the number of spaces can be specified. (replaces the key disabled_spaces=* see proposal).
capacity:parent None yes; no; number node area Defines whether or not dedicated parent and child parking spaces are available. If known, the number of spaces can be specified.
capacity:charging None yes; no; number node area Defines whether or not dedicated parking spaces with charging infrastructure for electric vehicles are available. If known, the number of spaces can be specified.
surface None see key page node area Physical surface of car park.
maxstay None see key page node area Time limit for parking (e.g., customer parking for 2 hours)
opening_hours None see key page node area Opening hours of car park.
operator None * node area Operator of car park.
website None * node area Website of car park.

Related features

Several car park areas, each with one-way aisles

Standard method to draw parking of a complex size - ones that consists of disjointed areas, or because the area consists of multiple disjunct parts, or has holes is to use multipolygons.

Site relation proposal

It has been suggested that the type=site relation can be used with site=parking to group parking spaces and parking entrances together to form one parking facility, as described on Proposed features/parking. Currently however there is almost no support for this among either mappers or data consumers (analysis) - amenity=parking is far more widely used.


The Standard tile layer currently renders the "P" logo and a grey background for parking areas (or the "P" in a building style if the building tag is set).

See also