> 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/~/changes/AJZwzCsyrD9hiTbOxIbO/topography/os-mastermap-greenspace-layer/os-mastermap-greenspace-layer-technical-specification/code-lists-and-enumerations/form.md).

# Form

## **Code List: Form**

Value defining the land cover of the greenspace feature.

| Code               | Description                                                                                                                                                                                                                                                                           |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Woodland           | Areas of land covered with trees with an area size larger than 0.1hectares and width greater than 5m.                                                                                                                                                                                 |
| Open Semi-Natural  | Areas of undeveloped or previously developed land with natural habitats (except woodland) for example, scrub, heath and rough grassland.                                                                                                                                              |
| Inland Water       | Static water bodies (for example, reservoirs, lakes and ponds) and rivers above the normal tidal limit.                                                                                                                                                                               |
| Beach Or Foreshore | Areas of beach above the tidal minimum low tide (for example, sand and shingle).                                                                                                                                                                                                      |
| Manmade Surface    | Manmade areas within sites used for exercise and recreation (for example, paths and car parks within a public park).                                                                                                                                                                  |
| Multi-Surface      | Polygons which may be comprised of multiple surface types, such as grass, decking and hard standing making up a private garden polygon. This applies to Private Gardens\* and is generated from the Topography Layer Descriptive Term of Multi-Surface for the corresponding polygon. |

\* While most polygons with this form will have a primary function of Private Gardens, this will not always be the case due to the [Function Hierarchy](/os-downloads/~/changes/AJZwzCsyrD9hiTbOxIbO/topography/os-mastermap-greenspace-layer/os-mastermap-greenspace-layer-technical-specification/function-hierarchy.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/~/changes/AJZwzCsyrD9hiTbOxIbO/topography/os-mastermap-greenspace-layer/os-mastermap-greenspace-layer-technical-specification/code-lists-and-enumerations/form.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.