> 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.md). # Transport Network Portfolio This page provides an overview of the OS downloadable products in the Transport Network Portfolio. ## Transport network products This portfolio provides detailed network data for transport routes across Great Britain. It supports routing, asset management and transport planning, with topologically structured datasets and authoritative identifiers. The following downloadable products are available within the Transport Network Portfolio:
Cover image

OS MasterMap Highways Network – Paths

A path network dataset for Great Britain showing who is responsible for all the footpaths through towns and cities in Great Britain.Highways-Network-Paths-1.pngOS MasterMap Highways Network – Paths

OS MasterMap Highways Network – Roads

A navigable road network dataset with detailed information about planned roads and roads under construction.Highways-Network-1.pngOS MasterMap Highways Network – Roads

OS MasterMap Highways Network – Routing and Asset Management Information (RAMI)

Routing data from Ordnance Survey's large-scale road and path data integrated with data from the National Street Gazetteer (NSG), the Trunk Road Street Gazetteer (TRSG) and the Scottish Street Gazetteer (SSG).Highways-Network-RAMI-1.pngOS MasterMap Highways Network – Routing and Asset Management Information

OS Multi-Modal Routing Network (OS MRN)

A fully connected routable network containing  multi-modal connectivity between road, rail,  path and ferry networks for the routing of people and goods.MRN_Cover.pngOS Multi-modal Routing Network

OS Open Roads

An open dataset providing a high-level digital representation of Great Britain's road network.Open-Roads-5.pngOS Open Roads

OS Open USRN

An open dataset containing all Unique Street Reference Numbers (USRNs) from OS MasterMap Highways Network.USRN-attribution-1.pngOS Open USRN

OS Open Linked Identifiers

An open dataset of cross-referenced identifiers detailing relationships between Unique Property Reference Numbers (UPRNs), Unique Street Reference Numbers (USRNs) and Topographic Identifiers (TOIDs).LinkedIDs_banner_small.pngOS Open Linked Identifiers
{% hint style="info" %} ## OS Detailed Path Network now End of Life (withdrawn) The OS Detailed Path Network product was withdrawn on 30 September 2026. As of this date, Ordnance Survey no longer maintains or publishes updates to the product. Documentation for the product can be found in the [End of Life Product Documentation section](/os-downloads/resources/product-resources/end-of-life-product-documentation.md) for the 12 months following product withdrawal that data packages and download orders remain available on the OS Data Hub for existing customers. {% 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/products/transport-network-portfolio.md?ask=&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.