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 requirements
  • Hardware specification

Was this helpful?

Export as PDF
  1. Solution areas
  2. Parking Insights

Set-up Barrierless Parking with ANPR

How to succeed in setting up an Entry/Exit parking system with ANPR

PreviousSet-up Barrierless ParkingNextSet-up guide and recommendations - ANPR

Last updated 1 year ago

Was this helpful?

You have a parking space where you want to know your utilization and parking times of your customers, then you can use the SWARM solution as following.

What data can be generated?

For this use case, SWARM software is providing you with any relevant data for your Entry/Exit parking space. The solution is gathering the number of vehicles in your parking space as well as the number of vehicles entering and exiting your parking space for customizable time frames.

The vehicles are classified in any classes the SWARM software can detect. Nevertheless, consider that the following configuration set-up is optimized to detect vehicles and not people and bicycles.

Thanks to the License plate recognition, the parking duration of your customers will be analyzed. On top of the License plate information, license plate origin country as well as are available as meta information. The country codes are according to standard. The country classification is working with excellent accuracy of 99%.

What needs to be considered for a successful analysis?

Find below some general settings for the installation of this use case. As the automatic number plate reading needs some more detailed information you will find additional and more detailed information on how to set it up in the following page:

Especially for Automatic Number Plate Recognition (ANPR) the camera choice and positioning are essential.

The requirements for accurate number plate recognition can be aligned with respective norms for the accurate operation of (human-based) surveillance systems.

The standards give a recommended pixel-per-meter measure (“pixels on target”), to reliably perform that task (by a human). The relevant category for clear reading of license plates/identification of a person “without a reasonable doubt” is “identify”. A Bullet camera is recommended.

Recommended

Pixels Per Meter is a measurement used to define the amount of potential image detail that a camera offers at a given distance.

> 250 PPM

To clearly read a license plate, at least 250 PPM are required. Using the camera parameters defined below ensures to achieve the minimum required PPM value

Resolution

min. 1920×1080 (H264)

Focal Length

min 3.6-8 mm motorized adjustable focal length recommended

Mounting

Distance and height of installation

Note: setting correct distance to license plate and camera mounting height should result in the correct vertical angle to license plate Horizontal angle to license plate

Exposure / Shutter speed

max. 1/250 for objects not moving faster than 40 km/h

Possible Camera for this use case

Manufacturer
Model
Link
Note

Hikvision

Bullet Camera

DS-2CD2645FWD-IZS

Motorized varifocal lens

The configuration of the solution can be managed centrally in . Below, you can see how the Entry/Exit parking with license plate detection needs to be configured for optimal results.

In order to start your configuration, take care that you have configured your

Configuration settings

Configuration

Model

Configuration option

CL (Counting Line)

ANPR

Enabled

Raw tracks

Disabled

How to place the configuration type?

For receiving the utilization of your parking space including the park durations of your customers, a CL for each Entry/Exit needs to be configured. The CL should be placed approx at the beginning from last third of the frame in order that the object can be over several frames, so that the License plate detection and classification are most accurate.

Consider that the IN/OUT direction of the crossing line is important as it is relevant for calculation of the park duration. (IN = Entry to parking, OUT = Exit of parking).

Visualize data

Scenario

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

Example

You are able to visualize the data for any Entry/Exit you have configured with the Counting lines. So you are able to see the number of vehicles with their classes/subclasses and license plates of any Entry or Exit.

Furthermore, you will be able to gather a list of customers with the corresponding license plate that has parked longer than your preconfigured parking duration is. For the purpose of provability, you can also see a picture of the incoming and outgoing vehicle. Please mind that you need to configure the parking time due to your data privacy restriction.

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.

Environment requirements

European countries

Licence plate types

Note: square two line license plates (e.g. motorbike) are not supported

Object velocity

< 40km/h with low-light conditions

Area of focus

Single lane when camera mounted on the side; Two lanes when mounted above the center of both lanes

Day/Night/Lighting

Daytime or well illuminated only (min 500 lux)

Indoor/Outdoor

Indoor & Outdoor

Expected Accuracy (Counting + License Plate)

(when all environmental, hardware and camera requirements met)

>90% Only vehicles are considered. For parking spaces people, bicycles and motorbikes are not part of our test scenarios as they don't occupy parking spaces.

Hardware specification

The License plate recognition is not supported on the P100 SWARM Perception boxes. So for this use-case, the P401, P101 SWARM Perception box, or a VPX deployment option with NVIDIA-based hardware is needed.

Tip: Use the or .

You can visualize data via in different widgets.

If you would like to integrate the data in your IT environment, you can use the . In Data Analytics, you will find a description of the Request to use for retrieving the data of each widget.

In case you are using your custom MQTT broker, you can also retreive the raw data there. We provide a special option to have the license plate capture added to the event schema. This enables you to retrieve the capture within the pushed MQTT message. The picture is encoded in BASE64. In order to enable this option, please contact our .

Examples:

‘standard’ car license plates ()

Data Analytics
Parking Scenario
API
support
Pixels per Meter (PPM)
Axis lens calculator
generic lens calculator
https://www.hikvision.com/en/products/IP-Products/Network-Cameras/Pro-Series-EasyIP-/DS-2CD2645FWD-IZS/
Traffic & Parking (Standard)
License plate countries
520 by 120/110 mm
license plate area codes
ISO 3166 Alpha 2
Set-up guide and recommendations - ANPR
SWARM Control Center
camera and data configuration.
Parking time violations
csv. export
REST API