Modeling conflict areas for pedestrians

1.  Ensure that the following network objects are defined:

  • Links designated for pedestrians in which the attribute Is pedestrian area is selected (Defining pedestrian links): Link B in the figure.
  • Links designated for vehicles in which the attribute Is pedestrian area is deactivated (Attributes of links): This includes both links A in the figure.

2.  On the network object sidebar, click Conflict Areas.

Vissim creates passive conflict areas in the two opposite directions of pedestrian links. Passive conflict areas are marked yellow by default.

The figure shows a modeling example:

3.  Repeat the following steps until the desired priority rule is shown.

4.  Right-click the desired conflict area.

5.  On the shortcut menu, click the desired entry:

  • Set the status to "A has right of way."
  • Set the status to "B has right of way."
  • Set the status to "Undetermined".

Conflict areas on a link for pedestrians always have the same priority rule: pedestrians have the right of way or must give the right of way. Based on the current priority rule and the current speed as well as desired speed, pedestrians and vehicles decide when they can pass a conflict area.

The approaching vehicle does not perceive the pedestrian until at least 3 m before it reaches the conflict area. This distance depends on whether the pedestrian or vehicle is required to wait and on the values of the conflict area’s attributes Additional stop distance or Rear gap (default) (Attributes of conflict areas):

  • If the pedestrian has to wait, the following applies: 3 m + additional stop distance
  • If the vehicle has to wait, the following applies: max(3m, ([Rear gap (default)] + 0.5s) * 1.5m/s)

Note: If the two links intersect at an acute angle, the distance for crossing the road is greater. This also increases the time required by pedestrians to cross the link. As Vissim does not conduct a geometric analysis of the relative position of the two links connected by the conflict area, there is a possibility that a pedestrian may not have left the lane when the next vehicle reaches the lane.

Case 1: Pedestrians yield to vehicles

Pedestrians intending to cross the vehicle link (A1) and enter the conflict area on the left lane of (A1) in the illustration above, consider their minimum speed. This is dynamically calculated at the stop lines, where the arrows end. Pedestrians using minimum speed or a higher speed can pass the stop line, but other pedestrians have to wait before the stop line.

Pedestrians enter a conflict area with a vehicle link only if they can cross the entire link (in stages) so that they never are on a lane on which a vehicle is just passing through the conflict area. The desired speed of the pedestrian and the current speed of the vehicle are assumed here. The following are not taken into account:

  • Vehicles that have not yet reached the network.
  • Vehicles that are located more than 75 m times the number of lanes of the link from the conflict area. This condition can no longer be fulfilled after entering the conflict area if, for example, a vehicle accelerates or enters the network at a relatively short distance. In this case, the pedestrian waits before the first lane of the vehicle link which he probably cannot cross completely before the arrival of the vehicle.

If the attribute Avoid blocking the major flow is deactivated in the conflict area, and pedestrians who are obligated to wait are consequently permitted to obstruct the right-of-way for vehicles, the following conditions apply:

  • If no vehicle enters within the time period from SimTime to SimTime + MinGapBlockDef, pedestrians are allowed to enter the conflict area at any time.
  • If a vehicle enters the conflict area within the time period SimTime, SimTime + MinGapBlockDef, pedestrians may enter the conflict area, provided that they observe the minimum gap time RearGapDef when they leave the conflict area again and the vehicle enters the conflict area.

If the attribute Avoid blocking the major flow is chosen for the conflict area, preventing pedestrians obliged to wait from obstructing vehicles with priority, pedestrians can enter the conflict area. They must, however, adhere to the minimum gap time RearGapDef when leaving the conflict area, ensuring compatibility with the vehicle with priority entering the conflict area.

Case 2: Vehicles have to wait

On the pedestrian link, the area 3 m upstream from the conflict area to the start of the conflict area is used as a "detector area" for the pedestrians approaching the conflict area (Modeling detectors for pedestrians). Pedestrians within the conflict area are always taken into account:

If no pedestrian is expected to enter the conflict area, the gaps between pedestrians or groups of pedestrians are transferred to the approaching vehicles. Thus they can respond accordingly.

Superordinate topic:

Modeling links as pedestrian areas