|junction = circular|
|A road junction where the traffic goes around a non-traversable island but does not always have right of way.|
|Used on these elements|
|Tools for this tag|
The rotary or circular junction itself can include intersection controls such as traffic-signals, stop signs or stop markings, give-way (or yield) signs or give-way markings.
The size of circular junctions and rotaries can vary from small to very large with several lanes, however generally
the rotary or circular junction should not have any road network inside itself, this means circular ring roads around a city are not valid circular junctions.
Important Consideration When Mapping
Ways which enter and exit a rotary or circular junction should never connect to the same node on the junction.
This is required to allow routing applications and software to provide correct directions, otherwise the routing software will not correctly recognise the junction.
Further, generally rotaries and circular junctions have one-way traffic and should have the tag oneway=yes, however a circular junction with bi-directional traffic can be a valid junction to be tagged with junction=circular.
Please pay attention to the section “Possible misinterpretations” to differentiate between:
- Roundabouts (junction=roundabout)—where traffic on the roundabout has right of way;
- Rotaries and traffic-circles (junction=circular)—where traffic on the rotary or circular junction does not have right of way;
- Mini roundabouts (highway=mini_roundabout)—used only on nodes, as a roundabout where the centre of the roundabout must be traversable;
- Turning circles (highway=turning_circle)—used only on nodes, including cul-de-sacs; and
- Turning loops (highway=turning_loop)—used only on nodes, where a road island or similar feature is present.
The tag allows routing software to recognise circular junction structures more easily for cases that fail the OSM roundabout definition. OSRM has implemented the tag. There is no impact to expect on visual map rendering.
How to map
Draw the circular shape, which would represent the junction. Furthermore:
- The OSM ways of the junction must be drawn in the direction the traffic flow.
- Tag the OSM way(s) of the circular junction with junction=circular.
- Add oneway=yes for clarity. As this is a new value for the junction key, many data consumers might not be able to assume the oneway property implicitly.
- Connect it with the roads approaching the circular junction. If a road is split into two separated carriageways (one approaching, one departing), draw those explicitly and tag these carriageways with oneway=yes. Pay attention to their correct orientation and use separate nodes of the circular junction for the approaching and departing road.
- Also tag the junction and approaches with highway=*, the same as the connecting roads. If there are several roads of different importance connecting to the junction, you should usually use the one with the greatest importance, that does not begin or end at the junction. More details about selecting the correct tag can be found on the junction=roundabout page.
- Again, a roundabout should only be tagged with name=* if the junction itself is named independently and differently from the roads crossing it.
- Generally each road has to be connected with the circular junction in a separate node—that is, between these nodes a segment of the circular junction is required. Thus routers can safely recognise that a section of the circular junction has to be driven through.
- It is suggested to map give-way (yield) signs and road markings using highway=give_way.
Distinguishing from roundabouts
- If one of the roads entering the circle has the right-of-way and the other has to yield (Example: Berlin, Strausberger Platz)
- if the circular traffic in the junction always has to yield to incoming traffic (Example: Berlin, Großer Stern)
This form of a junction allows the major and minor road to intersect in one node only, typically in an acute angle. An example is the Strausberger Platz in Berlin, Germany.