Every Great Britain UPRN (41.6 million) linked to a point, building outline or land parcel, street and census areas, with a confidence label on each answer. Built only from open data, mostly under the OGL. GeoParquet, STAC and PMTiles.
Every Unique Property Reference Number (UPRN) in Great Britain, 41,593,127 of them, resolved to a point, a TOID, an approximate building outline, a land parcel, a street name and statistical geographies. Each answer comes with a measure of how specific it is, so you can tell a house's own outline from a city block.
Built only from open data, almost all under the Open Government Licence v3.0. Two small parts carry their own open licences, both labelled: Microsoft building footprints, used where no OS building or land parcel fits, and business names from Overture Maps. No house numbers, building names or postcodes are published.
2026-11, a one-off snapshot. There may be further releases; if so, latest.json will name the
newest.Since 2020 the UPRN has been openly available, which makes it a natural common key for property data in Great Britain. The open products each cover part of the picture: OS Open UPRN gives the location, OS Open Linked Identifiers links a UPRN to a building TOID and a street, and OS OpenMap Local provides building outlines. Putting them together to answer "which building, which parcel, which street?" for a UPRN still takes a fair amount of work, which can be a barrier for researchers, civic tech groups, students and open-source projects.
This dataset brings those open pieces together in one place, uses geometry to bridge the gaps between them, and
records how confident each answer is. The repository's RESEARCH.md describes the approach in detail.
Ordnance Survey's own products remain the recommended choice for authoritative or production use. OS NGD Buildings and OS MasterMap Topography Layer provide the definitive building polygon for each TOID, and AddressBase and the OS Places API provide full addresses and classification for each UPRN. Public sector organisations can access these under the Public Sector Geospatial Agreement (PSGA). This dataset is an open approximation intended to complement them, not to stand in for them.
This is a side project by staff at Avineon Tensing, for open-source and research activities, and is not an official Avineon Tensing product. It is not produced or endorsed by Ordnance Survey or any of the other data publishers, whose open data releases made it possible.
Look up one UPRN with DuckDB:
Every UPRN points to the shape of its best outline. best_outline_source says which table holds it, and
best_outline_id is the key:
For example, the land parcels behind UPRNs in Islington:
Each table is a single file, read over HTTP without downloading it: DuckDB, GDAL, QGIS and pandas fetch only the
parts a query needs. Rows are sorted spatially (Hilbert curve) in blocks of 100,000, and each block records its
extent, so filtering on lad (the local authority code) or on the bbox column skips most of the file. Looking
up a UPRN without a lad or area filter reads the whole uprn column, about 80 MB; add WHERE lad = '…' when
you know the authority. lad_index.parquet gives each authority's extent and UPRN count.
Coordinates are British National Grid (EPSG:27700). WGS84 sources were converted with the OSTN15 grid, not a Helmert approximation.
Also in each release: README.md (column-by-column schemas), LICENCE.md, accuracy.json (the OpenStreetMap
check below), stats.json (per-authority statistics), lad_index.parquet (each authority's extent), and
release_manifest.json (size, sha256 and row count of every file, plus source dataset versions).
To keep the release simple, some things are left out. Each is free from its publisher, and the code can rebuild them locally: full EPC certificates, HM Land Registry Price Paid records, Overture Maps places, the complete Microsoft footprint set, and OpenStreetMap streets, house numbers and buildings.
Figures for release 2026-11, over every UPRN in the ONS UPRN Directory. Per-authority figures are in stats.json.
Scotland's lower parcel coverage is expected: Registers of Scotland publish Land Register parcels only, and estimate that 32% of ownership polygons are missing. Price Paid Data covers England and Wales only.
uprn_lookup.best_outline_source, share of UPRNs:
Parcels often separate neighbouring properties better than OpenMap Local, which merges terraces into one shape.
outline_confidence says how many UPRNs share the best outline: property means none other, small_group two to
five, block more than five.
By source, in UPRNs:
Parcels supply two thirds of all property-level answers.
From the uprn_links table, which uses OpenMap Local only:
outline_granularity: parcel_finer (the parcel holds fewer UPRNs than the building) 47.6%, shared 27.0%,
single 11.0%, no outline 14.4%.
Most UPRNs without a street name sit on roads missing from the open road network, usually private or estate roads.
Built form, for the 21.6 million UPRNs that have one: semi-detached 31.7%, mid-terrace 26.4%, detached 23.5%, end-terrace 14.0%, enclosed terrace 2.3%, not recorded 2.1%.
quality_score starts at 100 and loses points for each issue, listed in quality:
A UPRN can carry several flags. The postcode flags come from checks against Code-Point Open; no postcodes are published.
About 3.4 million UPRNs carry an OpenStreetMap tag (ref:GB:uprn) on a building outline drawn by a mapper.
No OpenStreetMap data goes into uprn_lookup, so these give an independent check of what the confidence labels
claim. For the 2.8 million tagged buildings that hold a single UPRN, mostly houses:
So a property outline almost always belongs to that property alone, while small_group and block outlines
almost always take in neighbours, as their labels say. Where a property outline is an OS OpenMap Local or
Microsoft building, its area is typically within 5% of the mapped building's. Where it is a land parcel, it is
typically three to four times larger, because a parcel includes the garden.
Two caveats. Mappers often place the tag using the same OS Open UPRN point this dataset uses, so "lies inside" mainly
confirms we picked the right outline around that point rather than independently surveying where each property is.
And tagged buildings are concentrated where OpenStreetMap is well mapped, so they are not a random sample. Full
results by outline source, including buildings with several UPRNs, are in accuracy.json (aggregate statistics
derived from OpenStreetMap: © OpenStreetMap contributors, ODbL-1.0).
outline_confidence, uprns_in_building, uprns_in_parcel and outline_granularity before
treating an outline as one property.uprn_links.ppd_transaction_ids holds only sales in HMLR's UPRN lookup,
published since August 2026, so most UPRNs have none.building_id is not stable between releases. It is a hash of the outline geometry.Northern Ireland has no open UPRNs, so it is not covered.
Every input to this dataset is open data: published under an open licence and free to download and reuse, including commercially, provided the attribution terms are met. No premium, PSGA or paid-for data was used at any stage, and nothing here was derived from AddressBase, OS MasterMap, OS NGD, the OS Places API or the Royal Mail PAF. All sources are free to access; England and Wales EPC data needs only a free GOV.UK One Login account.
Exact source versions for this release are recorded in release_manifest.json. EPC address fields and Price Paid
address text are excluded, because they contain third-party address data that the open licences do not cover.
Everything is under the OGL v3.0 except two labelled parts: microsoft_buildings/ (CDLA-Permissive-2.0,
attribution only) and the business name columns of uprn_lookup/ (Overture Maps, per provider; see
uprn_lookup/LICENCE.txt). There is no share-alike data in the release. Full terms and every required statement
are in <release>/LICENCE.md. HM Land Registry INSPIRE data is
reused under its conditions of use.
For the OGL v3.0 tables, carry these statements with any reuse:
For microsoft_buildings/: "Building footprints © Microsoft, CDLA-Permissive-2.0". accuracy.json holds
aggregate statistics derived from OpenStreetMap: "© OpenStreetMap contributors, ODbL-1.0". This README and the STAC metadata are
available under CC0-1.0.
Questions and feedback: uk@avineon-tensing.com
os_buildingsland_parcels| OGL v3.0 |
stac/ | Static STAC catalogue: one collection and one item per table |
| 91.9% |
| Has a street name | 92.3% | 85.4% | 81.3% | 91.1% |
| Has an EPC property type | 55.7% | 49.8% | 51.8% | 54.9% |
| Has a matched business name (Overture) | 3.9% | 3.0% | 3.8% | 3.8% |
| Has a linked Price Paid sale | 0.2% | n/a | 0.2% | 0.2% |
Mean quality_score (0 to 100) | 84.7 | 79.2 | 84.5 | 84.2 |
| Ordnance Survey |
| OGL v3.0 |
| Street geometry for distance checks |
| OS Open Roads | Ordnance Survey | OGL v3.0 | Fallback street names |
| Code-Point Open | Ordnance Survey | OGL v3.0 | Postcode quality checks only; no postcodes published |
| ONS UPRN Directory (ONSUD) | Office for National Statistics | OGL v3.0 | UPRN list, local authority, OA / LSOA / MSOA |
| INSPIRE Index Polygons | HM Land Registry | OGL v3.0 | Land parcels, England and Wales |
| Price Paid Data and UPRN lookup | HM Land Registry | OGL v3.0 | Price Paid transaction IDs for linked UPRNs |
| INSPIRE Cadastral Parcels | Registers of Scotland | OGL v3.0 | Land parcels, Scotland |
| EPC register, England and Wales | MHCLG | OGL v3.0 (non-address fields) | Property type, built form and certificate ID |
| EPC register, Scotland | Scottish Government | OGL v3.0 (non-address fields) | As above, Scotland |
| GlobalMLBuildingFootprints | Microsoft | CDLA-Permissive-2.0 | Building footprints where no OS building or parcel fits |
| Overture Maps Places | Overture Maps Foundation | CDLA-Permissive-2.0, Apache-2.0 or CC0-1.0, per provider | Business and organisation names |
| OpenStreetMap (Geofabrik extracts) | OpenStreetMap contributors | ODbL-1.0 | The independent accuracy check only (aggregate statistics in accuracy.json); no OpenStreetMap data is in the tables |