> 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-linked-identifiers/release-notes/september-2025-epoch-46.md).

# September 2025 – Epoch 46

This release note provides information about the September 2025 release (Epoch 46) of OS Open Linked Identifiers.

No issues were identified in this release.

## Feature count

The feature count for Epoch 46 is as follows:

| Feature                                  | Feature count |
| ---------------------------------------- | ------------- |
| BLPU\_UPRN\_ROADLINK\_TOID\_9            | 41 294 125    |
| BLPU\_UPRN\_STREET\_USRN\_11             | 42 017 141    |
| BLPU\_UPRN\_TOPOGRAPHICAREA\_TOID\_5     | 41 294 860    |
| ORROADLINK\_GUID\_ROADLINK\_TOID\_12     | 6 743 116     |
| ORROADNODE\_GUID\_ROADLINK\_TOID\_13     | 40 798        |
| ROAD\_TOID\_STREET\_USRN\_10             | 1 306 334     |
| ROAD\_TOID\_TOPOGRAPHICAREA\_TOID\_3     | 6 242 648     |
| ROADLINK\_TOID\_ROAD\_TOID\_7            | 6 010 407     |
| ROADLINK\_TOID\_STREET\_USRN\_8          | 8 942 448     |
| ROADLINK\_TOID\_TOPOGRAPHICAREA\_TOID\_2 | 14 580 525    |
| STREET\_USRN\_TOPOGRAPHICAREA\_TOID\_4   | 9 478 912     |
| **Grand Total**                          | 177 951 314   |

## Next release

The next release of OS Open Linked Identifiers, Epoch 47, is scheduled for **16 October 2025**.


---

# 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-linked-identifiers/release-notes/september-2025-epoch-46.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.