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

# railwayusevalue

This code list is used in association with the Railway Use attribute which is present within the Railway Link Feature Type. The code list describes the intended use for a railway.

| Label                 | Definition                                                                                                   |
| --------------------- | ------------------------------------------------------------------------------------------------------------ |
| Amusement             | A railway line serving as a tourist attraction, e.g. a miniature railway.                                    |
| Freight               | A main line railway dedicated to the movement of freight rolling stock.                                      |
| Freight And Passenger | A main line railway for the movement of freight and passenger rolling stock                                  |
| Mineral               | A railway line serving quarry rolling stock for the movement of mined minerals, e.g. coal, slate or granite. |
| Passenger             | A main line railway dedicated to the movement of passenger rolling stock.                                    |
| Preserved             | A preserved railway line serving as a tourist attraction, e.g. a railway line dedicated to steam locomotive. |


---

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