How Civic calculates its results.

Postcode and location

Postcodes are uppercased, whitespace-normalised and validated before an exact ONS Postcode Directory lookup. Returned coordinates are the WGS84 postcode centroid; LSOA, ward and local-authority identifiers come from the same loaded release.

Fire incidents

Incidents are selected when their published point falls within the bounded radius of the postcode centroid and requested rolling period. Fire and dwelling-fire totals use LFB incident-group and property-category fields; the annual series groups by calendar year.

Fire appliance response

First-appliance response uses joined mobilisation rows where pump order is one and the publisher supplies an attendance duration. Median and 90th percentile are PostgreSQL continuous percentiles.

Five-year results retain row-level lineage and cite each incident and mobilisation release represented in the calculation.

Recorded crime

Postcodes resolve to LSOA. The latest total covers the 12 source months ending at the latest complete month; the comparison is the preceding 12 months. Year-over-year change is (latest − previous) / previous × 100 and is null when the previous total is zero. Classification regimes remain explicit.

Road safety

STATS19 collisions are selected by published point, radius and collision date. Severity follows the Department for Transport codes.

Planning

Planning Data entities must intersect the ONSPD postcode centroid. Empty results do not prove an absence of constraints. Successful responses are cached for 24 hours; an upstream failure degrades only the planning section.

Composed profiles

Area profiles reuse the same five-year fire and roads calculations, crime periods, location resolution and planning adapter as the atomic tools. Comparisons apply identical metrics to two to five postcodes and never rank or recommend an area.