Car Counter is a type of parking sensor which detects cars moving over and send number of detections to an Nwave Cloud. Car Counters are useful when there is no need to know which exctly parking spaces are occupied, but information about of total occupied/free spaces in a parking area is needed.

Car Counters Parking Structure

Nwave's parking structure is organized into a hierarchical system consisting of Projects, Zones, Levels, Groups, and Positions. Here's an overview of these hierarchy objects:

Project: This is the highest-level object in the hierarchy and is required. Projects allow you to group and manage Zones. Users can be granted access to specific projects or a set of projects.
Zone: A Zone represents a single parking area, and it is also a required object. Each parking area is defined as a Zone.
Level: Levels are optional objects in the hierarchy. You can add Levels to Zones if your parking facility has multiple floors or levels. For example, in a multi-level car parking structure.
Group: Groups allow you to unite Positions within them and describe lower-level areas within a Zone or Level. Groups must be added to a Level or directly to a Zone. Additionally, Groups can specify the type of parking area. If you are using Car Counters, the Group Type should be set to "Standalone Car Counter."
Position: Positions should be placed within Groups. Each Position can only belong to a single Group. However, in the case of using Car Counters, sensor data from a single sensor can be applied to two groups when the sensor is placed at a transition point between those groups. This specific behavior can be configured with the assistance of Nwave Team.

By utilizing these hierarchy objects, you can effectively describe the structure of your parking facility and place Positions within the correct hierarchy. For example:

If you want to describe a plane parking area with two zones, "Simple Spaces" and "EV Charging Spaces," you can register the hierarchy as follows:
- Project: My Parking Project
- Zone: My Plane Parking
- Group: Simple Spaces
  - Position: Entrance to parking lot
  - Position: Transition to EV charging area
- Group: EV charging spaces
  - Position: Transition to Simple Spaces area
  - Position: Exit from parking lot
If you need to describe a multi-storey car parking (MSCP) with three floors, you can incorporate Levels:
- Project: My Parking Project
- Zone: My MSCP
- Level: Floor 0
  - Group: Floor 0 Group
    - Position: Entrance to MSCP
    - Position: Exit from MSCP
    - Position: Transition to Floor 1
- Level: Floor 1
  - Group: Floor 1 Group
    - Position: Transition to Floor 2
    - Position: Transition to Floor 0
- Level: Floor 2
  - Group: Floor 2 Group
    - Position: Transition to Floor 1

This hierarchy structure allows for detailed organization and management of parking facilities. For more information on adding Nwave Parking Hierarchy objects, please refer to the provided documentation.

Please note that full car counters support is currently under construction. Nwave currently offers user support for configuring car counters only for single-group zones. If you have the need to split a zone into multiple groups or use car counters to obtain occupancy information for each floor in a multi-level car parking facility, we kindly request that you reach out to Nwave Support for further assistance.

Nwave is committed to providing comprehensive support and solutions to meet your specific requirements.

API

Before using API you need to create Authorization Token using this instructions

Analytics API

Nwave Cloud offers a wide range of analytical APIs, allowing you to access both raw and aggregated occupancy data. For more detailed information about the Car Counter Analytics API, please refer to the documentation page

Car Counter Group Configuration

Car Counter Groups supports only two configuration API:

Group Capacity - the total amount of parking spaces in the group
Occupancy Correction - allows users to adjust group occupancy before live running a project or after resolving issues with equipment.

Group Capacity Setup API

This API endpoint empowers you to configure the total number of parking spaces within a group identified by its unique {group_id}.

URL: https://api.nwave.io/car_counters/v1/group/{group_id}/capacity
Method: PUT
Request Body:

{"capacity": INT}

Example:

This request illustrates how to set a capacity of 100 spaces for a group with ID 1234:

curl --location --request PUT 'https://api.nwave.io/car_counters/v1/group/1234/capacity' \
--header 'X-Auth-Token: XXXXXXXXXXXXXXXXXXXXX' \
--data '{"capacity":100}'

Use this API to efficiently manage and configure the parking space capacity for specific groups.

Occupancy Correction API

Group Occupancy Setup API

This API endpoint allows you to specify the number of occupied spaces within a group identified by its unique {group_id}. Optionally, you can include a timestamp in the request body to set the occupancy value for a specific time.

URL: https://api.nwave.io/car_counters/v1/group/{group_id}/occupancy
Method: PUT
Request Body:

{
  "occupied":INT,
  "time": "2023-06-13T23:05:24.328Z" // optional
}

Example:

This request demonstrates how to set the current occupancy of 35 spaces for a group with ID 1234:

Use this API to efficiently manage and configure the occupancy status for specific groups, with the option to specify a timestamp for accurate tracking of occupancy changes.