When measuring values for CO2, temperature, relative humidity etc. you can just display the actual value immediately on the screen. In case you are missing a value the overall trend is not influenced by the data you haven’t received*1.
This is different when you start counting like with People Counting.
In case you did not receive*1 a count you will have a different total value at the end.
For this reason it is recommended working with total count values from our counting devices.
Once you start working with the total count values you can not just display the received value within your dashboard or report. Of course there is a possibility to reset or preset the total count values within our devices. This however requires an action back to the device to give this command.
It is recommended to calculate back the counted value using the received total count value.
Once you do this you will have an ‘easier to work with’ dataset for further processing which enables combining entrances and calculating occupancy.
For occupancy you might first think of a solution which counts the number of ‘heads’ in a room/floor/building. This will become very complex once a single device is not able to cover the complete area.
For that reason it is recommended to apply a line based counting solution. This is done by counting at each entrance/exit to the targeted area.
This works for most situations and use cases and is easy to setup.
When you know that at any given moment people enter or leave the room/floor/building you can calculate the occupancy and you will also know from which entrance you had the traffic.
In the writing above we are working with the idea that people counting is done using a count line. By using a count line complex scenarios can be counted.
For example when you have a building with several entrances you can determine the following
in and outgoing traffic per entrance/exit
calculate the number of people within the building.
This same concept can be applied and combined for a building, floor, room etc.
1) When we speak about missing data we refer mainly to cases where LoRaWAN is used. The rules regarding the use of the specific frequency spectrum limits the number of messages back to a device/sensor. This also means that the information for the device to know if the transmitted data was received is not available.
If, for whatever reason, the data was not received the device doesn’t do a reattempt.
When measuring values for CO2, temperature, relative humidity etc. you can just display the actual value immediately on the screen. In case you are missing a value the overall trend is not influenced by the data you haven’t received*1.
This is different when you start counting like with People Counting.
In case you did not receive*1 a count you will have a different total value at the end.
For this reason it is recommended working with total count values from our counting devices.
Once you start working with the total count values you can not just display the received value within your dashboard or report. Of course there is a possibility to reset or preset the total count values within our devices. This however requires an action back to the device to give this command.
When measuring values for CO2, temperature, relative humidity etc. you can just display the actual value immediately on the screen. In case you are missing a value the overall trend is not influenced by the data you haven’t received*1.
This is different when you start counting like with People Counting.
In case you did not receive*1 a count you will have a different total value at the end.
For this reason it is recommended working with total count values from our counting devices.
Once you start working with the total count values you can not just display the received value within your dashboard or report. Of course there is a possibility to reset or preset the total count values within our devices. This however requires an action back to the device to give this command.