UK Crime Statistics
Population-adjusted national benchmarkingEvery scored neighbourhood resolves through GeoCode to its LSOA, population and deprivation decile. Without that layer, the platform could only report counts.
Read the case studyGeospatial toolkit
Postcode in, coordinates and census geography out.
A reusable .NET toolkit that turns any UK postcode into a complete picture of place — latitude and longitude, full address, and the administrative geography that makes fair comparison possible.
2.6M
UK postcodes
LSOA
Census geography resolution
Monthly
Unattended data sync
NuGet
Versioned package
Why it exists
Every honest comparison starts with knowing where you are.
Almost every question worth asking about a place needs more than a pin on a map. Is this area deprived? How many people live here? Which police force covers it? Which other areas is it actually comparable to?
Those answers live in ONS administrative geography, and joining them to a postcode reliably is fiddly, thankless work that goes stale every month. Rather than repeat it in every project, we built it once as a toolkit and kept it maintained.
It is the layer that lets our crime platform benchmark a neighbourhood against genuinely similar places instead of against raw counts — which is the entire difference between a statistic and an assessment.
Returns for any postcode
- Coordinates
- Latitude and longitude
- Address
- Line, city, county, country
- Census geography
- LSOA code and name
- Administrative
- Local authority district, region
- Context
- Population, IMD decile, police force
How it works
A toolkit, not a dependency you have to babysit
1
Reference it like any other package
Distributed as a versioned NuGet package. Add it to a solution, resolve the client, and call it. No service to stand up, no endpoint to configure, no separate deployment to keep in step with the rest of your application.
2
Forwards and backwards
Resolve a postcode to its full geographic picture, or take an LSOA and get back every postcode inside it. The reverse direction is what makes area-level analysis possible rather than just point lookups.
3
Kept current, unattended
Postcodes are created and retired continuously. A scheduled monthly sync refreshes the dataset and backfills missing area data, with a dry-run mode that reports what would change before anything is written, and a full audit log afterwards.
4
Async throughout
Every call is asynchronous and cancellable, because geography lookups sit in the hot path of a web request and should never be the reason a page hangs.
Where it is used
The layer under our own platforms
Client work
Wherever UK geography is involvedCatchment analysis, site comparison, regional roll-ups, deprivation weighting — anything that needs a postcode turned into context rather than a dot on a map.
Our data engineeringGet in touch
Need UK geography handled properly?
GeoCode underpins our own platforms. If you have a project that needs the same foundation, or you are interested in using the toolkit directly, tell us what you are working on.
info@meddalwedd.co.uk