> For the complete documentation index, see [llms.txt](https://docs.os.uk/osngd/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/osngd/using-os-ngd-data/os-ngd-structures/field-boundary/field-boundary-feature-type.md).

# Field Boundary Feature Type

Field Boundary features are coincident with and reference all, or part of, an underlying Structure (Built Obstruction) Line. They represent physical barriers between adjoining areas of land. There are five distinct categories to describe Field Boundary features: Tree Canopy, Wooded Strip, Hedge, Wall, and Other. An 'Unknown' description is applied when a feature hasn’t yet been classified.

<figure><img src="https://170091638-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0pZjHxkAvY7Mn6TqFBMD%2Fuploads%2FSjC43Jic8a9aV7n279sR%2Fimage.png?alt=media&amp;token=f3455eea-c8ef-4177-a871-6a4a56ec9766" alt="Example map showing Field Boundary categories, including Tree Canopy, Wooded Strip, Hedge, Wall and Other. The data has been mapped to symbolic images that represent each field boundary description value. A background map has been included to provide context. "><figcaption><p>Example map showing Field Boundary categories, including Tree Canopy, Wooded Strip, Hedge, Wall and Other. The data has been mapped to symbolic images that represent each field boundary description value. A background map has been included to provide context. </p></figcaption></figure>

## Field Boundary descriptions

Field Boundary features are predominately classified across Rural and Moorland areas in Great Britain where they are adjacent to, or contained within, topographic areas of Agricultural Land, Trees, Rough Grassland or Heath, or when they are adjacent to land in the Rural Payment Agency’s (RPA) Rural Land Register (RLR) where they are situated within urban areas in England. Features adjacent to land in the RPA’s RLR are buffered by 2metres.

<figure><img src="https://170091638-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0pZjHxkAvY7Mn6TqFBMD%2Fuploads%2FqNf5ia48oCu8eIW10akQ%2Fimage.png?alt=media&amp;token=63a043f6-4530-4932-9e83-96a5c2d950ad" alt="Example map showing Field Boundary features and the adjacent topographic areas they typically surround. The data has been mapped to symbolic images that represent each field boundary description value. A background map has been included to provide context. "><figcaption><p>Example map showing Field Boundary features and the adjacent topographic areas they typically surround. The data has been mapped to symbolic images that represent each field boundary description value. A background map has been included to provide context. </p></figcaption></figure>

See the [Field Boundary Description Value Code List](https://docs.os.uk/osngd/code-lists/code-lists-overview/fieldboundarydescriptionvalue.md) for Field Boundary feature definitions.

{% hint style="info" %}
Water-based boundaries (for example, Ditches and Drains) are features within the OS NGD Water Theme and are therefore not categorised as Field Boundary features.&#x20;
{% endhint %}


---

# 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/osngd/using-os-ngd-data/os-ngd-structures/field-boundary/field-boundary-feature-type.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.
