Page Comparison

Nwave platform can manage labeled Nwave’s platform supports hybrid solutions, enabling the integration of per-space parking sensors inside the area, which are car counting sensors on entrancesand car-counting sensors within a single parking facility.

This can be setup is particularly useful when there is a need to control monitoring the occupancy of a few particular spaces inside the specific spaces, such as EV-charging spots, within a broader parking area equipped with car vehicle counters. For example, it is possible to look at the availability of spaces with EV charges inside the bigger areaallows real-time tracking of available EV-charging spaces within a larger facility.

This document describes how to set up the area, which is controlled by a car counting system and contains 4 EV outlines the setup process for an area managed by a vehicle counting system that includes four EV-charging spaces.

Image RemovedImage Added

As you can seeshown, the parking contains 2 entrancesfacility has two entry points: one for entry and one for exit. Both entrances Each entrance should be equipped with sensors with running “Car Counter” (CC) firmware.

The 4 spaces with EV charges should be equipped with sensors that have Par Space four EV-charging spaces should use sensors with “Per Space” (PS) firmware installed.

All these sensors can be registered in 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 rulesensors to function correctly, label each position as follows:

1. Entry sensor position - label

   Status
   colour Blue title IN

2. Exist sensor position - label

   Status
   colour Blue title out

3. EV sensor positions - label

   Status
   colour Blue title EV

As long as Given that the parking area contains has a total of 20 spaces, set the Zone zone capacity must be set to 20 by these using the following instructions: https://nwaveio.atlassian.net/wiki/spaces/ND/pages/3018686469/Car+Counters+Getting+Started#Capacity-configuration

Since Once sensors are positioned and labeled, the analytics, car counting, and real-time parking systems start will begin processing data.

Now you can see full parking occupancy on the A nalytics Analytics Car-Counters page.

Please , keep in mind, note that per-space and car-counting systems are different onesFor, so you should get separate, and each requires data from different distinct APIs. For example, If you need to get full parking occupancy data, you can use the following request to the 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 To retrieve occupancy data exclusively for EV spaces only, you should use the 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 are using GraphQL API v2, you can use the same API for getting obtain occupancy data for both CC and PS occupancy data.Additional information about the API is available on pagessensors using a single API.

For further details, please refer to:

• Per-Space Parking Analytics API

• Car Counters Analytics API

• GraphQL Occupancy API V2