Best Practices

Overview

TrafficVision™ is a flexible computer-vision solution that has the ability to work with most camera configurations. By following a few basic guidelines regarding the positioning of cameras and identifying good fields of view, tilt and pan angles, and zoom levels, the software can be maximized to provide optimal results. This is a basic overview of best practices, followed by both ideal and poor camera view examples to help you optimize deployment and performance.

General Guidelines

TrafficVision™ performs best:

• Ideal camera position is at a height of between 60’ to 80’ facing a straight section of highway with the lanes closer to the camera traveling away from the camera to minimize the effect of headlight glare

• Fixed cameras are recommended for critical functionality such as Wrong Way detection or highly accurate data collection.

• For PTZ cameras, always make a TrafficVision™ configuration preset at a desirable view, tilt angle and zoom level, and then set cameras to automatically return to it (home position).

• Keeping the “known length” in the field of view consistent with the preset keeps the data accurate, as well as reduces false positives for slow speed and pedestrian alerts.

• TrafficVision works best when camera movement is rare/minimal. It’s best to disable touring mode for cameras performing video analytics, however if touring mode must be used it is recommended to adjust the dwell time to at least 15 minutes for each view in the tour.

• Using a view without curves, ramps, under and over passes, or secondary directions of travel will greatly improve the system.

• Minimizing sky and placing the horizon line towards the top of the view will increase performance of the system.

• For Wrong Way Detection, aim the camera down an off ramp so that the standard flow of traffic is away from the camera.

• Wrong Way Detection cameras require a view that will not change (either using a fixed camera, or a PTZ camera that is left in one position) for accurate detection.

• Views for Data Collection are typically usable for Automated Incident Detection (AID), however not all AID views are usable for Data Collection.