Traffic Flow Data July to Dec 2020 SDCC

Some of the nodes may be double cycling at half of the region cycle time. system: SCOOT STC UTC (UTC-MX) locn: Locations site: Site numbers day: Days of the week Monday to Sunday. Abbreviations; MO,TU,WE,TH,FR,SA,SU. date: Reflects correct actual Date of when data was collected. start_time: NOTE - Please ignore the date displayed in this column. The actual data collection date is correctly displayed in the 'date' column.

The date displayed here is the date of when report was run and extracted from the system, but correctly reflects start time of 15 minute intervals. end_time: End time of 15 minute intervals. flow: A representation of demand (flow) for each link built up over several minutes by the SCOOT model. SCOOT has two profiles: (1) Short – Raw data representing the actual values over the previous few minutes (2) Long – A smoothed average of values over a longer period SCOOT will choose to use the appropriate profile depending on a number of factors. flow_pc: Same as above ref PC SCOOT cong: Congestion is directly measured from the detector.

If the detector is placed beyond the normal end of queue in the street it is rarely covered by stationary traffic, except of course when congestion occurs. If any detector shows standing traffic for the whole of an interval this is recorded. The number of intervals of congestion in any cycle is also recorded.

The percentage congestion is calculated from: No of congested intervals x 4 x 100 cycle time in seconds. This percentage of congestion is available to view and more importantly for the optimisers to take into account. cong_pc: Same as above ref PC SCOOT dsat: The ratio of the demand flow to the maximum possible discharge flow, i.e. it is the ratio of the demand to the discharge rate (Saturation Occupancy) multiplied by the duration of the effective green time.

The Split optimiser will try to minimise the maximum degree of saturation on links approaching the node.