UpToWhereYour camera plan on ground that is not flat
A field-of-view viewshed per camera on real elevation, the blind spots the ground puts in it, and DORI distances from the lens you actually specified. The longer the lens, the more the ground decides.
See what Studio includesWhat Studio does for a camera plan
Field of view, not a full circle
Give a camera its bearing and its horizontal field of view and get the viewshed for exactly that wedge, computed ray by ray on real elevation.
DORI from the lens you specify
Detection, observation, recognition and identification distances from IEC 62676-4, computed from the sensor width and the lens as you set up the run, updating as you change them. Read them against the wedge on the map: a distance the ground blocks is a distance you do not have.
One project per site plan
Every camera is a site with its mount height, imported from CSV up to 500 at a time, and every wedge is a stored analysis you can re-run the moment a mast, a bearing or a lens changes.
Vegetation included, and said so
The terrain model is a surface model, so treelines and buildings are partly in the heights. For a camera looking across a valley or along a coast, that is the point, not a caveat to bury.
From a site plan to a coverage report
| Step | You do | Studio returns |
|---|---|---|
| Place | Import or search for the camera positions and set each mount height | Sites on real terrain, up to 500 per CSV, in metres or feet |
| Aim | Give each camera a bearing and a field of view | The viewshed for that wedge, and the four DORI distances for that lens |
| Fix | Raise a mast or re-aim | The wedge run again from the new mount or bearing |
| Hand over | Export | The site list as provenance-stamped CSV, and a branded PDF with the site schedule and the methodology page |
Studio is 49€/month or 490€/year. No credits, no per-export fees. What you export is yours to hand on, and yours to check.
What we deliberately do not do
This is terrain and geometry. It tells you whether the ground leaves the line open and how many pixels per metre the lens puts on a target at that distance. It does not model light levels, glare, backlight, weather, motion blur, compression, lens quality, IR reach or video analytics, and it is not a substitute for a site visit or a test install. A camera can pass everything on this page and still give you an unusable picture at 08:00 in February. What it will not do is surprise you with a hill.
FAQ
Is this a CCTV coverage calculator?
It is the part of one that a flat plan cannot do. Coverage area and DORI distances come from the lens and sensor you enter, the same numbers a lens calculator gives; then the field of view is clipped by the terrain, so the coverage map shows the ground a camera on a pole actually sees across a valley, a quarry or a shoreline, and the ground it does not.
How is this different from a CCTV lens calculator?
A lens calculator gives you pixel density on flat ground. This computes the same DORI distances and, beside them, runs the wedge ray by ray on 30 m elevation data to show where the ground actually lets the camera see that far. Read the two together. On a level car park they agree. On a perimeter with a slope, a bund or a treeline they do not, and the difference is the blind spot.
Which DORI numbers do you use?
IEC 62676-4: 25 px/m detection, 62 observation, 125 recognition, 250 identification. The distance for each comes from the horizontal sensor width and the horizontal field of view you enter. It is horizontal pixel density on a target facing the camera, which is what the standard specifies.
Does it handle a PTZ camera?
Model the positions you care about. A PTZ at a given bearing and zoom is a sector, so run the presets you actually use as separate sector analyses, one per position. There is no continuous pan simulation.
Can it tell me who can see IN to my site?
Yes, by putting the observer outside and looking in: the same engine answers a viewshed from any point, which is the calculation a substation perimeter assessment needs.
Does it combine every camera into one coverage map?
Not yet. The cumulative layer sums full circles, which is right for a wind turbine and wrong for a camera: a 10 degree lens would be credited with 360 degrees. Today each wedge is its own analysis, and a sector-aware combined layer with overlap and blind spots is on the roadmap. We would rather you knew that before the first multi-camera job than after it.
What about vegetation growing?
The elevation model is a 2019-2023 surface model, so it holds the canopy as it was, not as it will be. A shot that clears a treeline by two metres today is a shot to check on site and re-check later. We would rather say that than let you find out from a camera.
How is it priced?
One price: 49€/month or 490€/year. No credits, no per-report fees, no per-seat fees, no quotas. What you export is yours to hand on, and yours to check. Cancel anytime.