13.4.5 Basic Geometry – Arterial Coding

Intersections are coded using different links for each approach that end at the intersection. Links typically should not continue through the intersection and all movements for an intersection should be coded using connectors. For the introduction of additional lanes at intersection approaches, a separate link with the total number of intersection approach lanes is used downstream of the network link, using a single connector to smoothly make the transition. The link with the intersection approach lanes is typically the entire storage length of these lanes plus half the length of the taper for the developing lanes.
Once all approach links have been coded, connectors are used to code all possible movements at the intersection. The modeler typically follows the standard number of splines for each movement (if the standard number of splines does not accurately reflect the movement curvature, a different number of splines can be used):
  • 12-point spline for left-turns;
  • 8-point spline for right-turns;
  • 15-spline for right-turn channelization; and
  • 2-point spline for through movements
The modeler connects all connectors to the appropriate lane on the downstream link. For instance, connectors for right-turns connect to the right-most lane of the downstream link and connectors for left-turns to the left-most lane.
An RSA is coded on all turning movement connectors, so that vehicles slow their speed when making a turn. For right turns, 10 mph is typically used as the desired distribution for RSA. For left turns, 15 mph is typically used as the desired distribution for RSA.

13.4.5.1 Traffic Control Devices

Traffic control devices are an important part of network coding. There are numerous ways to code the different traffic control devices such as signalized intersections, AWSC intersections, two-way stop control (TWSC) intersections, roundabouts, etc. in Vissim. below provides a summary of the main network objects that are used to code the different types of traffic controls and their applications
Table 13-1: Traffic Control Devices
Traffic Control
Description
Application
Signal Heads
Signal heads are used to code signalized intersections and are assigned to the signal controller created for that intersection. Signal controllers are typically created using an *.RBC file that is imported from Synchro or created based on signal timing plans.
  • Used for coding signalized intersections
  • Can be imported from Synchro or developed natively in file
  • Is typically placed on top of links and confirm that connectors do not cross the signal head
  • Is assigned to the corresponding signal group, which includes the signal controller and the signal phase associated with the timing plans
Detectors
A detector is used to model traffic sensors in the field that help detect vehicles for actuated signal operations.
  • Is placed directly behind the signal heads and are typically coded to a length of 30 - 90 ft to match the detection area in field.
  • Is assigned a port number (signal phase) and a signal controller number associated with the signal head and signal timing plan.
Stop Signs
Stop signs are used to model unsignalized intersections.
  • Is placed at the location of the stop bar.
  • Used to model right-turn on red operations.
  • Used to model AWSC and TWSC intersections.
Conflict Rules
Conflict rules occur where two links or connectors overlap each other. They are initially set to a passive stage. If an actual conflict exists, the rules need to be adjusted to give one movement priority over the other based on the actual ROW for the conflict vehicles.
  • Used to model yield conditions.
  • Is used for all basic types of conflicts such as right-turns, stop control intersections, permissive left-turns at signalized intersections, etc.
  • Use them were necessary and restrain from exorbitant use of conflict rules as they could lead to gridlock, especially in congested networks.
Priority Rules
Priority rules are similar to conflict rules. They are used to model yield conditions, however, they allow for more customization and are recommended for use in complex situations.
  • Used to model yield conditions.
  • Minimum gaps and headways are typically modified by vehicle type.
  • Can be tied to specific phases of signal.
  • Are used for more complicated conflicts that are not easily coded with a conflict rule such as multi-lane roundabout entries, keep clear of intersection, etc.
Roundabout
Roundabouts are typically coded using a combination of links, connectors, and priority rules/conflict areas. There are example demos within Vissim that can be used to understand the principles of coding a roundabout.
  • Use priority rules to code multi-lane roundabouts.
  • Use the HCM critical gap values for starting off points for minimum gaps for roundabouts. Adjust as needed per visual audits and other factors.
  • Links typically have their attributes modified to not allow lane changes within the circulating lanes.
  • RSA are typically used to model approach speeds and circulating speeds of a roundabout based on the fastest path/design speed or speed measured in field.

13.4.5.2 Pedestrians

A pedestrian crosswalk is typically coded at an intersection using links that match the width and location of the crosswalk in the field that cross over the leg of the intersection. It is best practice to use a different display type for pedestrian crosswalk links to show that these are separate from the vehicle network links. Signal heads and detectors are used on the pedestrian crosswalk links for pedestrian movements controlled by a pedestrian signal. Conflict areas are coded between vehicle and pedestrian links. It is best practice to give priority to pedestrians by coding the green conflict area for pedestrian links and red for the overlapping vehicle links. However, conflict areas can lead to gridlock in certain situations, such as urban areas and areas with congestion. For those areas, it is recommended to use priority rules to avoid the network from gridlocking.

13.4.5.3 Transit

A transit route is coded to show where a transit vehicle moves within the model. These routes originate from the start of a link and are coded with a departure time, which determines the exact time the transit vehicle enters the network. Transit stops are coded along the network to provide locations where the transit vehicle stops. The duration of the stop is controlled using either a predetermined dwell time or passenger boarding. Dwell time distributions are used to code the predetermined dwell time.
Passenger boarding is coded by adding passengers in the network that board the transit vehicle at the stop. The modeler can toggle the transit stops as active/inactive for specific transit vehicles.