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

# raildescriptionvalue

This code list is used in association with the Description attribute which is present within the Rail Feature Type. The code list describes the type of land the rail feature is used for; this may be to change the direction of a train, to slow trains down, or the general area that trains traverse along.

| Label               | Definition                                                                                                                                                    |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Railway Traverse    | A structure within a railway marshalling yard used to switch carriages or engines from railway track to railway track using a perpendicular series of tracks. |
| Made Surface        | A surface that has been enhanced through application of either a loose material, such as gravel, or a solid bonded material, such as concrete.                |
| Sloping Masonry     | A wall whose face is angled from the perpendicular.                                                                                                           |
| Transport Curtilage | The area of land attached as a boundary to a road or pavement.                                                                                                |
| Turntable           | A large flat metal area at ground level on which a train engine can be turned around or directed onto a different track.                                      |


---

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