How to code roundabouts – Part 2

Technical Note

December 2019

By Tessa Hayman

 

Before you start to code your model, you can set up roundabout road types to minimize local calibration. As vehicles travel around roundabouts at speeds significantly lower than the speed limit, you can use separate road types for roundabouts of different radii to set accurate speeds.


Figure 1: Road types within the project window


Figure 1: Road types within the project window


Figure 2: Use a polyline to measure the size of the roundabout island

Figure 2: Use a polyline to measure the size of the roundabout island

Once the road type is applied to the roundabout, the parameters for all roundabout sections as well as circulating and exiting turns based will by default be set to those in the road type.



Figure 3: The road type of this roundabout is set to roundabout 40-60m



Figure 3: The road type of this roundabout is set to roundabout 40-60m


If the model is in a country with a “choose-lane-on-entry” style roundabout (see part 1), the distance-zone parameters should be at least the circumference of the roundabout; this means that a vehicle entering the roundabout is aware of the exit lane on entry.

These parameters can be set within the road type for each roundabout road type:

Table 1




Figure 4: Calculating distance zones for a roundabout


Figure 4: Calculating distance zones for a roundabout

Locally, you may also wish to adjust the visibility parameters. The visibility is set to the entry section to the roundabout and therefore can’t be adjusted through the use of a roundabout road type. You could also change these globally with a script or additional road type.



Table 2



Figure 5: Visibility defaults can be set to design values


Figure 5: Visibility defaults can be set to design values

In congested situations in microsimulation, the distance zone parameters may need to be longer in order to minimize missed turns.

 

Micro parameters

If you are coding a “choose-lane-on-entry-type” it can also be useful to increase the co-operation and aggressiveness of the section to encourage lane changing on the approach.

 

Meso parameters

As there is no acceleration or deceleration in mesoscopic simulation, you may need to reduce the speed on approach and on the roundabout sections more than in micro; you can do this using an attribute override.



Figure 6: Attribute override for reducing speed on roundabouts at meso


Figure 6: Attribute override for reducing speed on roundabouts at meso


  • “Penalize shared lanes” can be used on the entry and circulating sections of the roundabout to balance lane usage.
  • Initial and final safety margin is calculated at the conflict zone in micro. In meso, it is calculated at the start of the two conflicting turns, therefore, the safety margin should be higher than in micro. The longer the turn, the higher the safety margin.
 

Results

As roundabouts have multiple turns, the turn counts cannot be obtained directly. There are two main ways of collecting roundabout turns:

  • Using a subpath: create a subpath between each entry and exit.
  • Using a supernode: select all of the nodes within a supernode and add it to a supernode – If you plan to merge the nodes of a signalized roundabout, do this before creating the supernode.


Figure 7: Use extensive select to ensure that all the nodes within a roundabout are selected.

Figure 7: Use extensive select to ensure that all the nodes within a roundabout are selected.



Figure 8: Right-click a node and select Create Supernode


Figure 9: Supernode is then generated with all possible turns within the junction



Figure 9: Supernode is then generated with all possible turns within the junction

More technical notes

  • Contact us

SHARE

Cite Aimsun Next

Aimsun Next 26

Aimsun (2026). Aimsun Next 26 User’s Manual, Aimsun Next Version 26.0.0, Barcelona, Spain. Accessed on: December. 3, 2025. [Online].

Available: https://docs.aimsun.com/next/26.0.0/

Aimsun Next 26

@manual {AimsunManual,
title = {Aimsun Next 26 User’s Manual},
author = {Aimsun},
edition = {Aimsun Next 26.0.0},
address = {Barcelona, Spain},
year = {2026. [Online]},
month = {Accessed on: Month, Day, Year},
url = {https://docs.aimsun.com/next/26.0.0},
}​​​​​​​​​​​​​​​

Aimsun Next 26

TY – COMP
T1 – Aimsun Next 26 User’s Manual
A1 – Aimsun
ET – Aimsun Next Version 26.0.0
Y1 – 2026
Y2 – Accessed on: Month, Day, Year
CY – Barcelona, Spain
PB – Aimsun
UR – [In software]. Available:
https://docs.aimsun.com/next/26.0.0/