|Total number of marked traffic lanes available for motorised traffic.|
|Used on these elements|
|Status: in use|
|Tools for this tag|
The lanes=* key should be used to specify the total number of marked of a road.
The following lanes should be included:
- General purpose traffic lanes suitable for vehicles wider than a motorbike.
- Bus lanes, that are reserved for public service vehicles (PSV), for example buses and taxis. Additionally to the total number of lanes, consider to tag the number of lanes for PSV with lanes:psv=*, lanes:bus=* and lanes:taxi=*.
- High-occupancy vehicle lanes (sometimes also called carpool lanes, commuter lanes, express lanes, transit lanes). The number of such lanes could be tagged using lanes:hov=*.
- Other lanes such as (nl) in the Netherlands or (de) in Austria, Germany and Switzerland which are available to traffic at certain restricted times, for example during the rush hour.
- Longer slip-roads, for example on motorways and other fast major roads. Turning lanes for minor roads are not normally included. See turn=* for further details about tagging turning lanes.
And the following lanes should be excluded:
- Minor slip roads without a deceleration/acceleration lane, i.e. the main road is wider only because of the intersecting road.
- Parking lanes. Consider using parking:lane=* to provide further information.
- Bicycle lanes. Use the tag cycleway=lane for those.
- Emergency shoulder lanes. See shoulder=* for further details.
If the number of lanes changes it is necessary to split the OSM way. This should be done as soon as:
- a new lane has reached its full width, or
- a lane starts to disappear (usually a merge with another lane)
Remark for data consumers
Many ways have not yet been tagged with the total number of lanes at all points, but only with the number of through lanes of a longer section. Therefore, data consumers can mostly treat the lanes tag as a minimum rather than an exact number.
If there are no marked lanes, the key width=* can be used.
Lanes in different directions
If the lanes on a two way road are not distributed evenly between the driving directions, the keys lanes:forward=* and lanes:backward=* can be used in addition to the lanes tag. The key lanes:forward=* hereby refers to lanes which direction is equal to the direction of the OSM way, and lanes:backward=* to the opposite direction.
The lanes=* tag is widely misused to mean the lanes in each direction rather than the total lanes. If the mapper chooses to describe the forward and backward lanes, this potential ambiguity is avoided.
See below for some examples of the usage of those keys.
Lanes reserved for specific vehicles
The number of lanes which are reserved for specific types of vehicles can be tagged by using the key
lanes and adding a suffix that indicates the transport mode from the key access=*, e.g. lanes:bus=1 for a single lane reserved for buses. If it is necessary to specify the direction of those lanes, add the suffix
:backward like in the previous section, i.e. lanes:taxi:forward=1 refers to single lane reserved for taxis in the same direction as the OSM way.
NOTE! The lanes:*=* key type can only be used to indicate the number of lanes that are reserved for a specific transport type on a way. It does not and cannot specify which lanes a transport type is restricted to.
If, for example, on a three lane motorway, heavy-good vehicles are restricted to the rightmost lane only, lanes:hgv=1 will not express that meaning! (lanes:hgv=1 means that hgv vehicles have one lane of the motorway reserved for them and doesn't specify which one, either.)
Restrictions for vehicles can be tagged using the
:lanes suffix and tagging scheme, e.g.
hgv:lanes=no|no|yes would restrict heavy-good vehicles to the rightmost lane.
Restrictions that only apply at certain times and days
For lanes that are restricted for parts of the day only, use the additional lanes conditions tag to indicate when the conditions apply. For example: lanes:bus:conditional=* or lanes:psv:conditional=*. See Conditional restrictions for more details.
There exist roads with no marked lanes, which are two-way roads but without marked lanes and so narrow, that vehicles must slow down to pass each other. It is strongly recommended in such a case to tag the width of the carriageway using width=* (Note: do not mistake this with maxwidth=*). If the width varies a lot, the minimum width of the carriageway should be specified. If it is not possible or reasonable to determine the exact width, use an estimation and tag additionally source:width=estimated, e.g. as follows:
Note: Some people prefer to tag narrow two-way roads with lanes=1.5. See the discussion on tagging. This tagging might not be processed correctly by data consumers. Also see the section Open Issues for this.
|lanes=2||A residential road with two lanes. Consider additional tagging with parking:lane=*.|
Each direction individually
|A dual 2-lane highway, represented by two ways as there is a physical divider between them (each with oneway=yes).|
|A narrow two-way road without marked lanes and with an estimated width of four metres.|
|highway=passing_place (on the node)||A road with passing place.|
|A cycleway with two marked lanes.|
depending on the country.
|A road with two lanes and a median. Depending on the country, special road restrictions may apply to the middle lane. If the middle lane can be considered a separate lane, using the proposed suffix |
Assuming the OSM way runs from left to right
|A road with five lanes, whereas three lanes run in forward direction, i.e. in the same direction as the OSM way. The turning lanes should be tagged using turn=* on the way.|
lanes:bus:conditional=1 @ (Mo-Fr 07:00-19:00)
|A road with three lanes where the rightmost lane is dedicated to buses at the given time. The merging of the leftmost lane should be tagged with the key turn=*. See the article Conditional restrictions for an detailed explanation of the :conditional suffix.|
If for a two way road only the total lane count is tagged and this number is even, it is assumed that the lanes are allocated evenly to both driving directions (e.g. lanes=6 assumes the road has 3 lanes for each direction).
If no lane count is specified at all, a lane count might be assumed as follows:
|2||1||If the actual number of lanes is equal to the given assumption, the lane count is usually not tagged.|
|1||1||If the actual number of lanes is equal to the given assumption, the lane count is usually not tagged.|
|These should usually be mapped as two separate ways||2 or more||The actual number of lanes should always be tagged. However the given assumptions might be helpful for data consumers.|
- For lanes running in both directions there currently exists only the proposed suffix :both_ways.
Displaying the number of lanes
- ITO Map offers an overlay for lanes. (There bug in ITO maps, it will count: lanes=4 lanes:backward=1 lanes:forward=3 as 8 lanes, instead of 4)
- To view the number of lanes in JOSM, a Lane and road attributes style is available. Alternatively, its routes plugin can be used with this lane coloring example.
- These Maperitive lane rules renders highway widths, lanes and offsets based on lanes=* and placement=*.
- OpenStreetMap detailed overlays generates a road overlay with lanes, cycleways, parking, and sidewalks rendered at higher zooms (16+). A slippy map version is available online.
- width=* for tagging the width of the carriageway
- source:width=* for specifying the source of the width
- access=* for transport modes and additional access restrictions
- parking:lane=* for parking lanes
- turn=* for turning lanes
- highway=passing_place for passing places
- shoulder=* pro krajinici
- ITO Maps for verification: Highway lanes - major roads
- Tagging of individual lanes and their properties
- Proposal for turnlanes relation to describe complex geometry of lanes, supported by JOSM "turnlanes" plugin
- Proposal for lane tagging system using different delimiters
- Proposal for tagging the number of tracks of railways
- Proposal for the suffix :both_ways
- Discussion on tagging
- Discussion on tagging, before the cleanup of this article in April 2012