> 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-detailed-path-network/os-detailed-path-network-technical-specification/os-detailed-path-network-structure.md).
# OS Detailed Path Network structure
The data is supplied as a link and node model similar to that used for the [OS MasterMap Highways](https://www.ordnancesurvey.co.uk/business-government/tools-support/mastermap-highways-support) [Networks products](https://www.ordnancesurvey.co.uk/business-government/tools-support/mastermap-highways-support).
Route Links represent the general alignment of roads, tracks, paths and rights of way and Route Nodes are used to record the connectivity between links explicitly. A Route feature, that records collections of links or link sets, is used to record recognised named routes as single features.
OS Detailed Path Network contains three feature types (Route, RouteLink and RouteNode); the product's structure is demonstrated in Figure 1.
## Route
A Route is a feature representing a named entity that forms a recognised and signed route that the public can use. For example, a [National Trail](https://www.nationaltrail.co.uk/), such as the Pennine Way, or one of [Scotland’s Great Trails](https://www.scotlandsgreattrails.com/), such as the West Highland Way.
A route can include references to different types of RouteLink, for example, a route may include sections of paths, tracks and public roads to create a continuous named trail.
The Route feature is not included in the vector tiles format, as these would directly overlay and replicate the RouteLink features referenced by a single route.
See the [Route feature type page](/os-downloads/~/changes/AJZwzCsyrD9hiTbOxIbO/networks/os-detailed-path-network/os-detailed-path-network-technical-specification/feature-types/route.md) for more details.
## RouteLink
A RouteLink is a feature that represents all or part of a road, track, path or right of way that can be used by pedestrians, cyclists and horse riders.
See the [RouteLink feature type page](/os-downloads/~/changes/AJZwzCsyrD9hiTbOxIbO/networks/os-detailed-path-network/os-detailed-path-network-technical-specification/feature-types/routelink.md) for more details.
## RouteNode
A RouteNode is a feature at the end of one or more RouteLinks. It allows software to quickly identify connections by using references to the unique identifier. The RouteNode also indicates:
* The junction of three or more RouteLink features.
* A change in real-world information (for example, the route type) that requires the creation of two RouteLink features with different attribution.
* The start or end of a RouteLink feature.
See the [RouteNode feature type page](/os-downloads/~/changes/AJZwzCsyrD9hiTbOxIbO/networks/os-detailed-path-network/os-detailed-path-network-technical-specification/feature-types/routenode.md) for more details.
UML diagram of the OS Detailed Path Network product model.
---
# 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/~/changes/AJZwzCsyrD9hiTbOxIbO/networks/os-detailed-path-network/os-detailed-path-network-technical-specification/os-detailed-path-network-structure.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.
