> 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/land-and-terrain-portfolio/os-mastermap-sites-layer/release-notes/october-2025.md).

# October 2025

This release note provides information about the October 2025 release of OS MasterMap Sites Layer.

OS MasterMap Sites Layer provides a nationally consistent representation of polygon features that represent the area or extent of certain types of function or activity in Sites with the appropriate attribution. The product also includes Access Points to assist users in navigating into and out of the Sites (with references to the OS MasterMap Highways Network – Roads product).

## Feature type counts

<table><thead><tr><th width="205">Feature Type</th><th>Previous Release Count (April 2025)</th><th>New Release Count (October 2025)</th></tr></thead><tbody><tr><td>Functional Site (TOIDs)</td><td>49 076</td><td>49 197</td></tr><tr><td>Access Point (TOIDs)</td><td>148 525</td><td>148 592</td></tr><tr><td>Routing Point (TOIDs)</td><td>0</td><td>0</td></tr></tbody></table>

{% hint style="warning" %}
Routing Points are no longer supplied from the October 2023 release onwards (see the 'Product improvements' section below for full details).
{% endhint %}

## Known data issues

There are no significant issues that would impair the use of this product in the October 2025 release. However, two minor errors have been identified with the release that users should be aware of – please see the [OS MasterMap Sites Layer Known Data Issues and Service Disruptions page](https://docs.os.uk/os-downloads/products/land-and-terrain-portfolio/os-mastermap-sites-layer/os-mastermap-sites-layer-known-data-issues-and-service-disruptions.md) for details. This page provides details of the impacts of the data issues and updates on the expected time frame for their resolution; it also mentions any current service disruption to the product.

## Product improvements

To meet customer needs, Ordnance Survey has created a fully routable multi-modal network, and a key element of this is to provide more usable data about the access to destinations. To this end, we are now directly splitting our Road, Track and Path data where Access Link features connect to the network; this will allow customers to more easily route into Sites using OS network data.

Whereas previously some Access Points referenced Routing Points, all will now reference a Road Node from the OS MasterMap Highways Network – Roads product. Consequently, there is no requirement for Routing Point features, and these features are no longer suppled as part of the OS MasterMap Sites Layer product.

**As a result, the Routing Point layer has not been supplied from the October 2023 publication onwards.**

For customers that use Geography Markup Language (GML) format, there is no change to the schema, so product loading should be unaffected. However, please be aware that for customers using GeoPackage, no table for Routing Points is provided, and similarly for the vector tiles format, no layer is provided for Routing Points.

## Next release

The next release of OS MasterMap Sites Layer is scheduled for **April 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/land-and-terrain-portfolio/os-mastermap-sites-layer/release-notes/october-2025.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.
