1 of 33

OS Multi-modal Routing Network

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. 

This product is updated monthly.

Fully connected

OS MRN brings together existing OS Road, Rail, Path and Ferry networks in a fully connected dataset, using Modal Change Points to show where you can transition between them (for example, at railway stations and ferry terminals).

OpenStreetMap schema

OS MRN is built in the OpenStreetMap schema, which is widely supported by routing software, enabling use in a wide range of applications.

Ready-to-use

All the road restriction information you need for safe routing is included, as well as speed data, reducing the pain points of processing and joining multiple datasets.

OS MRN can be used for journey planning, routing, navigation, and distance and travel time analysis, to support use cases such as:

Planning safe routes to school
Emergency Services planning and response
Transport planning
Supporting Active Travel initiatives
Planning of accessible citizen services

Access: Download
Data theme: Transport
Data structure: Vector
Coverage: Great Britain
Format: Protocolbuffer Binary Format (PBF), GeoPackage
Ordering area: All of Great Britain or customisable area (user-defined polygon)
OS Data Hub plan: Premium Plan, Public Sector Plan

How to get this product

Access to this product is free for PSGA (Public Sector Geospatial Agreement) Members. Find out if you are a PSGA Member or try out a sample of OS MRN data by accessing the OS MRN product page on the OS website, where you will find links to all of the relevant resources.

The OS MRN product is supplied as an online download from the OS Data Hub.

Useful resources

A helpful introductory Lightning Talk on the OS MRN is available on our 'More than Maps' site (a self-serve site that provides a one-stop shop for all your OS technical geospatial support, including tutorials and demonstrators).

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 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
Coordinate reference system
Feature types overview
OpenStreetMap schema
Modal change
Grade separation

Product supply

Available formats

OS MRN is available in two formats:

Protocolbuffer Binary Format (PBF)
GeoPackage (GPKG)

Protocolbuffer Binary Format overview

PBF is an open source transfer format for vector GIS data created by the OpenStreetMap (OSM) community. PBF is an alternative to the original OSM XML format. PBF files are generally much smaller than OSM XML files and are faster to read and write.

GeoPackage overview

GeoPackage is an open standard data format as defined by the Open Geospatial Consortium (OGC). GeoPackage is designed to be a lightweight format that can contain large amounts of varied and complex data in a single, easy-to-distribute and ready-to-use file.

Supply mechanism

OS MRN is available as an online download from the OS Data Hub. You can select a data format (PBF or GeoPackage) during the download process.

It is available as a Full Supply only, and customers can order full Great Britain (GB) coverage or a customisable area of interest (AOI).

Currency

OS MRN is updated monthly, in-line with updates of OS transport network data.

Coverage

OS MRN covers Great Britain.

Coordinate reference system

The coordinate reference system used by OS MRN is the World Geodetic System (WGS84: EPSG: 4326). This applies to both the PBF and GPKG formats.

The WGS84 spatial reference system uses the WGS84 geodetic datum. Positions on this projection are described as latitude and longitude, and coordinates are provided in decimal degrees.

Feature types overview

The OS Multi-modal Routing Network (OS MRN) premium product contains three feature types: Transport Link, Transport Node and Turn Restriction

The pages in this section contain additional details about of the attribution for each feature type in the OS MRN and should be read in conjunction with the corresponding feature type page in the technical specification.

Transport Link overview

The information on this page supplements that of the page in the . Please read the two pages in conjunction for a complete understanding of the feature type.

A Transport Link is a linear spatial object that defines the geometry and connectivity of a road, path, rail, or ferry network between two points in the network. Transport Links are split for connectivity purposes (for example, at junctions) and connect the Transport Links together. Each Transport Link provides a reference to the Transport Nodes at the start and end of the Transport Link.

Transport Links contain information about the type of link (for example, highway='motorway') and information about the access restrictions for vehicles to indicate which modes can travel along the link (e.g motor_vehicle=’yes’). There is also a maximum speed attribute, and two average speed attributes:

a conditional delimited list of all the speeds at different time periods
a single average speed using the Mon-Fri 12-2 pm period.

Transport Links also incorporate Modal Change links which are a linear spatial object representing a logical connection between the transport network and a transport site. See the page for more information.

The Transport Link is attributed with a unique (but not persistent) WayID, which routing software uses to build out the network. Transport Links are also attributed with the OSID of the corresponding OS parent feature that is published in the OS NGD Transport Theme.

Transport Node overview

The information on this page supplements that of the Transport Node page in the technical specification. Please read the two pages in conjunction for a complete understanding of the feature type.

A Transport Node is a point spatial object that is used to break up the Transport Network for connectivity. The Transport Network splits at the following locations:

Where an attribute changes.
The intersection or crossing of Transport Links.
The start / end of a Transport Link.

Transport nodes build up the topology of the network and connect Transport Links together. They also represent Modal Change points where you can change travel modes. See the Modal Change page for more information.

Transport Nodes are also present at every vertex along the network. These ‘vertex nodes’ don’t split the network; they are provided to enable software that reads in OpenStreetMap (OSM) data to build up the network vertex by vertex. The vertex nodes allow customers to convert from GeoPackage format to OSM.

The Transport Node will be attributed with a unique (but not persistent) Node ID and also the OSID of the corresponding OS parent feature that is published in the OS NGD Transport Network Collection.

Turn Restriction overview

The information on this page supplements that of the Turn Restriction page in the technical specification. Please read the two pages in conjunction for a complete understanding of the feature type.

A Turn Restriction provides line geometry that indicates turn restrictions for the given Transport Link (for example No right turn or No U turn).

Where the Turn Restriction applies to specific vehicle type (for example, bus or HGV), this is identified by the corresponding separate attribute as described below, along with conditional values for when the turn restriction only exists on specific times or days.

The Turn Restriction is attributed with the OSID of the corresponding OS parent feature that is published in the OS NGD Transport RAMI Collection.

Turn Restrictions are named following a from-to-via pattern, where:

from is the wayid of the first Transport Link involved in the turn restriction.
to is the wayid of the last Transport Link involved in the turn restriction.
via is the nodeid of the Transport Node at the junction (when there are only two links involved in the turn restriction), or a wayid list of all the Transport Links which are not the from or to link (when there are more than two links involved in the turn restriction).

OpenStreetMap schema

OS Multi-modal Routing Network (OS MRN) 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, nodes and relations. See Elements - OpenStreetMap Wiki for more information.

A way represents a linear feature on the ground. In OS MRN, these are called Transport Links and are linear representations of where people can travel along a network.
A node is a single point in space. In OS MRN, these are called Transport Nodes and build up the topology of the network, connecting ways together.
A relation defines how other elements work together. In OS MRN, these are called Turn Restrictions 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 and mapped this to the OSM schema. We will include all the values from the OSM schema in the OS MRN code lists, but not all values are populated in the first release of OS MRN.

Transport Links combine the following existing transport information into one feature type:

OS NGD Road Links
OS NGD Path and Connecting Links
OS NGD Ferry Links
OS NGD Railway Links
OS NGD Access Restrictions
OS NGD Speed data

Transport Nodes combine the following existing transport information and into one feature type:

OS NGD Road Nodes
OS NGD Path and Connecting Nodes
OS NGD Ferry Nodes
OS NGD Railway Nodes

Turn Restrictions take the existing OS NGD Turn Restrictions.

Modal change

OS Multi-modal Routing Network (OS MRN) contains Modal Change points to represent where you can transition between different transport modes. The OS MRN takes keys sites such as train stations, ferry terminals and car parks, and creates modal change points at these locations to enable connectivity.

Within the Transport Node feature type there are Modal Change nodes which are derived from transport sites. A node is created and sits within the primary building of the site. It is attributed with the os_nodetype of ‘Modal Change’.

Within the Transport Link feature type there are Modal Change links which are a linear spatial object representing a logical connection between the transport network and the transport site. These Transport Links connect between the network and the Modal Change node.

Modal change connectivity is only provided between sites and the road, rail and ferry network. Modal change points do not connect to the Path network as we do not currently capture access points from paths to sites in OS data.

Grade separation

Where Transport Nodes have been split apart due to grade separation, the original node keeps the existing OSID and the additional nodes are indicated with the suffix --1 or --2, depending on the grade separation value. Also, the geometries of grade separated Transport Nodes are offset (5 cm in both the X and Y axes) to prevent routing software failure due to point spatial objects being at the same position.

If a Transport Link has a different grade separation at the start and end node, the link is split. The OSID of the new Transport Node between the split links is indicated with a suffix of --S. One of the Transport Links keeps to original OSID and the other has the suffix of --S.

OS MRN Technical Specification

This technical specification provides detailed technical information about the OS MRN. It is targeted at technical users and software developers.

Product overview

OS Multi-modal Routing Network (OS MRN) provides a fully connected road, rail, path and ferry network across Great Britain Road. It includes turn and vehicle access restrictions, road speed information, and modal change points where you can change transport mode.

Index

The sub-sections in this technical specification describe the:

Feature types available within the OS MRN product
Code lists used by attributes available in those feature types

Feature types

The OS Multi-modal Routing Network (OS MRN) product contains the following three feature types:

Transport Link
Transport Node
Turn Restriction

The pages in this section provide full details of the attributions for each feature.

Transport Node

A Transport Node is a point spatial object that is used to break up the Transport Network for connectivity. The Transport Network splits at the following locations:

Where an attribute changes.
The intersection or crossing of Transport Links.
The start / end of a Transport Link.

Temporal filtering

The earliest date on which you can request a one-off snapshot of a date in the past for data in this feature type is 27 March 2024.

Feature type attributes

The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

For more information about the Transport Node Feature Type please read the Transport Node overview page in the OS MRN Overview.

nodeid

A unique numerical ID given to each TransportNode. This is commonly used by routing software as the primary identifier for the feature.

Data Types: Integer (GPKG), String(PBF)
Nullable: false
Max Length: 10
Data Schema Version: 1.0

os_parentid

The OSID of the corresponding feature that is published in OS NGD Transport Network Collection. Where TransportNodes have been split apart due to grade separation, the original node will keep the existing OSID and the additional nodes will be indicated with the suffix --1 or --2 depending on the grade separation value.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 40
Data Schema Version: 1.0

os_nodetype

Describes the type of node and where the node represents a site of modal change, the type of interchange site where appropriate e.g. 'Ferry Vehicular Terminal','Railway Station' and/or 'Modal Change'

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 100
Data Schema Version: 1.0

name

Name given to a TransportNode or its junction, e.g. 'M42 J4', 'Cappers Roundabout', 'Mortlake;Mortlake Rail Station'.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 100
Data Schema Version: 1.0

geometry

2D geometry for the feature.

Data Types: Geometry (GPKG), Geometry (PBF)
Nullable: false
Data Schema Version: 1.0
Geometry Type: Point

Turn Restriction

A Turn Restriction provides line geometry that indicates turn restrictions for the given Transport Link (e.g. No right turn, No U turn).

Where the Turn Restriction applies to specific vehicle types (e.g. bus, HGV), this is identified by the corresponding separate attributes as described below.

Temporal Filtering

The earliest date on which you can request a one-off snapshot of a date in the past for data in this feature type is 27 March 2024.

Feature type attributes

The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

For more information about the Turn Restriction Feature Type please read the Turn Restriction overview page in the OS MRN Overview.

relationid

A unique numerical ID given to each TurnRestriction. This is commonly used by routing software as the primary identifier for the feature.

Data Types: Integer (GPKG), String (PBF)
Nullable: false
Max Length: 10
Data Schema Version: 1.0

os_parentid

The osid of the corresponding feature that is published in OS NGD Transport Network Collection.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 40
Data Schema Version: 1.0

type

Describes the type of relation. All relations take value 'restriction' to describe how they should be applied.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 26
Data Schema Version: 1.0

restriction

Describes the type of turn restriction. E.g. 'no_right_turn', 'only_straight_on'.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name: restrictionlabelvalue
Max Length: 16
Data Schema Version: 1.0

restriction:conditional

If the turn restriction only exists on specific times or days then the time periods will be populated here in OpenStreetMap time conditional formatting , e.g. 'no_right_turn @ (Mo-Fr 07:30-09:30)'

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

restriction:hgv

A turn restriction which applies only to heavy goods vehicles.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name: restrictionlabelvalue
Max Length: 16
Data Schema Version: 1.0

restriction:goods

A turn restriction which applies only to goods vehicles.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name: restrictionlabelvalue
Max Length: 16
Data Schema Version: 1.0

restriction:bus

A turn restriction which applies only to buses including school buses.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name: restrictionlabelvalue
Max Length: 16
Data Schema Version: 1.0

restriction:psv

A turn restriction which applies only to Public Service Vehicles inlcuding buses, coaches and local buses

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name: restrictionlabelvalue
Max Length: 16
Data Schema Version: 1.0

restriction:abnormalloads

A turn restriction which applies only to unspecified abnormal loads. This is not a standard OpenStreetMap (OSM) tag.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

restriction:wideloads

A turn restriction which applies only to unspecified wide loads. This is not a standard OSM tag.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

except

Specifies the vehicle types for which the turn restriction does not apply. Multiple vehicle types will be seperated.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 50
Data Schema Version: 1.0

from

The wayid of the first TransportLink involved in the turn restriction.

Data Types: Integer (GPKG), String (PBF)
Nullable: false
Max Length: 10
Data Schema Version: 1.0

to

The wayid of the last TransportLink involved in the turn restriction.

Data Types: Integer (GPKG), String (PBF)
Nullable: false
Max Length: 10
Data Schema Version: 1.0

via

A list of wayid's (and/or nodeid's). When there are only two links involved in the turn restriction, via is the node at the junction at which the turn restriction applies. When there are more than two links involved in the turn restriction, via is a list of all links which are not the from or to link.

Data Types: String (GPKG), String (PBF)
Nullable: false
Max Length: 250
Data Schema Version: 1.0

geometry

2D geometry for the feature.

Data Types: Geometry (GPKG), Geometry (PBF)
Nullable: false
Data Schema Version: 1.0
Geometry Type: MultiLineString

Code lists

A code list is a controlled set of allowable labels or codes represented as an alphanumeric attribute. The pages in this section show the code lists used within the OS Multi-modal Routing Network (MRN). Some of the code lists apply to attributes of multiple feature types, whereas others will only apply to attributes of one feature type.

The pages in this section display the code lists in alphabetical order, with one code list provided per page.

AccessValue

This code list is used in association with a number of attributes which are present within the Transport Link Feature Type. The code list describes the nature of the access permitted to the Transport Link.

Label

Definition

yes

General public access is assumed, but does not imply an official, legally-enshrined right of way.

General public access is prohibited. Stronger interdiction than private. E.g. a fully closed road; a restricted military facility. If only specific transport modes are forbidden, for example, at a vehicle no-entry sign, a more specific restriction like vehicle=no or motor_vehicle=no will be used over the general key access.

private

General public access is not allowed. Access is granted with individual permission only. E.g. A driveway with a no trespassing or keep out sign; A company parking lot for employees only.

permissive

Open to general traffic until such time as the owner revokes the permission which they are legally allowed to do at any time in the future.

permit

Open only to people who have obtained a permit granting them access.

destination

Only when travelling to this element area; i.e. local traffic only. This is signed, for example, as 'except for access' in the UK.

delivery

Only when delivering to the element. For example motor_vehicle=delivery on a highway=pedestrian.

customers

Only for customers of the element.

designated

A preferred or designated route for the class of traffic specified by the tag key, such as foot=designated. In general this means that there is a (explicit) sign such as pedestrians allowed, or a pedestrian icon.

use_sidepath

Used to indicate that a mapped parallel way (that belongs to the same road) must be used instead. A road can legally consist of several ways, such as a single or dual carriageway with parallel tracks for cyclists, mopeds, pedestrians and/or equestrians.

dismount

Permitted for some vehicle (or animal) only if you dismount. Mostly used for bicycle, for example bicycle=dismount which indicates people are not permitted to cycle but are allowed to dismount and bring the bike.

agricultural

Only for agricultural traffic.

forestry

Only for forestry traffic.

discouraged

A legal right of way exists (see yes) but usage is officially discouraged (e.g. HGVs on narrow but passable lanes). Only if marked by a traffic sign.

variable

Value used combination with lanes to denote where access might change e.g. access:lanes=* to denote a variable-access lane.

unknown

The access conditions are unknown or unclear.

BridgeValue

This code list is used in association with the Bridge attribute which is present within the Transport Link Feature Type. The code list describes the nature of the bridge crossed by the Transport Link.

Label

Definition

yes

Indicates that there is a bridge.

aqueduct

A longer structure for carrying a canal or fresh water.

boardwalk

A plank walkway over wet or otherwise difficult terrain, usually low to the ground and supported by posts.

cantilever

A bridge where a span is supported at one end only. Usually, the free ends of two spans are fastened to one another, giving a longer clear span between supports.

covered

A covered bridge has a roof and fully or partly enclosed sides, usually to protect the bridge deck and members from deterioration.

low_water_crossing

Also known as an Irish bridge, this is a low bridge which is engineered to carry vehicles above water at low flow levels and survive submersion at high flow levels.

movable

Movable bridges contain a span that can be moved up or to the side, often to provide greater clearance for traffic moving beneath the bridge.

trestle

A bridge composed of a series of short spans where each span is supported by a rigid frame, usually called a bent rather than a pier.

viaduct

A bridge composed of a series of spans, often short relative to its overall length. The spans may be arches, girders supported by piers.

HighwayValue

This code list is used in association with the Highway attribute which is present within the Transport Link Feature Type. For Transport Links that represent road or path features, this value describes the type of road or path represented e.g. 'Motorway', 'Footway', 'Trunk_primary'.

Label

Definition

motorway

A restricted access major divided highway, normally with 2 or more running lanes plus emergency hard shoulder.

trunk

The most important roads in a country's system that aren't motorways. Not necessarily a divided highway.

primary

The next most important roads in a country's system. Often link larger towns.

secondary

The next most important roads in a country's system. Often link towns.

tertiary

The next most important roads in a country's system. Often link smaller towns and villages.

unclassified

The least important through roads in a country's system i.e. minor roads of a lower classification than tertiary, but which serve a purpose other than access to properties. Often link villages and hamlets. The word 'unclassified' is a historical artefact of the UK road system and does not mean that the classification is unknown.

residential

Roads which serve as an access to housing without the function of connecting settlements. Often lined with housing.

motorway_link

The link roads (sliproads/ramps) leading to/from a motorway from/to a motorway or lower class highway. Normally with the same motorway restrictions.

trunk_link

The link roads (sliproads/ramps) leading to/from a trunk road from/to a trunk road or lower class highway.

primary_link

The link roads (sliproads/ramps) leading to/from a primary road from/to a primary road or lower class highway.

secondary_link

The link roads (sliproads/ramps) leading to/from a secondary road from/to a secondary road or lower class highway.

tertiary_link

The link roads (sliproads/ramps) leading to/from a tertiary road from/to a tertiary road or lower class highway.

living_street

For living streets which are residential streets where pedestrians have legal priority over cars. Speeds are kept very low and where children are allowed to play on the street.

service

For access roads or within an industrial estate, camp site, business park, car park, alleys etc.

pedestrian

For roads used mainly/exclusively for pedestrians in shopping and some residential areas which may allow access by motorised vehicles only for very limited periods of the day. To create a 'square' or 'plaza' create a closed way and tag as pedestrian.

track

Roads for mostly agricultural or forestry uses.

bus_guideway

A busway where the vehicle guided by the way (though not a railway) and is not suitable for other traffic.

escape

For runaway truck ramps, runaway truck lanes, emergency escape ramps, or truck arrester beds. It enables vehicles with braking failure to safely stop.

raceway

A course or track for (motor) racing

road

A road/way/street/motorway/etc. of unknown type. It can stand for anything ranging from a footpath to a motorway.

busway

A dedicated roadway for bus rapid transit systems.

footway

For designated footpaths mainly/exclusively for pedestrians. This includes walking tracks and gravel paths.

bridleway

For horse riders. Pedestrians are usually also permitted, cyclists may be permitted depending on local rules/laws. Motor vehicles are forbidden.

steps

Indication of whether there are steps.

corridor

For a hallway inside of a building.

path

A non-specific path.

via_ferrata

A via ferrata is a route equipped with fixed cables, stemples, ladders, and bridges in order to increase ease and security for climbers.

cycleway

For designated cycleways.

proposed

For planned roads

construction

For roads under construction.

bus_stop

A small bus stop where passengers wait.

crossing

A crosswalk. Pedestrians can cross a street here; e.g. zebra crossing.

elevator

An elevator or lift, used to travel vertically, providing passenger and freight access between pathways at different floor levels.

emergency_bay

An area beside a highway where you can safely stop your car in case of breakdown or emergency.

give_way

A give way or Yield sign

milestone

Highway location marker

mini_roundabout

Similar to roundabouts, but at the center there is either a painted circle or a fully traversable island.

motorway_junction

Indicates a junction. ref=* should be set to the exit number or junction identifier. Some roads – e.g., the A14 – also carry junction numbers, so the tag may be encountered elsewhere despite its name

passing_place

The location of a passing space.

platform

A platform at a bus stop or station.

rest_area

Place where drivers can leave the road to rest, but not refuel.

services

A service station to get food and eat something, often found at motorways.

speed_camera

A fixed road-side or overhead speed camera.

stop

A stop sign.

street_lamp

A street light, lamppost, street lamp, light standard, or lamp standard is a raised source of light on the edge of a road, which is turned on or lit at a certain time every night.

toll_gantry

A toll gantry is a gantry suspended over a way, usually a motorway, as part of a system of electronic toll collection.

traffic_mirror

Mirror that reflects the traffic on one road when direct view is blocked.

traffic_signals

Lights that control the traffic

trailhead

Designated place to start on a trail or route

turning_circle

A turning circle is a rounded, widened area usually, but not necessarily, at the end of a road to facilitate easier turning of a vehicle. Also known as a cul de sac.

turning_loop

A widened area of a highway with a non-traversable island for turning around, often circular and at the end of a road.

JunctionValue

This code list is used in association with the Junction attribute which is present within the Transport Link Feature Type. The code list describes the nature of the junction that the Transport Link forms part of.

Label

Definition

roundabout

A road junction where the traffic goes around a non-traversable island and has right of way.

circular

A road junction where the traffic goes around a non-traversable island but does not always have right of way.

jughandle

A jughandle is an at-grade intersection which includes a type of ramp or slip road that takes traffic turning across the centreline (left in right-hand-drive countries) in the other direction before looping around.

filter

A type of junction that assigns priority to junction users based on the order in which they arrive at the junction. It is usually combined with a box junction so users of the junction must not enter the junction unless their exit is clear.

OneWayValue

This code list is used in association with the One Way attribute which is present within the Transport Link Feature Type. It indicates whether there is a one-way restriction on a Transport Link.

Label

Definition

yes

Indicates travel only in the link direction.

Indicates travel in both directions.

-1

Indicates travel only against the link direction.

reversible

Roads that alternate between different directions regularly but infrequently.

alternating

Roads that alternate between different directions regularly and often.

RailServiceValue

This code list is used in association with the Service attribute which is present within the Transport Link Feature Type. It indicates additional detail about the type of railway service line that a Transport Link represents. Only populated with 'siding' or Null.

Label

Definition

yard

Tracks within marshalling or maintenance yards which are operated by the railway company.

siding

Relatively short lengths of track which run parallel to the main track and are connected to it. These tracks are used by slower trains to be overtaken or to let passengers enter/leave the train if the main tracks do not have platforms.

spur

Relatively short lengths of track connecting a company or entity (e.g. a factory or power plant) to the main railway network.

crossover

Short lengths of track which switch traffic from one parallel line to another. Found only on double or more tracked railways.

TunnelValue

This code list is used in association with the Tunnel attribute which is present within the Transport Link Feature Type. On Transport Links that represent a road feature, it indicates whether there is a presence of a Tunnel, e.g 'yes' or Null.

Label

Definition

pgRouting

Instructions to get you started with using OS MRN in pgRouting.

extends the PostGIS / PostgreSQL geospatial database to provide routing and other network analysis functionality.

What you need

(or any other database explorer)
(optional – see note below)

QGIS provides a few useful options for pgRouting and the handling of OS MRN data:

Part of the QGIS install gives access to a command prompt that comes with some spatial functionality for data management without needing much setup (this will be covered in more detail below).
It can be linked in with the PostgreSQL database to allow for visualising existing tables and pgRouting results.
It gives access to pgRouting in plugin form, allowing routes to be calculated within QGIS using those database tables.

Introduction to graph data and routing

A graph data structure is made up of nodes and edges. With OS MRN, these are represented by the mrn_ntwk_transportnode and mrn_ntwk_transportlink layers.

Nodes are points that represent junctions connecting one or more paths on a network. This is where a decision is made on where to turn next (or stop if you are at the end of the route). All nodes must connect to an edge.

Edges connect two or more nodes, and represent the distance between them. They can be directed (for example, one-way restrictions) or undirected (any direction allowed). Their default direction will be in the direction the edge was digitised, from startpoint to endpoint.

The distance is a reflection of the cost to travel along that edge. At the base level, this would be the length of the edge (in metres), but can be extended with maths to incorporate things like the speed of travel along the edge.

Using other data you may have, cost can be extended even further, for example, to take into account factors that might make a traveller use a particular route more (such as scenery, traffic, points of interest and gradient).

With pgRouting, these costs can be applied to each edge in a particular direction, that is, in direction (the direction of digitising) and in reverse direction. This enables the user to have more control on what the routing algorithms look for.

Routing algorithms

Routing algorithms are a set of rules used to determine the best path between two or more points. Some of the common ones used are:

Checking that PostGIS and pgRouting are enabled

In more recent versions of PostgreSQL, both PostGIS and pgRouting are enabled as standard, ready to be used.

To check this:

Load pgAdmin4 (or your chosen database explorer).
Highlight your database.
Open a SQL window and run:

In the example above, PostGIS was already enabled. However, in the example below, pgRouting wasn't enabled, but is now ready to be used within the selected database:

Loading the GeoPackage

Before loading the GPKG, check that environment variables have been set up so that PostgreSQL will be recognised by the command prompt. Admin permissions are required to edit these variables.
Add the folder location of your PostgreSQL install to the User->Path and System->Path variables.
Once you have done this, open the OSGeo4W Shell (as shown above), and type in ogr2ogr. If everything is setup correctly, you should see:
To then load the OS MRN GPKG into your PostgreSQL database, navigate to the location of the file, and type the following:

You could alternatively use the following command (where /vsizip/ is a file handler that allows reading ZIP archives on-the-fly without decompressing them beforehand):

This will load the three layers of the OS MRN GPKG into the defined database schema, and create the relevant spatial indexes.

You can now add some further attribute indexes for the unique identifiers:

With all the indexes added, you can create a basic edge table on which to start routing:

Loading the Protocolbuffer Binary Format

To find out if you have Java installed, open PowerShell / Command Prompt (Windows) or Shell (Linux) and type:

Once osm2po is downloaded and extracted, open and edit the config file to satisfy your usage requirements (for example, change the wtr.finalMask = car line (use Ctrl+F to search the file) to car,foot,bike travel types).
Uncomment the following line (this helps with getting the topology into a format pgRouting likes):

When this is done, and assuming Java is installed and accessible, open a command prompt and navigate to the location of the .pbf file, and then run the following:

This will create the .sql file version of the .pbf file.

Import the .sql file version of the .pbf file to the PostgreSQL database using the following:

In this newly created table, each record should have a source and target node, and an integer classification. Cost and reverse cost columns are also applied. Cost in this case is worked out using distance (in km) and speed (kmh) defined in the config file.

Running a test route with pgRouting (Dijkstra)

The mandatory things pgRouting needs to be able to route with are a routing table, start node and end node. Once the routing table is created, pgRouting can be run straight away.

For the following example, OS MRN sample data has been used, with the GPKG data being loaded into PostgreSQL via ogr2ogr (with the SQL run to create basic edge table). A couple of waypoints have been selected in Exeter, and a sample Dijkstra route query can look like the one below:

This route query is made up of three parts:

First, the 'start' section finds the start node to use from the network that is closest to the point given. This could be fed in to the query in multiple ways, such as clicking on a web map, or using a plugin.
Second, the 'destination' section finds the start node closest to the destination point given.
The final part includes the pgr_dijkstra function, reading in the start and destination ids, and returns a merged geometry of links that form the route.

When visualised in QGIS, the result should look similar to this:

It should be noted that the above route query does not take any of the additional OS MRN attribution into account. This means that every edge will be considered when calculating the shortest path. We can therefore apply some additional logic in the SELECT statement to facilitate either vehicular or pedestrian routing:

GraphHopper

Instructions to get you started with using OS MRN in GraphHopper.

is an open source routing engine for OpenStreetMap (OSM).

What you need

(Java 17+)
and

To find out if you have Java installed:

Open PowerShell / Command Prompt (Windows) or Shell (Linux) and type:

Press Enter. If Java is installed, you should see a few lines of text detailing which version you have installed. If you get something along the lines of "java is not recognized ..." please download JVM [or OpenJDK] using the link above in 'What you need'.

To see if you already have Node.js and npm installed and check the installed version:

Run the following commands:

If they are not installed, please follow the .

GraphHopper Routing Engine

The explains how to download and run the GraphHopper Routing Engine as a Java library or standalone web server to calculate the distance, time, turn-by-turn instructions and many road attributes for a route between two or more points.

To create routes using OS MRN, you require the following files (ensure that they are stored in the same directory):

A YAML configuration file (config-example.yml)

We have created a custom version of this file which allows for vehicular (car) routing with turn costs, as well as the calculation of pedestrian (walking) and cycling routes:

Compared to the basic configuration file, you'll see that the custom version enables turn restrictions (under the car profile) and includes additional profiles to enable cycling and walking:

The turn_costs line tells GraphHopper to force the car travel mode ("profile") to respect turn restrictions.
The u_turn_costs line tells GraphHopper how long a U-turn should add to your route (in this case, 60 seconds).
The custom_model_files are required but can be empty. The optional bike.json is a reference to a specification to get cycle routing to prefer less busy roads, for example.

By default (i.e. only using driving routing), GraphHopper knows there's no need to read in footpaths, cycleways, etc. Now that you want the additional "profiles", you need to change that.

This means that there is one final configuration change you need to do which will force GraphHopper to read every type of link:

Use Ctrl+F to search the config-example-multiple.ymlfile for:

You can now start the GraphHopper Maps UI and the web service as follows:

This reads in the OS MRN data and sets everything up. It might take a few minutes the first time you run this command, but when complete, you will see two folders have been added to your directory: "graph-cache" and "logs".

When you start GraphHopper again, it will see the data contained within the "graph-cache" folder and know that it doesn't have to re-read the PBF file. However, if you update your .pbf or .yml files, make sure you delete "graph-cache" before starting GraphHopper again.

Right-click on the map to create a route.

GraphHopper Maps

Transport Link

A Transport Link is a linear spatial object that defines the geometry and connectivity of a road, path, rail, or ferry network between two points in the network. Transport Links are split for connectivity purposes (for example, at junctions), and connect the Transport Links together. Each Transport Link provides a reference to the Transport Nodes at the start and end of the Transport Link.

Temporal filtering

The earliest date on which you can request a one-off snapshot of a date in the past for data in this feature type is 27 March 2024.

Feature type attributes

For more information about the Transport Link Feature Type, please read the page in the .

The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

wayid

A unique numerical ID given to each Transport Link. This is commonly used by routing software as the primary identifier for the feature.

Data Types: Integer (GPKG), Integer (PBF)
Nullable: false
Max Length: 10
Data Schema Version: 1.0

os_parentid

The OSID of the corresponding feature that is published in the OS NGD Transport Network Collection. Where Transport Links have been split due to grade separation, this will be indicated with the suffix --s.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 40
Data Schema Version: 1.0

os_startnode

The OSID of the start node of the Transport Link in the OS NGD Transport Network Collection.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 40
Data Schema Version: 1.0

os_endnode

The OSID of the end node of the Transport Link in the OS NGD Transport Network Collection.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 40
Data Schema Version: 1.0

os_roadwidthminimum

Value of the minimum width of the road carriageway for Transport Links representing road features. This attribute will be NULL for all Transport Links representing rail, ferry, path or modal change links.

Data Types: Float (GPKG), Real (PBF)
Nullable: true
Precision: 3
Scale: 1
Data Schema Version: 1.0

name

Name given to a Transport Link to identify it, for example, road name, number or description. If there is a known alternate name or a name known in an alternate language, such as Welsh, then these will be separated by a '/', for example, 'Heol Casnewydd / Newport Road / A4161'.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

ascent:forward

Total accumulated ascent in metres in the direction of digitisation of Transport Links that represent road or path features.

Data Types: Float (GPKG), String (PBF)
Nullable: true
Precision: 6
Scale: 1
Data Schema Version: 1.0

ascent:backward

Total accumulated ascent in metres against the direction of digitisation of Transport Links that represent road or path features.

Data Types: Float (GPKG), String (PBF)
Nullable: true
Precision: 6
Scale: 1
Data Schema Version: 1.0

access

Indicates the nature of access permitted for all vehicles and, if applicable, the type of access restrictions along a Transport Link.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

access:forward

Indicates the nature of access permitted for all vehicles and, if applicable, the type of access restrictions along a Transport Link. This attribute will only be populated if the access permissions only apply in the direction of digitisation of the link and not in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

access:backward

Indicates the nature of access permitted for all vehicles and, if applicable, the type of access restrictions along a Transport Link. This attribute will only be populated if the access permissions only apply against the direction of digitisation of the link and not in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

foot

Indicates whether a Transport Link can be traversed by foot and whether there is designated infrastructure for walking along a Transport Link.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length:
Data Schema Version: 1.0

os_overallpavementpresence

Indicates the percentage of a Transport Link that is served by a pavement.

Data Types: Integer (GPKG), String (PBF)
Nullable: true
Max Length: 3
Data Schema Version: 1.0

highway

For Transport Links that represent road or path features, this attribute describes the type of road or path represented, for example, 'Motorway', 'Footway', 'Trunk_primary'.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length:
Data Schema Version: 1.0

railway

For Transport Links that represent railway features, this attribute describes the type of railway infrastructure represented, for example, 'rail', 'tram'.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 19
Data Schema Version: 1.0

rail

Indicates whether a Transport Link is accessible by rail, and, if applicable, the type of railway service it is accessible by, for example, 'Passenger', 'Freight'.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

ferry

Indicates whether a Transport Link is accessible by ferry.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

toll

Indicates whether there is a presence of a toll payment on Transport Links that represent a road feature.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

junction

Indicates the type of junction that a Transport Link forms part of. Note: Only 'roundabout' is populated in the current release.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 10
Data Schema Version: 1.0

route

Indicates the type of transport route that a Transport Link forms a part of in the real world, for example, 'Railway', 'Ferry'.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 14
Data Schema Version: 1.0

ford

Indicates whether there is a presence of a ford on Transport Links that represent a road feature, for example, 'yes' or Null.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 15
Data Schema Version: 1.0

bridge

Indicates whether a Transport Link crosses over a bridge feature. Note: This is only populated for Transport Links representing Path Links.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 18
Data Schema Version: 1.0

tunnel

Indicates whether there is a presence of a Tunnel on Transport Links that represent a road feature, for example, 'yes' or Null.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 16
Data Schema Version: 1.0

service

Indicates additional detail about the type of railway service line that a Transport Link represents. Only populated with 'siding' or Null.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 9
Data Schema Version: 1.0

motor_vehicle

Indicates the nature of access permitted specifically for motor vehicles along a Transport Link.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

motor_vehicle:conditional

If the nature of access permitted for motor vehicles along a Transport Link varies depending on specific times or days, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in motor_vehicle applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

motor_vehicle:forward

Indicates the nature of access permitted specifically for motor vehicles along a Transport Link. This attribute will only be populated if the access permissions for motor vehicles only apply in the direction of digitisation of the link and not in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

motor_vehicle:forward:conditional

If the nature of access permitted for motor vehicles along a Transport Link varies depending on specific times or days and only applies in the direction of digitisation of the link, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in motor_vehicle applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

motor_vehicle:backward

Indicates the nature of access permitted specifically for motor vehicles along a Transport Link. This attribute will only be populated if the access permissions for motor vehicles only apply against the direction of digitisation of the link and not in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

motor_vehicle:backward:conditional

If the nature of access permitted for motor vehicles along a Transport Link varies depending on specific times or days and only applies against the direction of digitisation of the link, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in motor_vehicle applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

bicycle

Indicates the nature of access permitted specifically for bicycles along a Transport Link.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

bicycle:conditional

If the nature of access permitted for bicycles along a Transport Link varies depending on specific times or days, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in bicycle applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

bicycle:forward

Indicates the nature of access permitted specifically for bicycles along a Transport Link. This attribute will only be populated if the access permissions for bicycles only apply in the direction of digitisation of the link and not in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

bicycle:forward:conditional

If the nature of access permitted for bicycles along a Transport Link varies depending on specific times or days and only applies in the direction of digitisation of the link, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in bicycle applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

bicycle:backward

Indicates the nature of access permitted specifically for bicycles along a Transport Link. This attribute will only be populated if the access permissions for bicycles only apply against the direction of digitisation of the link and not in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

bicycle:backward:conditional

If the nature of access permitted for bicycles along a Transport Link varies depending on specific times or days and only applies against the direction of digitisation of the link, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in bicycle applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

motorcycle

Indicates the nature of access permitted specifically for motorcycles along a Transport Link.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

motorcycle:conditional

If the nature of access permitted for motorcycles along a Transport Link varies depending on specific times or days, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in motorcycles applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

motorcycle:forward

Indicates the nature of access permitted specifically for motorcycles along a Transport Link. This attribute will only be populated if the access permissions for motorcycles only apply in the direction of digitisation of the link and not in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

motorcycle:forward:conditional

If the nature of access permitted for motorcycles along a Transport Link varies depending on specific times or days and only applies in the direction of digitisation of the link, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in motorcycle applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

motorcycle:backward

Indicates the nature of access permitted specifically for motorcycles along a Transport Link. This attribute will only be populated if the access permissions for motorcycles only apply against the direction of digitisation of the link and not in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

motorcycle:backward:conditional

If the nature of access permitted for motorcycles along a Transport Link varies depending on specific times or days and only applies against the direction of digitisation of the link, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in motorcycle applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

moped

Indicates the nature of access permitted specifically for mopeds along a Transport Link.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

moped:conditional

If the nature of access permitted for mopeds along a Transport Link varies depending on specific times or days, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in moped applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

moped:forward

Indicates the nature of access permitted specifically for mopeds along a Transport Link. This attribute will only be populated if the access permissions for mopeds only apply in the direction of digitisation of the link and not in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

moped:forward:conditional

If the nature of access permitted for mopeds along a Transport Link varies depending on specific times or days and only applies in the direction of digitisation of the link, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in moped applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

moped:backward

Indicates the nature of access permitted specifically for mopeds along a Transport Link. This attribute will only be populated if the access permissions for mopeds only apply against the direction of digitisation of the link and not in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

moped:backward:conditional

If the nature of access permitted for mopeds along a Transport Link varies depending on specific times or days and only applies against the direction of digitisation of the link, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in moped applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

psv

Indicates the nature of access permitted specifically for public service vehicles along a Transport Link.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

psv:conditional

If the nature of access permitted for public service vehicles along a Transport Link varies depending on specific times or days, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in psv applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

psv:forward

Indicates the nature of access permitted specifically for public service vehicles along a Transport Link. This attribute will only be populated if the access permissions for public service vehicles only apply in the direction of digitisation of the link and not in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

psv:forward:conditional

If the nature of access permitted for public service vehicles along a Transport Link varies depending on specific times or days and only applies in the direction of digitisation of the link, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in psv applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

psv:backward

Indicates the nature of access permitted specifically for public service vehicles along a Transport Link. This attribute will only be populated if the access permissions for public service vehicles only apply against the direction of digitisation of the link and not in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

psv:backward:conditional

If the nature of access permitted for public service vehicles along a Transport Link varies depending on specific times or days and only applies against the direction of digitisation of the link, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in psv applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

coach

Indicates the nature of access permitted specifically for coaches along a Transport Link.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

coach:conditional

If the nature of access permitted for coaches along a Transport Link varies depending on specific times or days, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in coach applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

coach:forward

Indicates the nature of access permitted specifically for coaches along a Transport Link. This attribute will only be populated if the access permissions for coaches only apply in the direction of digitisation of the link and not in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

coach:forward:conditional

If the nature of access permitted for coaches along a Transport Link varies depending on specific times or days and only applies in the direction of digitisation of the link, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in coaches applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

coach:backward

Indicates the nature of access permitted specifically for coaches along a Transport Link. This attribute will only be populated if the access permissions for coaches only apply against the direction of digitisation of the link and not in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

coach:backward:conditional

If the nature of access permitted for coaches along a Transport Link varies depending on specific times or days and only applies against the direction of digitisation of the link, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in coaches applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

bus

Indicates the nature of access permitted specifically for buses along a Transport Link.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

bus:conditional

If the nature of access permitted for buses along a Transport Link varies depending on specific times or days, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in bus applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

bus:forward

Indicates the nature of access permitted specifically for buses along a Transport Link. This attribute will only be populated if the access permissions for buses only apply in the direction of digitisation of the link and not in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

bus:forward:conditional

If the nature of access permitted for buses along a Transport Link varies depending on specific times or days and only applies in the direction of digitisation of the link, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in bus applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

bus:backward

Indicates the nature of access permitted specifically for buses along a Transport Link. This attribute will only be populated if the access permissions for buses only apply against the direction of digitisation of the link and not in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

bus:backward:conditional

If the nature of access permitted for buses along a Transport Link varies depending on specific times or days and only applies against the direction of digitisation of the link, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in bus applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

goods

Indicates the nature of access permitted specifically for goods vehicles along a Transport Link.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

goods:conditional

If the nature of access permitted for goods vehicles along a Transport Link varies depending on specific times or days, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in goods applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

goods:forward

Indicates the nature of access permitted specifically for goods vehicles along a Transport Link. This attribute will only be populated if the access permissions for goods vehicles only apply in the direction of digitisation of the link and not in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

goods:forward:conditional

If the nature of access permitted for goods vehicles along a Transport Link varies depending on specific times or days and only applies in the direction of digitisation of the link, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in goods applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

goods:backward

Indicates the nature of access permitted specifically for goods vehicles along a Transport Link. This attribute will only be populated if the access permissions for goods vehicles only apply against the direction of digitisation of the link and not in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

goods:backward:conditional

If the nature of access permitted for goods vehicles along a Transport Link varies depending on specific times or days and only applies against the direction of digitisation of the link, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in goods applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

hgv

Indicates the nature of access permitted specifically for heavy goods vehicles along a Transport Link.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

hgv:conditional

If the nature of access permitted for heavy goods vehicles along a Transport Link varies depending on specific times or days, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in hgv applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

hgv:forward

Indicates the nature of access permitted specifically for heavy goods vehicles along a Transport Link. This attribute will only be populated if the access permissions for heavy goods vehicles only apply in the direction of digitisation of the link and not in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

hgv:forward:conditional

If the nature of access permitted for heavy goods vehicles along a Transport Link varies depending on specific times or days and only applies in the direction of digitisation of the link, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in hgv applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

hgv:backward

Indicates the nature of access permitted specifically for heavy goods vehicles along a Transport Link. This attribute will only be populated if the access permissions for heavy goods vehicles only apply against the direction of digitisation of the link and not in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

hgv:backward:conditional

If the nature of access permitted for heavy goods vehicles along a Transport Link varies depending on specific times or days and only applies against the direction of digitisation of the link, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in hgv applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

taxi

Indicates the nature of access permitted specifically for taxis along a Transport Link.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

taxi:conditional

If the nature of access permitted for taxis along a Transport Link varies depending on specific times or days, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in taxi applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

taxi:forward

Indicates the nature of access permitted specifically for taxis along a Transport Link. This attribute will only be populated if the access permissions for taxis only apply in the direction of digitisation of the link and not in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

taxi:forward:conditional

If the nature of access permitted for taxis along a Transport Link varies depending on specific times or days and only applies in the direction of digitisation of the link, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in taxi applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

taxi:backward

Indicates the nature of access permitted specifically for taxis along a Transport Link. This attribute will only be populated if the access permissions for taxis only apply against the direction of digitisation of the link and not in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

taxi:backward:conditional

If the nature of access permitted for taxis along a Transport Link varies depending on specific times or days and only applies against the direction of digitisation of the link, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in taxi applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

trailer

Indicates the nature of access permitted specifically for trailers along a Transport Link.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

trailer:conditional

If the nature of access permitted for trailers along a Transport Link varies depending on specific times or days, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in trailer applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

trailer:forward

Indicates the nature of access permitted specifically for trailers along a Transport Link. This attribute will only be populated if the access permissions for trailers only apply in the direction of digitisation of the link and not in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

trailer:forward:conditional

If the nature of access permitted for trailers along a Transport Link varies depending on specific times or days and only applies in the direction of digitisation of the link, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in trailer applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

trailer:backward

Indicates the nature of access permitted specifically for trailers along a Transport Link. This attribute will only be populated if the access permissions for trailers only apply against the direction of digitisation of the link and not in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

trailer:backward:conditional

If the nature of access permitted for trailers along a Transport Link varies depending on specific times or days and only applies against the direction of digitisation of the link, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in trailer applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

caravan

Indicates the nature of access permitted specifically for caravans along a Transport Link.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

caravan:conditional

If the nature of access permitted for caravans along a Transport Link varies depending on specific times or days, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in caravan applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

caravan:forward

Indicates the nature of access permitted specifically for caravans along a Transport Link. This attribute will only be populated if the access permissions for caravans only apply in the direction of digitisation of the link and not in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

caravan:forward:conditional

If the nature of access permitted for caravans along a Transport Link varies depending on specific times or days and only applies in the direction of digitisation of the link, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in caravan applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

caravan:backward

Indicates the nature of access permitted specifically for caravans along a Transport Link. This attribute will only be populated if the access permissions for caravans only apply against the direction of digitisation of the link and not in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

caravan:backward:conditional

If the nature of access permitted for caravans along a Transport Link varies depending on specific times or days and only applies against the direction of digitisation of the link, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in caravan applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

emergency

Indicates the nature of access permitted specifically for emergency vehicles along a Transport Link.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

emergency:conditional

If the nature of access permitted for emergency vehicles along a Transport Link varies depending on specific times or days, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in emergency applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

emergency:forward

Indicates the nature of access permitted specifically for emergency vehicles along a Transport Link. This attribute will only be populated if the access permissions for emergency vehicles only apply in the direction of digitisation of the link and not in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

emergency:forward:conditional

If the nature of access permitted for emergency vehicles along a Transport Link varies depending on specific times or days and only applies in the direction of digitisation of the link, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in emergency applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

emergency:backward

Indicates the nature of access permitted specifically for emergency vehicles along a Transport Link. This attribute will only be populated if the access permissions for emergency vehicles only apply against the direction of digitisation of the link and not in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

emergency:backward:conditional

If the nature of access permitted for emergency vehicles along a Transport Link varies depending on specific times or days and only applies against the direction of digitisation of the link, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in emergency applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

hazmat

Indicates the nature of access permitted specifically for hazmat vehicles along a Transport Link.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

hazmat:conditional

If the nature of access permitted for hazmat vehicles along a Transport Link varies depending on specific times or days, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in hazmat applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

hazmat:forward

Indicates the nature of access permitted specifically for hazmat vehicles along a Transport Link. This attribute will only be populated if the access permissions for hazmat vehicles only apply in the direction of digitisation of the link and not in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

hazmat:forward:conditional

If the nature of access permitted for hazmat vehicles along a Transport Link varies depending on specific times or days and only applies in the direction of digitisation of the link, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in hazmat applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

hazmat:backward

Indicates the nature of access permitted specifically for hazmat vehicles along a Transport Link. This attribute will only be populated if the access permissions for hazmat vehicles only apply against the direction of digitisation of the link and not in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

hazmat:backward:conditional

If the nature of access permitted for hazmat vehicles along a Transport Link varies depending on specific times or days and only applies against the direction of digitisation of the link, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in hazmat applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

disabled

Indicates the nature of access permitted specifically for vehicles travelling with occupants with a disability along a Transport Link.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

disabled:conditional

If the nature of access permitted for vehicles travelling with occupants with a disability along a Transport Link varies depending on specific times or days, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in disabled applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

disabled:forward

Indicates the nature of access permitted specifically for vehicles travelling with occupants with a disability along a Transport Link. This attribute will only be populated if the access permissions for vehicles travelling with occupants with a disability only apply in the direction of digitisation of the link and not in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

disabled:forward:conditional

If the nature of access permitted for vehicles travelling with occupants with a disability along a Transport Link varies depending on specific times or days and only applies in the direction of digitisation of the link, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in disabled applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

disabled:backward

Indicates the nature of access permitted specifically for vehicles travelling with occupants with a disability along a Transport Link. This attribute will only be populated if the access permissions for vehicles travelling with occupants with a disability only apply against the direction of digitisation of the link and not in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 12
Data Schema Version: 1.0

disabled:backward:conditional

If the nature of access permitted for vehicles travelling with occupants with a disability along a Transport Link varies depending on specific times or days and only applies against the direction of digitisation of the link, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), the access value in disabled applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

maxweight:hgv

Indicates whether there are any specific access restrictions for Heavy Goods Vehicles where a maximum permitted weight has been specified along a Transport Link. Uses values similar to those in the access attribute (for example, 'yes', 'no' or 'destination'), but represents specific access restrictions for vehicles with a maximum weight.

Data Types: Float (GPKG), String (PBF)
Nullable: true
Precision: 6
Scale: 1
Data Schema Version: 1.0

maxweight:hgv:conditional

If the access restrictions for Heavy Goods Vehicles where a maximum permitted weight has been specified along a Transport Link vary depending on specific times or days, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, '7.5t @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), then the access value in maxweight:hgv applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

maxweight:hgv:forward

Indicates whether there are any specific access restrictions for Heavy Goods Vehicles where a maximum permitted weight has been specified along a Transport Link. This attribute will only be populated if the access restrictions for vehicles with a maximum weight only apply in the direction of digitisation of the link and not in both directions.

Data Types: Float (GPKG), String (PBF)
Nullable: true
Precision: 6
Scale: 1
Data Schema Version: 1.0

maxweight:hgv:forward:conditional

If the access restrictions for Heavy Goods Vehicles where a maximum permitted weight has been specified along a Transport Link vary depending on specific times or days and this restriction only applies in the direction of digitisation of the link, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), then the access value in maxweight:hgv applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

maxweight:hgv:backward

Indicates whether there are any specific access restrictions for Heavy Goods Vehicles where a maximum permitted weight has been specified along a Transport Link. This attribute will only be populated if the access restrictions for vehicles with a maximum weight only apply against the direction of digitisation of the link and not in both directions.

Data Types: Float (GPKG), String (PBF)
Nullable: true
Precision: 6
Scale: 1
Data Schema Version: 1.0

maxweight:hgv:backward:conditional

If the access restrictions for Heavy Goods Vehicles where a maximum permitted weight has been specified along a Transport Link very depending on specific times or days and this restriction only applies against the direction of digitisation of the link, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), then the access value in maxweight:hgv applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

maxweight

The maximum allowed weight of any vehicle along a Transport Link.

Data Types: Float (GPKG), String (PBF)
Nullable: true
Precision: 6
Scale: 1
Data Schema Version: 1.0

maxweight:forward

The maximum allowed weight of any vehicle along a Transport Link. This attribute will only be populated if the access restrictions for vehicles exceeding the maximum weight only apply in the direction of digitisation of the link and not in both directions.

Data Types: Float (GPKG), String (PBF)
Nullable: true
Precision: 6
Scale: 1
Data Schema Version: 1.0

maxweight:backward

The maximum allowed weight of any vehicle along a Transport Link. This attribute will only be populated if the access restrictions for vehicles exceeding the maximum weight only apply against the direction of digitisation of the link and not in both directions.

Data Types: Float (GPKG), String (PBF)
Nullable: true
Precision: 6
Scale: 1
Data Schema Version: 1.0

maxheight

The maximum allowed height of any vehicle along a Transport Link.

Data Types: Float (GPKG), String (PBF)
Nullable: true
Precision: 6
Scale: 1
Data Schema Version: 1.0

maxheight:forward

The maximum allowed height of any vehicle along a Transport Link. This attribute will only be populated if the access restrictions for vehicles exceeding the maximum height only apply in the direction of digitisation of the link and not in both directions.

Data Types: Float (GPKG), String (PBF)
Nullable: true
Precision: 6
Scale: 1
Data Schema Version: 1.0

maxheight:backward

The maximum allowed height of any vehicle along a Transport Link. This attribute will only be populated if the access restrictions for vehicles exceeding the maximum height only apply against the direction of digitisation of the link and not in both directions.

Data Types: Float (GPKG), String (PBF)
Nullable: true
Precision: 6
Scale: 1
Data Schema Version: 1.0

maxlength

The maximum allowed length of any vehicle along a Transport Link.

Data Types: Float (GPKG), String (PBF)
Nullable: true
Precision: 6
Scale: 1
Data Schema Version: 1.0

maxlength:forward

The maximum allowed length of any vehicle along a Transport Link. This attribute will only be populated if the access restrictions for vehicles exceeding the maximum length only apply in the direction of digitisation of the link and not in both directions.

Data Types: Float (GPKG), String (PBF)
Nullable: true
Precision: 6
Scale: 1
Data Schema Version: 1.0

maxlength:backward

The maximum allowed length of any vehicle along a Transport Link. This attribute will only be populated if the access restrictions for vehicles exceeding the maximum length only apply against the direction of digitisation of the link and not in both directions.

Data Types: Float (GPKG), String (PBF)
Nullable: true
Precision: 6
Scale: 1
Data Schema Version: 1.0

maxaxleload

The maximum allowed axle load of any vehicle along a Transport Link.

Data Types: Float (GPKG), String (PBF)
Nullable: true
Precision: 6
Scale: 1
Data Schema Version: 1.0

maxaxleload:forward

The maximum allowed axle load of any vehicle along a Transport Link. This attribute will only be populated if the access restrictions for vehicles exceeding the maximum axle load only apply in the direction of digitisation of the link and not in both directions.

Data Types: Float (GPKG), String (PBF)
Nullable: true
Precision: 6
Scale: 1
Data Schema Version: 1.0

maxaxleload:backward

The maximum allowed axle load of any vehicle along a Transport Link. This attribute will only be populated if the access restrictions for vehicles exceeding the maximum axle load only apply against the direction of digitisation of the link and not in both directions.

Data Types: Float (GPKG), String (PBF)
Nullable: true
Precision: 6
Scale: 1
Data Schema Version: 1.0

maxwidth

The maximum allowed width of any vehicle along a Transport Link.

Data Types: Float (GPKG), String (PBF)
Nullable: true
Precision: 6
Scale: 1
Data Schema Version: 1.0

maxwidth:forward

The maximum allowed width of any vehicle along a Transport Link. This attribute will only be populated if the access restrictions for vehicles exceeding the maximum width only apply in the direction of digitisation of the link and not in both directions.

Data Types: Float (GPKG), String (PBF)
Nullable: true
Precision: 6
Scale: 1
Data Schema Version: 1.0

maxwidth:backward

The maximum allowed width of any vehicle along a Transport Link. This attribute will only be populated if the access restrictions for vehicles exceeding the maximum width only apply against the direction of digitisation of the link and not in both directions.

Data Types: Float (GPKG), String (PBF)
Nullable: true
Precision: 6
Scale: 1
Data Schema Version: 1.0

maxunladenweight

The maximum allowed unladen weight of any vehicle along a Transport Link. Note: This is not a standard OpenStreetMap tag.

Data Types: Float (GPKG), String (PBF)
Nullable: true
Precision: 6
Scale: 1
Data Schema Version: 1.0

maxunladenweight:forward

The maximum allowed unladen weight of any vehicle along a Transport Link. This attribute will only be populated if the access restrictions for vehicles exceeding the maximum unladen weight only apply in the direction of digitisation of the link and not in both directions. Note: This is not a standard OpenStreetMap tag.

Data Types: Float (GPKG), String (PBF)
Nullable: true
Precision: 6
Scale: 1
Data Schema Version: 1.0

maxunladenweight:backward

The maximum allowed unladen weight of any vehicle along a Transport Link. This attribute will only be populated if the access restrictions for vehicles exceeding the maximum unladen weight only apply against the direction of digitisation of the link and not in both directions. Note: This is not a standard OpenStreetMap tag.

Data Types: Float (GPKG), String (PBF)
Nullable: true
Precision: 6
Scale: 1
Data Schema Version: 1.0

oneway

Indicates whether there is a one-way restriction on a Transport Link. 'yes' indicates that travel is only permitted in the direction of digitisation of the Transport Link, '-1' indicates travel is permitted only against the direction of digitisation of the Transport Link, and 'no' indicates travel is permitted in both directions.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 11
Data Schema Version: 1.0

oneway:conditional

If the one-way restriction along a Transport Link varies depending on specific times or days, then the time periods will be populated here in OpenStreetMap time-conditional formatting, for example, 'no @ (Mo-Su 07:30-18:30)'. When outside of the specified time / day(s), then the value in the oneway attribute applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 250
Data Schema Version: 1.0

oneway:bicycle

Indicates whether one-way restrictions apply to bicycles specifically. If Null, the value in the oneway or oneway:conditional restriction applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 11
Data Schema Version: 1.0

oneway:motorcycle

Indicates whether one-way restrictions apply to motorcycles specifically. If Null, the value in the oneway or oneway:conditional restriction applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 11
Data Schema Version: 1.0

oneway:moped

Indicates whether one-way restrictions apply to mopeds specifically. If Null, the value in the oneway or oneway:conditional restriction applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 11
Data Schema Version: 1.0

oneway:psv

Indicates whether one-way restrictions apply to public service vehicles specifically. If Null, the value in the oneway or oneway:conditional restriction applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 11
Data Schema Version: 1.0

oneway:coach

Indicates whether one-way restrictions apply to coaches specifically. If Null, the value in the oneway or oneway:conditional restriction applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 11
Data Schema Version: 1.0

oneway:bus

Indicates whether one-way restrictions apply to buses specifically. If Null, the value in the oneway or oneway:conditional restriction applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 11
Data Schema Version: 1.0

oneway:taxi

Indicates whether one-way restrictions apply to taxis specifically. If Null, the value in the oneway or oneway:conditional restriction applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 11
Data Schema Version: 1.0

oneway:emergency

Indicates whether one-way restrictions apply to emergency vehicles specifically. If Null, the value in the oneway or oneway:conditional restriction applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 11
Data Schema Version: 1.0

oneway:private

Indicates whether one-way restrictions apply to private vehicles (which only have access on an invidual or permissive access basis) specifically. If Null, the value in the oneway or oneway:conditional restriction applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 11
Data Schema Version: 1.0

oneway:delivery

Indicates whether one-way restrictions apply to vehicles delivering goods specifically. If Null, the value in the oneway or oneway:conditional restriction applies.

Data Types: String (GPKG), String (PBF)
Nullable: true
Code List Name:
Max Length: 11
Data Schema Version: 1.0

maxspeed:forward

Speed limit along the Transport Link in the direction of digitisation of the link in kilometres per hour (kph).

Data Types: Float (GPKG), String (PBF)
Nullable: true
Precision: 3
Scale: 1
Data Schema Version: 1.0

maxspeed:backward

Speed limit along the Transport Link against the direction of digitisation of the link in kilometres per hour (kph).

Data Types: Float (GPKG), String (PBF)
Nullable: true
Precision: 3
Scale: 1
Data Schema Version: 1.0

avgspeed:forward

Single value for the average speed on a Transport Link Mon-Fri between 12:00-14:00 in kilometres per hour (kph) in the direction of digitisation of the link.

Data Types: Float (GPKG), String (PBF)
Nullable: true
Precision: 3
Scale: 1
Data Schema Version: 1.0

avgspeed:forward:conditional

Average speed values in kilometres per hour (kph) on a Transport Link in the direction of digitisation of the link, broken down into comma-separated time periods, for example, '31.95 @ (Mo-Su 00:00-05:30); 17.59 @ (Mo-Fr 05:30-09:30; PH off)'.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 450
Data Schema Version: 1.0

avgspeed:backward

Single value for the average speed on a Transport Link Mon-Fri between 12:00-14:00 in kilometres per hour (kph) against the direction of digitisation of the link.

Data Types: Float (GPKG), String (PBF)
Nullable: true
Precision: 3
Scale: 1
Data Schema Version: 1.0

avgspeed:backward:conditional

Average speed values in kilometres per hour (kph) on a Transport Link against the direction of digitisation of the link, broken down into comma-separated time periods, for example, '31.95 @ (Mo-Su 00:00-05:30); 17.59 @ (Mo-Fr 05:30-09:30; PH off)'.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 450
Data Schema Version: 1.0

layer

Indicates the vertical relationship between overlapping Transport Links at the point where they overlap. For example, a layer tag of 1 indicates that the Transport Link crosses above the Transport Link passing underneath it, which would have a layer tag of 0.

Data Types: String (GPKG), String (PBF)
Nullable: true
Max Length: 1
Data Schema Version: 1.0

nodes

A list of all the node IDs in direction order start to end.

Data Types: String (GPKG), Integer (PBF)
Nullable: false
Max Length: unbounded
Data Schema Version: 1.0

geometry

2D geometry for the feature.

Data Types: Geometry (GPKG), Geometry (PBF)
Nullable: false
Data Schema Version: 1.0
Geometry Type: MultiLineString

pgRouting

Instructions to get you started with using OS MRN in pgRouting.

extends the PostGIS / PostgreSQL geospatial database to provide routing and other network analysis functionality.

What you need

(or any other database explorer)
(optional – see note below)

QGIS provides a few useful options for pgRouting and the handling of OS MRN data:

Part of the QGIS install gives access to a command prompt that comes with some spatial functionality for data management without needing much setup (this will be covered in more detail below).
It can be linked in with the PostgreSQL database to allow for visualising existing tables and pgRouting results.
It gives access to pgRouting in plugin form, allowing routes to be calculated within QGIS using those database tables.

Introduction to graph data and routing

A graph data structure is made up of nodes and edges. With OS MRN, these are represented by the mrn_ntwk_transportnode and mrn_ntwk_transportlink layers.

Routing algorithms

Routing algorithms are a set of rules used to determine the best path between two or more points. Some of the common ones used are:

– The classic shortest path algorithm, from one node to another, using a directed or non-directed graph.
– Using Dijkstra, finds all nodes that are reachable within a set distance using a directed or non-directed graph. Produces results that can then be visualised as an isochrone polygon.
(turn restriction shortest path) – Runs similar to Dijkstra, with the addition of using restriction information. With OS MRN, this restriction data is available in the mrn_ntwk_turnrestriction layer. These turn restrictions reference the edges from the network layer and are used as a lookup as the algorithm works.

Checking that PostGIS and pgRouting are enabled

In more recent versions of PostgreSQL, both PostGIS and pgRouting are enabled as standard, ready to be used.

To check this:

Load pgAdmin4 (or your chosen database explorer).
Highlight your database.
Open a SQL window and run:

CREATE EXTENSION postgis;

ERROR: extension "postgis" already exists
SQL state: 42710

In the example above, PostGIS was already enabled. However, in the example below, pgRouting wasn't enabled, but is now ready to be used within the selected database:

CREATE EXTENSION pgrouting;

Query returned successfully in 151 msec.

Loading the GeoPackage

The easiest way to load the GeoPackage (GPKG) into PostgreSQL via is to use the OSGeo4W Shell that is provided with the QGIS install package:

Before loading the GPKG, check that environment variables have been set up so that PostgreSQL will be recognised by the command prompt. Admin permissions are required to edit these variables.
Add the folder location of your PostgreSQL install to the User->Path and System->Path variables.
Once you have done this, open the OSGeo4W Shell (as shown above), and type in ogr2ogr. If everything is setup correctly, you should see:
To then load the OS MRN GPKG into your PostgreSQL database, navigate to the location of the file, and type the following:

ogr2ogr -f PostgreSQL -progress -gt 65000 -a_srs EPSG:4326 -lco SCHEMA=<schema> -lco GEOMETRY_NAME=geometry PG:"dbname=<dbname> host=<host> port=<port> user=<user> password=<password>" OSMulti-modalRoutingNetwork.gpkg

You could alternatively use the following command (where /vsizip/ is a file handler that allows reading ZIP archives on-the-fly without decompressing them beforehand):

ogr2ogr -f PostgreSQL -progress -gt 65000 -a_srs EPSG:4326 -lco SCHEMA=<schema> -lco GEOMETRY_NAME=geometry PG:"dbname=<dbname> host=<host> port=<port> user=<user> password=<password>" /vsizip/OSMulti-modalRoutingNetwork.zip/OSMulti-modalRoutingNetwork.gpkg

This will load the three layers of the OS MRN GPKG into the defined database schema, and create the relevant spatial indexes.

You can now add some further attribute indexes for the unique identifiers:

CREATE INDEX mrn_ntwk_turnrestriction_wayid_idx ON <schema>.mrn_ntwk_transportlink USING btree (wayid);
CREATE INDEX mrn_ntwk_turnrestriction_nodeid_idx ON <schema>.mrn_ntwk_transportnode USING btree (nodeid);
CREATE INDEX mrn_ntwk_turnrestriction_relationid_idx ON <schema>.mrn_ntwk_turnrestriction USING btree (relationid);

With all the indexes added, you can create a basic edge table on which to start routing:

CREATE TABLE <schema>.edge_table AS
SELECT
  wayid AS id,
  name,
  foot,
  highway,
  railway,
  rail,
  ferry,
  toll,
  junction,
  route,
  ford,
  bridge,
  tunnel,
  service,
  oneway,
  ST_Length(geometry::geography) AS length,
  (STRING_TO_ARRAY(nodes, ',')::int[])[1] AS source, -- converts the nodes string to an array and extracts the first index item
  (STRING_TO_ARRAY(nodes, ',')::int[])[array_upper((STRING_TO_ARRAY(nodes, ',')::int[]), 1)] AS target, -- converts the nodes string to an array and extracts the last index item
  CASE
    WHEN oneway = '-1' THEN -1
    ELSE ST_Length(geometry::geography) -- returns the geometry length in metres
  END AS cost,
  CASE
    WHEN oneway = 'yes' THEN -1
    ELSE ST_Length(geometry::geography) -- returns the geometry length in metres
  END AS reverse_cost,
  geometry
FROM <schema>.mrn_ntwk_transportlink;

CREATE UNIQUE INDEX edge_table_id_idx ON <schema>.edge_table (id);
CREATE INDEX edge_table_source_idx ON <schema>.edge_table (source);
CREATE INDEX edge_table_target_idx ON <schema>.edge_table (target);

CREATE INDEX edge_table_geometry_idx
  ON <schema>.edge_table
  USING gist
  (geometry);

Loading the Protocolbuffer Binary Format

is a cross platform tool written in Java that can be used to parse OS MRN PBF data and make it routable in pgRouting.

To find out if you have Java installed, open PowerShell / Command Prompt (Windows) or Shell (Linux) and type:

java -version

Press Enter. If Java is installed, you should see a few lines of text detailing which version you have installed. If you get something along the lines of "java is not recognized ...", please download JVM [or OpenJDK] from .
Once osm2po is downloaded and extracted, open and edit the config file to satisfy your usage requirements (for example, change the wtr.finalMask = car line (use Ctrl+F to search the file) to car,foot,bike travel types).
Uncomment the following line (this helps with getting the topology into a format pgRouting likes):

postp.0.class = de.cm.osm2po.plugins.postp.PgRoutingWriter

When this is done, and assuming Java is installed and accessible, open a command prompt and navigate to the location of the .pbf file, and then run the following:

java -jar osm2po-core-5.5.11-signed.jar cmd=c prefix=osm2po OSMulti-modalRoutingNetwork.pbf

This will create the .sql file version of the .pbf file.

Import the .sql file version of the .pbf file to the PostgreSQL database using the following:

psql -h <host name> -U <username> -d <database name> -q -f <filename>.sql

Running a test route with pgRouting (Dijkstra)

The mandatory things pgRouting needs to be able to route with are a routing table, start node and end node. Once the routing table is created, pgRouting can be run straight away.

WITH start AS (
  SELECT source
    FROM <schema>.edge_table
    ORDER BY geometry <-> ST_SetSRID(
      ST_GeomFromText('POINT (-3.53532 50.72046)'), 4326)
    LIMIT 1
),
destination AS (
  SELECT source
    FROM <schema>.edge_table
    ORDER BY geometry <-> ST_SetSRID(
      ST_GeomFromText('POINT (-3.52133 50.72294)'), 4326)
    LIMIT 1
)
SELECT ST_Union(geometry) AS route
  FROM pgr_dijkstra(
    'SELECT id, source, target, cost, reverse_cost FROM <schema>.edge_table',
    ARRAY(SELECT source FROM start),
    ARRAY(SELECT source FROM destination)
  ) AS di
  JOIN <schema>.edge_table AS pt
  ON di.edge = pt.id;

This route query is made up of three parts:

First, the 'start' section finds the start node to use from the network that is closest to the point given. This could be fed in to the query in multiple ways, such as clicking on a web map, or using a plugin.
Second, the 'destination' section finds the start node closest to the destination point given.
The final part includes the pgr_dijkstra function, reading in the start and destination ids, and returns a merged geometry of links that form the route.

When visualised in QGIS, the result should look similar to this:

Vehicular routing – Determines the best vehicular route where the edges are deemed to be .

'SELECT id, source, target, cost, reverse_cost
  FROM <schema>.edge_table
  WHERE "rail" = ''no''
    AND "highway" IN (
      ''motorway'',
      ''motorway_link'',
      ''trunk'',
      ''trunk_link'',
      ''primary'',
      ''primary_link'',
      ''secondary'',
      ''secondary_link'',
      ''tertiary'',
      ''tertiary_link'',
      ''unclassified'',
      ''residential''
    )'

Pedestrian routing – Determines where the edges can be traversed by and whether there is designated infrastructure for walking.