What Is CCTV Blind Spot Mapping? (FOV Angles)
CCTV blind spot mapping is a controlled check of whether authorized cameras meet agreed coverage and image-detail goals. It combines field-of-view geometry with pixel-density checks at important distances, then verifies the recorded image in real conditions. It is not a map for public use, nor proof of code compliance by itself.
A camera can show a wide scene and still fail to capture useful detail where it matters. A doorway may appear in the live view, for example, but a person at that distance may occupy too few pixels for the intended task. FOV mapping helps reveal that difference.
I treat the process as a documented system check, not a hunt for weak points. Keep detailed gap locations in restricted project records. Share public-facing plans only at a level that does not expose sensitive coverage details.
Planning: Define Coverage Objectives, Authorization, and Applicable Standards
Coverage planning sets the purpose and limits of an assessment before anyone checks a camera view. Define which areas are authorized, what image detail is needed, and which privacy and code rules apply. This keeps the review focused on the approved design rather than creating an unnecessary inventory of security weaknesses.
Start with written authorization and a clear scope. List the protected areas and the tasks the system must support, such as detecting movement in a broad area or identifying a person at a controlled access point. Also note areas that must not be recorded, along with any required privacy masks.
IEC 62676-4 provides system-design guidance for video surveillance. DORI criteria are commonly used to describe image detail: detection, observation, recognition, and identification. The pixel densities below are design references, not guarantees of performance or legal minimums. Check the applicable IEC edition and project brief before using them as acceptance targets.
| DORI task | Reference density | General design meaning |
|---|---|---|
| Detection | 25 px/m | Notice that a person or object is present |
| Observation | 62.5 px/m | See general appearance or activity |
| Recognition | 125 px/m | Distinguish a person or object already known |
| Identification | 250 px/m | Capture detail intended to support identification |
There is no universal building-code rule requiring a particular camera FOV, overlap rate, mounting height, or complete CCTV coverage. Confirm local privacy rules, adopted electrical and building codes, and any requirements set by the authority having jurisdiction (AHJ). Treat the project brief and the listed equipment instructions as part of the design basis.
Before surveying, record camera models, lens settings, resolution, and relevant operating modes in a restricted-access inventory. Next step: agree on the required image task and the conditions under which it must work.
Access and Clearances: Check Mounting, Serviceability, Egress, and Privacy
A camera’s view is only one part of a sound installation. Check that the equipment can be mounted securely, serviced safely, and powered and routed in a compliant way. The position must also respect privacy, accessibility, and egress needs. No single height or clearance fits every site or camera.
Review the camera and mount instructions before changing a position or lens. Confirm that the supporting surface suits the equipment and that the mount is suitable for the load and environment. Route cables in a way that follows applicable electrical rules and allows service without damaging finishes or creating a hazard.
Check that the proposed camera or cable route does not obstruct an accessible route, door operation, required egress, or other building feature. Use the adopted local rules and approved project drawings; do not rely on a generic clearance number. Where work affects structure or rated construction, get the review required for that building and jurisdiction.
Privacy needs special attention. A privacy mask can block a sensitive area, but it can also cover part of the intended view. Removing the mask may expose a prohibited area. Check the mask in the recorded stream, both in daylight and after night-mode changes. Resolve conflicts through an approved position or privacy control, not by silently disabling the mask.
A service plan matters, too. Note how a technician can reach the unit, inspect its mount, clean the lens, and check focus without unsafe access. Next step: record clearance, access, and privacy constraints before testing coverage.
Execution: Assess FOV, Image Detail, Lighting, and Authorized Corrections
FOV, or field of view, is the portion of a scene a camera can capture. Blind spot mapping compares that view with the approved coverage plan and checks whether enough image detail remains at useful distances. A wide view can show more area, but it spreads the camera’s pixels across a wider scene.
Calculate the view and pixel density
Horizontal FOV can be estimated with:
FOV = 2 × arctan(sensor width ÷ (2 × focal length))
Use the active sensor width and the camera’s actual focal length or lens setting. Digital zoom, cropping, and dewarping can change the usable view, so check the configured output rather than relying only on a lens label.
For a simplified flat-scene estimate, scene width at a target distance is:
Scene width = 2 × distance × tan(FOV ÷ 2)
Then estimate horizontal pixel density:
Pixel density = horizontal image pixels ÷ scene width
Use the target plane and distance that match the approved task. Do not assume the center of the image represents the whole scene. Perspective, lens distortion, camera angle, and image processing can make edge detail differ from center detail.
Worked example: A camera has a 5.6 mm active sensor width and a 4 mm lens. The estimated horizontal FOV is about 70 degrees. At 10 m, the simplified scene width is about 14 m. With 3,840 horizontal pixels, the estimate is about 274 px/m at that plane. This is above the 250 px/m identification reference, but it does not prove identification performance. Focus, motion, lighting, compression, and edge quality still matter.
Check the recorded image under real conditions
A coverage review should use the intended recording stream, not just a live monitor image. Check focus, resolution, shutter behavior, illumination, compression, and motion blur. Repeat the check in day and night conditions if the camera changes exposure, illumination, or infrared mode.
| Check | What to compare | Why it matters |
|---|---|---|
| FOV | Actual lens setting and recorded crop | The usable view may differ from the nominal lens view |
| Pixel density | Horizontal pixels ÷ scene width at target plane | Shows whether the image meets the chosen DORI target |
| Position in image | Center and relevant edges | Detail can vary across a lens view |
| Lighting and motion | Day, night, and moving subjects | Blur or low light can reduce usable detail |
| Privacy mask | Recorded stream in each mode | Masks may hide needed coverage or fail to protect a sensitive area |
If a check fails, assess authorized changes to lens, camera position, lighting, or supplementary coverage. Recheck support, cable routing, service access, privacy, and code constraints before making a change. A wider lens or overlapping view may help with coverage, but neither guarantees identification-quality detail. Next step: document each test condition and result against the approved target.
Verification: Test Recorded Coverage and Control Sensitive Findings
Verification confirms that the installed system meets its agreed goals in recorded footage and under relevant conditions. It also protects sensitive findings. Keep a detailed gap register restricted to authorized personnel, and record acceptance results without placing precise weak-point locations in public plans or general project reports.
Use a repeatable test plan. For each camera, compare the authorized view with the approved coverage plan, then check the required DORI density at the relevant target distances. Include the center and important image edges, plus day, night, and motion tests where those conditions apply.
Review recorded clips at the intended playback quality. A live image can look sharp while the recording is softened by a lower stream setting or compression. Confirm that the focus and exposure remain usable after day/night switching, and verify that privacy masks remain correctly placed in the recorded footage.
When the system does not meet the target, document the issue in a controlled record and evaluate approved corrections. Retest after changes. Keep acceptance results, camera settings, and service notes with the system documentation. Limit access to detailed coverage records and review that access periodically.
A useful acceptance record includes:
- Camera identifier and approved purpose
- Lens setting, resolution, and relevant recording settings
- Test date, lighting, and motion conditions
- Target distance and measured pixel-density estimate
- Privacy-mask check and recorded-stream result
- Pass, fail, corrective action, and retest result
Next step: sign off only against agreed objectives and retain detailed findings securely.
Worked Examples: How FOV Mapping Guides Design Checks
These examples show how to apply the measurements without publishing real site weaknesses. They are simplified planning exercises, not field test results. Actual camera performance depends on the installed equipment, image settings, scene, and test method. Keep any real site-specific gap details in an access-controlled record.
Example 1: Broad entrance view. In a planning exercise, a 1,920-pixel-wide stream covers an estimated 12 m-wide plane. The simplified density is 160 px/m. That sits above the 125 px/m recognition reference but below the 250 px/m identification reference. If the approved task requires identification detail across the full plane, the design needs further review. A narrower view, a different position, or additional authorized coverage may be considered, then tested in recorded footage.
Example 2: Privacy mask meets a useful view. A camera view includes an approved access area and a nearby sensitive area that must not be recorded. A mask is applied, then checked in both daytime and night-mode recordings. If the mask covers part of the required access view, or leaves the sensitive area visible after a mode change, the installation does not meet both goals. The team should assess an approved repositioning or privacy-control change and repeat the tests.
These examples illustrate why a drawn viewing cone is not enough. Mapping should link the approved task, measured image detail, privacy limits, and recorded evidence. Key takeaway: treat calculated FOV as a screening estimate, then validate the actual system.
Conclusion and FAQ
CCTV blind spot mapping is a structured way to compare authorized camera views with coverage and image-detail goals. Use lens and sensor data for estimates, DORI references for task targets, and recorded footage for verification. Apply local rules, respect privacy, and restrict detailed findings to people who need them.
What does CCTV blind spot mapping mean?
It is a controlled review of whether authorized cameras meet an approved coverage plan and image-detail goals. It uses FOV and pixel-density checks, followed by tests of recorded footage.
What does FOV mean for a security camera?
FOV means field of view: the horizontal or vertical area visible to the camera. Lens focal length and active sensor size affect it.
How do I calculate horizontal camera FOV?
Use 2 × arctan(sensor width ÷ (2 × focal length)). Use the active sensor width and actual lens setting, then confirm the result against the configured recorded image.
How do I estimate pixels per meter?
Divide the horizontal pixel count by the scene width at the target plane. Repeat at relevant distances and image positions.
What are the DORI pixel-density references?
Common reference densities are 25 px/m for detection, 62.5 for observation, 125 for recognition, and 250 for identification. They are design targets, not guarantees or legal minima.
Does a wider lens prevent blind spots?
Not by itself. A wider lens may show more area but spread available pixels across a wider scene, reducing detail at a given resolution.
Is a particular camera height or overlap required by code?
There is no universal requirement for camera height, overlap, or complete CCTV coverage. Check local adopted codes, project rules, equipment instructions, and privacy law.
Should I assess the live view or recorded footage?
Assess both when useful, but base acceptance on the recorded stream. Resolution settings, compression, focus, lighting, and motion can affect the recording.
Can a privacy mask create a coverage failure?
Yes. A mask can block part of an intended view, while removing it may expose a sensitive area. Check masks in recorded day and night footage and resolve conflicts through approved design changes.
Should I share a detailed blind-spot map?
Keep precise gap locations and other sensitive coverage findings restricted to authorized personnel. Public-facing records should not disclose exploitable details.
(This article was written by one of our staff writers, Garrett Vance. Visit our Meet the Team page.)
