Tag:amenity=parking_entrance
 amenity = parking_entrance
|
 |
| Description |
|---|
A entrance to an underground or multi storey parking facility 
|
| Rendering in OSM Carto |
|
| Group: Parking |
| Used on these elements |
    |
| Useful combination |
|
| See also |
Status: approved
|
| Tools for this tag |
|
Use amenity=parking_entrance to map a single parking entrance (and/or exit). Group one or more of such entrances into a site relation representing a single underground or multi storey parking facility, as described below.
How to map
Add a node and tag with amenity=parking_entrance
- A parking entrance always has to be mapped as a node.
- The differentiation between different kind of entrances for different kind of transportation modes (car, foot, …) is defined by setting the correct access tags (access=*).
- If appropriate, the tag can be combined with entrance=*. The tag building=entrance is deprecated.
- Parking entrances should always be connected to a highway, often highway=service, and never be mapped isolated.
- The distinction between entrances which function as exits, entrances or both is defined by the oneway=* tag of the highway=* connected to the parking_entrance node.
- amenity=parking_entrance is normally used for underground or multi storey parking entrances, not for surface parking. Add parking=underground or parking=multi-storey.
While underground or multi-storey parking facilities can also be mapped as an area using amenity=parking in combination with location=*, it’s also helpful to map the entrances and exits as nodes.
Additional tags
| Key | Value | Comment | |
|---|---|---|---|
| required | amenity | parking_entrance | Mandatory tag for defining a parking entrance. |
| recommended | parking | underground multi-storey |
If it is an underground car park. Rendering in openstreetmap-carto: If it is a multi-storey. Rendering in openstreetmap-carto: 
|
| optional | ref | String | Internal reference number or alphanumberic code used by the operator of the parking entrance, e.g "2C") |
| optional | name | String | Commonly used name of the entrance. Examples: Main entrance Big Underground Parking, Side Exit 3rd Avenue |
| optional | maxheight | String | Signposted maximum vehicle height permitted to use the entrance. |
| optional | general tags | * | See chapter General tags in the proposal for tags that can be applied to spaces, entrances and relations. |
Optional relation
- More than one entrance might be grouped into a single parking facility by using a site relation. See example below and Relation:site for details.
- The relation would use the tags type=site + site=parking.
- If a amenity=parking_entrance node is added as a member of a site relation, the role entrance can be used, optionally.
- However, note that this type of relation is not yet supported by many database users.
Access restrictions
For a much more detailed explanation of the new scheme using amenity=parking_space, amenity=parking_entrance and site relations, please read the proposal. You will also find information on how to tag access restrictions for certain kind of user roles (parent parking, disabled parking).
Rendering
underground
multi-storey