...
A project is the highest level of the hierarchy. It is often used as a means for regional aggregation. For example, if all devices in a project are positioned in the same city, it makes sense to create a project with the name of the city and use this project for registration of all the devices inside of that. Also projects may be used for registration of Nwave’s base stations and granting user permissions.
Related pages:
Zone
Zone is the second level of the hierarchy. Zones are very useful as means of typical aggregation (grouping by type of location). For example, if one project contains parking sensors on-street parking bays and on multi-levels car parking, it makes sense to split up them on zones “On-Street”, “Multi-levels parking 1”, “Multi-levels parking 2”, “parking lot near WallMart” and so on.
The most important feature of zones is a possibility of setting up data routing. Nwave is able to push data to client’s services using HTTP and RabbitMQ protocols. For setting up sending data using one of these ways you need to create a route specified to a zone.
Related pages:
routeRabbitMQ
Level
Level is the third optional level of the hierarchy. Levels can be used for description of floors of multistorey car parkings. Levels are parts of Zones. By default, zones are not includes levels and you can add them manually if there is a need. Levels can include groups of positions (see the next section). It is not neccessary to register levels in zones for plane parkings, you can add groups right to Zones
Group
Group is the third level of the hierarchy. Groups are means of adjacency aggregation (adjoining spots or very close proximity). For example, if there is a necessity to analyze parking occupancy data of multi-levels car parking by levels, you can register a group for every level and keep devices inside of them. Also Nwave uses groups to calculation of real-time availability of parking bays. Groups also can be used for setting up HTTP and RabbitMQ routes.
Related pages:
Creating RabbitMQ route
Position
Position is the lowest hierarchy level. Positions are static mounting points on the map. Positions have a lot of properties. Position is used to keep information about device’s location. It preserves location information whether device is positioned there or not. Users can choose the most successful locations for devices positioning on the map, and then go there and position their devices. If there is a necessarily to change a device (upgrade, for example), the position will keep it’s IDs and client’s services will recognize it as before, irrespective of the real device ID.
...