Skip to content

Welsh Community Reviews

Jump to bottom
Will de Montmollin edited this page Jul 13, 2026 · 5 revisions

Intro

Discovery

Data

Process

Do the following locally, recording the final command for use on production:

  1. Check the shapefile in QGIS. We're getting these from the DBCC directly and so far they've had some issues. Some things to look out for:
    • invalid geometry: Use the check validity algorithm in the toolbox and, if necessary, fix geometries.
    • too many wards: Make sure that the file only contains electoral wards and doesn't have community wards. Some files have had a field name like "community" but the feature names and boundaries are for the electoral wards.
    • boundaries haven't changed: Make sure that the wards in the file actually have the 'consquential changes' applied. I did this by comparing the the previous boundaries.
  2. Set end date on the previous division set.
  3. Manually create a new division set in admin for the Community Review:
  4. Copy the divisions from the previous division set to the new one using python manage.py copy_divisions <old_id> <new_id> --no-geographies
  5. Upload the shapefile to the correct s3 bucket, e.g. "s3://ee.boundary-reviews.production/swansea/The County of Swansea (Communities) Order 2026/"
  6. Use import_lgbce to try and import the boundaries, creating and uploading a name_map.json, if necessary, e.g. python manage.py import_lgbce -s 'pembrokeshire/The County of Pembrokeshire (Communities) Order 2026/PEMBRO_1_fixed.zip' PEM
  7. Check that the boundaries look good by generating the pmtiles file using update_pmtiles --divset-ids <new_id>.

If it looks good locally, the shapefile and optional name_map is uploaded to s3, and you've got the commands ready to go, then create repeat steps 2-7 on production.

Clone this wiki locally