> For the complete documentation index, see [llms.txt](https://docs.os.uk/os-downloads/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.os.uk/os-downloads/~/changes/AJZwzCsyrD9hiTbOxIbO/addressing-and-location/addressbase-core/release-notes/03-december-2024.md).

# 03 December 2024

This release note provides information about the release of the AddressBase Core product on 03 December 2024.

## Record counts

| Product          | Full Supply record count0F\[\*] | Change-Only Update record count |
| ---------------- | ------------------------------- | ------------------------------- |
| AddressBase Core | 34 540 465                      | 32 496                          |

\[\*] These counts are 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 | 34 540 465      | 34 540 458                | 7          |

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 774  |
| Updates                      | 23 293 |
| Deletes                      | 2 429  |
| COU populated 5km tile count | 2 918  |

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/~/changes/AJZwzCsyrD9hiTbOxIbO/addressing-and-location/addressbase-core/addressbase-core-getting-started-guide/working-with-cou-data.md).

## 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) | 29 November 2024  |
| National Land and Property Gazetteer   | 29 November 2024  |
| One Scotland Gazetteer                 | 18 November 2024  |
| OS MasterMap Topography Layer          | 05 September 2024 |


---

# 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
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.os.uk/os-downloads/~/changes/AJZwzCsyrD9hiTbOxIbO/addressing-and-location/addressbase-core/release-notes/03-december-2024.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.