How to succeed in traffic counting including speed estimates of vehicles according to our Classes/Subclasses on dedicated urban & highway streets
Do you want to know the average speed of your traffic in given areas? SWARM software is providing the solution to get the number of vehicles passing at the street split in different speed segments (10km/h) or even see the average speed of the given count over an aggregated time period.
For this use case, SWARM software is providing you with any data needed for traffic counting as explained in the Traffic counting use case.
The configuration of the solution can be managed centrally in SWARM Control Center. Below, you can see how a standard traffic counting needs to be configured for optimal results.
In order to start your configuration, take care that you have configured your camera and data configuration.
When you have enabled the speed estimation, the Counting Line will transform into two lines with a distance calibration measurement. In order to get a good result on speed estimates it is crucial that the calibration distance between the two speed lines is accurate. The distance can be changed in the trigger settings on the left sidebar.
You can choose the direction IN/OUT as you want in order to retrieve the data as needed. On top, you have the option to give a custom direction name for the IN and OUT directions.
You can visualize data via Data Analytics in different widgets.
In our Traffic Scenario section, you can find more details about the possible Widgets to be created in the Traffic Scenario Dashboards.
Here is an example for a Traffic counting widget split by 10km/h groups of speed estimates. You have different options to choose the data you want for a certain time period.
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.
If you would like to integrate the data in your IT environment, you can use the API. In Data Analytics, you will find a description of the Request to use for retrieving the data of each widget.
Use Cases for Traffic Scenarios
There are two major use cases for understanding the traffic situation across your city, urban streets as well as highways.
Configuration | Settings |
---|---|
Camera
Comment
HikVision
Bullet Camera
2,8 mm fixed focal length
HikVision
Bullet Camera
2,8mm - 12mm motorised focal length
Model
Configuration option
Counting Line (optional speed)
ANPR
Disabled
Raw Tracks
Disabled
Speed Estimation
Enabled
Object velocity
< 130 km/h
Day/Night/Lighting
Daytime/Well illuminated/Night vision
Indoor/Outdoor
Outdoor
Supported Products
VPX, P401, P101/OP101, P100/OP100
Frames Per Second
25
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 for object classes car, truck
> 60 PPM for object classes person, bicycle, motorbike
Using the camera parameters defined below ensures to achieve the minimum required PPM value)
Tip: Use the Axis lens calculator or generic lens calculator.
Camera video resolution
1280×720 pixel
Camera video protocol/codec
RTSP/H264
Camera Focal Length
2,8mm-12mm
Camera mounting - distance to object center
Object classes car, truck
5-30 meters (2,8mm focal length)
35-100 meters (12mm focal length)
Object classes person, bicycle, scooter
3-12 meters (2,8mm focal length)
25-50 meters (12mm focal length)
Camera mounting height
Up to 10 meters
Note: Higher mounting is preferred to minimize occlusions from larger objects like trucks
Camera mounting - vertical angle to the object
<50°
Note: setting the correct distance to vehicle and camera mounting height should result in the correct vertical angle to the vehicle
0° - 90° Note: An angle of about 15° provides better classification results due to more visible object details (e.g. wheels/axes)
Wide Dynamic Range
Can be enabled
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.
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.
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.
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.
Camera mounting - horizontal angle to the object
The configuration of the solution can be managed centrally in . 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 accordingly.
You can visualize data via in different widgets.
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, P401, P101/OP101, P100/OP100 |
Frames Per Second (FPS) | 25 |
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 for object classes car, truck > 60 PPM for object classes person, bicycle, motorbike 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-12mm |
Camera mounting - distance to object center | Object classes car, truck 5-30 meters (2,8mm focal length) 35-100 meters (12mm focal length) Object classes person, bicycle, scooter 3-12 meters (2,8mm focal length) 25-50 meters (12mm focal length) |
Camera mounting height | Up to 10 meters Note: Higher mounting is preferred to minimize occlusions from larger objects like trucks |
Camera mounting - vertical angle to the object | <50° Note: setting the correct distance to vehicle and camera mounting height should result in the correct vertical angle to the vehicle |
0° - 360° |
Camera Infrared Mode | Can be enabled |
Wide Dynamic Range | Can be enabled |
Camera | Comment |
HikVision | Bullet Camera | 2,8 mm fixed focal length |
HikVision | Bullet Camera | 2,8mm - 12mm motorised focal length |
Configuration |
Model |
Configuration option | Origin Destination Zones |
ANPR | Disabled |
Raw tracks | Disabled |
How to succeed in traffic counting including the classification of vehicles according to our Classes/Subclasses on dedicated urban & highway streets
You want to know the traffic situation of an urban street or highway? SWARM software is providing the solution to get the number of vehicles passing at the street split per vehicle type (Classes) and direction.
For this use case, SWARM software is providing you with any data needed for traffic counting - The counts of vehicles including classification can be covered. The counts are split between two directions (IN/OUT). Furthermore, several counts can be made in one video camera, e.g.: count each lane separately. On top, you have the opportunity to add a second counting line, calibrate the distance in between and estimate the speed of the vehicles passing both lines.
The configuration of the solution can be managed centrally in SWARM Control Center. Below, you can see how the standard traffic counting needs to be configured for optimal results.
In order to start your configuration, take care that you have configured your camera and data configuration.
For receiving the best accuracy of the counting including the classification, the Counting Line should be placed approx. in the middle of the video frame so that vehicles from both directions are seen long enough for good detection and classification.
You can choose the direction IN/OUT as you want in order to retrieve the data as needed. On top, you have the option to give a custom direction name for the IN and OUT directions.
You can visualize data via Data Analytics in different widgets.
In our Traffic Scenario section, you can find more details about the possible Widgets to be created in the Traffic Scenario Dashboards.
Here is an example for a Traffic counting widget You have the different options to choose the data you want for a certain time period as well as choosing the output format (e.g.: bar chart, 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.
If you would like to integrate the data in your IT environment, you can use the API. In Data Analytics, you will find a description of the Request to use for retrieving the data of each widget.
Tip: Use the or .
Camera mounting - horizontal angle to the object
Configuration | Settings |
---|---|
Camera
Comment
HikVision
Bullet Camera
2,8 mm fixed focal length
HikVision
Bullet Camera
2,8mm - 12mm motorised focal length
Model
Configuration option
Counting Line (optional speed)
ANPR
Disabled
Raw Tracks
Disabled
Object velocity
< 130 km/h
Day/Night/Lighting
Daytime/Well illuminated/Night vision
Indoor/Outdoor
Outdoor
Expected Accuracy (Counting+Classification)
(when all environmental, hardware, and camera requirements are met)
Counting >95% (vehicles, bicycles) Classification of main classes: >95% Classification of subclasses: >85%
Supported Products
VPX, P401, P101/OP101, P100/OP100
Frames Per Second
25
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 for object classes car, truck
> 60 PPM for object classes person, bicycle, motorbike
Using the camera parameters defined below ensures to achieve the minimum required PPM value)
Tip: Use the Axis lens calculator or generic lens calculator.
Camera video resolution
1280×720 pixel
Camera video protocol/codec
RTSP/H264
Camera Focal Length
2.8mm-12mm
Camera mounting - distance to object center
Object classes car, truck
5-30 meters (2,8mm focal length)
35-100 meters (12mm focal length)
Object classes person, bicycle, scooter
3-12 meters (2,8mm focal length)
25-50 meters (12mm focal length)
Camera mounting height
Up to 10 meters
Note: Higher mounting is preferred to minimize occlusions from larger objects like trucks
Camera mounting - vertical angle to the object
<50°
Note: setting the correct distance to vehicle and camera mounting height should result in the correct vertical angle to the vehicle
0° - 90° Note: An angle of about 15° provides better classification results due to more visible object details (e.g. wheels/axes)
Wide Dynamic Range
Can be enabled
Camera mounting - horizontal angle to the object