> 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/resources/product-resources/end-of-life-product-documentation/os-detailed-path-network/os-detailed-path-network-getting-started-guide.md).

# OS Detailed Path Network Getting Started Guide

This getting started guide provides instructions for using OS Detailed Path Network in different software applications. Users with limited technical knowledge will be able to follow this guide.

{% hint style="warning" %}

#### Product has reached its End of Life (withdrawal) date

The OS Detailed Path Network product reached its End of Life on 30 September 2026. As of this date, Ordnance Survey ceased to maintain or publish updates to the product, and removed access to the product from the OS Data Hub, OS Features API and OS Vector Tile API.

Supporting product documentation will be removed from this site 12 months after this date, when access to existing data packages in the OS Data Hub is no longer available. Full details, including migration information and FAQs, are available on the [OS Detailed Path Network End of Life information page](/os-downloads/resources/product-resources/end-of-life-product-documentation/os-detailed-path-network/os-detailed-path-network-end-of-life-information.md).
{% endhint %}

The OS Detailed Path Network product is a topologically connected link and node network for roads, tracks, paths and rights of way within the National Parks of Great Britain. The product has been created from a number of existing Ordnance Survey data sources, including OS MasterMap Topography Layer, OS MasterMap Highways Network, 1:25 000 Scale Colour Raster, OS Terrain 5 and OS Terrain 50. The data is intended to provide sufficient detail for routing pedestrians, cyclists and horse riders when using mobile devices, with a typical positional accuracy of 10m.

The OS Detailed Path Network dataset was originally released in 2015. It is currently updated on an annual basis and coverage is restricted to the National Park areas of Great Britain.

## Adherence to standards <a href="#bookmark1" id="bookmark1"></a>

OS Detailed Path Network is a derived product that has been designed with consideration of the [INSPIRE](https://inspire.ec.europa.eu/) Transport Networks Data Specification, although INSPIRE does not apply to off road transport. Due to the process of deriving OS Detailed Path Network, feature instances and their identifiers will be regenerated at each data refresh.

## Loading GeoPackage data

This getting started guide focusses solely on using the product in GML format. For guidance on using the product in GeoPackage format, please see our [Getting Started with GeoPackage guide](/os-downloads/resources/product-resources/getting-started-with-geopackage-and-vector-tiles-guides/getting-started-with-geopackage.md).

## Loading vector tiles data

This getting started guide focusses solely on using the product in GML format. For guidance on using the product in vector tiles format, please see our [Getting started with Vector Tiles guide](/os-downloads/resources/product-resources/getting-started-with-geopackage-and-vector-tiles-guides/getting-started-with-vector-tiles.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 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/resources/product-resources/end-of-life-product-documentation/os-detailed-path-network/os-detailed-path-network-getting-started-guide.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.