Terrain-Aware Camera Coverage: What Flat-Plan Tools Can Miss Outdoors
Flat-plane camera planning can omit hills, buildings, and terrain dips. Source-labelled simulation can expose possible coverage gaps for field verification.
The flat-earth assumption
Many camera coverage calculators work on a flat plane. You place a camera, specify the lens and mounting height, and the tool draws concentric nominal DORI zones radiating outward in a perfect arc. On a flat indoor floor plan, this can be a useful first approximation. Outdoors, it can omit important terrain and obstacle effects.
Real terrain has elevation changes. A camera mounted at 4 metres on a post overlooking a sloped perimeter may lose geometric line of sight to a depression 80 metres away — even when that location is within its theoretical "Detect" distance. A flat-plan model may show coverage where a site-specific terrain model identifies a possible blind spot for field checking.
Where flat-plan assumptions need extra checks
The limitations grow with distance and terrain complexity. Common scenarios where flat-plan coverage maps need additional evidence include:
- Undulating perimeters — solar farms, substations, and rural sites where ground elevation varies by 2-5 metres over short distances. These dips can create modelled blind areas that flat assumptions do not represent.
- Hilltop installations — a camera on high ground looking downhill may have excellent range in one direction but lose line of sight over a ridge in another. Flat tools show uniform radial coverage.
- Urban canyons — buildings and walls block sightlines at oblique angles. Without a terrain/obstruction model, the planner cannot predict which corridors are covered.
- Mounting height effects — on flat ground, raising a camera from 3 m to 6 m extends the theoretical horizon. On sloped terrain, the benefit depends entirely on the gradient. Flat models overstate the gain when the ground falls away.
The cost of unverified plans
Coverage gaps discovered during commissioning are expensive. Re-positioning a camera means new mounting hardware, extended cable runs, and potentially another site visit. For large perimeters with dozens of cameras, the cumulative cost of even a few missed obstructions can exceed the original planning budget.
A site security plan submitted to a client or insurer should therefore state its source, resolution, assumptions and unresolved checks. Nominal "Identify" geometry is not proof of installed identification performance, and commissioning remains necessary.
How terrain-aware planning works
Terrain-aware tools use digital elevation data to model the actual ground surface. When you place a camera, the tool casts virtual sightlines from the camera position across the elevation model, checking at each point whether terrain blocks the view.
The result is a viewshed — the area the selected model predicts as geometrically visible at its stated resolution. Nominal DORI/PPM thresholds can then be clipped to that modelled area. This is more informative than an unqualified flat ring, but it is still a simulation rather than measured installed performance.
- Elevation queries — the tool samples ground height at regular intervals along each sightline using satellite-derived terrain data.
- Ray-cast analysis — for each azimuth angle, a ray is projected from the camera to the maximum range. If terrain intersects the ray, coverage is clipped at that point.
- Earth curvature — at longer ranges (500 m+), the curvature of the earth becomes a factor. Terrain-aware tools account for this; flat tools cannot.
- Source and obstacle uncertainty — terrain age, surface interpretation, building outlines, vegetation estimates and unsurveyed objects must stay visible as limitations rather than being treated as current site truth.
What to look for in a planning tool
If you plan outdoor camera installations, your coverage tool should, at minimum:
- Use real elevation data (not user-drawn contours or flat assumptions)
- Perform line-of-sight analysis per camera, not just radial range rings
- Calculate PPM from actual sensor specifications (focal length, sensor width, resolution)
- Show coverage gaps explicitly — not just where coverage exists, but where it does not
- Export source-labelled drafts in formats suitable for client, competent-person, or authority review, without predicting recipient acceptance
SighThor supports this planning workflow. Place a camera on the map, configure the lens, and the platform uses the selected terrain or surface evidence to calculate source-labelled visibility and nominal DORI geometry. The output requires review against current buildings, vegetation and site conditions, followed by commissioning checks for mounting, lighting, focus, compression and the complete imaging chain.
Turn a site brief into an inspectable planning draft.
Start with terrain-aware geometry, then review every source, limitation and field check.