An easier to download version of this can be found at: https://mysociety.github.io/uk_local_authority_names_and_codes/
--
Lookup between the many, many different ways of naming and coding UK local authorities.
If you ever try to match UK local authority statistics against each other you'll quickly find your efforts frustrated by inconsistent uses of official codes and different versions of LA names. These lookups are an on-going tool to help translate between these.
To update this information, update the files in the source folder:
source\local-authority-info.json is the core file, with most key relational information. source\lookups contains csvs which will be merged on the basis of keys in the main file. This is mostly for lookups between ID schemes. Updating these files and pushing to github will trigger a rebuild and test of the output files.
The output files avaliable are in the data directory:
uk_local_authorities.csv - big lookup table. lookup_name_to_registry.csv combines all alternate names into one column to let you quickly match any data and get back a canonical code (which can be checked against the other table to convert to your preferred format). Also combined with this name lookup from openregister for fuller coverage.lookup_gss_to_registry.csv file converts from present and former GSS LAD codes (which refer to the boundary shape rather than the authority to the canonical code. lookup_lsoa_to_registry.csv lookup from lsoa/datazone/soa to current local authority. This project originally used the official local authority registers to provide a canonical three character code and a canonical name for the local authority. This is required because the more common GSS id refers to boundaries rather than legal entities.
The registers are now depricated but the existing three letter codes will continue to be used. Technically these codes are independent of the register (they are BS-6879), but they are less likely to be released quickly and are not widely used anyway.
As such, there is now a seperate 'BS-6879' column that reflects the official code, and the internal 'local-authority-code' where new additions will be assigned a three digit code for use in this register.
As these codes are not widely used in data releases, it feels likely that maintaining continuity for pipelines and datasets produced using this sheet will be more important than the divergence if different codes are then assigned.
It is annoying and confusing that local-authority-code and BS-6879 columns may become almost but not entirely identical, but this entire project is required because of a series of similarly annoying and confusing problems, so we might just have to live with that.
Additional maps can be found here.
*The gss code used for the Greater London Authority is the gss code is for London region - when working from code point open use E18000007 and the NHS_HA_code column.
| Authority type | Current authorities | Former authorities |
|---|---|---|
| City corporation | 1 | 0 |
| Combined authority | 11 | 0 |
| County | 21 | 6 |
| London borough | 32 | 0 |
| Metropolitan district | 36 | 0 |
| NI district | 11 | 25 |
| Non-metropolitan district | 164 | 40 |
| Scottish unitary authority | 32 | 0 |
| Strategic Regional Authority | 1 | 0 |
| Unitary authority | 63 | 2 |
| Welsh unitary authority | 22 | 0 |
| Lower or unitary? | Count |
|---|---|
| No | 33 |
| Yes | 361 |
| All | 394 |
This are optional columns, and not entirely populated.
| column | complete | % |
|---|---|---|
| long | 391 | 99.2% |
| lat | 391 | 99.2% |
| x | 391 | 99.2% |
| y | 391 | 99.2% |
| BS-6879 | 387 | 98.2% |
| wdtk-id | 387 | 98.2% |
| old-register-and-code | 384 | 97.5% |
| open-council-data-id | 373 | 94.7% |
| gov-uk-slug | 371 | 94.2% |
| os | 361 | 91.6% |
| snac | 361 | 91.6% |
| mapit-area-code | 310 | 78.7% |
| ecode | 307 | 77.9% |
| old-ons-la-code | 307 | 77.9% |
| ofcom | 175 | 44.4% |
| os-file | 167 | 42.4% |
| even-older-register-and-code | 22 | 5.6% |