This article describes how to set up map displays of objects detected and tracked by Intelligent Video Analytics, Essential Video Analytics or Intelligent Tracking with FW 6.4x and Video Security Client 2.1.
In order to start to analyze and optimize Video Analytics settings for particular customer set up, we need initial information and export of example video.
This article describes the absolute minimum information we need in order to start analyzing and optimizing Video Analytics performance.
Video Analytics (VA) task performance optimization
Please provide the following details:
Symptom specific Information
Describe the expected result from the VA task.
It is important to get detailed information of the results VA should provide.
Define what is the customer’s priority:
High sensitivity - miss as few true alarms as possible, but increases the likelihood of more false alarms!
High precision – have less false alarms, but accept the risk to miss true alarm!
Using VA is always based on balancing between sensitivity and precision. It is not always possible to get high sensitivity and high precision at the same time.
Provide an export of recorded video that should contain:
for basic understanding of meta data, please read the latest Software Manual Video Content Analytics
for instructions about doing a video export with meta data, please read the article: How to export video including meta data (Export video including Video Analytics meta data).
Couple of examples of false alarms (in case false alarms are the issue)
Provide the number of false alarms per time span (per day, per week, etc.)
What would be acceptable as a number of false alarms per time span
Couple of examples of situation that should have caused alarm, but VA did not generate the alarm as expected.
In this case please provide the time stamp of the event and short description
Screenshot from the Camera Calibration Verification page - only in case calibration is needed for the particular VA functionality
access the Calibration Verification page of the camera (via the Configuration Manager or Web Interface)
provide screenshot from the verification of each parameter used for camera calibration
Note: For more information on Camera Calibration and Calibration Verification, please check:
How To calibrate camera for Video Analytics?
This article describes the camera tamper detection options available with FW 6.30: Scene too dark / bright, global change, reference image check.
Applications: - Detect camera blinding - Detect camera being moved away from of its view - Detect the loss of sufficient overall illumination - Detect idle / removed objects, e.g. objects in front of an emergency exit
Limitations: - Not available on thermal cameras
This article describes idle and removed object detection with Intelligent or Essential Video Analytics in FW 6.30, how to configure it and what the limitations are.
Applications: - Detect parked cars in no-parking zones - Detect blocked emergency exits - Detect the removal of museum exhibits - Detect suspiciously left packages in high-security areas - Detect idle bags in walk-through areas
Limitations: - Not available on thermal cameras - Does not work in crowds - No abandoned baggage detection - No differentiation between baggage and persons sitting or lying down - Does not work in front of moving background like wind in trees or water - Does not work during illumination changes or camera brightness adaptations
Never lose track of an object of interest! Intelligent Tracking automatically zooms in to and follows a selected Intelligent Video Analytics object as far as possible with the camera.
For AUTODOME / MIC IP 7000, this means automatically steering the camera to zoom in to the object and follow it.
For a FLEXIDOME IP panoramic 7000, Intelligent Tracking is available in the Virtual PTZ video and steers the dewarped cut-out.
For DINION / FLEXIDOME IP 7000 / 8000 cameras, Intelligent Tracking can steer a region of interest (ROI) stream. This article describes how to set Intelligent Tracking up with FW 6.30 and lists the differences based on the camera types.
Traffic detector has been developed to cope with all traffic densities up to high density like congestions and queues in front of traffic lights. It also detects non-moving vehicles and is thus applicable for smart parking. In addition to vehicles, it also detects pedestrians.
Tunnels & Highways: o Collection of traffic statistics o Detection of congestions for automatic speed signaling o Detection of wrong way driving
Intersections: o Detecting presence and volume of vehicles
Smart parking: o Detect parked cars
The museum mode of Intelligent and Essential Video Analytics is an optimized tracking mode to detect whenever someone tries to reach towards and touch a valuable asset like a museum exhibit.
It can also be used in any other application where approaching a sterile zone from a more crowded environment shall be detected.
When camera is set to auto track (by web interface) to "auto"-> IVA is detecting an object but camera is not following.
Auto tracking works and metadata is displayed only on a stored preposition.
There was a change introduced starting with FW v.7.70.
The new feature is: i-Track only starts on VCA-Alarm.
You can either program this on presets, e.g a detection field or if you want to have Itrack active regardless of its position, you need to activate "global VCA" and assign task detection area "whole screen"
now only activate iTrack "AUXON78" so the eye is in the corner, and your iTrack will always be on sharp
Note: IVA must be active for at least one preset scene in the VCA page on the Settings tab.
If IVA is configured for one scene, then all other scenes have Intelligent Tracking enabled by default. If a scene, however, has Motion+ or IVA 5.5 Flow activated, then Intelligent Tracker is disabled for these scenes.
Please refer also to the attached document.
This articles gives a short introduction to scripting alarm and counter tasks with Intelligent and Essential Video Analytics in FW 7.60. It also provides a broad selection of example scripts for explanation as well as including real world application examples.
Video Analytics for Firmware 6.60 and above
Technical Note on Intrusion Detection
The technical Note attached to this article contains detailed technical description of Intrusion Detection, set up guidance for different usage scenarios and best practices. It is useful to get in depth knowledge about Intrusion detection or to find the answer of frequently asked questions.
Intrusion detection without calibration
Learn how to use the default scenario - Intrusion detection no camera calibration: A predefined scenario that can be used to detect intruders in small areas and controlled environments
Intrusion detection one field
Learn how to use the default scenario - Intrusion detection one field: A predefined scenario that can be used to detect intruders in small areas.
Intrusion detection two fields
Learn how to use the default scenario - Intrusion detection two fields: A predefined scenario that can be used to detect intruders in large outdoor areas.
Note: If needed you can get additional how to information on camera calibration.