Changed
- More planning applications now return a site centroid in
spatialand a full site boundary inspatialFeatures, as geometry extraction was added for additional local-authority data sources behind GET /v1/planning/{applicationIds}, GET /v1/planning/sources/{sourceIds} and POST /v1/planning/query. Records that previously had no site point will now also rank innearspatial queries. - Summary-field coverage improved across the same endpoints: more applications now populate
caseOfficer,decidedDate,receivedDate,addressandrelatedCases, which were previously null for the affected data sources. No fields were added or removed; this is a data-coverage improvement only.
Fixed
- Census ratios for Scotland geographies were computed against an incorrectly detected denominator, leaving most Scotland leaf ratios null or wrong. Per-topic totals are now synthesised correctly, so ratio values returned by GET /v1/census/datasets/{datasetCode}/categories/{categoryCode}, POST /v1/census/datasets/{datasetCode}/profile, POST /v1/census/datasets/{datasetCode}/rollup and the choropleth
tiles/breaksendpoints are now accurate for Scotland. - Census ratio values are now clamped to the valid
[0, 1]range, preventing out-of-bounds values from reaching choroplethbreaksandtilesresponses.
Affected endpoints
- GET /v1/planning/{applicationIds}
- GET /v1/planning/sources/{sourceIds}
- POST /v1/planning/query
- GET /v1/census/datasets/{datasetCode}/categories/{categoryCode}
- POST /v1/census/datasets/{datasetCode}/profile
- POST /v1/census/datasets/{datasetCode}/rollup
- GET /v1/census/tiles/{datasetCode}/{geotype}/{tile}/{categoryCode}
- GET /v1/census/breaks/{datasetCode}/{geotype}/{categoryCode}