Skip to content
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

Closed
chris48s opened this issue Jul 9, 2019 · 7 comments

Comments

@chris48s
Copy link
Member

chris48s commented Jul 9, 2019

From the ONSPD May 2019 release notes
https://www.arcgis.com/sharing/rest/content/items/4e39873ca62c432cbc3a71b55851c6fd/data
page 5

The 2019 ward changes are included on the ONSPD from May 2019. Unfortunately, the draft release of OS Boundary-Line includes errors for a number of wards:

E05002732 – Stretham – should be E05011571
E05005276 – Garrison – should be E05012199
E05012199 – Sharoe Green – should be E05012208
E05005857 – Mundesley – should be E05011847
E05005863 – Roughton – should be E05011853
E05005865 – St Benet’s – should be E05011854
E05006336 – Seamer – should be E05012387
E05009795 – Warwick Saltisford – should be E05012630

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-boundaries

@chris48s
Copy link
Member Author

chris48s commented Jul 9, 2019

/remind me "check 1019 BoundaryLine release" on 31st Oct 2019

@reminders reminders bot added the reminder label Jul 9, 2019
@reminders
Copy link

reminders bot commented Jul 9, 2019

@chris48s set a reminder for Oct 31st 2019

@chris48s
Copy link
Member Author

Also Kingston Bagpuize Ward (Vale of White Horse)
has code E05009767 but should be... ???
(to follow up with Ordnance Survey)

@chris48s
Copy link
Member Author

Screenshot at 2019-07-11 12-52-45

@chris48s
Copy link
Member Author

Also Canterbury:

  • Barton has code E0501039 but should be ??
  • Chartham & Stone Street has code E05010394 but should be ??

@chris48s
Copy link
Member Author

chris48s commented Aug 7, 2019

Codes should be:

  • E05012990 - Barton
  • E05012991 - Chartham & Stone Street
  • E05012992 - Kingston Bagpuize

those should be in the Oct BoundaryLine release

@chris48s
Copy link
Member Author

all fixed, topojson layers regenerated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant