Set-up Barrierless Parking
How to succeed in setting up a Barrierless Parking Scenario to gather data about utilization
You have a parking space where you simply want to know your utilization by making an Entry/Exit count, SWARM provides a perfect solution for doing that quite easily. See yourself:
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.
Camera Set-up
How to configure the solution?
How to get the data?
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. | > 60 PPM 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 |
Camera mounting - distance to object center | 5-20 meters |
Camera mounting height | 3-6 meters |
Camera mounting - vertical angle to vehicle | <50° Note: setting correct distance to vehicle and camera mounting height should result in the correct vertical angle to vehicle |
Camera mounting - horizontal angle to vehicle
| 0° - 90° |
Camera FPS | > 25 FPS |
Wide Dynamic Range | Must be enabled |
Camera | | Link | Comment |
HikVision | DS-2CD2046G2-IU | 2,8 mm Focal Length |
The configuration of the solution can be managed centrally in SWARM Control Center. 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 camera and data configuration.
Configuration | |
Model | Traffic & Parking |
Configuration option | CL (Counting Line) |
Events for repeated CL crossings | Enabled |
ANPR | Disabled |
Raw tracks | Disabled |
To receive the best accuracy in counting including the classification, the CL should be placed approx. in the middle of the video frame so that vehicles from both directions are seen long enough for good detection and classification.
Consider that the IN/OUT direction of the counting line is important as it is relevant for the calculation of the utilization. (IN = Entry to parking, OUT = Exit of parking).
Toggle direction
In our Parking Scenario section, you can find more details about the possible Widgets to be created in the Parking Scenario Dashboards.
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 that entered or left your parking spot, either aggregated over several Entry/Exits or separately per Entry/Exit. We deliver the following two standard widgets Current & Historic Parking Utilization out of the box when creating a Parking Scenario Dashboard
Standard Parking Widgets
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.
csv. export
If you would like to integrate the data in your IT environment, you can use the API. In Data Analytics, you will find a description of the Request to use for retrieving the data of each widget.
REST API
Object velocity | < 30 km/h |
Day/Night/Lighting | Daytime or Well illuminated |
Indoor/Outdoor | Indoor or Outdoor |
Expected Accuracy (Counting only) (when all environmental, hardware and camera requirements met) | >95%
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. |
Supported Products | VPX,P100/OP100/StarterKit |
Frames Per Second (FPS) | 12 |
Last modified 23d ago