Canonical URL: https://density.io/resources/density-vs-haltian

# Density vs. Haltian: what does your anonymous floor count represent?

Before using a floor count to change your office, confirm which spaces it covers and how the system maintains the total. Density is a strong starting point when you want to choose the measurement for each space, then examine building and floor use in [Atlas](https://density.io/atlas). Its [trust guidance](https://density.io/about-density/trust) describes anonymous radar sensing.

Haltian also offers anonymous occupancy measurement. Its system can combine doorway counts and presence detections into a floor estimate. The useful comparison follows that number from the proposed sensors to the report, rather than treating every camera-free product as the same measurement.

## Trace the Haltian count to its device group

Haltian’s [ENTRYWAY documentation](https://developer.haltian.io/haltian-iot/devices/sensors/haltian-entryway/operation/) describes directional people counting using three passive-infrared detection zones. [Thingsee PRESENCE](https://developer.haltian.io/haltian-iot/devices/sensors/thingsee-presence/) detects activity and supports occupancy or visitor-movement modes.

Its [Occupancy Data Engine](https://developer.haltian.io/haltian-iot/concepts/occupancy-data-engine/) processes sensors assigned to a device group and publishes calculated occupancy under that group’s identifier. An analyst should confirm that the selected record represents the intended floor group, rather than one doorway device. Ask Haltian to list the group’s member sensors, covered routes and reported measurement.

Haltian’s [privacy statement](https://haltian.com/products/privacy-and-security/) describes anonymous occupancy sensing without employee tracking. A device or group identifier identifies equipment or a configured space; it does not, by itself, identify an employee. Review what the proposed application adds to that record. Neither supplier’s camera-free label replaces that review.

## Choose the Density measurement around the space

[Density Open Area](https://density.io/open-area) measures occupancy within covered areas. Evaluate it when the workplace decision needs counts within desk neighborhoods or collaboration spaces. Agree the boundaries and coverage before combining their results into a floor view.

[Density Entry](https://density.io/resources/entry-counts-building-occupancy) measures directional doorway crossings used to calculate occupancy across a covered boundary. It suits questions about building or floor demand when every route across that boundary is accounted for. The distinction is where the count comes from: observations within an area or accumulated crossings into and out of it. Both require an appropriate installation and a defined output.

## Plan for a quiet floor with two entrances

Consider a hypothetical floor with two entrances and an area used by late-working staff. The team wants to understand concurrent demand without identifying individual employees.

For a Haltian proposal, mark which entrance and presence sensors belong to the floor group. Its [reset documentation](https://developer.haltian.io/haltian-iot/concepts/occupancy-data-engine/reset-logic/) explains the conditions: for an entryway-only group, the engine can reset the count after all doorway sensors have been inactive for the configured period. A mixed group also requires every presence sensor to report vacant and no movement, with no activity from any member sensor during that period. Set the correction policy around actual use. Quiet occupancy is not the same as a confirmed empty floor.

For a Density Entry proposal, review the same late-working period. Density’s [Entry guidance](https://support.density.io/hc/en-us/articles/47782967345563-Understanding-Drift-in-Entry-Based-Occupancy-Counting) describes a running count and overnight reset. Its [historical correction guidance](https://support.density.io/hc/en-us/articles/38800110339099-Drift-and-Drift-Correction) applies correction at query time after the daily reset and calls for a reset time when the space is empty, including cleaners and night staff.

Have the deployment owner document the count’s boundary, correction settings and review responsibility. Keep the current reading separate from a corrected historical result.

## Follow the count into the planning decision

Ask Density to demonstrate the selected spaces in Atlas with the operating hours and comparison period visible. Atlas documents building and floor views, custom operating hours and downloadable charts. [Instant’s demonstration](https://density.io/instant) also shows workplace questions and charts, including comparisons between sites. Use the proposed sensor outputs in that discussion.

Give the Haltian team the same question and inspect its proposed report. Its engine documentation describes API access to calculated group measurements. Confirm the devices, services and availability in each actual proposal.

Bring Density your floor plan and the decision the count should support. [Book a demo](https://demo.density.io), or email [sales@density.io](mailto:sales@density.io). Use the [camera-free privacy guide](https://density.io/resources/people-counting-privacy) to review the data path, and [browse the occupancy guides](https://density.io/resources/occupancy-guides-and-comparisons) for related measurement decisions.