Correct counting line and zone placement is the single most important factor in counting accuracy. This guide covers where to place lines, which logic type to use, and how to use activation zones to eliminate false counts from staff and passersby. Source: Xovis Knowledge Base.
In/Out logic | Count triggered immediately when a person crosses the line. Use in combination with an Activation Zone (recommended by Xovis). |
Late logic | Count triggered when the person's track is deleted (they leave the scene). Use in combination with a Zone of Interest (recommended by Xovis). |
Xovis recommendation: In/Out logic + Activation Zone for entrance counting. Late logic + Zone of Interest for scenarios where U-turns should not be counted (e.g. people who approach but don't enter).
Place the line where people are actually being tracked — not at the physical door. To find the right position, use:
Tracking area visualisation | Enable the Tracking Area layer in Scene Configuration → live view. Shows the theoretical area where people will be detected based on mounting height. |
Start/Stop points | Enable Start/Stop points in the layer selector. Green dots = track start (person enters sensor view). Red dots = track stop (person leaves). Place the counting line between the two clusters. |
Line shape: Use V-shaped or angled lines rather than straight horizontal lines. Straight lines allow people to walk around the ends — a V-shape forces all traffic to cross.
An Activation Zone adds a condition to In/Out logic: a count only fires if the track was created OR deleted inside the zone. This prevents counting people who walk along a corridor past the entrance without entering or leaving.
Draw the counting line at the entrance
Draw an Activation Zone extending into the interior of the space, covering the area just inside the entrance
People who pass by without entering/exiting will not have a track created or deleted within the zone → no count
People who genuinely enter or exit will have their track start or end inside the zone → counted
With Late logic, by default the count fires when the track is deleted at the edge of the tracking area. A Zone of Interest moves this trigger point to a specific zone — the count fires when the person enters or leaves the zone instead. This gives more reliable results in busy multi-entrance areas.
When using Gender statistics, Staff exclusion, or Height filter — counts are always triggered when the track is deleted regardless of logic type. Plan your geometry accordingly.
Deactivation Zone | Inverted Activation Zone — tracks that meet the condition (start OR stop inside zone) do NOT trigger a count. Useful for service entrances you want to ignore. |
Minimum Dwell Zone | For queue counting at checkouts, kiosks, service counters — prevents rapid passersby from inflating counts. Only counts people who dwell in the zone for a minimum time. |
The Path Stitcher fills gaps in tracking continuity in defined zones. If a person's track is lost and reappears within the set radius and time period, the two track fragments are merged into one. This prevents double-counting in areas where tracking is momentarily interrupted (e.g. under bright skylights, at narrow doorways).
Configure in Settings → Singlesensor (or Multisensor) → Path Stitcher.
The Blocked Space Trigger monitors whether a defined zone is physically blocked — measuring what percentage of pixels in that area are covered. Use cases include:
Detecting if a lift/elevator is full before opening doors
Detecting if a bus or train is present at a platform
Alerting when a sensor's view is accidentally obstructed
Configure up to 4 blocked space zones per sensor. Set upper and lower thresholds (0–100%). Configure a Live Data Push agent filtering on "Blocked space above" or "Blocked space below" events to receive alerts.