> 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/code-lists/code-lists-overview/parentfeaturetypevalue.md).

# parentfeaturetypevalue

This code list is used in association with the Boundary Parent Reference Feature Type attribute (of which, for some feature types, there are more than one, suffixed with a number) which is present in several feature types within the OS Boundaries Collection. The code list identifies the OS NGD feature type in which the parent boundary would reside. Examples include Lower Tier Local Authority, and Ward.

| Label                                | Definition               |
| ------------------------------------ | ------------------------ |
| Devolved Parliament Electoral Region | No definition available. |
| Electoral Division                   | No definition available. |
| Lower Tier Local Authority           | No definition available. |
| Parish Or Community                  | No definition available. |
| Regional Authority                   | No definition available. |
| Upper Tier Local Authority           | No definition available. |
| Ward                                 | No definition available. |


---

# 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/code-lists/code-lists-overview/parentfeaturetypevalue.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.