> 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-greenspace-layer/release-notes/october-2025.md).

# October 2025

The October 2025 release note for the OS MasterMap Greenspace Layer product

The OS MasterMap Greenspace Layer dataset has been designed for the public sector; it shows accessible and non-accessible green spaces in urban areas, helping to support a wider set of government initiatives around health and the environment.

## Feature count

<table data-full-width="false"><thead><tr><th width="174">Feature Type</th><th width="268.5999755859375">Previous Release Count (April 2025)</th><th>New Release Count (October 2025)</th></tr></thead><tbody><tr><td>Area</td><td>35 094 112</td><td>35 358 059</td></tr></tbody></table>

## Known data issues

Details of live and resolved data issues for OS MasterMap Greenspace Layer will be communicated on the [OS MasterMap Greenspace Layer known data issues page](/os-downloads/products/land-and-terrain-portfolio/os-mastermap-greenspace-layer/os-mastermap-greenspace-layer-known-data-issues.md). This page will provide details of their impacts and updates on the expected time frame for their resolution.

## Next release

The next release of OS MasterMap Greenspace 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-greenspace-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.