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
  • Adaptive Traffic Control
  • What needs to be considered for a successful analysis?
  • Environment specification
  • Hardware Specifications

Was this helpful?

Export as PDF
  1. Solution areas
  2. Advanced Traffic Insights

Set-up Adaptive Traffic Control

PreviousAdvanced Traffic InsightsNextSet-up Journey Time & Traffic Flow

Last updated 8 months ago

Was this helpful?

Adaptive Traffic Control

Adaptive traffic control enables you to interface with hardware devices like traffic controllers using dry contacts. Use cases and benefits:

  • 'Smart Prio' System: Prioritise certain traffic classes and ensure fluid traffic behavior in real-time (e.g. pedestrians, bicyclists, e-scooters, heavy traffic).

  • Simplify infrastructure maintenance: Replace multiple induction loops with a single Swarm Perception Box. The installation does not require excavation work, and reduces the maintenance effort/costs.

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 cars, trucks

> 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

Object classes cars, trucks

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

Possible Camera for this use case

Camera

Note

HikVision

Bullet Camera

2,8mm - 12mm motorised focal length

Configuration settings

Configuration
Settings

Model

Configuration option

Region of Interest + Rule

ANPR

Disabled

Raw Tracks

Disabled

Configuration

  • Requirements:

    • Supported event types: Region of Interest (ROI) in combination with rules

First off, enable IO-device, specify the used Quido device type and the endpoint (IP or hostname).

Rule Configuration

Define at least one ROI and create an associated rule. As long as the rule is valid, the associated Quido relay output is enabled (contact closed). One or more rules can be created for the same ROI.

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.

Environment specification

Object velocity

< 40 km/h

Day/Night/Lighting

Daytime/Well illuminated/Night vision

Indoor/Outdoor

Outdoor

Expected Accuracy

(when all environmental, hardware, and camera requirements are met)

Presence Detection >95% Classification of main classes: >95% Classification of subclasses: >85%

Hardware Specifications

Supported Products

VPX, P401, P101

Frames Per Second

12

Tip: Use the or .

Camera mounting - horizontal angle to the object

The configuration of the solution can be managed centrally in . 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

Supported hardware: , ,

All you need to get started: Define a Region of Interest (ROI), define a and select which relay output to trigger.

You can visualize data via in different widgets.

SWARM Control Center
camera and data configuration.
Quido 4/4
Quido 8/8
Quido 2/16
rule
Data Analytics
Traffic Scenario
Pixels per Meter (PPM)
Axis lens calculator
generic lens calculator
DS-2CD2645FWD-IZS
Traffic & Parking (Accuracy+)
Showcase Adaptive Traffic Control with the Rule Engine: Left Lane >=3 objects; Right Lane: >= 1 object
IO-device Configuration
Rule Configuration for Adaptive Traffic Control