1 / 6

2 – Planning: Video alerts (Vehicle traffic patterns)

2 – Planning: Video alerts (Vehicle traffic patterns). Alerts were configured to count vehicles and detect congestion on Court St. near Washington during the 2013 Boston Calling concert.

dasha
Download Presentation

2 – Planning: Video alerts (Vehicle traffic patterns)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 2 – Planning: Video alerts (Vehicle traffic patterns) • Alerts were configured to count vehicles and detect congestion on Court St. near Washington during the 2013 Boston Calling concert. • Analysis showed a surge in traffic volume between 12:15 and 2:00 pm with the largest spike coming between 12:20 and 12:30, just as people were beginning to be let into the concert venue. • Congestion was rarely detected. • Conclusion: Court St. is a main driving route for people attending such a concert, but can handle the volume as congestion rarely results.

  2. 3 – Planning: Video alerts (People counting at Entrance) • Alerts were configured to count people entering the concert through 6 lanes (approximately half the entrance lanes). • Analysis shows that during good visibility conditions the count was very accurate, within 5%. • During hard rain when contrast was poor, and during bright sun when strong shadows appear, the count can become very inaccurate. • Improvements in camera angle and modifications to the entry procedure can improve visibility and reduce error, but variation will still occur with weather conditions.

  3. 6 – Monitoring: Video Alerts (Large vehicles) • An alert was configured on Atlantic & High St. to detect large vehicles at the intersection. • This alert fired reliably till the camera was moved. • This alert can easily be configured to look only for large vehicles stopped for some period of time.

  4. 7 – Monitoring: Video Alerts (Sidewalk congestion) • A Sidewalk Congestion alert was configured on the near Congress St. sidewalk. • A large number of Sidewalk Congestion alerts on Congress St between 7:30-8:15pm Sat. result from pedestrians in-bound to the concert. • Sidewalk Congestion alerts around 8:55pm result from pedestrians out-bound after the concert. • Note This alert is less reliable with night lighting, so few alerts fired at this time

  5. 8 – Monitoring: Video Alerts (Person Over Fence) • A Tripwire alert was configured to detect object passing over the perimeter fence (e.g. person climbing over fence). • The long distance and poor video quality reduced alert performance. • Two tests were conducted • Person climbing over the fence • Coat thrown over fence • The person climbing over the fence was not detected. • Probable cause: The small size and poor contrast of the person caused IVA to discard their track as noise. • The coat being thrown over the fence generated two alerts

  6. 9 – Monitoring: Video Alerts (Abandoned package) • An Abandoned Package alert was configured in a pedestrian hallway at the Downtown Crossing subway station. • This alert fired reliably on items left by maintenance personel (e.g. mop buckets) with very few false alerts

More Related