Nwave’s platform supports hybrid solutions, enabling the integration of per-space parking sensors and car-counting sensors within a single parking facility.
This setup is particularly useful when monitoring the occupancy of specific spaces, such as EV-charging spots, within a broader parking area equipped with vehicle counters. For example, it allows real-time tracking of available EV-charging spaces within a larger facility.
This document outlines the setup process for an area managed by a vehicle counting system that includes four EV-charging spaces.
As shown, the parking facility has two entry points: one for entry and one for exit. Each entrance should be equipped with sensors running “Car Counter” (CC) firmware.
The four EV-charging spaces should use sensors with “Per Space” (PS) firmware installed.
All sensors can be registered under the same project, zone, and group.
For the correct working of the sensor configuration, the positions must be marked with labels by the following rule:
Entry sensor position - label IN
Exist sensor position - label OUT
EV sensor positions - label EV
As long as the parking area contains 20 spaces, the Zone zone capacity must be set to 20 by these instructions: https://nwaveio.atlassian.net/wiki/spaces/ND/pages/3018686469/Car+Counters+Getting+Started#Capacity-configuration
You can read more about the sensor positioning in these documents:
Since sensors are positioned and labeled, the analytics, car counting, and real-time parking systems start processing data.
Now you can see full parking occupancy on the Analytics Car-Counters page.
Please, keep in mind, that per-space and car counting systems are different onesFor, so you should get data from different APIs. For example, If you need to get full parking occupancy data, you can use the following request to car counters analytics API:
curl --request GET 'https://api.nwave.io/analytics/v1/car_counters/realtime/occupancy_summary?group_by=group&zone_id=123' --header 'x-Auth-Token: XXXXXXXXXXXX'
Even though, for getting occupancy of EV spaces only, you should use per-space analytics API:
curl --request GET 'https://api.nwave.io/analytics/v1/realtime/occupancy_summary?zone_id=123&labels=EV&group_by=zone' --header 'x-Auth-Token: XXXXXXXXXXXX'
However, if you use GraphQL API v2, you can use the same API for getting CC and PS occupancy data.
Additional information about the API is available on pages: