What is Line Crossing Detection? Virtual Tripwire Analytics

Line Crossing Detection

Line crossing detection is a video analytic that draws a virtual line (or polygon) inside a camera scene and triggers an alarm when an object crosses it. Direction can be specified (only alarm if a person crosses left-to-right) or bidirectional. Common uses: perimeter intrusion when a person crosses a fence line, dock-door entry counting, after-hours pool or playground access, retail entrance counting, and dwell-time start markers. Line crossing is a subset of broader intrusion detection focused on directional events rather than zone occupancy.

The short definition

Line crossing is a directional analytic. The installer draws one or more lines (or open polygons) on the camera scene. Each line is a 2D representation of a 3D plane in the world: a fence, a door threshold, a property line. The engine tracks each detected object's bounding-box centroid frame-to-frame and fires an event when the centroid crosses the line.

Direction sensitivity distinguishes line crossing from zone intrusion. A line has two sides, and the rule can filter on direction, alarming only on the security-relevant one.

Common use patterns

Fence-line perimeter. Line along the property fence. Inbound crossings alarm, outbound filtered. Pairs with thermal cameras for long perimeters and verified monitoring for response.
Building dock-door tracking. Line at each dock-door threshold for usage analytics; pairs with LPR for vehicle entry logging.
Retail entrance counting. Line at the front-door threshold. Inbound and outbound counted separately for occupancy, conversion, and dwell-time.
Restricted-zone access. Line at a pool deck, playground, or rooftop entrance. Any crossing during restricted hours alarms.
Tailgating detection support. Line at the door paired with an access-control event. Two crossings within a 5-second window of a single badge swipe flags potential tailgating. See the tailgating entry.

Implementation patterns

Three architectures handle most installs.

Edge AI. Camera runs object detection plus line-crossing logic on-board. Sends event metadata to the VMS along with the video stream. Lowest latency. Standard on Axis, Hanwha Wisenet 7, Avigilon H5A, Verkada cameras.
VMS-side analytics. Camera streams raw video to the VMS server, which runs detection and line crossing in the VMS layer. Common in Genetec KiwiVision, Milestone XProtect with analytics, Avigilon Unity. Higher latency but more flexibility.
Camera-agnostic analytics platforms. Briefcam, Dragonfruit AI, and similar take raw streams from any ONVIF camera and run analytics centrally. Strong for retrofits where existing cameras don't have edge AI.

Configuring line crossing well

Three rules of thumb that prevent the most common configuration mistakes.

Place the line where bounding-box centroids will cleanly cross. A line drawn at floor level on a low-angle camera will be crossed by feet but the centroid (typically chest-high) won't cross until the person is well inside the zone. Place the line at chest-to-head height in the scene, accounting for camera angle.
Filter by object class. Specify person, vehicle, or both. Without a class filter, the line will fire on any moving object including animals, leaves, and rain.
Use direction sensibly. If the legitimate direction (employees walking out at end of day) is the same as the alarm direction, the rule is wrong. Walk the scene, identify normal traffic patterns, and configure direction to ignore them.

When to ask Tec-Tel about line crossing

Line crossing is one of the simplest analytics to deploy and one of the easiest to misconfigure. We'll walk a site, mark up the scenes where line crossing fits, configure direction and class filters, and validate against a sample of real footage. Free scoping call.

Frequent buyer questions

What's the difference between line crossing and zone intrusion detection?

Line crossing alarms on a directional event: an object passing a defined line in a specified direction. Zone intrusion alarms on occupancy: an object inside a defined polygon. Line crossing fits perimeter and entry/exit logic ('alarm when someone crosses the fence inbound'). Zone intrusion fits restricted-area logic ('alarm when someone is inside the restricted server room'). Both ride on object detection.

Where is line crossing typically used?

Five common patterns. (1) Perimeter fence-line crossings (chain-link, building face). (2) Dock-door entry counting at warehouses. (3) Retail entrance traffic counting (with directional logic to count entries vs exits). (4) After-hours pool, playground, or restricted-zone access. (5) People-counting at concert and event venues. Each uses the same line-crossing primitive with different rules and downstream actions.

Can line crossing trigger alarms only in one direction?

Yes. The standard implementation supports three modes: any-direction (any crossing alarms), single-direction (only alarm on one direction), or each-direction-tracked (count separately for both directions). Useful at retail entrances where you want to count entries and exits independently. Useful at fence lines where outbound traffic is fine and only inbound generates an alarm.

Does line crossing work on PTZ cameras?

Limited. Line crossing requires the line to stay in a fixed scene. If a PTZ camera is panning or zooming, the line position drifts relative to the world. Most VMS implementations either disable line crossing on PTZ cameras or implement scene-anchored lines that follow the PTZ position back to a known origin. For perimeter installs, fixed bullets are the standard mount; PTZs handle cue-and-slew zoom-in after the fixed camera triggers.

How accurate is line crossing detection?

When paired with object detection, very accurate (95 percent+ for person and vehicle on enterprise cameras). Without object detection (motion-only line crossing), accuracy drops because any moving pixel can trigger: leaf, shadow, weather. Always pair line crossing with object classification to filter the events by what crossed.

Start with a free consultation.

Tell us what you're protecting and what's already in place. The Tec-Tel team reviews it and comes back with a written plan.

Tell us how many sites you run and what's already in place. We'll show you what a build or upgrade looks like.

Straight answers from the team that does the work. We're platform-agnostic, so you get the system that fits your sites, not one brand's catalog.

Since 2010 · 1,000+ deployments nationwide · ISN-accredited

Book a free consultation 855-577-0400

Line Crossing Detection

The short definition

Common use patterns

Implementation patterns

Configuring line crossing well

When to ask Tec-Tel about line crossing

Frequent buyer questions

Object detection

Intrusion detection

Heat map

Full glossary

Start with a free consultation.

How can we help?