> 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-open-greenspace/os-open-greenspace-technical-specification.md).

# OS Open Greenspace Technical Specification

This technical specification provides detailed technical information about OS Open Greenspace. It is targeted at technical users and software developers.

OS Open Greenspace depicts the location and extent of greenspaces, such as parks and sports facilities, which are likely to be accessible to the public. Where appropriate, it also includes access points to show how to get into these sites. Its primary purpose is to enable members of the public to find and access greenspaces near them for exercise and recreation.

OS Open Greenspace is an OpenData product. It is part of the OS OpenData portfolio, which currently consists of a range of datasets, such as [OS VectorMap District](/os-downloads/products/maps-and-imagery-portfolio/os-vectormap-district.md), [OS Open Map – Local](/os-downloads/products/maps-and-imagery-portfolio/os-openmap-local.md), [OS Terrain 50](/os-downloads/products/land-and-terrain-portfolio/os-terrain-50.md), and [OS Open Roads](/os-downloads/products/transport-network-portfolio/os-open-roads.md). For more information on the OpenData portfolio, see the [OS OpenData Downloads page of the OS Data Hub](https://osdatahub.os.uk/downloads/open).

<figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2F2zJ4cX3CuvNiycHBnSgq%2F1.jpeg?alt=media" alt="Example map showing OS Open Greenspace polygons and access points overlaid on an OS OpenMap – Local basemap. The polygons depict areas of greenspace while the points depict access points into the greenspace areas."><figcaption><p>OS Open Greenspace polygons and Access Points overlaid on an OS OpenMap – Local basemap.</p></figcaption></figure>

## Formats <a href="#bookmark11" id="bookmark11"></a>

OS Open Greenspace is available in the following formats:

* Geography Markup Language (GML) 3.2.1
* Esri shapefile
* GeoPackage
* Vector tiles (MBTiles)

## Index <a href="#bookmark25" id="bookmark25"></a>

* [Data structure](/os-downloads/products/land-and-terrain-portfolio/os-open-greenspace/os-open-greenspace-technical-specification/data-structure.md)
* [Feature types](/os-downloads/products/land-and-terrain-portfolio/os-open-greenspace/os-open-greenspace-technical-specification/feature-types.md)
* [Code lists](/os-downloads/products/land-and-terrain-portfolio/os-open-greenspace/os-open-greenspace-technical-specification/code-lists.md)
* [GML overview](/os-downloads/products/land-and-terrain-portfolio/os-open-greenspace/os-open-greenspace-technical-specification/gml-overview.md)
* [GeoPackage overview](/os-downloads/products/land-and-terrain-portfolio/os-open-greenspace/os-open-greenspace-technical-specification/geopackage-overview.md)
* [Vector tiles overview](/os-downloads/products/land-and-terrain-portfolio/os-open-greenspace/os-open-greenspace-technical-specification/vector-tiles-overview.md)
* [Attribute mapping](/os-downloads/products/land-and-terrain-portfolio/os-open-greenspace/os-open-greenspace-technical-specification/attribute-mapping.md)


---

# 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-open-greenspace/os-open-greenspace-technical-specification.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.