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

# OS MRN FAQs

Frequently asked questions for the OS MRN product.

<details>

<summary>How does OS MRN differ from OS MasterMap Highways Network products?</summary>

For customers interested in **routing use cases**, OS MRN is a viable alternative to [OS MasterMap Highways Network products](https://docs.os.uk/os-downloads/products/transport-network-portfolio/os-mastermap-highways-network-fundamentals.md) and the [OS NGD Transport Theme](https://docs.os.uk/osngd/data-structure/transport).

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. 

For routing use cases, OS MRN offers the following advantages over OSMM Highways Network products and the OS NGD Transport Theme:

* It's designed specifically for routing
* There's full connectivity between different networks
* It's a single dataset that incorporates routing information and speed data
* It follows the OpenStreetMap (OSM) schema to enable straightforward import into routing applications, particularly open-source routing engines
* The modal change points enable connectivity with key transport sites
* There's easy integration with third party bus and train timetable datasets
* Less processing required to use it – for example, OS has implemented the logic to determine what links are suitable for walking

</details>

<details>

<summary>How do I identify links that are accessible on foot?</summary>

To broadly identify links which are routable on foot in OS MRN, select links that have a foot value of ‘yes’, or ‘designated’.\
\
The [Foot attribute](https://docs.os.uk/os-downloads/products/transport-network-portfolio/os-multi-modal-routing-network/os-mrn-technical-specification/feature-types/transport-link.md#foot) identifies whether a link is accessible by foot in the OS MRN, and the code list values used for this attribute are ‘yes’, ‘no’ and ‘designated’, as defined in the [OpenStreetMap schema](https://wiki.openstreetmap.org/wiki/Key:foot):

* [‘designated’](https://wiki.openstreetmap.org/wiki/Tag%3Afoot%3Ddesignated) describes any link specifically designed for pedestrians, such as path links, as well as those with designated infrastructure, for example, pavements along the entire length of the link.&#x20;
* ‘yes’ is used for links where you can walk but there may not be designated infrastructure along the entire length, for example, only 50% pavement coverage or a pedestrian ferry link.&#x20;
* ‘no’ is used for links where pedestrians are forbidden or it would be unsafe to walk, for example, motorways or A roads without full pavement coverage.

</details>

<details>

<summary>Why do some links under bridges or other structures unexpectedly have a foot attribute of 'no'?</summary>

At present, OS data does not always capture topographic area detail below bridges and other elevated structures, instead prioritising the capture of structure surfaces (that is, what is captured from above from aerial imagery). This leaves 'gaps' in the topography underneath structures, such as in the capture of pavement topographic areas.

For safety reasons, in the OS MRN product links belonging to major roads without 100% pavement coverage along their length may be assigned a foot attribute of 'no'. In a small number of instances, the above limitation may result in links under bridges or other supported structures being assigned foot = 'no' due to the lack of pavement polygons where pavements may exist in the real world but are obscured.

</details>

<details>

<summary>Where does the average speed data and speed limit data in OS MRN come from?</summary>

OS MRN uses the average and indicative speed data from the OS NGD Transport Theme as its source. This data, in turn, is supplied to OS by a third party.&#x20;

For further information see the [OS NGD Transport Average And Indicative Speed Feature Type documentation](https://docs.os.uk/osngd/data-structure/transport/rami/average-and-indicative-speed).

</details>

<details>

<summary>Why can I see transport links cutting straight across buildings / water / other links?</summary>

[Modal Change Links](https://docs.os.uk/os-downloads/products/transport-network-portfolio/os-multi-modal-routing-network/os-mrn-overview/modal-change.md) are fictitious links describing the connection between the transport network and a ‘modal change point’, such as a ferry terminal, car park or bus station. As they do not represent the alignment of a real-world feature, they are straight links between the nearest transport node and the centroid of the site representing the modal change point. Because of this, they may cut through real-world features, such as buildings, and across other transport links.&#x20;

Modal Change Links can be identified by a null os\_parentid.

</details>

<details>

<summary>What does the PSV attribute describe?</summary>

In the OS MRN, the [PSV attribute](https://wiki.openstreetmap.org/wiki/Key:psv) stands for 'Public Service Vehicles' and describes the nature of access for buses, coaches and public transport. If a link has an access restriction forbidding public transport, this link will have a PSV value of ‘no’.

OS MRN has numerous attributes describing whether particular vehicle types can use a link, for example, motorvehicle and bicycle are derived from the OpenStreetMap schema.

</details>


---

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