Tag:parking=street_side

parking = street_side
Description
Area suitable or designated for parking which is directly adjacent to the carriageway of a road and can be reached directly from the roadway without having to use an access way.
Rendering in OSM Carto
Group: parking
Used on these elements
Requires
amenity=parking — or — amenity=motorcycle_parking
Useful combination
orientation=* surface=* access=* fee=* maxstay=* restriction=*
See also
Street parking
Status: approved
parking=street_side $1% $1% $1% $1% More details at taginfo
Tools for this tag
taginfo · AD · AT · BR · BY · CH · CN · CZ · DE · DK · FI · FR · GB · GR · HU · IN · IR · IT · LI · LU · JP · KP · KR · NL · PL · PT · RU · ES · AR · MX · CO · BO · CL · EC · PY · PE · UY · VE · TW · UA · US · VN overpass-turbo Sophox OSM Tag History

Area suitable or designated for parking which is directly adjacent to the carriageway of a road — either single parking areas (often only for a few vehicles) or chains of "bays" or "pockets" alongside the roadway which, in contrast to parking lanes, are structurally designed and therefore regularly interrupted by structural elements like curb extensions or islands for street furniture. In contrast to parking=surface, these parking spaces are accessed directly from the street without having to use an access/service road or driveway.

Typical street-side parking areas (highlighted) with different orientations (parallel, perpendicular and diagonal).

Tagging

Street-side parking areas can be drawn as separate areas using amenity=parking (or amenity=motorcycle_parking) + parking=street_side. Consider using the street parking scheme on the highway=* line as a simple alternative if the streetside parking spaces are stretched over a longer section of the road and no micromapping of these areas is desired. The separate variant is particularly suitable in areas where the road space is already mapped in great detail, or if there is only a single (small) street side parking area.

If possible, add the following information in case of separately drawn parking areas:

• parking:side=separate should be added to the highway to indicate that the parking information is already mapped separately on the given side (left, right or both, see examples).
• The key orientation=* with the values parallel, diagonal or perpendicular can be used additionally on the separately drawn parking areas to indicate the orientation of the parked vehicles in relation to the street.
• It is useful to provide other common information (if identifiable) such as capacity=*, capacity:disabled=*, or surface=*.
• Parking restrictions can be mapped by using fee=*, maxstay=*, access restrictions or restriction=*. See the street parking page for informations about mapping parking restrictions.
• Same as with parking=surface, separate parking places can be drawn in and tagged with amenity=parking_space, but this is optional (Note: Do not use parking=street_side on these parking spaces if they are already part of a larger area with this tag).

When not to use

Where parking is done directly on the carriageway, consider using parking=lane (or parking:left=*/parking:right=*/parking:both=lane for street parking mapped on the highway line).

For parking lots (i.e., a dedicated area for parking enclosed by a barrier or containing its own service roads) see parking=surface.

Small rest-areas along a road outside built-up areas where drivers can pull over for a brief rest can be tagged with parking=layby.

Examples

Single street side parking area On a separate area: amenity=parking parking=street_side orientation=perpendicular capacity=4

Several street side parking areas (on the left – and lane parking on the right) Variant 1 – with separate area for the streetside parking areas on the left: On the parking areas: amenity=parking parking=street_side orientation=perpendicular On the highway: parking:left=separate parking:right=lane parking:right:orientation=parallel Variant 2 – using street parking scheme on highway lines for both sides: parking:left=street_side parking:left:orientation=perpendicular parking:right=lane parking:right:orientation=parallel

Rendering

Rendering in most cartographic styles follows that of other amenity=parking types, such as parking=surface. In OpenStreetMap Carto, the blue P is rendered slightly smaller than that of larger parking features:

• 
  Rendering of street side parking in OSM Carto
• 
  Comparison between the rendering of amenity=parking with parking=street_side or parking=lane, and those with parking=surface (or no parking=* at all) in OSM Carto; the smaller P is used for parking=street_side and parking=lane.

Relation to area:highway=*

When the parking areas are explicitly mapped using amenity=parking (or amenity=motorcycle_parking) plus parking=street_side, then there is some overlap with the subject of the area:highway=* proposal. Street-side parking mapped with parking=street_side can complement area:highway=* where used.

The relevant proposal shows street-side parking areas mapped as separate areas, which would be a good fit for parking=street_side. Some mappers use area:highway=parking_space to map the area of street_side parking spaces (Note: rarely used area:highway=parking could be better to avoid confusing it with amenity=parking_space). amenity=parking (or amenity=motorcycle_parking) + parking=street_side should be added there as main tag.

amenity=parking plus parking=street_side, combined with area:highway=*. Other tags such as capacity=* and orientation=* are omitted for brevity.

Distinction between street_side and lane parking

Street-side parking bays and areas differ more or less clearly from normal lane parking on the carriageway (parking:side=lane on the street line or parking=lane as separate feature). In general, a street_side parking area is a structural extension at the edge of the carriageway, whereas lane parking is on the carriageway itself.

However, in some cases, a distinction can be difficult and depend on the subjective perception of the mapper. For example, 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. Those kerb extensions doesn't make a lane parking of an entire street into a street_side parking. But if there are many kerb extensions in one street, it may become a little hard to distinguish between these two situations in reality.

The following criteria can help to make a classification: they do not have to be fulfilled individually, but can facilitate a categorisation when combined.

Note: When mapping the carriageway width (width=* on the highway line), be aware that the carriageway width includes lane parking areas, but never includes street-side parking areas.

Characteristics indicating street_side parking

	The parking area clearly stands out from the roadway along part of the street through kerbing or other structural elements.
	The parking area forms a structural "pocket" and is bordered on its sides by fixed obstacles such as trees, lampposts or bollards.
	The parking area is divided into several individual parking "bays" by structural features.
	The surface in the parking area is different from that on the carriageway.
	The parking area is separated from the carriageway by a kerb.

Characteristics indicating lane parking

	The parking area could be used as traffic area if no vehicles were parked on it.
	The parking area is indicated by installations on the roadway (e.g. bollards), which could, however, be removed without major reconstruction efforts in order to restore the roadway.
	The parking area is bordered by structural elements on one side only.
	The parking area is bordered only by simple kerb extensions with large distances between them.

Kerb Extensions

Kerb extensions and the parking space in between extend structurally into the carriageway, while street-side parking areas adjoin the carriageway area at its outer edge.

Particularly in combination with kerb extensions (also called "bulb out", "neckdown" and similar), it can be unclear whether a parking area is considered street-side or lane parking. Kerb extensions are traffic calming measures which widens the sidewalk for a short distance to increasing traffic safety for pedestrians.

Kerb extensions are often built into existing road cross-sections. Whether or not this turns a former lane parking into a street-side parking in the OSM sense must be considered in each individual case. The characteristics mentioned above or the following principles can help:

• Large distances between the pavement extensions, the absence of fixed obstacles such as trees, lampposts or bollards as well as an unchanged road surface in the parking area tend to indicate the category of lane parking.
• If, on the other hand, the parking area is divided into rather short sections that are clearly separated from the roadway, this indicates street_side parking.
• Kerbs form a line that separates the carriageway from the roadside space. Kerb extensions and the parking area in between usually extend out from this "baseline", while street-side parking areas fall behind this "baseline" (see illustration on the right).

Also note the remark above about carriageway width if this is specified at the highway line: For lane parking, the parking area is part of the width value, whereas for street-side parking it's not.

See also

• Street parking – General informations about how to map parking along streets
• parking=lane – Parking on the carriageway, including partially on it
• parking=on_kerb - Parking outside the carriageway, on a neighbouring footway
• highway=emergency_bay - Emergency bay on a highway
• shoulder=* - shoulders, also known as breakdown lanes, often serves as an emergency stopping lanes
• parking=layby - facility, often rural, alongside a major road where motorists can take a break en-route to their destination