-
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
The Leeds (Electoral Changes) Order 2018 #366
Comments
/remind me "check Oktober BoundaryLine release - does it have updated Leeds boundaries?" on 31st Oct |
@chris48s set a reminder for Oct 31st 2018 |
👋 @chris48s, "check Oktober BoundaryLine release - does it have updated Leeds boundaries?" |
Oct Boundaryline probably asks more questions than it answers Horsforth and Otley & Yeadon appear with the new GSS codes ( The other 4 appear with the old GSS codes but 2 of them have different boundaries than they did in the May release (which shouldn't happen). I've updated Horsforth and Otley & Yeadon to the new GSS codes. I've imported the boundaries as published in the Oct release using:
but I probably need to check in on these again in the May release. |
/remind me "check 0519 BoundaryLine release - does it have updated Leeds codes?" on 13th May 2019 |
@chris48s set a reminder for May 13th 2019 |
👋 @chris48s, "check 0519 BoundaryLine release - does it have updated Leeds codes?" |
AFAIK this is all accounted for in the relevant division sets now https://elections.democracyclub.org.uk/admin/organisations/organisationdivisionset/513 |
May 2018 BoundaryLine release included the boundaries/codes for the boundaries defined based on LGBCE recommendations in The Leeds (Electoral Changes) Order 2017:
These ward names appear in http://geoportal.statistics.gov.uk/datasets/wards-may-2018-uk-bfc with new GSS codes:
which will be the new boundaries defined in The Leeds (Electoral Changes) Order 2018. Hopefully these will appear with the revised codes/boundaries in the October BoundaryLine release.
The text was updated successfully, but these errors were encountered: