{"id":13026,"date":"2026-09-14T07:35:00","date_gmt":"2026-09-14T05:35:00","guid":{"rendered":"https:\/\/www.lukaswojcik.com\/blog\/?p=13026"},"modified":"2026-10-26T13:27:56","modified_gmt":"2026-10-26T12:27:56","slug":"tutorial-turning-a-floor-plan-into-a-camera-layout-with-lens-and-mounting-height","status":"publish","type":"post","link":"https:\/\/www.lukaswojcik.com\/blog\/en\/cctv\/tutorials-en-cctv\/tutorial-turning-a-floor-plan-into-a-camera-layout-with-lens-and-mounting-height\/","title":{"rendered":"Tutorial: Turning a Floor Plan into a Camera Layout with Lens and Mounting Height"},"content":{"rendered":"

A camera layout connects each position to a clear task: following activity across a yard, capturing characteristics at a gate or recognizing a known person at an entrance. That task determines the required framing and detail. Resolution, lens and mounting position follow from those requirements.<\/p>\n

Calculations narrow the choice of suitable configurations. Whether the recording actually performs the task requires testing with movement, difficult lighting and the stream intended for recording.<\/p>\n

\"Camera
Pixel density states how many image pixels cover one metre of the observed area. A calculated pixel density is not an identification guarantee. Lens, viewing angle, lighting and compression must jointly meet the actual task.<\/figcaption><\/figure>\n

1. Task and standard edition<\/h2>\n

The familiar DORI values belong to the older IEC 62676-4:2014 model: Detect 25, Observe 62.5, Recognize 125 and Identify 250 pixels per metre. These numbers do not form a uniform doubling sequence. DORI remains present in datasheets and design tools.<\/p>\n

The second edition, IEC 62676-4:2025, was published on 9 October 2025. The current Axis explanation lists seven detail levels. Keeping the original English names avoids confusion with the older DORI labels:<\/p>\n
IEC 62676-4:2025<\/th>px\/m<\/th><\/tr><\/thead>
Overview<\/td>20<\/td><\/tr>
Outline<\/td>40<\/td><\/tr>
Discern<\/td>80<\/td><\/tr>
Perceive<\/td>125<\/td><\/tr>
Characterize<\/td>250<\/td><\/tr>
Validate<\/td>500<\/td><\/tr>
Scrutinize<\/td>1500<\/td><\/tr><\/tbody><\/table>\n

Characterize concerns visible characteristics such as gait and behaviour. Validate concerns checking known persons; Scrutinize targets a much more confident identity assessment. These are task categories for human evaluation, not success guarantees.<\/p>\n

In this model, 250 px\/m belongs to Characterize, not to a general promise of identification. The plan must record the edition, specific task and numerical target together. These levels concern human interpretation of visible-light images; automated analytics and thermal imaging need suitable separate requirements.<\/p>\n

Meeting a pixel target does not guarantee a usable face or licence plate. Viewing direction, occlusion and image quality remain decisive. The 250 px\/m target below is an example for calculation, not a general recommendation for every identification task.<\/p>\n

2. Test areas on the floor plan<\/h2>\n

A scaled plan records target areas, possible routes, obstructions and mounting positions. A passage may need a detailed view while another camera records activity across the yard. The requirements determine the number and placement; no fixed rule of two or three cameras follows.<\/p>\n

Each target area has a near and a far boundary. Lighting, low sun, glass, reflections and potential occlusion also matter. Direction and shielding can reduce backlight. Wide Dynamic Range (WDR) aims to keep detail visible in both bright and dark parts of a scene. WDR may help but needs testing and can itself introduce motion artifacts, depending on the method. A generic gain of one or two stops is not a reliable device specification.<\/p>\n

Unwanted areas such as neighbouring windows belong in the initial planning. Technical coverage alone does not establish permission to capture an area.<\/p>\n

3. Scene width and pixel density<\/h2>\n

The following relationships describe a simplified distortion-free model. W<\/code> is scene width in metres, d<\/code> the axial distance to the target plane, S<\/code> active sensor width and f<\/code> focal length in matching units. N<\/code> is the horizontal pixel count of the image actually used, and P<\/code> is pixel density. HFOV<\/code> means horizontal field of view; the tangent function must use the intended angle units.<\/p>\n

Text<\/span>