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
  • Number plate area code (Early Availability Feature)
  • How does this work?
  • How to configure?
  • How can I access the data?
  • Minor improvements and bug fixes

Was this helpful?

Export as PDF
  1. What's new?
  2. Version 2023.3

Update 1

Release Date: 13.12.2023

Number plate area code (Early Availability Feature)

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

How does this work?

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

How to configure?

All use cases based on ANPR are supported, no additional configuration is required.

How can I access the data?

The Data Analytics widgets "Journey Distributions" and "License Plates" allow segmenting by "License Plate Area"

Minor improvements and bug fixes

  • 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

PreviousVersion 2023.3NextSWARM Perception Platform Overview

Last updated 1 year ago

Was this helpful?

If you are using a custom broker, the has been adjusted to contain the area code.

Barrierless Parking with ANPR
Journey Time
event schema
Data Analytics Widget "Journey Time Distributions"