Changed
- More planning applications return a site centroid in
spatialand a full site boundary inspatialFeatureson GET /v1/planning/{applicationIds}, GET /v1/planning/sources/{sourceIds} and POST /v1/planning/query, covering more local-authority data sources. These applications also rank innearspatial queries. - More applications populate
caseOfficer,decidedDate,receivedDate,addressandrelatedCasesacross the same endpoints. No fields were added or removed.
Fixed
- Census ratios for Scotland geographies are computed against each topic's own total, so leaf ratios for Scotland are populated on GET /v1/census/datasets/{datasetCode}/categories/{categoryCode}, POST /v1/census/datasets/{datasetCode}/profile, POST /v1/census/datasets/{datasetCode}/rollup and the choropleth
tilesandbreaksendpoints. - Census ratio values always fall within
[0, 1]in 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}