> 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/openstreetmap-schema.md). # OpenStreetMap schema The OS Multi-modal Routing Network (OS MRN) product is designed and built in the OpenSteetMap (OSM) schema to facilitate straightforward import into many routing software applications. The OpenStreetMap model has three core data elements: * **Ways**: A way represents a linear feature on the ground. In OS MRN, these are called [Transport Links](/os-downloads/products/transport-network-portfolio/os-multi-modal-routing-network/os-mrn-overview/feature-types-overview/transport-link-overview.md) and are linear representations of where people can travel along a network. * **Nodes**: A node is a single point in space. In OS MRN, these are called [Transport Nodes](/os-downloads/products/transport-network-portfolio/os-multi-modal-routing-network/os-mrn-overview/feature-types-overview/transport-node-overview.md) and build up the topology of the network, connecting ways together. * **Relations**: A relation defines how other elements work together. In OS MRN, these are called [Turn Restrictions ](/os-downloads/products/transport-network-portfolio/os-multi-modal-routing-network/os-mrn-overview/feature-types-overview/turn-restriction-overview.md)and represent information about turn restrictions. OSM uses a system of tags to apply information against different features. We have taken existing OS network and routing data from the [OS National Geographic Database](https://docs.os.uk/osngd/data-structure/transport) (OS NGD) and mapped this to the OSM schema. We include all the values from the OSM schema in the [OS MRN code lists](/os-downloads/products/transport-network-portfolio/os-multi-modal-routing-network/os-mrn-technical-specification/code-lists.md); however, please note that not all values are populated in the first release of OS MRN. {% hint style="info" %} ## More information on the OpenStreetMap model's elements, features and tags * Please see [Elements - OpenStreetMap Wiki](https://wiki.openstreetmap.org/wiki/Elements) for more information on the three core data elements in the OSM model. * Please see [Map features – OpenStreetMap Wiki](https://wiki.openstreetmap.org/wiki/Map_features) for more information on how the OSM model represents features. * Please see [Tags – OpenStreetMap Wiki](https://wiki.openstreetmap.org/wiki/Tags) for more information on how the OSM model uses tags. {% endhint %} Transport Link features in OS MRN combine the following existing transport information from the OS NGD into one feature type: * OS NGD Road Links * OS NGD Path Links and Connecting Links * OS NGD Ferry Links * OS NGD Railway Links * OS NGD Access Restrictions * OS NGD Average And Indicative Speeds Transport Node features in OS MRN combine the following existing transport information from the OS NGD into one feature type: * OS NGD Road Nodes * OS NGD Path Nodes and Connecting Nodes * OS NGD Ferry Nodes * OS NGD Railway Nodes Turn Restriction features in OS MRN take information from the OS NGD Restriction Feature Type. --- # 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/openstreetmap-schema.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.