Tag:parking=on_kerb

parking = on_kerb
Description
An area suitable or designated for parking on the sidewalk.
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=on_kerb $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

parking=on_kerb is used to explicitly map parking on the sidewalk. This is related but distinct from parking=street_side which too is generally located outside a road's carriageway but doesn't necessarily make up part of the sidewalk surface.

This is distinct from parking=street_side where the parking is on a separate surface

How to map

Place a node or draw an area with amenity=parking and add parking=on_kerb to it.

Keep in mind that this is a form of micro-mapping that requires a high degree of precision to be effective. It is recommend to only draw a parking=on_kerb where the parking spaces are marked. For unmarked spaces, the street parking scheme with parking:left, parking:both and parking:right is more useful.

Distinction between street_side and on_kerb parking

The distinction between parking=street_side and parking=on_kerb is comparably subtle, especially in relation to the other parking values since in both cases, the parking is often located outside the carriageway (note that some parking bays are part of the carriageway). The decision to use one tag over the other thus depends on the subjective perception of the mapper.

The general rule of thumb is: Can pedestrians move straightforward even if no cars are parked? If so, it's on_kerb, else street_side (compare the difference between street_side and lane where the latter can easily be converted to a travel lane).

Some more detailed rules to decide on whether to use parking=street_side or parking=on_kerb:

• on_kerb is only used on parking spaces which are level with the sidewalk. If the parking space is separate by a kerb from the footway (especially if it shares the surface with a road), it's likely parking=street_side.
• A change in the surface is no hard prerequisite for street_side. In general, if the surface colour changes, it's a sign towards on_kerb.
• on_kerb is usually located next the carriageway, separating pedestrians from moving cars by a layer of parked cars whereas street_side can also appear behind pedestrians.
• If the footway is otherwise separated by a grass strip or (hard to remove) barriers such as a row of trees from the carriageway, even if the surface is the same, the parking is street_side.

It should also be noted that some mappers are of the opinion that street_side should be used regardless since on-kerb parking still fits the description of the side of a street, especially because it has better support than on_kerb as noted below (note that this doesn't truly violate the Don't map for the renderer principle because no data gets truly falsified).

Support

Even though parking=street_side is one of the official parking values, most software, from renderers to editor to quality assurance, don't actually treat them as actual street parking, instead processing them as bigger parking infrastructure such as parking lots. This makes them stand out when placed next to parking=street_side and parking=lane.

See also

• Street parking
• Key:parking#Common_values for more parking values
  • parking=street_side
  • parking=lane
  • parking=half_on_kerb - if the parking is between on_kerb and lane.