Open chris48s opened 5 years ago
/remind me "check Oct BoundaryLine release - does it have GSS codes for CEDs?" on 31st Oct at 10:30am
@chris48s set a reminder for Oct 1st 2018
/remind me "check Oktober BoundaryLine release - does it have GSS codes for CEDs?" on 31st Oct
@chris48s set a reminder for Oct 31st 2018
:wave: @chris48s, "check Oktober BoundaryLine release - does it have GSS codes for CEDs?"
/remind me "check 0519 BoundaryLine release - does it have GSS codes for CEDs?" on 13th May 2019
@chris48s set a reminder for May 13th 2019
:wave: @chris48s, "check 0519 BoundaryLine release - does it have GSS codes for CEDs?"
Not in the May 2019 boundaryline release either..
I guess at some point we probably need to attempt a name matching exercise on the mashup of OS and LGBCE data we've got and the ONS codes, but the next major elections using CEDs are scheduled for 2021 which makes this easy to carry on ignoring for a bit..
/remind me "check 1019 BoundaryLine release - does it have GSS codes for CEDs?" on 31st Oct 2019
@chris48s set a reminder for Oct 31st 2019
(loosely) related issue:
Ahead of the 2021 County Council elections, there are some boundary changes we need to account for which are defined in Community Governance Reviews e.g:
We've got the usual issue here that the updated boundaries won't be in BoundaryLine until the May 2021 release, but in the cases where the CED changes mirror a change to the district wards and we've already applied the ward boundary changes, we can probably create correct ad-hoc boundaries for the CEDs as a union of the ward boundaries ahead of time.
still not in BoundaryLine Oct 2019
Still not in BoundaryLine Oct 2020
Useful sql for when tackling this https://github.com/DemocracyClub/EveryElection/issues/191
Currently CEDs in Every Election either have a temporary id we've made up, or in some cases we assigned them a unit_id. OS unit_ids have the unhelpful property that they are not consistent across releases. The same unit_id may refer to 2 quite different areas in 2 different releases. Example:
https://mapit.mysociety.org/code/unit_id/44017.html?generation=30 https://mapit.mysociety.org/code/unit_id/44017.html?generation=31
This makes it a bad id for us to use. Recently the ONS have started assigning CEDs a GSS code using the
E58
prefix: http://geoportal.statistics.gov.uk/datasets/county-electoral-division-may-2017-names-and-codes-for-england but they aren't in BoundaryLine yet.Right now this isn't high priority because the next major elections using CEDs aren't for a few years, but it would be useful to be able to attach codes to the CEDs we've imported from LGBCE and replace the boundaries with the ones from BL before the next major County-level elections.
The next thing to do is check the Oct BL release and see if the
E58
GSS codes have popped up in the CED layer.