> 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/products/transport-network-portfolio/os-mastermap-highways-network-fundamentals/os-mastermap-highways-network-code-lists/formofwaterwaynodevalue.md).

# FormOfWaterwayNodeValue

This code list is present in OS MasterMap Highways Network – Roads and OS MasterMap Highways Network – Paths products. The FerryNode Feature Type is attributed with a 'formOfWaterwayNode' property with the data type of FormOfWaterwayNodeValue. The following table describes the codes used to populate this field.

{% hint style="info" %}
The code list has been inherited from INSPIRE and is not extendable.
{% endhint %}

## Code List: FormOfWaterwayNodeValue

Function of a Waterway Node in the water transport network.

{% embed url="<http://inspire.ec.europa.eu/codelist/FormOfWaterwayNodeValue>" %}

| Code           | Description                               |
| -------------- | ----------------------------------------- |
| water terminal | The location where goods are transhipped. |


---

# 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/products/transport-network-portfolio/os-mastermap-highways-network-fundamentals/os-mastermap-highways-network-code-lists/formofwaterwaynodevalue.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.