Follow

How data is aggregated and apportioned

How we apportion and aggregate data

With the Upload Your Data tool, it’s possible to create a custom dataset using Postcodes, OAs, LSOAs, MSOAs or Local Authorities as the geography.  

When you upload at Postcode level we can easily aggregate to higher geographies. Postcode-level data imported into Local Insight is aggregated to all higher levels (OA, LSOA, MSOA, LA). For each of the higher levels, a total is calculated based on the data values for the constituent smaller areas. The same principle is put in place for other geographies. See the following table:

Please note: we do not store raw postcode data

Geography used in UYD

Geographic levels Local Insight will aggregate to

Postcode

OA, LSOA, MSOA, LA

OA

LSOA, MSOA, LA

LSOA

MSOA, LA

MSOA

LA

LA

 

 

However, we are not able to apportion down to lower levels when viewing data on the map. In such a case, as you zoom in to view lower levels, you will continue to see the same data overlay as you do for the level it was uploaded for. Clicking on the info button in the top right hand corner will confirm which level the data you’re seeing is for.

Viewing custom datasets for your custom areas

When you overlay your custom data onto the map, you are able to view this data for your custom areas by clicking the Info button and then Data for your areas. Here you will see your data apportioned down based on population weighting.

Exactly how this is calculated depends on whether you are summing or averaging your data.

The higher (larger) the geography you upload data for, the harder it becomes to accurately apportion data to your custom areas. (This has been the reason we do not include Local Authority level datasets within Local Insight.)

For example, for data uploaded at Local Authority level:

    • Summing will apportion the value down based on population. For example, if 500 people cycled to work in your Local Authority, and your custom area accounted for 10% of the Local Authority, then we will assume that 50 people cycle to work for your custom area.

 

  • Averaging will assume each of your custom areas will have the same value as the Local Authority. For example, if on average rent prices in your Local Authority were £450 per month, it would assume the average rent price in each of your custom areas is also £450 per month.

 

Please note: The above explanation assumes that your custom area does not transcend Local Authority boundaries. You will see different data if it does. If you have any questions on the data displaying for your custom areas, please get in touch with the support team at support@ocsi.co.uk who can talk you through the aggregation process.

Health warnings on data

It is very important that you use the “Description” field in your metadata effectively. Please ensure you explicitly state the geographic level that you have uploaded data for, and what users of the data can expect to see when looking at “data for your areas”. You may also want to give guidance on what the data can and cannot be used for.

For more information, see our articles on:

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.

Can't find what you're looking for?

Contact Us