> 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/trackrepresentationvalue.md).

# trackrepresentationvalue

This code list is used in association with the Track Representation attribute which is present within the Railway Link Feature Type. The code list describes the various track types (for example, Multiple Tracks).

| Label           | Definition                                                                                                                                                                                                               |
| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Multiple Tracks | Multiple tracks are a group of two or more railway tracks which form part of the rail network and provide general transit use for multiple passenger and/or freight rolling stock.                                       |
| Siding          | A siding is a single railway track or multiple railway tracks which is a low-speed section of track generally used for storing rolling stock or for loading and unloading goods (e.g. in factories, ports and quarries). |
| Single Track    | A single track is a railway track which forms part of the rail network and provides general transit use for a passenger and/or freight rolling stock.                                                                    |


---

# 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/trackrepresentationvalue.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.