> 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/relationshiptypevalue.md).
# relationshiptypevalue
This code list is used in association with the Relationship Type attribute which is present within the Related Entity Related Component*.* The code list describes the type of spatial operation used to create the cross-reference link with the target dataset.
{% tabs %}
{% tab title="v2.0" %}
V2.0 of the code list will be released on 26 March 2026.
#### What's new?
One new value has been added to this code list for v2.0:
* Intersects – The source feature touches / overlaps the target feature.
The new value has a 'new' emoji (🆕) against it.
| **Label** | **Definition** |
| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Accessed From | A feature can be accessed from the related feature, for example, an AddressableObject can be accessed from a Road feature in the OS NGD Transport Network Theme. |
| :new: Intersects | The source feature touches / overlaps the target feature. |
| Nearest | Nearest related feature (spatially defined), for example, the nearest street to an Non-Addressable object. |
| Same As | The feature can be considered to represent the same real world feature, for example, NGD site is the same as the AddressableObject. |
| Within | Spatially within another feature, for example, AddressableObject point within an NGD Topo Area. |
| {% endtab %} | |
{% tab title="v1.0" %}
V1.0 of the code list was released on 02 November 2022.
| Label | Definition |
| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Within | Spatially within another feature, for example, AddressableObject point within an NGD Topo Area. |
| Same As | The feature can be considered to represent the same real world feature, for example, NGD site is the same as the AddressableObject. |
| Accessed From | A feature can be accessed from the related feature, for example, an AddressableObject can be accessed from a Road feature in the OS NGD Transport Network Theme. |
| Nearest | Nearest related feature (spatially defined), for example, the nearest street to an Non-Addressable object |
| {% endtab %} | |
| {% endtabs %} | |
---
# 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/relationshiptypevalue.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.