> This is part 1 of 17 of the full documentation (pages 1–100 of 1679).
> The content is paginated: fetch every part to see all of it.
> Next part: https://docs.os.uk/os-downloads/llms-full.txt/1
> Page index: https://docs.os.uk/os-downloads/llms.txt

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
This site has an agentic ask interface you may use to query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.os.uk/os-downloads/index.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

---

# OS Download Products' Documentation

Explore documentation and guides for OS Premium and OpenData Download products, such as AddressBase Premium, OS MasterMap Topography Layer, Boundary-Line and OS Open Zoomstack.

## What's available on this site?

This is a self-serve site containing documentation and guides relating to the Ordnance Survey (OS) [Premium](#types-of-download-data-products) and [OpenData](#types-of-download-data-products) Download products [available to download through the OS Data Hub](https://osdatahub.os.uk/).

On the left-hand-side menu, we've grouped documentation first by portfolio, then alphabetically by product. Under each product's landing page, you'll usually find the following product-specific documents:

* Release Notes (available for most products)
* An Overview
* A Getting Started Guide (available for most products)
* A Technical Specification
* Downloads (contains any additional files to download for a product, such as classification schemes and CSV header files, and links to product stylesheets and XML schemas held on other OS sites, if available for a product)
* Known Data Issues

***

### Download data product portfolios

The Download data products are grouped by portfolio:

<table data-column-title-hidden data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden></th><th data-hidden></th><th data-hidden data-type="content-ref"></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><h4>Addresses and Names</h4></td><td>Explore mapping data relating to addresses, Unique Property Reference Numbers (UPRNs), named features and places. Discover address details, postcodes, identifiers and features.</td><td><a href="/os-downloads/products/addresses-and-names-portfolio">Addresses and Names Portfolio</a></td><td></td><td></td><td><a href="/os-downloads/products/addresses-and-names-portfolio/addressbase-premium">AddressBase Premium</a></td><td data-object-fit="cover" data-alt="Example image showing AddressBase data."><a href="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2Fcj9UR9pSIrQEoNFY9SeB%2Faddressbase.xeaf23c9e.webp?alt=media&amp;token=a2ed94d6-10d5-4265-aeb4-c6886bf3ad23">addressbase.xeaf23c9e.webp</a></td></tr><tr><td><h4>Areas and Zones</h4></td><td>Explore mapping data designed to provide information about areas used for administration and analysis. Discover postcodes, boundaries and built up areas.</td><td><a href="/os-downloads/products/areas-and-zones-portfolio">Areas and Zones Portfolio</a></td><td></td><td></td><td></td><td data-object-fit="cover" data-alt="Example image showing Code-Point product data over a background map."><a href="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FZkpZwEKiV0b3QAcv2rR0%2FCode-Point-4.png?alt=media&amp;token=b982d13f-ecd8-4ad4-920b-36e6164f103b">Code-Point-4.png</a></td></tr><tr><td><h4>Buildings and Infrastructure</h4></td><td>Explore mapping data designed to provide information about the built environment. Discover building and structure features, identifiers and topography layers.</td><td><a href="/os-downloads/products/buildings-and-infrastructure-portfolio">Buildings and Infrastructure Portfolio</a></td><td></td><td></td><td></td><td data-object-fit="cover" data-alt="Example image showing OS MasterMap Topography Layer – Building Height Attribute product data."><a href="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2F0r6Sp1CKhq90dfGBabMp%2FMasterMap-Topography-And-Building-Heights-2.PNG?alt=media&amp;token=ea35a13d-4a5a-441d-ab11-ebb2a4915a5d">MasterMap-Topography-And-Building-Heights-2.PNG</a></td></tr><tr><td><h4>Land and Terrain</h4></td><td>Explore mapping data designed to show land cover, land use and elevation. Discover land and built environment features, greenspace and topography layers.</td><td><a href="/os-downloads/products/land-and-terrain-portfolio">Land and Terrain Portfolio</a></td><td></td><td></td><td></td><td data-object-fit="cover" data-alt="Example image showing OS MasterMap Greenspace Layer product data over a background map of an urban area."><a href="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2Ftu1vE5BgoIL3FQiO4B1Z%2FMasterMap-Greenspace-5.png?alt=media&amp;token=5ddb79e8-4799-42bf-bacb-324a7862c54f">MasterMap-Greenspace-5.png</a></td></tr><tr><td><h4>Maps and Imagery</h4></td><td>Explore mapping data designed to provide visual context, allowing you to perform simple analysis. Discover raster and vector maps, imagery and topography layers.</td><td><a href="/os-downloads/products/maps-and-imagery-portfolio">Maps and Imagery Portfolio</a></td><td></td><td></td><td></td><td data-object-fit="cover" data-alt="Example image showing 1:25 000 Scale Colour Raster data."><a href="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FpQhLYyuZ2Ngu4TDAOlVX%2Fimage.png?alt=media&amp;token=63907468-baee-4c44-abdf-f05ae9730c38">image.png</a></td></tr><tr><td><h4>Transport Network</h4></td><td>Explore mapping data designed to provide information about roads, paths, trams, ferries and railways. Discover transport networks, features and identifiers.</td><td><a href="/os-downloads/products/transport-network-portfolio">Transport Network Portfolio</a></td><td></td><td></td><td></td><td data-object-fit="cover" data-alt="Example image showing OS Multi-Modal Routing Network product data over a background map of an urban area."><a href="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FbmimQGB9EAbOOFWJSj6N%2Fspaces_cNpJpLP8RROUaWVQo5ea_uploads_Yg04Mhx2AuEmd9cphnsi_image.webp?alt=media&amp;token=86dbf19b-57ce-4b39-a65a-23593b1ea859">spaces_cNpJpLP8RROUaWVQo5ea_uploads_Yg04Mhx2AuEmd9cphnsi_image.webp</a></td></tr><tr><td><h4>Water</h4></td><td>Explore mapping data designed to show water bodies, tidelines and river networks. Discover water features, identifiers and topography layers.</td><td><a href="/os-downloads/products/water-portfolio">Water Portfolio</a></td><td></td><td></td><td></td><td data-object-fit="cover" data-alt="Example image showing OS Open Rivers product data over a background map."><a href="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FYGqi12crn1Swv8amxqn1%2FOpen-Rivers-1.png?alt=media&amp;token=6cb7f7f7-eb72-409e-b478-f7c0cc463216">Open-Rivers-1.png</a></td></tr></tbody></table>

***

### Types of Download data products

There are two types of Download data product: **OS Premium** and **OS OpenData:**

{% tabs %}
{% tab title="OS Premium Download data products" %}
When we refer to Premium products we mean paid-for datasets – whether they’re paid for by businesses, purchased through an [OS Partner](https://www.ordnancesurvey.co.uk/customers/os-channel-partners), or accessed free at the point of use under the [Public Sector Geospatial Agreement (PSGA)](https://www.ordnancesurvey.co.uk/customers/public-sector/public-sector-geospatial-agreement).

The OS Premium Download data products are available to download in a range of formats, with a variety of ordering options, through the [OS Data Hub](https://osdatahub.os.uk/) on our [Premium and Public Sector plans](https://osdatahub.os.uk/plans).

Our Premium Download data products work in a range of software, including ESRI ArcGIS, QGIS, Mapbox, Cadcorp SIS, MapInfo, Tableau, Kepler.gl and many more.
{% endtab %}

{% tab title="OS OpenData Download products" %}
OS OpenData Download products are **free** to use by anyone for any purpose – including for services from which you make a profit.

The OS OpenData Download products are available to download in a variety of formats, with a variety of ordering options, through the [OS Data Hub](https://osdatahub.os.uk/data/downloads/open).
{% endtab %}
{% endtabs %}

***

## Additional OS product resources

The following pages may be of interest:

<table data-view="cards"><thead><tr><th></th><th data-hidden data-type="content-ref"></th><th data-hidden></th><th data-hidden></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4><span data-gb-custom-inline data-tag="emoji" data-code="1f4e3">📣</span> Product Announcements</h4><p>A page detailing any newsworthy announcements for the OS Download data products.</p></td><td></td><td></td><td></td><td></td><td><a href="/os-downloads/resources/product-resources/product-announcements">Product Announcements</a></td></tr><tr><td><h4><span data-gb-custom-inline data-tag="emoji" data-code="1f50d">🔍</span> Sample Data</h4><p>Download product sample data from the <a href="https://osdatahub.os.uk/data/downloads/sample">OS Data Hub</a> or visualise it online using the <a href="https://experience.arcgis.com/experience/20981dabcb14402687dccb437a4a78fb/">OS MasterMap Product Viewer Tool</a>.</p></td><td></td><td></td><td></td><td></td><td><a href="/os-downloads/resources/product-resources/product-sample-data">Product Sample Data</a></td></tr><tr><td><h4><span data-gb-custom-inline data-tag="emoji" data-code="1f4c3">📃</span> Terms and Conditions</h4><p>The terms and conditions on which the OS Premium data and OS OpenData Download products are made available.</p></td><td></td><td></td><td></td><td></td><td><a href="/os-downloads/resources/site-resources/terms-and-conditions">Terms and Conditions</a></td></tr><tr><td><h4><span data-gb-custom-inline data-tag="emoji" data-code="1f4c5">📅</span> Product Refresh Dates</h4><p>The update frequencies of the Premium and OpenData Download products and the calendar months in which these updates are published. You'll also find tables listing the upcoming and past publication and data cut / extraction dates for AddressBase and OS MasterMap Topography Layer.</p></td><td><a href="broken://pages/AZW9NmXjnp3h16Es991c">Broken link</a></td><td></td><td></td><td></td><td><a href="/os-downloads/resources/product-resources/product-refresh-dates">Product Refresh Dates</a></td></tr><tr><td><h4><i class="fa-map-location">:map-location:</i> OS Product Roadmap</h4><p>The roadmap has details of new Download product releases (for Premium and OpenData products) and upcoming OS National Geographic Database (OS NGD) releases, plus dates for planned product withdrawals as they reach their End of Life stage.</p></td><td></td><td></td><td></td><td></td><td><a href="https://www.ordnancesurvey.co.uk/products/roadmap">https://www.ordnancesurvey.co.uk/products/roadmap</a></td></tr><tr><td><h4><span data-gb-custom-inline data-tag="emoji" data-code="1f5fa">🗺️</span> PSGA <strong>Product Summary</strong></h4><p>A page listing all of the OS data products available to Public Sector Geospatial Agreement (PSGA) Members on an unlimited basis across the OS National Geographic Database (OS NGD), APIs and Download data products.</p></td><td></td><td></td><td></td><td></td><td><a href="/os-downloads/resources/product-resources/psga-product-summary">PSGA Product Summary</a></td></tr></tbody></table>


# Addresses and Names Portfolio

This page provides an overview of the OS downloadable products in the Addresses and Names Portfolio.

## Addresses and names products

This portfolio provides authoritative and accurate address data for Great Britain and lists of named features and places as identifiers for real-world locations. Access a comprehensive register of all property addresses (including their UPRNs, locations, function and key characteristics), geographic place names and a gazetteer designed for Emergency Services.

Addresses and names products support everything from property, logistics and planning to public service delivery and geocoding.

The following downloadable products are available within the Addresses and Names Portfolio:

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3>AddressBase</h3></td><td>Access to a current view of all Royal Mail Postcode Address File (PAF) addresses with additional location-based data featuring residential or commercial classifications.</td><td><em>N.B. This product will become <strong>End of Life on 29 November 2027</strong> and will be withdrawn.</em></td><td data-object-fit="cover" data-alt="Example image showing AddressBase product data over a background map."><a href="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2Fcj9UR9pSIrQEoNFY9SeB%2Faddressbase.xeaf23c9e.webp?alt=media&amp;token=a2ed94d6-10d5-4265-aeb4-c6886bf3ad23">addressbase.xeaf23c9e.webp</a></td><td><a href="/os-downloads/products/addresses-and-names-portfolio/addressbase">AddressBase</a></td></tr><tr><td><h3>AddressBase Core</h3></td><td>Access to over 33 million addresses sourced from Local Authority data and supplied with a Unique Property Reference Number (UPRN) and property-level coordinates.</td><td></td><td data-object-fit="cover" data-alt="Example image showing AddressBase Core product data over a background map."><a href="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FzHxBEHBSZemNhjsr5lcD%2FABCore_Cover.webp?alt=media&amp;token=ba571c25-439c-4db4-80f1-5dbee5952a8f">ABCore_Cover.webp</a></td><td><a href="/os-downloads/products/addresses-and-names-portfolio/addressbase-core">AddressBase Core</a></td></tr><tr><td><h3>AddressBase Plus</h3></td><td>Access to over 37 million postal and non-postal addresses sourced from Local Authorities, Ordnance Survey and Royal Mail for England, Wales and Scotland.</td><td><em>N.B. This product will become <strong>End of Life on 29 November 2027</strong> and will be withdrawn.</em></td><td data-object-fit="cover" data-alt="Example image showing AddressBase Plus product data over a background map."><a href="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FqgYi8w0EfdWfMB0AsffB%2FAddressBase-Plus-1.png?alt=media&amp;token=a6cc0eb7-2593-47ee-825e-2c18dd617eef">AddressBase-Plus-1.png</a></td><td><a href="/os-downloads/products/addresses-and-names-portfolio/addressbase-plus">AddressBase Plus</a></td></tr><tr><td><h3>AddressBase Plus Islands</h3></td><td>An addressing gazetteer offering full lifecycle information of a property for Northern Ireland, Isle of Man and the Channel Islands.</td><td><em>N.B. This product will become <strong>End of Life on 29 November 2027</strong> and will be withdrawn.</em></td><td data-object-fit="cover" data-alt="Example image showing AddressBase Plus Islands product data over a background map."><a href="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FvtegALy4RxhDAw2ldiTt%2FAddressBase-Islands-1.png?alt=media&amp;token=7723f624-46e2-45ef-a597-7da2d5e69ff1">AddressBase-Islands-1.png</a></td><td><a href="/os-downloads/products/addresses-and-names-portfolio/addressbase-plus-islands">AddressBase Plus Islands</a></td></tr><tr><td><h3>AddressBase Premium</h3></td><td>Provides the most detailed view available of an address and its lifecycle from creation through to retirement in England, Wales and Scotland.</td><td></td><td data-object-fit="cover" data-alt="Example image showing AddressBase Premium product data over a background map."><a href="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FtGufKalamXFnqFfZ6O6w%2FAddressBase-Premium-3.png?alt=media&amp;token=5e1991ba-4bf3-45ae-b860-03c8ec7d9145">AddressBase-Premium-3.png</a></td><td><a href="/os-downloads/products/addresses-and-names-portfolio/addressbase-premium">AddressBase Premium</a></td></tr><tr><td><h3>AddressBase Premium Islands</h3></td><td>Provides the most detailed view of an address and its lifecycle for Northern Ireland, Channel Islands and the Isle of Man.</td><td></td><td data-object-fit="cover" data-alt="Example image showing AddressBase Premium Islands product data over a background map."><a href="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FtGufKalamXFnqFfZ6O6w%2FAddressBase-Premium-3.png?alt=media&amp;token=5e1991ba-4bf3-45ae-b860-03c8ec7d9145">AddressBase-Premium-3.png</a></td><td><a href="/os-downloads/products/addresses-and-names-portfolio/addressbase-premium-islands">AddressBase Premium Islands</a></td></tr><tr><td><h3>Code-Point</h3></td><td>A postcode locator that locates over 1.7 million postcode units in Great Britain and Northern Ireland – providing information about delivery points, positional quality, type and district codes amongst other data points.</td><td><em>N.B. This product will become <strong>End of Life on 31 March 2028</strong> and will be withdrawn.</em></td><td data-object-fit="cover" data-alt="Example image showing Code-Point product data over a background map."><a href="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FZkpZwEKiV0b3QAcv2rR0%2FCode-Point-4.png?alt=media&amp;token=b982d13f-ecd8-4ad4-920b-36e6164f103b">Code-Point-4.png</a></td><td><a href="/os-downloads/products/areas-and-zones-portfolio/code-point">Code-Point Documentation</a></td></tr><tr><td><h3>Code-Point Open</h3></td><td>An open dataset of all 1.7 million postcode units in Great Britain.</td><td></td><td data-object-fit="cover" data-alt="Example image showing Code-Point Open product data over a background map."><a href="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2Fdeirn0CBM2uasdfC4MLr%2FCodepoint-Open-5.png?alt=media&amp;token=6611da8c-a25f-49f0-af9c-92994131b577">Codepoint-Open-5.png</a></td><td><a href="/os-downloads/products/areas-and-zones-portfolio/code-point-open">Code-Point Open Documentation</a></td></tr><tr><td><h3>Code-Point with Polygons</h3></td><td>A dataset providing the notional extent of every postcode in Great Britain for visualisation and analysis at a national scale.</td><td><em>N.B. This product will become <strong>End of Life on 31 March 2028</strong> and will be withdrawn.</em></td><td data-object-fit="cover" data-alt="Example image showing Code-Point with Polygons product data over a background map."><a href="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FzIDQ0Ab7SzhHhaRehUiT%2FCode-Point-Polygons-4.png?alt=media&amp;token=0c698d9d-c76e-40bf-8dd8-cd82a3d966ad">Code-Point-Polygons-4.png</a></td><td><a href="/os-downloads/products/areas-and-zones-portfolio/code-point-with-polygons">Code-Point with Polygons Documentation</a></td></tr><tr><td><h3>OS Emergency Services Gazetteer (OS ESG)</h3></td><td>Provides a national, consistent, and maintained view of the locations of names, places and objects in Great Britain to support the Emergency Services.</td><td></td><td data-object-fit="cover" data-alt="Example image showing OS ESG product data over a background map."><a href="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FY2Zn9pW6JvSW8scjBpay%2FESGCoverImage.avif?alt=media&amp;token=f1038c5d-6d46-47c7-b0d0-225b2f05211e">ESGCoverImage.avif</a></td><td><a href="/os-downloads/products/addresses-and-names-portfolio/os-emergency-services-gazetteer">OS Emergency Services Gazetteer</a></td></tr><tr><td><h3>OS Open Names</h3></td><td>A comprehensive open dataset of place names, road numbers and postcodes for Great Britain.</td><td></td><td data-object-fit="cover" data-alt="Example image showing OS Open Names product data over a background map."><a href="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FN4MmqmCBT1cnmt15WR5N%2FOS_OpenNames_Cover.webp?alt=media&amp;token=ecbb5a14-9fdd-42c9-8b3b-ba1d66504b3b">OS_OpenNames_Cover.webp</a></td><td><a href="/os-downloads/products/addresses-and-names-portfolio/os-open-names">OS Open Names</a></td></tr><tr><td><h3>OS Open UPRN</h3></td><td>An open dataset enabling linking, sharing and visualisation of data related to Unique Property Reference Numbers (UPRNs).</td><td></td><td data-object-fit="cover" data-alt="Example image showing OS Open UPRN product data over a background map."><a href="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FUE7Vn7zIxQljRvmIi0Ne%2Fopen_uprn_residential.png?alt=media&amp;token=58a7d2b7-c0b0-402d-8548-b3e2bf0a0e41">open_uprn_residential.png</a></td><td><a href="/os-downloads/products/addresses-and-names-portfolio/os-open-uprn">OS Open UPRN</a></td></tr><tr><td><h3>Points of Interest</h3></td><td>Provides a comprehensive location-based directory of all public and privately owned businesses, educational institutions and leisure services in Great Britain.</td><td></td><td data-object-fit="cover" data-alt="Example image showing Points of Interest product data over a background map."><a href="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FIV8GMgJeHzwbmvPjdnUn%2FPoints-of-Interest-1.png?alt=media&amp;token=27cbb11b-fb65-43fe-92a5-50a039561277">Points-of-Interest-1.png</a></td><td><a href="/os-downloads/products/addresses-and-names-portfolio/points-of-interest">Points of Interest</a></td></tr></tbody></table>


# AddressBase Fundamentals

Here you will find shared documentation for products within the AddressBase family of products.

The following AddressBase Fundamentals pages provide an overview of the 'family' of AddressBase products. They cover key elements of design for AddressBase products, including data formats, classification scheme, product supply, coordinate reference systems, currency, precision, and data sources, amongst other topics.

* [Release notes](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/release-notes)
* [AddressBase product family](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/addressbase-product-family)
* [Future and past publication dates](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/future-and-past-publication-dates)
* [Unique Property Reference Number (UPRN)](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/unique-property-reference-number-uprn)
* [Coordinate reference systems](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/coordinate-reference-systems)
* [Classification scheme](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/classification-scheme)
* [Data sources](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/data-sources)
* [Street names and numbering](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/street-names-and-numbering)
* [Currency, completeness and precision](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/currency-completeness-and-precision)
* [Product supply](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/product-supply)
* [Code lists and enumerations](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/code-lists-and-enumerations)
* [AddressBase local custodian codes](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/addressbase-local-custodian-codes)
* [AddressBase Islands local custodian codes](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/addressbase-islands-local-custodian-codes)

These pages should be used in conjunction with the detailed technical specifications for each product (which can be found under the top-level product page for each individual product from the left-hand-side menu).


# Release Notes

Release notes listed here provide information about the current release of the AddressBase 'family' of products and the previous nine releases.

{% hint style="info" %}

* The 'AddressBase Products' release notes include information on the AddressBase, AddressBase Plus and AddressBase Premium products.
* The 'AddressBase Islands' release notes include information on the AddressBase Plus Islands and AddressBase Premium Islands products.
* AddressBase Core is supplied weekly and its release notes can be found on the [AddressBase Core Release Notes page](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/release-notes).
* OS Open UPRN release notes can be found on the [OS Open UPRN Release Notes pages](/os-downloads/products/addresses-and-names-portfolio/os-open-uprn/release-notes).
  {% endhint %}

## Epoch 130

### [AddressBase products - September 2026 release note](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/release-notes/addressbase-products-september-2026-epoch-130)

This release note provides information about the September 2026 (Epoch 130) release of AddressBase products.

### [AddressBase Islands products - September 2026 release note](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/release-notes/addressbase-islands-products-september-2026-epoch-130)

This release note provides information about the September 2026 (Epoch 130) release of AddressBase Islands products.

## Epoch 129

### [AddressBase products – August 2026 release note](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/release-notes/addressbase-products-august-2026-epoch-129)

This release note provides information about the August 2026 (Epoch 129) release of AddressBase products.

### [AddressBase Islands products – August 2026 release note](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/release-notes/addressbase-islands-products-august-2026-epoch-129)

This release note provides information about the August 2026 (Epoch 129) release of AddressBase Islands products.

## Epoch 128

### [AddressBase products – June 2026 release note](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/release-notes/addressbase-products-june-2026-epoch-128)

This release note provides information about the June 2026 (Epoch 128) release of AddressBase products.

### [AddressBase Islands products – June 2026 release note](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/release-notes/addressbase-islands-products-june-2026-epoch-128)

This release note provides information about the June 2026 (Epoch 128) release of AddressBase Islands products.

## Epoch 127

### [AddressBase products – May 2026 release note](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/release-notes/addressbase-products-may-2026-epoch-127)

This release note provides information about the May 2026 (Epoch 127) release of AddressBase products.

### [AddressBase Islands products – May 2026 release note](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/release-notes/addressbase-islands-products-may-2026-epoch-127)

This release note provides information about the May 2026 (Epoch 127) release of AddressBase Islands products.

## Epoch 126

### [AddressBase products – April 2026 release note](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/release-notes/addressbase-products-april-2026-epoch-126)

This release note provides information about the April 2026 (Epoch 126) release of AddressBase products.

### [AddressBase Islands products – April 2026 release note](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/release-notes/addressbase-islands-products-april-2026-epoch-126)

This release note provides information about the April 2026 (Epoch 126) release of AddressBase Islands products.

## Epoch 125

### [AddressBase products – February 2026 release note](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/release-notes/addressbase-products-february-2026-epoch-126)

This release note provides information about the February 2026 (Epoch 125) release of AddressBase products.

### [AddressBase Islands products – February 2026 release note](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/release-notes/addressbase-islands-products-february-2026-epoch-125)

This release note provides information about the February 2026 (Epoch 125) release of AddressBase Islands products.

## Epoch 124

### [AddressBase products – January 2026 release note](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/release-notes/addressbase-products-january-2026-epoch-124)

This release note provides information about the January 2026 (Epoch 124) release of AddressBase products.

### [AddressBase Islands products – January 2026 release note](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/release-notes/addressbase-islands-january-2026-epoch-124)

This release note provides information about the January 2026 (Epoch 124) release of AddressBase Islands products.

## Epoch 123

### [AddressBase products – November 2025 release note](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/release-notes/addressbase-products-november-2025-epoch-123)

This release note provides information about the November 2025 (Epoch 123) release of AddressBase products.

### [AddressBase Islands products – November 2025 release note](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/release-notes/addressbase-islands-november-2025-epoch-123)

This release note provides information about the November 2025 (Epoch 123) release of AddressBase Islands products.

## Epoch 122

### [AddressBase products – October 2025 release note](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/release-notes/addressbase-products-october-2025-epoch-122)

This release note provides information about the October 2025 (Epoch 122) release of AddressBase products.

### [AddressBase Islands products – October 2025 release note](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/release-notes/addressbase-islands-october-2025-epoch-122)

This release note provides information about the October 2025 (Epoch 122) release of AddressBase Islands products.

## Epoch 121

### [AddressBase products – September 2025 release note](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/release-notes/addressbase-products-september-2025-epoch-121)

This release note provides information about the September 2025 (Epoch 121) release of AddressBase products.

### [AddressBase Islands products – September 2025 release note](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/release-notes/addressbase-islands-september-2025-epoch-121)

This release note provides information about the September 2025 (Epoch 121) release of AddressBase Islands products.


# Copy of AddressBase Release Note Template AddressBase Products \[Month YYYY] – Epoch \[Epoch #]

This release note provides information about the \[Month YYYY] (Epoch #) release of the AddressBase products. These products were released to customers on \[DD Month YYYY].

## Record counts

| Product                | Full Supply Record Count | Change-Only Update Record Count |
| ---------------------- | ------------------------ | ------------------------------- |
| OS Open UPRN           |                          | N/A                             |
| AddressBase            |                          |                                 |
| AddressBase Plus       |                          |                                 |
| AddressBase Premium    | See rows below           | See rows below                  |
| Street                 |                          |                                 |
| Street Descriptor      |                          |                                 |
| BLPU                   |                          |                                 |
| Classification         |                          |                                 |
| LPI                    |                          |                                 |
| Organisation           |                          |                                 |
| Delivery Point Address |                          |                                 |
| Application Cross Ref. |                          |                                 |
| Successor              | 0                        | 0                               |

**Please note:**

* The Full Supply record counts are based on a Managed Great Britain Set (MGBS). If you have ordered your national coverage via the online ordering system using a polygon outline, then your counts may differ.
* Change-Only Updates (COUs) are not available for the OS Open UPRN product.

## Product supply comparison

There is a difference in product counts between taking a national Managed Great Britain Set (MGBS) and a national Area of Interest (AOI). This is because the two supplies use different selection criteria. The differences are shown in the following table, allowing for you to validate your data holdings once you have loaded the latest release of AddressBase data.

The national AOI refers to the pre-selection GB polygon from our download store. Therefore, if you have drawn your own AOI, the count will vary.

If you are unsure of your supply type, please check this with your OS Relationship Manager.

| Product                | MGBS Full Count | National AOI Full Count | Difference     |
| ---------------------- | --------------- | ----------------------- | -------------- |
| AddressBase            |                 |                         |                |
| AddressBase Plus       |                 |                         |                |
| AddressBase Premium    | See rows below  | See rows below          | See rows below |
| Street                 |                 |                         |                |
| Street Descriptor      |                 |                         |                |
| BLPU                   |                 |                         |                |
| Classification         |                 |                         |                |
| LPI                    |                 |                         |                |
| Organisation           |                 |                         |                |
| Delivery Point Address |                 |                         |                |
| Application Cross Ref. |                 |                         |                |
| Successor              | 0               | 0                       | 0              |

It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in '[Working with COU data](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-getting-started-guide/working-with-cou-data)' in the AddressBase Getting Started Guide.

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the numbers of these records which can be expected in an **MGBS supply**, and also how many tiles are affected if you take your supply as Changed Chunks.

### AddressBase

| Change Type              | Count |
| ------------------------ | ----- |
| Inserts                  |       |
| Updates                  |       |
| Deletes                  |       |
| COU Populated Tile Count |       |

### AddressBase Plus

| Change Type              | Count |
| ------------------------ | ----- |
| Inserts                  |       |
| Updates                  |       |
| Deletes                  |       |
| COU Populated Tile Count |       |

### AddressBase Premium

| AddressBase Premium Table | Inserts | Updates | Deletes |
| ------------------------- | ------- | ------- | ------- |
| Street                    |         |         |         |
| Street Descriptor         |         |         |         |
| BLPU                      |         |         |         |
| Classification            |         |         |         |
| LPI                       |         |         |         |
| Organisation              |         |         |         |
| Delivery Point Address    |         |         |         |
| Application Cross Ref.    |         |         |         |

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch \[**Epoch #**]:

| Data Source                          | Date             |
| ------------------------------------ | ---------------- |
| Royal Mail PAF                       | \[DD Month YYYY] |
| National Land and Property Gazetteer | \[DD Month YYYY] |
| One Scotland Gazetteer               | \[DD Month YYYY] |
| VOA Non-Domestic Rates               | \[DD Month YYYY] |
| VOA Council Tax                      | \[DD Month YYYY] |
| OS MasterMap Topography Layer        | \[DD Month YYYY] |
| OS MasterMap Highways Network        | \[DD Month YYYY] |
| Code-Point with Polygons             | \[DD Month YYYY] |
| Boundary-Line                        | \[DD Month YYYY] |

## Data issues

### AddressBase

Details of live and resolved data issues for AddressBase will be communicated on the [AddressBase Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Plus issues

Details of live and resolved data issues for AddressBase Plus will be communicated on the [AddressBase Plus Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus/addressbase-plus-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Premium

Details of live and resolved data issues for AddressBase Premium will be communicated on the [AddressBase Premium Known Data Issues, Service Disruptions and Planned Maintenance page](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium/addressbase-premium-known-data-issues-service-disruptions-and-planned-maintenance). This page will provide details of their impacts and updates on the expected time frame for their resolution.

## Improvements in Epoch \[Epoch #]

### Valuation Office Agency matching

The match rates for Council Tax and Non-Domestic Rates for Epoch \[**Epoch #**] are detailed as follows based on Valuation Office Agency (VOA) records up to \[**DD Month YYYY**]. The match rate is applicable to the AddressBase Premium product.

| Data Source        | Records Received | % Matched |
| ------------------ | ---------------- | --------- |
| Council Tax        |                  |           |
| Non-Domestic Rates |                  |           |

### Tertiary classifications

Work is being undertaken to improve the classifications of records within the AddressBase products. This work has resulted in **\[XX XXX]** more tertiary classifications present in Epoch \[**Epoch #**] compared to Epoch \[**Previous Epoch #**]. Indeed, \[**Residential code improvement %**] of these tertiary classification improvements are against residential codes.

### PAF matching

The following graph shows the number of Postcode Address File (PAF) matched records in AddressBase by epoch:

\[**PAF matched records by epoch image**]

## Next release

The next release of AddressBase products, Epoch \[**Next Epoch #**], is scheduled for **\[DD Month YYYY]**.


# AddressBase Products September 2026 – Epoch 130

This release note provides information about the September 2026 (Epoch 130) release of the AddressBase products. These products were released to customers on 17 September 2026.

## Record counts

| Product                | Full Supply Record Count | Change-Only Update Record Count |
| ---------------------- | ------------------------ | ------------------------------- |
| OS Open UPRN           | 41 676 575               | N/A                             |
| AddressBase            | 31 000 728               | 136 574                         |
| AddressBase Plus       | 38 860 895               | 971 258                         |
| AddressBase Premium    | See rows below           | See rows below                  |
| Street                 | 1 532 580                | 17 618                          |
| Street Descriptor      | 1 657 099                | 7 043                           |
| BLPU                   | 41 676 575               | 820 912                         |
| Classification         | 45 440 946               | 187 787                         |
| LPI                    | 47 073 085               | 188 224                         |
| Organisation           | 1 390 423                | 13 553                          |
| Delivery Point Address | 31 117 915               | 66 769                          |
| Application Cross Ref. | 201 683 570              | 772 677                         |
| Successor              | 0                        | 0                               |

**Please note:**

* The Full Supply record counts are based on a Managed Great Britain Set (MGBS). If you have ordered your national coverage via the online ordering system using a polygon outline, then your counts may differ.
* Change-Only Updates (COUs) are not available for the OS Open UPRN product.

## Product supply comparison

There is a difference in product counts between taking a national Managed Great Britain Set (MGBS) and a national Area of Interest (AOI). This is because the two supplies use different selection criteria. The differences are shown in the following table, allowing for you to validate your data holdings once you have loaded the latest release of AddressBase data.

The national AOI refers to the pre-selection GB polygon from our download store. Therefore, if you have drawn your own AOI, the count will vary.

If you are unsure of your supply type, please check this with your OS Relationship Manager.

| Product                | MGBS Full Count | National AOI Full Count | Difference     |
| ---------------------- | --------------- | ----------------------- | -------------- |
| AddressBase            | 31 000 728      | 31 000 727              | 1              |
| AddressBase Plus       | 38 860 895      | 38 860 869              | 26             |
| AddressBase Premium    | See rows below  | See rows below          | See rows below |
| Street                 | 1 532 580       | 1 532 578               | 2              |
| Street Descriptor      | 1 657 099       | 1 657 097               | 2              |
| BLPU                   | 41 676 575      | 41 676 545              | 30             |
| Classification         | 45 440 946      | 45 440 916              | 30             |
| LPI                    | 47 073 085      | 47 073 054              | 31             |
| Organisation           | 1 390 423       | 1 390 421               | 2              |
| Delivery Point Address | 1 390 423       | 31 117 915              | 0              |
| Application Cross Ref. | 201 683 570     | 201 683 540             | 30             |
| Successor              | 0               | 0                       | 0              |

It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in '[Working with COU data](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-getting-started-guide/working-with-cou-data)' in the AddressBase Getting Started Guide.

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the numbers of these records which can be expected in an **MGBS supply**, and also how many tiles are affected if you take your supply as Changed Chunks.

### AddressBase

| Change Type              | Count  |
| ------------------------ | ------ |
| Inserts                  | 35 618 |
| Updates                  | 90 708 |
| Deletes                  | 10 248 |
| COU Populated Tile Count | 5 529  |

### AddressBase Plus

| Change Type              | Count   |
| ------------------------ | ------- |
| Inserts                  | 53 641  |
| Updates                  | 984 181 |
| Deletes                  | 13 436  |
| COU Populated Tile Count | 7 513   |

### AddressBase Premium

| AddressBase Premium Table | Inserts | Updates | Deletes |
| ------------------------- | ------- | ------- | ------- |
| Street                    | 1 139   | 16 434  | 45      |
| Street Descriptor         | 1 245   | 5 752   | 46      |
| BLPU                      | 49 972  | 768 150 | 2 790   |
| Classification            | 66 427  | 102 935 | 18 425  |
| LPI                       | 63 291  | 121 433 | 3 500   |
| Organisation              | 4 747   | 4 532   | 4 274   |
| Delivery Point Address    | 35 858  | 20 890  | 10 021  |
| Application Cross Ref.    | 0       | 0       | 0       |

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 130.

| Data Source                          | Date           |
| ------------------------------------ | -------------- |
| Royal Mail PAF                       | 12 August 2026 |
| National Land and Property Gazetteer | 14 August 2026 |
| One Scotland Gazetteer               | 26 July 2026   |
| VOA Non-Domestic Rates               | 10 August 2026 |
| VOA Council Tax                      | 11 August 2026 |
| OS MasterMap Topography Layer        | 04 August 2026 |
| OS MasterMap Highways Network        | 05 August 2026 |
| Code-Point with Polygons             | 01 July 2026   |
| Boundary-Line                        | 01 May 2026    |

## Data issues

### AddressBase

Details of live and resolved data issues for AddressBase will be communicated on the [AddressBase Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Plus issues

Details of live and resolved data issues for AddressBase Plus will be communicated on the [AddressBase Plus Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus/addressbase-plus-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Premium

Details of live and resolved data issues for AddressBase Premium will be communicated on the [AddressBase Premium Known Data Issues, Service Disruptions and Planned Maintenance page](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium/addressbase-premium-known-data-issues-service-disruptions-and-planned-maintenance). This page will provide details of their impacts and updates on the expected time frame for their resolution.

## Improvements in Epoch 130

### Valuation Office Agency matching

The match rates for Council Tax and Non-Domestic Rates for Epoch 130 are detailed as follows based on Valuation Office Agency (VOA) records up to 11 August 2026. The match rate is applicable to the AddressBase Premium product.

| Data Source        | Records Received | % Matched |
| ------------------ | ---------------- | --------- |
| Council Tax        | 27 510 650       | 99.32%    |
| Non-Domestic Rates | 2 123 085        | 85.18%    |

## Next release

The next release of AddressBase products, **Epoch 131**, is scheduled for **29 October 2026**.


# AddressBase Islands Products September 2026 – Epoch 130

This release note provides information about the September 2026 Epoch 130 release of the AddressBase Islands products. These products were released to customers on 17 September 2026.

## Record counts

| Product                     | Full Supply Record Count | Change-Only Update Record Count |
| --------------------------- | ------------------------ | ------------------------------- |
| AddressBase Plus Islands    | 1 177 146                | 5 980                           |
| AddressBase Premium Islands | See rows below           | See rows below                  |
| Street                      | 49 335                   | 201                             |
| Street Descriptor           | 49 335                   | 24                              |
| BLPU                        | 1 255 376                | 6 902                           |
| Classification              | 1 255 376                | 3 169                           |
| LPI                         | 1 266 008                | 5 296                           |
| Organisation                | 37 963                   | 87                              |
| Delivery Point Address      | 989 585                  | 1 156                           |
| Application Cross Ref.      | 1 320 166                | 2 450                           |
| Successor                   | 0                        | 0                               |

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase Islands product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the count of these records.

### AddressBase Plus Islands

| Change Type | Count |
| ----------- | ----- |
| Inserts     | 1 773 |
| Updates     | 4 015 |
| Deletes     | 192   |

### AddressBase Premium Islands

| AddressBase Premium Table | Inserts | Updates | Deletes |
| ------------------------- | ------- | ------- | ------- |
| Street                    | 24      | 177     | 0       |
| Street Descriptor         | 24      | 0       | 0       |
| BLPU                      | 1 617   | 5 201   | 84      |
| Classification            | 1 617   | 1 468   | 84      |
| LPI                       | 1 662   | 3 550   | 84      |
| Organisation              | 9       | 8       | 70      |
| Delivery Point Address    | 837     | 192     | 127     |
| Application Cross Ref.    | 1,630   | 653     | 167     |
| Successor                 | 0       | 0       | 0       |

It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in '[Working with COU data](https://docs.os.uk/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-getting-started-guide/working-with-cou-data)' in the AddressBase Getting Started Guide

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 130:

| Data Source                                                     | Date           |
| --------------------------------------------------------------- | -------------- |
| <p>Pointer (Northern Ireland)</p><h3 id="data-issues"><br></h3> | 05 August 2026 |
| DigiMap (Channel Islands)                                       | 12 August 2026 |
| Isle of Man                                                     | 12 August 2026 |
| Royal Mail PAF                                                  | 12 August 2026 |

## Data issues

### AddressBase Plus Islands issues

Details of live and resolved data issues for AddressBase Plus Islands will be communicated on the [AddressBase Plus Islands Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus-islands/addressbase-plus-islands-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Premium Islands issues

Details of live and resolved data issues for AddressBase Premium Islands will be communicated on the [AddressBase Premium Islands Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium-islands/addressbase-premium-islands-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

## Next release

The next release of AddressBase Islands products, **Epoch 131**, is scheduled for **29 October 2026.**


# AddressBase Products August 2026 – Epoch 129

This release note provides information about the August (Epoch 129) release of the AddressBase products. These products were released to customers on 06 August 2026.

## Record counts

| Product                | Full Supply Record Count | Change-Only Update Record Count |
| ---------------------- | ------------------------ | ------------------------------- |
| OS Open UPRN           | 41 593 225               | N/A                             |
| AddressBase            | 30 975 358               | 130 146                         |
| AddressBase Plus       | 38 820 690               | 1 011 076                       |
| AddressBase Premium    | See rows below           | See rows below                  |
| Street                 | 1 531 486                | 11 812                          |
| Street Descriptor      | 1 655 900                | 6 934                           |
| BLPU                   | 41 629 393               | 915 753                         |
| Classification         | 45 392 944               | 313 767                         |
| LPI                    | 47 013 294               | 155 218                         |
| Organisation           | 1 389 950                | 12 779                          |
| Delivery Point Address | 31 092 078               | 55 541                          |
| Application Cross Ref. | 201 497 278              | 639 897                         |
| Successor              | 0                        | 0                               |

**Please note:**

* The Full Supply record counts are based on a Managed Great Britain Set (MGBS). If you have ordered your national coverage via the online ordering system using a polygon outline, then your counts may differ.
* Change-Only Updates (COUs) are not available for the OS Open UPRN product.

## Product supply comparison

There is a difference in product counts between taking a national Managed Great Britain Set (MGBS) and a national Area of Interest (AOI). This is because the two supplies use different selection criteria. The differences are shown in the following table, allowing for you to validate your data holdings once you have loaded the latest release of AddressBase data.

The national AOI refers to the pre-selection GB polygon from our download store. Therefore, if you have drawn your own AOI, the count will vary.

If you are unsure of your supply type, please check this with your OS Relationship Manager.

| Product                | MGBS Full Count | National AOI Full Count | Difference     |
| ---------------------- | --------------- | ----------------------- | -------------- |
| AddressBase            | 30 975 358      | 30 975 357              | 1              |
| AddressBase Plus       | 38 820 690      | 38 820 665              | 25             |
| AddressBase Premium    | See rows below  | See rows below          | See rows below |
| Street                 | 1 531 486       | 1 531 484               | 2              |
| Street Descriptor      | 1 655 900       | 1 655 898               | 2              |
| BLPU                   | 41 629 393      | 41 629 366              | 27             |
| Classification         | 45 392 944      | 45 392 917              | 27             |
| LPI                    | 47 013 294      | 47 013 266              | 28             |
| Organisation           | 1 389 950       | 1 389 948               | 2              |
| Delivery Point Address | 31 092 078      | 31 092 078              | 0              |
| Application Cross Ref. | 201 497 278     | 201 497 251             | 27             |
| Successor              | 0               | 0                       | 0              |

It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in '[Working with COU data](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-getting-started-guide/working-with-cou-data)' in the AddressBase Getting Started Guide.

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the numbers of these records which can be expected in an **MGBS supply**, and also how many tiles are affected if you take your supply as Changed Chunks.

### AddressBase

| Change Type              | Count  |
| ------------------------ | ------ |
| Inserts                  | 31 528 |
| Updates                  | 90 136 |
| Deletes                  | 8 482  |
| COU Populated Tile Count | 5 289  |

### AddressBase Plus

| Change Type              | Count   |
| ------------------------ | ------- |
| Inserts                  | 46 421  |
| Updates                  | 949 822 |
| Deletes                  | 14 833  |
| COU Populated Tile Count | 7 334   |

### AddressBase Premium

| AddressBase Premium Table | Inserts | Updates | Deletes |
| ------------------------- | ------- | ------- | ------- |
| Street                    | 1 313   | 10 254  | 245     |
| Street Descriptor         | 1 357   | 5 322   | 245     |
| BLPU                      | 39 354  | 873 213 | 3 186   |
| Classification            | 83 420  | 162 568 | 67 779  |
| LPI                       | 52 006  | 98 975  | 4 237   |
| Organisation              | 4 268   | 4 245   | 4 266   |
| Delivery Point Address    | 31 906  | 15 324  | 8 311   |
| Application Cross Ref.    | 193 742 | 383 548 | 62 607  |

## Source data currency

The following information relates to the currency of the source data used in the creation of **Epoch 129**:

| Data Source                          | Date         |
| ------------------------------------ | ------------ |
| Royal Mail PAF                       | 02 July 2026 |
| National Land and Property Gazetteer | 02 July 2026 |
| One Scotland Gazetteer               | 02 July 2026 |
| VOA Non-Domestic Rates               | 01 July 2026 |
| VOA Council Tax                      | 01 July 2026 |
| OS MasterMap Topography Layer        | 22 June 2026 |
| OS MasterMap Highways Network        | 03 June 2026 |
| Code-Point with Polygons             | 01 July 2026 |
| Boundary-Line                        | 01 May 2026  |

## Data issues

### AddressBase

Details of live and resolved data issues for AddressBase will be communicated on the [AddressBase Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Plus issues

Details of live and resolved data issues for AddressBase Plus will be communicated on the [AddressBase Plus Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus/addressbase-plus-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Premium

Details of live and resolved data issues for AddressBase Premium will be communicated on the [AddressBase Premium Known Data Issues, Service Disruptions and Planned Maintenance page](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium/addressbase-premium-known-data-issues-service-disruptions-and-planned-maintenance). This page will provide details of their impacts and updates on the expected time frame for their resolution.

## Improvements in Epoch 129

### Valuation Office Agency matching

The match rates for Council Tax and Non-Domestic Rates for **Epoch 129** are detailed as follows based on Valuation Office Agency (VOA) records up to **01 July 2026**. The match rate is applicable to the AddressBase Premium product.

| Data Source        | Records Received | % Matched |
| ------------------ | ---------------- | --------- |
| Council Tax        | 27 483 969       | 99.99     |
| Non-Domestic Rates | 2 121 123        | 96.52     |

## Next release

The next release of AddressBase products, **Epoch 130**, is scheduled for **17 September 2026**.


# AddressBase Islands Products August 2026 – Epoch 129

This release note provides information about the August 2026 Epoch 129 release of the AddressBase Islands products. These products were released to customers on 06 August 2026.

## Record counts

| Product                     | Full Supply Record Count | Change-Only Update Record Count |
| --------------------------- | ------------------------ | ------------------------------- |
| AddressBase Plus Islands    | 1 175 565                | 5 206                           |
| AddressBase Premium Islands | See rows below           | See rows below                  |
| Street                      | 49 311                   | 140                             |
| Street Descriptor           | 49 311                   | 26                              |
| BLPU                        | 1 253 843                | 5 368                           |
| Classification              | 1 253 843                | 2 288                           |
| LPI                         | 1 264 430                | 3 273                           |
| Organisation                | 38 024                   | 229                             |
| Delivery Point Address      | 988 875                  | 1 253                           |
| Application Cross Ref.      | 1 318 703                | 2 257                           |
| Successor                   | 0                        | 0                               |

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase Islands product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the count of these records.

### AddressBase Plus Islands

| Change Type | Count |
| ----------- | ----- |
| Inserts     | 1 508 |
| Updates     | 3 497 |
| Deletes     | 201   |

### AddressBase Premium Islands

| AddressBase Premium Table | Inserts | Updates | Deletes |
| ------------------------- | ------- | ------- | ------- |
| Street                    | 25      | 115     | 0       |
| Street Descriptor         | 25      | 1       | 0       |
| BLPU                      | 1 015   | 4 286   | 67      |
| Classification            | 1 015   | 1 206   | 67      |
| LPI                       | 1 092   | 2 114   | 67      |
| Organisation              | 60      | 59      | 110     |
| Delivery Point Address    | 920     | 258     | 75      |
| Application Cross Ref.    | 1 028   | 1 078   | 151     |
| Successor                 | 0       | 0       | 0       |

It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in '[Working with COU data](https://docs.os.uk/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-getting-started-guide/working-with-cou-data)' in the AddressBase Getting Started Guide

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 129:

| Data Source                                                     | Date         |
| --------------------------------------------------------------- | ------------ |
| <p>Pointer (Northern Ireland)</p><h3 id="data-issues"><br></h3> | 30 June 2026 |
| DigiMap (Channel Islands)                                       | 01 July 2026 |
| Isle of Man                                                     | 01 July 2026 |
| Royal Mail PAF                                                  | 02 July 2026 |

## Data issues

### AddressBase Plus Islands issues

Details of live and resolved data issues for AddressBase Plus Islands will be communicated on the [AddressBase Plus Islands Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus-islands/addressbase-plus-islands-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Premium Islands issues

Details of live and resolved data issues for AddressBase Premium Islands will be communicated on the [AddressBase Premium Islands Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium-islands/addressbase-premium-islands-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

## Next release

The next release of AddressBase Islands products, **Epoch 130**, is scheduled for **17 September 2026.**


# AddressBase Products June 2026 – Epoch 128

This release note provides information about the June 2026 (Epoch 128) release of the AddressBase products. These products were released to customers on 25 June 2026.

## Record counts

| Product                | Full Supply Record Count | Change-Only Update Record Count |
| ---------------------- | ------------------------ | ------------------------------- |
| OS Open UPRN           | 41 593 225               | N/A                             |
| AddressBase            | 30 952 312               | 135 790                         |
| AddressBase Plus       | 38 789 102               | 4 167 563                       |
| AddressBase Premium    | See rows below           | See rows below                  |
| Street                 | 1 530 418                | 8 576                           |
| Street Descriptor      | 1 654 788                | 5 398                           |
| BLPU                   | 41 593 225               | 1 208 933                       |
| Classification         | 45 377 303               | 173 882                         |
| LPI                    | 46 965 525               | 156 033                         |
| Organisation           | 1 389 948                | 15 603                          |
| Delivery Point Address | 31 068 483               | 65 596                          |
| Application Cross Ref. | 201 366 143              | 7 034 623                       |
| Successor              | 0                        | 0                               |

**Please note:**

* The Full Supply record counts are based on a Managed Great Britain Set (MGBS). If you have ordered your national coverage via the online ordering system using a polygon outline, then your counts may differ.
* Change-Only Updates (COUs) are not available for the OS Open UPRN product.

## Product supply comparison

There is a difference in product counts between taking a national Managed Great Britain Set (MGBS) and a national Area of Interest (AOI). This is because the two supplies use different selection criteria. The differences are shown in the following table, allowing for you to validate your data holdings once you have loaded the latest release of AddressBase data.

The national AOI refers to the pre-selection GB polygon from our download store. Therefore, if you have drawn your own AOI, the count will vary.

If you are unsure of your supply type, please check this with your OS Relationship Manager.

| Product                | MGBS Full Count | National AOI Full Count | Difference     |
| ---------------------- | --------------- | ----------------------- | -------------- |
| AddressBase            | 30 952 312      | 30 952 311              | 1              |
| AddressBase Plus       | 38 789 102      | 38 789 076              | 26             |
| AddressBase Premium    | See rows below  | See rows below          | See rows below |
| Street                 | 1 530 418       | 1 530 416               | 2              |
| Street Descriptor      | 1 654 788       | 1 654 786               | 2              |
| BLPU                   | 41 593 225      | 41 593 196              | 29             |
| Classification         | 45 377 303      | 45 377 272              | 31             |
| LPI                    | 46 965 525      | 46 965 495              | 30             |
| Organisation           | 1 389 948       | 1 389 946               | 2              |
| Delivery Point Address | 31 068 483      | 31 068 482              | 1              |
| Application Cross Ref. | 201 366 143     | 201 366 113             | 30             |
| Successor              | 0               | 0                       | 0              |

It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in '[Working with COU data](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-getting-started-guide/working-with-cou-data)' in the AddressBase Getting Started Guide.

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the numbers of these records which can be expected in an **MGBS supply**, and also how many tiles are affected if you take your supply as Changed Chunks.

### AddressBase

| Change Type              | Count  |
| ------------------------ | ------ |
| Inserts                  | 38 340 |
| Updates                  | 86 943 |
| Deletes                  | 10 507 |
| COU Populated Tile Count | 5 284  |

### AddressBase Plus

| Change Type              | Count     |
| ------------------------ | --------- |
| Inserts                  | 59 013    |
| Updates                  | 4 094 953 |
| Deletes                  | 13 597    |
| COU Populated Tile Count | 7 102     |

### AddressBase Premium

| AddressBase Premium Table | Inserts   | Updates   | Deletes   |
| ------------------------- | --------- | --------- | --------- |
| Street                    | 4 233     | 4 187     | 156       |
| Street Descriptor         | 4 275     | 966       | 157       |
| BLPU                      | 50 042    | 1 155 592 | 3 299     |
| Classification            | 60 594    | 96 900    | 16 388    |
| LPI                       | 63 478    | 88 525    | 4 030     |
| Organisation              | 4 783     | 6 821     | 3 999     |
| Delivery Point Address    | 38 725    | 16 379    | 10 492    |
| Application Cross Ref.    | 3 561 768 | 333 594   | 3 139 261 |

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 128:

| Data Source                          | Date          |
| ------------------------------------ | ------------- |
| Royal Mail PAF                       | 22 April 2026 |
| National Land and Property Gazetteer | 22 April 2026 |
| One Scotland Gazetteer               | 21 May 2026   |
| VOA Non-Domestic Rates               | 19 May 2026   |
| VOA Council Tax                      | 19 May 2026   |
| OS MasterMap Topography Layer        | 12 May 2026   |
| OS MasterMap Highways Network        | 08 May 2026   |
| Code-Point with Polygons             | 01 April 2026 |
| Boundary-Line                        | 01 May 2026   |

## Data issues

### AddressBase

Details of live and resolved data issues for AddressBase will be communicated on the [AddressBase Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Plus issues

Details of live and resolved data issues for AddressBase Plus will be communicated on the [AddressBase Plus Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus/addressbase-plus-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Premium

Details of live and resolved data issues for AddressBase Premium will be communicated on the [AddressBase Premium Known Data Issues, Service Disruptions and Planned Maintenance page](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium/addressbase-premium-known-data-issues-service-disruptions-and-planned-maintenance). This page will provide details of their impacts and updates on the expected time frame for their resolution.

## Improvements in Epoch 128

### Valuation Office Agency matching

The match rates for Council Tax and Non-Domestic Rates for **Epoch 128** are detailed as follows based on Valuation Office Agency (VOA) records up to **19 May 2026**. The match rate is applicable to the AddressBase Premium product.

| Data Source        | Records Received | % Matched |
| ------------------ | ---------------- | --------- |
| Council Tax        | 27 472 486       | 99.98     |
| Non-Domestic Rates | 2 131 965        | 96.52     |

## Next release

The next release of AddressBase products, **Epoch 129**, is scheduled for **06 August 2026**.

### **VOA Resync – Address data update (planned maintenance)**

A VOA resynchronisation activity is being undertaken to correct and align address data, improving overall data currency and completeness. The update is expected to introduce a higher-than-normal volume of changes (\~75,000 records), resulting in larger COU files for affected products.

The changes will be reflected in **Epoch 129** for AddressBase Premium.

### Customer impact

Customers should expect increased file sizes and a higher volume of change records in the relevant epoch; no service downtime is anticipated.


# AddressBase Islands Products June 2026 – Epoch 128

This release note provides information about the June 2026 Epoch 128 release of the AddressBase Islands products. These products were released to customers on 25 June 2026.

## Record counts

| Product                     | Full Supply Record Count | Change-Only Update Record Count |
| --------------------------- | ------------------------ | ------------------------------- |
| AddressBase Plus Islands    | 1 174 258                | 5 952                           |
| AddressBase Premium Islands | See rows below           | See rows below                  |
| Street                      | 49 286                   | 293                             |
| Street Descriptor           | 49 286                   | 42                              |
| BLPU                        | 1 252 895                | 6 454                           |
| Classification              | 1 252 895                | 2 881                           |
| LPI                         | 1 263 405                | 3 493                           |
| Organisation                | 38 074                   | 939                             |
| Delivery Point Address      | 988 030                  | 1 935                           |
| Application Cross Ref.      | 1 317 826                | 1 960                           |
| Successor                   | 0                        | 0                               |

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase Islands product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the count of these records.

### AddressBase Plus Islands

| Change Type | Count |
| ----------- | ----- |
| Inserts     | 1 276 |
| Updates     | 3 700 |
| Deletes     | 976   |

### AddressBase Premium Islands

| AddressBase Premium Table | Inserts | Updates | Deletes |
| ------------------------- | ------- | ------- | ------- |
| Street                    | 42      | 251     | 0       |
| Street Descriptor         | 42      | 0       | 0       |
| BLPU                      | 1 251   | 5 133   | 70      |
| Classification            | 1 251   | 1 560   | 70      |
| LPI                       | 1 275   | 2 148   | 70      |
| Organisation              | 245     | 538     | 156     |
| Delivery Point Address    | 809     | 220     | 906     |
| Application Cross Ref.    | 1 302   | 447     | 211     |
| Successor                 | 0       | 0       | 0       |

It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in '[Working with COU data](https://docs.os.uk/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-getting-started-guide/working-with-cou-data)' in the AddressBase Getting Started Guide

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 128:

| Data Source                                                     | Date        |
| --------------------------------------------------------------- | ----------- |
| <p>Pointer (Northern Ireland)</p><h3 id="data-issues"><br></h3> | 20 May 2026 |
| DigiMap (Channel Islands)                                       | 10 May 2026 |
| Isle of Man                                                     | 10 May 2026 |
| Royal Mail PAF                                                  | 10 May 2026 |

## Data issues

### AddressBase Plus Islands issues

Details of live and resolved data issues for AddressBase Plus Islands will be communicated on the [AddressBase Plus Islands Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus-islands/addressbase-plus-islands-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Premium Islands issues

Details of live and resolved data issues for AddressBase Premium Islands will be communicated on the [AddressBase Premium Islands Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium-islands/addressbase-premium-islands-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

## Next release

The next release of AddressBase Islands products, **Epoch 129**, is scheduled for **06 August 2026.**


# AddressBase Products May 2026 – Epoch 127

This release note provides information about the May 2026 (Epoch 127) release of the AddressBase products. These products were released to customers on 14 May 2026.

## Record counts

<table><thead><tr><th width="169.6666259765625">Product</th><th>Full Supply Record Count</th><th>Change-Only Update Record Count</th></tr></thead><tbody><tr><td>OS Open UPRN</td><td>41 546 482</td><td>N/A</td></tr><tr><td>AddressBase</td><td>30 924 479</td><td>130 223</td></tr><tr><td>AddressBase Plus</td><td>38 743 686</td><td>849 637</td></tr><tr><td>AddressBase Premium</td><td>See rows below</td><td>See rows below</td></tr><tr><td>Street</td><td>1 526 341</td><td>16 251</td></tr><tr><td>Street Descriptor</td><td>1 650 670</td><td>5 027</td></tr><tr><td>BLPU</td><td>41 546 482</td><td>804 236</td></tr><tr><td>Classification</td><td>45 333 097</td><td>168 187</td></tr><tr><td>LPI</td><td>46 906 077</td><td>167 545</td></tr><tr><td>Organisation</td><td>1 389 164</td><td>16 417</td></tr><tr><td>Delivery Point Address</td><td>31 040 250</td><td>55 299</td></tr><tr><td>Application Cross Ref.</td><td>200 943 636</td><td>733 641</td></tr><tr><td>Successor</td><td>0</td><td>0</td></tr></tbody></table>

**Please note:**

* The Full Supply record counts are based on a Managed Great Britain Set (MGBS). If you have ordered your national coverage via the online ordering system using a polygon outline, then your counts may differ.
* Change-Only Updates (COUs) are not available for the OS Open UPRN product.

## Product supply comparison

There is a difference in product counts between taking a national Managed Great Britain Set (MGBS) and a national Area of Interest (AOI). This is because the two supplies use different selection criteria. The differences are shown in the following table, allowing for you to validate your data holdings once you have loaded the latest release of AddressBase data.

The national AOI refers to the pre-selection GB polygon from our download store. Therefore, if you have drawn your own AOI, the count will vary.

If you are unsure of your supply type, please check this with your OS Relationship Manager.

| Product                | MGBS Full Count | National AOI Full Count | Difference     |
| ---------------------- | --------------- | ----------------------- | -------------- |
| AddressBase            | 30 924 479      | 30 924 478              | 1              |
| AddressBase Plus       | 38 743 686      | 38 743 660              | 26             |
| AddressBase Premium    | See rows below  | See rows below          | See rows below |
| Street                 | 1 526 341       | 1 526 339               | 2              |
| Street Descriptor      | 1 650 670       | 1 650 668               | 2              |
| BLPU                   | 41 546 482      | 41 546 453              | 29             |
| Classification         | 45 333 097      | 45 333 066              | 31             |
| LPI                    | 46 906 077      | 46 906 047              | 30             |
| Organisation           | 1 389 164       | 1 389 162               | 2              |
| Delivery Point Address | 31 040 250      | 31 040 249              | 1              |
| Application Cross Ref. | 200 943 636     | 200 943 606             | 30             |
| Successor              | 0               | 0                       | 0              |

It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in '[Working with COU data](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-getting-started-guide/working-with-cou-data)' in the AddressBase Getting Started Guide.

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the numbers of these records which can be expected in an **MGBS supply**, and also how many tiles are affected if you take your supply as Changed Chunks.

### AddressBase

| Change Type              | Count  |
| ------------------------ | ------ |
| Inserts                  | 35 340 |
| Updates                  | 86 132 |
| Deletes                  | 8 751  |
| COU Populated Tile Count | 5 782  |

### AddressBase Plus

| Change Type              | Count   |
| ------------------------ | ------- |
| Inserts                  | 52 923  |
| Updates                  | 785 703 |
| Deletes                  | 15 141  |
| COU Populated Tile Count | 7 746   |

### AddressBase Premium

| AddressBase Premium Table | Inserts | Updates | Deletes |
| ------------------------- | ------- | ------- | ------- |
| Street                    | 1 414   | 14 757  | 80      |
| Street Descriptor         | 1 456   | 3 491   | 80      |
| BLPU                      | 44 268  | 754 821 | 5 147   |
| Classification            | 55 960  | 95 212  | 17 015  |
| LPI                       | 57 022  | 104 141 | 6 382   |
| Organisation              | 7 085   | 5 047   | 4 285   |
| Delivery Point Address    | 35 789  | 11 072  | 8 438   |
| Application Cross Ref.    | 207 708 | 487 396 | 38 537  |

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 127:

| Data Source                          | Date            |
| ------------------------------------ | --------------- |
| Royal Mail PAF                       | 09 April 2026   |
| National Land and Property Gazetteer | 09 April 2026   |
| One Scotland Gazetteer               | 22 March 2026   |
| VOA Non-Domestic Rates               | 07 April 2026   |
| VOA Council Tax                      | 07 April 2026   |
| OS MasterMap Topography Layer        | 31 March 2026   |
| OS MasterMap Highways Network        | 08 April 2026   |
| Code-Point with Polygons             | 01 April 2026   |
| Boundary-Line                        | 02 October 2025 |

## Data issues

### AddressBase

Details of live and resolved data issues for AddressBase will be communicated on the [AddressBase Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Plus issues

Details of live and resolved data issues for AddressBase Plus will be communicated on the [AddressBase Plus Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus/addressbase-plus-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Premium

Details of live and resolved data issues for AddressBase Premium will be communicated on the [AddressBase Premium Known Data Issues, Service Disruptions and Planned Maintenance page](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium/addressbase-premium-known-data-issues-service-disruptions-and-planned-maintenance). This page will provide details of their impacts and updates on the expected time frame for their resolution.

## Improvements in Epoch 127

### Valuation Office Agency matching

The match rates for Council Tax and Non-Domestic Rates for Epoch 127 are detailed as follows based on Valuation Office Agency (VOA) records up to 07 April 2026. The match rate is applicable to the AddressBase Premium product.

| Data Source        | Records Received | % Matched |
| ------------------ | ---------------- | --------- |
| Council Tax        | 27 453 896       | 99.89     |
| Non-Domestic Rates | 2 130 117        | 96.41     |

## Next release

The next release of AddressBase products, Epoch 128, is scheduled for **25 June 2026.**


# AddressBase Islands Products May 2026 – Epoch 127

This release note provides information about the May 2026 Epoch 127 release of the AddressBase Islands products. These products were released to customers on 14 May 2026.

## Record counts

| Product                     | Full Supply Record Count | Change-Only Update Record Count |
| --------------------------- | ------------------------ | ------------------------------- |
| AddressBase Plus Islands    | 1 173 958                | 4 130                           |
| AddressBase Premium Islands | See rows below           | See rows below                  |
| Street                      | 49 244                   | 166                             |
| Street Descriptor           | 49 244                   | 29                              |
| BLPU                        | 1 251 714                | 4 580                           |
| Classification              | 1 251 714                | 1 791                           |
| LPI                         | 1 262 200                | 2 623                           |
| Organisation                | 37 985                   | 88                              |
| Delivery Point Address      | 988 127                  | 1 366                           |
| Application Cross Ref.      | 1 316 735                | 2 147                           |
| Successor                   | 0                        | 0                               |

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase Islands product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the count of these records.

### AddressBase Plus Islands

| Change Type | Count |
| ----------- | ----- |
| Inserts     | 1 137 |
| Updates     | 2 661 |
| Deletes     | 638   |

### AddressBase Premium Islands

| AddressBase Premium Table | Inserts | Updates | Deletes |
| ------------------------- | ------- | ------- | ------- |
| Street                    | 27      | 139     | 0       |
| Street Descriptor         | 27      | 2       | 0       |
| BLPU                      | 898     | 3 410   | 272     |
| Classification            | 898     | 621     | 272     |
| LPI                       | 972     | 1 379   | 272     |
| Organisation              | 20      | 24      | 44      |
| Delivery Point Address    | 1 025   | 182     | 159     |
| Application Cross Ref.    | 926     | 867     | 354     |
| Successor                 | 0       | 0       | 0       |

It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in '[Working with COU data](https://docs.os.uk/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-getting-started-guide/working-with-cou-data)' in the AddressBase Getting Started Guide

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 127:

| Data Source                                                     | Date          |
| --------------------------------------------------------------- | ------------- |
| <p>Pointer (Northern Ireland)</p><h3 id="data-issues"><br></h3> | 01 April 2026 |
| DigiMap (Channel Islands)                                       | 08 April 2026 |
| Isle of Man                                                     | 09 April 2026 |
| Royal Mail PAF                                                  | 09 April 2026 |

## Data issues

### AddressBase Plus Islands issues

Details of live and resolved data issues for AddressBase Plus Islands will be communicated on the [AddressBase Plus Islands Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus-islands/addressbase-plus-islands-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Premium Islands issues

Details of live and resolved data issues for AddressBase Premium Islands will be communicated on the [AddressBase Premium Islands Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium-islands/addressbase-premium-islands-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

## Next release

The next release of AddressBase Islands products, Epoch 128, is scheduled for **25 June 2026.**


# AddressBase Products April 2026 – Epoch 126

This release note provides information about the April 2026 Epoch 126 release of the AddressBase products. These products were released to customers on 02 April 2026.

## Record counts

| Product                | Full Supply Record Count | Change-Only Update Record Count |
| ---------------------- | ------------------------ | ------------------------------- |
| OS Open UPRN           | 41 507 361               | N/A                             |
| AddressBase            | 30 897 890               | 138 295                         |
| AddressBase Plus       | 38 706 709               | 733 300                         |
| AddressBase Premium    | See rows below           | See rows below                  |
| Street                 | 1 525 007                | 16 118                          |
| Street Descriptor      | 1 649 294                | 2 502                           |
| BLPU                   | 41 507 361               | 655 949                         |
| Classification         | 45 294 152               | 165 924                         |
| LPI                    | 46 855 437               | 175 454                         |
| Organisation           | 1 386 364                | 14 108                          |
| Delivery Point Address | 31 012 899               | 63 989                          |
| Application Cross Ref. | 200 774 465              | 620 825                         |
| Successor              | 0                        | 0                               |

**Please note:**

* The Full Supply record counts are based on a Managed Great Britain Set (MGBS). If you have ordered your national coverage via the online ordering system using a polygon outline, then your counts may differ.
* Change-Only Updates (COUs) are not available for the OS Open UPRN product.

## Product supply comparison

There is a difference in product counts between taking a national Managed Great Britain Set (MGBS) and a national Area of Interest (AOI). This is because the two supplies use different selection criteria. The differences are shown in the following table, allowing for you to validate your data holdings once you have loaded the latest release of AddressBase data.

The national AOI refers to the pre-selection GB polygon from our download store. Therefore, if you have drawn your own AOI, the count will vary.

If you are unsure of your supply type, please check this with your OS Relationship Manager.

| Product                | MGBS Full Count | National AOI Full Count | Difference     |
| ---------------------- | --------------- | ----------------------- | -------------- |
| AddressBase            | 30 897 890      | 30 897 889              | 1              |
| AddressBase Plus       | 38 706 709      | 38 706 682              | 27             |
| AddressBase Premium    | See rows below  | See rows below          | See rows below |
| Street                 | 1 525 007       | 1 525 004               | 3              |
| Street Descriptor      | 1 649 294       | 1 649 291               | 3              |
| BLPU                   | 41 507 361      | 41 507 331              | 30             |
| Classification         | 45 294 152      | 45 294 120              | 32             |
| LPI                    | 46 855 437      | 46 855 406              | 31             |
| Organisation           | 1 386 364       | 1 386 362               | 2              |
| Delivery Point Address | 31 012 899      | 31 012 898              | 1              |
| Application Cross Ref. | 200 774 465     | 200 774 434             | 31             |
| Successor              | 0               | 0                       | 0              |

It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in '[Working with COU data](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-getting-started-guide/working-with-cou-data)' in the AddressBase Getting Started Guide.

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the numbers of these records which can be expected in an **MGBS supply**, and also how many tiles are affected if you take your supply as Changed Chunks.

### AddressBase

| Change Type              | Count  |
| ------------------------ | ------ |
| Inserts                  | 34 944 |
| Updates                  | 92 168 |
| Deletes                  | 11 183 |
| COU Populated Tile Count | 5 198  |

### AddressBase Plus

| Change Type              | Count   |
| ------------------------ | ------- |
| Inserts                  | 55 006  |
| Updates                  | 671 373 |
| Deletes                  | 13 152  |
| COU Populated Tile Count | 7 080   |

### AddressBase Premium

| AddressBase Premium Table | Inserts | Updates | Deletes |
| ------------------------- | ------- | ------- | ------- |
| Street                    | 1 068   | 14 989  | 61      |
| Street Descriptor         | 1 107   | 1 331   | 64      |
| BLPU                      | 45 018  | 607 147 | 3 784   |
| Classification            | 56 866  | 87 934  | 21 124  |
| LPI                       | 57 671  | 112 787 | 4 996   |
| Organisation              | 4 349   | 5 194   | 4 565   |
| Delivery Point Address    | 35 532  | 17 075  | 11 382  |
| Application Cross Ref.    | 205 091 | 379 576 | 36 158  |

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch **126**:

| Data Source                          | Date             |
| ------------------------------------ | ---------------- |
| Royal Mail PAF                       | 26 February 2026 |
| National Land and Property Gazetteer | 26 February 2026 |
| One Scotland Gazetteer               | 08 February 2026 |
| VOA Non-Domestic Rates               | 24 February 2026 |
| VOA Council Tax                      | 24 February 2026 |
| OS MasterMap Topography Layer        | 17 February 2026 |
| OS MasterMap Highways Network        | 05 February 2026 |
| Code-Point with Polygons             | 02 January 2026  |
| Boundary-Line                        | 02 October 2025  |

## Data issues

### AddressBase

Details of live and resolved data issues for AddressBase will be communicated on the [AddressBase Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Plus issues

Details of live and resolved data issues for AddressBase Plus will be communicated on the [AddressBase Plus Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus/addressbase-plus-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Premium

Details of live and resolved data issues for AddressBase Premium will be communicated on the [AddressBase Premium Known Data Issues, Service Disruptions and Planned Maintenance page](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium/addressbase-premium-known-data-issues-service-disruptions-and-planned-maintenance). This page will provide details of their impacts and updates on the expected time frame for their resolution.

## Improvements in Epoch 126

### Valuation Office Agency matching

The match rates for Council Tax and Non-Domestic Rates for Epoch 126 are detailed as follows based on Valuation Office Agency (VOA) records up to **24 February 2026.** The match rate is applicable to the AddressBase Premium product.

| Data Source        | Records Received | % Matched |
| ------------------ | ---------------- | --------- |
| Council Tax        | 27 423 462       | 99.89     |
| Non-Domestic Rates | 2 125 966        | 96.44     |

### Tertiary classifications

Work is being undertaken to improve the classifications of records within the AddressBase products. This work has resulted in **45 684** more tertiary classifications present in Epoch **126** compared to Epoch **125**. Indeed, **87.99 %** of these tertiary classification improvements are against residential codes.

## Next release

The next release of AddressBase products, Epoch **127**, is scheduled for **14 May 2026**.


# AddressBase Islands Products April 2026 – Epoch 126

This release note provides information about the April 2026 Epoch 126 release of the AddressBase Islands products. These products were released to customers on 02 April 2026.

## Record counts

| Product                     | Full Supply Record Count | Change-Only Update Record Count |
| --------------------------- | ------------------------ | ------------------------------- |
| AddressBase Plus Islands    | 1 173 153                | 6 231                           |
| AddressBase Premium Islands | See rows below           | See rows below                  |
| Street                      | 49 217                   | 131                             |
| Street Descriptor           | 49 217                   | 22                              |
| BLPU                        | 1 251 088                | 6 329                           |
| Classification              | 1 251 088                | 2 975                           |
| LPI                         | 1 261 500                | 2 866                           |
| Organisation                | 38 009                   | 1 689                           |
| Delivery Point Address      | 987 261                  | 1 496                           |
| Application Cross Ref.      | 1 316 163                | 2 016                           |
| Successor                   | 0                        | 0                               |

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase Islands product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the count of these records.

### AddressBase Plus Islands

| Change Type | Count |
| ----------- | ----- |
| Inserts     | 933   |
| Updates     | 4 660 |
| Deletes     | 638   |

### AddressBase Premium Islands

| AddressBase Premium Table | Inserts | Updates | Deletes |
| ------------------------- | ------- | ------- | ------- |
| Street                    | 21      | 110     | 0       |
| Street Descriptor         | 21      | 1       | 0       |
| BLPU                      | 699     | 5 389   | 241     |
| Classification            | 699     | 2 035   | 241     |
| LPI                       | 713     | 1 912   | 241     |
| Organisation              | 234     | 795     | 660     |
| Delivery Point Address    | 885     | 430     | 181     |
| Application Cross Ref.    | 732     | 883     | 401     |
| Successor                 | 0       | 0       | 0       |

It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in '[Working with COU data](https://docs.os.uk/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-getting-started-guide/working-with-cou-data)' in the AddressBase Getting Started Guide

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 126:

| Data Source                                                     | Date             |
| --------------------------------------------------------------- | ---------------- |
| <p>Pointer (Northern Ireland)</p><h3 id="data-issues"><br></h3> | 18 February 2026 |
| DigiMap (Channel Islands)                                       | 26 February 2026 |
| Isle of Man                                                     | 26 February 2026 |
| Royal Mail PAF                                                  | 26 February 2026 |

## Data issues

### AddressBase Plus Islands issues

Details of live and resolved data issues for AddressBase Plus Islands will be communicated on the [AddressBase Plus Islands Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus-islands/addressbase-plus-islands-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Premium Islands issues

Details of live and resolved data issues for AddressBase Premium Islands will be communicated on the [AddressBase Premium Islands Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium-islands/addressbase-premium-islands-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

## Next release

The next release of AddressBase Islands products, Epoch 127, is scheduled for **14 May 2026.**


# AddressBase Products February 2026 – Epoch 125

This release note provides information about the February 2026 Epoch 125 release of the AddressBase products. These products were released to customers on 19 February 2026.

## Record counts

<table><thead><tr><th>Product</th><th>Full Supply Record Count</th><th width="183.328125">Change-Only Update Record Count</th></tr></thead><tbody><tr><td>OS Open UPRN</td><td>41 431 031</td><td>N/A</td></tr><tr><td>AddressBase</td><td>30 874 129</td><td>126 236</td></tr><tr><td>AddressBase Plus</td><td>38 665 150</td><td>540 622</td></tr><tr><td>AddressBase Premium</td><td>See rows below</td><td>See rows below</td></tr><tr><td>Street</td><td>1 524 000</td><td>8 604</td></tr><tr><td>Street Descriptor</td><td>1 648 251</td><td>1 788</td></tr><tr><td>BLPU</td><td>41 466 127</td><td>393 436</td></tr><tr><td>Classification</td><td>45 258 410</td><td>122 086</td></tr><tr><td>LPI</td><td>46 802 762</td><td>155 177</td></tr><tr><td>Organisation</td><td>1 386 580</td><td>13 693</td></tr><tr><td>Delivery Point Address</td><td>30 988 749</td><td>63 449</td></tr><tr><td>Application Cross Ref.</td><td>200 605 532</td><td>553 973</td></tr><tr><td>Successor</td><td>0</td><td>0</td></tr></tbody></table>

**Please note:**

* The Full Supply record counts are based on a Managed Great Britain Set (MGBS). If you have ordered your national coverage via the online ordering system using a polygon outline, then your counts may differ.
* Change-Only Updates (COUs) are not available for the OS Open UPRN product.

## Product supply comparison

There is a difference in product counts between taking a national Managed Great Britain Set (MGBS) and a national Area of Interest (AOI). This is because the two supplies use different selection criteria. The differences are shown in the following table, allowing for you to validate your data holdings once you have loaded the latest release of AddressBase data.

The national AOI refers to the pre-selection GB polygon from our download store. Therefore, if you have drawn your own AOI, the count will vary.

If you are unsure of your supply type, please check this with your OS Relationship Manager.

| Product                | MGBS Full Count | National AOI Full Count | Difference     |
| ---------------------- | --------------- | ----------------------- | -------------- |
| AddressBase            | 30 874 129      | 30 874 128              | 1              |
| AddressBase Plus       | 38 665 150      | 38 665 123              | 27             |
| AddressBase Premium    | See rows below  | See rows below          | See rows below |
| Street                 | 1 524 000       | 1 523 997               | 3              |
| Street Descriptor      | 1 648 251       | 1 648 248               | 3              |
| BLPU                   | 41 466 127      | 41 466 097              | 30             |
| Classification         | 45 258 410      | 45 258 378              | 32             |
| LPI                    | 46 802 762      | 46 802 731              | 31             |
| Organisation           | 1 386 580       | 1 386 578               | 2              |
| Delivery Point Address | 30 988 749      | 30 988 748              | 1              |
| Application Cross Ref. | 200 605 532     | 200 605 501             | 31             |
| Successor              | 0               | 0                       | 0              |

It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in '[Working with COU data](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-getting-started-guide/working-with-cou-data)' in the AddressBase Getting Started Guide.

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the numbers of these records which can be expected in an **MGBS supply**, and also how many tiles are affected if you take your supply as Changed Chunks.

### AddressBase

| Change Type              | Count  |
| ------------------------ | ------ |
| Inserts                  | 38 200 |
| Updates                  | 78 063 |
| Deletes                  | 9 973  |
| COU Populated Tile Count | 5 055  |

### AddressBase Plus

| Change Type              | Count   |
| ------------------------ | ------- |
| Inserts                  | 54 832  |
| Updates                  | 471 150 |
| Deletes                  | 14 640  |
| COU Populated Tile Count | 6 718   |

### AddressBase Premium

| AddressBase Premium Table | Inserts | Updates | Deletes |
| ------------------------- | ------- | ------- | ------- |
| Street                    | 951     | 7 645   | 8       |
| Street Descriptor         | 1 021   | 757     | 10      |
| BLPU                      | 38 515  | 351 502 | 3 419   |
| Classification            | 49 351  | 56 965  | 15 770  |
| LPI                       | 52 183  | 98 902  | 4 092   |
| Organisation              | 4 226   | 5 029   | 4 438   |
| Delivery Point Address    | 38 450  | 14 998  | 10 001  |
| Application Cross Ref.    | 174 454 | 350 798 | 28 721  |

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 125:

| Data Source                          | Date            |
| ------------------------------------ | --------------- |
| Royal Mail PAF                       | 15 January 2026 |
| National Land and Property Gazetteer | 15 January 2026 |
| One Scotland Gazetteer               | 04 January 2026 |
| VOA Non-Domestic Rates               | 12 January 2026 |
| VOA Council Tax                      | 12 January 2026 |
| OS MasterMap Topography Layer        | 06 January 2026 |
| OS MasterMap Highways Network        | 09 January 2026 |
| Code-Point with Polygons             | 02 January 2026 |
| Boundary-Line                        | 02 October 2025 |

## Data issues

### AddressBase

Details of live and resolved data issues for AddressBase will be communicated on the [AddressBase Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Plus issues

Details of live and resolved data issues for AddressBase Plus will be communicated on the [AddressBase Plus Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus/addressbase-plus-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Premium

Details of live and resolved data issues for AddressBase Premium will be communicated on the [AddressBase Premium Known Data Issues, Service Disruptions and Planned Maintenance page](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium/addressbase-premium-known-data-issues-service-disruptions-and-planned-maintenance). This page will provide details of their impacts and updates on the expected time frame for their resolution.

## Improvements in Epoch 125

### Valuation Office Agency matching

The match rates for Council Tax and Non-Domestic Rates for Epoch 125 are detailed as follows based on Valuation Office Agency (VOA) records up to 12 January 2026. The match rate is applicable to the AddressBase Premium product.

| Data Source        | Records Received | % Matched |
| ------------------ | ---------------- | --------- |
| Council Tax        | 27 386 555       | 99.92     |
| Non-Domestic Rates | 2 124 360        | 96.50     |

## Next release

The next release of AddressBase products, Epoch 126, is scheduled for **02 April 2026**.


# AddressBase Islands Products February 2026 – Epoch 125

This release note provides information about the February 2026 Epoch 125 release of the AddressBase Islands products. These products were released to customers on 19 February 2026.

## Record counts

| Product                     | Full Supply Record Count | Change-Only Update Record Count |
| --------------------------- | ------------------------ | ------------------------------- |
| AddressBase Plus Islands    | 1 172 858                | 14 718                          |
| AddressBase Premium Islands | See rows below           | See rows below                  |
| Street                      | 49 196                   | 170                             |
| Street Descriptor           | 49 196                   | 39                              |
| BLPU                        | 1 250 630                | 15 429                          |
| Classification              | 1 250 630                | 7 222                           |
| LPI                         | 1 261 028                | 13 863                          |
| Organisation                | 38 435                   | 102                             |
| Delivery Point Address      | 986 557                  | 1 442                           |
| Application Cross Ref.      | 1 315 832                | 2 229                           |
| Successor                   | 0                        | 0                               |

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase Islands product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the count of these records.

### AddressBase Plus Islands

| Change Type | Count  |
| ----------- | ------ |
| Inserts     | 3 126  |
| Updates     | 11 373 |
| Deletes     | 219    |

### AddressBase Premium Islands

| AddressBase Premium Table | Inserts | Updates | Deletes |
| ------------------------- | ------- | ------- | ------- |
| Street                    | 39      | 131     | 0       |
| Street Descriptor         | 39      | 0       | 0       |
| BLPU                      | 1 464   | 13 854  | 111     |
| Classification            | 1 464   | 5 647   | 111     |
| LPI                       | 1 484   | 12 268  | 111     |
| Organisation              | 13      | 24      | 65      |
| Delivery Point Address    | 1 016   | 301     | 125     |
| Application Cross Ref.    | 1 443   | 613     | 173     |
| Successor                 | 0       | 0       | 0       |

It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in '[Working with COU data](https://docs.os.uk/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-getting-started-guide/working-with-cou-data)' in the AddressBase Getting Started Guide

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 125:

| Data Source                                                     | Date            |
| --------------------------------------------------------------- | --------------- |
| <p>Pointer (Northern Ireland)</p><h3 id="data-issues"><br></h3> | 15 January 2026 |
| DigiMap (Channel Islands)                                       | 15 January 2026 |
| Isle of Man                                                     | 15 January 2026 |
| Royal Mail PAF                                                  | 15 January 2026 |

## Data issues

### AddressBase Plus Islands issues

Details of live and resolved data issues for AddressBase Plus Islands will be communicated on the [AddressBase Plus Islands Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus-islands/addressbase-plus-islands-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Premium Islands issues

Details of live and resolved data issues for AddressBase Premium Islands will be communicated on the [AddressBase Premium Islands Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium-islands/addressbase-premium-islands-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

## Next release

The next release of AddressBase Islands products, Epoch 126, is scheduled for **02 April 2026**.


# AddressBase Products January 2026 – Epoch 124

This release note provides information about the January 2026 Epoch 124 release of the AddressBase products. These products were released to customers on 08 January 2026.

## Record counts

| Product                | Full Supply Record Count | Change-Only Update Record Count |
| ---------------------- | ------------------------ | ------------------------------- |
| OS Open UPRN           | 41 431 031               | N/A                             |
| AddressBase            | 30 845 902               | 129 661                         |
| AddressBase Plus       | 38 624 958               | 637 192                         |
| AddressBase Premium    | See rows below           | See rows below                  |
| Street                 | 1 523 057                | 6 933                           |
| Street Descriptor      | 1 647 240                | 4 473                           |
| BLPU                   | 41 431 031               | 401 527                         |
| Classification         | 45 224 829               | 166 474                         |
| LPI                    | 46 754 671               | 161 905                         |
| Organisation           | 1 386 792                | 12 772                          |
| Delivery Point Address | 30 960 300               | 62 734                          |
| Application Cross Ref. | 200 459 799              | 714 652                         |
| Successor              | 0                        | 0                               |

**Please note:**

* The Full Supply record counts are based on a Managed Great Britain Set (MGBS). If you have ordered your national coverage via the online ordering system using a polygon outline, then your counts may differ.
* Change-Only Updates (COUs) are not available for the OS Open UPRN product.

## Product supply comparison

There is a difference in product counts between taking a national Managed Great Britain Set (MGBS) and a national Area of Interest (AOI). This is because the two supplies use different selection criteria. The differences are shown in the following table, allowing for you to validate your data holdings once you have loaded the latest release of AddressBase data.

The national AOI refers to the pre-selection GB polygon from our download store. Therefore, if you have drawn your own AOI, the count will vary.

If you are unsure of your supply type, please check this with your OS Relationship Manager.

| Product                | MGBS Full Count | National AOI Full Count | Difference     |
| ---------------------- | --------------- | ----------------------- | -------------- |
| AddressBase            | 30 845 902      | 30 845 901              | 1              |
| AddressBase Plus       | 38 624 958      | 38 624 931              | 27             |
| AddressBase Premium    | See rows below  | See rows below          | See rows below |
| Street                 | 1 523 057       | 1 523 054               | 3              |
| Street Descriptor      | 1 647 240       | 1 647 237               | 3              |
| BLPU                   | 41 431 031      | 41 431 001              | 30             |
| Classification         | 45 224 829      | 45 224 797              | 32             |
| LPI                    | 46 754 671      | 46 754 640              | 31             |
| Organisation           | 1 386 792       | 1 386 790               | 2              |
| Delivery Point Address | 30 960 300      | 30 960 299              | 1              |
| Application Cross Ref. | 200 459 799     | 200 459 768             | 31             |
| Successor              | 0               | 0                       | 0              |

It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the '[Working with COU data' page in the AddressBase Core Getting Started Guide](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-getting-started-guide/working-with-cou-data).

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the numbers of these records which can be expected in an **MGBS supply**, and also how many tiles are affected if you take your supply as Changed Chunks.

### AddressBase

| Change Type              | Count  |
| ------------------------ | ------ |
| Inserts                  | 34 765 |
| Updates                  | 84 466 |
| Deletes                  | 10 430 |
| COU Populated Tile Count | 5 401  |

### AddressBase Plus

| Change Type              | Count   |
| ------------------------ | ------- |
| Inserts                  | 57 650  |
| Updates                  | 566 160 |
| Deletes                  | 13 382  |
| COU Populated Tile Count | 7 279   |

### AddressBase Premium

| AddressBase Premium Table | Inserts | Updates | Deletes |
| ------------------------- | ------- | ------- | ------- |
| Street                    | 1 962   | 4 932   | 39      |
| Street Descriptor         | 1 999   | 2 434   | 40      |
| BLPU                      | 48 087  | 349 834 | 3 606   |
| Classification            | 58 348  | 88 700  | 19 426  |
| LPI                       | 61 868  | 95 510  | 4 527   |
| Organisation              | 4 048   | 4 478   | 4 246   |
| Delivery Point Address    | 35 162  | 17 314  | 10 258  |
| Application Cross Ref.    | 213 522 | 466 630 | 34 500  |

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 124:

| Data Source                          | Date             |
| ------------------------------------ | ---------------- |
| Royal Mail PAF                       | 04 December 2025 |
| National Land and Property Gazetteer | 04 December 2025 |
| One Scotland Gazetteer               | 17 November 2025 |
| VOA Non-Domestic Rates               | 01 December 2025 |
| VOA Council Tax                      | 01 December 2025 |
| OS MasterMap Topography Layer        | 02 December 2025 |
| OS MasterMap Highways Network        | 04 December 2025 |
| Code-Point with Polygons             | 01 October 2025  |
| Boundary-Line                        | 02 October 2025  |

## Data issues

### AddressBase

Details of live and resolved data issues for AddressBase will be communicated on the [AddressBase Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Plus issues

Details of live and resolved data issues for AddressBase Plus will be communicated on the [AddressBase Plus Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus/addressbase-plus-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Premium

Details of live and resolved data issues for AddressBase Premium will be communicated on the [AddressBase Premium Known Data Issues, Service Disruptions and Planned Maintenance page](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium/addressbase-premium-known-data-issues-service-disruptions-and-planned-maintenance). This page will provide details of their impacts and updates on the expected time frame for their resolution.

## Improvements in Epoch 124

### Valuation Office Agency matching

The match rates for Council Tax and Non-Domestic Rates for Epoch 124 are detailed as follows based on Valuation Office Agency (VOA) records up to 04 December 2025. The match rate is applicable to the AddressBase Premium product.

| Data Source        | Records Received | % Matched |
| ------------------ | ---------------- | --------- |
| Council Tax        | 27 363 655       | 99.2      |
| Non-Domestic Rates | 2 122 323        | 96.47     |

## Next release

The next release of AddressBase products, Epoch 125, is scheduled for **19 February 2026**


# AddressBase Islands January 2026 – Epoch 124

This release note provides information about the January 2026 Epoch 124 release of the AddressBase Islands products. These products were released to customers on 08 January 2026.

## Record counts

| Product                     | Full Supply Record Count | Change-Only Update Record Count |
| --------------------------- | ------------------------ | ------------------------------- |
| AddressBase Plus Islands    | 1 169 951                | 6 709                           |
| AddressBase Premium Islands | See rows below           | See rows below                  |
| Street                      | 49 157                   | 211                             |
| Street Descriptor           | 49 157                   | 58                              |
| BLPU                        | 1 249 277                | 7 524                           |
| Classification              | 1 249 277                | 3 351                           |
| LPI                         | 1 259 655                | 4 334                           |
| Organisation                | 38 487                   | 1 332                           |
| Delivery Point Address      | 985 666                  | 1 394                           |
| Application Cross Ref.      | 1 314 562                | 3 474                           |
| Successor                   | 0                        | 0                               |

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase Islands product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the count of these records.

### AddressBase Plus Islands

| Change Type | Count |
| ----------- | ----- |
| Inserts     | 1 329 |
| Updates     | 5 048 |
| Deletes     | 332   |

### AddressBase Premium Islands

| AddressBase Premium Islands Table | Inserts | Updates | Deletes |
| --------------------------------- | ------- | ------- | ------- |
| Street                            | 58      | 153     | 0       |
| Street Descriptor                 | 58      | 0       | 0       |
| BLPU                              | 1 598   | 5 755   | 171     |
| Classification                    | 1 598   | 1 582   | 171     |
| LPI                               | 1 702   | 2 461   | 171     |
| Organisation                      | 157     | 679     | 496     |
| Delivery Point Address            | 949     | 263     | 182     |
| Application Cross Ref.            | 1 703   | 1 440   | 331     |
| Successor                         | 0       | 0       | 0       |

It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the '[Working with COU data' page in the AddressBase Core Getting Started Guide](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-getting-started-guide/working-with-cou-data).

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 124:

| Data Source                | Date             |
| -------------------------- | ---------------- |
| Pointer (Northern Ireland) | 04 December 2025 |
| DigiMap (Channel Islands)  | 04 December 2025 |
| Isle of Man                | 04 December 2025 |
| Royal Mail PAF             | 04 December 2025 |

## Data issues

### AddressBase Plus Islands issues

Details of live and resolved data issues for AddressBase Plus Islands will be communicated on the [AddressBase Plus Islands Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus-islands/addressbase-plus-islands-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Premium Islands issues

Details of live and resolved data issues for AddressBase Premium Islands will be communicated on the [AddressBase Premium Islands Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium-islands/addressbase-premium-islands-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

## Next release

The next release of AddressBase Islands products, Epoch 125, is scheduled for **19 February 2026**


# AddressBase Products November 2025 – Epoch 123

This release note provides information about the November 2025 (Epoch 123) release of the AddressBase products. These products were released to customers on 27 November 2025.

## Record counts

| Product                | Full Supply Record Count | Change-Only Update Record Count |
| ---------------------- | ------------------------ | ------------------------------- |
| OS Open UPRN           | 41 386 550               | N/A                             |
| AddressBase            | 30 821 567               | 131 373                         |
| AddressBase Plus       | 38 580 690               | 632 773                         |
| AddressBase Premium    | See rows below           | See rows below                  |
| Street                 | 1 521 134                | 21 137                          |
| Street Descriptor      | 1 645 281                | 2 669                           |
| BLPU                   | 41 386 550               | 494 886                         |
| Classification         | 45 185 907               | 183 823                         |
| LPI                    | 46 697 330               | 207 444                         |
| Organisation           | 1 386 990                | 14 848                          |
| Delivery Point Address | 30 935 396               | 59 171                          |
| Application Cross Ref. | 200 280 777              | 679 795                         |
| Successor              | 0                        | 0                               |

**Please note:**

* The Full Supply record counts are based on a Managed Great Britain Set (MGBS). If you have ordered your national coverage via the online ordering system using a polygon outline, then your counts may differ.
* Change-Only Updates (COUs) are not available for the OS Open UPRN product.

## Product supply comparison

There is a difference in product counts between taking a national Managed Great Britain Set (MGBS) and a national Area of Interest (AOI). This is because the two supplies use different selection criteria. The differences are shown in the following table, allowing for you to validate your data holdings once you have loaded the latest release of AddressBase data.

The national AOI refers to the pre-selection GB polygon from our download store. Therefore, if you have drawn your own AOI, the count will vary.

If you are unsure of your supply type, please check this with your OS Relationship Manager.

| Product                | MGBS Full Count | National AOI Full Count | Difference     |
| ---------------------- | --------------- | ----------------------- | -------------- |
| AddressBase            | 30 821 567      | 30 821 566              | 1              |
| AddressBase Plus       | 38 580 690      | 38 580 664              | 26             |
| AddressBase Premium    | See rows below  | See rows below          | See rows below |
| Street                 | 1 521 134       | 1 521 131               | 3              |
| Street Descriptor      | 1 645 281       | 1 645 278               | 3              |
| BLPU                   | 41 386 550      | 41 386 519              | 31             |
| Classification         | 45 185 907      | 45 185 874              | 33             |
| LPI                    | 46 697 330      | 46 697 298              | 32             |
| Organisation           | 1 386 990       | 1 386 988               | 2              |
| Delivery Point Address | 30 935 396      | 30 935 395              | 1              |
| Application Cross Ref. | 200 280 777     | 200 280 745             | 32             |
| Successor              | 0               | 0                       | 0              |

It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the '[Working with COU data' page in the AddressBase Core Getting Started Guide](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-getting-started-guide/working-with-cou-data).

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the numbers of these records which can be expected in an **MGBS supply**, and also how many tiles are affected if you take your supply as Changed Chunks.

### AddressBase

| Change Type              | Count  |
| ------------------------ | ------ |
| Inserts                  | 31 370 |
| Updates                  | 88 794 |
| Deletes                  | 11 209 |
| COU Populated Tile Count | 5 260  |

### AddressBase Plus

| Change Type              | Count   |
| ------------------------ | ------- |
| Inserts                  | 57 974  |
| Updates                  | 559 035 |
| Deletes                  | 15 764  |
| COU Populated Tile Count | 7 287   |

### AddressBase Premium

| AddressBase Premium Table | Inserts | Updates | Deletes |
| ------------------------- | ------- | ------- | ------- |
| Street                    | 1 398   | 19 689  | 50      |
| Street Descriptor         | 1 430   | 1 189   | 50      |
| BLPU                      | 42 394  | 448 615 | 3 877   |
| Classification            | 54 370  | 107 917 | 21 536  |
| LPI                       | 54 146  | 148 726 | 4 572   |
| Organisation              | 4 303   | 5 843   | 4 702   |
| Delivery Point Address    | 32 165  | 15 818  | 11 188  |
| Application Cross Ref.    | 215 860 | 401 543 | 62 392  |

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 123:

| Data Source                          | Date            |
| ------------------------------------ | --------------- |
| Royal Mail PAF                       | 23 October 2025 |
| National Land and Property Gazetteer | 23 October 2025 |
| One Scotland Gazetteer               | 06 October 2025 |
| VOA Non-Domestic Rates               | 23 October 2025 |
| VOA Council Tax                      | 23 October 2025 |
| OS MasterMap Topography Layer        | 14 October 2025 |
| OS MasterMap Highways Network        | 06 October 2025 |
| Code-Point with Polygons             | 01 October 2025 |
| Boundary-Line                        | 02 October 2025 |

## Data issues

### AddressBase

Details of live and resolved data issues for AddressBase will be communicated on the [AddressBase Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Plus issues

Details of live and resolved data issues for AddressBase Plus will be communicated on the [AddressBase Plus Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus/addressbase-plus-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Premium

Details of live and resolved data issues for AddressBase Premium will be communicated on the [AddressBase Premium Known Data Issues, Service Disruptions and Planned Maintenance page](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium/addressbase-premium-known-data-issues-service-disruptions-and-planned-maintenance). This page will provide details of their impacts and updates on the expected time frame for their resolution.

## Improvements in Epoch 123

### Valuation Office Agency matching

The match rates for Council Tax and Non-Domestic Rates for Epoch 123 are detailed as follows based on Valuation Office Agency (VOA) records up to 23 October 2025. The match rate is applicable to the AddressBase Premium product.

| Data Source        | Records Received | % Matched |
| ------------------ | ---------------- | --------- |
| Council Tax        | 27 338 190       | 99.90     |
| Non-Domestic Rates | 2 124 934        | 96.35     |

## Next release

The next release of AddressBase products, Epoch 124, is scheduled for **08 January 2026**


# AddressBase Islands November 2025 – Epoch 123

This release note provides information about the November 2025  (Epoch 123) release of the AddressBase Islands products. These products were released to customers on 27 November 2025.

## Record counts

| Product                     | Full Supply Record Count | Change-Only Update Record Count |
| --------------------------- | ------------------------ | ------------------------------- |
| AddressBase Plus Islands    | 1 168 954                | 8 215                           |
| AddressBase Premium Islands | See rows below           | See rows below                  |
| Street                      | 49 099                   | 226                             |
| Street Descriptor           | 49 099                   | 65                              |
| BLPU                        | 1 247 850                | 8 434                           |
| Classification              | 1 247 850                | 3 873                           |
| LPI                         | 1 258 124                | 5 077                           |
| Organisation                | 38 826                   | 1 228                           |
| Delivery Point Address      | 984 899                  | 2 074                           |
| Application Cross Ref.      | 1 313 190                | 2 962                           |
| Successor                   |                          |                                 |

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase Islands product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the count of these records.

### AddressBase Plus Islands

| Change Type | Count |
| ----------- | ----- |
| Inserts     | 2 430 |
| Updates     | 5 504 |
| Deletes     | 281   |

### AddressBase Premium Islands

| AddressBase Premium Islands Table | Inserts | Updates | Deletes |
| --------------------------------- | ------- | ------- | ------- |
| Street                            | 48      | 175     | 3       |
| Street Descriptor                 | 48      | 14      | 3       |
| BLPU                              | 1 722   | 6 570   | 142     |
| Classification                    | 1 722   | 2 009   | 142     |
| LPI                               | 2 131   | 2 804   | 142     |
| Organisation                      | 240     | 696     | 292     |
| Delivery Point Address            | 1 636   | 277     | 161     |
| Application Cross Ref.            | 2 091   | 664     | 207     |
| Successor                         | 0       | 0       | 0       |

It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the '[Working with COU data' page in the AddressBase Core Getting Started Guide](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-getting-started-guide/working-with-cou-data).

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 123:

| Data Source                | Date            |
| -------------------------- | --------------- |
| Pointer (Northern Ireland) | 22 October 2025 |
| DigiMap (Channel Islands)  | 23 October 2025 |
| Isle of Man                | 23 October 2025 |
| Royal Mail PAF             | 23 October 2025 |

## Data issues

### AddressBase Plus Islands issues

Details of live and resolved data issues for AddressBase Plus Islands will be communicated on the [AddressBase Plus Islands Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus-islands/addressbase-plus-islands-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Premium Islands issues

Details of live and resolved data issues for AddressBase Premium Islands will be communicated on the [AddressBase Premium Islands Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium-islands/addressbase-premium-islands-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

## Next release

The next release of AddressBase Islands products, Epoch 124, is scheduled for **08 January 2026**


# AddressBase Products October 2025 – Epoch 122

This release note provides information about the October 2025 (Epoch 122) release of the AddressBase products. These products were released to customers on 16 October 2025.

## Record counts

| Product                | Full Supply Record Count | Change-Only Update Record Count |
| ---------------------- | ------------------------ | ------------------------------- |
| OS Open UPRN           | 41 348 033               | N/A                             |
| AddressBase            | 30 801 406               | 129 609                         |
| AddressBase Plus       | 38 538 480               | 583 698                         |
| AddressBase Premium    | See rows below           | See rows below                  |
| Street                 | 1 519 786                | 3 535                           |
| Street Descriptor      | 1 643 901                | 1 715                           |
| BLPU                   | 41 348 033               | 446 875                         |
| Classification         | 45 153 073               | 112 212                         |
| LPI                    | 46 647 756               | 109 748                         |
| Organisation           | 1 387 389                | 18 623                          |
| Delivery Point Address | 30 914 419               | 43 569                          |
| Application Cross Ref. | 200 127 309              | 468 449                         |
| Successor              | 0                        | 0                               |

**Please note:**

* The Full Supply record counts are based on a Managed Great Britain Set (MGBS). If you have ordered your national coverage via the online ordering system using a polygon outline, then your counts may differ.
* Change-Only Updates (COUs) are not available for the OS Open UPRN product.

## Product supply comparison

There is a difference in product counts between taking a national Managed Great Britain Set (MGBS) and a national Area of Interest (AOI). This is because the two supplies use different selection criteria. The differences are shown in the following table, allowing for you to validate your data holdings once you have loaded the latest release of AddressBase data.

The national AOI refers to the pre-selection GB polygon from our download store. Therefore, if you have drawn your own AOI, the count will vary.

If you are unsure of your supply type, please check this with your OS Relationship Manager.

| Product                | MGBS Full Count | National AOI Full Count | Difference     |
| ---------------------- | --------------- | ----------------------- | -------------- |
| AddressBase            | 30 801 406      | 30 801 406              | 0              |
| AddressBase Plus       | 38 538 480      | 38 538 455              | 25             |
| AddressBase Premium    | See rows below  | See rows below          | See rows below |
| Street                 | 1 519 786       | 1 519 783               | 3              |
| Street Descriptor      | 1 643 901       | 1 643 898               | 3              |
| BLPU                   | 41 348 033      | 41 348 003              | 30             |
| Classification         | 45 153 073      | 45 153 041              | 32             |
| LPI                    | 46 647 756      | 46 647 725              | 31             |
| Organisation           | 1 387 389       | 1 387 387               | 2              |
| Delivery Point Address | 30 914 419      | 30 914 419              | 0              |
| Application Cross Ref. | 200 127 309     | 200 127 278             | 31             |
| Successor              | 0               | 0                       | 0              |

It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the '[Working with COU data' page in the AddressBase Core Getting Started Guide](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-getting-started-guide/working-with-cou-data).

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the numbers of these records which can be expected in an **MGBS supply**, and also how many tiles are affected if you take your supply as Changed Chunks.

### AddressBase

| Change Type              | Count  |
| ------------------------ | ------ |
| Inserts                  | 27 357 |
| Updates                  | 95 524 |
| Deletes                  | 6 728  |
| COU Populated Tile Count | 9 395  |

### AddressBase Plus

| Change Type              | Count   |
| ------------------------ | ------- |
| Inserts                  | 42 865  |
| Updates                  | 531 846 |
| Deletes                  | 8 987   |
| COU Populated Tile Count | 10 343  |

### AddressBase Premium

| AddressBase Premium Table | Inserts | Updates | Deletes |
| ------------------------- | ------- | ------- | ------- |
| Street                    | 911     | 2 548   | 76      |
| Street Descriptor         | 955     | 682     | 78      |
| BLPU                      | 31 114  | 413 889 | 1 872   |
| Classification            | 39 431  | 58 873  | 13 908  |
| LPI                       | 40 960  | 66 500  | 2 288   |
| Organisation              | 3 114   | 2 847   | 12 662  |
| Delivery Point Address    | 27 650  | 9 512   | 6 407   |
| Application Cross Ref.    | 187 411 | 260 020 | 21 018  |

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 122:

| Data Source                          | Date              |
| ------------------------------------ | ----------------- |
| Royal Mail PAF                       | 11 September 2025 |
| National Land and Property Gazetteer | 11 September 2025 |
| One Scotland Gazetteer               | 01 September 2025 |
| VOA Non-Domestic Rates               | 11 September 2025 |
| VOA Council Tax                      | 11 September 2025 |
| OS MasterMap Topography Layer        | 14 August 2025    |
| OS MasterMap Highways Network        | 04 September 2025 |
| Code-Point with Polygons             | 01 July 2025      |
| Boundary-Line                        | 01 May 2025       |

## Data issues

### AddressBase

Details of live and resolved data issues for AddressBase will be communicated on the [AddressBase Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Plus issues

Details of live and resolved data issues for AddressBase Plus will be communicated on the [AddressBase Plus Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus/addressbase-plus-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Premium

Details of live and resolved data issues for AddressBase Premium will be communicated on the [AddressBase Premium Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium/addressbase-premium-known-data-issues-service-disruptions-and-planned-maintenance). This page will provide details of their impacts and updates on the expected time frame for their resolution.

## Improvements in Epoch 122

### Valuation Office Agency matching

The match rates for Council Tax and Non-Domestic Rates for Epoch 122 are detailed as follows based on Valuation Office Agency (VOA) records up to 08 September 2025. The match rate is applicable to the AddressBase Premium product.

| Data Source        | Records Received | % Matched |
| ------------------ | ---------------- | --------- |
| Council Tax        | 27 312 781       | 99.92     |
| Non-Domestic Rates | 2 121 813        | 96.5      |

## Next release

The next release of AddressBase products, Epoch 123, is scheduled for **27 November 2025**.


# AddressBase Islands October 2025 – Epoch 122

This release note provides information about the October 2025  (Epoch 122) release of the AddressBase Islands products. These products were released to customers on 16 October 2025.

## Record counts

| Product                     | Full Supply Record Count | Change-Only Update Record Count |
| --------------------------- | ------------------------ | ------------------------------- |
| AddressBase Plus Islands    | 1 166 805                | 5 566                           |
| AddressBase Premium Islands | See rows below           | See rows below                  |
| Street                      | 49 054                   | 120                             |
| Street Descriptor           | 49 054                   | 31                              |
| BLPU                        | 1 246 270                | 5 481                           |
| Classification              | 1 246 270                | 2 719                           |
| LPI                         | 1 256 135                | 3 659                           |
| Organisation                | 38 878                   | 71                              |
| Delivery Point Address      | 983 424                  | 2 446                           |
| Application Cross Ref.      | 1 311 306                | 2 592                           |
| Successor                   | 0                        | 0                               |

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase Islands product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the count of these records.

### AddressBase Plus Islands

| Change Type | Count |
| ----------- | ----- |
| Inserts     | 1 114 |
| Updates     | 4 218 |
| Deletes     | 234   |

### AddressBase Premium Islands

| AddressBase Premium Islands Table | Inserts | Updates | Deletes |
| --------------------------------- | ------- | ------- | ------- |
| Street                            | 30      | 90      | 0       |
| Street Descriptor                 | 30      | 1       | 0       |
| BLPU                              | 1 673   | 3 626   | 182     |
| Classification                    | 1 673   | 864     | 182     |
| LPI                               | 1 680   | 1 797   | 182     |
| Organisation                      | 11      | 13      | 47      |
| Delivery Point Address            | 917     | 1 326   | 203     |
| Application Cross Ref.            | 1 647   | 634     | 311     |
| Successor                         | 0       | 0       | 0       |

It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the '[Working with COU data' page in the AddressBase Core Getting Started Guide](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-getting-started-guide/working-with-cou-data).

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 122:

| Data Source                | Date              |
| -------------------------- | ----------------- |
| Pointer (Northern Ireland) | 10 September 2025 |
| DigiMap (Channel Islands)  | 11 September 2025 |
| Isle of Man                | 11 September 2025 |
| Royal Mail PAF             | 11 September 2025 |

## Data issues

### AddressBase Plus Islands issues

Details of live and resolved data issues for AddressBase Plus Islands will be communicated on the [AddressBase Plus Islands Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus-islands/addressbase-plus-islands-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Premium Islands issues

Details of live and resolved data issues for AddressBase Premium Islands will be communicated on the [AddressBase Premium Islands Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium-islands/addressbase-premium-islands-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

## Next release

The next release of AddressBase Islands products, Epoch 123, is scheduled for **27 November 2025**.


# AddressBase Products September 2025 – Epoch 121

This release note provides information about the September 2025 (Epoch 121) release of the AddressBase products. These products were released to customers on 04 September 2025.

## Record counts

| Product                | Full Supply Record Count | Change-Only Update Record Count |
| ---------------------- | ------------------------ | ------------------------------- |
| OS Open UPRN           | 41 270 485               | N/A                             |
| AddressBase            | 30 780 777               | 190 178                         |
| AddressBase Plus       | 38 504 602               | 747 079                         |
| AddressBase Premium    | See rows below           | See rows below                  |
| Street                 | 1 518 951                | 6 979                           |
| Street Descriptor      | 1 643 024                | 3 566                           |
| BLPU                   | 41 318 791               | 497 400                         |
| Classification         | 45 127 550               | 186 102                         |
| LPI                    | 46 609 084               | 196 818                         |
| Organisation           | 1 396 937                | 21 750                          |
| Delivery Point Address | 30 893 176               | 81 996                          |
| Application Cross Ref. | 199 960 916              | 1 028 132                       |
| Successor              | 0                        | 0                               |

{% hint style="info" %}

* The Full Supply record counts are based on a Managed Great Britain Set (MGBS). If you have ordered your national coverage via the online ordering system using a polygon outline, then your counts may differ.
* Please note that Change-Only Updates (COUs) are not available for the OS Open UPRN product.
  {% endhint %}

## Product supply comparison

There is a difference in product counts between taking a national Managed Great Britain Set (MGBS) and a national Area of Interest (AOI). This is because the two supplies use different selection criteria. The differences are shown in the following table, allowing for you to validate your data holdings once you have loaded the latest release of AddressBase data.

The national AOI refers to the pre-selection GB polygon from our download store. Therefore, if you have drawn your own AOI, the count will vary.

If you are unsure of your supply type, please check this with your OS Relationship Manager.

| Product                | MGBS Full Count | National AOI Full Count | Difference     |
| ---------------------- | --------------- | ----------------------- | -------------- |
| AddressBase            | 30 780 777      | 30 780 777              | 0              |
| AddressBase Plus       | 38 504 602      | 38 504 577              | 25             |
| AddressBase Premium    | See rows below  | See rows below          | See rows below |
| Street                 | 1 518 951       | 1 518 948               | 3              |
| Street Descriptor      | 1 643 024       | 1 643 021               | 3              |
| BLPU                   | 41 318 791      | 41 318 761              | 30             |
| Classification         | 45 127 550      | 45 127 518              | 22             |
| LPI                    | 46 609 084      | 46 609 053              | 31             |
| Organisation           | 1 396 937       | 1 396 935               | 2              |
| Delivery Point Address | 30 893 176      | 30 893 176              | 0              |
| Application Cross Ref. | 199 960 916     | 199 960 885             | 31             |
| Successor              | 0               | 0                       | 0              |

It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the '[Working with COU data' page in the AddressBase Core Getting Started Guide](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-getting-started-guide/working-with-cou-data).

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the numbers of these records which can be expected in an **MGBS supply**, and also how many tiles are affected if you take your supply as Changed Chunks.

### AddressBase

| Change Type              | Count   |
| ------------------------ | ------- |
| Inserts                  | 49 044  |
| Updates                  | 131 238 |
| Deletes                  | 9 896   |
| COU Populated Tile Count | 5 351   |

### AddressBase Plus

| Change Type              | Count   |
| ------------------------ | ------- |
| Inserts                  | 67 012  |
| Updates                  | 665 372 |
| Deletes                  | 14 695  |
| COU Populated Tile Count | 7 259   |

### AddressBase Premium

| AddressBase Premium Table | Inserts | Updates | Deletes |
| ------------------------- | ------- | ------- | ------- |
| Street                    | 1 241   | 5 726   | 12      |
| Street Descriptor         | 1 321   | 2 233   | 12      |
| BLPU                      | 50 956  | 443 794 | 2 650   |
| Classification            | 65 969  | 95 869  | 24 264  |
| LPI                       | 68 758  | 123 806 | 4 254   |
| Organisation              | 6 401   | 8 820   | 6 529   |
| Delivery Point Address    | 49 531  | 22 842  | 9 623   |
| Application Cross Ref.    | 227 695 | 720 867 | 79 570  |

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 121:

| Data Source                          | Date           |
| ------------------------------------ | -------------- |
| Royal Mail PAF                       | 07 August 2025 |
| National Land and Property Gazetteer | 07 August 2025 |
| One Scotland Gazetteer               | 14 July 2025   |
| VOA Non-Domestic Rates               | 05 July 2025   |
| VOA Council Tax                      | 05 July 2025   |
| OS MasterMap Topography Layer        | 10 July 2025   |
| OS MasterMap Highways Network        | 07 August 2025 |
| Code-Point with Polygons             | 01 July 2025   |
| Boundary-Line                        | 01 May 2025    |

## Data issues

### AddressBase

Details of live and resolved data issues for AddressBase will be communicated on the [AddressBase Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Plus issues

Details of live and resolved data issues for AddressBase Plus will be communicated on the [AddressBase Plus Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus/addressbase-plus-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Premium

Details of live and resolved data issues for AddressBase Premium will be communicated on the [AddressBase Premium Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium/addressbase-premium-known-data-issues-service-disruptions-and-planned-maintenance). This page will provide details of their impacts and updates on the expected time frame for their resolution.

## Improvements in Epoch 121

### Valuation Office Agency matching

The match rates for Council Tax and Non-Domestic Rates for Epoch 121 are detailed as follows based on Valuation Office Agency (VOA) records up to 28 July 2025. The match rate is applicable to the AddressBase Premium product.

| Data Source        | Records Received | % Matched |
| ------------------ | ---------------- | --------- |
| Council Tax        | 27 246 694       | 99.91     |
| Non-Domestic Rates | 2 122 283        | 96.43     |

## Next release

The next release of AddressBase products, Epoch 122, is scheduled for **16 October 2025**.


# AddressBase Islands September 2025 – Epoch 121

This release note provides information about the September 2025  (Epoch 121) release of the AddressBase Islands products. These products were released to customers on 04 September 2025.

## Record counts

| Product                     | Full Supply Record Count | Change-Only Update Record Count |
| --------------------------- | ------------------------ | ------------------------------- |
| AddressBase Plus Islands    | 1 165 925                | 7 173                           |
| AddressBase Premium Islands | See rows below           | See rows below                  |
| Street                      | 49 024                   | 277                             |
| Street Descriptor           | 49 024                   | 325                             |
| BLPU                        | 1 244 779                | 7 295                           |
| Classification              | 1 244 779                | 2 629                           |
| LPI                         | 1 254 637                | 3 937                           |
| Organisation                | 38 914                   | 137                             |
| Delivery Point Address      | 982 710                  | 3 659                           |
| Application Cross Ref.      | 1 309 970                | 2 914                           |
| Successor                   | 0                        | 0                               |

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase Islands product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the count of these records.

### AddressBase Plus Islands

| Change Type | Count |
| ----------- | ----- |
| Inserts     | 1 572 |
| Updates     | 5 311 |
| Deletes     | 290   |

### AddressBase Premium Islands

| AddressBase Premium Islands Table | Inserts | Updates | Deletes |
| --------------------------------- | ------- | ------- | ------- |
| Street                            | 147     | 129     | 1       |
| Street Descriptor                 | 147     | 177     | 1       |
| BLPU                              | 1 367   | 5 606   | 322     |
| Classification                    | 1 367   | 940     | 322     |
| LPI                               | 1 385   | 2 230   | 322     |
| Organisation                      | 33      | 30      | 74      |
| Delivery Point Address            | 2 768   | 691     | 200     |
| Application Cross Ref.            | 1 338   | 1 114   | 462     |
| Successor                         | 0       | 0       | 0       |

It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the '[Working with COU data' page in the AddressBase Core Getting Started Guide](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-getting-started-guide/working-with-cou-data).

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 121:

| Data Source                | Date           |
| -------------------------- | -------------- |
| Pointer (Northern Ireland) | 06 August 2025 |
| DigiMap (Channel Islands)  | 06 August 2025 |
| Isle of Man                | 07 August 2025 |
| Royal Mail PAF             | 07 August 2025 |

## Data issues

### AddressBase Plus Islands issues

Details of live and resolved data issues for AddressBase Plus Islands will be communicated on the [AddressBase Plus Islands Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus-islands/addressbase-plus-islands-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Premium Islands issues

Details of live and resolved data issues for AddressBase Premium Islands will be communicated on the [AddressBase Premium Islands Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium-islands/addressbase-premium-islands-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

## Next release

The next release of AddressBase Islands products, Epoch 121, is scheduled for **16 October 2025**


# AddressBase Products July 2025 – Epoch 120

This release note provides information about the July 2025 (Epoch 120) release of the AddressBase products. These products were released to customers on 31 July 2025.

## Record counts

| Product                | Full Supply Record Count | Change-Only Update Record Count |
| ---------------------- | ------------------------ | ------------------------------- |
| OS Open UPRN           | 41 270 485               | N/A                             |
| AddressBase            | 30 741 629               | 121 243                         |
| AddressBase Plus       | 38 452 285               | 477 547                         |
| AddressBase Premium    | See rows below           | See rows below                  |
| Street                 | 1 517 722                | 6 124                           |
| Street Descriptor      | 1 641 715                | 2 909                           |
| BLPU                   | 41 270 485               | 409 362                         |
| Classification         | 45 085 845               | 181 304                         |
| LPI                    | 46 544 580               | 142 261                         |
| Organisation           | 1 397 065                | 18 469                          |
| Delivery Point Address | 30 853 268               | 53 795                          |
| Application Cross Ref. | 199 812 791              | 536 071                         |
| Successor              | 0                        | 0                               |

{% hint style="info" %}

* The Full Supply record counts are based on a Managed Great Britain Set (MGBS). If you have ordered your national coverage via the online ordering system using a polygon outline, then your counts may differ.
* Please note that Change-Only Updates (COUs) are not available for the OS Open UPRN product.
  {% endhint %}

## Product supply comparison

There is a difference in product counts between taking a national Managed Great Britain Set (MGBS) and a national Area of Interest (AOI). This is because the two supplies use different selection criteria. The differences are shown in the following table, allowing for you to validate your data holdings once you have loaded the latest release of AddressBase data.

The national AOI refers to the pre-selection GB polygon from our download store. Therefore, if you have drawn your own AOI, the count will vary.

If you are unsure of your supply type, please check this with your OS Relationship Manager.

| Product                | MGBS Full Count | National AOI Full Count | Difference     |
| ---------------------- | --------------- | ----------------------- | -------------- |
| AddressBase            | 30 741 629      | 30 741 629              | 0              |
| AddressBase Plus       | 38 452 285      | 38 452 261              | 24             |
| AddressBase Premium    | See rows below  | See rows below          | See rows below |
| Street                 | 1 517 722       | 1 517 719               | 3              |
| Street Descriptor      | 1 641 715       | 1 641 712               | 3              |
| BLPU                   | 41 270 485      | 41 270 456              | 29             |
| Classification         | 45 085 845      | 45 085 816              | 29             |
| LPI                    | 46 544 580      | 46 544 550              | 30             |
| Organisation           | 1 397 065       | 1 397 063               | 2              |
| Delivery Point Address | 30 853 268      | 30 853 268              | 0              |
| Application Cross Ref. | 199 812 791     | 199 812 762             | 29             |
| Successor              | 0               | 0                       | 0              |

It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the '[Working with COU data' page in the AddressBase Core Getting Started Guide](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-getting-started-guide/working-with-cou-data).

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the numbers of these records which can be expected in an **MGBS supply**, and also how many tiles are affected if you take your supply as Changed Chunks.

### AddressBase

| Change Type              | Count  |
| ------------------------ | ------ |
| Inserts                  | 29 279 |
| Updates                  | 83 730 |
| Deletes                  | 8 234  |
| COU Populated Tile Count | 5 103  |

### AddressBase Plus

| Change Type              | Count   |
| ------------------------ | ------- |
| Inserts                  | 45 736  |
| Updates                  | 420 603 |
| Deletes                  | 11 208  |
| COU Populated Tile Count | 7 064   |

### AddressBase Premium

| AddressBase Premium Table | Inserts | Updates | Deletes |
| ------------------------- | ------- | ------- | ------- |
| Street                    | 1 340   | 4 766   | 18      |
| Street Descriptor         | 1 410   | 1 481   | 18      |
| BLPU                      | 42 746  | 364 247 | 2 369   |
| Classification            | 62 130  | 94 342  | 24 832  |
| LPI                       | 53 762  | 85 450  | 3 049   |
| Organisation              | 7 624   | 4 893   | 5 952   |
| Delivery Point Address    | 29 693  | 15 672  | 8 430   |
| Application Cross Ref.    | 179 975 | 327 464 | 28 632  |

## Source data currency

The following information relates to the currency of the source data used in the creation of **Epoch 120**:

| Data Source                          | Date          |
| ------------------------------------ | ------------- |
| Royal Mail PAF                       | 19 June 2025  |
| National Land and Property Gazetteer | 19 June 2025  |
| One Scotland Gazetteer               | 02 June 2025  |
| VOA Non-Domestic Rates               | 16 June 2025  |
| VOA Council Tax                      | 16 June 2025  |
| OS MasterMap Topography Layer        | 22 May 2025   |
| OS MasterMap Highways Network        | 05 June 2025  |
| Code-Point with Polygons             | 01 April 2025 |
| Boundary-Line                        | 01 May 2025   |

## Data issues

### AddressBase

Details of live and resolved data issues for AddressBase will be communicated on the [AddressBase Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Plus issues

Details of live and resolved data issues for AddressBase Plus will be communicated on the [AddressBase Plus Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus/addressbase-plus-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Premium

Details of live and resolved data issues for AddressBase Premium will be communicated on the [AddressBase Premium Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium/addressbase-premium-known-data-issues-service-disruptions-and-planned-maintenance). This page will provide details of their impacts and updates on the expected time frame for their resolution.

## Improvements in Epoch 120

### Valuation Office Agency matching

The match rates for Council Tax and Non-Domestic Rates for Epoch 120 are detailed as follows based on Valuation Office Agency (VOA) records up to 16 June 2025. The match rate is applicable to the AddressBase Premium product.

| Data Source        | Records Received | % Matched |
| ------------------ | ---------------- | --------- |
| Council Tax        | 27 270 370       | 99.9      |
| Non-Domestic Rates | 2 123 017        | 96.4      |

### Tertiary classifications

Work is being undertaken to improve the classifications of records within the AddressBase products. This work has resulted in 45 295 more tertiary classifications present in Epoch 120 compared to Epoch 119. Indeed, 88.15\*\*%\*\* of these tertiary classification improvements are against residential codes.

## Next release

The next release of AddressBase products, Epoch 121, is scheduled for **04 September 2025**.


# AddressBase Islands July 2025 – Epoch 120

This release note provides information about the July 2025  (Epoch 120) release of the AddressBase Islands products. These products were released to customers on 31 July 2025.

## Record counts

| Product                     | Full Supply Record Count | Change-Only Update Record Count |
| --------------------------- | ------------------------ | ------------------------------- |
| AddressBase Plus Islands    | 1 164 643                | 6 384                           |
| AddressBase Premium Islands | See rows below           | See rows below                  |
| Street                      | 48 878                   | 130                             |
| Street Descriptor           | 48 878                   | 31                              |
| BLPU                        | 1 243 734                | 6 768                           |
| Classification              | 1 243 734                | 3 673                           |
| LPI                         | 1 253 574                | 2 536                           |
| Organisation                | 38 955                   | 1 470                           |
| Delivery Point Address      | 980 142                  | 1 047                           |
| Application Cross Ref.      | 1 309 094                | 2 134                           |
| Successor                   | 0                        | 0                               |

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase Islands product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the count of these records.

### AddressBase Plus Islands

| Change Type | Count |
| ----------- | ----- |
| Inserts     | 1 050 |
| Updates     | 5 102 |
| Deletes     | 232   |

### AddressBase Premium Islands

| AddressBase Premium Islands Table | Inserts | Updates | Deletes |
| --------------------------------- | ------- | ------- | ------- |
| Street                            | 31      | 99      | 0       |
| Street Descriptor                 | 31      | 0       | 0       |
| BLPU                              | 944     | 5 632   | 192     |
| Classification                    | 944     | 2 537   | 192     |
| LPI                               | 964     | 1 380   | 192     |
| Organisation                      | 413     | 781     | 276     |
| Delivery Point Address            | 705     | 195     | 147     |
| Application Cross Ref.            | 919     | 897     | 318     |
| Successor                         | 0       | 0       | 0       |

It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the '[Working with COU data' page in the AddressBase Core Getting Started Guide](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-getting-started-guide/working-with-cou-data).

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch EPOCH 120:

| Data Source                | Date         |
| -------------------------- | ------------ |
| Pointer (Northern Ireland) | 18 June 2025 |
| DigiMap (Channel Islands)  | 19 June 2025 |
| Isle of Man                | 19 June 2025 |
| Royal Mail PAF             | 19 June 2025 |

## Data issues

### AddressBase Plus Islands issues

Details of live and resolved data issues for AddressBase Plus Islands will be communicated on the [AddressBase Plus Islands Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus-islands/addressbase-plus-islands-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Premium Islands issues

Details of live and resolved data issues for AddressBase Premium Islands will be communicated on the [AddressBase Premium Islands Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium-islands/addressbase-premium-islands-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

## Next release

The next release of AddressBase Islands products, Epoch 120, is scheduled for **04 September 2025**.


# AddressBase Products June 2025 – Epoch 119

This release note provides information about the June 2025 (Epoch 119) release of the AddressBase products. These products were released to customers on 12 June 2025.

## Record counts

| Product                | Full Supply Record Count | Change-Only Update Record Count |
| ---------------------- | ------------------------ | ------------------------------- |
| OS Open UPRN           | 41 230 108               | N/A                             |
| AddressBase            | 30 720 584               | 119 944                         |
| AddressBase Plus       | 38 417 757               | 2 268 393                       |
| AddressBase Premium    | See rows below           | See rows below                  |
| Street                 | 1 516 400                | 8 955                           |
| Street Descriptor      | 1 640 323                | 5 538                           |
| BLPU                   | 41 230 108               | 293 195                         |
| Classification         | 45 048 547               | 177 703                         |
| LPI                    | 46 493 867               | 138 503                         |
| Organisation           | 1 395 393                | 18 469                          |
| Delivery Point Address | 30 832 005               | 52 027                          |
| Application Cross Ref. | 199 661 448              | 4 638 074                       |
| Successor              | 0                        | 0                               |

{% hint style="info" %}

* The Full Supply record counts are based on a Managed Great Britain Set (MGBS). If you have ordered your national coverage via the online ordering system using a polygon outline, then your counts may differ.
* Please note that Change-Only Updates (COUs) are not available for the OS Open UPRN product.
  {% endhint %}

## Product supply comparison

There is a difference in product counts between taking a national Managed Great Britain Set (MGBS) and a national Area of Interest (AOI). This is because the two supplies use different selection criteria. The differences are shown in the following table, allowing for you to validate your data holdings once you have loaded the latest release of AddressBase data.

The national AOI refers to the pre-selection GB polygon from our download store. Therefore, if you have drawn your own AOI, the count will vary.

If you are unsure of your supply type, please check this with your OS Relationship Manager.

| Product                | MGBS Full Count | National AOI Full Count | Difference     |
| ---------------------- | --------------- | ----------------------- | -------------- |
| AddressBase            | 30 720 584      | 30 720 584              | 0              |
| AddressBase Plus       | 38 417 757      | 38 417 734              | 23             |
| AddressBase Premium    | See rows below  | See rows below          | See rows below |
| Street                 | 1 516 400       | 1 516 397               | 3              |
| Street Descriptor      | 1 640 323       | 1 640 320               | 3              |
| BLPU                   | 41 230 108      | 41 230 081              | 27             |
| Classification         | 45 048 547      | 45 048 520              | 27             |
| LPI                    | 46 493 867      | 46 493 839              | 28             |
| Organisation           | 1 395 393       | 1 395 391               | 2              |
| Delivery Point Address | 30 832 005      | 30 832 005              | 0              |
| Application Cross Ref. | 199 661 448     | 199 661 421             | 0              |
| Successor              | 0               | 0                       | 0              |

It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the '[Working with COU data' page in the AddressBase Core Getting Started Guide](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-getting-started-guide/working-with-cou-data).

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the numbers of these records which can be expected in an **MGBS supply**, and also how many tiles are affected if you take your supply as Changed Chunks.

### AddressBase

| Change Type              | Count  |
| ------------------------ | ------ |
| Inserts                  | 25 566 |
| Updates                  | 83 966 |
| Deletes                  | 10 412 |
| COU Populated Tile Count | 5 491  |

### AddressBase Plus

| Change Type              | Count     |
| ------------------------ | --------- |
| Inserts                  | 42 185    |
| Updates                  | 2 211 332 |
| Deletes                  | 14 876    |
| COU Populated Tile Count | 7 563     |

### AddressBase Premium

| AddressBase Premium Table | Inserts   | Updates | Deletes   |
| ------------------------- | --------- | ------- | --------- |
| Street                    | 1 131     | 7 465   | 359       |
| Street Descriptor         | 1 186     | 3 991   | 361       |
| BLPU                      | 36 990    | 253 219 | 2986      |
| Classification            | 56 145    | 96 264  | 25 294    |
| LPI                       | 47 663    | 87 038  | 3 802     |
| Organisation              | 5 360     | 5 096   | 8 013     |
| Delivery Point Address    | 25 837    | 16 062  | 10 128    |
| Application Cross Ref.    | 2 215 974 | 426 221 | 1 995 879 |

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 119:

| Data Source                          | Date          |
| ------------------------------------ | ------------- |
| Royal Mail PAF                       | 08 May 2025   |
| National Land and Property Gazetteer | 08 May 2025   |
| One Scotland Gazetteer               | 21 April 2025 |
| VOA Non-Domestic Rates               | 06 May 2025   |
| VOA Council Tax                      | 06 May 2025   |
| OS MasterMap Topography Layer        | 10 April 2025 |
| OS MasterMap Highways Network        | 07 May 2025   |
| Code-Point with Polygons             | 01 April 2025 |
| Boundary-Line                        | 01 May 2025   |

## Data issues

### AddressBase

Details of live and resolved data issues for AddressBase will be communicated on the [AddressBase Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Plus issues

Details of live and resolved data issues for AddressBase Plus will be communicated on the [AddressBase Plus Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus/addressbase-plus-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Premium

Details of live and resolved data issues for AddressBase Premium will be communicated on the [AddressBase Premium Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium/addressbase-premium-known-data-issues-service-disruptions-and-planned-maintenance). This page will provide details of their impacts and updates on the expected time frame for their resolution.

## Improvements in Epoch 119

### Valuation Office Agency matching

The match rates for Council Tax and Non-Domestic Rates for Epoch 119 are detailed as follows based on Valuation Office Agency (VOA) records up to 06 May 2025. The match rate is applicable to the AddressBase Premium product.

| Data Source        | Records Received | % Matched |
| ------------------ | ---------------- | --------- |
| Council Tax        | 27 259 167       | 99.91     |
| Non-Domestic Rates | 2 122 646        | 96.40     |

### Tertiary classifications

Work is being undertaken to improve the classifications of records within the AddressBase products. This work has resulted in 45 877 more tertiary classifications present in Epoch 119 compared to Epoch 118. Indeed, 88.2\*\*%\*\* of these tertiary classification improvements are against residential codes.

## Next release

The next release of AddressBase products, Epoch 120, is scheduled for **31 July 2025**.


# AddressBase Islands June 2025 – Epoch 119

This release note provides information about the June 2025 (Epoch 119) release of the AddressBase Islands products. These products were released to customers on 12 June 2025.

## Record counts

| Product                     | Full Supply Record Count | Change-Only Update Record Count |
| --------------------------- | ------------------------ | ------------------------------- |
| AddressBase Plus Islands    | 1 163 825                | 4 446                           |
| AddressBase Premium Islands | See rows below           | See rows below                  |
| Street                      | 48 847                   | 169                             |
| Street Descriptor           | 48 847                   | 55                              |
| BLPU                        | 1 242 982                | 4 896                           |
| Classification              | 1 242 982                | 1 915                           |
| LPI                         | 1 252 802                | 2 892                           |
| Organisation                | 38 818                   | 61                              |
| Delivery Point Address      | 979 584                  | 1 135                           |
| Application Cross Ref.      | 1 308 493                | 2 023                           |
| Successor                   | 0                        | 0                               |

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase Islands product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the count of these records.

### AddressBase Plus Islands

| Change Type | Count |
| ----------- | ----- |
| Inserts     | 1 087 |
| Updates     | 3 142 |
| Deletes     | 217   |

### AddressBase Premium Islands

| AddressBase Premium Islands Table | Inserts | Updates | Deletes |
| --------------------------------- | ------- | ------- | ------- |
| Street                            | 55      | 114     | 0       |
| Street Descriptor                 | 55      | 0       | 0       |
| BLPU                              | 1 211   | 3 586   | 99      |
| Classification                    | 1 211   | 605     | 99      |
| LPI                               | 1 223   | 1 570   | 99      |
| Organisation                      | 12      | 13      | 36      |
| Delivery Point Address            | 745     | 206     | 184     |
| Application Cross Ref.            | 1 150   | 706     | 167     |
| Successor                         | 0       | 0       | 0       |

It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the '[Working with COU data' page in the AddressBase Core Getting Started Guide](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-getting-started-guide/working-with-cou-data).

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 119:

| Data Source                | Date        |
| -------------------------- | ----------- |
| Pointer (Northern Ireland) | 07 May 2025 |
| DigiMap (Channel Islands)  | 08 May 2025 |
| Isle of Man                | 08 May 2025 |
| Royal Mail PAF             | 08 May 2025 |

## Data issues

### AddressBase Plus Islands issues

Details of live and resolved data issues for AddressBase Plus Islands will be communicated on the [AddressBase Plus Islands Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus-islands/addressbase-plus-islands-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Premium Islands issues

Details of live and resolved data issues for AddressBase Premium Islands will be communicated on the [AddressBase Premium Islands Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium-islands/addressbase-premium-islands-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

## Next release

The next release of AddressBase Islands products, Epoch 120, is scheduled for **31 July 2025**.


# AddressBase Products May 2025 – Epoch 118

This release note provides information about the May 2025 (Epoch 118) release of the AddressBase products. These products were released to customers on 01 May 2025.

{% hint style="info" %}

## Object Without Postal Address (OWPA) enhancement in Epoch 118 for AddressBase Premium and AddressBase Plus

There is a small uplift in this release of both AddressBase Premium and AddressBase Plus due to an improvement in the Object Without Postal Address (OWPA) features contained within these two products. As a result of this uplift, COU counts are around 30% larger, in comparison to the 3 previous releases. This may result in slower processing times.
{% endhint %}

## Record counts

| Product                | Full Supply Record Count | Change-Only Update Record Count |
| ---------------------- | ------------------------ | ------------------------------- |
| OS Open UPRN           | 41 196 104               | N/A                             |
| AddressBase            | 30 705 430               | 152 191                         |
| AddressBase Plus       | 38 390 448               | 1 085 737                       |
| AddressBase Premium    | See rows below           | See rows below                  |
| Street                 | 1 515 628                | 4 732                           |
| Street Descriptor      | 1 639 498                | 3 233                           |
| BLPU                   | 41 196 104               | 790 039                         |
| Classification         | 45 017 696               | 446 122                         |
| LPI                    | 46 450 006               | 620 587                         |
| Organisation           | 1 398 046                | 19 314                          |
| Delivery Point Address | 30 816 296               | 64 760                          |
| Application Cross Ref. | 199 441 353              | 1 235 928                       |
| Successor              | 0                        | 0                               |

{% hint style="info" %}

* The Full Supply record counts are based on a Managed Great Britain Set (MGBS). If you have ordered your national coverage via the online ordering system using a polygon outline, then your counts may differ.
* Please note that Change-Only Updates (COUs) are not available for the OS Open UPRN product.
  {% endhint %}

## Product supply comparison

There is a difference in product counts between taking a national Managed Great Britain Set (MGBS) and a national Area of Interest (AOI). This is because the two supplies use different selection criteria. The differences are shown in the following table, allowing for you to validate your data holdings once you have loaded the latest release of AddressBase data.

The national AOI refers to the pre-selection GB polygon from our download store. Therefore, if you have drawn your own AOI, the count will vary.

If you are unsure of your supply type, please check this with your OS Relationship Manager.

| Product                | MGBS Full Count | National AOI Full Count | Difference     |
| ---------------------- | --------------- | ----------------------- | -------------- |
| AddressBase            | 30 705 430      | 30 705 430              | 0              |
| AddressBase Plus       | 38 390 448      | 38 390 426              | 22             |
| AddressBase Premium    | See rows below  | See rows below          | See rows below |
| Street                 | 1 515 628       | 1 515 625               | 3              |
| Street Descriptor      | 1 639 498       | 1 639 495               | 3              |
| BLPU                   | 41 196 104      | 41 196 078              | 26             |
| Classification         | 45 017 696      | 45 017 670              | 4              |
| LPI                    | 46 450 006      | 46 449 979              | 27             |
| Organisation           | 1 398 046       | 1 398 044               | 2              |
| Delivery Point Address | 30 816 296      | 30 816 296              | 0              |
| Application Cross Ref. | 199 441 353     | 199 441 327             | 26             |
| Successor              | 0               | 0                       | 0              |

It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the '[Working with COU data' page in the AddressBase Core Getting Started Guide](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-getting-started-guide/working-with-cou-data).

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the numbers of these records which can be expected in an **MGBS supply**, and also how many tiles are affected if you take your supply as Changed Chunks.

### AddressBase

| Change Type              | Count   |
| ------------------------ | ------- |
| Inserts                  | 39 607  |
| Updates                  | 103 385 |
| Deletes                  | 9 199   |
| COU Populated Tile Count | 5 450   |

### AddressBase Plus

| Change Type              | Count   |
| ------------------------ | ------- |
| Inserts                  | 146 606 |
| Updates                  | 896 728 |
| Deletes                  | 42 403  |
| COU Populated Tile Count | 8 520   |

### AddressBase Premium

| AddressBase Premium Table | Inserts | Updates | Deletes |
| ------------------------- | ------- | ------- | ------- |
| Street                    | 1 524   | 3 177   | 31      |
| Street Descriptor         | 1 572   | 1 627   | 34      |
| BLPU                      | 146 717 | 640 377 | 2 945   |
| Classification            | 172 147 | 242 226 | 31 749  |
| LPI                       | 168 697 | 448 093 | 3 797   |
| Organisation              | 5 785   | 5 762   | 7 767   |
| Delivery Point Address    | 40 444  | 14 910  | 9 406   |
| Application Cross Ref.    | 564 892 | 636 931 | 34 105  |

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 118:

| Data Source                          | Date             |
| ------------------------------------ | ---------------- |
| Royal Mail PAF                       | 27 March 2025    |
| National Land and Property Gazetteer | 27 March 2025    |
| One Scotland Gazetteer               | 10 March 2025    |
| VOA Non-Domestic Rates               | 25 March 2025    |
| VOA Council Tax                      | 25 March 2025    |
| OS MasterMap Topography Layer        | 27 February 2025 |
| OS MasterMap Highways Network        | 07 March 2025    |
| Code-Point with Polygons             | 02 January 2025  |
| Boundary-Line                        | 02 October 2024  |

## Data issues

### AddressBase

Details of live and resolved data issues for AddressBase will be communicated on the [AddressBase Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Plus issues

Details of live and resolved data issues for AddressBase Plus will be communicated on the [AddressBase Plus Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus/addressbase-plus-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Premium

Details of live and resolved data issues for AddressBase Premium will be communicated on the [AddressBase Premium Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium/addressbase-premium-known-data-issues-service-disruptions-and-planned-maintenance). This page will provide details of their impacts and updates on the expected time frame for their resolution.

## Improvements in Epoch 118

### Valuation Office Agency matching

The match rates for Council Tax and Non-Domestic Rates for Epoch **Epoch 118** are detailed as follows based on Valuation Office Agency (VOA) records up to **25 March 2025**. The match rate is applicable to the AddressBase Premium product.

| Data Source        | Records Received | % Matched |
| ------------------ | ---------------- | --------- |
| Council Tax        | 27 251 204       | 99.91     |
| Non-Domestic Rates | 2 120 750        | 96.46     |

## Next release

The next release of AddressBase products, Epoch 119, is scheduled for **12 June 2025**.


# AddressBase Islands May 2025 – Epoch 118

This release note provides information about the May 2025 (Epoch 118) release of the AddressBase Islands products. These products were released to customers on 01 May 2025.

{% hint style="info" %}

### Object Without Postal Address (OWPA) enhancement in Epoch 118 for AddressBase Premium Islands and AddressBase Plus Islands

There is a small uplift in this release of both AddressBase Premium Islands and AddressBase Plus Islands due to an improvement in the Object Without Postal Address (OWPA) features contained within these products. As a result of this uplift, COU counts are around 30% larger, in comparison to the 3 previous releases; this may result in slower processing times.
{% endhint %}

## Record counts

| Product                     | Full Supply Record Count | Change-Only Update Record Count |
| --------------------------- | ------------------------ | ------------------------------- |
| AddressBase Plus Islands    | 1 162 955                | 17 958                          |
| AddressBase Premium Islands | See rows below           | See rows below                  |
| Street                      | 48 792                   | 321                             |
| Street Descriptor           | 48 792                   | 32                              |
| BLPU                        | 1 241 870                | 17 908                          |
| Classification              | 1 241 870                | 3 589                           |
| LPI                         | 1 251 678                | 4 131                           |
| Organisation                | 38 842                   | 254                             |
| Delivery Point Address      | 979 023                  | 14 044                          |
| Application Cross Ref.      | 1 307 510                | 3 429                           |
| Successor                   | 0                        | 0                               |

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase Islands product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the count of these records.

### AddressBase Plus Islands

| Change Type | Count |
| ----------- | ----- |
| Inserts     | 8 257 |
| Updates     | 9 464 |
| Deletes     | 237   |

### AddressBase Premium Islands

| AddressBase Premium Islands Table | Inserts | Updates | Deletes |
| --------------------------------- | ------- | ------- | ------- |
| Street                            | 32      | 289     | 0       |
| Street Descriptor                 | 32      | 0       | 0       |
| BLPU                              | 2 806   | 14 937  | 165     |
| Classification                    | 2 806   | 618     | 165     |
| LPI                               | 2 825   | 1 141   | 165     |
| Organisation                      | 156     | 42      | 56      |
| Delivery Point Address            | 13 190  | 213     | 641     |
| Application Cross Ref.            | 2 773   | 360     | 296     |
| Successor                         | 0       | 0       | 0       |

It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the '[Working with COU data' page in the AddressBase Core Getting Started Guide](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-getting-started-guide/working-with-cou-data).

## Source data currency

The following information relates to the currency of the source data used in the creation of **Epoch 118**:

| Data Source                | Date          |
| -------------------------- | ------------- |
| Pointer (Northern Ireland) | 27 March 2025 |
| DigiMap (Channel Islands)  | 27 March 2025 |
| Isle of Man                | 27 March 2025 |
| Royal Mail PAF             | 27 March 2025 |

## Data issues

### AddressBase Plus Islands issues

Details of live and resolved data issues for AddressBase Plus Islands will be communicated on the [AddressBase Plus Islands Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus-islands/addressbase-plus-islands-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

### AddressBase Premium Islands issues

Details of live and resolved data issues for AddressBase Premium Islands will be communicated on the [AddressBase Premium Islands Known Data Issues page](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium-islands/addressbase-premium-islands-known-data-issues). This page will provide details of their impacts and updates on the expected time frame for their resolution.

## Next release

The next release of AddressBase Islands products, **Epoch 119**, is scheduled for **12 June 2025**.


# AddressBase Products March 2025 – Epoch 117

This release note provides information about the March 2025 Epoch 117 release of the AddressBase products. These products were released to customers on 20 March 2025.

## Record counts

| Product                | Full Supply Record Count | Change-Only Update Record Count |
| ---------------------- | ------------------------ | ------------------------------- |
| OS Open UPRN           | 41 052 332               | N/A                             |
| AddressBase            | 30 675 022               | 138 394                         |
| AddressBase Plus       | 38 286 245               | 721 346                         |
| AddressBase Premium    | See rows below           | See rows below                  |
| Street                 | 1 514 135                | 4 127                           |
| Street Descriptor      | 1 637 960                | 4 765                           |
| BLPU                   | 41 052 332               | 348 127                         |
| Classification         | 44 877 298               | 198 513                         |
| LPI                    | 46 285 106               | 149 761                         |
| Organisation           | 1 400 028                | 27 007                          |
| Delivery Point Address | 30 785 258               | 57 204                          |
| Application Cross Ref. | 198 910 566              | 717 312                         |
| Successor              | 0                        | 0                               |

{% hint style="info" %}

* The Full Supply record counts are based on a Managed Great Britain Set (MGBS). If you have ordered your national coverage via the online ordering system using a polygon outline, then your counts may differ.
* Please note that Change-Only Updates (COUs) are not available for the OS Open UPRN product.
  {% endhint %}

## Product supply comparison

There is a difference in product counts between taking a national Managed Great Britain Set (MGBS) and a national Area of Interest (AOI). This is because the two supplies use different selection criteria. The differences are shown in the following table, allowing for you to validate your data holdings once you have loaded the latest release of AddressBase data.

The national AOI refers to the pre-selection GB polygon from our download store. Therefore, if you have drawn your own AOI, the count will vary.

If you are unsure of your supply type, please check this with your OS Relationship Manager.

| Product                | MGBS Full Count | National AOI Full Count | Difference     |
| ---------------------- | --------------- | ----------------------- | -------------- |
| AddressBase            | 30 675 022      | 30 675 022              | 0              |
| AddressBase Plus       | 38 286 245      | 38 286 223              | 22             |
| AddressBase Premium    | See rows below  | See rows below          | See rows below |
| Street                 | 1 514 135       | 1 514 132               | 3              |
| Street Descriptor      | 1 637 960       | 1 637 957               | 3              |
| BLPU                   | 41 052 332      | 41 052 306              | 26             |
| Classification         | 44 877 298      | 44 877 272              | 26             |
| LPI                    | 46 285 106      | 46 285 079              | 27             |
| Organisation           | 1 400 028       | 1 400 026               | 2              |
| Delivery Point Address | 30 785 258      | 30 785 258              | 0              |
| Application Cross Ref. | 198 910 566     | 198 910 540             | 26             |
| Successor              | 0               | 0                       | 0              |

It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the '[Working with COU data' page in the AddressBase Core Getting Started Guide](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-getting-started-guide/working-with-cou-data).

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the numbers of these records which can be expected in an **MGBS supply**, and also how many tiles are affected if you take your supply as Changed Chunks.

### AddressBase

| Change Type              | Count  |
| ------------------------ | ------ |
| Inserts                  | 32 301 |
| Updates                  | 96 676 |
| Deletes                  | 9 417  |
| COU Populated Tile Count | 5 412  |

### AddressBase Plus

| Change Type              | Count   |
| ------------------------ | ------- |
| Inserts                  | 47 638  |
| Updates                  | 659 891 |
| Deletes                  | 13 817  |
| COU Populated Tile Count | 7 297   |

### AddressBase Premium

| AddressBase Premium Table | Inserts | Updates | Deletes |
| ------------------------- | ------- | ------- | ------- |
| Street                    | 1 071   | 3 031   | 25      |
| Street Descriptor         | 1 114   | 3 616   | 35      |
| BLPU                      | 44 401  | 299 702 | 4 024   |
| Classification            | 68 269  | 102 102 | 28 142  |
| LPI                       | 59 085  | 85 866  | 4 810   |
| Organisation              | 5 710   | 8 051   | 13 246  |
| Delivery Point Address    | 33 073  | 14 982  | 9 149   |
| Application Cross Ref.    | 191 523 | 486 447 | 39 342  |

## Source data currency

The following information relates to the currency of the source data used in the creation of **Epoch 117**:

| Data Source                          | Date             |
| ------------------------------------ | ---------------- |
| Royal Mail PAF                       | 13 February 2025 |
| National Land and Property Gazetteer | 13 February 2025 |
| One Scotland Gazetteer               | 27 January 2025  |
| VOA Non-Domestic Rates               | 10 February 2025 |
| VOA Council Tax                      | 10 February 2025 |
| OS MasterMap Topography Layer        | 16 January 2025  |
| OS MasterMap Highways Network        | 06 February 2025 |
| Code-Point with Polygons             | 02 January 2025  |
| Boundary-Line                        | 02 October 2024  |

## Data issues

### AddressBase Plus issues

**Affected output formats: CSV and GML**

* There are **7 966** Unique Property Reference Numbers (UPRNs) which reference a Parent UPRN that cannot be found in the product. This is because the Parent UPRN is either provisional or historic and is not matched to the Royal Mail Postcode Address File (PAF) or Valuation Office Agency (VOA) record, meaning that it is not included in the AddressBase Plus product as per the existing background logic rules.
* There are **231** records with a sao\_start\_no or sao\_text that have no Parent UPRN in the product. This is because the Parent UPRN is a historical record which is included as part of the logic for record inclusion in the AddressBase Plus products.

## Improvements in Epoch 117

### Valuation Office Agency matching

The match rates for Council Tax and Non-Domestic Rates for Epoch 117 are detailed as follows based on Valuation Office Agency (VOA) records up to **10 February 2025**. The match rate is applicable to the AddressBase Premium product.

| Data Source        | Records Received | % Matched |
| ------------------ | ---------------- | --------- |
| Council Tax        | 27 247 539       | 99.9      |
| Non-Domestic Rates | 2 120 424        | 96.48     |

### Tertiary classifications

Work is being undertaken to improve the classifications of records within the AddressBase products. This work has resulted in 69 348 more tertiary classifications present in Epoch 117 compared to Epoch 116. Indeed, 88.6 % of these tertiary classification improvements are against residential codes.

## Next release

The next release of AddressBase products, Epoch **118**, is scheduled for **01 May 2025**.


# AddressBase Islands March 2025 – Epoch 117

This release note provides information about the March 2025 Epoch 117 release of the AddressBase Islands products. These products were released to customers on 20 March 2025

## Record counts

| Product                     | Full Supply Record Count | Change-Only Update Record Count |
| --------------------------- | ------------------------ | ------------------------------- |
| AddressBase Plus Islands    | 1 154 935                | 3 461                           |
| AddressBase Premium Islands | See rows below           | See rows below                  |
| Street                      | 48 760                   | 127                             |
| Street Descriptor           | 48 760                   | 49                              |
| BLPU                        | 1 239 229                | 3 933                           |
| Classification              | 1 239 229                | 2 023                           |
| LPI                         | 1 249 018                | 2 597                           |
| Organisation                | 38 742                   | 258                             |
| Delivery Point Address      | 966 474                  | 1 129                           |
| Application Cross Ref.      | 1 305 033                | 1 692                           |
| Successor                   | 0                        | 0                               |

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase Islands product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the count of these records.

### AddressBase Plus Islands

| Change Type | Count |
| ----------- | ----- |
| Inserts     | 1 039 |
| Updates     | 2 234 |
| Deletes     | 188   |

### AddressBase Premium Islands

| AddressBase Premium Islands Table | Inserts | Updates | Deletes |
| --------------------------------- | ------- | ------- | ------- |
| Street                            | 35      | 90      | 2       |
| Street Descriptor                 | 35      | 12      | 2       |
| BLPU                              | 1 124   | 2 684   | 125     |
| Classification                    | 1 124   | 774     | 125     |
| LPI                               | 1 193   | 1 279   | 125     |
| Organisation                      | 58      | 57      | 143     |
| Delivery Point Address            | 654     | 325     | 150     |
| Application Cross Ref.            | 1 114   | 385     | 193     |
| Successor                         | 0       | 0       | 0       |

It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the '[Working with COU data' page in the AddressBase Core Getting Started Guide](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-getting-started-guide/working-with-cou-data).

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 117:

| Data Source                | Date             |
| -------------------------- | ---------------- |
| Pointer (Northern Ireland) | 13 February 2025 |
| DigiMap (Channel Islands)  | 13 February 2025 |
| Isle of Man                | 13 February 2025 |
| Royal Mail PAF             | 13 February 2025 |

## Data issues

### AddressBase Plus Islands issues

There are no reported issues in this release of AddressBase Plus Islands.

### AddressBase Premium Islands issues

**Affected output formats: CSV and GML**

* **Street incorrect coordinates** – There are two Streets which have incorrect start or end coordinates of 000000. The unique identifiers can be provided upon request through your OS Relationship Manager.

## Next release

The next release of AddressBase Islands products, Epoch 118, is scheduled for 01 May 2025.


# AddressBase Products February 2025 – Epoch 116

This release note provides information about the February 2025 (Epoch 116) release of the AddressBase products. These products were released to customers on 06 February 2025.

Known issues will now be displayed on the 'Product Known Data Issues' subpages under each product.

## Record counts

<table><thead><tr><th width="253">Product</th><th>Full Supply Record Count</th><th>Change-Only Update Record Count</th></tr></thead><tbody><tr><td>OS Open UPRN</td><td>41,011,955</td><td>N/A</td></tr><tr><td>AddressBase</td><td>30,652,138</td><td>157,150</td></tr><tr><td>AddressBase Plus</td><td>38,252,424</td><td>582,353</td></tr><tr><td>AddressBase Premium</td><td>See rows below</td><td>See rows below</td></tr><tr><td>Street</td><td>1,513,089</td><td>5,202</td></tr><tr><td>Street Descriptor</td><td>1,636,881</td><td>2,918</td></tr><tr><td>BLPU</td><td>41,011,955</td><td>320,110</td></tr><tr><td>Classification</td><td>44,837,171</td><td>154,389</td></tr><tr><td>LPI</td><td>46,230,831</td><td>129,683</td></tr><tr><td>Organisation</td><td>1,407,564</td><td>16,239</td></tr><tr><td>Delivery Point Address</td><td>30,761,334</td><td>69,996</td></tr><tr><td>Application Cross Ref.</td><td>198,758,385</td><td>736,674</td></tr><tr><td>Successor</td><td>0</td><td>0</td></tr></tbody></table>

{% hint style="info" %}

* The Full Supply record counts are based on a Managed Great Britain Set (MGBS). If you have ordered your national coverage via the online ordering system using a polygon outline, then your counts may differ.
* Please note that Change-Only Updates (COUs) are not available for the OS Open UPRN product.
  {% endhint %}

## Product supply comparison

There is a difference in product counts between taking a national Managed Great Britain Set (MGBS) and a national Area of Interest (AOI). This is because the two supplies use different selection criteria. The differences are shown in the following table, allowing for you to validate your data holdings once you have loaded the latest release of AddressBase data.

The national AOI refers to the pre-selection GB polygon from our download store. Therefore, if you have drawn your own AOI, the count will vary.

If you are unsure of your supply type, please check this with your OS Relationship Manager.

| Product                | MGBS Full Count | National AOI Full Count | Difference     |
| ---------------------- | --------------- | ----------------------- | -------------- |
| AddressBase            | 30,652,138      | 30,652,138              | 0              |
| AddressBase Plus       | 38,252,424      | 38,252,403              | 21             |
| AddressBase Premium    | See rows below  | See rows below          | See rows below |
| Street                 | 1,513,089       | 1,513,086               | 3              |
| Street Descriptor      | 1,636,881       | 1,636,878               | 3              |
| BLPU                   | 1,011,955       | 41,011,930              | 25             |
| Classification         | 44,837,171      | 44,837,146              | 25             |
| LPI                    | 6,230,831       | 46,230,805              | 26             |
| Organisation           | 407,564         | 1,407,562               | 2              |
| Delivery Point Address | 30,761,334      | 30,761,334              | 0              |
| Application Cross Ref. | 198,758,385     | 198,758,360             | 25             |
| Successor              | 0               | 0                       | 0              |

It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the '[Working with COU data' page in the AddressBase Core Getting Started Guide](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-getting-started-guide/working-with-cou-data).

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the numbers of these records which can be expected in an **MGBS supply**, and also how many tiles are affected if you take your supply as Changed Chunks.

### AddressBase

| Change Type              | Count   |
| ------------------------ | ------- |
| Inserts                  | 43,892  |
| Updates                  | 103,297 |
| Deletes                  | 9,961   |
| COU Populated Tile Count | 5,743   |

### AddressBase Plus

| Change Type              | Count   |
| ------------------------ | ------- |
| Inserts                  | 48,887  |
| Updates                  | 521,021 |
| Deletes                  | 12,445  |
| COU Populated Tile Count | 6,909   |

### AddressBase Premium

<table><thead><tr><th width="187">AddressBase Premium Table</th><th>Inserts</th><th>Updates</th><th>Deletes</th></tr></thead><tbody><tr><td>Street</td><td>1,633</td><td>3,535</td><td>34</td></tr><tr><td>Street Descriptor</td><td>1,684</td><td>1,194</td><td>40</td></tr><tr><td>BLPU</td><td>42,757</td><td>274,322</td><td>3,031</td></tr><tr><td>Classification</td><td>52,337</td><td>82,401</td><td>19,651</td></tr><tr><td>LPI</td><td>57,853</td><td>67,612</td><td>4,218</td></tr><tr><td>Organisation</td><td>4,337</td><td>4,480</td><td>7,422</td></tr><tr><td>Delivery Point Address</td><td>44,752</td><td>15,200</td><td>10,044</td></tr><tr><td>Application Cross Ref.</td><td>192,512</td><td>509,368</td><td>34,794</td></tr></tbody></table>

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 116:

| Data Source                          | Date             |
| ------------------------------------ | ---------------- |
| Royal Mail PAF                       | 02 January 2025  |
| National Land and Property Gazetteer | 02 January 2025  |
| One Scotland Gazetteer               | 09 December 2024 |
| VOA Non-Domestic Rates               | 23 December 2024 |
| VOA Council Tax                      | 23 December 2024 |
| OS MasterMap Topography Layer        | 28 November 2024 |
| OS MasterMap Highways Network        | 05 December 2024 |
| Code-Point with Polygons             | 02 January 2025  |
| Boundary-Line                        | 02 October 2024  |

## Improvements in Epoch 116

### Valuation Office Agency matching

The match rates for Council Tax and Non-Domestic Rates for Epoch 116 are detailed as follows based on Valuation Office Agency (VOA) records up to **23 December 2024**. The match rate is applicable to the AddressBase Premium product.

| Data Source        | Records Received | % Matched |
| ------------------ | ---------------- | --------- |
| Council Tax        | 27,227,905       | 99.92     |
| Non-Domestic Rates | 2,120,341        | 96.44     |

### Tertiary classifications

Work is being undertaken to improve the classifications of records within the AddressBase products. This work has resulted in **49 241** more tertiary classifications present in **Epoch 116** compared to **Epoch 115**. Indeed, **88.69 %** of these tertiary classification improvements are against residential codes.

## Next release

The next release of AddressBase products, Epoch **117**, is scheduled for **20 March 2025**.


# AddressBase Islands February 2025 – Epoch 116

This release note provides information about the February 2025  (Epoch 116) release of the AddressBase Islands products. These products were released to customers on 06 February 2025.

Known issues will now be displayed on the 'Product Known Data Issues' subpages under each product.

## Record counts

| Product                     | Full Supply Record Count | Change-Only Update Record Count |
| --------------------------- | ------------------------ | ------------------------------- |
| AddressBase Plus Islands    | 1,154,084                | 3,135                           |
| AddressBase Premium Islands | See rows below           | See rows below                  |
| Street                      | 48,727                   | 179                             |
| Street Descriptor           | 48,727                   | 55                              |
| BLPU                        | 1,238,230                | 4,281                           |
| Classification              | 1,238,230                | 2,461                           |
| LPI                         | 1,247,950                | 3,075                           |
| Organisation                | 38,827                   | 250                             |
| Delivery Point Address      | 965,970                  | 1,124                           |
| Application Cross Ref.      | 1,304,112                | 2,138                           |
| Successor                   | 0                        | 0                               |

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase Islands product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the count of these records.

### AddressBase Plus Islands

| Change Type | Count |
| ----------- | ----- |
| Inserts     | 1,315 |
| Updates     | 1,539 |
| Deletes     | 281   |

### AddressBase Premium Islands

| AddressBase Premium Islands Table | Inserts | Updates | Deletes |
| --------------------------------- | ------- | ------- | ------- |
| Street                            | 52      | 126     | 1       |
| Street Descriptor                 | 52      | 2       | 1       |
| BLPU                              | 1,535   | 2,515   | 231     |
| Classification                    | 1,535   | 695     | 231     |
| LPI                               | 1,544   | 1,300   | 231     |
| Organisation                      | 55      | 109     | 86      |
| Delivery Point Address            | 886     | 143     | 95      |
| Application Cross Ref.            | 1,499   | 297     | 342     |
| Successor                         | 0       | 0       | 0       |

It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the '[Working with COU data' page in the AddressBase Core Getting Started Guide](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-getting-started-guide/working-with-cou-data).

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 116:

| Data Source                | Date                |
| -------------------------- | ------------------- |
| Pointer (Northern Ireland) | **02 January 2025** |
| DigiMap (Channel Islands)  | **02 January 2025** |
| Isle of Man                | **02 January 2025** |
| Royal Mail PAF             | **02 January 2025** |

## Next release

The next release of AddressBase Islands products, Epoch **117**, is scheduled for **20 March 2025**.


# AddressBase Products December 2024 – Epoch 115

This release note provides information about the December 2024 release of the AddressBase products. These products were released to customers on 19 December 2024.

## Record counts

| Product                | Full Supply Record Count\[1] | Change-Only Update Record Count\[2] |
| ---------------------- | ---------------------------- | ----------------------------------- |
| OS OpenUPRN            | 40 972 229                   | N/A                                 |
| AddressBase            | 30,618,207                   | 160,698                             |
| AddressBase Plus       | 38,215,982                   | 567,209                             |
| AddressBase Premium    | See rows below               | See rows below                      |
| Street                 | 1,511,490                    | 8,819                               |
| Street Descriptor      | 1,635,237                    | 3,827                               |
| BLPU                   | 40,972,229                   | 351,639                             |
| Classification         | 44,804,485                   | 156,612                             |
| LPI                    | 46,177,196                   | 155,834                             |
| Organisation           | 1,410,649                    | 24,087                              |
| Delivery Point Address | 30,726,626                   | 75,116                              |
| Application Cross Ref. | 198,600,667                  | 735,324                             |
| Successor              | 0                            | 0                                   |

1. These counts are based on a Managed Great Britain Set (MGBS). If you have ordered your national coverage via the online ordering system using a polygon outline, then your counts may differ.
2. Change-Only Updates are not available for the OS Open UPRN product.

## Product supply comparison

There is a difference in product counts between taking a national Managed Great Britain Set (MGBS) and a national Area of Interest (AOI). This is because the two supplies use different selection criteria. The differences are shown in the following table, allowing for you to validate your data holdings once you have loaded the latest release of AddressBase data.

The national AOI refers to the pre-selection GB polygon from our download store. Therefore, if you have drawn your own AOI, the count will vary.

If you are unsure of your supply type, please check this with your OS Relationship Manager.

| Product                | MGBS Full Count | National AOI Full Count | Difference     |
| ---------------------- | --------------- | ----------------------- | -------------- |
| AddressBase            | 30 618 207      | 30 618 207              | 0              |
| AddressBase Plus       | 38 215 982      | 38 215 961              | 21             |
| AddressBase Premium    | See rows below  | See rows below          | See rows below |
| Street                 | 1,511,490       | 1,511,487               | 3              |
| Street Descriptor      | 1,635,237       | 1,635,234               | 3              |
| BLPU                   | 40,972,229      | 40,972,204              | 25             |
| Classification         | 44,804,485      | 44,804,460              | 25             |
| LPI                    | 46,177,196      | 46,177,170              | 26             |
| Organisation           | 1,410,649       | 1,410,647               | 2              |
| Delivery Point Address | 30,726,626      | 30,726,626              | 0              |
| Application Cross Ref. | 198,600,667     | 198,600,642             | 25             |
| Successor              | 0               | 0                       | 0              |

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the numbers of these records which can be expected in an **MGBS supply**,and also how many tiles are affected if you take your supply as Changed Chunks.

## AddressBase

| Change Type              | Count  |
| ------------------------ | ------ |
| Inserts                  | 52 317 |
| Updates                  | 92 108 |
| Deletes                  | 16 273 |
| COU Populated Tile Count | 5 743  |

## AddressBase Plus

| Change Type              | Count   |
| ------------------------ | ------- |
| Inserts                  | 47 492  |
| Updates                  | 498 918 |
| Deletes                  | 20 799  |
| COU Populated Tile Count | 7 094   |

## AddressBase Premium

| AddressBase Premium Table | Inserts | Updates | Updates |
| ------------------------- | ------- | ------- | ------- |
| Street                    | 1,175   | 6,933   | 711     |
| Street Descriptor         | 1,225   | 1,891   | 711     |
| BLPU                      | 40,941  | 299,115 | 11,583  |
| Classification            | 49,447  | 77,489  | 29,676  |
| LPI                       | 54,934  | 88,243  | 12,657  |
| Organisation              | 4,697   | 4,318   | 15,072  |
| Delivery Point Address    | 48,355  | 15,438  | 11,323  |
| Application Cross Ref.    | 203,570 | 460,627 | 71,127  |

It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the '[Working with COU data' page in the AddressBase Core Getting Started Guide](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-getting-started-guide/working-with-cou-data).

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 115:

| Data Source                          | Date             |
| ------------------------------------ | ---------------- |
| Royal Mail PAF                       | 14 November 2024 |
| National Land and Property Gazetteer | 14 November 2024 |
| One Scotland Gazetteer               | 28 October 2024  |
| VOA Non-Domestic Rates               | 11 November 2024 |
| VOA Council Tax                      | 11 November 2024 |
| OS MasterMap Topography Layer        | 05 November 2024 |
| OS MasterMap Highways Network        | 07 November 2024 |
| Code-Point with Polygons             | 01 October 2024  |
| Boundary-Line                        | 02 October 2024  |

## Data issues

### AddressBase Plus

**Affected output formats: CSV and GML**

* There are 6 552 Unique Property Reference Numbers (UPRNs) which reference a Parent UPRN that cannot be found in the product. This is because the Parent UPRN is either provisional or historic and is not matched to the Royal Mail Postcode Address File (PAF) or Valuation Office Agency (VOA) record, meaning that it is not included in the AddressBase Plus product as per the existing background logic rules.
* There are 219 records with a sao\_start\_no or sao\_text that have no Parent UPRN in the product. This is because the Parent UPRN is a historical record which is included as part of the logic for record inclusion in the AddressBase Plus products.

## Improvements in Epoch 115

### Valuation Office Agency matching

The match rates for Council Tax and Non-Domestic Rates for Epoch 115 are detailed as follows based on Valuation Office Agency (VOA) records up to 11 November 2024. The match rate is applicable to the AddressBase Premium product.

| Data Source        | Records Received | % Matched |
| ------------------ | ---------------- | --------- |
| Council tax        | 27 201 555       | 99.92     |
| Non-domestic rates | 2 119 490        | 96.49     |

### Tertiary classifications

Work is being undertaken to improve the classifications of records within the AddressBase products. This work has resulted in 38 207 more tertiary classifications present in Epoch 115 compared to Epoch 114. A total of 88.71% of these tertiary classification improvements are against residential codes.

### PAF matching

**AddressBase, AddressBase Plus and AddressBase Premium**

**Increased PAF matches shown in product** – 14 102 PAF records had been previously withheld from product due to a processing constraint which omitted UPRNs with multiple candidate PAF matches from showing in product as a one-one match. This was resolved on the 25/10/24.

The following graph shows the number of Postcode Address File (PAF) matched records in AddressBase by epoch:

<figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2Fg5J1yDAqhY601PbU39Rd%2F0.png?alt=media" alt="A graph showing the number of Postcode Address File (PAF) matched records in AddressBase by epoch starting from 30,353,039 in Epoch 102 and rising linearly to 30,726,641 in epoch 115."><figcaption><p>A graph showing the number of Postcode Address File (PAF) matched records in AddressBase by epoch.</p></figcaption></figure>

## Next release

The next release of AddressBase products, Epoch 116, is scheduled for **06 February 2025**.


# AddressBase Islands December 2024 – Epoch 115

This release note provides information about the December 2024 release of the AddressBase Islands products. These products were released to customers on 19 December 2024.

## Record counts

| Product                     | Full Supply Record Count | Change-Only Update Record Count |
| --------------------------- | ------------------------ | ------------------------------- |
| AddressBase Plus Islands    | 1 153 050                | 4 262                           |
| AddressBase Premium Islands | See rows below           | See rows below                  |
| Street                      | 48,676                   | 112                             |
| Street Descriptor           | 48,676                   | 32                              |
| BLPU                        | 1,236,926                | 4,892                           |
| Classification              | 1,236,926                | 2,348                           |
| LPI                         | 1,246,637                | 3,017                           |
| Organisation                | 38,858                   | 231                             |
| Delivery Point Address      | 965,179                  | 1,081                           |
| Application Cross Ref.      | 1,302,955                | 2,789                           |
| Successor                   | 0                        | 0                               |

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase Islands product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the count of these records.

## AddressBase Plus Islands

| Change Type | Count |
| ----------- | ----- |
| Inserts     | 1 275 |
| Updates     | 2 687 |
| Deletes     | 300   |

## AddressBase Premium Islands

| AddressBase Premium Islands Table | Inserts | Updates | Deletes |
| --------------------------------- | ------- | ------- | ------- |
| Street                            | 30      | 82      | 0       |
| Street Descriptor                 | 30      | 2       | 0       |
| BLPU                              | 1,272   | 3,438   | 182     |
| Classification                    | 1,272   | 894     | 182     |
| LPI                               | 1,299   | 1,536   | 182     |
| Organisation                      | 37      | 28      | 166     |
| Delivery Point Address            | 666     | 323     | 92      |
| Application Cross Ref.            | 1,291   | 1,194   | 304     |
| Successor                         | 0       | 0       | 0       |

It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the '[Working with COU data' page in the AddressBase Core Getting Started Guide](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-getting-started-guide/working-with-cou-data).

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 115:

| Data Source                | Date             |
| -------------------------- | ---------------- |
| Pointer (Northern Ireland) | 14 November 2024 |
| DigiMap (Channel Islands)  | 14 November 2024 |
| Isle of Man                | 14 November 2024 |
| Royal Mail PAF             | 14 November 2024 |

## Data issues

### AddressBase Premium Islands

* **Street incorrect coordinates** – There are two Streets which have incorrect start or end coordinates of 000000. The unique identifiers can be provided upon request through your OS Relationship Manager.
* AddressBase Premium Islands, AddressBase Plus Islands
* 14 102 PAF records (across GB and Islands product) had been previously withheld from product due to a processing constraint, which omitted UPRNs with multiple candidate PAF matches from showing in product as a one-one match. This was resolved on the 25/10/24.

## Next release

The next release of AddressBase products, Epoch 116, is scheduled for **06 February 2025**.


# AddressBase Products November 2024 – Epoch 114

This release note provides information about the November 2024 (Epoch 114) release of the AddressBase products. These products were released to customers on 07 November 2024.

## Update to the location of AddressBase technical documentation and release notes

AddressBase family product technical documentation (including technical specifications, release notes, getting started guides, etc.) is now available on the new [OS Download Products’ Documentation Platform](https://docs.os.uk/os-downloads). This platform is the new central location for all technical documentation for OS Premium and OpenData Download products (such as AddressBase, OS MasterMap Topography Layer, OS Open UPRN, etc.).

Over the next few months, the old PDFs containing product technical documentation will be removed from the product pages of the OS website and replaced by links to the refreshed documentation on the new platform.

[Release notes for AddressBase products are available on the new platform](https://docs.os.uk/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/release-notes); simply navigate to the new platform and click *Addressing and location portfolio* > *AddressBase Fundamentals* > *Release Notes*. Static PDF release notes for the AddressBase products will be replaced by digital release notes on the new platform over the next few months.

## Record counts

| Product                | Full Supply Record Count\[1] | Change-Only Update Record Count\[2] |
| ---------------------- | ---------------------------- | ----------------------------------- |
| OS OpenUPRN            | 40 942 871                   | N/A                                 |
| AddressBase            | 30 582 163                   | 141 175                             |
| AddressBase Plus       | 38 189 289                   | 575 982                             |
| AddressBase Premium    | See rows below               | See rows below                      |
| Street                 | 1 511 026                    | 10 216                              |
| Street Descriptor      | 1 634 723                    | 3 405                               |
| BLPU                   | 40 942 871                   | 281 573                             |
| Classification         | 44 784 714                   | 114 548                             |
| LPI                    | 46 134 919                   | 134 455                             |
| Organisation           | 1 421 024                    | 13 457                              |
| Delivery Point Address | 30 689 594                   | 60 166                              |
| Application Cross Ref. | 198 468 224                  | 739 827                             |
| Successor              | 0                            | 0                                   |

1. These counts are based on a Managed Great Britain Set (MGBS). If you have ordered your national coverage via the online ordering system using a polygon outline, then your counts may differ.
2. Change-Only Updates are not available for the OS Open UPRN product.

## Product supply comparison

There is a difference in product counts between taking a national Managed Great Britain Set (MGBS) and a national Area of Interest (AOI). This is because the two supplies use different selection criteria. The differences are shown in the following table, allowing for you to validate your data holdings once you have loaded the latest release of AddressBase data.

The national AOI refers to the pre-selection GB polygon from our download store. Therefore, if you have drawn your own AOI, the count will vary.

If you are unsure of your supply type, please check this with your OS Relationship Manager.

| Product                | MGBS Full Count | National AOI Full Count | Difference     |
| ---------------------- | --------------- | ----------------------- | -------------- |
| AddressBase            | 30 582 163      | 30 582 163              | 0              |
| AddressBase Plus       | 38 189 289      | 38 189 268              | 21             |
| AddressBase Premium    | See rows below  | See rows below          | See rows below |
| Street                 | 1 511 026       | 1 511 024               | 2              |
| Street Descriptor      | 1 634 723       | 1 634 721               | 2              |
| BLPU                   | 40 942 871      | 40 942 846              | 25             |
| Classification         | 44 784 714      | 44 784 689              | 25             |
| LPI                    | 46 134 919      | 46 134 893              | 26             |
| Organisation           | 1 421 024       | 1 421 022               | 2              |
| Delivery Point Address | 30 689 594      | 30 689 594              | 0              |
| Application Cross Ref. | 198 468 224     | 198 468 199             | 25             |
| Successor              | 0               | 0                       | 0              |

It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the '[Working with COU data' page in the AddressBase Core Getting Started Guide](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-getting-started-guide/working-with-cou-data).

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the numbers of these records which can be expected in an **MGBS supply**, and also how many tiles are affected if you take your supply as Changed Chunks.

### AddressBase

| Change Type              | Count  |
| ------------------------ | ------ |
| Inserts                  | 39 785 |
| Updates                  | 91 284 |
| Deletes                  | 10 106 |
| COU Populated Tile Count | 5 139  |

### AddressBase Plus

| Change Type              | Count   |
| ------------------------ | ------- |
| Inserts                  | 47 501  |
| Updates                  | 514 065 |
| Deletes                  | 14 416  |
| COU Populated Tile Count | 7 133   |

### AddressBase Premium

| AddressBase Premium Table | Inserts | Updates | Deletes |
| ------------------------- | ------- | ------- | ------- |
| Street                    | 1 372   | 8 603   | 241     |
| Street Descriptor         | 1 503   | 1 661   | 241     |
| BLPU                      | 38 154  | 238 422 | 4 997   |
| Classification            | 46 915  | 47 356  | 20 277  |
| LPI                       | 51 599  | 76 996  | 5 860   |
| Organisation              | 3 892   | 3 831   | 5 734   |
| Delivery Point Address    | 39 984  | 10 212  | 9 970   |
| Application Cross Ref.    | 202 342 | 496 125 | 41 360  |

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 114:

| Data Source                          | Date              |
| ------------------------------------ | ----------------- |
| Royal Mail PAF                       | 03 October 2024   |
| National Land and Property Gazetteer | 03 October 2024   |
| One Scotland Gazetteer               | 16 September 2024 |
| VOA Non-Domestic Rates               | 01 October 2024   |
| VOA Council Tax                      | 01 October 2024   |
| OS MasterMap Topography Layer        | 24 September 2024 |
| OS MasterMap Highways Network        | 03 October 2024   |
| Code-Point with Polygons             | 01 October 2024   |
| Boundary-Line                        | 02 October 2024   |

## Data issues

### AddressBase Plus issues

**Affected output formats: CSV and GML**

* There are 6 038 Unique Property Reference Numbers (UPRNs) which reference a Parent UPRN that cannot be found in the product. This is because the Parent UPRN is either provisional or historic and is not matched to the Royal Mail Postcode Address File (PAF) or Valuation Office Agency (VOA) record, meaning that it is not included in the AddressBase Plus product as per the existing background logic rules.
* There are 211 records with a sao\_start\_no or sao\_text that have no Parent UPRN in the product. This is because the Parent UPRN is a historical record which is included as part of the logic for record inclusion in the AddressBase Plus products.

## Improvements in Epoch 114

### Valuation Office Agency matching

The match rates for Council Tax and Non-Domestic Rates for Epoch 114 are detailed as follows based on Valuation Office Agency (VOA) records up to 01 October 2024. The match rate is applicable to the AddressBase Premium product.

| Data Source        | Records Received | % Matched |
| ------------------ | ---------------- | --------- |
| Council tax        | 27 171 964       | 99.92     |
| Non-domestic rates | 2 121 757        | 96.47     |

### Tertiary classifications

Work is being undertaken to improve the classifications of records within the AddressBase products. This work has resulted in 37 159 more tertiary classifications present in Epoch 114 compared to Epoch 113. Indeed, 88.71% of these tertiary classification improvements are against residential codes.

### PAF matching

The following graph shows the number of Postcode Address File (PAF) matched records in AddressBase by epoch:

<figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FvgMYn8euLcCcdVvujVbG%2FPAF%20image%20AB%20release%20note%20epoch%20114.png?alt=media&amp;token=98d70eec-da32-460a-a838-dafb5016befb" alt="The number of Postcode Address File (PAF) matched records in AddressBase by epoch. The number of PAF matched records in AddressBase has increased steadily over time, from 30 353 039 in Epoch 102 to 30 689 609 in Epoch 114."><figcaption><p>The number of Postcode Address File (PAF) matched records in AddressBase by epoch. The number of PAF matched records in AddressBase has increased steadily over time, from 30 353 039 in Epoch 102 to 30 689 609 in Epoch 114.</p></figcaption></figure>

## Next release

The next release of AddressBase products, Epoch 115, is scheduled for **19 December 2024**.


# AddressBase Islands November 2024 – Epoch 114

This release note provides information about the November 2024 release of the AddressBase Islands products. These products were released to customers on 07 November 2024.

## Update to the location of AddressBase technical documentation and release notes

AddressBase family product technical documentation (including technical specifications, release notes, getting started guides, etc.) is now available on the new [OS Download Products’ Documentation Platform](https://docs.os.uk/os-downloads). This platform is the new central location for all technical documentation for OS Premium and OpenData Download products (such as AddressBase, OS MasterMap Topography Layer, OS Open UPRN, etc.).

Over the next few months, the old PDFs containing product technical documentation will be removed from the product pages of the OS website and replaced by links to the refreshed documentation on the new platform.

[Release notes for AddressBase products are available on the new platform](https://docs.os.uk/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/release-notes); simply navigate to the new platform and click *Addressing and location portfolio* > *AddressBase Fundamentals* > *Release Notes*. Static PDF release notes for the AddressBase products will be replaced by digital release notes on the new platform over the next few months.

## Record counts

| Product                     | Full Supply Record Count | Change-Only Update Record Count |
| --------------------------- | ------------------------ | ------------------------------- |
| AddressBase Plus Islands    | 1 152 075                | 7 952                           |
| AddressBase Premium Islands | See rows below           | See rows below                  |
| Street                      | 48 646                   | 151                             |
| Street Descriptor           | 48 646                   | 30                              |
| BLPU                        | 1 235 836                | 9 106                           |
| Classification              | 1 235 836                | 5 652                           |
| LPI                         | 1 245 520                | 3 980                           |
| Organisation                | 38 987                   | 3 359                           |
| Delivery Point Address      | 964 605                  | 776                             |
| Application Cross Ref.      | 1 301 968                | 1 577                           |
| Successor                   | 0                        | 0                               |

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase Islands product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the count of these records.

### AddressBase Plus Islands

| Change Type | Count |
| ----------- | ----- |
| Inserts     | 869   |
| Updates     | 6960  |
| Deletes     | 123   |

### AddressBase Premium Islands

| AddressBase Premium Islands Table | Inserts | Updates | Deletes |
| --------------------------------- | ------- | ------- | ------- |
| Street                            | 30      | 121     | 0       |
| Street Descriptor                 | 30      | 0       | 0       |
| BLPU                              | 619     | 8 444   | 43      |
| Classification                    | 619     | 4 990   | 43      |
| LPI                               | 735     | 3 202   | 43      |
| Organisation                      | 1 458   | 1 160   | 741     |
| Delivery Point Address            | 538     | 184     | 54      |
| Application Cross Ref.            | 749     | 713     | 115     |
| Successor                         | 0       | 0       | 0       |

It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the '[Working with COU data' page in the AddressBase Core Getting Started Guide](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-getting-started-guide/working-with-cou-data).

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 114:

| Data Source                | Date              |
| -------------------------- | ----------------- |
| Pointer (Northern Ireland) | 30 September 2024 |
| DigiMap (Channel Islands)  | 03 October 2024   |
| Isle of Man                | 03 October 2024   |
| Royal Mail PAF             | 03 October 2024   |

## Data issues

### AddressBase Plus Islands issues

There are no reported issues in this release of AddressBase Plus Islands.

### AddressBase Premium Islands issues

**Affected output formats: CSV and GML**

* **Street incorrect coordinates** – There are two Streets which have incorrect start or end coordinates of 000000. The unique identifiers can be provided upon request through your OS Relationship Manager.

## Next release

The next release of AddressBase Islands products, Epoch 115, is scheduled for **19 December 2024**.


# AddressBase Products September 2024 – Epoch 113

This release note provides information about the September 2024 release of the AddressBase products. These products were released to customers on 26 September 2024.

## Record counts

| Product                | Full Supply Record Count\[1] | Change-Only Update Record Count\[2] |
| ---------------------- | ---------------------------- | ----------------------------------- |
| OS Open UPRN           | 40 909 714                   | N/A                                 |
| AddressBase            | 30 552 484                   | 137 772                             |
| AddressBase Plus       | 38 156 204                   | 677 294                             |
| AddressBase Premium    | See rows below               | See rows below                      |
| Street                 | 1 509 895                    | 5 780                               |
| Street Descriptor      | 1 633 461                    | 2 501                               |
| BLPU                   | 40 909 714                   | 355 256                             |
| Classification         | 44 758 076                   | 125 856                             |
| LPI                    | 46 089 180                   | 182 176                             |
| Organisation           | 1 422 866                    | 14 505                              |
| Delivery Point Address | 30 659 580                   | 54 376                              |
| Application Cross Ref. | 198 307 242                  | 735 178                             |
| Successor              | 0                            | 0                                   |

1. These counts are based on a Managed Great Britain Set (MGBS). If you have ordered your national coverage via the online ordering system using a polygon outline, then your counts may differ.
2. Change-Only Updates are not available for the OS Open UPRN product.

## Product supply comparison

There is a difference in product counts between taking a national Managed Great Britain Set (MGBS) and a national Area of Interest (AOI). This is because the two supplies use different selection criteria. The differences are shown in the following table, allowing for you to validate your data holdings once you have loaded the latest release of AddressBase data.

The national AOI refers to the pre-selection GB polygon from our download store. Therefore, if you have drawn your own AOI, the count will vary.

If you are unsure of your supply type, please check this with your OS Relationship Manager.

| Product                | MGBS Full Count | National AOI Full Count | Difference     |
| ---------------------- | --------------- | ----------------------- | -------------- |
| AddressBase            | 30 552 484      | 30 552 484              | 0              |
| AddressBase Plus       | 38 156 204      | 38 156 184              | 20             |
| AddressBase Premium    | See rows below  | See rows below          | See rows below |
| Street                 | 1 509 895       | 1 509 892               | 3              |
| Street Descriptor      | 1 633 461       | 1 633 458               | 3              |
| BLPU                   | 40 909 714      | 40 909 690              | 24             |
| Classification         | 44 758 076      | 44 758 052              | 24             |
| LPI                    | 46 089 180      | 46 089 155              | 25             |
| Organisation           | 1 422 866       | 1 422 864               | 2              |
| Delivery Point Address | 30 659 580      | 30 659 580              | 0              |
| Application Cross Ref. | 198 307 242     | 198 307 218             | 24             |
| Successor              | 0               | 0                       | 0              |

It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the '[Working with COU data' page in the AddressBase Core Getting Started Guide](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-getting-started-guide/working-with-cou-data).

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the numbers of these records which can be expected in an **MGBS supply**,and also how many tiles are affected if you take your supply as Changed Chunks.

### AddressBase

| Change Type              | Count  |
| ------------------------ | ------ |
| Inserts                  | 32 275 |
| Updates                  | 96 919 |
| Deletes                  | 8 578  |
| COU Populated Tile Count | 5 003  |

### AddressBase Plus

| Change Type              | Count   |
| ------------------------ | ------- |
| Inserts                  | 43 451  |
| Updates                  | 621 151 |
| Deletes                  | 12 692  |
| COU Populated Tile Count | 7 088   |

### AddressBase Premium

| AddressBase Premium Table | Inserts | Updates | Deletes |
| ------------------------- | ------- | ------- | ------- |
| Street                    | 1 264   | 4 501   | 15      |
| Street Descriptor         | 1 484   | 999     | 18      |
| BLPU                      | 39 273  | 312 858 | 3 125   |
| Classification            | 47 617  | 59 927  | 18 312  |
| LPI                       | 51 254  | 127 306 | 3 616   |
| Organisation              | 5 675   | 4 479   | 4 351   |
| Delivery Point Address    | 32 839  | 13 224  | 8 313   |
| Application Cross Ref.    | 183 150 | 520 267 | 31 761  |

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 113:

| Data Source                          | Date           |
| ------------------------------------ | -------------- |
| Royal Mail PAF                       | 22 August 2024 |
| National Land and Property Gazetteer | 22 August 2024 |
| One Scotland Gazetteer               | 05 August 2024 |
| VOA Non-Domestic Rates               | 19 August 2024 |
| VOA Council Tax                      | 19 August 2024 |
| OS MasterMap Topography Layer        | 13 August 2024 |
| OS MasterMap Highways Network        | 06 August 2024 |
| Code-Point with Polygons             | 01 July 2024   |
| Boundary-Line                        | 24 June 2024   |

## Data issues

### AddressBase Plus issues

**Affected output formats: CSV and GML**

* There are 6 504 Unique Property Reference Numbers (UPRNs) which reference a Parent UPRN that cannot be found in the product. This is because the Parent UPRN is either provisional or historic and is not matched to the Royal Mail Postcode Address File (PAF) or Valuation Office Agency (VOA) record, meaning that it is not included in the AddressBase Plus product as per the existing background logic rules.
* There are 227 records with a sao\_start\_no or sao\_text that have no Parent UPRN in the product. This is because the Parent UPRN is a historical record which is included as part of the logic for record inclusion in the AddressBase Plus products.

## Improvements in Epoch 113

### Valuation Office Agency matching

The match rates for Council Tax and Non-Domestic Rates for Epoch 113 are detailed as follows based on Valuation Office Agency (VOA) records up to 19 August 2024. The match rate is applicable to the AddressBase Premium product.

| Data Source        | Records Received | % Matched |
| ------------------ | ---------------- | --------- |
| Council tax        | 27 145 616       | 99.92     |
| Non-domestic rates | 2 122 260        | 96.47     |

### Tertiary classifications

Work is being undertaken to improve the classifications of records within the AddressBase products. This work has resulted in 37 159 more tertiary classifications present in Epoch 113 compared to Epoch 112. Indeed, 88.71% of these tertiary classification improvements are against residential codes.

### PAF matching

The following graph shows the number of Postcode Address File (PAF) matched records in AddressBase by epoch:

<figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FqfS8c6UD53zsStLUxuCs%2F0.png?alt=media" alt="The number of Postcode Address File (PAF) matched records in AddressBase by epoch. The number of PAF matched records in AddressBase has increased steadily over time, from 30 353 039 in Epoch 102 to 30 659 595 in Epoch 113."><figcaption><p>The number of Postcode Address File (PAF) matched records in AddressBase by epoch. The number of PAF matched records in AddressBase has increased steadily over time, from 30 353 039 in Epoch 102 to 30 659 595 in Epoch 113.</p></figcaption></figure>

## Next release

The next release of AddressBase products, Epoch 114, is scheduled for **07 November 2024**.


# AddressBase Islands September 2024 – Epoch 113

This release note provides information about the September 2024 release of the AddressBase Islands products. These products were released to customers on 26 September 2024.

## Record counts

| Product                     | Full Supply Record Count | Change-Only Update Record Count |
| --------------------------- | ------------------------ | ------------------------------- |
| AddressBase Plus Islands    | 1 151 329                | 4 703                           |
| AddressBase Premium Islands | See rows below           | See rows below                  |
| Street                      | 48 616                   | 162                             |
| Street Descriptor           | 48 616                   | 45                              |
| BLPU                        | 1 235 260                | 5 216                           |
| Classification              | 1 235 260                | 2 378                           |
| LPI                         | 1 244 828                | 3 229                           |
| Organisation                | 38 270                   | 181                             |
| Delivery Point Address      | 964 121                  | 1 018                           |
| Application Cross Ref.      | 1 301 334                | 3 067                           |
| Successor                   | 0                        | 0                               |

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase Islands product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the count of these records.

### AddressBase Plus Islands

| Change Type | Count |
| ----------- | ----- |
| Inserts     | 1 531 |
| Updates     | 2 916 |
| Deletes     | 256   |

### AddressBase Premium Islands

| AddressBase Premium Islands Table | Inserts | Updates | Deletes |
| --------------------------------- | ------- | ------- | ------- |
| Street                            | 45      | 117     | 0       |
| Street Descriptor                 | 45      | 0       | 0       |
| BLPU                              | 1 523   | 3 481   | 212     |
| Classification                    | 1 523   | 643     | 212     |
| LPI                               | 1 587   | 1 430   | 212     |
| Organisation                      | 53      | 25      | 103     |
| Delivery Point Address            | 605     | 293     | 120     |
| Application Cross Ref.            | 1 538   | 1 261   | 268     |
| Successor                         | 0       | 0       | 0       |

It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the '[Working with COU data' page in the AddressBase Core Getting Started Guide](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-getting-started-guide/working-with-cou-data).

## Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 113:

| Data Source                | Date           |
| -------------------------- | -------------- |
| Pointer (Northern Ireland) | 22 August 2024 |
| DigiMap (Channel Islands)  | 22 August 2024 |
| Isle of Man                | 21 August 2024 |
| Royal Mail PAF             | 22 August 2024 |

## Data issues

### AddressBase Plus Islands issues

There are no reported issues in this release of AddressBase Plus Islands.

### AddressBase Premium Islands issues

**Affected output formats: CSV and GML**

* **Street incorrect coordinates** – There are two Streets which have incorrect start or end coordinates of 000000. The unique identifiers can be provided upon request through your OS Relationship Manager.

## Next release

The next release of AddressBase Islands products, Epoch 114, is scheduled for **07 November 2024**.


# Future and past publication dates

AddressBase, AddressBase Plus, AddressBase Premium and AddressBase Islands are updated every six weeks. This six week period of time is known as an **epoch**.​

Our AddressBase products are currently available as a Full Supply or Change-Only Update (COU) for each epoch.​

{% hint style="info" %}
The information supplied here is replicated in full on the [Product Refresh Dates](https://docs.os.uk/os-downloads/resources/product-refresh-dates) page, alongside publication information for all of our other Premium and OpenData products.
{% endhint %}

## Future AddressBase epoch publication dates

Future dates are provided as an indication only and are subject to change. Data cut dates are estimates; these are given to provide an indication of the last point at which changes will reach the epoch. ​

{% hint style="info" %}
As we approach the publication date and prepare to release a new epoch, any new requests placed for data will be paused to ensure data integrity. These requests will be processed as soon as this pause is lifted.
{% endhint %}

| Epoch Number | Publication Date | Data Cut Date     |
| ------------ | ---------------- | ----------------- |
| 131          | 29 October 2026  | 25 September 2026 |
| 132          | 10 December 2026 | 06 November 2026  |
| 133          | 21 January 2027  | 18 December 2026  |

{% hint style="info" %}

* [AddressBase product 'family' release notes](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/release-notes) (for all AddressBase products bar AddressBase Core) are available from the AddressBase Core Principles pages of this site.
* AddressBase Core is a weekly supply and information is covered in a separate [AddressBase Core release note](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/release-notes).
  {% endhint %}

## Past AddressBase epoch publication dates

| Epoch Number | Publication Date  | Data Cut Date     |
| ------------ | ----------------- | ----------------- |
| 130          | 17 September 2026 | 14 August 2026    |
| 129          | 06 August 2026    | 03 July 2026      |
| 128          | 25 June 2026      | 22 May 2026       |
| 127          | 14 May 2026       | 10 April 2026     |
| 126          | 02 April 2026     | 27 February 2026  |
| 125          | 19 February 2026  | 16 January 2026   |
| 124          | 08 January 2026   | 05 December 2025  |
| 123          | 27 November 2025  | 24 October 2025   |
| 122          | 16 October 2025   | 12 September 2025 |
| 121          | 04 September 2025 | 08 August 2025    |
| 120          | 31 July 2025      | 20 June 2025      |
| 119          | 12 June 2025      | 09 May 2025       |
| 118          | 01 May 2025       | 28 March 2025     |
| 117          | 20 March 2025     | 14 February 2025  |
| 116          | 06 February 2025  | 03 January 2025   |
| 115          | 19 December 2024  | 14 November 2024  |


# Unique Property Reference Number (UPRN)

The Unique Property Reference Number (UPRN) is the persistent identifier providing consistency across the AddressBase products range.

Each address record has a UPRN, which provides a reference key to join related address records across different datasets.

Throughout its lifecycle, information on the address of a property can change. This may be due to a change of name, change of use, or the eventual demolition of the property. All these changes are reflected against the same UPRN, meaning that users are aware that it is the same physical property.

{% hint style="warning" %}
Please be aware that the UPRN is not the Primary Key for all tables within the [AddressBase Premium](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium) and [AddressBase Premium Islands](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium-islands) supply. Please see the relational models in [AddressBase Premium structure](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium/addressbase-premium-technical-specification/addressbase-premium-structure) and [AddressBase Premium Islands structure](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium-islands/addressbase-premium-islands-technical-specification/addressbase-premium-islands-structure) for more information.
{% endhint %}


# Coordinate reference systems

AddressBase products have two coordinate reference systems (CRS) present within the data:

* **British National Grid (BNG)**: BNG uses the OSGB36 geodetic datum and a single Transverse Mercator projection for the whole of Great Britain. Positions on this projection are described using Easting and Northing coordinates in units of metres. The BNG is a horizontal spatial reference system only; it does not specify a vertical (height) reference system.
* **European Terrestrial Reference System 89 (ETRS89)**: ETRS89 is the EU-recommended frame of reference for European data and is represented as Latitude and Longitude values. ETRS89 is a horizontal spatial reference system only; it does not specify a vertical (height) reference system.

View our [guide to coordinate systems in Great Britain](https://docs.os.uk/more-than-maps/deep-dive/a-guide-to-coordinate-systems-in-great-britain) for more information.


# Classification scheme

The AddressBase Classification Scheme provides varying levels of classification for addresses which are captured and maintained by the Local Authorities and Ordnance Survey. This allows searches to be limited on residential or commercial addresses or be more specific to find all the flats or all fast-food outlets. The varying levels of classification are as follows:

* Primary Level Classification\
  R: Residential\
  C: Commercial
  * Secondary Level Classification\
    RD: Residential Dwelling\
    CH: Hotel/Motel/ Boarding/ Guest House
    * Tertiary Level Classification\
      RD02: Detached House\
      CH01: Boarding/Guest House/ Bed And Breakfast/Youth Hostel
      * Quaternary Level\
        CH01YH: Youth Hostel

{% hint style="info" %}

* The AddressBase Classification Scheme is applicable to all of the AddressBase products
* The level of classification varies across all addressable objects and across the different AddressBase products. AddressBase provides primary level classification for addressable objects, AddressBase Core provides up to secondary level, while AddressBase Plus, AddressBase Plus Islands, AddressBase Premium and AddressBase Premium Islands provide up to tertiary / quaternary level.
* There are only certain classification codes that extend to the quaternary classification level as shown above.
  {% endhint %}

## Use of third party data in classifications

The AddressBase Classification Scheme incorporates selected third-party data sources to provide additional intelligence and contribute towards classification validation.

## AddressBase Classification Scheme download

The full AddressBase Classification Scheme is available in CSV (comma-separated values) and .xlsx formats for download in the following zip file:

{% file src="/files/c71UtRviZrwJf7IJuMvB" %}

{% hint style="info" %}
The AddressBase product classification scheme was last updated on **17 January 2025**
{% endhint %}


# Data sources

Through collaborative working between Ordnance Survey, GeoPlace, the Local Government Agency and Improvement Service, a single definitive spatial address database for Great Britain has been created and maintained since September 2011 for England and Wales, and April 2012 for Scotland.

This initiative supports the UK Location Strategy concept of a 'core reference geography', including the key principles of the European Union INSPIRE directive, that data should only be collected once and kept where it can be maintained most effectively.

## AddressBase Data Inputs <a href="#bookmark16" id="bookmark16"></a>

The creation of AddressBase products brings together the best parts of:

### Local Government’s National Land and Property Gazetteer (NLPG) <a href="#bookmark17" id="bookmark17"></a>

The National Land and Property Gazetteer (NLPG) provides the most up-to-date addresses, including street names and numbers from each Local Authority’s LLPG in England and Wales. This data also provides a Unique Property Reference Number (UPRN) for each address encompassing residential, commercial and public infrastructure such as fire stations.

### The One Scotland Address Gazetteer (OSG) <a href="#bookmark18" id="bookmark18"></a>

One Scotland Address Gazetteer (OSG) provides the most up-to-date addresses including street names and numbers from each Scottish Local Authority’s CAG. This data also provides a Unique Property Reference Number (UPRN) for each address encompassing residential, commercial and public infrastructure such as fire stations.

### Ordnance Survey owned large-scale data and coordinates <a href="#bookmark19" id="bookmark19"></a>

Ordnance Survey provides a wide range of additional addresses including Objects Without a Postal Address (OWPAs) such as Telephone Exchanges, a wider spatial context by including references for both the OS MasterMap Topography Layer and OS MasterMap Highways Networks Layer which the address feature is related to and additional classification information.

### Royal Mail Postcode Address File (PAF) <a href="#bookmark20" id="bookmark20"></a>

PAF contains approximately 30 million Royal Mail addresses that are identified as receiving post in Great Britain. Addresses from the NLPG and OSG are matched to the PAF addresses to provide the Unique Delivery Point Reference Number (UDPRN) into product and supplement the Local Authority address with information such as organisation name, postal town and postcode.

### Valuation Office Agency <a href="#bookmark21" id="bookmark21"></a>

The Valuation Office Agency (VOA) gives the government the valuations and property advice needed to support taxation and benefits within England and Wales. Addresses from the NLPG are matched to the VOA address to provide the Unique Address Reference Number (UARN), VOA Special Category and Primary Description classification codes in product.

## Roles and Responsibilities <a href="#bookmark22" id="bookmark22"></a>

### GeoPlace <a href="#bookmark23" id="bookmark23"></a>

GeoPlace is a limited liability partnership jointly owned by the Local Government Association and Ordnance Survey and is the centre of excellence for spatial address and street information in Great Britain. GeoPlace brings together local government's address and streets gazetteers with information from Ordnance Survey, Improvement Service, Royal Mail’s PAF dataset and VOA addresses into a central spatial address data hub. The database hub is updated by GeoPlace based upon the receipt of data from all the contributing data sources.

GeoPlace manage this hub and provide address and street information to be utilised in the AddressBase products.

<figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2F1kXzSGvp9rw10NEflsNJ%2F2.png?alt=media" alt="Diagram showing the relationship between GeoPlace, Ordnance Survey, LLPGs, Royal Mail, Scottish LGs" width="375"><figcaption><p>Diagram showing the relationship between GeoPlace, Ordnance Survey, LLPGs, Royal Mail and Scottish LGs.</p></figcaption></figure>

### England and Wales <a href="#bookmark24" id="bookmark24"></a>

At present, there are 314 local authorities in England and Wales, inputting updates to their Local Land and Property Gazetteers (LLPG). These changes are submitted to the GeoPlace Hub daily, weekly or monthly as part of their update schedule.

On receipt of these updates, they are checked to ensure that they have been produced in accordance with the NLPG Data Entry Conventions and they are in compliance with the national standard for the representation of address information – BS 7666 Parts 1 and 2.

### Scotland <a href="#bookmark25" id="bookmark25"></a>

There are currently 32 local authorities in Scotland which update their local address gazetteers on a daily, weekly or monthly as part of their update schedule to the OSG. The Improvement Service check each

update to ensure compliance with the national standard for addressing (BS7666.2006) and the Scottish Gazetteer Conventions 1-3.

### Local Authority Custodians <a href="#bookmark26" id="bookmark26"></a>

One of the key strengths of AddressBase products is the collection and verification of data at the local level. A real benefit is the capture of addresses at the earliest point in their lifecycle, and then this address being maintained by the local authority.

To do this the Local Custodians will utilise the wealth of information at their disposal until the address is demolished (when it becomes a historical record).

Local Custodians will use information such as:

* Building and Development control
* Planning and Land Charges
* Waste Collection
* Electoral Roll

LLPG custodians (England and Wales) are allocated sequential batches of UPRNs by GeoPlace, which are assigned by the LLPG custodian at the creation of a new address.

The OSG (Scotland) custodians are allocated sequential batches of UPRNs by the Improvement Service, which are assigned by the OSG custodian at the creation of a new address.


# Street names and numbering

A critical step in the creation of an address is undertaken within each Local Authority by the dedicated Street Name and Numbering (SNN) custodian and the Scottish Local Street Gazetteer (LSG) custodians, who allocates the official street name and building information.

The SNN/LSG custodian has a statutory obligation to provide SNN/LSG information for all addresses within their administrative area. Once the SNN/LSG custodian has fulfilled their statutory obligation for initial capture, the LLPG/OSG custodian will maintain the address for the life of the address record.

The official street name and building information for new properties captured by the SNN/LSG custodians is provided to Royal Mail who then allocate a postcode to the address.


# Currency, completeness and precision

## Currency <a href="#bookmark28" id="bookmark28"></a>

Updates are continuously made to the central spatial address data hub, which is managed by GeoPlace. These are used to produce the AddressBase Core product, which is supplied on a weekly basis. An extract is taken for the creation of AddressBase, AddressBase Plus and AddressBase Premium on a 6-weekly basis.

## Completeness <a href="#bookmark29" id="bookmark29"></a>

Quality control procedures are undertaken at all stages of production to ensure that the data is as accurate and complete as possible and conforms to the specification. These quality control checks include automated data testing against the product specification and visual checks by operators.

## Precision <a href="#bookmark30" id="bookmark30"></a>

Coordinates for all addressable objects with each AddressBase product are published with geometry given to a precision of up to two decimal places for British National Grid coordinates, and up to seven decimal places for ETRS89 coordinates.


# Product supply

## Available supply formats <a href="#bookmark32" id="bookmark32"></a>

All four of the AddressBase products are available as Comma-Separated Value (CSV) files. AddressBase, AddressBase Plus and AddressBase Premium are also available as Geography Markup Language (GML). AddressBase Core is also available as a GeoPackage.

### Comma-Separated Values (CSV) <a href="#bookmark33" id="bookmark33"></a>

Comma-separated value (CSV) files are a delimited text file that use commas or other characters to separate individual elements of a feature. It is used to store data, often in the form of a table. These tables can be freely loaded into databases and programs allowing for the easy loading and updating of data holdings.

The supply of AddressBase products in the CSV format means:

* There will be one record per line in each file.
* Fields will be separated by commas.
* Character strings will be encapsulated with double quotation marks.
* No comma will be placed at the end of each row in the file.
* Records will be terminated by Carriage Return / Line Feed.

For AddressBase Core, the first line of the CSV file will be the Header row. Other AddressBase products have a separate Header file that is available on the product's Downloads page; this Header file can be combined with the data to give a structure tabular view. Instructions to do this are provided in each product's Getting Started Guide.

### Geography Markup Language (GML) version 3.2 <a href="#bookmark34" id="bookmark34"></a>

The Geography Markup Language (GML) Encoding standard is an Extensible Markup Language (XML) grammar for expressing geographical features. XML schemas are used to define and validate the format and content of GML. The XML specifications that GML is based on are available from the World Wide Web Consortium (W3C) website: [http://www.w3.org.](http://www.w3.org/) More information can be found in the Open Geospatial Consortium (OGC) document, Geography Markup Language v3.2.1.

The GML 3.2 specification provides a set of schemas that define the GML feature constructs and geometric types. These are designed to be used as a basis for building application-specific schemas, which define the data content.

More information on the XML schemas can be found in the product technical specification.

### GeoPackage <a href="#bookmark35" id="bookmark35"></a>

GeoPackage (GPKG) is an open, standards-based data format as defined by the Open Geospatial Consortium (OGC). It is designed to be a lightweight format that can contain large amounts of varied and complex data in a single, easy-to-distribute and ready-to-use file. Please be advised that older versions of GIS software may need updating before being able to display and interact with GeoPackage files.

GeoPackage offers the following benefits:

* The single file is easy to transfer and offers the end-user a rich experience.
* Attribute names are not limited in length making it user-friendly.
* No file size limit so lots of data can be easily accommodated.
* Supports raster, vector and database formats making it a highly versatile solution.
* It is an OGC Standard.
* In most cases, it is a Plug and Play format.

## Supply media and file structure <a href="#bookmark36" id="bookmark36"></a>

AddressBase products incorporate a web-based ordering system that allows customers to order initial data supply and updates, obtain price estimates and view details of their data holdings on demand.

<https://www.ordnancesurvey.co.uk/business-government/tools-support/orders> AddressBase products can be ordered via DVD or Secure File Transfer Protocol (SFTP).

AddressBase Core is provided as a single file which will contain all records regardless of format and supply option: full supply or COU.

The AddressBase, AddressBase Plus and AddressBase Premium products have been split into chunks of smaller data. The primary supply mechanism is referred to as non-geographic chunks. This is the main mechanism for the delivery of data.

Public Sector Geospatial Agreement (PSGA) customers are able to order all AddressBase products via geographic chunks (5km tiles). Address records are provided in individual files, which represent each 5km tile ordered.

### Non-geographic chunking <a href="#bookmark37" id="bookmark37"></a>

Non-geographic chunking is a way of dividing up data into chunks that are supplied in separate volumes that have a fixed maximum number of records, as opposed to a given geographic National Grid area. For this reason, it is possible for features from various geographic locations to appear in one volume and for adjacent features to appear in different volumes.

Non-geographic chunk volumes are designed to be loaded into spatial databases, but can be used in a file format as long as all chunks are translated or imported into the system at the same time.

CSV files can supply a maximum of one million complete address records within one volume, when this limit is reached, a new volume will be started.

For the GML supply a maximum of 200 000 features will be provided in one volume before the next one is started.

### Geographic chunking <a href="#bookmark38" id="bookmark38"></a>

For data that is supplied in 5km-by-5km chunks, the file name will reference the 1km tile in the south-west corner of the 5km tile.

Based on your area of interest (AOI), for example the boundary of your local authority, a 5km-by-5km grid covering the area of interest is generated.

All features within each 5km grid that intersects the AOI are added to a geographic chunk file. Geographic chunking is performed using the standard Ordnance Survey National Grid.

## Coverage <a href="#bookmark39" id="bookmark39"></a>

AddressBase products provide address data for England, Wales and Scotland.

### National sets <a href="#bookmark40" id="bookmark40"></a>

A national set of AddressBase, known as a Managed GB Set (MGBS) service is a way of processing identical orders faster, which improves delivery times. All records within England, Wales and Scotland will be provided. If you are signed up to an MGBS service you will benefit from:

* Data arriving faster and in a more predictable manner.
* Seeing the same version of features as other organisations.
* Easier data management – no need to manage your order beyond signing up.

For Public Sector Geospatial Agreement (PSGA) customers, MGBS will be supplied as geographic or non-geographic chunks. For non-PSGA users, MGBS will be supplied as non-geographic chunks.

### Customer defined areas of interest <a href="#bookmark41" id="bookmark41"></a>

Customers may provide their own area of interest (AOI) in any standard GIS format.

You can supply us with a polygon or you can digitise a polygon within our online ordering service.

## Product updates <a href="#bookmark42" id="bookmark42"></a>

Customers are able to take a full supply for all AddressBase products. An easier way to manage the addressing data which each product release is to take change-only updates (COU)

### Full Supply <a href="#bookmark43" id="bookmark43"></a>

A Full Supply is a resupply of all addressable features in each product each time it is released. This may require you to delete to current holding and replace this with the newly supplied product on each product refresh.

AddressBase Core in GeoPackage format is only available as a Full Supply each week.

### COU <a href="#bookmark44" id="bookmark44"></a>

Change-only update (COU) is a supply of features which have been created, changed or deleted in a customer’s area of interest since their last supply.

Any feature which has not undergone one of the above changes since a customer’s last supply will not be supplied as part of a COU.

COU will be supplied on a weekly basis for AddressBase Core CSV or a six-weekly basis for AddressBase, AddressBase Plus and AddressBase Premium.

A Geographic chunked COU is not supplied as per the Non-Geographic chunked COU outlined above. For a specified 5km tile, all features within the tile will be supplied should any of the individual features change.

This means the user will need to remove all features that previously existed in the provided tile(s) and insert the entire new tile(s) in its place.


# Code lists and enumerations

A code list is a controlled set of allowable labels or codes represented as an alphanumeric attribute. The sub-pages in this section show the code lists used within the AddressBase 'family' of products. Some of the code lists apply to attributes of multiple feature types, whereas others will only apply to attributes of one feature type.


# AddressbasePostalCode

This code list is used in association with the attribute addressbasePostalCode/ADDRESSBASE\_POSTAL\_CODE found on the BLPU table. The code list describes the record as postal or not as defined by Addressbase logic.

<table><thead><tr><th width="179">Value</th><th>Description</th></tr></thead><tbody><tr><td>D</td><td>A record which is linked to PAF</td></tr><tr><td>N</td><td>Not a postal address</td></tr><tr><td>C</td><td>A record which is postal and has a parent record which is linked to PAF</td></tr><tr><td>L</td><td>A record which is identified as postal based on Local Authority information</td></tr></tbody></table>


# BLPUStateCode

This enumeration is used in association with the attribute blpuState/BLPU\_STATE. This enumeration describes the physical nature of the address record.

<table><thead><tr><th width="280">Value</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td>under construction</td></tr><tr><td>2</td><td>In use</td></tr><tr><td>3</td><td>Unoccupied /vacant/derelict</td></tr><tr><td>4</td><td>No longer existing</td></tr><tr><td>6</td><td>Planning permission granted</td></tr></tbody></table>


# ChangeTypeCode

This enumeration is used in association with the attribute ChangeType/CHANGE\_TYPE. This enumeration identifies the type of change that has been made to a feature.

| Value | Description |
| ----- | ----------- |
| I     | Insert      |
| U     | Update      |
| D     | Delete      |


# CountryCode

This code list is used in association with the attribute country/COUNTRY found on the BLPU table. The code list describes within which country the address feature falls within.

<table><thead><tr><th width="150">Value</th><th>Description</th></tr></thead><tbody><tr><td>E</td><td>This record is within England</td></tr><tr><td>W</td><td>This record is within Wales</td></tr><tr><td>S</td><td>This record is within Scotland</td></tr><tr><td>N</td><td>This record is within Northern Ireland</td></tr><tr><td>L</td><td>This record is within the Channel Islands</td></tr><tr><td>M</td><td>This record is within the Isle of Man</td></tr><tr><td>J</td><td>This record is not assigned to a country as it falls outside of the land boundaries used.</td></tr></tbody></table>


# Date

There are many Date columns within the AddressBase product. Where a type format of Date has been used in the above attribute tables, the data will be defined in the following format.

<table><thead><tr><th>Value</th><th width="114">Type</th><th>Notes</th></tr></thead><tbody><tr><td>2024-10-24</td><td>Date</td><td>Date columns will follow the structure: CCYY-MM-DD</td></tr></tbody></table>


# FileTypeCode

This enumeration is used in association with the attribute fileType/FILE\_TYPE found in the Header record. This enumeration allows the identification of either a change-only update (COU) supply or a full supply.

<table><thead><tr><th width="252">Value</th><th>Description</th></tr></thead><tbody><tr><td>F</td><td>Signifies the supply is a full supply</td></tr><tr><td>C</td><td>Signifies the supply is a COU file</td></tr></tbody></table>


# LanguageCode

This enumeration is used in association with the LANGUAGE attribute found in the Street Descriptor and LPI tables; and also the Metadata table for CSV supply. This enumeration identifies the language of the address displayed.

{% hint style="info" %}
This is not required for the GML supply as the Language is specified in the GML tag ‘xml:lang’.
{% endhint %}

| Value | Description       |
| ----- | ----------------- |
| ENG   | English           |
| CYM   | Welsh             |
| GAE   | Gaelic (Scottish) |
| BIL   | Bilingual         |


# LogicalStatusCode

This enumeration is used in association with the logicalStatus/LOGICAL\_STATUS attribute found in the BLPU and LPI table. This enumeration provides a value to show the lifecycle stage of the address record.

| Value | Description |
| ----- | ----------- |
| 1     | Approved    |
| 3     | Alternative |
| 6     | Provisional |
| 8     | Historical  |

{% hint style="info" %}
BLPU records will not have a logical status value of 3, whereas LPI records can have all of the values expressed above.
{% endhint %}


# OfficialFlagCode

This enumeration is used in association with the officialFlag/OFFICIAL\_FLAG attribute. This enumeration is an indicator of whether an address record corresponds to an entry in the official Street Name and Numbering register.

| Value | Description        |
| ----- | ------------------ |
| N     | Unofficial Address |
| Y     | Official Address   |


# PostcodeTypeCode

This enumeration is used in association with the postcodeType/POSTCODE\_TYPE attribute. This enumeration identifies the code used by Royal Mail to describe the user as a small or large user. This is defined for postal services based on the number of letters delivered to that user.

<table><thead><tr><th width="177">Value</th><th>Description</th></tr></thead><tbody><tr><td>S</td><td>A small user, for example, a residential property</td></tr><tr><td>L</td><td>A large user, for example, a large commercial company</td></tr></tbody></table>


# RPCCode

This enumeration is used in association with the rpc/RPC attribute. This enumeration identifies the accuracy value of the coordinates allocated to the address.

<table><thead><tr><th width="101">Value</th><th width="145">Description</th><th>Implementation notes</th></tr></thead><tbody><tr><td>1</td><td>Central Internal Position</td><td><p>The address seed is <strong>contained within</strong> an OS MasterMap Topography Layer <strong>building</strong> and <strong>within 2.5m of its calculated centre</strong>.</p><p><em>Or</em></p><p>The seed is in the best possible position based on the nature of the premises, for example, Development Land, House Boat, Wind Farm.</p></td></tr><tr><td>2</td><td>General Internal Position</td><td><p>The address seed is <strong>contained within</strong> an OS MasterMap Topography Layer <strong>building</strong> but is more than 2.5m away from its calculated centre.</p><p><em>Or</em></p><p>The seed is in an internal position based on the nature of the premises, for example, Development Land, House Boat.</p></td></tr><tr><td>3</td><td>Transitional Position</td><td><p>The address seed has been <strong>changed from provisional to live in the last six months</strong>. It has been captured to a high level of positional accuracy, but the <strong>OS MasterMap Topography Layer feature is not yet captured</strong>.</p><p><em>Please note the address seed will only be moved pending any imminent mapping updates.</em></p></td></tr><tr><td>4</td><td>Street Location</td><td><p>The <strong>address seed is plotted in accordance with the declared street</strong> start or end coordinates.</p><p><em>Please note this is the highest accuracy possible for Street Records.</em></p></td></tr><tr><td>5</td><td>Postcode Unit Position</td><td>The address seed has been <strong>captured to Postcode Unit level</strong>. It will be updated when more information becomes available.</td></tr><tr><td>9</td><td>Low accuracy – marked for priority review</td><td>This address seed has been captured to a <strong>lower level of accuracy and will be updated as a priority</strong> over the coming releases.</td></tr></tbody></table>


# StateCode

This enumeration is used in association with the stateCode/STATE\_CODE attribute. This enumeration describes the physical nature of the address record.

| Value | Description                    |
| ----- | ------------------------------ |
| 1     | Under construction             |
| 2     | In use                         |
| 3     | Unoccupied / vacant / derelict |
| 4     | No longer existing             |
| 6     | Planning permission granted    |


# StreetClassificationCode

This enumeration is used in association with the \_s\_treetClassification/STREET\_CLASSIFICATION attribute found in the Street table. The enumeration provides a value denoting the primary classification of the street record.

| Value | Description                |
| ----- | -------------------------- |
| 4     | Pedestrian way or footpath |
| 6     | Cycletrack or cycleway     |
| 8     | All vehicles               |
| 9     | Restricted byway           |
| 10    | Bridleway                  |


# StreetRecordTypeCode

This enumeration is used in association with the recordType/RECORD\_TYPE attribute found in the Street table. This enumeration identifies the record type of the street record.

| Value | Description                      |
| ----- | -------------------------------- |
| 1     | Official designated Street Name  |
| 2     | Street Description               |
| 3     | Numbered Street                  |
| 4     | Unofficial Street Description    |
| 9     | Description used for LLPG Access |


# StreetStateCode

This enumeration is used in association with the state/STATE attribute found in the street table. This enumeration identifies at which point the street record is within its lifecycle.

<table><thead><tr><th width="222">Value</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td>Under construction</td></tr><tr><td>2</td><td>Open</td></tr><tr><td>4</td><td>Permanently closed (STREET_END_DATE must be entered)</td></tr></tbody></table>


# StreetSurfaceCode

This enumeration is used in association with the streetSurface/STREET\_SURFACE attribute found in the Street table. This enumeration identifies the surface finish of the street.

| Value | Description |
| ----- | ----------- |
| 1     | Metalled    |
| 2     | UnMetalled  |
| 3     | Mixed       |


# Time

There are columns within the AddressBase product which provide a Time value. Where this is declared, the data will be provided in the following format.

| Value    | Type | Notes                                                                |
| -------- | ---- | -------------------------------------------------------------------- |
| 14:11:15 | Time | Time will follow the structure of HH:MM:SS based on a 24-hour clock. |


# USRNMatchIndicatorCode

This enumeration is used in association with the usrnMatchIndicator/USRN\_MATCH\_INDICATOR attribute found in the LPI table. This enumeration identifies how the USRN has been allocated to an address record.

<table><thead><tr><th width="164">Value</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td>Matched manually to the nearest accessible Street.</td></tr><tr><td>2</td><td>Matched spatially to the nearest USRN. Not necessarily the access street.</td></tr></tbody></table>


# AddressBase local custodian codes

The following page details the current local custodian codes of all local custodians contributing to the AddressBase, AddressBase Core, AddressBase Plus and AddressBase Premium products.

{% hint style="info" %}
The local custodian codes listed in the zip file and table below are applicable to the AddressBase, AddressBase Core, AddressBase Plus and AddressBase Premium products.

They are not applicable to the AddressBase Plus Islands or AddressBase Premium Islands products; local custodian codes for these two islands products are available from the [AddressBase Islands local custodian codes page](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/addressbase-islands-local-custodian-codes).

Local custodian codes available on this page were last updated on **10 March 2026**
{% endhint %}

## Local custodian codes download

Local custodian code data is available to download in CSV format in the following zip file:

{% file src="/files/7SMWthYf95pM0uyd875E" %}

## Local custodian codes table

<table><thead><tr><th width="123">Local Custodian Code</th><th width="220">Local Custodian Name</th><th width="161">Local Custodian Type</th><th width="105">Submits Address data</th><th width="123">Submits Street data</th></tr></thead><tbody><tr><td>114</td><td>BATH AND NORTH EAST SOMERSET</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>116</td><td>BRISTOL</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>119</td><td>SOUTH GLOUCESTERSHIRE</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>121</td><td>NORTH SOMERSET</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>230</td><td>LUTON</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>235</td><td>BEDFORD</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>240</td><td>CENTRAL BEDFORDSHIRE</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>335</td><td>BRACKNELL FOREST</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>340</td><td>WEST BERKSHIRE</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>345</td><td>READING</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>350</td><td>SLOUGH</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>355</td><td>WINDSOR AND MAIDENHEAD</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>360</td><td>WOKINGHAM</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>435</td><td>MILTON KEYNES</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>440</td><td>BUCKINGHAMSHIRE</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>505</td><td>CAMBRIDGE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>510</td><td>EAST CAMBRIDGESHIRE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>515</td><td>FENLAND</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>520</td><td>HUNTINGDONSHIRE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>530</td><td>SOUTH CAMBRIDGESHIRE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>535</td><td>CAMBRIDGESHIRE</td><td>English County</td><td>N</td><td>Y</td></tr><tr><td>540</td><td>PETERBOROUGH</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>650</td><td>HALTON</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>655</td><td>WARRINGTON</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>660</td><td>CHESHIRE EAST</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>665</td><td>CHESHIRE WEST AND CHESTER</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>724</td><td>HARTLEPOOL</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>728</td><td>REDCAR AND CLEVELAND</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>734</td><td>MIDDLESBROUGH</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>738</td><td>STOCKTON-ON-TEES</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>835</td><td>ISLES OF SCILLY</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>840</td><td>CORNWALL</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>935</td><td>WESTMORLAND AND FURNESS</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>940</td><td>CUMBERLAND</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>1005</td><td>AMBER VALLEY</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1010</td><td>BOLSOVER</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1015</td><td>CHESTERFIELD</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1025</td><td>EREWASH</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1030</td><td>HIGH PEAK</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1035</td><td>NORTH EAST DERBYSHIRE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1040</td><td>SOUTH DERBYSHIRE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1045</td><td>DERBYSHIRE DALES</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1050</td><td>DERBYSHIRE</td><td>English County</td><td>N</td><td>Y</td></tr><tr><td>1055</td><td>DERBY</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>1105</td><td>EAST DEVON</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1110</td><td>EXETER</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1115</td><td>NORTH DEVON</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1125</td><td>SOUTH HAMS</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1130</td><td>TEIGNBRIDGE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1135</td><td>MID DEVON</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1145</td><td>TORRIDGE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1150</td><td>WEST DEVON</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1155</td><td>DEVON</td><td>English County</td><td>N</td><td>Y</td></tr><tr><td>1160</td><td>PLYMOUTH</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>1165</td><td>TORBAY</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>1260</td><td>BOURNEMOUTH, CHRISTCHURCH AND POOLE</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>1265</td><td>DORSET</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>1350</td><td>DARLINGTON</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>1355</td><td>DURHAM</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>1410</td><td>EASTBOURNE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1415</td><td>HASTINGS</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1425</td><td>LEWES</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1430</td><td>ROTHER</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1435</td><td>WEALDEN</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1440</td><td>EAST SUSSEX</td><td>English County</td><td>N</td><td>Y</td></tr><tr><td>1445</td><td>BRIGHTON &#x26; HOVE</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>1505</td><td>BASILDON</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1510</td><td>BRAINTREE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1515</td><td>BRENTWOOD</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1520</td><td>CASTLE POINT</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1525</td><td>CHELMSFORD</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1530</td><td>COLCHESTER</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1535</td><td>EPPING FOREST</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1540</td><td>HARLOW</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1545</td><td>MALDON</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1550</td><td>ROCHFORD</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1560</td><td>TENDRING</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1570</td><td>UTTLESFORD</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1585</td><td>ESSEX COUNTY</td><td>English County</td><td>N</td><td>Y</td></tr><tr><td>1590</td><td>SOUTHEND-ON-SEA</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>1595</td><td>THURROCK</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>1600</td><td>GLOUCESTERSHIRE</td><td>English County</td><td>N</td><td>Y</td></tr><tr><td>1605</td><td>CHELTENHAM</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1610</td><td>COTSWOLD</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1615</td><td>FOREST OF DEAN</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1620</td><td>GLOUCESTER</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1625</td><td>STROUD</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1630</td><td>TEWKESBURY</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1705</td><td>BASINGSTOKE AND DEANE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1710</td><td>EAST HAMPSHIRE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1715</td><td>EASTLEIGH</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1720</td><td>FAREHAM</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1725</td><td>GOSPORT</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1730</td><td>HART</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1735</td><td>HAVANT</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1740</td><td>NEW FOREST</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1750</td><td>RUSHMOOR</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1760</td><td>TEST VALLEY</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1765</td><td>WINCHESTER</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1770</td><td>HAMPSHIRE</td><td>English County</td><td>N</td><td>Y</td></tr><tr><td>1775</td><td>PORTSMOUTH CITY COUNCIL</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>1780</td><td>SOUTHAMPTON</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>1805</td><td>BROMSGROVE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1820</td><td>MALVERN HILLS</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1825</td><td>REDDITCH</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1835</td><td>WORCESTER</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1840</td><td>WYCHAVON</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1845</td><td>WYRE FOREST</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1850</td><td>HEREFORDSHIRE</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>1855</td><td>WORCESTERSHIRE</td><td>English County</td><td>N</td><td>Y</td></tr><tr><td>1900</td><td>HERTFORDSHIRE</td><td>English County</td><td>N</td><td>Y</td></tr><tr><td>1905</td><td>BROXBOURNE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1910</td><td>DACORUM</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1915</td><td>EAST HERTFORDSHIRE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1920</td><td>HERTSMERE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1925</td><td>NORTH HERTFORDSHIRE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1930</td><td>ST ALBANS</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1935</td><td>STEVENAGE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1940</td><td>THREE RIVERS</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1945</td><td>WATFORD</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>1950</td><td>WELWYN HATFIELD</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2001</td><td>EAST RIDING OF YORKSHIRE</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>2002</td><td>NORTH EAST LINCOLNSHIRE</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>2003</td><td>NORTH LINCOLNSHIRE</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>2004</td><td>HULL</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>2114</td><td>ISLE OF WIGHT</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>2205</td><td>ASHFORD</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2210</td><td>CANTERBURY</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2215</td><td>DARTFORD</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2220</td><td>DOVER</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2230</td><td>GRAVESHAM</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2235</td><td>MAIDSTONE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2245</td><td>SEVENOAKS</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2250</td><td>FOLKESTONE &#x26; HYTHE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2255</td><td>SWALE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2260</td><td>THANET</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2265</td><td>TONBRIDGE &#x26; MALLING</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2270</td><td>TUNBRIDGE WELLS</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2275</td><td>KENT</td><td>English County</td><td>N</td><td>Y</td></tr><tr><td>2280</td><td>MEDWAY</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>2315</td><td>BURNLEY</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2320</td><td>CHORLEY</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2325</td><td>FYLDE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2330</td><td>HYNDBURN</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2335</td><td>LANCASTER CITY</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2340</td><td>PENDLE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2345</td><td>PRESTON</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2350</td><td>RIBBLE VALLEY</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2355</td><td>ROSSENDALE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2360</td><td>SOUTH RIBBLE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2365</td><td>WEST LANCASHIRE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2370</td><td>WYRE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2371</td><td>LANCASHIRE</td><td>English County</td><td>N</td><td>Y</td></tr><tr><td>2372</td><td>BLACKBURN WITH DARWEN</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>2373</td><td>BLACKPOOL</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>2405</td><td>BLABY</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2410</td><td>CHARNWOOD</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2415</td><td>HARBOROUGH</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2420</td><td>HINCKLEY &#x26; BOSWORTH</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2430</td><td>MELTON</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2435</td><td>NORTH WEST LEICESTERSHIRE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2440</td><td>OADBY AND WIGSTON</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2460</td><td>LEICESTERSHIRE COUNTY</td><td>English County</td><td>N</td><td>Y</td></tr><tr><td>2465</td><td>LEICESTER CITY</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>2470</td><td>RUTLAND</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>2500</td><td>LINCOLNSHIRE</td><td>English County</td><td>N</td><td>Y</td></tr><tr><td>2505</td><td>BOSTON</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2510</td><td>EAST LINDSEY</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2515</td><td>LINCOLN</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2520</td><td>NORTH KESTEVEN</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2525</td><td>SOUTH HOLLAND</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2530</td><td>SOUTH KESTEVEN</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2535</td><td>WEST LINDSEY</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2600</td><td>NORFOLK COUNTY</td><td>English County</td><td>N</td><td>Y</td></tr><tr><td>2605</td><td>BRECKLAND</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2610</td><td>BROADLAND</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2615</td><td>GREAT YARMOUTH</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2620</td><td>NORTH NORFOLK</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2625</td><td>NORWICH</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2630</td><td>SOUTH NORFOLK</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2635</td><td>KINGS LYNN AND WEST NORFOLK</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>2741</td><td>CITY OF YORK</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>2745</td><td>NORTH YORKSHIRE</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>2840</td><td>NORTH NORTHAMPTONSHIRE</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>2845</td><td>WEST NORTHAMPTONSHIRE</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>2935</td><td>NORTHUMBERLAND</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>3005</td><td>ASHFIELD</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3010</td><td>BASSETLAW</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3015</td><td>BROXTOWE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3020</td><td>GEDLING</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3025</td><td>MANSFIELD</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3030</td><td>NEWARK &#x26; SHERWOOD</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3040</td><td>RUSHCLIFFE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3055</td><td>NOTTINGHAMSHIRE</td><td>English County</td><td>N</td><td>Y</td></tr><tr><td>3060</td><td>NOTTINGHAM</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>3100</td><td>OXFORDSHIRE</td><td>English County</td><td>N</td><td>Y</td></tr><tr><td>3105</td><td>CHERWELL</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3110</td><td>OXFORD</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3115</td><td>SOUTH OXFORDSHIRE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3120</td><td>VALE OF WHITE HORSE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3125</td><td>WEST OXFORDSHIRE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3240</td><td>TELFORD &#x26; WREKIN</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>3245</td><td>SHROPSHIRE</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>3300</td><td>SOMERSET</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>3405</td><td>CANNOCK CHASE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3410</td><td>EAST STAFFORDSHIRE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3415</td><td>LICHFIELD</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3420</td><td>NEWCASTLE-UNDER-LYME</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3425</td><td>STAFFORD</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3430</td><td>SOUTH STAFFORDSHIRE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3435</td><td>STAFFORDSHIRE MOORLANDS</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3445</td><td>TAMWORTH</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3450</td><td>STAFFORDSHIRE COUNTY</td><td>English County</td><td>N</td><td>Y</td></tr><tr><td>3455</td><td>STOKE-ON-TRENT</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>3500</td><td>SUFFOLK COUNTY</td><td>English County</td><td>N</td><td>Y</td></tr><tr><td>3505</td><td>BABERGH</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3515</td><td>IPSWICH</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3520</td><td>MID SUFFOLK</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3540</td><td>EAST SUFFOLK</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3545</td><td>WEST SUFFOLK</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3600</td><td>SURREY COUNTY</td><td>English County</td><td>N</td><td>Y</td></tr><tr><td>3605</td><td>ELMBRIDGE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3610</td><td>EPSOM AND EWELL</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3615</td><td>GUILDFORD</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3620</td><td>MOLE VALLEY</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3625</td><td>REIGATE AND BANSTEAD</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3630</td><td>RUNNYMEDE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3635</td><td>SPELTHORNE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3640</td><td>SURREY HEATH</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3645</td><td>TANDRIDGE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3650</td><td>WAVERLEY</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3655</td><td>WOKING</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3700</td><td>WARWICKSHIRE</td><td>English County</td><td>N</td><td>Y</td></tr><tr><td>3705</td><td>NORTH WARWICKSHIRE</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3710</td><td>NUNEATON AND BEDWORTH</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3715</td><td>RUGBY</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3720</td><td>STRATFORD-ON-AVON</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3725</td><td>WARWICK</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3800</td><td>WEST SUSSEX</td><td>English County</td><td>N</td><td>Y</td></tr><tr><td>3805</td><td>ADUR</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3810</td><td>ARUN</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3815</td><td>CHICHESTER</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3820</td><td>CRAWLEY</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3825</td><td>HORSHAM</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3830</td><td>MID SUSSEX</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3835</td><td>WORTHING</td><td>English Shire District</td><td>Y</td><td>N</td></tr><tr><td>3935</td><td>SWINDON</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>3940</td><td>WILTSHIRE</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4205</td><td>BOLTON</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4210</td><td>BURY</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4215</td><td>MANCHESTER</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4220</td><td>OLDHAM</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4225</td><td>ROCHDALE</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4230</td><td>SALFORD</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4235</td><td>STOCKPORT</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4240</td><td>TAMESIDE</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4245</td><td>TRAFFORD</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4250</td><td>WIGAN</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4305</td><td>KNOWSLEY</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4310</td><td>LIVERPOOL</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4315</td><td>ST. HELENS COUNCIL</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4320</td><td>SEFTON COUNCIL</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4325</td><td>WIRRAL</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4405</td><td>BARNSLEY</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4410</td><td>DONCASTER</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4415</td><td>ROTHERHAM</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4420</td><td>SHEFFIELD</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4505</td><td>GATESHEAD</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4510</td><td>NEWCASTLE UPON TYNE</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4515</td><td>NORTH TYNESIDE</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4520</td><td>SOUTH TYNESIDE</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4525</td><td>SUNDERLAND</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4605</td><td>BIRMINGHAM</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4610</td><td>COVENTRY</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4615</td><td>DUDLEY</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4620</td><td>SANDWELL</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4625</td><td>SOLIHULL</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4630</td><td>WALSALL</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4635</td><td>WOLVERHAMPTON</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4705</td><td>BRADFORD</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4710</td><td>CALDERDALE</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4715</td><td>KIRKLEES</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4720</td><td>LEEDS</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>4725</td><td>WAKEFIELD</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5030</td><td>CITY OF LONDON</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5060</td><td>BARKING AND DAGENHAM</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5090</td><td>BARNET</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5120</td><td>BEXLEY</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5150</td><td>BRENT</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5180</td><td>BROMLEY</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5210</td><td>CAMDEN</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5240</td><td>CROYDON</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5270</td><td>EALING</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5300</td><td>ENFIELD</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5330</td><td>GREENWICH</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5360</td><td>HACKNEY</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5390</td><td>HAMMERSMITH &#x26; FULHAM</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5420</td><td>LONDON BOROUGH OF HARINGEY</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5450</td><td>HARROW</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5480</td><td>HAVERING</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5510</td><td>HILLINGDON</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5540</td><td>LONDON BOROUGH OF HOUNSLOW</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5570</td><td>ISLINGTON</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5600</td><td>KENSINGTON AND CHELSEA</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5630</td><td>KINGSTON UPON THAMES</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5660</td><td>LAMBETH</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5690</td><td>LEWISHAM</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5720</td><td>MERTON</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5750</td><td>NEWHAM</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5780</td><td>REDBRIDGE</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5810</td><td>RICHMOND UPON THAMES</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5840</td><td>SOUTHWARK</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5870</td><td>SUTTON</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5900</td><td>TOWER HAMLETS</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5930</td><td>WALTHAM FOREST</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5960</td><td>WANDSWORTH</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>5990</td><td>CITY OF WESTMINSTER</td><td>English Unitary</td><td>Y</td><td>Y</td></tr><tr><td>6805</td><td>ISLE OF ANGLESEY</td><td>Welsh Unitary</td><td>Y</td><td>Y</td></tr><tr><td>6810</td><td>GWYNEDD</td><td>Welsh Unitary</td><td>Y</td><td>Y</td></tr><tr><td>6815</td><td>CARDIFF</td><td>Welsh Unitary</td><td>Y</td><td>Y</td></tr><tr><td>6820</td><td>CEREDIGION</td><td>Welsh Unitary</td><td>Y</td><td>Y</td></tr><tr><td>6825</td><td>CARMARTHENSHIRE</td><td>Welsh Unitary</td><td>Y</td><td>Y</td></tr><tr><td>6830</td><td>DENBIGHSHIRE</td><td>Welsh Unitary</td><td>Y</td><td>Y</td></tr><tr><td>6835</td><td>FLINTSHIRE</td><td>Welsh Unitary</td><td>Y</td><td>Y</td></tr><tr><td>6840</td><td>MONMOUTHSHIRE</td><td>Welsh Unitary</td><td>Y</td><td>Y</td></tr><tr><td>6845</td><td>PEMBROKESHIRE</td><td>Welsh Unitary</td><td>Y</td><td>Y</td></tr><tr><td>6850</td><td>POWYS</td><td>Welsh Unitary</td><td>Y</td><td>Y</td></tr><tr><td>6855</td><td>SWANSEA</td><td>Welsh Unitary</td><td>Y</td><td>Y</td></tr><tr><td>6905</td><td>CONWY</td><td>Welsh Unitary</td><td>Y</td><td>Y</td></tr><tr><td>6910</td><td>BLAENAU GWENT</td><td>Welsh Unitary</td><td>Y</td><td>Y</td></tr><tr><td>6915</td><td>BRIDGEND</td><td>Welsh Unitary</td><td>Y</td><td>Y</td></tr><tr><td>6920</td><td>CAERPHILLY</td><td>Welsh Unitary</td><td>Y</td><td>Y</td></tr><tr><td>6925</td><td>MERTHYR TYDFIL</td><td>Welsh Unitary</td><td>Y</td><td>Y</td></tr><tr><td>6930</td><td>NEATH PORT TALBOT</td><td>Welsh Unitary</td><td>Y</td><td>Y</td></tr><tr><td>6935</td><td>NEWPORT</td><td>Welsh Unitary</td><td>Y</td><td>Y</td></tr><tr><td>6940</td><td>RHONDDA CYNON TAF</td><td>Welsh Unitary</td><td>Y</td><td>Y</td></tr><tr><td>6945</td><td>TORFAEN</td><td>Welsh Unitary</td><td>Y</td><td>Y</td></tr><tr><td>6950</td><td>VALE OF GLAMORGAN</td><td>Welsh Unitary</td><td>Y</td><td>Y</td></tr><tr><td>6955</td><td>WREXHAM</td><td>Welsh Unitary</td><td>Y</td><td>Y</td></tr><tr><td>9000</td><td>ORKNEY ISLANDS</td><td>Scottish Unitary</td><td>Y</td><td>N</td></tr><tr><td>9010</td><td>SHETLAND ISLANDS</td><td>Scottish Unitary</td><td>Y</td><td>N</td></tr><tr><td>9020</td><td>WESTERN ISLES</td><td>Scottish Unitary</td><td>Y</td><td>N</td></tr><tr><td>9051</td><td>CITY OF ABERDEEN</td><td>Scottish Unitary</td><td>Y</td><td>N</td></tr><tr><td>9052</td><td>ABERDEENSHIRE</td><td>Scottish Unitary</td><td>Y</td><td>N</td></tr><tr><td>9053</td><td>ANGUS</td><td>Scottish Unitary</td><td>Y</td><td>N</td></tr><tr><td>9054</td><td>ARGYLL &#x26; BUTE</td><td>Scottish Unitary</td><td>Y</td><td>N</td></tr><tr><td>9055</td><td>SCOTTISH BORDERS</td><td>Scottish Unitary</td><td>Y</td><td>N</td></tr><tr><td>9056</td><td>CLACKMANNAN</td><td>Scottish Unitary</td><td>Y</td><td>N</td></tr><tr><td>9057</td><td>WEST DUNBARTONSHIRE</td><td>Scottish Unitary</td><td>Y</td><td>N</td></tr><tr><td>9058</td><td>DUMFRIES AND GALLOWAY</td><td>Scottish Unitary</td><td>Y</td><td>N</td></tr><tr><td>9059</td><td>CITY OF DUNDEE</td><td>Scottish Unitary</td><td>Y</td><td>N</td></tr><tr><td>9060</td><td>EAST AYRSHIRE</td><td>Scottish Unitary</td><td>Y</td><td>N</td></tr><tr><td>9061</td><td>EAST DUNBARTONSHIRE</td><td>Scottish Unitary</td><td>Y</td><td>N</td></tr><tr><td>9062</td><td>EAST LOTHIAN</td><td>Scottish Unitary</td><td>Y</td><td>N</td></tr><tr><td>9063</td><td>EAST RENFREWSHIRE</td><td>Scottish Unitary</td><td>Y</td><td>N</td></tr><tr><td>9064</td><td>CITY OF EDINBURGH</td><td>Scottish Unitary</td><td>Y</td><td>N</td></tr><tr><td>9065</td><td>FALKIRK</td><td>Scottish Unitary</td><td>Y</td><td>N</td></tr><tr><td>9066</td><td>FIFE</td><td>Scottish Unitary</td><td>Y</td><td>N</td></tr><tr><td>9067</td><td>CITY OF GLASGOW</td><td>Scottish Unitary</td><td>Y</td><td>N</td></tr><tr><td>9068</td><td>HIGHLAND</td><td>Scottish Unitary</td><td>Y</td><td>N</td></tr><tr><td>9069</td><td>INVERCLYDE</td><td>Scottish Unitary</td><td>Y</td><td>N</td></tr><tr><td>9070</td><td>MIDLOTHIAN</td><td>Scottish Unitary</td><td>Y</td><td>N</td></tr><tr><td>9071</td><td>MORAY</td><td>Scottish Unitary</td><td>Y</td><td>N</td></tr><tr><td>9072</td><td>NORTH AYRSHIRE</td><td>Scottish Unitary</td><td>Y</td><td>N</td></tr><tr><td>9073</td><td>NORTH LANARKSHIRE</td><td>Scottish Unitary</td><td>Y</td><td>N</td></tr><tr><td>9074</td><td>PERTH &#x26; KINROSS</td><td>Scottish Unitary</td><td>Y</td><td>N</td></tr><tr><td>9075</td><td>RENFREWSHIRE</td><td>Scottish Unitary</td><td>Y</td><td>N</td></tr><tr><td>9076</td><td>SOUTH AYRSHIRE</td><td>Scottish Unitary</td><td>Y</td><td>N</td></tr><tr><td>9077</td><td>SOUTH LANARKSHIRE</td><td>Scottish Unitary</td><td>Y</td><td>N</td></tr><tr><td>9078</td><td>STIRLING</td><td>Scottish Unitary</td><td>Y</td><td>N</td></tr><tr><td>9079</td><td>WEST LOTHIAN</td><td>Scottish Unitary</td><td>Y</td><td>N</td></tr></tbody></table>


# AddressBase Islands local custodian codes

The following page details the current local custodian codes of all local custodians contributing to AddressBase Plus Islands and AddressBase Premium Islands products.

{% hint style="info" %}
The local custodian codes listed in the zip file and table below are applicable to the AddressBase Plus Islands and AddressBase Premium Islands products.

They are not applicable to the AddressBase, AddressBase Core, AddressBase Plus and AddressBase Premium products; local custodian codes for these products are available from the [AddressBase local custodian codes page](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/addressbase-local-custodian-codes).

Local custodian codes available on this page were last reviewed on **03 February 2026**
{% endhint %}

## Islands local custodian codes download

Local custodian code data is available to download in CSV format in the following zip file:

{% file src="/files/U3krxi5S9lIhnklr2g7N" %}

## Islands local custodian codes table

| Local Custodian Code | Local Custodian Name            |
| -------------------- | ------------------------------- |
| 28                   | Isle of Man                     |
| 8130                 | Antrim and Newtownabbey         |
| 8131                 | Armagh, Banbridge and Craigavon |
| 8132                 | Belfast                         |
| 8133                 | Causeway Coast and Glens        |
| 8134                 | Derry and Strabane              |
| 8135                 | Fermanagh and Omagh             |
| 8136                 | Lisburn and Castlereagh         |
| 8137                 | Mid and East Antrim             |
| 8138                 | Mid Ulster                      |
| 8139                 | Newry Mourne and Down           |
| 8140                 | North Down and Ards             |
| 8200                 | Jersey                          |
| 8205                 | Guernsey                        |


# AddressBase Documentation

Here you will find all documentation for the AddressBase product.

{% hint style="warning" %}
**Product nearing its End of Life (withdrawal) date**

The AddressBase product will become End of Life on 29 November 2027. As of this date, Ordnance Survey will cease to maintain or publish updates to the product.

Further information and details about the recommended product migration pathway are available on the [End of Life Notice – AddressBase page](/os-downloads/resources/product-resources/end-of-life-product-notices/end-of-life-notice-addressbase).
{% endhint %}

AddressBase provides a current view of all Royal Mail Postcode Address File (PAF) addresses that have been matched to the National Land and Property Gazetteer (NLPG) and One Scotland Gazetteer (OSG). The product provides Royal Mail attribution as well as enhancing the Royal Mail Postcode Address File (PAF) data with X and Y coordinates on the British National Grid and ETRS89 coordinate reference system and providing the classification of an address to a primary level. It also provides a primary level classification.

This product will provide you with a single view of an address, allow you to locate this address on a map to give you a geographic view and carry out primary analysis on the function of the address to determine, for example, residential from commercial properties.

{% hint style="info" %}
**This product is updated every six weeks.**
{% endhint %}

<figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2Fv6d7HI4KlOxnpH7ABzLK%2FAddressBase7%201.png?alt=media&amp;token=d9196f0a-1d42-4715-9fee-268bf6ca3e33" alt="Representation of AddressBase data showing address data as red dots against a background map"><figcaption><p>Representation of AddressBase data.</p></figcaption></figure>

{% hint style="info" %}
Please see the [AddressBase Getting Started Guide](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-getting-started-guide) for instructions on how to load and work with AddressBase data; this is a composite guide for [AddressBase](/os-downloads/products/addresses-and-names-portfolio/addressbase), [AddressBase Plus](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus) and [AddressBase Plus Islands](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus-islands).
{% endhint %}

{% tabs %}
{% tab title="Benefits" %}
**Precision identification**

Identify a property and locate it on a map with precision – using the X and Y coordinates we’ve assigned to the Royal Mail Postcode Address File (PAF) data.

**Understand the nation with PAF**

Every address geo data record provides Royal Mail address information from PAF, the Unique Delivery Point Reference Number (UDPRN) and X and Y coordinates.

**Track customer data**

Using the basic classifications in AddressBase you can quickly filter between residential and commercial addresses, which is ideal for marketing purposes.

**Reduce marketing costs**

Our basic classifications – residential or commercial – will reduce the costs and increase the effectiveness of your direct marketing.

**Confidence in data**

In customer services, the need for accuracy is paramount. Have confidence in your front-line staff’s ability to look up addresses on a database of millions, quickly and efficiently.
{% endtab %}

{% tab title="Use Cases" %}
**Reduce marketing costs**

Our basic classifications – residential or commercial – will reduce the costs and increase the effectiveness of your direct marketing.

**Confidence in data**

In customer services, the need for accuracy is paramount. Have confidence in your front-line staff’s ability to look up addresses on a database of millions, quickly and efficiently.
{% endtab %}

{% tab title="Summary" %}

* **Access:** Download via the [OS Data Hub](https://osdatahub.os.uk/) via the [OS Data Hub](https://osdatahub.os.uk/)
* **Data theme:** Address
* **Data structure:** Vector – Points
* **Coverage**: Great Britain
* **Scale**: 1:1 250 to 1: 10 000
* **Format:** CSV, GML 3.2.1
* **Ordering area:** All of Great Britain or customisable area (5km² tiles or user-defined polygon)
* **Publication:** Monthly
  {% endtab %}

{% tab title="Additional Information" %}
**House to flat conversions**

To find out details such as houses that have been converted to flats, you'll need AddressBase Plus. it includes current properties and addresses sourced from local authorities, Ordnance Survey and Royal Mail. These are all matched to the UPRN and structured in a flat-file model.

AddressBase Plus has more records than AddressBase as it includes objects without postal addresses such as places of worship and community centres – as well as sub-divided properties. It lets you locate an address or property on a map, through the assigned X and Y coordinates.

Crucially, the cross-referencing information with OS MasterMap products via Topographic Identifiers (TOIDs) means you can view address data within a wider context.

**Paying Royal Mail royalties as a commercial customer**

Royal Mail royalties are included in the licence fee. A separate Royal Mail royalty fee applies if you license the AddressBase data on External Transaction Solution (ETS) terms.

**File size**

If the file size of your order is smaller than 2Gb, you can get it from our FTP server. in addition, public sector customers can download 5km chunk orders via our download service.

**Data from Royal Mail’s PAF**

The database is a vital component of the single address gazetteer database and is in each of the AddressBase products where there has been a match confirming the address to the LLPG address.
{% endtab %}
{% endtabs %}

## How to get this product

Access to this product is free for PSGA (Public Sector Geospatial Agreement) Members. You can [check if your organisation is a member of the PSGA on the OS website](https://www.ordnancesurvey.co.uk/customers/public-sector/psga-member-finder).

AddressBase will reach its [end of life](/os-downloads/resources/product-resources/end-of-life-product-notices/end-of-life-notice-addressbase) in Autumn 2027. Until then you can access the data via the [OS Data Hub](https://osdatahub.os.uk/).

## Sample data

### Download AddressBase sample data <a href="#download-os-egs-sample-data" id="download-os-egs-sample-data"></a>

You can download sample data for the product for free from the [OS Data Hub](https://osdatahub.os.uk/data/downloads/sample/AddressBase). The sample data are available in CSV format and cover one area (Exeter).

### Visualise AddressBase sample data online

This product is available to try out free online using one of our three sets of sample data (Exeter, Newport and Inverness) through the OS MasterMap Product Viewer:

<table data-view="cards" data-full-width="false"><thead><tr><th></th><th></th><th data-hidden></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>OS MasterMap Product Viewer</strong></td><td>Interactive demonstrator of OS MasterMap Generation data</td><td></td><td data-object-fit="cover" data-alt="Example image showing OS VectorMap Local product data over an urban area."><a href="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FcNsAjPzkb3JUfxlTSFGM%2FVectorMap-Local-1.png?alt=media&amp;token=5223a62e-33bb-4424-aa24-e5171eeef649">VectorMap-Local-1.png</a></td><td><a href="https://experience.arcgis.com/experience/20981dabcb14402687dccb437a4a78fb/">https://experience.arcgis.com/experience/20981dabcb14402687dccb437a4a78fb/</a></td></tr></tbody></table>

## Other ways to access this data

AddressBase will reach its [end of life](/os-downloads/resources/product-resources/end-of-life-product-notices/end-of-life-notice-addressbase) in November 2027. We recommend that customers migrate to the [OS NGD Address Theme](https://docs.os.uk/osngd/data-structure/address) as its new Royal Mail Address Feature Type is a direct replacement for AddressBase. The feature type contains data that enables you to access Royal Mail Postcode Address File (PAF) content, alongside Unique Property Reference Numbers (UPRNs) and limited additional attribution, similar to the information contained within AddressBase. Benefits to using OS NGD's Royal Mail Address Feature Type data over AddressBase data are listed on the [AddressBase End of Life notification](/os-downloads/resources/product-resources/end-of-life-product-notices/end-of-life-notice-addressbase#what-are-the-benefits-to-using-os-ngds-royal-mail-address-feature-type-data).

## What's next?

To access documentation and resources relating to this product, please refer to the following:

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><h4>AddressBase Lightning Talk</h4></td><td>A helpful introductory article hosted on our More than Maps platform providing additional information and context about using AddressBase data.</td><td></td><td><a href="https://docs.os.uk/more-than-maps/data-demonstrators/addressing-and-location-demonstrators/addressbase">https://docs.os.uk/more-than-maps/data-demonstrators/addressing-and-location-demonstrators/addressbase</a></td><td data-object-fit="cover" data-alt="Graphic showing the names of four of the addressing products: AddressBase, AddressBase Core, AddressBase Plus and AddressBase Premium."><a href="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FiyLIwRiwKL0YihGRCzgV%2Fimage%20(1).png?alt=media&amp;token=63fd88cb-975e-487d-ab00-9b82dc396965">image (1).png</a></td></tr><tr><td><h4>AddressBase Fundamentals</h4></td><td>The AddressBase Fundamentals pages provide an overview of the 'family' of AddressBase products, covering key elements of design for AddressBase products.</td><td></td><td><a href="/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals">AddressBase Fundamentals</a></td><td data-object-fit="cover" data-alt="Example image showing AddressBase product data over a background map."><a href="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2F5Ndx4lWXSbXYqfiVzXn4%2FAddressBase-1.png?alt=media&amp;token=df659059-f5af-47d4-b89d-a1548bba79f6">AddressBase-1.png</a></td></tr><tr><td><h4>Getting Started Guide</h4></td><td>The getting started guide provides instructions for using three AddressBase products in different software applications. Users with limited technical knowledge will be able to follow this guide.</td><td></td><td><a href="/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-getting-started-guide">AddressBase Getting Started Guide</a></td><td data-object-fit="cover" data-alt="Example image showing AddressBase product data over a background map."><a href="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FioExoMKQ4UfJZoOmF6OD%2FAddressBase-2.png?alt=media&amp;token=67b59085-8fa2-49f9-9f8a-bec3c1938819">AddressBase-2.png</a></td></tr><tr><td><h4>Technical Specification</h4></td><td>The technical specification provides detailed technical information about AddressBase. It is targeted at technical users and software developers.</td><td></td><td><a href="/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-technical-specification">AddressBase Technical Specification</a></td><td data-object-fit="cover" data-alt="Example image showing AddressBase product data over a background map."><a href="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FixjfpHyNW9VPyMzZ7grr%2FAddressBase-4.png?alt=media&amp;token=e23c78b1-4c50-4df2-833d-d6d88d6529b8">AddressBase-4.png</a></td></tr><tr><td><h4>Downloads</h4></td><td>The downloads page provides links and resources to support the application of AddressBase within your environment.</td><td></td><td><a href="/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-downloads">AddressBase Downloads</a></td><td data-object-fit="cover" data-alt="Example image showing AddressBase product data over a background map."><a href="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2Flb7OjBp8baXFnltljh6I%2FAddressBase-3.png?alt=media&amp;token=fcf0a5f6-3e3d-4f03-9484-e8fee7b4c02f">AddressBase-3.png</a></td></tr></tbody></table>

{% hint style="info" %}
New users should start with the Fundamentals pages to gain high-level insight into AddressBase products. The Getting Started Guide will help you to begin using product data in different software systems. The Technical Specification contains detailed technical insights.
{% endhint %}


# AddressBase Getting Started Guide

This getting started guide provides instructions for using three AddressBase products in different software applications. Users with limited technical knowledge will be able to follow this guide.

{% hint style="info" %}
These instructions show you how to get started with [AddressBase](/os-downloads/products/addresses-and-names-portfolio/addressbase), [AddressBase Plus](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus) and [AddressBase Plus Islands](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus-islands).
{% endhint %}

AddressBase products are created by bringing together different address sources:

* Local Authority Gazetteers across Great Britain, Northern Ireland, the Channel Islands and the Isle of Man
* Royal Mail PAF data
* References to Valuation Office Agency (VOA) data
* Additional addresses and coordinates from Ordnance Survey

The data is supplied as comma-separated values (CSV) or Geography Markup Language (GML).

<figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FixjfpHyNW9VPyMzZ7grr%2FAddressBase-4.png?alt=media&amp;token=e23c78b1-4c50-4df2-833d-d6d88d6529b8" alt="Example image showing AddressBase data."><figcaption></figcaption></figure>

This getting started guide shows you how to obtain a data supply, load and work with AddressBase data. It includes the following sections:

* [Prerequisites](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-getting-started-guide/prerequisites)
* [Data supply](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-getting-started-guide/data-supply)
* [Working with CSV data](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-getting-started-guide/working-with-csv-data)
* [Working with GML data](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-getting-started-guide/working-with-gml-data)
* [Working with COU data](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-getting-started-guide/working-with-cou-data)
* [Creating a single-line or multi-line address](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-getting-started-guide/creating-a-single-line-or-multi-line-address)
* [Searching for addresses](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-getting-started-guide/searching-for-addresses)


# Prerequisites

## System requirements <a href="#bookmark3" id="bookmark3"></a>

AddressBase data is an addressing gazetteer that can be used within GIS and database systems. For details of Ordnance Survey’s licensed partners, who can incorporate the AddressBase products in their systems, please see the [systems/software page](https://www.ordnancesurvey.co.uk/business-government/tools-support/gis/software) on the Ordnance Survey website.

Ordnance Survey does not recommend either suppliers or software products as the most appropriate system depends on many factors, such as the amount of data being taken, resources available within the organisation, the existing and planned information technology infrastructure and the applications that AddressBase products can be used for.

However, as a minimum, the following elements will be required in any system:

* A means of reading the data, either in its native format, or by translating it into a file format or for storage in a database.
* A means of storing and distributing the data, perhaps in a database or through a web-based service.
* A way of visualising and querying the data, typically a GIS.

## Backup provision of the product <a href="#bookmark4" id="bookmark4"></a>

You are advised to copy the supplied data to a backup medium.

## Typical data volumes <a href="#bookmark5" id="bookmark5"></a>

For reading purposes, it is recommended to store the data on a single hard disc. This will speed up the ability of your computer to read the data. Unzipped file sizes for the full supply of each product are as follows:

| Product                  | Unzipped CSV file size | Unzipped GML file size |
| ------------------------ | ---------------------- | ---------------------- |
| AddressBase              | 6Gb                    | 32Gb                   |
| AddressBase Plus         | 16Gb                   | 78Gb                   |
| AddressBase Plus Islands | 450Mb                  | 2Gb                    |


# Data supply

## DVD Supply of area of interest <a href="#bookmark8" id="bookmark8"></a>

When you receive an order via hard media (DVD), the following files will be supplied for the contracted area of interest (AOI):

* Data
* Doc
* Order\_Details.txt

Within the Data directory, data files will be found in their compressed format.

Within the Doc folder, a text file called *Label Information.txt* will contain information that is printed on the DVD.

The Order\_Details text file will provide information about the order, including the order date, currency date and file structure.

## DVD supply of Managed Great Britain Sets <a href="#bookmark9" id="bookmark9"></a>

When you receive an order of a Managed Great Britain Set (MGBS) via hard media (DVD), the following files will be supplied:

* Data
* Doc
* Resources
* readme.txt

There are several items contained within your supply:

* Data folder – This folder contains all of your data supply.
* Doc folder – This folder contains the Medialis.txt file, which outlines the contents of the data you have been supplied.
* Resources folder – This folder contains lookup tables for the local custodian code and AddressBase classification scheme as well as the Header files for the product.
* The readme text file – This document provides guidance notes on matters such as the filename referencing used and the directory structure of the DVD.

## Secure File Transfer Protocol <a href="#bookmark10" id="bookmark10"></a>

With a Secure File Transfer Protocol (SFTP) order, the same folder structure is supplied as in [DVD Supply of area of interest](#bookmark8). The filenames will be slightly different, reflecting the SFTP order number, and the Docs folder will be empty.

## Download <a href="#bookmark11" id="bookmark11"></a>

Public Sector Geospatial Agreement (PSGA) customers can download their geographic chunk data for AddressBase and AddressBase Plus as well as a full supply of AddressBase Plus Islands via our download service.

<details>

<summary>Download instructions</summary>

1. When you click *Download data*, you will be required to enter a password to access the PSGA Member’s Area. On successful entry to the download service, you will be able to view all your orders in the Member’s Area and download your data.
2. If you have ordered your data from our online portal, you will be sent an email with a link to a download page.
3. Within the PSGA Member’s Area, you can order and download the data that you require by clicking on *Order Data*, which can be found under the *Map Data* heading.
4. Once you have selected *Order Data*, you will be presented with the Order page. From here, you can manage all your orders, including those for AddressBase products.
5. When you have placed an order for a product, the data will become available as a series of zipped data files. To unzip these files, please refer to [Unzipping the data](#bookmark15).

</details>

## Chunked files <a href="#bookmark12" id="bookmark12"></a>

The data is supplied as chunked files that cover your selected area. These files are named according to the convention shown below.

When you open your data, you will see a series of zip folders:

#### Non-geographic chunks <a href="#bookmark13" id="bookmark13"></a>

Using AddressBase Plus and Islands as an example:

* `AddressBasePlus_FULL_2020-01-21_001_csv.zip` (Full supply of GB CSV)
* `AddressBasePlus_ISL_FULL_2020-01-21_001_csv.zip` (Full supply of Islands CSV) or
* `AddressBasePlus_COU_2020-01-21_001_gml.zip` (COU supply of GB GML)
* `AddressBasePlus_ISL_COU_2020-01-21_001_gml.zip` *(COU supply of Islands GML)*

### Geographic chunks <a href="#bookmark14" id="bookmark14"></a>

Using AddressBase Plus as an example:

* `AddressBasePlus_FULL_2011-07-29_TQ2020_csv.zip` (Full supply of CSV) or
* `AddressBasePlus_COU_2011-07-29_TQ2020_gml.zip` (COU supply of GML)

{% hint style="info" %}
The AddressBase Plus Islands product is not available in geographic chunks.
{% endhint %}

### Unzipping the data <a href="#bookmark15" id="bookmark15"></a>

The GML and CSV data is supplied in a compressed form (ZIP). Some software can access these files directly, while other software will require the files to be unzipped.

To unzip the zipped data files (.zip extension), use an unzipping utility found on most PCs, for example, WinZip. Alternatively, open-source zipping/unzipping software can be downloaded from the Internet, for example, 7-Zip.

When you unzip the files, the data will be extracted as CSV files, which are ready to use. For example, unzipping AddressBase Plus will extract files similar to the chunks below:

### Non-geographic chunks <a href="#bookmark16" id="bookmark16"></a>

* `AddressBasePlus_FULL_2020-01-21_001.csv`
* `AddressBasePlus_ISL_FULL_2020-01-21_001.csv`

### Geographic chunks <a href="#bookmark17" id="bookmark17"></a>

* `AddressBasePlus_2011-07-29_NC4040.csv`


# Working with CSV data

## Preparing the CSV data <a href="#bookmark18" id="bookmark18"></a>

These instructions describe how to prepare the CSV format of AddressBase, AddressBase Plus and AddressBase Plus Islands data for processing.

<details>

<summary>Downloading header files</summary>

AddressBase and AddressBase Plus contain different attributes. This means that there is a separate header file for each of product. Download the file that matches your product using the links below. You will use this file in the [Appending a header file to the CSV](#appending-a-header-file-to-the-csv) section.

* [AddressBase Header files](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-downloads#addressbase-header-files)
* [AddressBase Plus Header files](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus/addressbase-plus-downloads#addressbase-plus-header-files)

</details>

<details>

<summary>Merging multiple CSV files</summary>

1. Unzip all the CSV files into a single folder.\
   \Ensure there are no spaces in your chosen folder path, for example: `C:\AddressBase_Data` or `C:\AddressBase_Plus_Data or C:\AddressBase_Plus_Islands_Data`.\_
2. We recommend merging all the CSV files together to save time importing individual files.\
   \You can do this manually using a text editor such as Notepad or TextPad, but it is much faster to use a `.bat` batch file or an MS-DOS command as described below.\_
3. To use the `.bat` batch function, copy the following text and paste it into a new Notepad document:\
   \
   `copy *.csv mergedABdata.csv`\
   \
   \In this example, `mergedABdata.csv` is the output name of the merged file which will be created, but this can be any user-defined filename with the extension `.csv`.\_
4. Save the Notepad document with the file extension `.bat` (for example, `mergedABdata.bat`) in the same directory as the CSV files unzipped previously (for example, `C:\AddressBase_Data` or `C:\AddressBase_Plus_Data`).
5. Close the `.bat` file and navigate to the directory where you just saved it. Double-click on the `.bat file` (for example, `mergedABdata.bat`) and an MS-DOS window will run. Once the process is complete, the MS-DOS screen will close automatically.
6. If you look in the directory containing the AddressBase CSV files and batch file, you’ll see that there is now an additional single file called `mergedABdata.csv` (or the user-defined filename you picked when creating your batch file).

</details>

<details>

<summary>Appending a header file to the CSV</summary>

1. Download and save the appropriate product CSV header file into the same folder as the merged `AddressBase.csv` file created in [Merging multiple CSV files](#bookmark19).<br>
2. For AddressBase data, copy the relevant text below and paste it into a new Notepad document:\
   \
   `copy addressbase-header.csv+ mergedABdata.csv AB_Data.csv`\
   \
   For AddressBase Plus and AddressBase Plus Islands data, copy the relevant text below and paste it into a new Notepad document:\
   \
   `copy addressbase-plus-header.csv+ mergedAB_Plusdata.csv AB_Plus_Data.csv`\
   \
   `copy addressbase-plus-header.csv+ mergedAB_Plus_Islands_data.csv AB_Plus_Islands_Data.csv`\
   \
   \These examples use the name `mergedABdata.csv` or `mergedAB_Plusdata.csv` as the file that contains the AddressBase data merged into a single CSV file created above. If you have named this something else, amend that text above accordingly.\
   \
   The order that the documents are referred to in the above text is also important as it states which file is appended to the other. In this instance, the headers CSV file comes first so that the column headers are the first line of the final AddressBase file and the merged data is appended to the column headers.\_
3. Save the above Notepad document with the file extension `.bat` (for example, `append.bat`) in the same directory as the column headers and the merged AddressBase data (for example, `C:\AddressBase_Data` or `C:\AddressBase_Plus_Data` or `C:\AddressBase_Plus_Islands_Data`).
4. Close the `.bat` file and navigate to the directory where it was saved to (for example, *`C:\AddressBase_Data or C:\AddressBase_Plus_Data`*). Double-click on the new `.bat` file (for example, `append.bat`) and an MS-DOS window will open. Once the process is complete, the MS-DOS screen will close automatically.
5. Navigate to the directory where the column headers and the merged AddressBase data are located. You will see that a new CSV file has been created, which is the merged column headers and AddressBase data (for example, `AddressBase.csv` or `AddressBase_Plus.csv`).

</details>

## Loading CSV into GIS software <a href="#bookmark21" id="bookmark21"></a>

These instructions describe how to load the CSV format of AddressBase, AddressBase Plus and AddressBase Plus Islands data. In these examples, AddressBase Plus data will be used to describe the procedures in various GI systems.

It is assumed that the preparation of the AddressBase, AddressBase Plus or AddressBase Plus Islands CSV data has been carried out as instructed in [Preparing the CSV data](#bookmark18) before attempting to load the data. If it has not been done, the full set of data will not load, and data loaded will not contain header information.

{% hint style="info" %}
AddressBase, AddressBase Plus and AddressBase Plus Islands are also available from Ordnance Survey as a supply in GML format. Loading GML into most GIS applications requires the use of third-party translation software, which is not covered in this guide. If more information is required in the loading of GML format, please [contact Ordnance Survey.](https://www.ordnancesurvey.co.uk/contact-us)
{% endhint %}

<details>

<summary>Loading CSV into ArcGIS Pro</summary>

*Note - These instructions are based on ArcGIS Pro version 2.3.3.*

*Note - When using CSV data in ArcGIS Pro, it is necessary to have column headings. Please ensure that headings have already been prepared as instructed* [*Preparing the CSV data*](#bookmark18)*.*

1. Launch ArcGIS Pro and start a new blank project.
2. Select a folder to save the project to.<br>

   <figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2Fw2H9Z6uOAjaLNIL4FVTS%2F0.png?alt=media" alt="ArcGIS Pro Select a folder dialog"><figcaption><p>ArcGIS Pro Select a folder dialog</p></figcaption></figure>
3. Name your project and click *OK*. The project will then be created.\
   \
   \Note - ArcGIS Pro automatically creates a new File Geodatabase (`.gdb`) within the project folder created. This is different to the creation process in the older ESRI application ArcMap.\_<br>

   <figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FSGBufYEuqbsMv2W0ajUK%2F1.png?alt=media" alt="ArcGIS Pro Create a New Project dialog" width="391"><figcaption><p>ArcGIS Pro Create a New Project dialog</p></figcaption></figure>
4. You can add a backdrop map for contextual purposes from the available backdrop maps supplied by ESRI or add one of your own from a different File Geodatabase.\
   \
   \In this example, we have added a light grey backdrop map canvas supplied by ESRI.\_<br>

   <figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FkLGNi9Rm9hzUlNGuWcPz%2F2.jpeg?alt=media" alt="ArcGIS Pro UI showing backdrop map"><figcaption><p>ArcGIS Pro UI showing backdrop map</p></figcaption></figure>
5. Open the Catalog pane on the right-hand side of the window and expand the listing to see the File Geodatabase created with the project.\ <br>

   <figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2Fd7DjDPx6Ia59IykP9T82%2F3.jpeg?alt=media" alt="ArcGIS Pro UI showing File Geodatabase Catalog pane"><figcaption><p>ArcGIS Pro UI showing File Geodatabase Catalog pane</p></figcaption></figure>
6. To import the AddressBase or AddressBase Plus data, right-click the File Geodatabase, then select *Import* and from that sub-menu, select *Table*. A new Geoprocessing window will display in the right-hand pane.
7. Click the folder icon on the right-hand side of the Input Rows field. A new dialog will open.\ <br>

   <figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FnnNSJOANIMp520U5JaG7%2F4.jpeg?alt=media" alt="ArcGIS Pro UI showing Geoprocessing window"><figcaption><p>ArcGIS Pro UI showing Geoprocessing window</p></figcaption></figure>
8. Navigate to the location with the merged AddressBase or AddressBase Plus CSV file with the appended headers that you created in [Preparing the CSV data](#bookmark18). Select the file and click *OK*.<br>

   <figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FIPTWdkMLfiKg8hpR9rx0%2F5.jpeg?alt=media" alt="ArcGIS Pro Input Rows dialog"><figcaption><p>ArcGIS Pro Input Rows dialog</p></figcaption></figure>
9. Back in the Geoprocessing window, type a name in the Output Name field, then click *Run* at the bottom of the window.\ <br>

   <figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FRvd6MYscY1EWOocveCHH%2F6.jpeg?alt=media" alt="ArcGIS Pro UI showing Geoprocessing window"><figcaption><p>ArcGIS Pro UI showing Geoprocessing window</p></figcaption></figure>
10. Once the process has run, a green box will display at the bottom of the Geoprocessing window and the new AddressBase table will be listed in the left-hand panel.<br>

    <figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2Fz3m09FhpwUADiS7y6sNT%2F7.jpeg?alt=media" alt="ArcGIS Pro UI showing new table in Geoprocessing window"><figcaption><p>ArcGIS Pro UI showing new table in Geoprocessing window</p></figcaption></figure>

    \
    The data has loaded as a non-geometry table.
11. To make the data visible against the mapping backdrop, the XY Coordinate fields need to be specified.
    * In the Contents pane, right-click the *AB\_Plus* table (or the output name you chose) and in the dropdown click *Display XY data*.<br>

      <figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FQ17E1OmWqg9GiNdf3e0b%2F8.jpeg?alt=media" alt="ArcGIS Pro UI showing Contents pane"><figcaption><p>ArcGIS Pro UI showing Contents pane</p></figcaption></figure>
12. In the Geoprocessing window, the XY Table To Point parameters will be displayed.
    * Using the dropdown options, change the X Field to *X\_COORDINATE* or *Longitude* and the Y Field to *Y\_COORDINATE* or *Latitude*.
    * Change the Coordinate System to *British\_National\_Grid* by clicking the globe icon <img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FdIoqpmSZeQWrbIxqgtto%2Fimage.png?alt=media&amp;token=863dd252-dd11-470e-81f0-18eff5da1469" alt="" data-size="line">.
    * Then select *Projected Co-ordinate Systems* > *National Grids* > *Europe* > *British National Grid*.\
      \
      \Note – If you selected X and Y as Longitude and Latitude in the step above, then you need to select ETRS89 \[EPSG: 4258] instead.\_<br>

      <figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2Fv5qgbZlcRA7WKJJIUBQr%2F9.jpeg?alt=media" alt="ArcGIS Pro UI showing Geoprocessing window showing XY Table To Point parameters"><figcaption><p>ArcGIS Pro UI showing Geoprocessing window showing XY Table To Point parameters</p></figcaption></figure>
13. Click *Run*.
14. Once the process has run, a green box will appear at the bottom of the Geoprocessing window and the output *XYTableToPoint* map layer should appear ticked on the left-hand Contents pane. In the Map window, the addresses will now be displayed as point features.<br>

    <figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FCmsj6uAvwBgidVorG7jU%2F11.jpeg?alt=media" alt="Example image showing ArcGIS Pro with Address data against a backdrop map."><figcaption><p>ArcGIS Pro UI showing address data on the backdrop map</p></figcaption></figure>

    \
    You have now successfully loaded the data in ArcGIS Pro.

</details>

<details>

<summary>Loading CSV into ArcGIS Desktop</summary>

*Note - These instructions are based on ArcGIS Desktop versions 9.3 and 10.*

*Note - When using CSV data in ArcGIS , it is necessary to have column headings. Please ensure that headings have already been prepared as instructed* [*Preparing the CSV data*](#bookmark18)*.*

1. Launch ArcCatalog as a separate program, or within ArcMap if you are using version 10.
2. Connect to a folder where the AddressBase data you wish to use can be accessed, for example, *`C:\AddressBase_Data or C:\AddressBase_Plus_Data`*. To do this:
   * Click *File*, or select *Folder Connections* if you are using version 10.
   * Click *Connect Folder*, or in version 10, right-click on *Folder connections* > *Connect Folder* and navigate to the relevant folder.
   * From the main window, select the folder to connect to and click *OK*.
3. The folder should now appear in the navigation window to the left of the screen, or within your Catalog window if you have opened it within ArcGIS Map.
4. Create a File Geodatabase to store the address data. Using the file tree, go to folder connections and navigate to the directory where you wish to create the File Geodatabase, for example: `C:\AddressBase_Geodatabase\AddressBase_Plus`. This may need to be set up as a new connection as per the above.
5. Right-click on the folder where you the File Geodatabase should to be contained, then select *New* and *File Geodatabase*.
6. A File Geodatabase will be created and named by default as *New File Geodatabase*. Rename the File Geodatabase to a name of your choice.
7. Right-click on your new File Geodatabase, and select *Import* > *Table (single)…*
   * For *Input Rows*, navigate to the location of the CSV data file that contains the merged header and AddressBase or AddressBase Plus data file.
   * The Output Location should automatically populate with the location of the File Geodatabase that is to be updated; this should be the File Geodatabase you created above.
   * Insert a relevant name for the Output Table, for example: *AddressBase\_data*. Ensure that there are no spaces in the table name. This name will appear under your geodatabase.
8. Click *OK*.
9. To create a map of the locations of the AddressBase records, they need to be geocoded.
   * Right-click on the AddressBase table in the geodatabase that you have just created and select *Create Feature Class*.
   * In the *XY Table…* window, you can use the dropdowns to change the X Field to either *X\_COORDINATE* or *Longitude*, and the Y Field to *Y\_COORDINATE* or *Latitude*.
   * Click on the Input Coordinates icon and navigate to *Projected Co-ordinate Systems* > *National Grids* > *Europe* > *British National Grid*.\
     \
     \Note – If you selected X and Y as Longitude and Latitude in the step above, then you need to select ETRS89 \[EPSG: 4258] instead.\_
10. Double-click on the chosen Coordinate System, then click *Apply* and *OK*.
11. Click on the folder icon alongside the Output field and navigate to the File Geodatabase you just created above. If you cannot see the File Geodatabase, ensure that the *Save as type* box at the bottom of the dialog box is set to *File and Personal Geodatabase feature classes*.
12. Type in a name for it and click *Save*.
13. Leave the Configuration keyword dropdown menu as DEFAULTS. Click *OK*.\
    \
    \Note – You may need to right-click on the Personal Geodatabase where it was saved and select Refresh\_ in order to see your points.\
    \
    \At this stage, if you have completed the steps above in ArcCatalog and not within ArcMap, please continue to follow the steps below. Otherwise, if you have been using version 10 with the catalog inside ArcMap, the data can now be loaded into ArcMap.\_<br>
14. In ArcMap, select *File* > *Add Data* and navigate to the folder where the File Geodatabase was created above.
15. Double-click on the File Geodatabase to open it, then select all the files inside.
16. Click *Add*.
17. Once the data has been loaded into ArcMap, you may wish to display more than the ESRI-defined Object ID in the Info tool. To change this:
    * Double-click on the spatial dataset.
    * Select the *Fields* tab.
    * Change the *Primary Display Field* to your desired field, for example, *UPRN*.

</details>

<details>

<summary>Loading CSV into MapInfo Pro</summary>

*Note - These instructions are based on MapInfo Pro 2023.*

*Note –* Some versions of MapInfo has a size limit of 2Gb on each table. This equates to a maximum number of approximately 4 million AddressBase records. However it is possible to extend this, please refer to the MapInfo support guide for further information.

*Note - When using CSV data in MapInfo, it is not a critical requirement to have column headings. However, for ease of use we recommend using the headings supplied by Ordnance Survey. Instructions on how to merge the data and append the header files can be found in* [*Preparing the CSV data*](#bookmark18)*.*

1. Launch MapInfo.
2. Home > Open Table and navigate to the folder that contains the AddressBase data.
3. In the *Files of Type* dropdown menu, select *Comma delimited CSV (\*.csv),* then click on the AddressBase data to be loaded. Click *Open*.
4. In the next window, tick the *Use First Line for Column Titles* box and select the character set *INSERT CHARACTER SET*. Click *OK*.\
   \
   \Note – When adding data this way, the field type classifications and field sizes of each column automatically try to fit the type of data that MapInfo believes is contained within the column and the largest value of that classification found within that column. This means that the classifications and field sizes of some attributes may not match the field types and sizes stated in the Technical Specification. The following instructions outline how to change these columns to match those values:\_<br>
5. Select Home > Save > Save Copy As\_…\_ and select the AddressBase table that was loaded. Select *Save As…* and name the table to be created, then click *Save*.
6. Open the table that was just created via *File* > *Open*. Navigate to and select the copy of the table you just named. Click *Open*.
7. Navigate to Table>Modify Structure and select the table to be edited. Click *OK*.
8. Here you can change the *Type* and *Width* of each attribute to match the ones stated in the technical specification:

* [AddressBase technical specification](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-technical-specification)
* [AddressBase Plus technical specification](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus/addressbase-plus-technical-specification)
* [AddressBase Plus Islands technical specification](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus-islands/addressbase-plus-islands-technical-specification)

9. *Type* and *Width* should be changed for all attributes, apart from the following (due to software-specific dependencies):

* *UPRN* should be classified as *Float.*
* All attributes that have a Field Type of *Date* in the technical specification should be classified as *Character* with a length of 10.

10. After all changes have been made, click *OK*.
11. To create a map of the location of the AddressBase records, they need to be geocoded:

* Ensure the table of AddressBase records that you wish to geocode is open, then navigate to Spatial > Create > Create Points.
* Select the table you wish to geocode from the *Create Points for Table* dropdown menu.
* Expand the *Get X Coordinates from Column* dropdown menu and select either *X\_Coordinate* or *Longitude*.
* Expand the *Get Y Coordinates from Column* dropdown menu and select either *Y\_Coordinate* or *Latitude*.
* Click on the *Projection* icon, then select the *British Coordinate Systems* option from the *Category* dropdown menu. Select the *British National Grid \[EPSG: 27700]*, or if you selected Longitude and Latitude in the steps above, select *ETRS89 \[EPSG: 4258]*.
* Click *OK* to close that window and *OK* again to close the next window.
* Finally, click *Window* > *New Map Window* to view the loaded geocoded points.

</details>

<details>

<summary>Loading CSV into QGIS</summary>

*Note - These instructions are based on QGIS version 2.6.*

1. Launch QGIS and click *Settings* > *Options*.
2. Select *CRS* from the left-hand menu and check that the Coordinate Reference System is set to *British National Grid.*\
   \
   Note - Check this is set for both Default CRS for new projects and the CRS for new layers sections. If these are not already set, click Select at the end of each section and type 27700 into the Filter Box to find and select British National Grid. Alternatively, if you intend to use Latitude and Longitude columns, select ETRS89 \[EPSG: 4258].\_<br>

   <figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FZidhKFIkUL27h05McH1U%2F12.jpeg?alt=media" alt="QGIS Options | CRS dialog"><figcaption><p>QGIS Options | CRS dialog</p></figcaption></figure>
3. Click *OK*.
4. Back in the QGIS UI, go to *Layer* and select *Add Delimited Text Layer.*
5. Click *Browse* next to the filename and locate the CSV file that was created in [Preparing the CSV data](#bookmark18), containing the merged header files and AddressBase data.
6. Select the CSV file and click *Open*.
7. Accept the default or create a new layer name for the dataset.
8. Ensure that the *First record has field names* box is ticked.
9. For *Field Options*, select *Decimal separator is comma.*
10. For *Geometry Definition*, select *Point Coordinates*.
11. You should now be able to select the *X\_Coordinate field* for the *X Field* dropdown and the *Y\_Coordinate field* for the *Y Field* dropdown if this was not done automatically. Alternatively, if you wish to use the *Latitude and Longitude columns*, the *Longitude column* needs to be inserted into the *X\_COORDINATE field*, and the *Latitude column* needs to be inserted into the *Y\_COORDINATE field*.
12. Click *OK*.

</details>

## Loading CSV into a database <a href="#bookmark26" id="bookmark26"></a>

This section describes how to load AddressBase products into a few common databases.

### **Software dependencies**: <a href="#bookmark28" id="bookmark28"></a>

ArcMap, ArcGIS Desktop and ArcGIS Server software do not support the BIGINT/NUMBER data type as an Object ID. Bear this in mind if the expectation is to use this data type directly with these ESRI products. An alternative method to facilitate using ESRI software is to store this data as a string and add a new Serial ID to act as the Object ID.\
\
If you are loading AddressBase data directly into a database, you may need to increase the column length to accommodate language characters such as '^'. Some databases treat this as an additional character and therefore, if you define the column length according to our specification, there is a chance that the load may fail. Please bear in mind such adjustments may be required depending on the database you use to load the data.

### **UPRN deletions**: <a href="#bookmark29" id="bookmark29"></a>

If a UPRN is deleted and then reinserted, this does not compromise the integrity of the UPRN and its use as a primary key. If a delete is issued for a UPRN, this does not mean it will not reappear in subsequent supplies.

These are the reasons why this may happen:

* The record has moved in location more than once, moving it out of your Area of Interest (AOI), hence the deletion, but then moved back into your AOI in the future. This would also occur if you altered your AOI.
* A record has failed data validation upon a change being made. This can result, dependent on the change being made, in the record being deleted and then reintroduced when the error is fixed by the data supplier.

If a UPRN is deleted, it will not be reallocated to a different property and it therefore remains the unique identifier for a property.

<details>

<summary>Loading CSV into a PostGreSQL database</summary>

*Note - These steps describe how to load AddressBase into a PostGreSQL database using the text files created by following the instructions in* [*Preparing the CSV data*](#bookmark18) *to merge the CSV files.*

*Note - These instructions are based on PostGreSQL version 1.12.3 and assume that you have set-up your database with the PostGIS spatial extension. It is recommended that you have basic understanding of database terminology before following this guide.*

1. Prepare the text files as described in [Preparing the CSV data](#bookmark18).
2. Check that there are no carriage returns (extra rows) at the end of the CSV output file as this will result in errors. To do this, open the CSV file and hit *End* on your keyboard. Your cursor should now be at the end of the last line, and not on any extra line below. If it is on the line below, hit *Delete* to remove the extra empty row.
3. Open the *PGAdmin* tool (this can be found in *Windows Start Menu* > *PostGreSQL*).
4. Either connect to an existing database or create a new database. It is recommended that the encoding is set to *UTF-8*.
5. Open the public schema (although in a production environment, it is advised to use a different schema) and create the tables using the following steps:
   * Open the SQL query tool.
   * Depending on the data to be loaded, download the SQL file from either the AddressBase or AddressBase\_Plus\_and\_Island folder on: [https://github.com/OrdnanceSurvey/AddressBase/tree/master/Loading\_Scripts/PostgreSQL.](https://github.com/OrdnanceSurvey/AddressBase/tree/master/Loading_Scripts/PostgreSQL)
   * This SQL file can be opened in a text editor, and the SQL scripts within it can be copied and pasted into the SQL query tool within PostGreSQL.
6. Once the table has been created, the data can be loaded into each table using the SQL COPY. Adding the CSV option as the first line contains a header record for each table.\
   \Please note that the examples below are for AddressBase, then AddressBase Plus and AddressBase Plus Islands, respectively. The path and filename may need to be changed to reflect your data set-up:\_\
   \
   `COPY addressbase FROM 'C:/Address/AddressBase.csv' DELIMITER ', ' CSV HEADER;`\
   \
   `COPY addressbase_plus FROM 'C:/Address/AddressBase_Plus.csv' DELIMITER ', ' CSV HEADER;`\
   \
   `COPY addressbase_plus_islands FROM 'C:/Address/AddressBase_Plus_Islands.csv' DELIMITER ', ' CSV HEADER;`
7. Once loaded, you may want to add Primary Keys to the data. However, these can only be added on columns where the data values are unique. Where there are no unique data values, an index may be added which will aid searching. The UPRN provides the only unique value in AddressBase and AddressBase Plus.\
   \
   Primary Keys are added using the following steps:

* Right-click on the table name and select *Properties*.
* Select the *Constraints* tab.
* Click the + to add a new primary key.
* Click the *edit icon* <img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2F6oCKH2oCGOIjrzGpInK9%2F13.png?alt=media" alt="" data-size="line">.
* Enter a name to call the key under the *general tab* (for example, Key1).
* Under the definition tab, select *UPRN* or any other unique value from the dropdown under columns.

8. Click *Save*.
9. You can also index the data by following these steps:

* Right-click on the table name and select *Create* > *Index*.
* Under *general*, enter a name (for example, Idx1).
* Under the *definition tab* > *Columns*, click the +.
* Select the *UPRN* for example, or any other unique value.
* Click *Save*.

#### Converting coordinates to geometry <a href="#bookmark31" id="bookmark31"></a>

A PostGIS extension is required to create geometries. The AddressBase products contain both British National Grid (BNG) and ETRS89 coordinates. The SQL below shows how to create a column for BNG, but it can be altered to utilise the ETRS89 data.

1. Add a geometry column called `geom` to make the data usable in a GIS:\
   \
   \`SELECT AddGeometryColumn ('public', 'addressbase\_plus', 'geom', 27700, 'POINT', 2);\`\_
2. Load the data into your new geometry column:\
   \
   \`UPDATE public.addressbase\_plus SET geom = ST\_GeomFromText('POINT(' || x\_coordinate || ' ' || y\_coordinate || ') ', 27700);`_\ \ \This sets the` geom\` column in the table to equal the values from the X\_coordinate and Y\_coordinate columns, with the spatial reference defined as 27700.\_
3. Create a spatial index on the data using:\
   \
   \`CREATE INDEX idx\_abp\_geom ON public.addressbase\_plus USING gist(geom);\`\
   \
   This adds the index name idx\_abp\_geom to the same table on the geom column.\_

</details>

<details>

<summary>Loading CSV into an Oracle database</summary>

*Note - These instructions assume a basic knowledge of Oracle databases and SQLLDR (the package used to load the CSV files into the database). Other options are available for loading data into Oracle databases.*

*Using SQLLDR it is not necessary to merge all the AddressBase files into a single file, but it can load the data directly from the file provided as long as it has been unzipped first.*

*The following steps describe one method for loading a full supply of the data. Sections in italics denote where changes will need to be made to accommodate local file naming.*

1. Copy the data files from the disk to an appropriate location. It is worth noting that the files will need to be unzipped and therefore you will need in the region of 43Gb of free space.
2. Once the data is copied, the next stage is to unzip the `*.zip` files to `*.csv`. *This can be done using a package such as Winzip or 7Zip. Please see the* [*data supply page*](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium/addressbase-premium-getting-started-guide/data-supply) *for more information.*
3. With all the files unzipped, the latter stages are easier if you create a list of all the CSV files to be loaded. This can be done using a batch file that writes all the files out to a text file:\
   \
   \`dir \*.csv /b/s >filelisting.txt pause\`\_\
   \
   This file will form the basis for loading the control file in a later step.
4. Go to the OS GitHub repository: [https://github.com/OrdnanceSurvey/AddressBase/tree/master/Loading\_Scripts/Oracle.](https://github.com/OrdnanceSurvey/AddressBase/tree/master/Loading_Scripts/Oracle)
5. Open the folder of your chosen product and you should see three files. Open the file ending *`createtable.sql`* in a text editor.
6. Within the provided SQL there are references to *`<TablespaceName>`,* which need to be changed to the tablespace that is being worked in. When these are changed, copy and paste the SQL into Oracle to create the tables.
7. Next, create a SQLLDR control file. An example of one of these files is *`Oracle AddressBase_Control.ctl`*, which is provided in the folder of the GitHub repository in Step 4 above. Open the SQLLDR control file for your chosen product in a text editor.
8. Within the file you will see lines referencing *`INFILE`*. Populate these *`INFILE`* lines with the file listing created in Step 3, with one *`INFLE`* command for each file.\
   \This tells the process to open each of the files and carry out the other tasks listed below it.\
   \
   \Note – The last section of the control file creates the Geometry for the X and Y coordinate (British National Grid) if you want to create a Geometry for the Latitude and Longitude values, this will need to be created separately.\_
9. Once this file is created, it can be called from a `.bat` file to run it on the box that holds the database rather than a remote machine. If you wish to run it from a remote machine, contact your Oracle Administrator who will be able to advise on the best way to do this within your environment. The contents of the `.bat` file should be similar to the following:\
   \
   \`@sqlldr /@ control= Pause\`\_
10. Once the load has completed the relevant indexes need to be built. The SQL statements to create the indexes can be found in the same GitHub repository linked in Step 4 above.\
    \
    As before, you can copy and paste the SQL statements from a text editor into Oracle to create the indexes. The example table name provided may be different to yours, so check if this needs to be changed before use.

</details>

<details>

<summary>Loading CSV into Microsoft SQL Server</summary>

*Note - The following instructions assume that users have basic knowledge of Microsoft SQL Server and that the CSV data is already prepared as described in* [*Preparing the CSV data*](#bookmark18)*.*

*Note – There are many ways to load AddressBase products into Microsoft SQL Server; this is just one suggested method for guidance.*

1. Open the *SQL Server Management Studio (SSMS)*.
2. Right-click on the database you are loading into and select *Properties*.
3. Select *Options* on the left-hand side.
4. Expand the dropdown box for *Recovery Model* and select *Bulk-logged*.\
   \This minimises the logfile size, otherwise the default logging for Microsoft SQL Server can cause logfiles to grow over 20Gb and this can cause issues with loading.\_<br>

   <figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FWYSPNH6f1uzj7XNytXoa%2F14.jpeg?alt=media" alt="SQL Server Database Properties dialog"><figcaption><p>SQL Server Database Properties dialog</p></figcaption></figure>
5. Open the *SQL Server Management Studio (SSMS)* and right-click your database from the left-hand panel.
6. Navigate to *Tasks* and click *Import Data*. This will open the *SQL Server Import and Export Wizard*.
7. Click *Next*.
8. On the next screen, change your *Data Source* to *Flat File Source*.
9. Use the *Browse* button to navigate to your CSV file and select it.\
   \If you cannot see your files, ensure that the bottom right dropdown box has CSV files (`*.csv`) selected.\_
10. Click *Open*.
11. Your CSV file should have a header row already prepared in [Preparing the CSV data](#bookmark18). Ensure the *Column names in the first data row* is ticked.
12. Check that the *Text Qualifier* is set to a double quote (“).\
    \This is to make sure that the quotations in the raw data supply are removed upon loading but that the data remains intact\_.
13. On the left-hand side of this screen, select *Columns* and check that the *Column delimiter* is set to *Comma*.
14. On the left-hand side of the screen, select *Advanced*.
15. For each column of data you are loading, you will need to specify a `DataType`. The Microsoft SQL Server loader defaults each column to a `String`. The correct Data Type for each column is given in the technical specification:
    * [AddressBase technical specification](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-technical-specification)
    * [AddressBase Plus technical specification](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus/addressbase-plus-technical-specification)
    * [AddressBase Plus Islands technical specification](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus-islands/addressbase-plus-islands-technical-specification)
16. Once you have changed the Data Types for each column to match those given in the technical specification, click *Next*.
17. Check that your table is going to be imported into the correct database and click *Next*.
18. On this screen, you can edit the default table name that Microsoft SQL Server has chosen by clicking in the destination box. For example, for AddressBase Plus renaming to *`[dbo].[ADDRESSBASE_PLUS]`*.
19. Select *Edit Mappings* in the bottom right-hand corner.
20. In the new window, you must remove the tick in the checkbox against the *UPRN column*, which needs to be the Primary Key of the table. Click *OK* once the Primary Key alterations have been completed.
21. Click *Next*. On this screen, you can check that the Source column and Destination columns are correct.
22. Click *Next*. A summary of your import will display. If you want to continue, click *Finish*.
23. A report will be generated as your data is imported. *Success* should appear at the top once complete.
24. You may need to right-click on your database and click *Refresh* to see your new table listed.

#### Setting Primary Keys <a href="#bookmark34" id="bookmark34"></a>

To create a Primary Key field, you can run an SQL statement, such as this example for AddressBase Plus below.\
\Note - the columns you are creating these constraints on cannot be null or allowed to be null.\_

```sql
alter table dbo.ADDRESSBASE_PLUS add primary key ([UPRN]);
```

#### Creating the point geometry <a href="#bookmark35" id="bookmark35"></a>

You can also create point geometry using the X and Y coordinates or the Latitude and Longitude coordinate values. This is achieved by running the following SQL statement:

{% code overflow="wrap" %}

```sql
alter table dbo.ADDRESSBASE_PLUS
add geometry_column as geometry::Point([X_Coordinate],[Y_Coordinate], 27700); 
```

{% endcode %}

*Note – This is using British National Grid coordinates, with 27700 representing the spatial reference of the data. To use the Latitude and Longitude coordinate, the spatial reference should be set to 4258 for ETRS89.*

</details>


# Working with GML data

## Loading GML <a href="#bookmark36" id="bookmark36"></a>

GML is an XML dialect which can be used to model geographic features. It was designed by the Open Geospatial Consortium (OGC) as a means for people to share information regardless of the applications or technology that they use.

In the first instance, GML was used to overcome the differences between different GIS applications by providing a neutral file format as an alternative to proprietary formats. Because it is independent of applications, it can also be moved between databases or other types of application, which allows a wider application than just GIS data transfer.

GML data can be viewed and loaded into a database using software such as Safe FME: <https://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_ReadersWriters/gml/gml.htm>


# Working with COU data

All the AddressBase products are available as a full supply or a COU. A COU means you will only be supplied with the features which have changed since your last supply. The following sections provide guidance on how you could potentially manage a COU supply of AddressBase and AddressBase Plus data.

{% hint style="info" %}
If you receive a tile supply, you will receive Change Chunks. This means if a record within your tile has changed, all of the records in that tile will be provided to you as inserts, and no updates or deletes will be issued.
{% endhint %}

{% hint style="info" %}
Tiles are only available for GB supplies, so this does not apply to AddressBase Plus Islands.
{% endhint %}

## Types of change <a href="#bookmark39" id="bookmark39"></a>

At a high-level, there are three types of change found within a COU:

* Deletes (CHANGE\_TYPE ‘D’) are objects that have ceased to exist in your AOI since the last product refresh.
* Inserts (CHANGE\_TYPE ‘I’) are objects that have been newly inserted into your AOI since the last product refresh.
* Updates (CHANGE\_TYPE ‘U’) are objects that have been updated in your AOI since the last product refresh.

## High-level COU implementation model <a href="#bookmark40" id="bookmark40"></a>

The diagram below shows how to implement an AddressBase, AddressBase Plus and AddressBase Plus Islands COU within a database.

<figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FaIW3fSSJGD2oi3swQl81%2F15.png?alt=media" alt="High-level COU implementation model"><figcaption><p>High-level COU implementation model</p></figcaption></figure>

## High-level COU implementation model – with archiving <a href="#bookmark41" id="bookmark41"></a>

Before a COU is applied, there may be a business requirement to archive existing address records. The table below shows how to implement archiving with an AddressBase COU within a database.

<figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2F0mrZ6teaXpy427vh5ZI1%2F16.png?alt=media" alt="High-level COU implementation model on how to create archive tables and apply a COU"><figcaption><p><em>High-level COU implementation model on how to create archive tables and apply a COU</em></p></figcaption></figure>

## Applying COU to tables <a href="#bookmark42" id="bookmark42"></a>

Within AddressBase and AddressBase Plus there will be no records with the same UPRN. This can be tested by checking the number of records that have the same UPRN. The following SQL code would notify you of any duplicates:

```sql
SELECT uprn, COUNT(uprn) AS NumOccurrences FROM addressbase_plus
GROUP BY uprn
HAVING ( COUNT(uprn) > 1 );
```

This query should return 0 rows, and this confirms that there are no duplicates. As there are no duplicate records, we can use the UPRN to apply the COU.

Once confirmed, the following steps can be taken to apply the COU (without archiving):

Initially delete the existing records that will be updated and deleted:

{% code overflow="wrap" %}

```sql
DELETE FROM addressbaseplus WHERE uprn IN (SELECT uprn FROM addressbaseplus_cou WHERE change_type != 'I');
```

{% endcode %}

Insert the new updated records and the new inserted records:

{% code overflow="wrap" %}

```sql
INSERT INTO addressbaseplus SELECT * FROM addressbaseplus _cou WHERE change_type != 'D';
```

{% endcode %}

Where there is a business requirement to keep the records that are being Updated and Deleted in a separate archive table, the following SQL will create an Archive Table. It will populate with records that are being Updated and Deleted from the live AddressBase or AddressBase Plus table.

The following command creates an archive table of the records that are being updated and deleted from the existing table.

If this table already exists, you can simply use INSERT INTO rather than CREATE TABLE.

{% code overflow="wrap" %}

```sql
CREATE TABLE addressbaseplus_archive AS SELECT * FROM addressbaseplus
WHERE uprn IN (SELECT uprn FROM addressbaseplus_cou WHERE change_type != 'I');
```

{% endcode %}

The following command then deletes the records from the existing table, which are either updates or deletions:

{% code overflow="wrap" %}

```sql
DELETE FROM addressbaseplus
WHERE uprn IN (SELECT uprn FROM addressbaseplus_cou WHERE change_type!= 'I');
```

{% endcode %}

The following command then inserts the new insert records and the new updated records into the live table:

{% code overflow="wrap" %}

```sql
INSERT INTO addressbaseplus SELECT * FROM addressbaseplus_cou WHERE change_type != 'D';
```

{% endcode %}


# Creating a single-line or multi-line address

The AddressBase products provide a variety of data fields, allowing you to construct different forms of an address for a given addressable object, dependent on how the address is to be used.

AddressBase contains the Delivery Point Address which is sourced from Royal Mail’s Postcode Address File (PAF) – a non-geocoded list of addresses. These addresses are used primarily as a ‘mailing list’ for postal purposes.

There are two types of address contained in the AddressBase Plus products:

* Delivery Point Address
* Geographic Address

These two address types come from different sources and are matched together by GeoPlace.

As noted above, the Delivery Point Address is sourced from Royal Mail’s PAF data. Geographic Addresses are maintained by contributing Local Authorities. The structure of a Geographic Address is based on the British Standard BS7666. These addresses are used to provide an accurate geographic locator for an object to support, for example, service delivery, asset management, or command and control operations. They also represent the legal form of addresses as created under street naming and numbering legislation.

Each UPRN in AddressBase Plus provides the Geographic Address and, where matched, the Delivery Point Address in a one-to-one relationship. If there is no match, then the following fields will be left empty:

| DEPARTMENT\_NAME                                                     |
| -------------------------------------------------------------------- |
| ORGANISATION\_NAME                                                   |
| SUB\_BUILDING\_NAME                                                  |
| BUILDING\_NAME                                                       |
| BUILDING\_NUMBER                                                     |
| PO\_BOX\_NUMBER                                                      |
| DEPENDENT\_THOROUGHFARE (and WELSH\_DEPENDENT\_THOROUGHFARE)         |
| THOROUGHFARE (and WELSH\_THOROUGHFARE)                               |
| DOUBLE\_DEPENDENT\_LOCALITY (and WELSH\_DOUBLE\_DEPENDENT\_LOCALITY) |
| DEPENDENT\_LOCALITY (and WELSH\_DEPENDENT\_LOCALITY)                 |
| POST\_TOWN (and WELSH\_POST\_TOWN)                                   |
| POSTCODE                                                             |

## Background <a href="#bookmark45" id="bookmark45"></a>

A common requirement for customers using the AddressBase products is to build a single address label from core address elements.

There are two types of address label. The simplest is a full address on a single line with different elements separated by commas and spaces. This type of label is suited for displaying a full address within a tabular display, such as within an on-screen data grid or spreadsheet, or where a single-line printed address is most appropriate (such as within the text, header or footer of a letter):

ROSE COTTAGE, 5 MAIN STREET, ADDRESSVILLE, LONDON, SE99 9EX

The other type of formatted address is a multi-line address label. These are most often used on envelopes or at the tops of letters, where different parts of an address are separated onto different lines:

| <p>ROSE COTTAGE</p><p>5 MAIN STREET</p><p>ADDRESSVILLE LONDON</p><p>SE99 9EX</p> |
| -------------------------------------------------------------------------------- |

This guide outlines a methodology for structuring and layering a single address label, providing suggested logic to build both the Delivery Point and Geographic Address. The logic in [Delivery Point Address](#bookmark46) is applicable to AddressBase, AddressBase Plus and AddressBase Plus Islands. The logic in [Geographic Address](#bookmark50) is only applicable to AddressBase Plus and AddressBase Plus Islands.

The rules in this guide are suggestions only and can be used for visual display of full addresses. It is strongly recommended that address components are stored in the format in which they are provided in order to allow maximum flexibility of use and derived value.

## Delivery Point Address (PAF Address) <a href="#bookmark46" id="bookmark46"></a>

A Delivery Point Address contains information sourced from Royal Mail (PAF). Stringent rules are used to match these addresses to the Geographic Address and assign a common UPRN to link addresses from the two addressing sources together in the data model.

To construct a single address label based purely on the Royal Mail PAF address fields, the following attributes can be used to build a Delivery Point Address label.

The table below provides details of the Delivery Point Address Components.

<table><thead><tr><th width="516">Delivery Point Address Component</th><th>Type</th></tr></thead><tbody><tr><td>DEPARTMENT_NAME</td><td>Character</td></tr><tr><td>ORGANISATION_NAME</td><td>Character</td></tr><tr><td>SUB_BUILDING_NAME</td><td>Character</td></tr><tr><td>BUILDING_NAME</td><td>Character</td></tr><tr><td>BUILDING_NUMBER</td><td>Integer</td></tr><tr><td>PO_BOX_NUMBER</td><td>Integer</td></tr><tr><td>DEPENDENT_THOROUGHFARE (or WELSH_DEPENDENT_THOROUGHFARE)</td><td>Character</td></tr><tr><td>THOROUGHFARE (or WELSH_THOROUGHFARE)</td><td>Character</td></tr><tr><td>DOUBLE_DEPENDENT_LOCALITY (or WELSH_DOUBLE_DEPENDENT_LOCALITY)</td><td>Character</td></tr><tr><td>DEPENDENT_LOCALITY (or WELSH_DEPENDENT_LOCALITY)</td><td>Character</td></tr><tr><td>POST_TOWN (or WELSH_POST_TOWN)</td><td>Character</td></tr><tr><td>POSTCODE</td><td>Character</td></tr></tbody></table>

These address components are listed in the correct order in which they should appear on an address label. There may be a business need to replace the thoroughfare, locality and post\_town attributes with the Welsh equivalent. The following examples use the English version of these attributes only.

It should be noted that most of the PAF fields are optional and may contain null values (or zero, in the cases of ‘BUILDING NUMBER’ and ‘PO BOX NUMBER’). In these cases, those fields should be omitted.

The following (entirely fictional) example shows all of the PAF fields filled in (apart from the PO Box number) and indicates how they should be ordered in a single address label.

| Delivery Point Address Component | Example                     |
| -------------------------------- | --------------------------- |
| DEPARTMENT\_NAME                 | CUSTOMER SERVICE DEPARTMENT |
| ORGANISATION\_NAME               | JW SIMPSON LTD.             |
| SUB\_BUILDING\_NAME              | UNIT 3                      |
| BUILDING\_NAME                   | THE OLD FORGE 7             |
| BUILDING\_NUMBER                 | 7                           |
| PO\_BOX\_NUMBER                  |                             |
| DEPENDENT\_THOROUGHFARE          | RICHMOND TERRACE            |
| THOROUGHFARE                     | MAIN STREET                 |
| DOUBLE\_DEPENDENT\_LOCALITY      | HOOK                        |
| DEPENDENT\_LOCALITY              | WARSASH                     |
| POST\_TOWN                       | SOUTHAMPTON                 |
| POSTCODE                         | SO99 9ZZ                    |

In cases where a PO BOX NUMBER is present, it will only be described in the data as an integer. In order to properly format these addresses when generating an address label, these integers should be prefixed with the text ‘PO BOX’, as shown in the following example:

<table><thead><tr><th width="228">Delivery Point Address Component</th><th>Data Content</th><th>Formatted output</th></tr></thead><tbody><tr><td>ORGANISATION_NAME</td><td>‘JWS CONSULTING’</td><td>JWS CONSULTING</td></tr><tr><td>PO_BOX_NUMBER</td><td>5422</td><td>PO BOX 5422</td></tr><tr><td>THOROUGHFARE</td><td>‘HIGH STREET’</td><td>HIGH STREET</td></tr><tr><td>POST_TOWN</td><td>'SPRINGFIELD’</td><td>SPRINGFIELD</td></tr><tr><td>POSTCODE</td><td>‘SP77 0SF’</td><td>SP77 0SF</td></tr></tbody></table>

Where null or empty, string values exist (for character fields) or zeros or nulls (for integer fields), those fields should be entirely omitted from the output. However, the order in which the fields should be concatenated always remains the same.

<table><thead><tr><th width="307">Delivery Point Address Component</th><th width="174">Data content</th><th>Formatted output</th></tr></thead><tbody><tr><td>DEPARTMENT_NAME</td><td>Null</td><td></td></tr><tr><td>ORGANISATION_NAME</td><td>‘TM MOTORS’</td><td>TM MOTORS</td></tr><tr><td>SUB_BUILDING_NAME</td><td>Null</td><td></td></tr><tr><td>BUILDING_NAME</td><td>‘THE OLD BARN’</td><td>THE OLD BARN</td></tr><tr><td>BUILDING_NUMBER</td><td>0 (or null)</td><td></td></tr><tr><td>PO_BOX_NUMBER</td><td>0 (or null)</td><td></td></tr><tr><td>DEPENDENT_THOROUGHFARE</td><td>Null</td><td></td></tr><tr><td>THOROUGHFARE</td><td>‘HORSHAM LANE’</td><td>HORSHAM LANE</td></tr><tr><td>DOUBLE_DEPENDENT_LOCALITY</td><td>Null</td><td></td></tr><tr><td>DEPENDENT_LOCALITY</td><td>Null</td><td></td></tr><tr><td>POST_TOWN</td><td>‘HORSHAM’</td><td>HORSHAM</td></tr><tr><td>POSTCODE</td><td>‘RH12 1EQ’</td><td>RH12 1EQ</td></tr></tbody></table>

### Building a single-line Delivery Point Address <a href="#bookmark48" id="bookmark48"></a>

Building a single-line, formatted address for a Delivery Point is relatively straightforward. All the fields should be checked in the order shown previously in Table 1, and those that have values should be concatenated together into a single line. Generally, address components should be separated by a comma followed by a single space (‘, ’), although sometimes only a space is used between a building number and a thoroughfare name. You can use your preference.

An example of SQL logic to create a single-line Delivery Point Address is on our GitHub repository [https://github.com/OrdnanceSurvey/AddressBase/tree/master/SQL,](https://github.com/OrdnanceSurvey/AddressBase/tree/master/SQL) which should be used under the following considerations:

* The SQL operator for concatenating text is a double pipe (‘||’).
* CASE blocks have been used to test each of the fields for null values before concatenating its contents (along with a suitable separator – either ‘, ’ or ‘ ’).
* The field names and table names used are illustrative and may vary between databases.
* Depending on the database schema and data loading method used, it may be necessary to test some fields for empty strings (‘’) or zero values (for integer fields) instead of, or as well as, testing for NULLs.
* If you are using PostGres (PostGIS), it might be beneficial to substitute the ‘IS NOT NULL’ with != ‘’. This should improve the overall appearance of the output.

### Building a multi-line Delivery Point Address <a href="#bookmark49" id="bookmark49"></a>

Splitting a Delivery Point Address into multiple lines is more complicated. There are several rules to consider in order to avoid having very short lines (for example, just a building number) or very long lines within the formatted address. A summary of these rules is as follows:

* Generally, if there is a building number, it should appear on the same line as the thoroughfare (or dependent thoroughfare) name. If there is no thoroughfare name information, it should appear on the same line as the first locality name.
* In cases where building numbers have been placed in the building name field due to the presence of a letter suffix (for example, ‘11A’) or a number range separator (for example, ‘3–5’), these should be detected and placed on the same line as the thoroughfare name in the same way as a building number (or on the first locality line if no thoroughfare name is present).
* In most other cases, the building name, if present, should appear on a separate line above the thoroughfare (or dependent thoroughfare) name. If there is no thoroughfare name present, it should appear on the same line as the first locality name.
* Similar tests should be applied to the SUB\_BUILDING\_NAME field: if this field contains a number, a number with a suffix, or a numeric range, it should precede the building name on the same line. In most other cases, it should appear on a separate line above the building name.

## Geographic Address (Local Authority Address) <a href="#bookmark50" id="bookmark50"></a>

The structure of a Geographic Address is based on the British Standard BS7666 and is split into several components. This means that in order to construct a complete address label (for example, on an envelope, database form or GIS display), the components need to be constructed according to a set of rules.

Within the AddressBase Plus products, the core property level address information is stored within the Primary Addressable Object (PAO) and Secondary Addressable Object (SAO) fields. The additional attribution required to build a full address label are the `la_organisation`, `street_description`, `locality`, `town_name`, `administrative_area` and `postcode_locator`.

For a full description of PAOs and SAOs, and the complete set of AddressBase Plus fields, please refer to the Technical Specification on your respective product:

* [AddressBase technical specification](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-technical-specification)
* [AddressBase Plus technical specification](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus/addressbase-plus-technical-specification)
* [AddressBase Plus Islands technical specification](/os-downloads/products/addresses-and-names-portfolio/addressbase-plus-islands/addressbase-plus-islands-technical-specification)

### Constructing a single address label from the Geographic Address fields <a href="#bookmark51" id="bookmark51"></a>

To construct a single address label based purely on the BS7666 address fields, the following attributes should be used to build a Geographic Address label.

<table><thead><tr><th width="489">Geographic Address Component</th><th>Type</th></tr></thead><tbody><tr><td>LA_ORGANISATION</td><td>Character</td></tr><tr><td>SAO_TEXT (or ALT_LANGUAGE_SAO_TEXT)</td><td>Character</td></tr><tr><td>SAO_START_NUMBER</td><td>Integer</td></tr><tr><td>SAO_START_SUFFIX</td><td>Character</td></tr><tr><td>SAO_END_NUMBER</td><td>Integer</td></tr><tr><td>SAO_END_SUFFIX</td><td>Character</td></tr><tr><td>PAO_TEXT (or ALT_LANGUAGE_PAO_TEXT)</td><td>Character</td></tr><tr><td>PAO_START_NUMBER</td><td>Integer</td></tr><tr><td>PAO_START_SUFFIX</td><td>Character</td></tr><tr><td>PAO_END_NUMBER</td><td>Integer</td></tr><tr><td>PAO_END_SUFFIX</td><td>Character</td></tr><tr><td>STREET_DESCRIPTION (or ALT_LANGUAGE_STREET_DESCRIPTION)</td><td>Character</td></tr><tr><td>LOCALITY</td><td>Character</td></tr><tr><td>TOWN_NAME</td><td>Character</td></tr><tr><td>ADMINISTRATIVE_AREA*</td><td>Character</td></tr><tr><td>POSTCODE_LOCATOR</td><td>Character</td></tr></tbody></table>

\*ADMINISTRATIVE\_AREA is optional because it is common for this field to be the same as the TOWN\_NAME. Sometimes, however, this field will help users construct a more complete address.

These address components are listed in the correct order in which they should appear on an address label. There may be a business need to use alternate language fields for the SAO\_TEXT, PAO\_TEXT and STREET\_DESCRIPTION, which are also listed in the correct order above.

### Rendering SAOs and PAOs <a href="#bookmark53" id="bookmark53"></a>

When building a single address label, it may be necessary to concatenate the various SAO fields and PAO fields together respectively. These fields contain any property names, numbers, number ranges or suffixes that apply to an address.

A PAO number/range string should be constructed from the PAO\_START\_NUMBER, PAO\_START\_SUFFIX, PAO\_ END\_NUMBER and PAO\_END\_SUFFIX fields, as illustrated in the following table.

<table><thead><tr><th width="221">Attribute</th><th>Example 1</th><th>Example 2</th><th>Example 3</th><th>Example 4</th></tr></thead><tbody><tr><td>PAO_START_NUMBER PAO_START_SUFFIX PAO_END_NUMBER PAO_END_SUFFIX</td><td>1</td><td><p>1</p><p>A</p></td><td><p>1</p><p>5</p></td><td><p>1</p><p>A 5 C</p></td></tr><tr><td>Rendered PAO range</td><td>1</td><td>1A</td><td>1-5</td><td>1A-5C</td></tr></tbody></table>

Similarly, a SAO number/range string should be constructed from the SAO\_START\_NUMBER, SAO\_START\_SUFFIX, SAO\_END\_NUMBER and SAO\_END\_SUFFIX fields, as illustrated in the following table.

In addition to the numeric range fields described above, there are also PAO\_text and SAO\_text fields. These fields may be populated instead of, or as well as, the numeric range fields. In both cases, if both text and a numeric range string are present, the text should appear before the numeric range in any formatted address.

<table><thead><tr><th>Attribute</th><th width="116">Example 1</th><th width="119">Example 2</th><th width="180">Example 3</th><th>Example 4</th></tr></thead><tbody><tr><td>PAO (number string) PAO (text)</td><td>1</td><td>1A</td><td><p>1A</p><p>Rose Cottage</p></td><td>Rose Cottage</td></tr><tr><td>Rendered PAO (showing street name location)</td><td>1</td><td>1A</td><td>Rose Cottage, 1A</td><td>Rose Cottage,</td></tr></tbody></table>

{% hint style="info" %}
For PAOs, there will always be either a text entry or a numeric/range entry, or both. This is not the case for SAOs, which may be entirely absent for a given address.
{% endhint %}

### Street description, town, locality and administrative area names <a href="#bookmark54" id="bookmark54"></a>

The street description and administrative area names are always present, while the locality name and town name may be empty.

The ADMINISTRATIVE\_AREA field always contains a value; however, this value will not always enhance an address, but in some cases it will. In particular, check that it is not the same as the value in the TOWN\_NAME field, as this is often the case.

<table><thead><tr><th width="313">Administrative area not included</th><th width="49">vs</th><th>Administrative area included (BURY)</th></tr></thead><tbody><tr><td>34, CROW LANE, RAMSBOTTOM, BL0 9BR</td><td></td><td>34, CROW LANE, RAMSBOTTOM, BURY, BL0 9BR</td></tr></tbody></table>

In other cases, the administrative area name will simply contain the local authority name, which would not traditionally form part of a single or multi-line address but can be included to add additional information to an address label. Its inclusion is largely down to business requirements or personal preference; however, it may also be useful to 'de-duplicate' some Geographic Addresses.

The following (entirely fictional) example shows all of the BS7666 Geographic Address fields filled in and how they should be ordered in a single address label.

| Geographic Address Component                                                                                                                                                                               | Example                                                                                                                    |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| <p>LA\_ORGANISATION SAO\_TEXT</p><p>SAO (number/range string)\* PAO\_TEXT</p><p>PAO (number/range string)\* STREET\_DESCRIPTION LOCALITY</p><p>TOWN\_NAME ADMINISTRATIVE\_AREA</p><p>POSTCODE\_LOCATOR</p> | <p>JW SIMPSON LTD THE ANNEXE</p><p>1A</p><p>THE OLD MILL 7–9</p><p>MAIN STREET HOOK WARSASH SOUTHAMPTON</p><p>SO99 9ZZ</p> |

\*The number/range strings are built from the relevant PAO/SAO START\_NUMBER, START\_SUFFIX, END\_NUMBER and END\_SUFFIX fields, as described above, and formatted as character strings.

Where an administrative area matches the town name, it should always be omitted.

| Delivery Point Address Component | Data content     | Formatted output |
| -------------------------------- | ---------------- | ---------------- |
| PAO\_TEXT                        | ‘HIGHBURY HOUSE’ | HIGHBURY HOUSE   |
| STREET\_DESCRIPTION              | ‘HIGH STREET’    | HIGH STREET      |
| TOWN\_NAME                       | ‘SOUTHAMPTON’    | SOUTHAMPTON      |
| ADMINISTRATIVE\_AREA             | ‘SOUTHAMPTON’    |                  |
| POSTCODE\_LOCATOR                | ‘SO77 0SF’       | SO77 0SF         |

Where null or empty string values exist (for character fields) or zeros or nulls (for integer fields), those fields should be entirely omitted from the output; however, the order in which the fields should be concatenated always remains the same.

| Delivery Point Address Component | Data content   | Formatted output          |
| -------------------------------- | -------------- | ------------------------- |
| ORGANISATION                     | ‘TM MOTORS’    | TM MOTORS                 |
| SAO\_TEXT                        | null           |                           |
| SAO (number/range string)\*      | null           |                           |
| PAO\_TEXT                        | ‘THE OLD BARN’ | THE OLD BARN              |
| PAO (number/range string)\*      | ‘1’            | 1                         |
| STREET\_DESCRIPTION              | ‘HORSHAM LANE’ | HORSHAM LANE              |
| LOCALITY                         | null           |                           |
| TOWN\_NAME                       | ‘HORSHAM’      | HORSHAM                   |
| ADMINISTRATIVE\_AREA             | ‘HORSHAM’      | \* Duplicate name omitted |
| POSTCODE\_LOCATOR                | ‘RH12 1EQ’     | RH12 1EQ                  |

### Building a single-line Geographic Address <a href="#bookmark55" id="bookmark55"></a>

Building a single-line, formatted address for a Geographic Address is slightly more complicated than for a Delivery Point Address due to the need to preformat the SAO and PAO number/range strings. However, once this is done, the process is largely the same as before: the calculated fields should be checked in the order shown previously in [Constructing a single address label from the Geographic Address fields](#bookmark51), and those that have values should be concatenated together into a single line. Generally, address components should be separated by a comma followed by a single space (‘, ’), although sometimes only a space is used between a PAO number/range string and a street description. This is down to personal preference.

Example SQL logic to create a single-line Geographic Address can be found [on our GitHub repository](https://github.com/OrdnanceSurvey/AddressBase/tree/master/SQL), which should be used under the following considerations:

* The SQL operator for concatenating text is a double pipe (‘||’).
* CASE blocks have been used to test each of the fields for null values before concatenating its contents (along with a suitable separator – either ‘, ’ or ‘ ’).
* The field names and table names used are illustrative and may vary between databases.
* Depending on the database schema and data loading method used, it may be necessary to test some fields for empty strings (‘’) or zero values (for integer fields) instead of or as well as testing for NULLs.

### Building a multi-line Geographic Address <a href="#bookmark56" id="bookmark56"></a>

Splitting a Geographic Address into multiple lines is more complex. As with Delivery Point Addresses, there are several rules to consider in order to avoid having very short lines (for example, just a building number) or very long lines within the formatted address.

A summary of these rules is as follows:

1. Generally, if there is a PAO number/range string, it should appear on the same line as the Street Description. For example: 11A MAIN STREET
2. If there is a PAO\_text value, it should always appear on the line above the Street Name (or on the line above the \<PAO number string> + \<Street Name> where there is a PAO number/range).<br>

   | PAO\_text only            | PAO\_text and PAO number or range |
   | ------------------------- | --------------------------------- |
   | ROSE COTTAGE, MAIN STREET | ROSE COTTAGE, 11A MAIN STREET     |
3. If there is a SAO\_text value, it should appear on a separate line above the PAO\_text line (or the PAO number/range + Street Name where there is no PAO\_text value).<br>

   | **SAO\_text value only, with PAO\_text value only** | **SAO\_text value only, with PAO number/range only** |
   | --------------------------------------------------- | ---------------------------------------------------- |
   | THE ANNEXE, ROSE COURT, MAIN STREET                 | THE ANNEXE, 11A MAIN STREET                          |
4. If there is a SAO number/range value, it should be inserted either on the same line as the PAO\_text (if there is a PAO\_text value), or on the same line as the PAO number/range + Street Name (if there is only a PAO number/range value and no PAO\_text value). If there are both PAO\_text and a PAO number/range, then the SAO number/range should appear on the same line as the PAO\_text, and the PAO number/range should appear on the street line.<br>

   | **SAO number/range value only, and PAO\_text value only** | **SAO number/range value only, and PAO number/range value only** | **SAO number/range value only, and both PAO\_text and PAO number/range values** |
   | --------------------------------------------------------- | ---------------------------------------------------------------- | ------------------------------------------------------------------------------- |
   | 1A ROSE COURT, MAIN STREET                                | 1-3, 11A MAIN STREET                                             | <p>1A ROSE COURT,</p><p>11A MAIN STREET</p>                                     |
5. If there is a SAO\_text value, it should always appear on its own line.<br>

   | **SAO\_text value only with PAO\_text only** | **SAO\_text and SAO number/range and PAO\_text and PAO number/range** |
   | -------------------------------------------- | --------------------------------------------------------------------- |
   | THE ANNEXE, ROSE COTTAGE, MAIN STREET        | <p>WARDEN’S FLAT,</p><p>1A ROSE COURT,</p><p>11A MAIN STREET</p>      |
6. If there is an Organisation Name, it should always appear alone as the top line of the address.<br>

   | **Organisation Name along with all PAO + SAO fields**                               |
   | ----------------------------------------------------------------------------------- |
   | <p>COTTAGE INDUSTRY LTD, THE ANNEXE,</p><p>1A ROSE COURT,</p><p>11A MAIN STREET</p> |
7. The Locality (if present) should appear on a separate line beneath the Street Description, followed by the Town Name on the line below it. If there is no Locality, the Town Name should appear alone on the line beneath the Street Description.<br>

   | **Locality and Town Name present**                                                                      | **Town Name only**                                                                           |
   | ------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
   | <p>\[first part of address, formatted as described above] MAIN STREET,</p><p>HIGHFIELD, SOUTHAMPTON</p> | <p>\[first part of address, formatted as described above] HIGH STREET,</p><p>SOUTHAMPTON</p> |
8. If the Administrative Area name is required and it is not a duplicate of the Town Name, it can optionally be included on a separate line beneath the Town Name.<br>

   | **Administrative Area name included**                                                                                                   |
   | --------------------------------------------------------------------------------------------------------------------------------------- |
   | <p>\[first part of address, formatted as described above] MAIN STREET,</p><p>WINDSOR,</p><p>ROYAL BOROUGH OF WINDSOR AND MAIDENHEAD</p> |
9. Finally, the Postcode Locator should be inserted on the final line of the address.<br>

   | **With Postcode\_Locator on final line**                                                          |
   | ------------------------------------------------------------------------------------------------- |
   | <p>\[first part of address, formatted as described above] HIGH STREET,</p><p>MILTON, ML99 0WW</p> |

## Creating mailing lists <a href="#bookmark57" id="bookmark57"></a>

Given that AddressBase Plus contains two different types of address, a decision needs to be made as to whether to use the Geographic or Delivery Point Addresses, or a mixture.

The following two options should be considered:

1. Use Delivery Point Addresses whenever they are available, and when they are not, use a Geographic Address.
2. Use Geographic Addresses in all cases.

Depending on business requirements, in some user interfaces it may be worth considering displaying both forms of an address where possible, since this will provide the maximum information available about a given UPRN.

‘Mixing and matching’ components from the two different forms of address into a single address label is not recommended as this is likely to cause confusion in some instances.

### Other filters <a href="#bookmark58" id="bookmark58"></a>

AddressBase Plus offers other attributes that could be used in conjunction with address labels. For example, classification can be used to target certain types of property, or OS MasterMap Topography TOID cross references can be used to link address labels to Topographic objects and viewed in a GIS.

{% hint style="info" %}
TOID cross references are not available in AddressBase Plus Islands.
{% endhint %}


# Searching for addresses

A common requirement for customers using the AddressBase products is to search for properties using full or partial addresses. Address searches may return a large number of addresses, a short list of possibilities, a single match or no results, depending on the search criteria.

There are many methods of implementing an address search, from free text queries through to structured address component searches. This guide will step through two such approaches that may be used when working with AddressBase and/or AddressBase Plus.

{% hint style="info" %}
These methods are not intended as recommendations; they are merely examples of how to get maximum value out of the product when implementing an address search function.
{% endhint %}

## Free text search <a href="#bookmark60" id="bookmark60"></a>

One type of search implementation involves a single ‘search engine’ style text box, into which a user can type all or some of an address. For example:

| Find address            | Results                                                                                                                                                                                                                                                                                                                                                                                                                |
| ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| CLOVER AVENUE, SW99 9ZZ | <p>1, Clover Avenue, Fieldtown, Addressville, SW99 9ZZ</p><p>2, Clover Avenue, Fieldtown, Addressville, SW99 9ZZ</p><p>3, Clover Avenue, Fieldtown, Addressville, SW99 9ZZ</p><p>4, Clover Avenue, Fieldtown, Addressville, SW99 9ZZ</p><p>5, Clover Avenue, Fieldtown, Addressville, SW99 9ZZ</p><p>6, Clover Avenue, Fieldtown, Addressville, SW99 9ZZ</p><p>7, Clover Avenue, Fieldtown, Addressville, SW99 9ZZ</p> |

In this scenario, the user can choose to type anything in *Find address*, which may be just one component of an address (for example, a postcode, street name or building name), several parts of an address (for example, street name + town name, house name + postcode, etc.) or even (rarely) a complete address.

There may or may not be commas between search items, or address components can be entered with or without capitalised letters, etc. In short, with this search method, there is no structure to the user input and the search methodology must be designed with this in mind.

### Structured component search <a href="#bookmark61" id="bookmark61"></a>

The other common type of implementation for address searches involves entering search criteria in a structured way (for example, with a different text box for each major address component).

<figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FHYhDXvz2ZkJsiYGOyBTs%2F17.png?alt=media" alt="Example Search UI with text boxes for each address component"><figcaption><p>Example Search UI with text boxes for each address component</p></figcaption></figure>

| Results                                                                                                                                                                                             |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <p>Rose Cottage, Main Street, Fieldtown, Addressville, SW99 9ZZ</p><p>Rose Cottage, Main Street, Ashford, AS45 9PP</p><p>Rose Cottage, Main Street, Buxtew, Monley, MO88 4TY</p><p>And so on...</p> |

This method guides the user to enter known components of an address and creates a predictable user input structure around which to build a search function. While generally simpler to use and implement, it can be less user-friendly, particularly in cases where it is not obvious which box to type an address component into, for example, is *Richmond Terrace* a building name or a street?

## The search operation <a href="#bookmark62" id="bookmark62"></a>

This guide suggests how to implement the two search methods described above. Both should be used alongside the instructions on formatting single address labels.

{% hint style="info" %}
The methods described here may be adapted to work with both AddressBase Plus, AddressBase Plus Islands and AddressBase; however, in the case of AddressBase, only Delivery Point Addresses are searchable, so the geographic guidance will not apply to this product.
{% endhint %}

An address search operation typically requires two stages of interaction from a user and several processing steps from the underlying IT system. These steps can be summarised in the following diagram:

<figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2F2oJ0ILgYwhKTMRBuzpuP%2F18.jpeg?alt=media" alt="Diagram showing typical processing steps when search for an address"><figcaption><p>Diagram showing typical processing steps when search for an address</p></figcaption></figure>

The second user interaction can be omitted if there is only one result returned from the query. In almost all cases, there should be an option to ‘search again’ at the second and third stages in case no results are returned, or if none of the options shown is the required address.

Of course, different applications require different approaches; however, the general principles of the above process apply in all cases where an address is searched for based on user-entered criteria.

## Generating a search query from structured user input <a href="#bookmark63" id="bookmark63"></a>

Within an interface that accepts structured user input for an address search, it is necessary to ‘map’ the fields presented to the user with those found within AddressBase or AddressBase Plus. In particular, any query will need to test multiple fields for a given input and will need to combine result sets from the two different address formats of AddressBase Plus (or the single address format of AddressBase) in order to produce the most complete result set.

Generally, a search form will describe a simplified view of an address in order to keep the user interface tidy and intuitive. Users may be given a set of text boxes to fill in, generally including building name, building number, street name, locality name, town name and postcode. The relationships between some common search fields and the fields found in AddressBase Plus are as follows:

| Search Box                  | Mapped Delivery Point fields                                                               | Mapped geographic fields                                                     |
| --------------------------- | ------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------- |
| Business Name               | Organisation\_Name                                                                         | <p>Organisation</p><p>PAO\_Text</p><p>SAO\_Text</p>                          |
| **Flat/Subdivision Name**   | Sub\_Building\_Name Department\_Name                                                       | SAO\_Text                                                                    |
| **Flat/Subdivision Number** | Sub\_Building\_Name                                                                        | <p>SAO\_StartNumber SAO\_StartSuffix SAO\_EndNumber</p><p>SAO\_EndSuffix</p> |
| **Building Name**           | Building\_Name                                                                             | PAO\_Text                                                                    |
| **Building Number**         | <p>Building\_Number</p><p>Building\_Name (in cases where a suffix or range is present)</p> | <p>PAO\_StartNumber PAO\_StartSuffix PAO\_EndNumber</p><p>PAO\_EndSuffix</p> |
| **Street**                  | Thoroughfare Dependent\_Thoroughfare                                                       | Street PAO\_Text                                                             |
| **Locality**                | Dependent\_Locality Double\_Dependent\_Locality                                            | Locality Town Street                                                         |
| **Town**                    | Dependent\_Locality Post\_Town                                                             | Town Locality                                                                |
| **Postcode**                | Postcode                                                                                   | Postcode\_Locator                                                            |

The above mapping is an example only, and it is possible to breakdown the search fields differently, in which case, a different mapping would be required. The important thing is to consider all possibilities for how data might be recorded. For example, a business name can sometimes appear as an organisation name or a building/PAO name depending on circumstances, so both must be checked when creating a search query.

Numbers need to be handled very carefully due to the presence of suffixes and ranges. There are two options for structuring the search input in these cases:

1. A single ‘number’ box can be used (as shown above in Flat/Subdivision Number and Building Number), which will then require some string manipulation to split the input into the appropriate numeric range and suffix components in order to search the geographic addresses; or
2. Four boxes can be provided for each number (start number, start suffix, end number and end suffix), which would then need to be combined into an appropriate string to search the Delivery Point Addresses.

## Structuring the query for a structured address search <a href="#bookmark64" id="bookmark64"></a>

The basic rules to adhere to when generating a search query from structured input are as follows:

1. Ignore any search boxes that are not filled in with values.
2. Where a value is entered, assume that a match on at least one of the mapped fields is essential.

In SQL query terms, this means that each search term should generate a sub-query that searches each of the mapped fields (using OR), and that these sub-queries should then be combined together (using AND) into a single search query. The following SQL code illustrates this (for the Delivery Point Address search only) for an example where a street, locality and town name have been entered by the user:

{% code overflow="wrap" %}

```sql
SELECT dp.UPRN, GetFormattedAddress(dp.*) FROM abp dp

WHERE (dp.thoroughfare = streetsearchtext OR dp.dependent_thoroughfare = streetsearchtext) AND (dp.dependent_locality = localitysearchtext OR dp.double_dependent_locality = localitysearchtext) AND (dp.dependent_locality = townsearchtext OR dp.post_town = townsearchtext)
```

{% endcode %}

In the above example, `streetsearchtext`, `localitysearchtext`, and `townsearchtext` represent user- entered search terms (which could be parameters within an SQL function) and the `GetFormattedAddress(*)` function is a hypothetical user-defined function that returns the formatted address as a single string (suitable for display in the user interface). For more information on formatting addresses, please see [Creating a single-line or multi-line address](#bookmark43).

On top of this, for a complete query, the two different types of addresses should be queried separately (Geographic and Delivery Point Addresses), and the two result sets should be amalgamated into a single set using a UNION. The following example builds upon the previous example to include Geographic Addresses as well as Delivery Point Addresses.

{% code overflow="wrap" %}

```sql
SELECT UPRN, GetFormattedAddress(*) FROM abp

WHERE (thoroughfare = streetsearchtext OR dependent_thoroughfare = streetsearchtext) AND (dependent_locality = localitysearchtext OR double_dependent_locality = localitysearchtext) AND (dependent_locality = townsearchtext OR post_town = townsearchtext)

UNION

SELECT uprn, GetFormattedAddress(*) FROM abp WHERE (.street_name = streetsearchtext OR .pao_text = streetsearchtext) AND
(.locality = localitysearchtext OR .town = localitysearchtext OR .street_name = localitysearchtext) AND (.town = townsearchtext OR .locality = townsearchtext)
```

{% endcode %}

The SQL `UNION` operator will combine the two result sets, discarding any exact duplicates. (Retaining the exact duplicates requires the use of `UNION ALL`, but that is not desirable in this example.)

The resulting output from this query will be a set of search results as formatted addresses along with their UPRN. Exact duplicates will be omitted, but all ‘variations’ of the same address will be output (one row for each variation, with the same UPRN repeated more than once potentially). It may be wise to return the *Postal Address Flag* values against each to enable further filtering, for example, to restrict the results to postal addresses only. Note that the *Postal Address Flag* is only available in AddressBase Plus. All records in AddressBase are deemed postal as they are from Royal Mail’s PAF data.

## Supporting case-insensitive queries and partial matches <a href="#bookmark65" id="bookmark65"></a>

A flaw in the above examples is the use of equality operators. In practice, because people do not tend to be consistent with capitalisation of letters, the SQL ‘LIKE’ operator might work better, and depending on the nature of the application, a ‘%’ wildcard could be appended to the end of each search term to allow only the first few letters of an address component to be entered. For example:

{% code overflow="wrap" %}

```sql
post_town LIKE townsearchtext -- Case insensitive search in some databases ;
post_town LIKE (townsearchtext || ‘%’) -- Matches post towns that start with the search text ;
post_town LIKE (‘%’ || townsearchtext || ‘%’) -- Matches post towns that contain the search text;
```

{% endcode %}

Alternatively, if exact matches are required but case sensitivity is not, then the UPPER() or LOWER() SQL functions can be used on each side of the equals sign in comparisons (a solution that should work in all databases):

{% code overflow="wrap" %}

```sql
UPPER(post_town) = UPPER(townsearchtext) -- Case insensitive equality;
```

{% endcode %}

Finally, to combine all of the approaches, the following would work for maximum flexibility:

```sql
UPPER(post_town) LIKE (‘%’ || UPPER(townsearchtext) || ‘%’)
```

## Generating a search query from unstructured user input <a href="#bookmark66" id="bookmark66"></a>

When offering a ‘search engine’ style search feature with just a single text box to enter search terms, a wholly different approach is required. No assumptions can be made about the order, format or style of the user input, and the data will need to be ‘indexed’ in a way that facilitates searches of this type.

### Creating a search index for addresses <a href="#bookmark67" id="bookmark67"></a>

Search engine style searches are likely to require the creation of an additional index/lookup table for addresses. Such a table is likely to consist of just two main columns: a key value (UPRN) and a formatted address string. Additional columns may be required to allow filtering of results (such as the *AddressBase Postal flag* values from AddressBase Plus, which would allow the results to be filtered by *different address statuses*).

The following table shows a possible address index table structure:

| UPRN         | Address Text                                                  | Statuses (multiple fields) |
| ------------ | ------------------------------------------------------------- | -------------------------- |
| 123456789012 | 4 THE MEADOWS HIGH STREET WALTHAMSDALE BURRIDGE BU27 9UB      | Local Authority            |
| 123456789012 | FLAT 4 THE MEADOWS HIGH STREET WALTHAMSDALE BURRIDGE BU27 9UB | PAF                        |
| 123456789013 | 4 HIGH STREET WALTHAMSDALE BURRIDGE BU27 9UB                  | Non-postal                 |

Note how the addresses have been formatted as a single text string with a single space between each word (although leaving commas in would do no harm). All forms of each address (both PAF and geographic) have been added to the index, so there can be several rows with the same UPRN. To speed up complex searching, an appropriate index could be added to the Address Text field, such as a full text search index.

### Structuring the query for an unstructured address search <a href="#bookmark68" id="bookmark68"></a>

Once a suitable search index is in place, the query itself can be put together. The basic idea is to split the user input into search terms by removing commas, double spaces, and other unnecessary whitespace and then splitting it at each single space, as follows:

* User input: 4, High Street, westville, wv17

Capitalised, with commas and double-spaces removed:

* 4 HIGH STREET WESTVILLE WV17

Split into separate search terms:

* 4
* HIGH
* STREET
* WESTVILLE
* WV17

Once the user input has been pre-processed into separate search terms, a query can be generated. The key assumption in this example will be that ALL search terms must be matched against the index table to be considered as a result. This implies a query where each value is matched using an ‘AND’ operator. In order to search the whole index, the ‘LIKE’ operator will need to be used along with a ‘%’ wildcard on either side of the search text. A suitable search query for the above example would be as follows:

{% code overflow="wrap" %}

```sql
SELECT UPRN, AddressText FROM AddressSearchIndex 
WHERE
AddressText LIKE ‘%4%’ AND 
AddressText LIKE ‘%HIGH%’ AND 
AddressText LIKE ‘%STREET%’ AND 
AddressText LIKE ‘%WESTVILLE%’ AND 
AddressText LIKE ‘%WV17%’;
```

{% endcode %}

This query would return all rows from the index table that contain all of the search terms, along with the appropriate UPRNs. The following table shows how the index table would be used in the above example to return relevant results:

<table><thead><tr><th width="176"></th><th>Address text</th><th>Statuses (multiple fields)</th></tr></thead><tbody><tr><td>894756389092</td><td>4 HIGH STREET WESTVILLE SUNNYTOWN WV17 7HL</td><td>Geographic + PAF</td></tr><tr><td>894756389132</td><td>ROSE COTTAGE 4 HIGH STREET WESTVILLE SUNNYTOWN WV17 7HL</td><td>Geographic</td></tr><tr><td>274859037849</td><td>FLAT 4 HIGHBURY COURT HIGH STREET WESTVILLE SUNNYTOWN WV17 7HL</td><td>Geographic + PAF</td></tr><tr><td>482974769830</td><td>MAPS4U LTD HIGH STREET WESTVILLE SUNNYTOWN WV17 7HL</td><td>Geographic + PAF</td></tr></tbody></table>

This result set can then be presented to the user, who can select the most appropriate record, which can then be retrieved in full using the UPRN.

Of course, in a practical implementation, the above query would need to be dynamically generated, with a separate condition added for each search term. This example is quite a strict search query that requires all search terms to be present. Many layers of complexity could be added to allow partial and ‘fuzzy’ matches, and to return confidence scores, for example, but such enhancements are beyond the scope of this guide.

## Summary <a href="#bookmark69" id="bookmark69"></a>

This guide is intended as an introduction to implementing address search functionality using AddressBase, AddressBase Plus and AddressBase Plus Islands. The following list is a summary of the main points:

1. A user front-end for an address search may contain a single, search engine style text box or multiple text boxes representing different parts of an address.
2. A typical address search function takes place in three stages:
   * A user enters search text.
   * A query is run, returning a set of possible matches.
   * The user selects the address of interest and the full record is then returned.
3. With a structured search interface, the addresses can be queried directly by mapping the various address fields to the text boxes supplied.
4. For an unstructured (single text box) interface, it is necessary to create an index table with fully formatted address strings against each UPRN. Queries can then be run against this index table by splitting the user input into individual search terms and requiring them all to be present.
5. It is possible to filter results by status in AddressBase Plus (for example, *postal* or *non-postal*).
6. Any search function should search all forms of an address (both Geographic and Delivery Point Addresses).
7. Careful consideration should be given to the use of ‘fuzzy’ search algorithms (such as using wildcard or sound-alike searches).


# AddressBase Technical Specification

This technical specification provides detailed technical information about AddressBase. It is targeted at technical users and software developers.

AddressBase provides an address product containing both residential and commercial addresses where a Local Authority address has been matched to a Royal Mail PAF address. This allows users to link additional information about a property to a single address. The product also provides enhancements to the Royal Mail PAF data by assigning an X and Y coordinate on British National Grid and an ETRS89 projection, as well as a primary level classification, and a representative point code describing the positional quality.

This technical specification includes the following sections:

* [Data formats](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-technical-specification/data-formats)
* [Supply and update](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-technical-specification/supply-and-update)
* [AddressBase Premium structure](/os-downloads/products/addresses-and-names-portfolio/addressbase-premium/addressbase-premium-technical-specification/addressbase-premium-structure)
* [Feature types](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-technical-specification/feature-types)
* [Code list and enumerations](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-technical-specification/code-list-and-enumerations)
* [CSV to GML mapping](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-technical-specification/csv-to-gml-mapping)
* [Example records](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-technical-specification/example-records)

Additional documentation covering the complete family of AddressBase products is available in the AddressBase Fundamentals pages. These covers key elements of design for AddressBase products, including:

* [Future and past publication dates](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/future-and-past-publication-dates)
* [Unique Property Reference Number (UPRN)](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/unique-property-reference-number-uprn)
* [Coordinate reference systems](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/coordinate-reference-systems)
* [Classification scheme](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/classification-scheme)
* [Data sources](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/data-sources)
* [Street names and numbering](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/street-names-and-numbering)
* [Currency completeness and precision](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-overview/currency-completeness-and-precision)
* [Product supply](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/product-supply)
* [AddressBase local custodian codes](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/addressbase-local-custodian-codes)
* [AddressBase Islands local custodian codes](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/addressbase-islands-local-custodian-codes)


# Data formats

The AddressBase product will be distributed as a comma-separated values (CSV) file or Geography Markup Language (GML) version 3.2. Both of these formats can either be supplied as a full supply or a change-only update (COU) supply.

## CSV <a href="#id-1.1.1_csv" id="id-1.1.1_csv"></a>

The CSV supply of AddressBase means:

* There will be one record per line in each file.
* Fields will be separated by commas.
* String fields will be delimited by double quotes.
* No comma will be placed at the end of each row in the file.
* Records will be terminated by Carriage Return / Line Feed.
* Double quotes inside strings will be escaped by doubling.

Where a field has no value in a record, two commas will be placed together in the record (one for the end of the previous field and one for the end of the null field). Where the null field is a text field double quotes will be included between the two commas, for example - , “”,

AddressBase CSV data will be transferred using Unicode encoded in UTF-8. Unicode includes all the characters in ISO-8859-14 (Welsh characters). Some accented characters are encoded differently.

The transfer will normally be in a single file, but the data can be split into multiple files using volume numbers. Most files will only be split where there are more than one million records.

The header row for the CSV is supplied separately and can be downloaded from the product support pages.

## GML <a href="#id-1.1.2_gml" id="id-1.1.2_gml"></a>

The GML Encoding standard is an Extensible Markup Language (XML) grammar for expressing geographical features. XML schemas are used to define and validate the format and content of GML. The XML specifications that GML is based on are available from the World Wide Web Consortium (W3C) website: [http://www.w3.org.](http://www.w3.org/) More information can be found in the Open Geospatial Consortium (OGC) document, Geography Markup Language v3.2.1: <https://portal.ogc.org/files/?artifact_id=20509> The GML 3.2.1 specification provides a set of schemas that define the GML feature constructs and geometric types. These are designed to be used as a basis for building application-specific schemas, which define the data content.

A GML document is described using a GML Schema. The AddressBase schema document (addressbase.xsd), defines the features in AddressBase GML.

It imports the GML 3.2.1 schemas which rely on XML as defined by W3C at: `http://www.w3.org/XML/1998/namespace.html`

The application schema uses the following XML namespaces, for which definitions are available as given here:

<table><thead><tr><th width="102">Prefix</th><th>Namespace Identifier</th><th>Definition available at</th></tr></thead><tbody><tr><td>gml</td><td><code>http://www.opengis.net/gml</code></td><td><a href="http://schemas.opengis.net/gml/3.2.1/gml.xsd">http://schemas.opengis.net/gml/3.2.1/gml.xsd</a></td></tr><tr><td>xsi</td><td><code>http://www.w3.org/2001/XMLSchema- instance</code></td><td>Built into XML – <a href="http://www.w3.org/TR/xmlschema-1/">http://www.w3.org/TR/xmlschema-1/</a></td></tr><tr><td>xlink</td><td><code>http://www.w3.org/1999/xlink</code></td><td><a href="http://www.w3.org/1999/xlink.xsd">http://www.w3.org/1999/xlink.xsd</a></td></tr></tbody></table>

Information about Unicode and UTF-8, the character encoding we have chosen, is available on the Unicode Consortium website: <http://www.unicode.org/>.

## **Features**

Each feature within the `AddressBaseSupplySet:FeatureCollection` is encapsulated in the following member element according to its feature type:

| Member Element         | Feature Type |
| ---------------------- | ------------ |
| `<abpl:addressMember>` | `Address`    |

The UPRN of the feature is provided in the XML attribute of the `gml:id`

```html
<abpl:addressMember>
<abpl:Address gml:id=”uk.geoplace.uprn.1000011535314”>
………………..
</abpl:Addrress>
</abpl:addressMember>
```

See [the example records page](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-technical-specification/example-records) for specific GML examples.

## **Envelope**

In the GML supply you can determine the extent of your supply by the `<gml: Envelope>`. For example:

```html
<gml:boundedBy>
<gml:Envelope srsName=”urn:ogc:def:crs:EPSG::27700”>
<gml:lowerCorner>82643.6 5333.6</gml:lowerCorner>
<gml:upperCorner>655989 657599.5</gml:upperCorner>
</gml:Envelope>
</gml:boundedBy>
```


# Supply and update

The primary supply mechanism of AddressBase data is referred to as non-geographic chunks. This is a way of dividing up the data into chunks that are supplied in separate volumes, which have a fixed maximum number of records. The supply is not supplied with any reference to the geographic position of records.

Public Sector Geospatial Agreement (PSGA) customers can order Geographic chunks (5km tiles) as well as non-geographic chunks, although geographic chunks are not considered the main form of supply.

All customers are also able to take a complete supply (referred to as a Managed Great Britain Set: MGBS) or an Area of Interest (AOI) as a full supply or a COU supply.

## **Non-geographic chunks (unzipped)**

If you receive your data as non-geographic chunks, the filename will be constructed as follows:

*productName\_supply\_ccyy-mm-dd\_vvv.format*

Where:

* **ProductName** is AddressBase.
* **supply** is defined as `FULL` or `COU`.
* **ccyy-mm-dd** is the date the file was generated.
* **vvv** is the volume number of the file.
* **format** is the format of the files received, for example, `csv` or `gml`.

For example:

* `AddressBase_FULL_2013-05-28_001.gml` (GML full supply)
* `AddressBase_COU_2013-05-28_001.csv` (CSV COU supply)

## **Non-geographic chunks (zipped)**

If the data has been provided in a ZIP file, the filename will be constructed as follows:

*productName\_supply\_ccyy-mm-dd\_vvv\_format.zip*

For example:

* `AddressBase_FULL_2013-05-28_001_gml.zip` (GML full supply zipped)

## **Geographic chunks (unzipped)**

If you receive your data as geographic chunks (PSGA customers only), the filename will be constructed as follows:

*productName\_supply\_ccyy-mm-dd\_ngxxyy.format*

Where:

* **ProductName** is AddressBase.
* **supply** is defined as `FULL` or `COU`.
* **ccyy-mm-dd** is the date the file was generated.
* **ngxxyy** is the four-digit grid reference belonging to the 1km south-west corner of the 5km chunk.
* **format** is the format of the files received, for example, `csv` or `gml`.

For example:

* `AddressBase_FULL_2013-05-28_NC4040.gml` (GML full supply)
* `AddressBase_COU_2013-05-28_NC4040.csv` (CSV COU supply)

### **Geographic chunks (zipped)**

If the data has been provided in a ZIP file, the filename will be constructed as follows:

*productName\_supply\_ccyy-mm-dd\_ngxxyy\_format.zip*

For example:

* `AddressBase_COU_2013-05-28_NC4040_csv.zip` (CSV COU supply zipped)

## COU Supply

AddressBase is available as a full or COU supply.

A COU supply of data contains records or files that have changed between product refresh cycles. The primary benefit in supplying data in this way is that data volumes are smaller therefore reducing the amount of data that requires processing when compared to a full supply.

COU data enables a user to identify three types of change:

* Deletes (CHANGE\_TYPE ‘D’) are objects that have ceased to exist in your AOI since the last product refresh.
* Inserts (CHANGE\_TYPE ‘I’) are objects that have been newly inserted into your AOI since the last product refresh.
* Updates (CHANGE\_TYPE ‘U’) are objects that have been updated in your AOI since the last product refresh.

### Non-geographic chunked COU <a href="#id-4.1_non-geographic_chunked_cou" id="id-4.1_non-geographic_chunked_cou"></a>

A COU file for non-geographic chunked data can be identified by its naming convention. Any change record will be provided as a full record with the appropriate change type, as listed above.

### Geographic chunked COU (tile-based) <a href="#id-4.2_geographic_chunked_cou_-tile-based" id="id-4.2_geographic_chunked_cou_-tile-based"></a>

A geographic chunked COU is not supplied as per the non-geographic chunked COU outlined above. Its file naming convention can be found above. If a single record has changed within a specified 5km tile, the entire 5km tile containing all features will be supplied. This means the user will need to remove all features that previously existed in the provided tile(s) and insert the entire new tile(s) in its place.

### Archiving <a href="#id-4.3_archiving" id="id-4.3_archiving"></a>

When users are deleting, inserting or updating features, it is up to the user to consider their archiving requirements. If deleted records are important to your business requirements, you must take appropriate action to archive previous records.


# AddressBase structure

AddressBase is structured as a flat file. The data structure in this document is described by means of Unified Modeling Language (UML) class diagrams.

The AddressBase product is constructed as per the following UML diagrams.

## Model overview CSV <a href="#id-2.1.1_model_overview_csv" id="id-2.1.1_model_overview_csv"></a>

<figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FwVvbJCo9sCZ2lWk04NF4%2F0.png?alt=media" alt="High level data model representing the address feature (CSV)."><figcaption><p>High level data model representing the address feature (CSV).</p></figcaption></figure>

### **AddressBase CSV**

**Definition:** This address record follows the lifecycle of a Postcode Address File (PAF) record matched to a Local Authority record. As a matched record is inserted, deleted and updated within PAF, these changes are incorporated into the AddressBase product. Similarly, if the matched Local Authority address record updates an attribute contained within the AddressBase product, this change will be reflected.

The UML model of AddressBase in CSV format can be seen in the UML diagram below; classes from the Ordnance Survey product specification are coloured orange; all code lists are coloured blue, while enumerations are coloured green.

### **UML model of AddressBase in CSV format**

<figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2F7dpzZfM9n93u6GeNyVQP%2F1.png?alt=media" alt="UML model showing AddressBase feature types, enumerations and code lists for the CSV supply."><figcaption><p>UML model showing AddressBase feature types, enumerations and code lists for the CSV supply.</p></figcaption></figure>

## Model overview GML <a href="#id-2.1.2_model_overview_gml" id="id-2.1.2_model_overview_gml"></a>

<figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FEVonJZ55ySZjqcmqkcmW%2F2.png?alt=media" alt="High level data model representing the address relationships (GML)." width="563"><figcaption><p>High level data model representing the address relationships (GML).</p></figcaption></figure>

### **AddressBase GML**

**Definition:** This address record follows the lifecycle of a Postcode Address File (PAF) record matched to a Local Authority record. As a matched record is inserted, deleted and updated within PAF, these changes are incorporated into the AddressBase product. Similarly, if the matched Local Authority address record updates an attribute contained within the AddressBase product, this change will be reflected.

The UML model of AddressBase in GML format can be seen in the diagram below. In the UML diagram, classes from the Ordnance Survey product specification are orange, all code lists are coloured blue and enumerations are green.

### **UML model of AddressBase in GML format**

<figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FgvY2rL7xrzflb3qRhcvy%2F3.png?alt=media" alt="UML model showing AddressBase feature types, enumerations and code lists for the GML supply."><figcaption><p>UML model showing AddressBase feature types, enumerations and code lists for the GML supply.</p></figcaption></figure>


# Feature types

This section describes the features (one for CSV and two for GML) which make up the AddressBase product, giving the following information about each attribute.

## AddressBase attribute information

### **Name and Definition**

The name of the attribute and what it is describing.

### **Condition**

A condition associated with this attribute (optional).

### **Attribute Type**

The nature of the attribute, for example a numeric value or a code list value.

### **Multiplicity**

Describes how many times this element is expected to be populated in the data. An attribute may be optional or mandatory within the AddressBase product. These are denoted by:

* ‘1’ – there must be a value.
* ‘0..1’ – population is optional but a maximum of one attribute will be returned These values may be used in combination.

## AddressBase feature types

* [Address](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-technical-specification/feature-types/address)
* [AddressBase Supply Set](/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-technical-specification/feature-types/addressbase-supply-set)


# Address

This address record follows the lifecycle of a Postcode Address File (PAF) record matched to a Local Authority record. As a matched record is inserted, deleted and updated within PAF, these changes are incorporated into the AddressBase product. Similarly, if the matched Local Authority address record updates an attribute contained within the AddressBase product, this change will be reflected.

## Feature type attributes <a href="#feature-type-attributes" id="feature-type-attributes"></a>

The following sub-sections provide details about the attributes included with this feature, their data types in the different output formats, and other important metadata about them.

The following sub-sections provide details about the attributes included with the Address feature type.

### UPRN

Unique Property Reference Number (UPRN) assigned by the LLPG Custodian or Ordnance Survey.

* **Attribute Name:** uprn (GML), UPRN (CSV)
* **Data Type:** Integer (GML), Integer (CSV)
* **Multiplicity:** \[1]
* **Size**: 12
* **Source**: Contributing Local Authority / Ordnance Survey

### TOID:

Unique identifier provided by Ordnance Survey.

* **Attribute Name:** osAddressTOID (GML), OS\_ADDRESS\_TOID (CSV)
* **Data Type:** LocalisedCharacterString (GML), char (CSV)
* **Multiplicity:** \[0..1]
* **Size**: 20
* **Source**: Ordnance Survey

### UDPRN

Royal Mail’s Unique Delivery Point Reference Number (UDPRN).

* **Attribute Name:** udprn (GML), UDPRN (CSV)
* **Data Type:** Integer (GML), Integer (CSV)
* **Multiplicity:** \[1]
* **Size**: 8
* **Source**: Royal Mail

### Organisation name

The organisation name is the business name given to a delivery point within a building or small group of buildings. For example: TOURIST INFORMATION CENTRE

This field could also include entries for churches, public houses and libraries.

* **Attribute Name:** organisationName (GML), ORGANISATION\_NAME (CSV)
* **Condition**: Organisation Name or PO Box Number must be present if Building Name or Building Number are all not present.
* **Data Type:** LocalisedCharacterString (GML), char (CSV)
* **Multiplicity:** \[0..1]
* **Size**: 60
* **Source**: Royal Mail

### Department name

For some organisations, department name is indicated because mail is received by subdivisions of the main organisation at distinct delivery points. For example, Organisation Name: ABC COMMUNICATIONS or RM Department Name: MARKETING DEPARTMENT

* **Attribute Name:** departmentName (GML), DEPARTMENT\_NAME (CSV)
* **Condition**: If a Department Name is present, an Organisation Name must also be present.
* **Data Type:** LocalisedCharacterString (GML), char (CSV)
* **Multiplicity:** \[0..1]
* **Size**: 60
* **Source**: Royal Mail

### Po box number

Post Office Box (PO Box) number.

* **Attribute Name:** poBoxNumber (GML), PO\_BOX\_NUMBER (CSV)
* **Condition**: Organisation Name or PO Box Number must be present if Building Name or Building Number are all not present.
* **Data Type:** CharacterString (GML), char (CSV)
* **Multiplicity:** \[0..1]
* **Size**: 6
* **Source**: Royal Mail

### Sub building name

The sub-building name and/or number are identifiers for subdivisions of properties.

For example: Sub-building Name: FLAT 3, Building Name: POPLAR COURT, Thoroughfare: LONDON ROAD

{% hint style="info" %}
If the above address is styled 3 POPLAR COURT, all the text will be shown in the Building Name attribute and the Sub-building Name will be empty. The building number will be shown in this field when it contains a range, decimal or non-numeric character (see Building Number).
{% endhint %}

* **Attribute Name: s**ubBuildingName (GML), SUB\_BUILDING\_NAME (CSV)
* **Condition**: If a Sub Building Name is present, a Building Name or Building Number must also be present.
* **Data Type:** LocalisedCharacterString (GML), char (CSV)
* **Multiplicity:** \[0..1]
* **Size**: 30
* **Source**: Royal Mail

### Building name

The building name is a description applied to a single building or a small group of buildings, such as Highfield House. This also includes those building numbers that contain non-numeric characters, such as 44A.

Some descriptive names, when included with the rest of the address, are sufficient to identify the property uniquely and unambiguously, for example, MAGISTRATES COURT.

Sometimes the building name will be a blend of distinctive and descriptive naming, for example, RAILWAY TAVERN (PUBLIC HOUSE) or THE COURT ROYAL (HOTEL).

* **Attribute Name:** buildingName (GML), BUILDING\_NAME (CSV)
* **Condition**: Building Name must be present if Organisation Name or Building Number or PO Box Number are all not present.
* **Data Type:** LocalisedCharacterString (GML), char (CSV)
* **Multiplicity:** \[0..1]
* **Size**: 50
* **Source**: Royal Mail

### Building number

The building number is a number given to a single building or a small group of buildings, thus identifying it from its neighbours, for example, 44. Building numbers that contain a range, decimals or non-numeric characters do not appear in this field but will be found in the buildingName or the sub-BuildingName fields.

* **Attribute Name:** buildingNumber (GML), BUILDING\_NUMBER (CSV)
* **Condition**: Building Number must be present if Organisation Name or Building Name or PO Box Number are all not present.
* **Data Type:** Integer (GML), Integer (CSV)
* **Multiplicity:** \[0..1]
* **Size**: 4
* **Source**: Royal Mail

### Thoroughfare

A thoroughfare in AddressBase is fundamentally a road, track or named access route on which there are Royal Mail delivery points, for example, HIGH STREET.

* **Attribute Name:** thoroughfare (GML), THOROUGHFARE (CSV)
* **Data Type:** LocalisedCharacterString (GML), char (CSV)
* **Multiplicity:** \[0..1]
* **Size**: 80
* **Source**: Royal Mail

### Post town

The town or city in which the Royal Mail sorting office is located which services this record. There may be more than one, possibly several, sorting offices in a town or city.

* **Attribute Name:** postTown (GML), POST\_TOWN (CSV)
* **Data Type:** LocalisedCharacterString (GML), char (CSV)
* **Multiplicity:** \[1]
* **Size**: 30
* **Source**: Royal Mail

### Double dependent locality

This is used to distinguish between similar thoroughfares or the same thoroughfare within a dependent locality. For example, Millbrook Industrial Estate and Cranford Estate in this situation: BRUNEL WAY, MILLBROOK INDUSTRIAL ESTATE, MILLBROOK, SOUTHAMPTON and BRUNEL WAY, CRANFORD ESTATE, MILLBROOK, SOUTHAMPTON.

* **Attribute Name:** doubleDependentLocality (GML), DOUBLE\_DEPENDENT\_LOCALITY (CSV)
* **Data Type:** LocalisedCharacterString (GML), char (CSV)
* **Condition**: If a Double Dependent Locality is present, a Dependent Locality must also be present.
* **Multiplicity:** \[0..1]
* **Size**: 35
* **Source**: Royal Mail

### Dependent locality

Dependent locality areas define an area within a post town. These are only necessary for postal purposes and are used to aid differentiation where there are thoroughfares of the same name in the same locality. For example, HIGH STREET in SHIRLEY and SWAYTHLING in this situation: HIGH STREET, SHIRLEY, SOUTHAMPTON and HIGH STREET, SWAYTHLING, SOUTHAMPTON.

* **Attribute Name**: dependentLocality (GML), DEPENDENT\_LOCALITY (CSV)
* **Data Type:** LocalisedCharacterString (GML), char (CSV)
* **Multiplicity:** \[0..1]
* **Size**: 35
* **Source**: Royal Mail

### Postcode

A postcode is an abbreviated form of address made up of combinations of between five and seven alphanumeric characters. These are used by Royal Mail to help with the automated sorting of mail. A postcode may cover between 1 and 100 addresses.

There are two main components of a postcode, for example, NW6 4DP:

* The outward code (or ‘outcode’). The first two–four characters of the postcode constituting the postcode area and the postcode district, for example, NW6. It is the part of the postcode that enables mail to be sent from the accepting office to the correct area for delivery.
* The inward code (or ‘incode’). The last three characters of the postcode constituting the postcode sector and the postcode unit, example, 4DP. It is used to sort mail at the local delivery office.<br>
* **Attribute Name:** postcode (GML), POSTCODE (CSV)
* **Data Type:** CharacterString (GML), char (CSV)
* **Multiplicity:** \[1]
* **Size**: 8
* **Source**: Royal Mail

### Postcode type

Describes the address as a small or large user as defined by Royal Mail.

* **Attribute Name**: postcodeType (GML), POSTCODE\_TYPE (CSV)
* **Code List Name**: [PostcodeTypeCode](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/code-lists-and-enumerations/postcodetypecode)
* **Condition**: If PO Box number is present Postcode Type must be ‘L’.
* **Multiplicity**: \[1]
* **Size**: 1
* **Source**: Royal Mail

### Position

A value in metres defining the x and y location in accordance with the British National Grid.

* **Attribute Name**: position (GML), X\_COORDINATE, Y\_COORDINATE (CSV)
* **Data Type:** GM\_Point (GML), Float (CSV)
* **Multiplicity:** \[1]
* **Size**: X\_COORDINATE (precision, scale) – (8, 2), Y\_COORDINATE (precision, scale) – (9, 2)
* **Source**: Contributing Local Authority/Ordnance Survey

### Position lat long

A value defining the Longitude and Latitude location in accordance with the ETRS89 coordinate reference system.

* **Attribute Name**: positionLatLong (GML), LATITUDE, LONGITUDE (CSV)
* **Data Type:** GM\_Point (GML), Float (CSV)
* **Multiplicity:** \[1]
* **Size**: LATITUDE (precision, scale) – (9, 7), LONGITUDE (precision, scale) – (8, 7)
* **Source**: Ordnance Survey

### RPC

Representative Point Code. This code is used to reflect positional accuracy.

* **Attribute Name**: rpc (GML), RPC (CSV)
* **Code List Name:** [RPCCode](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/code-lists-and-enumerations/rpccode)
* **Multiplicity:** \[1]
* **Size**: 1
* **Source**: Contributing Local Authority

### Country

The country in which a record can be found.

* **Attribute Name**: country (GML), COUNTRY (CSV)
* **Code List Name:** [CountryCode](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/code-lists-and-enumerations/countrycode)
* **Multiplicity:** \[1]
* **Size**: 1

### Change type

Type of Record Change – please see Section 4 for more information.

* **Attribute Name**: changeType (GML), CHANGE\_TYPE (CSV)
* **Code List Name:** [ChangeTypeCode](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/code-lists-and-enumerations/changetypecode)
* **Multiplicity:** \[1]
* **Size**: 1

### LA start date

The date on which the address record was inserted into the database in the CCYY-MM-DD format.

* **Attribute Name**: laStartDate (GML), LA\_START\_DATE (CSV)
* **Data Type:** Date (GML), Date (CSV)
* **Multiplicity:** \[1]
* **Source**: Contributing Local Authority

### RM start date

Date on which the Royal Mail address was loaded into the NAG (National Address Gazetteer in the CCYY-MM-DD format – as maintained by Geoplace) hub.

* **Attribute Name**: rmStartDate (GML), RM\_START\_DATE (CSV)
* **Data Type:** Date (GML), Date (CSV)
* **Multiplicity:** \[1]
* **Source**: Royal Mail

### Last update date

The date on which any of the attributes on this record were last changed in the CCYY-MM-DD format.

* **Attribute Name**: lastUpdateDate (GML), LAST\_UPDATE\_DATE (CSV)
* **Data Type:** Date (GML), Date (CSV)
* **Multiplicity:** \[1]

### Class

Primary classification of the address record. For example, identifying the record as commercial (value of ‘C’) or residential (value of ‘R’).

* **Attribute Name**: class (GML), CLASS (CSV)
* **Data Type:** CharacterString (GML), char (CSV)
* **Multiplicity:** \[1]
* **Size**: 1
* **Source**: Contributing Local Authority


# AddressBase Supply Set

This feature is formally known as the GML feature collection and is used to define a collection of features.

{% hint style="info" %}
This is not supplied as part of the CSV supply. Please see [Model Overview CSV](https://docs.os.uk/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-technical-specification/feature-types/pages/5oH7rGidMlJ6q5ZfS91z#id-2.1.1_model_overview_csv) and [Model Overview GML](https://docs.os.uk/os-downloads/products/addresses-and-names-portfolio/addressbase/addressbase-technical-specification/feature-types/pages/5oH7rGidMlJ6q5ZfS91z#id-2.1.2_model_overview_gml) for more information.
{% endhint %}

## Feature type attributes <a href="#feature-type-attributes" id="feature-type-attributes"></a>

The following sub-sections provide details about the attributes included with this feature, their data types in the different output formats, and other important metadata about them.

### Query time

Time the data was extracted from the database.

* **Attribute Name**: queryTime (GML), Not provided (CSV)
* **Data Type:** DateTime (GML)
* **Multiplicity:** \[1]
* **Size**: 1

### Query change since date

The date given as part of a change-only query.

* **Attribute Name**: queryChangeSinceDate (GML), Not provided (CSV)
* **Data Type:** Date (GML)
* **Multiplicity:** \[1]
* **Size**: 1


# Code list and enumerations

A code list or enumeration is a controlled set of values which can be used to populate a specific column. The code list and enumeration UML models associated with AddressBase are shown in the diagram below:

<figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FRxoHLyxTixXqi2TwKhV9%2F4.png?alt=media" alt="UML diagram providing details of the code list and enumerations in the AddressBase product"><figcaption><p>UML diagram providing details of the code list and enumerations in the AddressBase product.</p></figcaption></figure>

## AddressBase code list and enumerations

* [CountryCode](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/code-lists-and-enumerations/countrycode)
* [RPCCode](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/code-lists-and-enumerations/rpccode)
* [ChangeTypeCode](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/code-lists-and-enumerations/changetypecode)
* [PostcodeTypeCode](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/code-lists-and-enumerations/postcodetypecode)


# CSV to GML mapping

The naming of attributes between GML and CSV will be different due to the requirements of the file formats. For convenience the following table maps the CSV attribute name to the GML attribute name.

<table><thead><tr><th width="397">CSV</th><th>GML</th></tr></thead><tbody><tr><td>UPRN</td><td>uprn</td></tr><tr><td>OS_ADDRESS_TOID</td><td>osAddressTOID</td></tr><tr><td>UDPRN</td><td>udprn</td></tr><tr><td>ORGANISATION_NAME</td><td>organisationName</td></tr><tr><td>DEPARTMENT_NAME</td><td>departmentName</td></tr><tr><td>PO_BOX_NUMBER</td><td>poBoxNumber</td></tr><tr><td>SUB_BUILDING_NAME</td><td>subBuildingName</td></tr><tr><td>BUILDING_NAME</td><td>buildingName</td></tr><tr><td>BUILDING_NUMBER</td><td>buildingNumber</td></tr><tr><td>DEPENDENT_THOROUGHFARE</td><td>dependentThoroughfare</td></tr><tr><td>THOROUGHFARE</td><td>thoroughfare</td></tr><tr><td>POST_TOWN</td><td>postTown</td></tr><tr><td>DOUBLE_DEPENDENT_LOCALITY</td><td>doubleDependentLocality</td></tr><tr><td>DEPENDENT_LOCALITY</td><td>dependentLocality</td></tr><tr><td>POSTCODE</td><td>postcode</td></tr><tr><td>POSTCODE_TYPE</td><td>postcodeType</td></tr><tr><td>X_COORDINATE</td><td>position</td></tr><tr><td>Y_COORDINATE</td><td></td></tr><tr><td>LATITUDE</td><td>positionLatLong</td></tr><tr><td>LONGITUDE</td><td></td></tr><tr><td>RPC</td><td>rpc</td></tr><tr><td>COUNTRY</td><td>country</td></tr><tr><td>CHANGE_TYPE</td><td>changeType</td></tr><tr><td>LA_START_DATE</td><td>laStartDate</td></tr><tr><td>RM_START_DATE</td><td>rmStartDate</td></tr><tr><td>LAST_UPDATE_DATE</td><td>lastUpdateDate</td></tr><tr><td>CLASS</td><td>class</td></tr></tbody></table>


# Example records

The following section provides example records for both the CSV and GML supplies. Please note that the data given is to provide an example only and should not to be used as accurate data.

## CSV supply <a href="#id-5.1_csv_supply" id="id-5.1_csv_supply"></a>

### Original feature – AddressBase CSV <a href="#id-5.1.1_original_feature_-_addressbase_csv" id="id-5.1.1_original_feature_-_addressbase_csv"></a>

{% code overflow="wrap" %}

```
100100077917,"osgb1000002283010753",4201646,"","", "","","",166,"","LLANDAFF
ROAD","CARDIFF","","","CF11 9PX","S",316348.00,177163.00, 50.7268511, -3.5366289, 1,"E","I",2001-05- 10,2001-05-10,2007-08-29,"R"
```

{% endcode %}

### COU feature – AddressBase CSV <a href="#id-5.1.2_cou_feature_-_addressbase_csv" id="id-5.1.2_cou_feature_-_addressbase_csv"></a>

{% code overflow="wrap" %}

```
Changed fields are highlighted in red. 100100077917,"osgb1000002283010753",4201646,"","", "","","",166,"","LLANDAFF
ROAD","CARDIFF","","","CF11 9PX","S",316348.00,177163.00, 50.7268511,- 3.5366289, 2,"E","U",2001-05- 10,2001-05-10,2010-06-04,"R"
```

{% endcode %}

## GML supply <a href="#id-5.2_gml_supply" id="id-5.2_gml_supply"></a>

### Original feature – AddressBase GML <a href="#id-5.2.1_original_feature_-_addressbase_gml" id="id-5.2.1_original_feature_-_addressbase_gml"></a>

Please note how not all attributes are provided where the field is null.

<pre class="language-xml" data-overflow="wrap"><code class="lang-xml">
  
<strong>    100040205844
</strong>    osgb1000002274362298
    8782432
    FLAT C
    PEMBROKE HOUSE
<strong>    4
</strong>    BYSTOCK TERRACE
    EXETER
    EX4 4HY
    S
<strong>    
</strong>      
        291640.00 93040.00
      
    
    
<strong>      
</strong>        50.7268511 -3.5366289
      
    
<strong>    1
</strong>    E
<strong>    I
</strong>    2001-04-04
    2001-04-04
    2001-04-04
    R
  

</code></pre>

### COU feature – AddressBase GML <a href="#id-5.2.2_cou_feature_-_addressbase_gml" id="id-5.2.2_cou_feature_-_addressbase_gml"></a>

<pre class="language-xml" data-overflow="wrap"><code class="lang-xml">Changed fields are highlighted in red.

<strong>  
</strong>    100040205844
    osgb1000002274362298
    8782432
    FLAT C
    PEMBROKE HOUSE
    4
    BYSTOCK TERRACE
    EXETER
    EX4 4HY
    S
    
      
        291640.00 93040.00
      
    
    
      
        50.7268511 -3.5366289
      
    
    2
    E
    U
    2001-04-04
    2001-04-04
    2010-06-04
    R
  

</code></pre>


# CSV

## Original feature – AddressBase CSV <a href="#id-5.1.1_original_feature_-_addressbase_csv" id="id-5.1.1_original_feature_-_addressbase_csv"></a>

{% code overflow="wrap" %}

```csv
100100077917,"osgb1000002283010753",4201646,"","", "","","",166,"","LLANDAFF
ROAD","CARDIFF","","","CF11 9PX","S",316348.00,177163.00, 50.7268511, -3.5366289, 1,"E","I",2001-05- 10,2001-05-10,2007-08-29,"R"
```

{% endcode %}

## COU feature – AddressBase CSV <a href="#id-5.1.2_cou_feature_-_addressbase_csv" id="id-5.1.2_cou_feature_-_addressbase_csv"></a>

{% code overflow="wrap" %}

```csv
100100077917,"osgb1000002283010753",4201646,"","", "","","",166,"","LLANDAFF
ROAD","CARDIFF","","","CF11 9PX","S",316348.00,177163.00, 50.7268511,- 3.5366289, 2,"E","U",2001-05- 10,2001-05-10,2010-06-04,"R"
```

{% endcode %}


# GML

## Original feature – AddressBase GML <a href="#id-5.2.1_original_feature_-_addressbase_gml" id="id-5.2.1_original_feature_-_addressbase_gml"></a>

Please note how not all attributes are provided where the field is null.

```xml
<abs:addressMember>
  <abs:Address gml:id="uk.addressbase.uprn.100040205844">
    <abs:uprn>100040205844</abs:uprn>
    <abs:osAddressTOID>osgb1000002274362298</abs:osAddressTOID>
    <abs:udprn>8782432</abs:udprn>
    <abs:subBuildingName xml:lang="en">FLAT C</abs:subBuildingName>
    <abs:buildingName xml:lang="en">PEMBROKE HOUSE</abs:buildingName>
    <abs:buildingNumber>4</abs:buildingNumber>
    <abs:thoroughfare xml:lang="en">BYSTOCK TERRACE</abs:thoroughfare>
    <abs:postTown xml:lang="en">EXETER</abs:postTown>
    <abs:postcode>EX4 4HY</abs:postcode>
    <abs:postcodeType>S</abs:postcodeType>
    <abs:position>
      <gml:Point srsName="urn:ogc:def:crs:EPSG::27700" gml:id="uk.addressbase.uprn.p.100040205844">
        <gml:pos>291640.00 93040.00</gml:pos>
      </gml:Point>
    </abs:position>
    <abs:positionLatLong>
      <gml:Point srsName="urn:ogc:def:crs:EPSG::4258" gml:id="uk.addressbase.uprn.pl.100040205844">
        <gml:pos>50.7268511 -3.5366289</gml:pos>
      </gml:Point>
    </abs:positionLatLong>
    <abs:rpc>1</abs:rpc>
    <abs:country>E</abs:country>
    <abs:changeType>I</abs:changeType>
    <abs:laStartDate>2001-04-04</abs:laStartDate>
    <abs:rmStartDate>2001-04-04</abs:rmStartDate>
    <abs:lastUpdateDate>2001-04-04</abs:lastUpdateDate>
    <abs:class>R</abs:class>
  </abs:Address>
</abs:addressMember>
```

## COU feature – AddressBase GML <a href="#id-5.2.2_cou_feature_-_addressbase_gml" id="id-5.2.2_cou_feature_-_addressbase_gml"></a>

```xml
<abs:addressMember>
  <abs:Address gml:id="uk.addressbase.uprn.100040205844">
    <abs:uprn>100040205844</abs:uprn>
    <abs:osAddressTOID>osgb1000002274362298</abs:osAddressTOID>
    <abs:udprn>8782432</abs:udprn>
    <abs:subBuildingName xml:lang="en">FLAT C</abs:subBuildingName>
    <abs:buildingName xml:lang="en">PEMBROKE HOUSE</abs:buildingName>
    <abs:buildingNumber>4</abs:buildingNumber>
    <abs:thoroughfare xml:lang="en">BYSTOCK TERRACE</abs:thoroughfare>
    <abs:postTown xml:lang="en">EXETER</abs:postTown>
    <abs:postcode>EX4 4HY</abs:postcode>
    <abs:postcodeType>S</abs:postcodeType>
    <abs:position>
      <gml:Point srsName="urn:ogc:def:crs:EPSG::27700" gml:id="uk.addressbase.uprn.p.100040205844">
        <gml:pos>291640.00 93040.00</gml:pos>
      </gml:Point>
    </abs:position>
    <abs:positionLatLong>
      <gml:Point srsName="urn:ogc:def:crs:EPSG::4258" gml:id="uk.addressbase.uprn.pl.100040205844">
        <gml:pos>50.7268511 -3.5366289</gml:pos>
      </gml:Point>
    </abs:positionLatLong>
    <abs:rpc>2</abs:rpc>
    <abs:country>E</abs:country>
    <abs:changeType>U</abs:changeType>
    <abs:laStartDate>2001-04-04</abs:laStartDate>
    <abs:rmStartDate>2001-04-04</abs:rmStartDate>
    <abs:lastUpdateDate>2010-06-04</abs:lastUpdateDate>
    <abs:class>R</abs:class>
  </abs:Address>
</abs:addressMember>
```


# AddressBase Downloads

{% hint style="info" %}

### Product download

This page provides downloadable files to support the product in use. To download the product itself, please visit the [OS Data Hub](https://osdatahub.os.uk/data).
{% endhint %}

## Classification scheme

The product classification scheme is available to download as a zip file (in CSV and .xlsx formats) from the [classification scheme page](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/classification-scheme) in the AddressBase Fundamentals section.

## Header files

The header files for AddressBase are available for download as a CSV file:

{% file src="/files/iRo8odwr4BpIS6dS1Aeo" %}

## Local custodian codes

Local custodian codes for the product are available to download as a zip file (in CSV format) from the [AddressBase local custodian codes page ](/os-downloads/products/addresses-and-names-portfolio/addressbase-fundamentals/addressbase-local-custodian-codes)in the AddressBase Fundamentals section.


# AddressBase Known Data Issues

This page provides the details of known data issues in the AddressBase product. Once resolved, details of a known data issue will be held on the page until the next release of the product.

## Live known data issues

There are no live known data issues for AddressBase at this time.

{% hint style="info" %}
To report an issue not currently listed here, please visit the ['Contact us' page on the OS website](https://www.ordnancesurvey.co.uk/contact-us/business-government/use-os-data).
{% endhint %}


# AddressBase Core Documentation

Here you will find all documentation for the AddressBase Core product.

Local Authority data is at the heart of AddressBase Core. This data provides you with a complete address product; access to over 33 million addresses each unique referenced with the Unique Property Reference Number (UPRN) and property level coordinates.

{% hint style="info" %}
**This product is updated weekly.**
{% endhint %}

<figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FzHxBEHBSZemNhjsr5lcD%2FABCore_Cover.webp?alt=media&amp;token=ba571c25-439c-4db4-80f1-5dbee5952a8f" alt="Representation of AddressBase Core data showing several types of address classifications clustered in a single area" width="563"><figcaption><p>Representation of AddressBase Core data showing several types of address classifications.</p></figcaption></figure>

AddressBase Core takes many of the important elements from the other AddressBase products, such as coordinates, classification and cross-references to connect address information to other products via key identifiers.

AddressBase Core's primary source of addressing information is Local Authority data from the National Land and Property Gazetteer (NLPG) and One Scotland Gazetteer (OSG). They have the legal responsibility to capture and maintain address data for Great Britain, so you are assured of its authenticity and legal nature.

Address information is provided in an easy-to-use format alongside a single line attribute which concatenates all the address elements into what you would expect to see on an envelope. It is updated weekly and is offered in an easier to digest format to make the product as easy to access and use as possible.

Customers have asked for easy file formats, so CSV and GeoPackage are available for this product, with headers included – removing the need for any post-processing. Simply load, or drag and drop into a GIS package to start analysing.

{% tabs %}
{% tab title="Benefits" %}
**Approved addressing records**

AddressBase Core provides approved addressing records for England, Wales and Scotland based on Local Authority holdings of the National Land and Property Gazetteer (NLPG) and One Scotland Address Gazetteer (OSG). Other attribution includes property-level coordinates and secondary level classifications (detailing the use and type of an address).

**Property classification**

Through property classification attributes, you can quickly understand, locate and perform analysis on the type of addresses you want to interact with.

**Authoritative data**

AddressBase Core's primary source of addressing information is local authority data. They have the legal responsibility to capture and maintain address data for Great Britain, so you can be sure of its authenticity and legal nature.

**Weekly updates**

AddressBase Core is released weekly, keeping you more up to date with changes.
{% endtab %}

{% tab title="Use Cases" %}
**Property classification**

Making the most of the property classification attributes, you can quickly understand, locate and perform analysis on the type of addresses you want to interact with.

**Easy cross-referencing**

AddressBase Core makes it easier to locate, match and gain insights from other location data with the benefit of having  key identifiers referenced throughout. The Unique Property Reference Number (UPRN), Unique Street Reference Number (USRN) and Topographic Identifier (TOID) allow users to reference to other OS products.
{% endtab %}

{% tab title="Summary" %}

* **Access:** Download via the [OS Data Hub](https://osdatahub.os.uk/)
* **Data theme:** Address
* **Data structure:** Vector – Points
* **Coverage:** Great Britain
* **Scale:** 1:1 250 to 1:10 000
* **Format:** CSV, GeoPackage
* **Ordering area:** All of Great Britain or customisable area (5km² tiles or user-defined polygon)
* **Publication:** Weekly
  {% endtab %}

{% tab title="Additional Information" %}
**Advantage of AddressBase Core over other AddressBase products**

AddressBase Core takes many of the high importance items from the other AddressBase products, such as coordinates, classifications (type of address) and links to other important identifiers; but it also includes a single attribute for an address line, is updated weekly, and is offered in an easier to digest format to make the product as easy to access and use as possible.

**Properties yet to be built or have been demolished**

Properties yet to be built, or those which have been demolished, do not appear in AddressBase Core. In order to keep AddressBase Core as simple as possible, these records are not present. If these are critical to you, please look at AddressBase Premium.

**AddressBase Core epoch correspondence**

AddressBase Core is released weekly and has a different data extraction date compared to the 6-weekly release schedule of the other AddressBase products. Due to these differences, AddressBase Core will not correspond to any of the epochs.

**Coverage of AddressBase Core**

AddressBase Core covers Great Britain only, i.e. England, Wales and Scotland. It does not include Northern Ireland and the Channel Islands.

**Data from Royal Mail’s PAF**

The database is a vital component of the single address gazetteer database and is in each of the AddressBase products where there has been a match confirming the address to the LLPG address.
{% endtab %}
{% endtabs %}

## How to get this product

Access to this product is free for PSGA (Public Sector Geospatial Agreement) Members. You can [check if your organisation is a member of the PSGA on the OS website](https://www.ordnancesurvey.co.uk/customers/public-sector/psga-member-finder).

The [AddressBase Core product page on the OS website](https://www.ordnancesurvey.co.uk/products/addressbase-core) has advice on how to get the product for businesses, developers, OS Partners and PSGA Members (i.e. government and the public sector).

Alternatively, you can try out the full product for free for three months by applying for [a Data Exploration licence](https://www.ordnancesurvey.co.uk/licensing/data-exploration-licence); this licence is primarily designed for organisations either considering becoming an OS Partner or who want to trial OS Premium data before working with an existing OS Partner.

## Sample data

### Download AddressBase Core sample data <a href="#download-os-egs-sample-data" id="download-os-egs-sample-data"></a>

You can download sample data for the product for free from the [OS Data Hub](https://osdatahub.os.uk/data/downloads/sample/AddressBaseCore). The sample data are available in CSV format and cover one area (Exeter).

### Visualise AddressBase Core sample data online

This product is available to try out free online using one of our three sets of sample data (Exeter, Newport and Inverness) through the OS MasterMap Product Viewer:

<table data-view="cards" data-full-width="false"><thead><tr><th></th><th></th><th data-hidden></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>OS MasterMap Product Viewer</strong></td><td>Interactive demonstrator of OS MasterMap Generation data</td><td></td><td data-object-fit="cover" data-alt="Example image showing OS VectorMap Local product data over an urban area."><a href="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FcNsAjPzkb3JUfxlTSFGM%2FVectorMap-Local-1.png?alt=media&amp;token=5223a62e-33bb-4424-aa24-e5171eeef649">VectorMap-Local-1.png</a></td><td><a href="https://experience.arcgis.com/experience/20981dabcb14402687dccb437a4a78fb/">https://experience.arcgis.com/experience/20981dabcb14402687dccb437a4a78fb/</a></td></tr></tbody></table>

## What's next?

To access documentation and resources relating to this product, please refer to the following:

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><h4>AddressBase Core Lightning Talk</h4></td><td>A helpful introductory article hosted on our More than Maps platform providing additional information and context about using AddressBase Core data.</td><td></td><td><a href="https://docs.os.uk/more-than-maps/data-demonstrators/addressing-and-location-demonstrators/addressbase-core">https://docs.os.uk/more-than-maps/data-demonstrators/addressing-and-location-demonstrators/addressbase-core</a></td><td data-object-fit="cover" data-alt="Graphic showing the names of four of the addressing products: AddressBase, AddressBase Core, AddressBase Plus and AddressBase Premium."><a href="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FTXhIkG8xvAPSY5Kp62cK%2Fimage%20(2).png?alt=media&amp;token=918014b7-bd66-446a-8e55-065527247b49">image (2).png</a></td></tr><tr><td><h4>Overview</h4></td><td>The Overview introduces AddressBase Core, giving context for all users – highlighting key features, providing examples of potential uses, and listing details such as file sizes, supply formats, etc.</td><td></td><td><a href="https://docs.os.uk/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-overview">https://docs.os.uk/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-overview</a></td><td data-object-fit="cover" data-alt="Example image showing AddressBase Core product data over a background map."><a href="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FSi5V3hnnUXRtrL9SC7Y1%2FHeader%20Image.png?alt=media&amp;token=a7a17e8c-b1f4-46d8-8f58-6e9401434707">Header Image.png</a></td></tr><tr><td><h4>Getting Started Guide</h4></td><td>The getting started guide provides instructions for using AddressBase Core in different software applications. Users with limited technical knowledge will be able to follow this guide.</td><td></td><td><a href="/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-getting-started-guide">AddressBase Core Getting Started Guide</a></td><td data-object-fit="cover" data-alt="Example image showing AddressBase Core product data over a background map."><a href="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FANnzizF07oRdUTZJEVks%2FLA%20completeness.png?alt=media&amp;token=ac7c442e-e6ad-4ada-91ab-a190aa25a1d5">LA completeness.png</a></td></tr><tr><td><h4>Technical Specification</h4></td><td>The technical specification provides detailed technical information about AddressBase Core. It is targeted at technical users and software developers.</td><td></td><td><a href="/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-technical-specification">AddressBase Core Technical Specification</a></td><td data-object-fit="cover" data-alt="Example image showing AddressBase Core product data over a background map."><a href="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FQsHRrOZKao0bTcLaaYWy%2Fcross%20ref.png?alt=media&amp;token=4cd57c91-8e06-4dc3-87da-2a1376251409">cross ref.png</a></td></tr><tr><td><h4>Downloads</h4></td><td>The downloads page provides links and resources to support the application of AddressBase Core within your environment.</td><td></td><td><a href="/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-downloads">AddressBase Core Downloads</a></td><td></td></tr><tr><td><h4>Ordnance Survey Website</h4></td><td>View AddressBase Core product information and find out how to get this product on the OS website.</td><td></td><td><a href="https://www.ordnancesurvey.co.uk/products/addressbase-core">https://www.ordnancesurvey.co.uk/products/addressbase-core</a></td><td></td></tr></tbody></table>

{% hint style="info" %}
New users should start with the Overview to gain high-level insight into the product. The Getting Started Guide will help you to begin using product data in different software systems. The Technical Specification contains detailed technical insights.
{% endhint %}


# Release Notes

Release notes listed here provide information about the current release of AddressBase Core and the previous nine releases.

{% hint style="info" %}
Any interruptions or data issues impacting the AddressBase Core product will be documented on the [AddressBase Core Data Issues, Service Disruption and Planned Maintenance page](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-data-issues-service-disruptions-and-planned-maintenance).
{% endhint %}

## [AddressBase Core – 20 October 2026 release note](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/release-notes/20-october-2026)

This release note provides information about the 20 October 2026 release of AddressBase Core.

## [AddressBase Core - 13 October 2026 release note](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/release-notes/13-october-2026)

This release note provides information about the 13 October 2026 release of AddressBase Core.&#x20;

## [AddressBase Core – 06 October 2026 release note](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/release-notes/06-october-2026)

This release note provides information about the 06 October 2026 release of AddressBase Core.

## [AddressBase Core – 29 September 2026 release note](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/release-notes/29-september-2026)

This release note provides information about the 29 September 2026 release of AddressBase Core.

## [AddressBase Core – 22 September 2026 release note](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/release-notes/22-september-2026)

This release note provides information about the 22 September 2026 release of AddressBase Core.

## [AddressBase Core – 15 September 2026 release note](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/release-notes/15-september-2026)

This release note provides information about the 15 September 2026 release of AddressBase Core.

## [AddressBase Core – 08 September 2026 release note](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/release-notes/08-september-2026)

This release note provides information about the 08 September 2026 release of AddressBase Core.

## [Address Base Core – 01 September 2026 release note](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/release-notes/01-september-2026)

This release note provides information about the 01 September 2026 release of AddressBase Core.

## [Address Base Core – 25 August 2026 release note](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/release-notes/01-september-2026)

This release note provides information about the 25 August 2026 release of AddressBase Core.

## [AddressBase Core – 18 August 2026 release note](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/release-notes/18-august-2026)

This release note provides information about the 18 August 2026 release of AddressBase Core.


# 20 October 2026

This release note provides information about the release of the AddressBase Core product on 20 October 2026.

## Record counts

| Product          | Full Supply Record Count | Change-Only Update Record Count |
| ---------------- | ------------------------ | ------------------------------- |
| AddressBase Core | 35 034 540               | 29 722                          |

**Please note that the Full Supply record count is based on a Managed Great Britain Set (MGBS). If you ordered your national coverage via the online ordering system using a polygon outline, your counts may differ.**

## Product supply comparison

There is a difference in record counts between taking a national Managed Great Britain Set (MGBS) and the national 5km tile supply. This is because the two supplies use different selection criteria. The difference in record counts is shown in the following table, allowing you to validate your data holdings once you have loaded the latest release of AddressBase Core.

| Product          | MGBS Full Count | National 5km Tiled Supply | Difference |
| ---------------- | --------------- | ------------------------- | ---------- |
| AddressBase Core | 35 034 540      | 35 034 526                | 14         |

A small difference in record counts is expected due to there being several features supplied in the MGBS which fall outside of the tiled area.

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase Core product, you will receive Insert, Update and Delete records within the supplied file. The following table details the numbers of these records which can be expected in the COU supply of the product:

| Change Type                  | Count  |
| ---------------------------- | ------ |
| Inserts                      | 6 420  |
| Updates                      | 20 303 |
| Deletes                      | 2 999  |
| COU populated 5km tile count | 3 177  |

It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the '[Working with COU data' page in the AddressBase Core Getting Started Guide](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-getting-started-guide/working-with-cou-data).

## Source data currency

The following information relates to the currency of the source data used in the creation of this release of AddressBase Core:

| Data Source                            | Date              |
| -------------------------------------- | ----------------- |
| Royal Mail Postcode Address File (PAF) | 15 October 2026   |
| National Land and Property Gazetteer   | 15 October 2026   |
| One Scotland Gazetteer                 | 11 September 2026 |
| OS MasterMap Topography Layer          | 14 September 2026 |

## Known data issues

Details of data issues, service disruptions and planned maintenance for AddressBase Core will be communicated on the [AddressBase Core Data Issues, Service Disruption and Planned Maintenance page](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-data-issues-service-disruptions-and-planned-maintenance); this page will provide details of the impacts of any data issues, plus updates on the expected timeframe for resolution.


# 13 October 2026

This release note provides information about the release of the AddressBase Core product on 13 October 2026.

## Record counts

| Product          | Full Supply Record Count | Change-Only Update Record Count |
| ---------------- | ------------------------ | ------------------------------- |
| AddressBase Core | 35 031 119               | 39 476                          |

**Please note that the Full Supply record count is based on a Managed Great Britain Set (MGBS). If you ordered your national coverage via the online ordering system using a polygon outline, your counts may differ.**

## Product supply comparison

There is a difference in record counts between taking a national Managed Great Britain Set (MGBS) and the national 5km tile supply. This is because the two supplies use different selection criteria. The difference in record counts is shown in the following table, allowing you to validate your data holdings once you have loaded the latest release of AddressBase Core.

| Product          | MGBS Full Count | National 5km Tiled Supply | Difference |
| ---------------- | --------------- | ------------------------- | ---------- |
| AddressBase Core | 35 031 119      | 35 031 105                | 14         |

A small difference in record counts is expected due to there being several features supplied in the MGBS which fall outside of the tiled area.

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase Core product, you will receive Insert, Update and Delete records within the supplied file. The following table details the numbers of these records which can be expected in the COU supply of the product:

| Change Type                  | Count  |
| ---------------------------- | ------ |
| Inserts                      | 8 398  |
| Updates                      | 28 326 |
| Deletes                      | 2 752  |
| COU populated 5km tile count | 3 254  |

It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the '[Working with COU data' page in the AddressBase Core Getting Started Guide](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-getting-started-guide/working-with-cou-data).

## Source data currency

The following information relates to the currency of the source data used in the creation of this release of AddressBase Core:

| Data Source                            | Date              |
| -------------------------------------- | ----------------- |
| Royal Mail Postcode Address File (PAF) | 08 October 2026   |
| National Land and Property Gazetteer   | 08 October 2026   |
| One Scotland Gazetteer                 | 04 September 2026 |
| OS MasterMap Topography Layer          | 14 September 2026 |

## Known data issues

Details of data issues, service disruptions and planned maintenance for AddressBase Core will be communicated on the [AddressBase Core Data Issues, Service Disruption and Planned Maintenance page](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-data-issues-service-disruptions-and-planned-maintenance); this page will provide details of the impacts of any data issues, plus updates on the expected timeframe for resolution.


# 06 October 2026

This release note provides information about the release of the AddressBase Core product on 06 October 2026.

## Record counts

| Product          | Full Supply Record Count | Change-Only Update Record Count |
| ---------------- | ------------------------ | ------------------------------- |
| AddressBase Core | 35 025 473               | 47 631                          |

**Please note that the Full Supply record count is based on a Managed Great Britain Set (MGBS). If you ordered your national coverage via the online ordering system using a polygon outline, your counts may differ.**

## Product supply comparison

There is a difference in record counts between taking a national Managed Great Britain Set (MGBS) and the national 5km tile supply. This is because the two supplies use different selection criteria. The difference in record counts is shown in the following table, allowing you to validate your data holdings once you have loaded the latest release of AddressBase Core.

| Product          | MGBS Full Count | National 5km Tiled Supply | Difference |
| ---------------- | --------------- | ------------------------- | ---------- |
| AddressBase Core | 35 025 473      | 35 025 459                | 14         |

A small difference in record counts is expected due to there being several features supplied in the MGBS which fall outside of the tiled area.

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase Core product, you will receive Insert, Update and Delete records within the supplied file. The following table details the numbers of these records which can be expected in the COU supply of the product:

| Change Type                  | Count  |
| ---------------------------- | ------ |
| Inserts                      | 8 193  |
| Updates                      | 37 382 |
| Deletes                      | 2 056  |
| COU populated 5km tile count | 3 217  |

It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the '[Working with COU data' page in the AddressBase Core Getting Started Guide](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-getting-started-guide/working-with-cou-data).

## Source data currency

The following information relates to the currency of the source data used in the creation of this release of AddressBase Core:

| Data Source                            | Date              |
| -------------------------------------- | ----------------- |
| Royal Mail Postcode Address File (PAF) | 01 October 2026   |
| National Land and Property Gazetteer   | 01 October 2026   |
| One Scotland Gazetteer                 | 27 September 2026 |
| OS MasterMap Topography Layer          | 14 September 2026 |

## Known data issues

Details of data issues, service disruptions and planned maintenance for AddressBase Core will be communicated on the [AddressBase Core Data Issues, Service Disruption and Planned Maintenance page](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-data-issues-service-disruptions-and-planned-maintenance); this page will provide details of the impacts of any data issues, plus updates on the expected timeframe for resolution.


# 29 September 2026

This release note provides information about the release of the AddressBase Core product on 29 September 2026.

## Record counts

| Product          | Full Supply Record Count | Change-Only Update Record Count |
| ---------------- | ------------------------ | ------------------------------- |
| AddressBase Core | 35 019 336               | 46 878                          |

**Please note that the Full Supply record count is based on a Managed Great Britain Set (MGBS). If you ordered your national coverage via the online ordering system using a polygon outline, your counts may differ.**

## Product supply comparison

There is a difference in record counts between taking a national Managed Great Britain Set (MGBS) and the national 5km tile supply. This is because the two supplies use different selection criteria. The difference in record counts is shown in the following table, allowing you to validate your data holdings once you have loaded the latest release of AddressBase Core.

| Product          | MGBS Full Count | National 5km Tiled Supply | Difference |
| ---------------- | --------------- | ------------------------- | ---------- |
| AddressBase Core | 35 019 336      | 35 019 322                | 14         |

A small difference in record counts is expected due to there being several features supplied in the MGBS which fall outside of the tiled area.

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase Core product, you will receive Insert, Update and Delete records within the supplied file. The following table details the numbers of these records which can be expected in the COU supply of the product:

| Change Type                  | Count  |
| ---------------------------- | ------ |
| Inserts                      | 8 739  |
| Updates                      | 34 754 |
| Deletes                      | 3 385  |
| COU populated 5km tile count | 3 392  |

It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the '[Working with COU data' page in the AddressBase Core Getting Started Guide](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-getting-started-guide/working-with-cou-data).

## Source data currency

The following information relates to the currency of the source data used in the creation of this release of AddressBase Core:

| Data Source                            | Date              |
| -------------------------------------- | ----------------- |
| Royal Mail Postcode Address File (PAF) | 24 September 2026 |
| National Land and Property Gazetteer   | 24 September 2026 |
| One Scotland Gazetteer                 | 20 September 2026 |
| OS MasterMap Topography Layer          | 10 August 2026    |

## Known data issues

Details of data issues, service disruptions and planned maintenance for AddressBase Core will be communicated on the [AddressBase Core Data Issues, Service Disruption and Planned Maintenance page](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-data-issues-service-disruptions-and-planned-maintenance); this page will provide details of the impacts of any data issues, plus updates on the expected timeframe for resolution.


# 22 September 2026

This release note provides information about the release of the AddressBase Core product on 22 September 2026.

## Record counts

| Product          | Full Supply Record Count | Change-Only Update Record Count |
| ---------------- | ------------------------ | ------------------------------- |
| AddressBase Core | 35 013 982               | 73 152                          |

**Please note that the Full Supply record count is based on a Managed Great Britain Set (MGBS). If you ordered your national coverage via the online ordering system using a polygon outline, your counts may differ.**

## Product supply comparison

There is a difference in record counts between taking a national Managed Great Britain Set (MGBS) and the national 5km tile supply. This is because the two supplies use different selection criteria. The difference in record counts is shown in the following table, allowing you to validate your data holdings once you have loaded the latest release of AddressBase Core.

| Product          | MGBS Full Count | National 5km Tiled Supply | Difference |
| ---------------- | --------------- | ------------------------- | ---------- |
| AddressBase Core | 35 013 982      | 35 013 968                | 14         |

A small difference in record counts is expected due to there being several features supplied in the MGBS which fall outside of the tiled area.

## Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase Core product, you will receive Insert, Update and Delete records within the supplied file. The following table details the numbers of these records which can be expected in the COU supply of the product:

| Change Type                  | Count  |
| ---------------------------- | ------ |
| Inserts                      | 7 360  |
| Updates                      | 63 809 |
| Deletes                      | 1 983  |
| COU populated 5km tile count | 3 561  |

It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the '[Working with COU data' page in the AddressBase Core Getting Started Guide](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-getting-started-guide/working-with-cou-data).

## Source data currency

The following information relates to the currency of the source data used in the creation of this release of AddressBase Core:

| Data Source                            | Date              |
| -------------------------------------- | ----------------- |
| Royal Mail Postcode Address File (PAF) | 17 September 2026 |
| National Land and Property Gazetteer   | 17 September 2026 |
| One Scotland Gazetteer                 | 13 September 2026 |
| OS MasterMap Topography Layer          | 10 August 2026    |

## Known data issues

Details of data issues, service disruptions and planned maintenance for AddressBase Core will be communicated on the [AddressBase Core Data Issues, Service Disruption and Planned Maintenance page](/os-downloads/products/addresses-and-names-portfolio/addressbase-core/addressbase-core-data-issues-service-disruptions-and-planned-maintenance); this page will provide details of the impacts of any data issues, plus updates on the expected timeframe for resolution.




---

[Next Page](https://docs.os.uk/os-downloads/llms-full.txt/1)