> 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/using-os-ngd-data/os-ngd-transport/transport-networks-in-the-os-ngd/ferry-network.md).

# Ferry network

This page covers the three feature types of the OS ferry network (Ferry Link, Ferry Node and Ferry Terminal), which provide a view of connectivity across Great Britain via ferry.

If you want to build a more complete routing network of Great Britain, you can use the Ferry Terminal Feature Type to connect the ferry network to the road and path network.

### Ferry Link, Ferry Node and Ferry Terminal Feature Types

Ferries with both terminals in Great Britain and a timetabled service available to the public are captured in [OS Transport Network Collection](/osngd/data-structure/transport/transport-network.md) data and represented by the [Ferry Link](/osngd/data-structure/transport/transport-network/ferry-link.md), [Ferry Node](/osngd/data-structure/transport/transport-network/ferry-node.md) and [Ferry Terminal](/osngd/data-structure/transport/transport-network/ferry-terminal.md) Feature Types:

* **Ferry Links**: These are represented spatially as line features. Unlike road and path networks, Ferry Links do not necessarily represent the course of a ferry route but instead represent the connection between ferry terminals. Where a detailed alignment is provided, it's only an indication of the route a vessel would take. Attribution on Ferry Links includes the route operator of the ferry and a Boolean flag telling you if a ferry can be used by vehicles.
* **Ferry Nodes**: At each end of a Ferry Link is a Ferry Node; a reference to the Ferry Nodes at the start and end of the Ferry Link is provided in the [Start Node](/osngd/data-structure/transport/transport-network/ferry-link.md#startnode) and [End Node](/osngd/data-structure/transport/transport-network/ferry-link.md#endnode) attributes on Ferry Link features, respectively.
* **Ferry Terminals**: The ferry network can be connected to the road and path network using the Ferry Terminal Feature Type. Ferry Terminals share the geometry of a Ferry Node, which is referenced in the [Ferry Node ID attribute](/osngd/data-structure/transport/transport-network/ferry-terminal.md#ferrynodeid), and the link back to the road or path network is represented through the [Road Node ID](/osngd/data-structure/transport/transport-network/ferry-terminal.md#roadnodeid) or [Path Node ID](/osngd/data-structure/transport/transport-network/ferry-terminal.md#pathnodeid) attribute, respectively. If a ferry is a vehicular service which can be used by cars, then the Road Node ID attribute will be populated with the identifier of the closest [Road Node](/osngd/data-structure/transport/transport-network/road-node.md), representing the logical connection for vehicles to move from the ferry network to the road network; if the ferry is not vehicular, the Road Node ID attribute value will be null and the Path Node ID attribute value will be populated with the identifier of the closest [Path Node](/osngd/data-structure/transport/transport-network/path-node.md), representing the logical connection for foot passengers to move from the ferry network to the path network. In addition, the [Site ID attribute](/osngd/data-structure/transport/transport-network/ferry-terminal.md#siteid) will provide a link to the functional [Site feature](/osngd/data-structure/land-use/land-use-features/site.md) representing the ferry terminal, if applicable. Attribution on Ferry Terminal features includes the terminal name and NaPTAN (National Public Transport Access Node) code.

The following image shows an example of a short passenger ferry route; at each end of the route are a Path Node, Ferry Node and Ferry Terminal at the same point, providing a spatial and logical connection between path and ferry networks:

<figure><img src="https://170091638-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0pZjHxkAvY7Mn6TqFBMD%2Fuploads%2F6FSQjqlYTXXgZciHgDXb%2F6.png?alt=media&amp;token=e00fefa3-9c5c-407f-b907-4c85587ab3ca" alt="Example visualisation showing Ferry Link, Ferry Node and Ferry Terminal features. The image shows an example of a short passenger ferry route. At each end of the route are a Path Node, Ferry Node and Ferry Terminal at the same point, providing a spatial and logical connection between path and ferry networks. A background map has been included to provide context."><figcaption><p>Example visualisation showing Ferry Link, Ferry Node and Ferry Terminal features. A background map has been included to provide context.</p></figcaption></figure>

### Links to and from Ferry Links, Ferry Nodes and Ferry Terminals

The following table describes all the links to and from Ferry Links, Ferry Nodes and Ferry Terminals within the OS NGD Transport Theme and OS NGD Land Use Theme:

| Source Feature Type                                                                   | Foreign Key Attribute | Destination Feature Type                                                      |
| ------------------------------------------------------------------------------------- | --------------------- | ----------------------------------------------------------------------------- |
| [Ferry Link](/osngd/data-structure/transport/transport-network/ferry-link.md)         | `startnode`           | [Ferry Node](/osngd/data-structure/transport/transport-network/ferry-node.md) |
| [Ferry Link](/osngd/data-structure/transport/transport-network/ferry-link.md)         | `endnode`             | [Ferry Node](/osngd/data-structure/transport/transport-network/ferry-node.md) |
| [Ferry Terminal](/osngd/data-structure/transport/transport-network/ferry-terminal.md) | `roadnodeid`          | [Road Node](/osngd/data-structure/transport/transport-network/road-node.md)   |
| [Ferry Terminal](/osngd/data-structure/transport/transport-network/ferry-terminal.md) | `pathnodeid`          | [Path Node](/osngd/data-structure/transport/transport-network/path-node.md)   |
| [Ferry Terminal](/osngd/data-structure/transport/transport-network/ferry-terminal.md) | `ferrynodeid`         | [Ferry Node](/osngd/data-structure/transport/transport-network/ferry-node.md) |
| [Ferry Terminal](/osngd/data-structure/transport/transport-network/ferry-terminal.md) | `siteid`              | [Site](/osngd/data-structure/land-use/land-use-features/site.md)              |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.os.uk/osngd/using-os-ngd-data/os-ngd-transport/transport-networks-in-the-os-ngd/ferry-network.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.