> 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/resources/product-resources/end-of-life-product-documentation/os-detailed-path-network/os-detailed-path-network-technical-specification/code-lists/levelcodevalue.md).

# LevelCodeValue

The LevelCode value is used to indicate when a route is above or below normal ground level. The attribute is only applied where the level difference extends for distances greater than approximately 50m.

Routes that cross at different levels are not split at the intersection; those that are in tunnels or on bridges less than 50m long are given the default LevelCode attribute of Surface Level.

| Value                            | Description                                                                                                                                                                                                                                        |
| -------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Surface Level                    | The route is at the same level as the surrounding terrain. This is the default value for RouteLink features.                                                                                                                                       |
| Above Surface Level On Structure | <p>The RouteLink is supported or suspended above ground level on a manmade structure that extends for more than 50m.</p><p>For example, a road, track or path may be on a bridge, footbridge or viaduct.</p>                                       |
| Below Surface Level Tunnel       | The route passes through a specially built construction underneath the normal terrain surface primarily to avoid or reduce the effect of the terrain surface or to avoid an obstruction such as a river or mountain and extends for more than 50m. |

The LevelCode value is used to indicate when a route is above or below normal ground level. The attribute is only applied where the level difference extends for distances greater than approximately 50m.

Routes that cross at different levels are not split at the intersection; those that are in tunnels or on bridges less than 50m long are given the default LevelCode attribute of Surface Level.

**Above surface level on structure – example**

<figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FlaWOo1GQbdNGANCnZMCl%2F10.jpeg?alt=media" alt="Photo showing an example of an &#x27;Above surface level on structure&#x27; feature, which in this case is a road over a viaduct."><figcaption><p>Example where a RouteLink is supported or suspended above ground level on a manmade structure.</p></figcaption></figure>

**Below surface level tunnel – example**

<figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FJ4noOFeVEzgr5aUbrVXl%2F11.jpeg?alt=media" alt="Photo showing an example of a below surface level tunnel."><figcaption><p>This route passes through a specially built construction underneath the normal terrain surface.</p></figcaption></figure>


---

# 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/resources/product-resources/end-of-life-product-documentation/os-detailed-path-network/os-detailed-path-network-technical-specification/code-lists/levelcodevalue.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.
