|Using this tag is discouraged, use Street parking instead.|
|Used on these elements|
|Tools for this tag|
The reason is documented in Deprecated features. You are still free to continue to use or interpret this tag as you see fit since OpenStreetMap does not have “banned features”.
Under no circumstances should you (semi-)automatically change “deprecated” tags to something else in the database on a large scale without conforming to the automated edits code of conduct. Any such change will be reverted.
This page documents the usage of the key parking:lane=* to indicate the physical presence of a parking lane. It can be added to ways tagged with highway=*.
- parking:lane=* is used to express the allowed type or position of parking. Parallel, perpendicular, and diagonal are examples of types of street parking. On-street, on-kerb, and street side are examples of positions of street parking.
- parking:condition=*, a similar but different tag, is used to describe the legal properties of the parking space. You can use this to tag who can park somewhere (residents, customers, etc.), when they can park, how long they can park, and more.
Both can be used independently of each other, they do not necessarily require the other.
- The key parking:lane=* should always be used with the appended subtags :both, :left, or :right; indicating the side of the street they apply to.
- The roadway needs to be split up where any of the parking type, position or condition changes. For example, when parallel parking is available only alongside the first third of a way between two intersections.
Parking adjacent to the carriageway (parking:lane:side:type=street_side) can alternatively be mapped as areas with amenity=parking and parking=street_side. Especially in places where the parking situation is very diverse, this can actually be easier to do and easier to maintain than to split the roadway into many small segments just to accommodate for the different parameters that change down the road.
it is assumed that way is pointing like vehicles, toward us
it is assumed that way is pointing like vehicles, toward us
There are more pictures of different roads and how to tag them in Key:parking:lane/Examples.
The parking:lane tag is used to describe the physical properties of the parking (essentially, the orientation) – in other words the types of street parking (and optionally the parking position).
Please note that this tag only describes the space properties, not the actual condition. A parking:condition tag is required in those cases.
The type of parking can be tagged with the key parking:lane:side. If there is no parking lane, it is also directly specified as a value.
- side is one of the values both, left or right.
- So following keys will be used:
- Known values for this keys are:
|parking:lane:side||parallel||There is parking space. Vehicles must park parallel to the road.|
|diagonal||There is parking space. Vehicles must park diagonally. Also known as angle parking or echelon parking.|
|perpendicular||There is parking space. Vehicles must park at a 90° angle so that the front or back of the vehicle is pointing straight towards the road centre line.|
|marked||There is parking space, with only some parking spaces available that are individually marked.
If it is just parallel, diagonal or perpendicular parking with marked parking spaces, use these values instead. marked should only be used in exceptional cases, as this value is less meaningful and cannot be usefully evaluated. Alternatively, consider mapping the parking spaces as separate areas (with amenity=parking + parking=lane or parking=street_side).
Note that there is an obvious overlap with parking:lane:side:type=painted_area_only (see below). As opposed to this tag, the latter allows to also specify the orientation.
|no||There is no parking space.|
|yes||There is some type of parking space. If possible, be more specific.|
|separate||Parking facilities are mapped explicitly as another object (usually with parking=street_side).|
|Deprecated. Use parking:condition|
Sometimes the parking on the street is allowed at the edge of the driving lane, at other times there is a painted, dedicated strip at the edge of the road, and sometimes one must park on the high side of the kerb stone.
This can be tagged with the key parking:lane:side:type.
- side is one of the values both, left or right.
- type takes values of parallel, diagonal or perpendicular, as applicable.
- Known values for this key are:
|on_street||Parking on the street, which could be easily converted to a travel lane.||In use|
|half_on_kerb||Partially on sidewalk.||In use|
|on_kerb||On sidewalk.||The left side of||In use|
|street_side||Parking only in parking bays adjacent to the carriageway, which could not easily be converted into a travel lane.
Parking bays, also known as lay-bys, are areas dedicated to parking directly adjacent to the carriageway. Often but not always they are clearly offset from the rest of the carriageway; e.g., using different paving and marked individual spaces. See parking=street_side for more details.
|In the past often used for street-side parking (see above), but ambiguous because lay-by is also the term used for rest areas (see rest areas on Wikipedia). Thus, the newer tag value street_side should be used instead. In case you really want to map a lay-by rest area, consider using layby (without underscore), which is consistent to amenity=parking + parking=layby.||Deprecated|
|painted_area_only||Parking only in marked areas on the street.
If it is just e.g. on_street or street_side parking with marked parking spaces, use the other values instead. painted_area_only should only be used in exceptional cases, as this value is less meaningful and cannot be usefully evaluated. Alternatively, consider mapping the parking spaces as separate areas (with amenity=parking + parking=lane or parking=street_side).
Note that there is an obvious overlap with parking:lane:side=marked. Using this tag instead allows to also specify the orientation (parallel, diagonal or perpendicular).
|shoulder||Shoulders are hard sections of the road area not normally meant to be driven on, they can be of the same surface as the way or of a degraded or use-graded surface; requires shoulder=yes|left|right|both||In use|
Distinguishing between on_street and street_side
In many places, it is common to extend the kerb at intersections and crossings to slow down traffic and make it safer to cross for pedestrians. This is tagged as a traffic_calming=choker, it does not make an
on_street parking of an entire street into a
street_side parking. When there are many chokers in one street, it may become a little hard to distinguish between these two situations in reality.
As a rule of thumb, if the parking cars are on the part of the road that is traversable (i.e. that could and would otherwise be used by traffic) it is parking
on_street. If not, it is parking
Whatever tag value you decide to use in ambiguous situations, it is important to update width=* (or width:carriageway=*) accordingly if it is set because the definitions for those are tied together: The width=* includes the space for
on_street parking but excludes the space for
street_side parking because the latter count as adjacent to, not on the carriageway.
- parking:lane:both=parallel: both on the left and right hand side parallel parking is possible.
- parking:lane:both:parallel=half_on_kerb: both on the left and right hand side parallel parking is possible, and the parking position is half on kerb (partially on the sidewalk).
- parking:lane:right=perpendicular: on the right hand side you can park perpendicularly.
- parking:lane:both=marked: there are only some parking spaces available that are individually marked.
- parking:lane:both=no: there is no parking lane.
Specifying the maximum capacity for a given stretch of parking (especially for parking:lane:side=perpendicular). For parking along the street, this can usually be estimated automatically quite accurately. However, if parking is only possible in dedicated spaces (
painted_area_only), to add such information is potentially more useful.
These taginfo statistics are not representative of all uses of parking:lane=* or parking:condition=* since they do not account for all possible subtags (e.g. parking:lane:right:parallel=*, etc.).
Notes on evaluating data
Data consumers that require precise spatial data on street parking should consider that depending on the local legislation, implicit parking restrictions may exist that are not explicitly tagged with parking:lane=* etc., so some spatial post-processing may be required. For example, in most legislations throughout the world, parking is prohibited on and about 5 metres around intersections and crossings. Yet, few mappers bother to split up the road the first and last 5 metres of every road to map a no-stopping prohibition. In fact, some even deprecate this practice, as such restrictions are implicit or common sense.
Because parking adjacent to the carriageway can also be mapped as areas, some spatial post-processing may be required anyway. In the case above, some possible parking spaces would need to be cut out around the intersection.
Here is a not necessarily complete list of situations that imply a parking restriction which can be found in many legislations and may not come with explicit tagging:
- on motorways and motorroads
- in pedestrian zones, throughflow and parking is forbidden but there may be exceptions for delivery vehicles
- in living streets, parking is usually only allowed in explicitly marked areas
- in some legislations generally on bridges and in tunnels
- often priority roads (at least rural ones) and often on roads where overtaking is forbidden; i.e., where there is a continuous centre line
- in roundabouts and circular junctions (junction=roundabout, junction=circular should appear on road line in such cases)
- usually in turning circles and turning loops
- on sections of the roadway marked with arrows, i.e. turn lanes - though often only on side where turn lanes are present
- in front of certain important signs such as the stop sign, saltires or yield traffic because obscuring these signs is dangerous
- at taxi stands and bus stops parking is prohibited. Depending on the legislation, stopping or standing may be allowed
- on and near pedestrian crossings, railway crossings, on tram tracks, etc. stopping is prohibited for obvious reasons. Some legislations allow at least stopping around (not on) crossings.
- at narrow points, sharp bends, fire rescue paths and other places where parking would put the parking car or other traffic in danger
- at entries to driveways and other places where there is a dropped kerb
- in some legislations also in front of police stations, post offices and hospitals
Most of this is common sense, but software does not know common sense. Also, some of these implicit restrictions may in some countries actually be explicitly signed.
Using with JOSM
To use these tags correctly, it helps to have visual feedback and contextual tagging assistance available in JOSM. Use of a Map Paint Style and Tagging Presets is highly recommended.
Map Paint style
There is a map paint style available called Parking lanes (or possibly a translation of this in the language you use JOSM with). It can be installed via JOSM's Map Paint preferences.
There is also a set of tagging presets available under the same name. These can be installed via JOSM's Tagging Presets preferences.
- Parking ticket vending machines
- amenity=vending_machine + vending=parking_tickets
Possible tagging mistakes
- parking=lane - Parking on the carriageway, including partially on it
- Parking Map for rendering and how the data is visualised
- ↑ It is intentional to use left and right instead of forward and backward, because parking space is about location, not direction. E.g., a one-way sometimes has parking space at the left and at the right hand side, but no "backward" parking. See Forward & backward, left & right.