UK Geocoding Coverage

Address-level geocoding for UK workflows, with postcode-centric lookups, full-address parsing, and admin context across England, Scotland, Wales, and Northern Ireland.

What is covered

Map Zena supports UK geocoding across all four nations. It handles full postal addresses, postcode-only lookups, and partial address strings used in logistics, retail checkout, property search, and KYC address verification workflows. Admin context — district, county, region, and nation — is returned where available in the source data.

Address componentCoverage detail
Building number and nameResolved where structured source records provide point-level data
Street and localityNational street-level coverage across all four nations
Post townUsed for disambiguation where street names repeat across areas
Postcode (outward + inward)All standard UK postcode formats supported, including single-digit and double-digit districts
Admin hierarchyNation, county or region, district, and ward where available
Nation coverageEngland, Scotland, Wales, Northern Ireland

UK postcode formats

UK postcodes follow a structured format: an outward code (area + district) and an inward code (sector + unit), separated by a space. Common formats include AN NAA, ANN NAA, AAN NAA, and AANN NAA. All standard variants are accepted and normalised before matching.

Postcode-only queries are fully supported and return the centroid coordinates of the postcode area, which is commonly used to seed address-selection dropdowns or to apply regional pricing logic.

Postcode format examples
SW1A 2AA   (ANN NAA — central London)
EH2 2BD    (AN NAA — Edinburgh)
CF10 1EP   (AAN NAA — Cardiff)
BT1 1AA    (AN NAA — Belfast)
M1 1AE     (A1 NAA — Manchester)

Address parsing and disambiguation

Ambiguous street names are common in the UK — there are hundreds of "High Streets" and "Church Roads" across the country. The geocoder uses post town, postcode, and county cues from the query string to resolve the correct location. Including the postcode in a query is the most reliable disambiguation method for UK addresses.

Flat and apartment designations (Flat 4, Flat A, Ground Floor) are parsed and matched where source records include sub-building data. Named buildings (block names on estates) are handled where the building name appears in the address index.

Scotland, Wales, and Northern Ireland

Coverage extends to all four nations. Welsh localities are indexed with both Welsh and English name variants where applicable — for example, Caerdydd and Cardiff both resolve correctly. Northern Ireland addresses use BT postcodes and include district council context. Scottish addresses include council area admin output.

Example query patterns

GET /geocode?q=
10 Downing Street, London SW1A 2AA
1 St Andrew Square, Edinburgh EH2 2BD
Cardiff CF10 1EP
Flat 3, 22 High Street, Manchester M1 1AD
BT1 1AA

Common use cases

  • KYC and AML address checks — Verify that customer-entered addresses resolve to real UK locations as part of financial onboarding.
  • E-commerce delivery validation — Check that a delivery postcode resolves before committing to a shipping rate or zone.
  • Property technology — Geocode listing addresses for map display, catchment queries, and travel-time overlays.
  • Postcode-driven address lookup — Use a postcode query to seed a "select your address" dropdown in checkout or registration flows.
  • Logistics zone assignment — Assign UK addresses to regional depots or delivery zones using geocoded coordinates.

Reverse geocoding for UK addresses

The reverse geocoding endpoint returns the nearest UK address for a given latitude/longitude pair, including postcode, locality, and nation fields. Useful for apps that receive GPS data and need to show a human-readable address.

Related pages