> 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-downloads.md).

# OS Detailed Path Network Downloads

{% 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 %}

## XML code lists

XML versions of the OS Detailed Path Network code lists are available below:

* [LevelCodeValue.xml](https://www.ordnancesurvey.co.uk/xml/codelists/LevelCodeValue.xml)
* [PotentialHazardValue.xml](https://www.ordnancesurvey.co.uk/xml/codelists/PotentialHazardValue.xml)
* [RightOfWayValue.xml](https://www.ordnancesurvey.co.uk/xml/codelists/RightOfWayValue.xml)
* [RouteDescriptiveGroupValue.xml](https://www.ordnancesurvey.co.uk/xml/codelists/RouteDescriptiveGroupValue.xml)
* [RouteDescriptiveTermValue.xml](https://www.ordnancesurvey.co.uk/xml/codelists/RouteDescriptiveTermValue.xml)
* [RouteLinkDescriptiveTermValue.xml](https://www.ordnancesurvey.co.uk/xml/codelists/RouteLinkDescriptiveTermValue.xml)
* [RouteNodeDescriptiveTermValue.xml](https://www.ordnancesurvey.co.uk/xml/codelists/RouteNodeDescriptiveTermValue.xml)
* [SurfaceTypeValue.xml](https://www.ordnancesurvey.co.uk/xml/codelists/SurfaceTypeValue.xml)

Code lists provide a controlled list and formal definition for values used in certain attributes of the product.

## XML schema

The OS Detailed Path Network XML schema is available to download from the [XML file resources page on the Ordnance Survey website](https://www.ordnancesurvey.co.uk/xml/).

* [detailedPathNetwork.xsd](https://www.ordnancesurvey.co.uk/xml/schema/detailedPathNetwork/v1/detailedPathNetwork.xsd)

{% hint style="info" %}
The XML File Repository License, covering the terms and conditions for the use of all Ordnance Survey XML schemas, is made available through the [Terms and Conditions page](/os-downloads/resources/site-resources/terms-and-conditions.md) in the Resources section.
{% endhint %}


---

# 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-downloads.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.