Source: Understanding the Deprivation Index on This Site

I wanted to take a moment to explain the Deprivation Index used on this site. Almost immediately after I first mentioned it, I started getting messages asking how it actually works.

The short answer: there isn’t one single dataset that gives you the full picture.

To create a reliable deprivation lookup, you need at least three datasets, and ideally four or five if you want complete accuracy across the UK.

Let’s break this down step by step.

Start with addresses and GSS codes?

When most of us think of an address, we think of something like:

1 Lansley Road, Basingstoke, Basingstoke & Deane, Hampshire, RG21 5RX

That’s simple and familiar.

But when it comes to government data, things aren’t that straightforward.

Public agencies, such as the ONS (Office for National Statistics), rarely use full written addresses like this. Instead, they use something called GSS codes to identify every area in the country.

What Are GSS Codes?

GSS stands for Government Statistical Service.

These are unique codes used to identify geographic areas across the UK, from entire countries down to small neighbourhoods.

Why use codes at all?

Because names can change, but codes stay the same.

For example, if Kensington (E09000020) later becomes Kensington and Chelsea, the code E09000020 still identifies the same place. Systems using GSS codes continue to work perfectly, but anything using names would break until updated.

That consistency is why these codes are so important for data integration.

The Problem: Datasets Only Include What They Need

Here’s where things start to get tricky.

Every dataset you download, whether from the government or elsewhere, only includes the identifiers that it needs.

Take the English Indices of Deprivation dataset, for example.

It includes deprivation scores for every area in England… but the only location field it provides is the LSOA code.

That’s it. No names, no postcodes, no map coordinates.

There are about 36,000 LSOAs in England, each with its own code.

On their own, those codes aren’t much help if you want to show users something meaningful like “Manchester” or “Basingstoke”.

So how do we make sense of them?

Matching LSOA Codes to Names

To attach a name to an LSOA code, we need a lookup file — a dataset that lists all the LSOA codes for England alongside their names and coordinates.

You can download this directly from gov.uk, and it will give you:

• The LSOA code
• The official LSOA name
• Map references
• Shape data (for mapping boundaries)

But the names themselves aren’t particularly user-friendly.

For example:

• City of London 001A
• City of London 001B
• City of London 001C
• And so on.

That’s not very descriptive! You couldn’t easily search or identify which one represents your specific area without a map.

And since this site focuses heavily on property, we really need a way to link deprivation data to postcodes, not just statistical area codes.

Connecting Postcodes with LSOAs

So how do we bridge that gap?

That’s where one of the most useful datasets comes in, the ONS Postcode Directory (ONSPD).

This file contains every UK postcode, updated regularly, along with:

• Latitude and longitude (for mapping)
• All relevant GSS codes (country, region, local authority, LSOA, MSOA, etc.)

It’s a big file, around 5GB, but it’s the glue that connects everything.

Thanks to the ONSPD, you can enter a postcode like RG21 5RX and instantly find out which LSOA, region, and authority it belongs to.

That connection makes postcode-based deprivation searches possible.

Expanding Beyond England

For this site, I’ve also added data for Scotland and Wales.

Both nations publish their own versions of deprivation indices:

• SIMD — Scottish Index of Multiple Deprivation
• WIMD — Welsh Index of Multiple Deprivation

Each has its own calculation methods and scales, so separate datasets are required.

The good news is that Scotland and Wales usually include readable area names directly in their datasets, which makes linking easier than in England’s case.

At this point, we now have five key datasets working together:

1. English Index of Multiple Deprivation (IMD)
2. LSOA Names for England
3. Scottish Index of Multiple Deprivation (SIMD)
4. Welsh Index of Multiple Deprivation (WIMD)
5. ONS Postcode Directory (ONSPD)

Bringing It All Together

Once these datasets are imported into a database and properly indexed, the process looks like this when someone searches by postcode:

1. User enters a postcode.
2. The system looks up the postcode in the ONSPD table to find its LSOA code.
3. If the LSOA starts with:

• E → use the English IMD dataset
• S → use the Scottish SIMD dataset
• W → use the Welsh WIMD dataset

1. Match the LSOA code in the deprivation dataset.
2. Retrieve and display the deprivation score, rank, decile, and other related data.

The Hidden Complexity

It sounds simple written like that, but the reality is far from it.

Each dataset is large and structured differently.

Linking them efficiently requires:

• Careful database design
• Indexing for speed
• Consistent data cleaning
• Handling updates when new versions of the datasets are released

It takes a lot of work behind the scenes to make a postcode search return results instantly, but that’s the goal: fast, accurate, and meaningful information for anyone who visits.

Want to Explore the Data Yourself?

The datasets I’ve mentioned are all publicly available. A quick search for the following will get you started:

• English Indices of Deprivation 2019 (LSOA level)
• Scottish Index of Multiple Deprivation (SIMD)
• Welsh Index of Multiple Deprivation (WIMD)
• ONS Postcode Directory (ONSPD)
• LSOA and MSOA boundaries shapefiles

If you enjoy working with data or just want to see how deprivation is measured across the UK, these are a great starting point.