CCTV Camera Placement Designer

Place cameras on a scaled site plan or a satellite map, in 2D and 3D, and see the coverage they deliver as pixel density in px/m.

Pro v1.8.0 ● Live 2 standards

Included in the 14-day Pro trial on every new account. No credit card.

Open a saved design or start a new site.

Walkthrough

See it working

Open a saved design or start a new site.
Step 02

Import the site plan

Import a floor plan or site layout from a PDF page or an image. Plan images are kept on the device that imported them, so opening the design elsewhere asks for the drawing again.

Step 03

Set the scale

Click two points a known distance apart, or fit the plan to a grid of known pitch. An unscaled level is flagged until this is done.

Walls with heights and openings.
Zones with their own requirements.
Placing and aiming a camera.
Step 07

Read the pixel density

The plot shows px/m across the level, coloured at the DORI thresholds. Place a person marker to see which camera covers that spot, at what pixel density, with a face mock-up at that resolution.

Step 08

Check the gaps and shadows

Areas no camera reaches and areas hidden by walls are highlighted, and each zone reports the share that meets its requirement. A camera can be fitted to a zone: its aim, tilt and zoom are searched together, counting the other cameras.

The design on satellite imagery.
Camera frustums against walls in 3D.
Step 11

Check plates, PTZs and night

Number plate zones report the share that can actually be read, PTZs are credited only when parked on a view, and a night assessment limits each camera to the light available. A design can be judged by day and at night together.

Camera schedule.
Step 13

Issue the report

Download a PDF report with the scaled plan, the camera schedule, the result for each zone and a statement of what the assessment does not cover, and an installer and acceptance sheet for each camera.

Open a saved design or start a new site.

Overview

Design camera coverage to DORI and pixels per metre

Camera layouts are often argued with a coverage cone drawn over a floor plan. A cone shows where a camera points, but not whether the image at a given spot has enough pixels to recognise or identify someone, and it assumes the camera can see through walls.

Read the full overview

The CCTV Camera Placement Designer works in pixel density instead. For each point it calculates how many pixels fall across a metre of a vertical target, from the camera's field of view and recorded image width. That is the measure the DORI criteria and most client specifications use, so each area of the site can be checked against the level it needs. Line of sight is tested in three dimensions against the walls, fences, glazing and openings you draw, so a low wall only blocks a camera where the sightline actually passes through it.

The same design can be viewed on the plan, over satellite imagery and in 3D. Because pixel density alone does not guarantee a usable image, the designer also checks that a camera sees a face rather than the top of a head before it credits Recognise or Identify, checks the angle a number plate is viewed from, does not credit a PTZ until it is parked on a view, and can assess the design at night against the available light. The design report states what was and was not assessed.

Capabilities 9

Pixel density, not a coverage cone

Coverage is calculated as px/m on a vertical target at each point and coloured at the DORI thresholds. Each camera also shows the distance at which each DORI level is reached and the blind spot directly beneath it, and a person marker shows how a face at that spot would look at the resolution delivered.

Faces, not the tops of heads

Recognise and Identify are credited only where a camera can see the face. A camera mounted high over a doorway can have the pixels for Identify and still see only the top of a head, so the designer shows where each camera starts to see faces and judges Recognise and Identify zones on that. Where you say which way people face, at a door or a till, a camera behind them or off to the side is not credited with their faces either.

Line of sight against real walls

Walls and fences carry a material, thickness, height and underside, and doors, windows and gates are cut into them as openings. A sightline is blocked only where it passes through solid wall in three dimensions, while mesh and tinted glass are reported as degraded rather than clear or solid.

Plans, maps and buildings

Import a site plan from a PDF page or an image and scale it from a known distance or by fitting it to a grid. A design can also be pinned to satellite imagery, where building outlines can be imported from OpenStreetMap as a starting point to check and correct.

Field of view from real optics

A datasheet field of view is used as printed. Where only focal length and sensor format are known, the angle is derived and marked as derived. Fisheye lenses are modelled with their own projection rather than as very wide ordinary lenses.

Generic and catalogue cameras

A generic library covers common resolution and lens classes, so a layout can be designed before a model is chosen. Models from the noIM₃ component catalogue can be used where their datasheet optics can be read, and you can type in any figures yourself.

Zones carry the requirement

Draw the areas the design will be judged on and give each its own pixel density target. Results are reported zone by zone, because a design is signed off area by area rather than on a site-wide percentage.

Plates, PTZs and night

Number plate zones are checked against the horizontal and vertical angle the plate is seen from, not just pixel count. A PTZ is only credited when it is parked on a view, and a night assessment limits each camera to the reach of the ambient light or its illuminator, with motion blur reported for the assumed shutter. A design can be judged by day and at night together, with each zone allowed to ask for less after dark.

Schedule and report

The camera schedule lists each camera's resolution, optics, DORI distances, power and PoE class, and can be copied for a spreadsheet. The PDF design report includes the scaled plan, the schedule, the result for each zone and a statement of the limits of the assessment. A second PDF gives each camera an installer and acceptance sheet: how to set and aim it, and numbered test spots with the pixels a board held there must span.

Inputs and outputs

What goes in, what comes out

Inputs 12

  • Site plan as a PDF page or image
  • A known distance or grid pitch for scale
  • Walls and fences with material, thickness and height
  • Doors, windows and gates
  • Target zones with a required pixel density
  • Cameras from the generic library or the component catalogue
  • Mounting height, bearing, tilt and zoom for each camera
  • Site location and plan rotation for the map view
  • Daylight, night, or day and night assessment, and site illuminance
  • What each zone needs at night, where it differs from the day
  • Number plate direction for plate reading zones
  • Whether each PTZ is parked on its view

Outputs 16

  • Pixel density plot in px/m
  • DORI distances and blind spot for each camera
  • Where each camera starts to see faces
  • Share of each zone meeting its requirement, by day and at night
  • Coverage gaps and wall shadows
  • Camera, pixel density and face mock-up at a chosen spot
  • Readable share of a number plate zone
  • Zone results with and without uncommitted PTZs
  • Night result for each camera, including illuminator reach
  • Motion blur at the assumed shutter
  • Camera schedule with resolution, optics, power and PoE class
  • Plan, satellite map and 3D views
  • PDF design report
  • Installer and acceptance sheet for each camera, with test spots and pass figures
  • Suggested aim, tilt and zoom to fit a camera to a zone
  • When the sun is in each camera's picture, for a site pinned to a map

Standards & methodology

  • IEC/EN 62676-4 DORI criteria, as commonly published
  • IEEE 802.3 PoE classes

Use cases

When to use this tool

  1. 01Showing that a retail layout meets an Identify requirement at the tills
  2. 02Checking perimeter coverage on a yard or depot
  3. 03Siting number plate capture on a car park lane
  4. 04Finding the columns, plant and walls that will shadow a site
  5. 05Answering a client specification written in px/m or DORI terms
  6. 06Setting mounting heights to avoid a blind spot over a doorway
  7. 07Finding which cameras fall short after dark
  8. 08Issuing a coverage report for a tender or handover

FAQ

Frequently asked questions

Not here? Ask us

What is pixel density and why not just draw a coverage cone?

Pixel density is the number of recorded pixels across a metre of a target at its distance from the camera. A cone shows where a camera points but not whether the image is good enough to recognise anyone, and it ignores walls. Pixel density is the measure the DORI criteria and most specifications use.

Which DORI figures does it use?

Detect 25 px/m, Observe 62.5, Recognise 125 and Identify 250, as commonly published for IEC/EN 62676-4, plus a separate band for number plate work. Every threshold can be changed for a zone when a client specification differs. The number plate and face viewing angles it checks come from ANPR siting practice and camera vendor guidance, not from IEC/EN 62676-4.

Does it take walls into account?

Yes. Line of sight is tested in three dimensions against the walls and fences you draw, using their heights. Openings take their own material, so a camera sees through clear glazing and open doorways. Anything you do not draw is treated as clear, so draw every wall that could get in a camera's way.

Can I use a PDF floor plan, or work without one?

You can import a page from a PDF or an image and scale it from a known distance or a grid. You can also draw directly on the metric grid or work over satellite imagery.

Why does my number plate zone have the pixels but say it cannot be read?

A plate is a flat panel, so viewed from too far to the side or too steeply from above its characters foreshorten, and a reflective plate may not return infrared to the camera. The zone checks both angles, and the usual cause is a camera mounted too high or too close to the lane.

Why does a zone right under my camera fall short of Identify when it has the pixels?

Because the camera is looking down on the tops of heads. Recognise and Identify need the face, so where a camera sits too steeply above a face it is credited as Observe at most. Mounting the camera lower, or further back from the area it has to cover, lets it see faces.

Why is my PTZ not counted toward a zone?

A PTZ can be driven elsewhere, so a requirement it meets on a tour is only met while nobody moves it. It is credited like a fixed camera once you mark it as parked on its view, and zones it serves show results with and without it.

Does it model low light?

Yes, as a light budget rather than a full simulation. At night each camera is credited only as far as there is enough ambient light or illuminator reach, with sensitivity corrected for the lens aperture. A design can be judged by day and at night together, each zone against what it needs then, such as Identify by day and Recognise after dark. Minimum illumination figures are the manufacturer's own and are not comparable between brands.

Does a coverage result mean the system will identify somebody?

Not on its own. Pixel density is a necessary condition, but image quality also depends on backlight, focus, compression and the condition of the camera, which are settled on site. Thermal cameras are modelled for geometry only and suit detection rather than recognition. The report sets out these limits.

Free for 14 days

Included in the 14-day Pro trial on every new account. No credit card.