Data methodology

Useful data begins with visible evidence.

Our job is not to hide the public sources. It is to make them cleaner, connected, historical and easier to interrogate.

01

What the current beta contains

The live application is built from the July 2026 Renewable Energy Planning Database snapshot published by the Department for Energy Security and Net Zero. It contains all 2,858 rows whose technology is recorded as Wind Onshore or Wind Offshore.

Source-complete, enrichment-incomplete

The beta is complete for wind rows in this REPD snapshot. Selected Great Britain projects also have reviewed Elexon BM-unit mappings; unmatched projects remain explicitly unavailable. Companies House ownership and broader grid enrichment are not yet complete.

02

Source hierarchy

When sources disagree, we do not silently choose the most convenient value. We retain the evidence, source date and observation date, then apply a documented confidence rule.

  1. Official registersDESNZ, Elexon, NESO, LCCC and planning authorities.
  2. Project evidenceDeveloper publications, consent documents and statutory filings.
  3. Manufacturer evidenceOfficial turbine specifications and product documentation.
  4. Derived metricsCalculations made from explicitly identified source values.
03

Normalisation and identity

Source values are preserved, then normalised into consistent types. Dates use ISO format internally. Capacity remains in MW. British National Grid coordinates are converted to WGS84 for mapping; Northern Ireland uses the Irish Grid transformation.

Project names become stable, unique URLs. A missing project name is not dropped: the source reference is used as an explicit placeholder. Company labels are currently grouped exactly as published and are not yet treated as verified legal entities.

04

Confidence and measurement

Official

Copied or normalised from an authoritative register.

Verified

Matched across two or more credible sources.

Estimated

Calculated using a published, reproducible method.

Unavailable

No defensible value has been established.

Generation remains unavailable until a project has a human-reviewed BM-unit mapping and a complete reporting period. Published output is the sum of Elexon B1610 settlement-period MWh, not an estimate or live MW reading. Capacity factor is separately derived only when a reviewed capacity basis covers the whole period. Values remain subject to Elexon settlement revision.

Mapping candidates use six separately stored signals: name, operator/lead party, capacity, GSP location, onshore/offshore technology evidence and official identifiers. Automation never promotes a candidate to reviewed. One BM unit cannot be allocated above 100% across overlapping reviewed mappings.

UOU2T14D Output Usable, PN/QPN/MILS/MELS, BOALF and REMIT are presented as separate MW/event context. They are not added to B1610 and are not automatically described as downtime, underperformance or curtailment. National actuals use AGWS/B1630 and forecasts use WINDFOR; forecast error compares a matching hourly actual with the latest forecast published before delivery where available.

Elexon covers the Great Britain balancing mechanism. It does not cover Northern Ireland and cannot provide complete measured coverage of every REPD wind project, including generation that is embedded or not operationally metered through a mapped BM Unit.

05

Refresh and change history

REPD is scheduled for quarterly ingestion. The July 2026 snapshot is the baseline. Future imports will create field-level changes for material values including capacity, turbine count, status, company roles and milestone dates.

Never overwrite history silently Keep source and observation dates Review ambiguous entity matches
06

Licensing and attribution

Source-specific licences

REPD-derived pages use the Open Government Licence v3.0. Measured generation is attributed to the Elexon Insights Solution under the BMRS Open Data Licence.

OpenStreetMap-derived data is not mixed into the project database; the map baselayer has its own visible attribution. Protected exports identify their included source and attribution.