Release Date: 15.11.2023
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.
To get started, check out the configuration steps.
The device health metrics allow you to provide evidence for reliable and continuous data collection and to self-diagnose common problems (e.g. stable network connectivity/power supply/camera connection/processing speed,... )
The following metrics are supported:
Device Uptime, Status, Restarts, Available Disk Space
Device Temperature (support for P101/OP101/Jetson Nano)
LTE Modem Traffic, Signal Strength and Reconnects (support for OP100/OP101)
Camera status and Camera processing speed (FPS)
Generated and Pending events
We replaced the model Parking (Single-/Multispace) with the model Traffic & Parking (Accuracy+). The model is tuned for accuracy while the processing speed (measured in FPS) is reduced. Ideally for use cases with less dynamic objects like Adaptive Traffic Control and Parking Insights (Single- and Multispace).
We improved the classification accuracy for both variants Standard and Accuracy+, especially for the classes: articulated truck, truck with trailer and car with trailer.
We fixed the class output, the event class output is now person (vs. previously head). Affected by this change are the devices P101/OP101/VPX. Not affected are the devices P100/OP100.
We improved the accuracy due to higher resolution processing.
We improved the accuracy due to higher resolution processing.
The model has been deprecated and will not be updated in the future. The model will continue to work as long as there are devices using it. Please consider switching to the Traffic & Parking model.
Organize devices and generate events containing pre-defined device metadata. You can define up to five key and value pairs for a device. The keys and values can be freely defined by your choice, we support autocompletion for keys to avoid nasty typos.
Once defined, metadata allows you to filter the list of devices by metadata values and the generated events will include the pre-defined metadata for further processing by your application. For details have a look at the event schema.
Track calibration overlays the last 100 object tracks on a current camera frame. This enables you to position event triggers (e.g. counting lines) for optimal results. We extend the functionality with a history over the last 24 hours.
With track calibration history enabled you will be able to access the track calibration for every hour of the past 24 hours.
The track calibration images will be stored on the edge device and are only accessible through the Control Center. Make sure that viewing, storing, and processing of these images for up to 24 hours is compliant with your applicable data privacy regulations.
You decide when your devices get an update. Please update soon in order to use the latest features (e.g. Adaptive Traffic Control, Track Calibration History) and to benefit from quality improvements (e.g. Model updates), bug fixes and security updates.
We will automatically update by 13.12.23.
Device Update size (2023.2 -> 2023.3):
P101/OP101 & NVIDIA Jetson devices: 460MB
P100/OP100: 470MB
Control Center - User Management - Invite users and manage permission of existing users
Control Center - MQTT client id can be defined for custom MQTT brokers
Data Analytics - Speed-up of Origin-Destination widgets
Data Analytics - Fix widget visualisation of the chord diagram (OD) and line charts
Under some conditions an ROI in combination with a rule did not trigger events
No breaking API/Event changes (only additions), this includes:
The Control Center API and Data Analytics API
The Event Format
Release Date: 13.12.2023
In addition to the number plate raw text and country code, we now support the number plate area code. Some number plates include an area code associated with a geographical area, such as "W" for Vienna (Austria) or "M" for Munich (Germany).
The following 13 countries are supported
Austria
Bulgaria
Switzerland
Czech Republic
Germany
Greece
Croatia
Ireland
Norway
Poland
Romania
Slovakia
Slovenia
For supported countries, we detect spaces between letters and parse the raw license plate text according to a predefined format.
In the case of countries that are not supported (e.g. Italy), the generated event won't contain an area code.
All use cases based on ANPR are supported, no additional configuration is required.
The Data Analytics widgets "Journey Distributions" and "License Plates" allow segmenting by "License Plate Area"
If you are using a custom broker, the event schema has been adjusted to contain the area code.
Improved classification accuracy for the classes person and bicycle (Traffic & Parking Standard/Accuracy+)
Fixed Data Analytics, some queries led to inconsistent data
Fixed rule engine for Region of Interest occupancy, triggering a hardware output
Fixed P100/OP100 slowdown introduced with 2023.3
Reduced downtime during device updates
Fixed debug video output pixelation of counting line overlays
Fixed license notification for not enough SPS licenses
Device Update size (2023.3 -> 2023.3 Update 1):
P101/OP101 & NVIDIA Jetson devices: 370MB
P100/OP100: 350MB
The device update will be automatically applied by 31.01.24!
No breaking API/Event changes (only additions), this includes:
The Control Center API and Data Analytics API
The Event Format