> 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-paths/os-mastermap-highways-network-paths-technical-specification/feature-types/ferryterminal.md).
# FerryTerminal
The Ferry and Road Network elements are linked together through a FerryTerminal. A FerryTerminal is a logical connection between the two networks and therefore there is no geometry supplied with these features. They will reference one PathNode and one FerryNode. The FerryTerminals will also provide a reference to the OS MasterMap Sites feature.
The context diagram shows how the FerryTerminal has been inherited from INSPIRE, the attribution held on the FerryTerminal and how it relates to the other Ferry components.
Context Diagram: FerryLink, FerryNode and FerryTerminal
## FerryTerminal Attributes
A logical connection between a PathNode or RoadNode and the FerryNode. It represents the connection between the Road or Path Network and the Ferry Network.
### id
Unique identifier; for FerryTerminal, this is a TOID.
* **Attribute name**: gml\_id (GML), toid (GeoPackage)
* **Type**: CharacterString
* **Size**: 20
* **Multiplicity**: \[1]
### identifier
Uniform Resource Identifier.
* **Attribute name**: identifier (GML), identifier (GeoPackage)
* **Type**: CharacterString
* **Size**: 37
* **Multiplicity**: \[1]
### inspireId
External object identifier of the spatial object.
* **Attribute name**: inspireId
* **Type**: Identifier
* **Multiplicity**: \[0..1]
### beginLifespanVersion
Date and time at which this version of the spatial object was inserted or changed in the spatial data set.
{% hint style="info" %}
The time part is always set to zero.
{% endhint %}
* **Attribute name**: beginLifespanVersion (GML), begin\_lifespan\_version (GeoPackage)
* **Type**: DateTime
* **Multiplicity**: \[1]
### type
Categorisation of the network connection.
* **Attribute name**: type (GML), type (GeoPackage)
* **Type**: [ConnectionTypeValue](/os-downloads/products/transport-network-portfolio/os-mastermap-highways-network-fundamentals/os-mastermap-highways-network-code-lists/connectiontypevalue.md)
* **Size**: 10
* **Multiplicity**: \[1]
### ferryTerminalName
The name of the Ferry Terminal. Note: Where a feature has more than one name, the language of each name is provided as a 3-digit ISO 639-2 code (‘eng’, ‘cym’, ‘gla’).
* **Attribute name**: ferryTerminalName (GML), ferry\_terminal\_name (GeoPackage)
* **Type**: LocalisedCharacterString
* **Size**: 120
* **Multiplicity**: \[0..2]
### ferryTerminalCode
The recognised code of the Ferry Terminal.
* **Attribute name**: ferryTerminalCode (GML), ferry\_terminal\_code (GeoPackage)
* **Type**: CharacterString
* **Size**: 10
* **Multiplicity**: \[0..1]
### reasonForChange
The reason for a change made to a feature.
* **Attribute name**: reasonForChange (GML), reason\_for\_change (GeoPackage)
* **Type**: [ChangeValue](/os-downloads/products/transport-network-portfolio/os-mastermap-highways-network-fundamentals/os-mastermap-highways-network-code-lists/changevalue.md)
* **Size**: 32
* **Multiplicity**: \[1]
### refToFunctionalSite
Reference to the Site representation of the Ferry Terminal in OS MasterMap Sites Layer.
* **Attribute name**: refToFunctionalSite (GML), ref\_to\_functional\_site (GeoPackage)
* **Size**: 20
* **Multiplicity**: \[0..1]
### element
The reference to the RoadNode or PathNode and the FerryNode. The type of node the element is referencing will be identified through the xlink:title.
* **Attribute name**: elementId (GML), element\_id (GeoPackage)
* **Size**: 20
* **Multiplicity**: \[2..\*]
---
# 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/os-downloads/products/transport-network-portfolio/os-mastermap-highways-network-paths/os-mastermap-highways-network-paths-technical-specification/feature-types/ferryterminal.md?ask=&goal=
```
`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.
