Type the address in the search box, then press ✦ Plan this lot. Everything below fills in by itself.
Your site
Two quick checks. Each thing we weren't sure about is listed; tap Show to see it on the map.
Exits
Parking rows we're unsure about
Rows found only from parked cars, not paint. Keep the real ones, delete the rest, or fix the stall count.
What should the cameras do?
How much of the lot? 95%
The last few percent are the expensive ones — the plan will tell you what each camera adds.
Which cameras?
Where do power and internet come from?
One point per building — the IT / electrical room the cables will run back to. Tap the button, then tap the spot on the map.
Places cameras, checks the result with an exact solver, then plans power and cabling. About a minute.
Manual plan
Tap + Add camera, then tap the map where the camera goes (it snaps to the nearest wall or pole). Drag the pin to move it, drag its orange dot to aim it. Coverage updates as you go. Add the power / internet points, then price it.
Model for new cameras: the first ticked camera in Needs (change it per camera in the list below).
The plan
To adjust: drag a camera to move it, drag its orange dot to aim it, ◀ ▶ to nudge. Anything you touch is locked and kept when you rebuild.
Documents
Save this site
Saved automatically in this browser after each build. Download a file to keep it or send it to someone.
Expert settings — standards, camera specs, costs, tuning and diagnostics. Changes apply on the next build.
1 Site
—paved sq ft
0buildings
0mounts
No property selected yet.
Search the address, center the property, click ✦ Plan this lot. Everything runs with defaults; change step 2 and Run optimizer to re-plan without re-fetching. Drag anything that's wrong; right-click a mount to remove it. P = light pole you added (Add a light pole), E/X = exit / crossing zones.
Advanced: individual steps
Drawing by hand: bottom bar → Draw ▾ → Lot outline / Building. Parcel mode adds/removes parcels by clicking.
2 Settingsdefaults = Vikram's standard
Monitoring = activity: people and cars moving, which happens in the drive aisles and at the exits. Parking = the stalls themselves. Monitoring-only keeps the stall rows out of the requirement, so cameras go where the movement is.
Cameras — the types we deploy (100°, 180° and the 180° floodlight, which always gets its own cable). Specs are editable: set processed W×H to the stream the pipeline actually uses
Reach ∝ processed width ÷ HFOV: the 180° Duo 2 on its 4608-px main stream reaches about two-thirds as far as the 4K 100° camera; on a 1536-px sub-stream it reaches a third as far again. Varifocal models get one profile per zoom stop.
Infrastructure & cost
Topology per head-end: switch → injector → Cat6 trunk (≤ max hop) → PoE passthrough at each cluster of ≤ 4 cameras. Cameras on other buildings or poles route at the off-building rate (trench / aerial). Set the head-ends with Power / net hub on the map.
Unit costs per camera model are in each camera's row above (edit there). Defaults from Vikram's Sep 11 pricing: injector route ≈ $150 per cluster + $25 switch.
Advanced
What the standards mean
A cell is covered when a camera has a clear line to it (buildings block), it is inside the lens's field of view, the camera looks down at it by ≥7° (so a parked car can't hide it), and the pixel density at that distance meets the standard. Density falls with distance: px/ft = (image width px ÷ horizontal FOV°) × 57.3 ÷ distance ft. DORI levels are the IEC 62676-4 definitions. Green = meets the selected standard; amber = Detect only; red = not seen.