Set-up Intersection Insights
How to succeed in getting the information for crossings or roundabouts as well as vehicle movements from Origin (Entry) to Destination (Exit).
You want to know the flow of your intersections, SWARM Perception platform is providing the solution to get the number of vehicles starting in an origin zone and ending up in a destination zone per vehicle type (Classes).
For this use case, SWARM software is providing you with any data needed for Origin Destination Zones - The number of vehicles from one zone to another including classification according to BAST/TLS standards can be covered.
All SWARM classes are detected. Nevertheless, you need to consider that the following configuration set-up is optimized to detect vehicles and not people and bicycles.
Camera Set-up
How to configure the solution?
How to get the data?
Find detailed information about camera requirements/settings as well as camera positioning in the table below.
| Recommended |
Pixels Per Meter is a measurement used to define the amount of potential image detail that a camera offers at a given distance. | >30 PPM (vehicle) >60 PPM (rider, person) Using the camera parameters defined below ensures to achieve the minimum required PPM value) |
Camera video resolution | 1280×720 pixel |
Camera video protocol/codec | RTSP/H264 |
Camera Focal Length | 2.8mm |
Camera mounting - distance to object center  | 5-30 meters (vehicle) 5-15 meters (rider, person) |
Camera mounting height  | 3-6 meters |
Camera mounting - vertical angle to the object  | <50° Note: setting the correct distance to the object and camera mounting height should result in the correct vertical angle to object |
Camera mounting - horizontal angle to the object
 | 0° - 360° |
Camera Infrared Mode | Can be enabled |
Wide Dynamic Range | Can be enabled |
Camera | | Link | Comment |
HikVision | DS-2CD2046G2-IU | 2,8 mm Focal Length |
The configuration of the solution can be managed centrally in SWARM Control Center. Below you can see how an Origin Destination analysis needs to be configured for optimal results.
In order to start your configuration, take care that you have configured your camera and data accordingly.
Configuration | |
Model | Traffic & Parking |
Configuration option | Origin Destination Zones |
ANPR | Disabled |
Raw tracks | Disabled |
For Origin/Destination at least two zones need to be configured. The zones can be placed as needed on the video frame. Consider that the first zone the vehicle is passing will be considered as the Origin zone and the last one the Destination zone.
If a vehicle is passing Zone A then Zone B and afterwards Zone C, the OD event will be Origin: A and Destination: C
On top, it is important that the zones are configured as big as possible in order that there is enough space/time to detect the vehicles successfully.
In our Traffic Scenario section, you can find more details about the possible Widgets to be created in the Traffic Scenario Dashboards.
You have the different options to choose the data you want in the preferred output format (e.g.: bar chart, table, ...). For Origin Destination analysis there is a special chart - Chord Chart - for visualizing the flow with the counts.
OD Chord
OD Table
If you need your data for further local analysis, you have the option to export the data of any created widget as csv file for further processing in Excel.
REST API
If you would like to integrate the data in your IT environment, you can use our SWARM API. In data discovery, you will find a description of the Request to use to retrieve the data of each widget.
csv. export
Object velocity | < 50 km/h |
Day/Night/Lighting | Daytime/Well illuminated/Night vision |
Indoor/Outdoor | Outdoor |
Expected Accuracy (From Origin to Destination) (when all environmental, hardware, and camera requirements met) | Origin Destination counts + right main class: >85% (for vehicles)
Classification of main classes: >95%
Classification of subclasses: >85% |
Supported Products | VPX, P100/OP100/StarterKit |
Frames Per Second (FPS) | 25 |