Vepler logo
v5.10.0

Scottish census profiles, explicit crime coverage, and sharper listing location

Census area profiles resolve Scottish geography codes, aggregated crime metrics document their England-only coverage, and listings pin to a dwelling only when the evidence uniquely identifies it.

Changed

  • Census area profiles at POST /v1/census/datasets/{datasetCode}/profile resolve Scottish geography codes: data-zone and intermediate-zone requests are built from their constituent output areas, with counts summed and proportions computed from the aggregate rather than averaged. Same request, same response shape; the geographyCode you request is the one returned.
  • Listing location matching is more precise: a listing is pinned to a dwelling only when the evidence uniquely identifies that dwelling, so more /v1/listings responses resolve to the correct address. No contract change.
  • GET /v1/safety/geography/metrics documentation now states its coverage explicitly: aggregated crime metrics cover England only, and codes in Wales, Scotland or Northern Ireland return an empty data array. Incident-level data for England and Wales remains available via GET /v1/safety/crime.

Removed

  • The violent_crime category from GET /v1/safety/geography/metrics responses. If you filtered on it, use violence_and_sexual_offences, which carries the aggregated crime data for that category.