English
English
English
  • SWARM Documentation
  • What's new?
    • Version 2024.2
    • Version 2024.1
    • Version 2023.3
      • Update 1
  • SWARM in a nutshell
    • SWARM Perception Platform Overview
  • Quick start guide
    • P101, P401 or OP101
      • P101 - Perception Box
      • P401 - Perception Box
      • OP101AC - Outdoor Perception Box
      • OP101DC - Outdoor Perception Box
    • Virtual Perception Box
      • System requirements
      • Install VPX Agent on NVIDIA Jetson (Jetpack 4.6)
      • Install VPX Agent on NVIDIA Jetson (Jetpack 5.1.2)
      • Install VPX Agent on X86/NVIDIA Server
  • Solution areas
    • Traffic Insights
      • Set-up Traffic Counting
      • Set-up Traffic Counting with speed estimates
      • Set-up Intersection Insights
    • Parking Insights
      • Set-up Barrierless Parking
      • Set-up Barrierless Parking with ANPR
        • Set-up guide and recommendations - ANPR
      • Set-up Single Space/Multi Space Parking
        • Standard examples
    • Advanced Traffic Insights
      • Set-up Adaptive Traffic Control
      • Set-up Journey Time & Traffic Flow
        • Set-up guide - Installation
        • Technical concept
      • Set-up Queue Length Detection
    • People Entry/Exit counting
  • SWARM Control Center
    • Devices
      • Camera & Device Monitoring
      • Camera Configuration
        • Scenario Configuration
          • Models
          • Calibration support
          • Camera settings
        • Rule Engine
          • Use Case Examples for Rule Engine
      • Device Health
    • Data Analytics
      • Creation and organization of dashboards
      • Dashboard overview & Widget creation
        • Traffic Scenario
        • Parking Scenario
        • Generic Scenario
    • Data Integration
      • Data Analytics API (REST API)
      • Raw event data with Custom MQTT server
      • SCC API
    • Administration
      • Monitoring Alerts
      • License Management
      • User Management
  • Test & Performance measurements
    • Benchmarks
      • How do we measure Performance?
    • White paper for use cases
      • Traffic Counting
      • Barrierless Parking and ANRP
  • Useful knowledge
    • 🚒Troubleshooting Guidelines
    • Network Requirements
    • Browser Compatibility SCC
    • Our Object Classes
    • Number Plate Area Code
  • Guidelines
    • How to access the debug output?
    • How to use Azure IotHub as Custom Broker
    • VPX
      • Upgrade IotEdge from 1.1 to 1.4
      • Upgrade Jetpack from 4.4.1 to 4.6.0
  • Getting Support
    • Get in touch
    • FAQs
Powered by GitBook
On this page
  • What data can be generated?
  • What needs to be considered for a successful analysis?
  • Environment specification
  • Hardware Specifications

Was this helpful?

Export as PDF
  1. Solution areas
  2. Traffic Insights

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).

PreviousSet-up Traffic Counting with speed estimatesNextParking Insights

Last updated 1 year ago

Was this helpful?

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).

What data can be generated?

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.

What needs to be considered for a successful analysis?

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 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

Possible Camera for this use case

Camera

Comment

HikVision

Bullet Camera

2,8 mm fixed focal length

HikVision

Bullet Camera

2,8mm - 12mm motorised focal length

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.

Configuration settings

Configuration

Model

Configuration option

Origin Destination Zones

ANPR

Disabled

Raw tracks

Disabled

How to place the configuration type?

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.

Visualize data

Scenario

In our Traffic Scenario section, you can find more details about the possible Widgets to be created in the Traffic Scenario Dashboards.

Example

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.

Retrieve your data

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.

Environment specification

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%

Hardware Specifications

Supported Products

VPX, P401, P101/OP101, P100/OP100

Frames Per Second (FPS)

25

Tip: Use the or .

Camera mounting - horizontal angle to the object

You can visualize data via in different widgets.

Data Analytics
Traffic Scenario
Pixels per Meter (PPM)
Axis lens calculator
generic lens calculator
DS-2CD2046G2-I
DS-2CD2645FWD-IZS
Traffic & Parking (Standard)
SWARM Control Center
camera and data
OD Chord
OD Table
REST API
csv. export