DAYLIGHT·API

ADaylight & sunlight screening for UK planning

Numbers you can put in front of a planning officer.

The BRE 209 screening battery — VSC, daylight factor, no-sky line, sunlight hours, garden amenity, overshadowing — computed on your real building geometry, and cross-checked against Radiance with the error bounds published.

0708091011121314151617 21 JUN 21 MAR / SEP 21 DEC E 90°135°S 180°225°W 270° 15°30°45°60°
SUN PATHS — LONDON 51.5°NCOMPUTED BY THIS ENGINE · DEV vs SPA ≤ 0.011°
≤ 0.13 pp
VSC dev. vs Radiance, obstructed cases
≤ 0.09 pp
3D mesh ray-cast vs Radiance
45/45
Independent checks passing
0.011°
Solar position vs NREL SPA

Plus Part B, live against Radiance and IfcOpenShell: annual sDA/ASE matches Radiance two-phase exactly on the reference case; mesh and IFC per-point VSC agree to ≤ 0.27 pp on a real building; the reflected-light term is characterised and defaulted off.

BThe test battery

Every test a daylight & sunlight report contains

BRE 209 splits the work into daylight (sky) tests and sunlight (sun) tests. So do we — each verb below is one API call on your geometry, most of them fast enough to run on every massing option.

TestFamilyWhat it answersBRE 209Status
vsc / vsc-geomDaylightVertical sky component at a neighbour's window — analytic walls or full 3D mesh§2.2Live
daylight-factor / df-avgDaylightRoom daylight factor — sky component and the Lynes average-DF method§2.1Live
df-gridDaylightPer-point DF across the working plane — mean, median, % above target, heatmap data§2.1.12Live
nslDaylightNo-sky-line contour — which part of a room sees any sky at allApp CLive
apshSunlightAnnual & winter probable sunlight hours at a window — plus the §3.2 before/after verdict on whether a development costs a neighbour noticeable sunlight§3.2Live
sun-amenitySunlightThe 2-hour / 50%-of-area garden test on 21 March§3.3Live
overshadowSunlightTransient shadow plots at chosen hours and dates§3.3.17Live
annualDaylightAnnual sDA / ASE on a grid with EPW weather and four sky modelsLive
glare-verdict / ocular-hazardSunlightDGP glare class (EN 17037) and SGHAT specular-reflection ocular safetyLive
mesh-importGeometryOBJ / glTF / IFC upload — store-nothing: analysed in memory, deleted after the replyLive

Every verb above is live and cross-checked against Radiance and published references — see Sheet 02 §D.

CWorked example

The rear-extension question, answered in four calls

Neighbour existing dwelling Proposed extension · 3.0 m sky lost to extension 25° check Window centre · 1.5 m AFL · faces the garden Section · not to scale
VSC · before39.60 %
VSC · with extension29.56 %
Ratio to former value0.746
BRE test — ≥ 27 % or ≥ 0.8 × formerPASS on ≥ 27 %
Garden 2-hour area · 21 Mar87.5 % → 65.6 % PASS

Real output from the validated engine on this geometry. The same before/after pair drives the §3.2 sunlight verdict at the window — annual and winter APSH, and whether the neighbour loses noticeable sunlight. Change the extension depth and re-run in seconds — that's the point: screen every option before the consultant's assessment, not after refusal.

DWho this is for

Screen early. Assess once.

A full daylight & sunlight assessment costs £800–2,500 and lands after design freeze. Failing it means redesign at ten times that. This API exists so the first time your scheme meets the BRE numbers isn't the last week before submission.

Architects & designers — test every massing option against the neighbours' windows while it's still cheap to change. Planning consultants — pre-screen applications and objections with defensible numbers. Developers — feasibility on a site in an afternoon, not a fortnight.

The honesty line

This is a screening tool, not a certified daylight & sunlight assessment. Planning authorities and courts expect assessments from a qualified consultant taking professional responsibility. What we provide: the same physics, validated in the open, at design speed — so the certified assessment holds no surprises. Our methodology, references and error bounds are public on Sheet 02.

EAccess

Two ways in

RouteWhat you get
APIEvery verb over HTTPS — JSON in, JSON out. IFC / glTF / OBJ upload, store-nothing. Grids sized for heatmaps. See the API sheet.
Screening report ComingThe full battery on your site, as a document: per-window VSC, DF grids, sunlight hours, amenity, methodology appendix with citations.

Enterprise & evaluation — talk to us directly

We onboard practices and consultancies one to one: an evaluation key, and your first study run with you on your own geometry. Tell us the practice, the kind of schemes you screen, and the geometry format you work in — IFC, glTF or OBJ — and we'll set you up. hello@kairoico.com