Live Use Cases
Density makes our sensor data available as quickly as possible for use in products that need immediate visibility into the use of any space covered by our devices.
This data is optimized for speed. We then run a set of historical algorithms and checks before saving the more permanent historical data, as described in the section below, so it is best practice to use the quickly available data for transient use cases and to save the historical data into permanent data storage.
Open Area Sensors
Live occupancy data is available for any area covered by an OA sensor from these endpoints:
- https://developers.density.io/docs/#operation/short_term_analytics_v3
- https://developers.density.io/docs/#operation/presence_v3
Latency on the live OA data is less than 500ms as long as the network connections are healthy.
Entry Sensors
Live occupancy data is available for any area covered by an Entry sensor from these endpoints:
- https://developers.density.io/docs/#operation/current_occupancy_v3
- https://developers.density.io/docs/#operation/presence_v3
Latency on the live Entry data is less than 500ms as long as the network connections are healthy.
Historical Reporting (Saving to a data lake)
To ensure the most accurate and consistent historical data, Density runs complex optimization and error correction algorithms. Additionally, whenever a device is slow to send its data due to any number of networking issues, we will rerun the floor and building data as soon as the data arrives, potentially changing the stored count data to make it more accurate. For these reasons, we recommend the following:
Open Area Sensors
Historical occupancy data is available for any area covered by an OA sensor from these endpoints:
- https://developers.density.io/docs/#operation/occupancy_v3
- https://developers.density.io/docs/#operation/timeUsed_v3
- https://developers.density.io/docs/#operation/utilization_v3
Note: We recommend waiting at least 7 hours to pull historical data into a data lake to ensure a <1% chance the count data will change due to late arriving sensor data.
Note: Open Area data for the previous day populates in Atlas at 5 a.m. local time.
Entry Sensors
Historical occupancy data is available for any area covered by an Entry sensor from this endpoint:
- https://developers.density.io/docs/#operation/occupancy_v3
- https://developers.density.io/docs/#operation/timeUsed_v3
- https://developers.density.io/docs/#operation/utilization_v3
Please note: We recommend waiting until after your site’s reset time to pull historical data into a data lake. Entry sensor data is corrected to distribute any drift error after the reset time.
The default reset time is 4 a.m. (local time for your site), so pulling data at 5 a.m. for all of yesterday would result in the most accurate and consistent data. Learn more about reset times here.
Comments
Article is closed for comments.