> 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/products/buildings-and-infrastructure-portfolio/os-open-toid/release-notes/december-2025-epoch-48.md).

# December 2025 – Epoch 48

This release note provides information about the December 2025 release of OS Open TOID (Epoch 48).

## Feature counts

Feature counts for this release are provided in the following table:

| Product                       | Source Product  | CSV             | GeoPackage      |
| ----------------------------- | --------------- | --------------- | --------------- |
| OS MasterMap Sites Layer      | 49 197          | 49 197          | 49 197          |
| OS MasterMap Highways Network | 20 865 185      | 20 865 185      | 20 865 185      |
| OS MasterMap Topography Layer | 489 574 698     | 489 574 698     | 489 574 698     |
| **Total**                     | **510 489 080** | **510 489 080** | **510 489 080** |

There are no missing features and no duplicated TOIDs in this release. No significant errors have been identified.

## Next release

The next release of OS Open TOID (Epoch 49), is scheduled for **05 January 2026**.


---

# 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 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/products/buildings-and-infrastructure-portfolio/os-open-toid/release-notes/december-2025-epoch-48.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.

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.