> 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-detailed-path-network/os-detailed-path-network-overview/product-details.md).
# Product details
## Data lineage
The OS DPN product has been created from a number of existing Ordnance Survey data sources:
* **Roads, tracks and paths** – The geometry and information about the physical nature of a route has been sourced from the Ordnance Survey large-scale data which is used to create the OS MasterMap Topography Layer and OS MasterMap Highways Network products.
* **Rights of way, long distance paths, cycle routes, access land and danger areas** – These have been extracted from [1:25 000 Scale Colour Raster](https://www.ordnancesurvey.co.uk/products/25k-raster).
* **Hazardous terrain** – Attribution relating to selected potential difficulties along a route (for example, scree / cliffs) has been interpolated by overlaying the network on the Ordnance Survey large-scale data used to create the OS MasterMap Topography Layer product.
* **Height values** – These have been interpolated from the source data used for the [OS Terrain 5](https://www.ordnancesurvey.co.uk/products/os-terrain-5) and [OS Terrain 50](https://www.ordnancesurvey.co.uk/products/os-terrain-50) products.
The raw data used to create the product has undergone extensive data re-engineering, manual editing and validation.
## Coverage
The OS DPN product includes all roads (except motorways), tracks and paths that the public are allowed to use within the 15 National Parks of England, Scotland and Wales.
Full details as to the locations of Britain’s National Parks can be found on the [National Parks UK website](https://www.nationalparks.uk/). The 15 National Parks covered in the OS Detailed Park Network product (and hyperlinks to the official website of each National Park) are as follows:
* [Brecon Beacons](https://www.beacons-npa.gov.uk/)
* [Broads](https://www.visitthebroads.co.uk/)
* [Cairngorms](http://www.cairngorms.co.uk/)
* [Dartmoor](https://www.dartmoor.gov.uk/)
* [Exmoor](http://www.exmoor-nationalpark.gov.uk/)
* [Lake District](https://lakedistrict.gov.uk/)
* [Loch Lomond and the](https://www.lochlomond-trossachs.org/) [Trossachs](https://www.lochlomond-trossachs.org/)
* [New Forest](http://www.newforestnpa.gov.uk/)
* [North York Moors](http://www.northyorkmoors.org.uk/)
* [Northumberland](http://www.northumberlandnationalpark.org.uk/)
* [Peak District](http://www.peakdistrict.gov.uk/)
* [Pembrokeshire Coast](http://www.pcnpa.org.uk/)
* [Snowdonia](https://authority.eryri.gov.wales/)
* [South Downs](http://www.southdowns.gov.uk/)
* [Yorkshire Dales](http://www.yorkshiredales.org.uk/)
## Product update schedule
This product is supplied annually each October, incorporating updates from Ordnance Survey core data and [1:25 000 Scale Colour Raster](https://www.ordnancesurvey.co.uk/products/25k-raster).
The product will be resupplied as a complete dataset; change-only updates (COUs) will not be available.
The product contains identifiers and feature versions; however, identifiers will not persist, and versions will not increment. They have been included for future, potential product enhancements.
{% hint style="warning" %}
Please note that the October 2025 release was the final release of the OS Detailed Path Network product; more information about the product withdrawal timeline and the recommended product migration pathway is available from the [End of Life Notice – Detailed Path Network](/os-downloads/resources/product-resources/end-of-life-product-notices/end-of-life-notice-os-detailed-path-network.md) page.
{% endhint %}
## Feature types included in the product
The data is supplied as a link and node model, similar to the OS MasterMap Highways Networks and
OS Open Roads products. Links represent the general alignment of roads, tracks, paths and rights of way; nodes are used to record the connectivity between links explicitly. Named routes are represented as collections of links.
The OS DPN product contains three feature types: Route, RouteLink and RouteNode. These feature types are defined below.
### 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 feature can include references to different types of RouteLink. For example, a Route feature may include sections of paths, tracks and public roads to create a continuous named trail.
### 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 or horse riders.
RouteLink features are split in the following circumstances:
* Where the classification changes.
* Where the name changes (or ceases to apply).
* Where there is a junction at the same physical level.
### RouteNode
A RouteNode is a feature at the end of one or more RouteLink features. 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.
---
# 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:
```
GET https://docs.os.uk/os-downloads/products/transport-network-portfolio/os-detailed-path-network/os-detailed-path-network-overview/product-details.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.