> 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/~/changes/AJZwzCsyrD9hiTbOxIbO/networks/os-mastermap-highways-network-paths/os-mastermap-highways-network-paths-technical-specification/how-does-the-product-fit-together.md).

# How does the product fit together?

OS MasterMap Highways Network – Paths is a relational product. This results in there being relationships between different feature types. This section summarises how the different feature types relate to one another, and which attributes are the primary and foreign keys.

The below table identifies how the feature types relate to one another and which attributes are the primary and foreign keys. This is also represented diagrammatically below. The attribute at the arrowhead is the primary key and the attribute at the base of the arrow is the foreign key.

<table><thead><tr><th width="254">Source Feature Information</th><th width="85"></th><th>Destination Feature Information</th><th></th></tr></thead><tbody><tr><td><strong>Feature Type</strong></td><td><strong>Foreign Key Attribute</strong></td><td><strong>Feature Type</strong></td><td><strong>Primary Key Attribute</strong></td></tr><tr><td>PathLink</td><td>startNode</td><td>PathNode</td><td>id</td></tr><tr><td>PathLink</td><td>endNode</td><td>PathNode</td><td>id</td></tr><tr><td>PathLink</td><td>relatedRoadArea</td><td>TopographicArea</td><td>TOID</td></tr><tr><td>PathLink</td><td>formsPartOf</td><td>Path</td><td>id</td></tr><tr><td>PathLink</td><td>formsPartOf</td><td>Street</td><td>id</td></tr><tr><td>ConnectingLink</td><td>pathNode</td><td>PathNode</td><td>id</td></tr><tr><td>ConnectingLink</td><td>connectingNode</td><td>ConnectingNode</td><td>id</td></tr><tr><td>ConnectingNode</td><td>roadLink</td><td>RoadLink</td><td>id</td></tr><tr><td>Path</td><td>link</td><td>PathLink</td><td>id</td></tr><tr><td>Street</td><td>link</td><td>PathLink</td><td>id</td></tr><tr><td>FerryTerminal</td><td>element</td><td>PathNode</td><td>id</td></tr><tr><td>FerryTerminal</td><td>element</td><td>FerryNode</td><td>id</td></tr><tr><td>FerryTerminal</td><td>refToFunctionalSite</td><td>FunctionalSite</td><td>id</td></tr><tr><td>FerryLink</td><td>startNode</td><td>FerryNode</td><td>id</td></tr><tr><td>FerryLink</td><td>endNode</td><td>FerryNode</td><td>id</td></tr><tr><td>Maintenance</td><td>element</td><td>Street</td><td>id</td></tr><tr><td>Reinstatement</td><td>element</td><td>Street</td><td>id</td></tr><tr><td>SpecialDesignation</td><td>element</td><td>Street</td><td>id</td></tr><tr><td>HighwayDedication</td><td>element</td><td>Street</td><td>id</td></tr><tr><td>HighwayDedication</td><td>element</td><td>RoadLink</td><td>id</td></tr></tbody></table>

<figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FDCxBXUcESAshYh5mA4Qy%2F19.png?alt=media" alt="Figure 19: Diagram of OS MasterMap Highways Network - Paths relational model."><figcaption><p>OS MasterMap Highways Network – Paths: relational model</p></figcaption></figure>


---

# 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/~/changes/AJZwzCsyrD9hiTbOxIbO/networks/os-mastermap-highways-network-paths/os-mastermap-highways-network-paths-technical-specification/how-does-the-product-fit-together.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.