-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Finish importing last few OS boundaryline boundaries relating to May 2019 local elections #567
Labels
Comments
/remind me "check 1019 BoundaryLine release" on 31st Oct 2019 |
@chris48s set a reminder for Oct 31st 2019 |
Also Kingston Bagpuize Ward (Vale of White Horse) |
Also Canterbury:
|
Codes should be:
those should be in the Oct BoundaryLine release |
all fixed, topojson layers regenerated |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From the ONSPD May 2019 release notes
https://www.arcgis.com/sharing/rest/content/items/4e39873ca62c432cbc3a71b55851c6fd/data
page 5
I've attached and corrected the GSS codes in EE, but I haven't updated the boundaries for these wards - I've just left them with the LGBCE provisional boundaries attached to those wards (with the correct codes) for now (in principle, I probably could have written a custom script to grab the boundary with code X from BoundaryLine and attach it to division Y, but I haven't bothered)
When the November BoundaryLine release appears, check that all of those areas now have the right codes attached to them, and use
boundaryline_import_boundaries
to replace the LGBCE boundaries for those last 8 areas with the Ordnance Survey versions: https://github.com/DemocracyClub/EveryElection/wiki/Boundary-Reviews-(2)#2-replace-temp-boundaries-with-os-boundariesThe text was updated successfully, but these errors were encountered: