Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[sumo-user] Pedestrian accumulation and spillback from auto-generated walking areas under high pedestrian demand

Dear SUMO developers,
I am currently running a set of alternative scenarios in which vehicular traffic demand is reduced, while pedestrian demand is increased. In some locations of the network, mainly at auto-generated walking areas near signalized pedestrian crossings, I observe the following behaviour.
Due to the increased pedestrian demand, pedestrians accumulate on certain walking areas. When the available space appears to become saturated, some pedestrians seem to move into the next part of the pedestrian route or crossing section, even though the corresponding pedestrian signal for that movement is red. In other words, the pedestrian queue seems to spill back or overflow from the walking area into the next pedestrian link/crossing section.
I would like to ask whether there is any SUMO parameter, command-line option, or network attribute that can be used to better control this behaviour. More specifically:
  • Is there an attribute that limits the storage capacity of walking areas or prevents pedestrians from entering the next section when the pedestrian signal is red?
  • Could this issue be addressed by manually editing the geometry or width of the walking areas/crossings?
  • Is this behaviour related to the pedestrian model settings, such as the pedestrian model, jam density, or pedestrian movement parameters?
  • Is there any recommended practice for modelling high pedestrian volumes at signalized crossings, in order to avoid unrealistic entry into sections controlled by a red pedestrian signal?
I am attaching an indicative screenshot of the issue, where the accumulation of pedestrians on the walking area and their movement towards the next crossing section can be seen.
Best regards
Botzoris Nikiforos

Attachment: Screenshot_2.png
Description: Screenshot_2.png

Attachment: Screenshot_3.png
Description: Screenshot_3.png


Back to the top