Back to Resources

Guide

Track Trespass Detection Using Existing CCTV

Author
DHI Safety OperationsEdge AI ArchitectureReviewed by DHI Engineering
Published
2026-07-02
Read time
9 min read
Updated
2026-07-02

Who this is for

For rail, transit, and station operations teams evaluating track trespass alerts on current camera infrastructure.

The buyer question

Can existing CCTV see enough of the rail envelope to support trespass detection?

Map the rail envelope

The first step is drawing the actual danger zone in each camera view. The model should understand the trackbed, platform edge, tunnel mouth, or right-of-way boundary.

Route to the control-room workflow

A useful event should include camera, platform, track, zone, and urgency so operators can slow movement, dispatch staff, trigger PA, or escalate.

Separate nuisance events

Maintenance crews, wildlife, wind, debris, and passing trains should be reviewed separately from confirmed human occupancy.

How to use this with DHI

Use this page as a pre-pilot checklist. Pick one zone, one event type, one alert owner, and one review cadence. If the current cameras cannot support the workflow, fix the camera plan before expanding the deployment.

Validate "track trespass detection using existing cctv" on your live feeds.

Coordinate a 30-day architecture review and live camera validation based on the protocol described in "track trespass detection using existing cctv" for your facility.

Best follow-up: bring the current workflow that "Track Trespass Detection Using Existing CCTV" is supposed to improve.