> 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-multi-modal-routing-network/os-mrn-overview.md). # OS MRN Overview This overview introduces the OS MRN and gives context for all users – highlighting key features, providing examples of potential uses, and listing details such as supply formats, currency, etc. OS Multi-modal Routing Network (OS MRN) is a fully connected routable network dedicated for the multi-modal routing of people and goods. The product is designed for use in routing applications and contains multi-modal connectivity between Road, Rail, Path, and Ferry networks, brought together by modal change points to enable transition between modes.  OS MRN was designed and built using the OpenStreetMap schema to facilitate its use in a wide range of routing applications. It takes existing OS network and routing data (available in the OS National Geographic Database – OS NGD) and maps this to the OpenStreetMap schema. New connectivity is added in the form of modal change points, which are key interchange sites where you can transition between different transport modes. Additionally, the dataset contains road restriction information and speed data. The pages in this Overview contain information and tips about the OS Multi-modal Routing Network (OS MRN) data and specific advice on how to make the most of the data provided by individual feature types: ## Key features * Fully connected Road, Rail, Path and Ferry networks across Great Britain * Road routing information, including turn restrictions and vehicle access restrictions * Road speed information, including maximum speed and average speed * Modal change points to represent sites where you can change transport mode * OpenStreetMap schema * OSParentIDs containing the OSID of the feature in the OS NGD ## Index This overview includes the following sections: * [Product supply](/os-downloads/products/transport-network-portfolio/os-multi-modal-routing-network/os-mrn-overview/product-supply.md) * [Coordinate reference system](/os-downloads/products/transport-network-portfolio/os-multi-modal-routing-network/os-mrn-overview/coordinate-reference-system.md) * [Feature types overview](/os-downloads/products/transport-network-portfolio/os-multi-modal-routing-network/os-mrn-overview/feature-types-overview.md) * [OpenStreetMap schema](/os-downloads/products/transport-network-portfolio/os-multi-modal-routing-network/os-mrn-overview/openstreetmap-schema.md) * [Modal change](/os-downloads/products/transport-network-portfolio/os-multi-modal-routing-network/os-mrn-overview/modal-change.md) * [Grade separation](/os-downloads/products/transport-network-portfolio/os-multi-modal-routing-network/os-mrn-overview/grade-separation.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/products/transport-network-portfolio/os-multi-modal-routing-network/os-mrn-overview.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.