> 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/os-mastermap-greenspace-layer-technical-specification.md).
# OS MasterMap Greenspace Layer Technical Specification
This technical specification provides detailed technical information about OS MasterMap Greenspace Layer. It is targeted at technical users and software developers.
OS MasterMap Greenspace Layer gives a comprehensive view of the greenspaces within an urban area. The dataset consists of topographic areas published in OS MasterMap Topography Layer, with additional greenspace-specific attribution to describe their function. It includes both publicly accessible and private greenspaces. This product has been designed for Public Sector Geospatial Agreement (PSGA) customers.
OS MasterMap Greenspace Layer data overlaid on OS MasterMap Topography Layer
## Index
The OS MasterMap Greenspace Layer technical specification contains the following sections:
* [Product classification and structure](/os-downloads/products/land-and-terrain-portfolio/os-mastermap-greenspace-layer/os-mastermap-greenspace-layer-technical-specification/product-classification-and-structure.md)
* [Feature types](/os-downloads/products/land-and-terrain-portfolio/os-mastermap-greenspace-layer/os-mastermap-greenspace-layer-technical-specification/feature-types.md)
* [Code lists and Enumerations](/os-downloads/products/land-and-terrain-portfolio/os-mastermap-greenspace-layer/os-mastermap-greenspace-layer-technical-specification/code-lists-and-enumerations.md)
* [Function hierarchy](/os-downloads/products/land-and-terrain-portfolio/os-mastermap-greenspace-layer/os-mastermap-greenspace-layer-technical-specification/code-lists-and-enumerations/function.md)
* [Form hierarchy](/os-downloads/products/land-and-terrain-portfolio/os-mastermap-greenspace-layer/os-mastermap-greenspace-layer-technical-specification/form-hierarchy.md)
* [OS Open Greenspace lookup table](/os-downloads/products/land-and-terrain-portfolio/os-mastermap-greenspace-layer/os-mastermap-greenspace-layer-technical-specification/os-open-greenspace-lookup-table.md)
* [GML overview](/os-downloads/products/land-and-terrain-portfolio/os-mastermap-greenspace-layer/os-mastermap-greenspace-layer-technical-specification/gml-overview.md)
* [ESRI shapefile overview](/os-downloads/products/water-portfolio/os-open-rivers/os-open-rivers-technical-specification/esri-shapefile-overview.md)
* [GeoPackage overview](/os-downloads/products/land-and-terrain-portfolio/os-mastermap-greenspace-layer/os-mastermap-greenspace-layer-technical-specification/geopackage-overview.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-mastermap-greenspace-layer/os-mastermap-greenspace-layer-technical-specification.md?ask=&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.
