|
|
|
# Geography Information
|
|
|
|
|
|
|
|
The only geographical reference we have for an areas data is LSOA11CD - which is the Lower Super Output Area 2011 code. [**A map of all these areas**](https://geoportal.statistics.gov.uk/datasets/ons::lower-layer-super-output-areas-dec-2011-boundaries-full-extent-bfe-ew-v3/explore) - there are over 30,000…
|
|
|
|
|
|
|
|
LSOAs are supposed to hold around ~1500 people, so typically only contain a couple of streets.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
_Number of individual 2011 LSOAs_
|
|
|
|
|
|
|
|
|
|
|
|
Looking at the map it is clear that it would be too slow to load the heat data onto all the LSOAs. Instead we should split the data up into the corresponding LADs - [**local authority districts**](https://geoportal.statistics.gov.uk/datasets/ons::lad-dec-2017-full-clipped-boundaries-in-the-uk-wgs84/explore)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
_Cardiff Local Authority District (LAD)_
|
|
|
|
|
|
|
|
LADs encompass a much larger area, making them more suitable when looking at the heat data for the whole of England and Wales. They also make up recognisable administrative areas, such as Cardiff, Newport, South Yorkshire, Islington etc.
|
|
|
|
|
|
|
|
The existing PowerBI tool uses LADs to show the head demand data, but it provides no option to look at the LSOAs within a LAD, as well as being slow and clunky - likely due to PowerBI having to match each LSOA to the LAD on the fly - something we can combat with indexes and joins on our database, as well as server side caching.
|
|
|
|
|
|
|
|
It is important to bear in mind that the LAD and LSOA boundaries change every couple of years - the data we are given uses 2011 LSOA codes, so it is important whatever LSOA map we use has the corresponding 2011 boundaries - We are using the [**2011 LSOA maps split into the 2017 LAD boundaries**](https://github.com/Laurafharding/lsoa-by-lad-topojson/tree/master/geojson) |
|
|
\ No newline at end of file |
