Terrain-aware CCTV coverage planning
SighThor gives security consultants a browser-based camera placement workflow with terrain masking, IEC 62676-4 DORI analysis, and evidence-ready exports.
Standards
IEC 62676-4
Exports
PDF, PNG, CSV, KML
Alternative to
JVSG-style desktop tools
Pain Points
Why camera planning fails in the field
The common failure mode is simple: a clean-looking plan is produced from geometry that ignores the actual terrain.
Flat-plan assumptions
Manual FOV calculations hide how slopes and embankments really affect coverage.
Expensive desktop lock-in
Traditional desktop tools are expensive, Windows-only, and still assume flat ground too often.
No real evidence
Clients ask for evidence, not just a nice-looking camera symbol on a plan.
Feature Deep Dive
What the camera workflow is built to show
Everything is organised around one question: can you prove the specified part of the site is covered to the required standard?
Terrain-masked FOV
Coverage footprints stop where the terrain blocks the view instead of pretending the lens sees through a hill. SighThor uses real elevation data to cast rays from the camera position, so the polygon you see on the map is the polygon that exists in the field.
DEM raycast at 1-arc-second resolution
DORI and PPM zones
Identification, recognition, observation, and detection bands update from the real lens and sensor geometry. PPM is calculated from sensor specs — never hardcoded — so swapping a lens or changing a camera model immediately reshapes every zone on the map.
PPM = resolution_h / (2 × distance × tan(hFOV/2))
Overlap awareness and camera schedule
See where multiple cameras cover the same ground so redundancy decisions are visual instead of speculative. Then export the full camera schedule — position, height, angle, model, and DORI distances — ready for handover or procurement review.
Multi-emitter overlap analysisPreset-driven workflow
Start from real camera presets with sensor_width_mm, focal_length_mm, and resolution baked in. Adjust on-site assumptions instead of rebuilding lens math from scratch. The hFOV is derived automatically so DORI zones are always physically accurate.
hFOV = 2 × arctan(sensor_w / (2 × focal_length))Workflow
From concept layout to client evidence in four moves
The workflow stays short enough to use during real design sessions, not just for final documentation.
Step 01
Create a site project and navigate to the real location on the map.
Step 02
Drop cameras into position, choose presets, and set height, bearing, tilt, and range.
Step 03
Inspect DORI zones, terrain masking, overlap, and blind areas directly on the map.
Step 04
Export the map, schedule, and report package for the client or internal design review.
Comparison
A web-native alternative to desktop CCTV design tools
SighThor is positioned for consultants who want the DORI math and the terrain context in the same place.
| Capability | SighThor | Typical desktop competitor |
|---|---|---|
| Terrain-aware coverage masking | Yes. Hills and slopes block the polygon. | Usually no. Flat-plan assumptions dominate. |
| Browser-based workflow | Yes. Mac, Windows, Linux, and tablet browsers. | Often Windows desktop only. |
| IEC 62676-4 DORI zones | Yes. Built from lens and sensor geometry. | Usually partial or manual. |
| Client-ready export pack | PDF, PNG, GeoJSON, CSV, KML, KMZ. | Varies. Often requires manual assembly. |
| Pricing posture | Free tier, then $29/month or $249/year. | Typical desktop alternative: around $300/year. |
Deliverables
Export the design without rebuilding it somewhere else
The camera mode is designed to finish the workflow with usable artefacts instead of leaving you to reconstruct the story manually.
Typical use cases
Design reviews, tenders, compliance discussions, and client sign-off.
Export once the map and the measurements line up. The output is meant to move directly into handover, review, or procurement workflows.
PDF report with site map, DORI maps, and camera schedule table
PNG
PNG for quick sharing or presentation decks
CSV
CSV schedule for project teams and procurement
GeoJSON
GeoJSON and KML/KMZ for GIS or Google Earth workflows
Camera Planning
Replace guesswork with terrain-backed camera evidence.
Start with the free tier, place cameras on a real site, and see how quickly the design discussion improves when the terrain is no longer hidden.