DORI Calculation Walkthrough (2026): Step-by-Step EN 62676-4 Compliance for Real Projects
Three real worked examples — warehouse loading dock, parking-lot ANPR gate, and bank teller station — with the full EN 62676-4 pixel-per-metre arithmetic spelled out. By the end of this article you'll be able to compute DORI levels for any camera and target distance in your head, and you'll know exactly which camera-and-lens combination satisfies which DORI threshold.
Table of Contents
What you'll learn
Reading about DORI is fine. Calculating DORI on a real project is what actually wins bids and survives commissioning. This article is the hands-on counterpart to the conceptual DORI explainer. We pick three project archetypes that come up in roughly 80% of CCTV designs and we run the EN 62676-4 numbers through each of them, end-to-end, with the math visible. By the end you should be able to look at a camera datasheet, a lens choice and a target distance and know — within thirty seconds — which DORI level the design satisfies.
Why three examples and not one? Because each archetype stresses a different part of the calculation. The warehouse forces you to think about how DORI degrades with distance. The ANPR gate forces you to think about pixel headroom for plate readability. The bank teller forces you to think about face-recognition pixel density at close range with a constrained lens choice. Together they cover the calculation muscles you need for almost every design you will run into.
DORI math refresher — the formula in one paragraph
EN 62676-4 defines DORI in terms of pixels per metre at the target distance. The arithmetic is high-school geometry: the angular field of view of the lens projects onto a horizontal slice at the scene, and the camera's horizontal pixel count is distributed across that slice. The compact formula is:
The DORI pixel-per-metre formula
PPM = (focal_length_mm × image_width_pixels) / (sensor_width_mm × distance_m)
- focal_length_mm — the lens you have selected (e.g. 6mm, 12mm).
- image_width_pixels — the horizontal pixel count (e.g. 2560 for 4MP at 16:9).
- sensor_width_mm — the horizontal sensor dimension (1/2.8" ≈ 5.376mm; 1/1.8" ≈ 7.20mm).
- distance_m — the metres from the camera to the target.
Compare the result against the EN 62676-4 thresholds: 25 ppm Detection, 62 ppm Observation, 125 ppm Recognition, 250 ppm Identification. The 2025 amendment introduces OODPCVS modes that extend this vocabulary, but the underlying pixel arithmetic is identical.
Two practical notes before we hit the walkthroughs. First, sensor size is usually given as a fraction of an inch (1/2.8", 1/1.8", 1/1.2") — these are not literal inches but a legacy nomenclature from vidicon-tube cameras. Use the conversion table below or trust your calculator to handle the lookup. Second, the formula assumes a standard rectilinear lens. Wide-angle and fisheye lenses introduce barrel distortion that subtly changes the effective pixel density across the frame; for those, use the manufacturer's effective-focal-length figure rather than the nominal one.
| Sensor size | Horizontal mm |
|---|---|
| 1/3" | 4.80mm |
| 1/2.8" | 5.376mm |
| 1/2.5" | 5.76mm |
| 1/1.8" | 7.20mm |
| 1/1.2" | 10.67mm |
Walkthrough 1 — Warehouse loading dock
The setup. A logistics customer is fitting CCTV to a 25m-wide loading dock with one camera mounted on the building wall directly above the dock door, looking out into the yard. The selected camera is 4MP with a 1/2.8" sensor (2560 × 1440, 5.376mm horizontal) on a 6mm fixed lens. The question: what DORI level does this camera achieve at 10m, 20m and 35m from the wall?
The numbers
- PPM @ 10m = (6 × 2560) / (5.376 × 10) = 285.7 ppm → Identification (>250)
- PPM @ 20m = (6 × 2560) / (5.376 × 20) = 142.9 ppm → Recognition (>125)
- PPM @ 35m = (6 × 2560) / (5.376 × 35) = 81.6 ppm → Observation (>62)
The interpretation. A single 4MP-on-6mm camera covers the dock with three different DORI levels at three different ranges: Identification right at the door, Recognition mid-yard, Observation deeper into the loading bay. For a 25m-wide dock, every pixel along the dock face satisfies Recognition or better, which is the right threshold for "we know who picked up which container".
The design conclusion. If the customer needs Identification at 20m (for example, to read forklift driver IDs at full yard range), this camera is not enough — they need either a longer focal length (which sacrifices the wide near-door view) or a higher-resolution sensor (8MP on the same 6mm lens reaches Identification past 20m). The walkthrough makes the trade-off visible in numbers, which is exactly the conversation you want to have with the customer before the install rather than after.
Walkthrough 2 — Parking lot ANPR gate
The setup. A commercial customer wants automatic number-plate recognition (ANPR) at the entrance gate of an underground car park. The barrier is 5m from the camera mount. The selected camera is 8MP with a 1/1.8" sensor (3840 × 2160, 7.20mm horizontal) on a 12mm fixed lens. The question: does this combination meet Identification (250 ppm) at the gate, and how much margin is there?
The numbers
- PPM @ 5m = (12 × 3840) / (7.20 × 5) = 1280 ppm → Identification (>>250)
- PPM @ 10m = (12 × 3840) / (7.20 × 10) = 640 ppm → Identification (>>250)
- PPM @ 25m = (12 × 3840) / (7.20 × 25) = 256 ppm → Identification (just above 250)
The interpretation. At 5m the camera delivers 1280 ppm — over five times the EN 62676-4 Identification threshold. That headroom is not wasted. ANPR works robustly only when the plate is well-lit, well-angled and free of motion blur — having pixel headroom means the system tolerates the inevitable real-world degradation (rain on the lens, low sun, a slight tilt of the vehicle) without dropping below the readability threshold. A design that just clears 250 ppm in lab conditions usually fails in production.
The design conclusion. The 8MP-on-12mm choice is well-matched to a 5m gate with significant margin. If the same camera were mounted further back — up to roughly 25m — it would still satisfy Identification but with much less environmental tolerance. For a single-purpose ANPR camera, generous pixel headroom is the right design call rather than a wasteful one.
Walkthrough 3 — Bank teller station
The setup. A retail bank is upgrading the in-branch CCTV at the teller counters. Each teller window has a dedicated camera mounted on the back wall, 4m from the customer side of the counter. The selected camera is 6MP with a 1/1.8" sensor (3072 × 2048, 7.20mm horizontal) on an 8mm fixed lens. The question: does this satisfy 250 ppm Identification at the customer side of the counter for face-recognition use?
The numbers
- PPM @ 4m = (8 × 3072) / (7.20 × 4) = 853 ppm → Identification (>>250)
- PPM @ 6m = (8 × 3072) / (7.20 × 6) = 569 ppm → Identification (>>250)
- PPM @ 12m = (8 × 3072) / (7.20 × 12) = 284 ppm → Identification (just above 250)
The interpretation. The 6MP-on-8mm camera satisfies 250 ppm Identification at the teller counter with substantial pixel headroom. EN 62676-4 designates 250 ppm as the level at which an unfamiliar individual can be identified from the image — exactly the use case for face-recognition triggered by a flagged transaction. The same camera continues to satisfy Identification out to roughly 12m, which is more than the depth of any normal teller hall.
The design conclusion. At this geometry, mounting height and the angle to the customer's face matter more than additional pixels. A face viewed from a steep overhead angle is harder to identify than the same pixel count on a face viewed near-frontally — pixel density is a necessary condition, not a sufficient one. The walkthrough surfaces the right design conversation: focus the next iteration on mounting position rather than on camera spec.
EN 62676-4 thresholds reminder. The 250 ppm Identification threshold is the standardised boundary above which an unfamiliar individual can be reliably identified from the image. Local face-recognition algorithms commonly need substantially less to work, but the 250 ppm number is what survives evidentiary scrutiny in court — which is the bar a bank teller deployment is ultimately designed against.
Common mistakes
Three mistakes account for almost every "the math says yes but the install fails" conversation we have. Saving you the round-trip is a large part of why this article exists.
- Sensor size confusion. A 1/2.8" sensor is not 1/2.8 of an inch — it is the legacy nomenclature from vidicon tubes and corresponds to roughly 5.376mm horizontal. Substituting 9.07mm (the literal value of 1 inch divided by 2.8) into the formula is one of the most reliable ways to overestimate identification distance by a factor of two.
- Aspect ratio missing. A "4MP camera" can be 2560 × 1440 (16:9) or 2048 × 1536 (4:3). The horizontal pixel counts differ by 25%, and so does the resulting DORI distance. Always read the resolution from the datasheet — never assume an aspect ratio from the megapixel count.
- Wrong unit conversions. Mixing centimetres and metres, feet and metres, or millimetres and centimetres is the failure mode that survives the longest because it produces plausible-looking numbers. Use a calculator that is unit-aware (the CCTVplanner DORI calculator handles m and ft natively) and double-check the unit at every step.
- Datasheet thresholds vs EN 62676-4 thresholds. Some manufacturers publish "identification distance" using their own internal pixel-density target. Always cross-check whether the datasheet number assumes 100 ppm, 150 ppm or the EN 62676-4 standard 250 ppm — the difference can be a factor of 2.5x in distance.
How to verify automatically
Doing the math by hand is a great way to learn it. Doing the math by hand on every camera in a 40-camera project is a great way to introduce errors. CCTVplanner ships two free, browser-based tools that wrap exactly the formula above with the EN 62676-4 thresholds and the 65,000+ camera catalogue.
Two calculators that do the math for you
- DORI calculator — pick a camera and a target distance, get the achieved pixel density and DORI level.
- EN 62676-4 calculator — standards-aware lens recommendation including 2025 OODPCVS modes.
- Designer — full-project canvas where every camera is automatically scored against EN 62676-4 in the canvas, BOM and PDF deliverable.
For a multi-camera project, the designer is the right entry point. Place every camera on the floor plan, set the lens, and the canvas colour-codes which area satisfies which DORI level. Compliance flags surface in red anywhere a camera is asked to do more pixels per metre than its lens and resolution allow. The exported multi-page PDF carries the per-camera DORI level into the equipment table — the procurement officer reads the number you computed without having to recompute it.
For a deeper read on the standards-side update behind these tools, the EN 62676-4:2025 OODPCVS update article walks through the seven new mode labels that sit on top of classic DORI in 2026 EU procurement.
Frequently Asked Questions
What is the basic formula for DORI pixel density?
Pixels per metre at the target distance equals (focal_length_mm × image_width_pixels) divided by (sensor_width_mm × distance_m). The horizontal resolution is in pixels, the focal length and sensor width are in millimetres, and the target distance is in metres. The result is the pixel density at that distance, which you compare against the EN 62676-4 thresholds: 25 ppm Detection, 62 ppm Observation, 125 ppm Recognition, 250 ppm Identification.
Do I use the horizontal pixels or the total megapixels in the formula?
Always use the horizontal pixel count. A 4MP camera at 16:9 has 2560 × 1440 pixels — for DORI you take 2560, not 4,000,000. Using megapixels in the formula will silently overestimate pixel density by orders of magnitude. This is the single most common mistake and the one most likely to make a design fail commissioning.
Why do my numbers differ from the camera datasheet's 'identification distance'?
Manufacturers sometimes publish identification distances using their own proprietary thresholds rather than the EN 62676-4 250 ppm value. Always cross-check the assumed pixel-density target. A datasheet that says 'identification at 18m' might be assuming 100 ppm or 150 ppm rather than the standard 250 ppm — at 250 ppm the same camera would only reach about 7m. The math is correct, the assumption is what differs.
Does the lens choice or the resolution matter more?
They matter equally — pixel density is proportional to focal length divided by sensor width, and proportional to horizontal resolution. Doubling either roughly doubles the achievable identification distance. In practice, varifocal lenses give you flexibility to optimise per-camera, while resolution upgrades benefit every zone uniformly. The right answer for any given site is usually a combination: a smaller number of higher-resolution cameras with appropriately-chosen lenses.
How do I verify a DORI calculation without doing the math by hand?
Use a calculator that knows the EN 62676-4 thresholds and the camera catalogue. The CCTVplanner DORI calculator at /calculator/dori takes the camera and the target distance and returns the achieved pixel density and DORI level. The dedicated EN 62676-4 calculator at /en-62676-4-calculator wraps the same maths with standards-aware language including the 2025 OODPCVS modes. Both are free and require no install.
Related Articles
The four levels and what each one is for, before the math.
The arithmetic underneath every DORI and OODPCVS target.
The seven-mode taxonomy that sits on top of classic DORI in 2026.
Side-by-side comparison including DORI rendering and OODPCVS support.
Free-tier options that compute DORI per EN 62676-4 out of the box.
Step-by-step playbook including DORI threshold migration.