1 of 63

Premium Products overview

What are OS Premium data products?

Ordnance Survey provide two types of data product: Premium products and OS OpenData products.

When we refer to Premium products, we mean paid-for datasets – whether they’re paid for by businesses, purchased through an OS Partner or accessed free at the point of use under the Public Sector Mapping Agreement (PSGA).

These premium data products are available as downloads in a range of formats, with a variety of ordering options and are available through the OS Data Hub on our Premium, Public Sector and Energy and Infrastructure plans.

Our Premium data download products work in a range of software, including ESRI ArcGIS, QGIS, Mapbox, Cadcorp SIS, MapInfo, Tableau, Kepler.gl and many more.

What's new?

Premium download products

Networks

Note:

All Networks Premium Download products will be in this section in the near future.

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. 

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

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

About the OS MRN

The pages in this section 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.

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

Note

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-2pm 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

Note

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

Note

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 : ways, nodes and relations. See for more information.

A way represents a linear feature on the ground. In OS MRN, these are called 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 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 and represent information about turn restrictions.

OSM uses a system of to apply information against different . 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 , 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 (5cm 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.

Technical specification

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.

Product Supply

OS MRN is available as a premium data download from the OS Data Hub. It is available as a Full Supply only, and customers can order full GB coverage or a customisable Area of Interest (AOI).

Formats

OS MRN is supplied in two formats:

Protocolbuffer Binary Format (PBF)
GeoPackage (GPKG)

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.

GPKG 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.

Update frequency

OS MRN is updated monthly in line with updates of the 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.

The sub-sections in this Technical Specification describe the:

Feature types available within the OS Multi-modal Routing Network premium product.
Code lists used by attributes available in those feature types.

Feature types

The OS Multi-modal Routing Network premium product contains three feature types: , , and .

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.

Note

For more information about the Transport Node feature type please read the Transport Node overview page in the About the OS MRN section.

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.

Note

For more information about the Turn Restriction feature type please read the Turn Restriction overview page in the About the OS MRN section.

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.

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.

FordValue

This code list is used in association with the Ford attribute which is present within the Transport Link Feature Type. The code list describes the nature of the ford present on the Transport Link.

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'.

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.

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.

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.

RailwayValue

This code list is used in association with the Railway attribute which is present within the Transport Link Feature Type. For Transport Links that represent railway features, the value indicates the type of railway infrastructure represented e.g 'rail', 'tram'.

RestrictionLabelValue

This code list is used in association with the Restriction attribute which is present within the Turn Restriction Feature Type. It describes the type of turn restriction. E.g. 'no_right_turn', 'only_straight_on'.

RouteValue

This code list is used in association with the Route attribute which is present within the Transport Link Feature Type. It indicates the type of transport route that a Transport Link forms a part of in the real world, e.g 'Railway', 'Ferry'.

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.

Getting started

This getting started guide provides instructions for using OS MRN in different routing software applications. Users with limited technical knowledge will be able to follow this guide.

OS Multi-modal Routing Network (OS MRN) is designed for use in routing applications. Numerous different routing software applications are available.

This guide includes instructions to get you started with using OS MRN in three open-source routing applications:

– for GeoPackage (GPKG) and Protocolbuffer Binary Format (PBF)
– for PBF
– for PBF

The guide also has a page on , where you will find guidance on:

The ability to carry out multi-modal routing is dependent on the software you use. To make full use of the functionality of OS MRN, you may need to make configuration changes to your software, for example, configuring it to use the speed data or time conditional attributes. It is also possible to use third party datasets, such as bus and train timetables, with OS MRN to enhance multi-modal routing.

How to get this product

OS MRN data can be downloaded from the (for further guidance, please see ).

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:

Notes:

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

OpenTripPlanner

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

is an open source multi-modal trip planner, focussing on travel by scheduled public transportation in combination with bicycling, walking, and mobility services, including bike share and ride hailing.

What you need

(Java 17+)

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'.

Basic usage

In terms of creating a transit network using OS MRN, you'll require the following files (ensure that they are stored in the same directory):

The "shaded" JAR (Java ARchive) containing OTP and all other libraries needed for it to work.
Some General Transit Feed Specification (GTFS) data for Transit Schedules and Stops, for example, Bus Open Data Service (BODS).
OS MRN Protocolbuffer Binary Format (PBF) data downloaded from the (OSMulti-modalRoutingNetwork.pbf).

The is an Open Standard used to distribute relevant information about transit systems to riders. It allows public transit agencies to publish their transit data in a format that can be consumed by a wide variety of software applications.

The provides bus timetable, vehicle location and fares data for every local bus service in England.

The provides a detailed set on instructions of how to get the interactive OTP instance up-and-running, but fundamentally the steps are as follows:

Open PowerShell / Command Prompt (Windows) or Shell (Linux) and navigate to the folder where the OTP JAR, BODS GTFS, and OS MRN PBF files have been stored.
Run the following command to start the service: java -Xmx8G -jar otp-2.5.0-shaded.jar --build --serve . --port 8801.

Working with OpenStreetMap files

Converting PBF to OSM XML

A lot of routing software used in the OpenStreetMap (OSM) project supports Protocolbuffer Binary Format (PBF). There are several tools to convert from PBF to OSM XML and vice versa, if required, including Osmconvert, Osmosis and Osmium:

Sorting OSM files

OSM files are usually sorted in a specific way: first the nodes ordered by ID, then ways ordered by ID, then relations ordered by ID. But this is not necessarily always the case.

It is important to check if a file is sorted correctly as many commands only work properly if a file is sorted.

To check if a file is sorted, in use fileinfo :

To sort a file using :

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 Transport Nodes 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

Note

For more information about the Transport Link Feature Type, please read the Transport Link overview page in the About the OS MRN section.

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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: highwayvalue
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: railwayvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: junctionvalue
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: routevalue
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: fordvalue
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: bridgevalue
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: tunnelvalue
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: railservicevalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: accessvalue
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: onewayvalue
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: onewayvalue
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: onewayvalue
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: onewayvalue
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: onewayvalue
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: onewayvalue
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: onewayvalue
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: onewayvalue
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: onewayvalue
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: onewayvalue
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: onewayvalue
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

BLPU (Type 21 Record)

The Basic Land and Property Unit (BLPU) Feature Type is a real-world object that is an area of land, property or structure of fixed location, having uniform occupation, ownership or function.

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.

Please note, the following attributes will not be populated within the OS ESG: Parent_UPRN and Multi_Occ_Count.

fid 

A non-persistent integer which is autogenerated and is required within the OGC GeoPackage format.

Attribute Name: fid (GKPG), Not provided (CSV)
Data Types: Integer  (GKPG), Integer (CSV)
Nullable:  false 
Data Schema Version: 1.0

Record ID

Identifies this record as a BLPU Record (type 21). 

Attribute Name: Not provided (GKPG), RECORD_IDENTIFIER (CSV)
Data Types: Integer  (GKPG), Integer (CSV)
Max Length: 2
Nullable:  false
Data Schema Version: 1.0

Change type

The type of record change.

Attribute Name: change_type (GKPG), CHANGE_TYPE (CSV)
Max Length: 1
Nullable:  false
Data Schema Version: 1.0

Processing order

The order in which the records were processed in to create the data supply. 

Attribute Name: Not provided (GKPG), PRO_ORDER (CSV)
Data Types: Integer  (GKPG), Integer (CSV)
Max Length: 16
Nullable:  false
Data Schema Version: 1.0

UPRN

Unique Property Reference Number (UPRN) assigned by Ordnance Survey. 

Attribute Name: uprn (GKPG), UPRN (CSV)
Data Types: Integer  (GKPG), Integer (CSV)
Max Length: 12
Nullable:  false
Data Schema Version: 1.0

Logical status

Logical status of this record as given by Ordnance Survey. This attribute shows whether the record is currently live or historic. 

Attribute Name: logical_status (GKPG), LOGICAL_STATUS (CSV)
Max Length: 1
Nullable:  false
Data Schema Version: 1.0

BLPU state

A code identifying the current state of the BLPU. 

Attribute Name: blpu_state_date (GPKG), BLPU_STATE_DATE (CSV)
Max Length: 1
Nullable:  true
Data Schema Version: 1.0

BLPU state date

Date at which the BLPU achieved its current state as defined in the BLPU State field. 

Attribute Name: blpu_state_date (GKPG), BLPU_STATE_DATE (CSV)
Condition: BLPU State Date must be present if BLPU State is present. 
Data Types: Date (GKPG), Date (CSV)
Nullable:  true
Data Schema Version: 1.0

Parent UPRN

UPRN of the parent Record if a parent-child relationship exists. 

Attribute Name: parent_uprn (GKPG), PARENT_UPRN (CSV)
Data Types: Integer (GKPG), Integer (CSV)
Max Length: 12
Nullable:  true
Data Schema Version: 1.0

X coordinates

A value in metres defining the x location in accordance with the British National Grid.  

Attribute Name: x_coordinate (GKPG) , X_COORDINATE (CSV)
Data Types: Double (GKPG), Real (CSV)
Precision: X_COORDINATE 8
Scale: 2
Nullable:  false
Data Schema Version: 1.0

Y coordinates

A value in metres defining the y location in accordance with the British National Grid.  

Attribute Name: y_coordinate (GKPG) , Y_COORDINATE (CSV)
Data Types: Double (GKPG), Real (CSV)
Precision: Y_COORDINATE 9
Scale: 2
Nullable:  false
Data Schema Version: 1.0

Latitude location

A value defining the Latitude location in accordance with the ETRS89 coordinate reference system.

Attribute Name: latitude (GKPG), LATITUDE (CSV)
Data Types: Double  (GKPG), Real  (CSV)
Precision: LATITUDE 9
Scale: 7
Nullable:  false
Data Schema Version: 1.0

Longitude location

A value defining the Longitude location in accordance with the ETRS89 coordinate reference system.

Attribute Name: longitude (GKPG), LONGITUDE (CSV)
Data Types: Double  (GKPG), Real  (CSV)
Precision: LONGITUDE 8
Scale: 7
Nullable:  false
Data Schema Version: 1.0

RPC

Representative Point Code. This describes the accuracy of the coordinate that has been allocated to the BLPU as indicated by Ordnance Survey. 

Attribute Name: rpc (GKPG), RPC (CSV)
Max Length: 1
Nullable:  false
Data Schema Version: 1.0

Local custodian ID

Unique identifier of the authority responsible for the maintenance of this record. 

Attribute Name: local_custodian_code (GKPG), LOCAL_CUSTODIAN_CODE (CSV)
Data Types: Integer  (GKPG), Integer (CSV)
Max Length: 4
Nullable:  false
Data Schema Version: 1.0

Start date

The date on which the record was inserted into the database. 

Attribute Name: start_date (GKPG), START_DATE  (CSV)
Data Types: Date  (GKPG), Date (CSV)
Nullable:  false
Data Schema Version: 1.0

End date

The date on which the record was closed in the database. 

Attribute Name: end_date (GKPG), END_Date (CSV)
Data Types: Date (GKPG), Date (CSV)
Nullable:  true
Data Schema Version: 1.0

Last update date

The date on which any of the attributes on this record were last changed. 

Attribute Name: last_update_date (GKPG), LAST_UPDATE_DATE (CSV)
Data Types: Date (GKPG), Date (CSV)
Nullable:  false
Data Schema Version: 1.0

Entry date

The date on which this record was inserted into the database. 

Attribute Name: entry_date (GKPG), ENTRY_DATE (CSV)
Data Types: Date (GKPG), Date (CSV)
Nullable:  false
Data Schema Version: 1.0

Multi-Occupation count

 A count of all of the child UPRNs for this record where a parent-child relationship exists. 

Attribute Name: multi_occ_count (GKPG), MULTI_OCC_COUNT (CSV)
Data Types:  Integer (GKPG), Integer (CSV)
Max Length: 4
Nullable:  false
Data Schema Version: 1.0

Addressbase postal

This field will be populated with ‘N’ within the OS ESG; all the BasicLandPropertyUnit features are considered as 'Not a postal address'.

Attribute Name: addressbase_postal (GKPG), ADDRESSBASE_POSTAL (CSV)
Max Length: 1
Nullable:  false
Data Schema Version: 1.0

LPI (Type 24 Record)

The Land Property Identifier (LPI) Data Type defines a structured entry that identifies a BLPU. The AddressBase Premium data structure provides the facility to describe a BLPU by more than one LPI. In England and Scotland there is one Approved LPI (English), whereas in Wales there are two Approved LPIs (English and Welsh).

Temporal filtering

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

Data type attributes

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

Please note, the following attributes will not be populated within the OS ESG: SAO Start Number, SAO Start Suffix, SAO End Number, SAO End Suffix, SAO Text, PAO Start Number, PAO Start Suffix, PAO End Number, and PAO End Suffix.

fid

 A non-persistent integer which is autogenerated and is required within the OGC GeoPackage format.

Attribute Name: fid (GKPG), Not provided (CSV)
Data Types:  Integer (GKPG), Integer (CSV)
Nullable:  false
Data Schema Version: 1.0

Record ID

Identifies this Record as an LPI Record (type 24). 

Attribute Name: Not provided (GKPG), RECORD_IDENTIFIER (CSV)
Data Types: Integer (GKPG), Integer (CSV)
Size: 2
Nullable:  false
Data Schema Version: 1.0

Change type

The type of record change.

Please see the 'Available formats' section in the OS ESG Overview for more information

Attribute Name: change_type (GKPG), CHANGE_TYPE (CSV)
Code List Name: ChangeTypeCode 
Size: 1
Nullable:  false
Data Schema Version: 1.0

Processing order

The order in which the records were processed to create the data supply. 

Attribute Name: Not provided (GKPG), PRO_ORDER (CSV)
Data Types:  Integer (GKPG), Integer (CSV)
Size: 16
Nullable:  false
Data Schema Version: 1.0

UPRN

The Unique Property Reference Number (UPRN). This is a foreign key used to reference the LPI to the corresponding BLPU. 

Attribute Name: uprn (GKPG), UPRN (CSV)
Data Types:  Integer (GKPG), Integer (CSV)
Size: 12
Nullable:  false
Data Schema Version: 1.0

LPI key

The unique key for the LPI and primary key for this table. A 14-character string, prefixed with '7655L' then a nine-digit sequential number.

Attribute Name: lpi_key (GKPG), LPI_KEY (CSV)
Data Types: String (CSV), String  (GKPG) 
Max Length: 14
Nullable:  false
Data Schema Version: 1.0

Language

A code that identifies the language used for the LPI record (the names and / or descriptions in PAO_text and SAO_text).

Attribute Name: language (GKPG), LANGUAGE (CSV)
Code List Name:  LanguageCode
Size: 3
Nullable:  false
Data Schema Version: 1.0

Logical status

The logical status of this record. 

Attribute Name: logical_status (GKPG), LOGICAL_STATUS (CSV)
Code List Name:  LogicalStatusCode
Size: 1
Nullable:  false
Data Schema Version: 1.0

Start date

The date on which this LPI record was inserted into the database. 

Attribute Name: start_date (GKPG), START_DATE (CSV)
Data Types:  Date (GKPG), Date (CSV)
Nullable:  false
Data Schema Version: 1.0

End date

The date on which this record ceased to exist in the database.   

Attribute Name: end_date (GKPG), END_DATE  (CSV)
Data Types:  Date (GKPG), Date (CSV)
Nullable:  true
Data Schema Version: 1.0

Last update date

The date on which any of the attributes on this record were last changed. 

Attribute Name: last_update_date (GKPG), LAST_UPDATE_DATE (CSV)
Data Types:  Date (GKPG), Date (CSV)
Nullable:  false
Data Schema Version: 1.0

Entry date

The date on which the record was inserted into the database. 

Attribute Name: entry_date (GKPG), ENTRY_DATE (CSV)
Data Types:  Date (GKPG), Date (CSV)
Nullable:  false
Data Schema Version: 1.0

SAO start number

The number of the secondary addressable object (SAO) or the start of the number range. 

Attribute Name: sao_start_number (GKPG), SAO_START_NUMBER (CSV),
Data Types:  Integer (GKPG), Integer (CSV)
Size: 4
Nullable:  true
Data Schema Version: 1.0

SAO start number suffix

The suffix to the SAO_START_NUMBER.

Attribute Name: sao_start_suffix (GKPG), SAO_START_SUFFIX  (CSV)
Data Types: String (GKPG) , String (CSV)
Max Length: 2
Nullable:  true
Data Schema Version: 1.0

SAO end number

The end of the number range for the SAO, where the SAO_START_NUMBER contains the first number in the range. 

Attribute Name: sao_end_number (GKPG), SAO_END_NUMBER (CSV)
Data Types:  Integer (GKPG), Integer (CSV)
Size: 4
Nullable:  true
Data Schema Version: 1.0

SAO end suffix

The suffix to the SAO_END_NUMBER. 

Attribute Name: sao_end_suffix  (GKPG), SAO_END_SUFFIX (CSV)
Data Types: String (GKPG) , String (CSV)
Max Length: 2
Nullable:  true
Data Schema Version: 1.0

SAO text

Additional location information where transport or water networks interact with the feature to provide the names and / or numbers of those networks. The pipe symbol (|) is used to separate multiple names.

Please note, SAO Text will be in alphanumeric order. Where names are known to be Gaelic in origin, these will appear first in records in Scotland. In Wales, the known Welsh names will be on the Welsh LPI (CYM), and the known English names will be on the English LPI (ENG). Where it is not known, or the name in use is in both languages, the same name may appear on both the English and Welsh LPI.

Attribute Name: sao_text  (GKPG), SAO_TEXT (CSV)
Data Types: String (GKPG) , String (CSV)
Max Length: 400
Nullable:  true
Data Schema Version: 1.0

PAO start number

The number of the primary addressable object (PAO) or the start of the number range.

Attribute Name: pao_start_number (GKPG), PAO_START_NUMBER (CSV)
Data Types:  Integer (GKPG), Integer (CSV)
Size: 4
Nullable:  true
Data Schema Version: 1.0

PAO start number suffix

The suffix to the PAO_START_NUMBER. 

Attribute Name: pao_start_suffix (GKPG), PAO_START_SUFFIX  (CSV)
Data Types: String (GKPG), String (CSV)
Max Length: 2
Nullable:  true
Data Schema Version: 1.0

PAO end number

The end of the number range for the PAO where the PAO_START_NUMBER contains the first number in the range. 

Attribute Name: pao_end_number (GKPG), PAO_END_NUMBER (CSV)
Data Types:  Integer (GKPG), Integer (CSV)
Size: 4
Nullable:  true
Data Schema Version: 1.0

PAO end suffix

The suffix to the PAO_END_NUMBER. 

Attribute Name: pao_end_suffix  (GKPG), PAO_END_SUFFIX (CSV)
Data Types: String (GKPG), String (CSV)
Max Length: 2
Nullable:  true
Data Schema Version: 1.0

PAO text

The proper name(s) used to identify the feature. Where the official name is not known, a default value is given based on the classification. The pipe symbol (|) is used to separate multiple names.

Please note, PAO text will be in alphanumeric order. Where names are known to be Gaelic in origin, these will appear first in records in Scotland. In Wales, the known Welsh names will be on the Welsh LPI (CYM), and the known English names will be on the English LPI (ENG). Where it is not known, or the name in use is in both languages, the same name may appear on both the English and Welsh LPI.

Attribute Name: pao_text (GKPG), PAO_TEXT (CSV)
Data Types: String (GKPG), String (CSV)
Max Length: 90
Nullable:  true
Data Schema Version: 1.0

USRN

The Unique Street Reference Number (USRN). This is a foreign key linking the Street record to the LPI record. 

Attribute Name: usrn (GKPG), USRN (CSV)
Data Types:  Integer (GKPG), Integer (CSV)
Size: 8
Nullable:  false
Data Schema Version: 1.0

Unique Street Reference Number (USRN) for a Street intersecting or near a junction. BLPUs will be assigned a USRN; these only refer to the USRNs published in AddressBase Premium.

USRN match indicator

This field indicates how the feature was matched to a Street. 1 is matched manually to the most accessible USRN, and 2 is matched spatially to the nearest USRN, which may not be the nearest accessible street.    

Attribute Name: usrn_match_indicator (GKPG), USRN_MATCH_INDICATOR (CSV)
Code List Name: USRNMatchIndicatorCode
Size: 1
Nullable:  false
Data Schema Version: 1.0

Area name

Additional location information indicating, for example, a city or town and any relevant other named urban areas. Where relevant, island names are included. In non-urban areas, the Lower Tier Local Authority is provided. (NEAR) indicates either within 1km of a settlement onshore, or within 500m of a named island or 1km from a Lower Tier Local Authority offshore.

Attribute Name: area_name (GKPG), AREA_NAME (CSV)
Data Types:  String (GKPG), String (CSV)
Max Length: 100
Nullable:  true
Data Schema Version: 1.0

Please note, settlement boundaries and islands used are an OS geographic depiction of the extent of settlements and should not be mistaken for official administrative or electoral boundaries. Please see Named Features - OS National Geographic Database for further information. Lower Tier Local Authority Areas used are from Boundaries - OS National Geographic Database.

Level

Detail on the vertical position of the property, if known and provided by the authority.

Attribute Name: level (GKPG), LEVEL (CSV)
Data Types: String (GKPG),  String (CSV)
Max Length: 30
Nullable:  true
Data Schema Version: 1.0

Official flag

The status of the feature. 

Attribute Name: official_flag (GKPG), OFFICIAL_FLAG (CSV)
Code List Name: OfficialFlagCode
Size: 1
Nullable:  true
Data Schema Version: 1.0

OS ESG Getting Started Guide

This getting started guide provides instructions for using the OS ESG in different software applications. Users with limited technical knowledge will be able to follow this guide.

Data supply

The OS ESG can be downloaded from the Premium Downloads section of the OS Data Hub.

It comes in two geospatial data formats:

GeoPackage
Comma-separated values (CSV)

The GeoPackage is formed of three tables: LPI, BLPU and Classification. This data does not need pre-processing before it can be used.

The CSV follows the AddressBase Premium data schema and contains rows of data with the following record identifiers: type 21, type 24 and type 32. This schema often requires pre-processing before it can be used. See 'Using the CSV data' on this page for guidance on how to do this.

Using the GeoPackage data

The GeoPackage format of the OS ESG does not require splitting as a GeoPackage can contain multiple tables.

The GeoPackage data supply contains three tables:

BLPU
LPI
Classification

It’s important to understand that only the BLPU table has a geometry field and this may dictate how you use it in your GIS software.

For general guidance on how to work with GeoPackage, please read our Getting Started with GeoPackage guide.

Accessing GeoPackage data via GIS software

The following sub-sections provide step-by-step instructions on how to access GeoPackage data via various GIS software packages; all current versions of these applications support GeoPackage natively.

ArcGIS Pro

Requirements:

ArcGIS Pro (version 1.1 or later)
OS ESG GeoPackage dataset, for example, OSEmergencyServicesGazetteer_FULL_2024-04-03_001.gpkg

Note: Certain versions of ArcGIS Pro (for example, version 2.5) require a GeoPackage to have a spatial index added before the data can be viewed on the map. This can be done in the Catalog by opening the Feature Class Properties window within the Indexes page.

Instructions:

These instructions were created using ArcGIS Pro version 3.2.0. Versions from 1.1 onwards also support GeoPackage features.

In ArcGIS Pro, open an existing project or create a new project:
- To create a new project, select Map in the New Project section, enter a name, select a location for the project, and then click OK.
In the Add Data dialog, select the GeoPackage to be added into ArcGIS Pro and click Open. This opens the GeoPackage to reveal the individual layers.
Select the layers you want to add and click OK. You can select more than one layer by holding down the Ctrl (control) key and clicking on multiple layers.
The layers added into ArcGIS Pro will appear in the contents pane on the left-hand side of the project.

ArcMap

Requirements:

ArcMap (version 10.2.2 or later)
OS ESG GeoPackage dataset, for example, OSEmergencyServicesGazetteer_FULL_2024-04-03_001.gpkg

Note: Certain versions of ArcMap (for example, version 10.8.1) require a GeoPackage to have a spatial index added before the data can be viewed on the map. This can be done in the Catalog by opening the Feature Class Properties window within the Indexes page.

Instructions:

These instructions were created using ArcMap version 10.5, but versions from 10.2.2 onwards also support GeoPackage features.

In ArcMap, open an existing map or create a new one.
In the Add Data dialog:
- Select the GeoPackage file you want to add into ArcMap and then click Open. This opens the GeoPackage to reveal the individual layers.
- Select the layers you want to upload into ArcMap. You can select more than one layer by holding down the Ctrl (control) key and clicking on multiple layers.
- Click Add to add the layers into the map.
The GeoPackage layers should now be viewable in the layers list in the Table Of Contents on the left-hand side of the workspace.

Cadcorp SIS

Requirements:

Cadcorp SIS (version SIS 9 or later)
OS ESG GeoPackage dataset, for example, OSEmergencyServicesGazetteer_FULL_2024-04-03_001.gpkg

Instructions:

These instructions were created using Cadcorp SIS 9.1 Desktop Express; however, all versions of Cadcorp SIS 9 or later support GeoPackage.

In Cadcorp SIS, open an existing map or create a new one.
Click Add Overlay in the top ribbon.
In the Overlay Types dialog, select Files > File and then click Next.
In the File Browser dialog, select the GeoPackage file and then click Finish.
The data should now appear on the map.

QGIS

Requirements:

QGIS (version 2.10.1 or later)
OS ESG GeoPackage dataset, for example, OSEmergencyServicesGazetteer_FULL_2024-04-03_001.gpkg

Instructions:

These instructions were created using QGIS version 3.28. You can use any version of QGIS from version 2.10.1 onwards.

In QGIS, open an existing project or create a new one.
In the top navigation, select Layer > Add Layer > Add Vector Layer...
In the Data Source Manager | Vector dialog:
- Source: Click ... (three dots) on the right of the Source field, select the GeoPackage file and click Open.
- Click Add. This opens the Select Items to Add dialog.
In the Select Items to Add dialog:
- Select the the layers of the GeoPackage to be added to the map. You can select more than one layer by holding down the Ctrl (control) key and clicking on multiple layers.
- Click Add Layers.
The GeoPackage layers should now be viewable in the layers list on the left-hand side of the workspace.

Converting / Loading a GeoPackage to other data formats

It is possible to use Extract, Transform, Load (ETL) tools to convert the data into different formats and to load into databases.

The following sub-section provides step-by-step instructions for FME:

FME

FME is a data integration platform which can read the GeoPackage format and be used to convert and transform the data into other formats or databases. The following instructions show you how to read a GeoPackage into an FME workbench.

Requirements:

FME Desktop
OS ESG GeoPackage dataset, for example, OSEmergencyServicesGazetteer_FULL_2024-04-03_001.gpkg

Instructions:

These instructions were created using FME Workbench 2023.2.2.0.

In FME, click Reader in the top ribbon.
In the Add Reader dialog:
- Format: Select OGC GeoPackage from the dropdown.
- Dataset: Click ... (three dots) to the right of the field, select the GeoPackage you want to read, and then click Open.
- Coord. System: Select an appropriate coordinate system.
- Parameters: Click this button to open the OGC GeoPackage Parameters dialog:
  - Tables: Click ... (three dots) to the right of the field to open the Select Tables dialog. You can also use the Use Search Envelope option in this dialog to clip the GeoPackage to an extent.
    In the Select Tables dialog, select the layers you want to add into the workbench and click OK.
- Click OK to close the OGC GeoPackage Parameters dialog.
- Click OK to close the Add Reader dialog.
An orange reader will display the name of the GeoPackage table that has been read in.

To use GDAL to load the GeoPackage datasets into a PostgreSQL database using the ETL tool, please read and adapt the instructions in the generic Getting Started with GeoPackage guide > GDAL guide.

Using the CSV data

Pre-processing CSV data

This section guides you through the process of pre-processing the OS ESG CSV data as a stand-alone dataset; this means splitting the data by record identifiers and appending the header files.

The OS ESG header files are available to download from the OS ESG Downloads page.

We have included instructions for two pre-processing options – gawk and Python:

gawk

You can use gawk to split the OS ESG CSV files by their record identifier and append the Header files.

Note: Running the .bat file creates temporary files and requires extra space in the location in which you are creating your files. These files can be much larger than the original CSV files. They are deleted once the process has finished, but the extra space is still required initially.

Instructions:

Add the OS ESG CSV files to an empty folder. It is very important to ensure that the folder does not contain any other CSV files. In addition, the folder name and the file directory path name must not contain any spaces, for example, C:\os_esg\.
Download the OSEmergencyServiceGazetteer-header-files.zip from the OS ESG Download page and extract the ZIP. You should have the following CSV files:
Place the extracted OS ESG header files into the folder containing the OS ESG CSV files (created in step 1).
Go to the OS ESG/gawk GitHub repository.
Open the esg-gawk-split-script.bat file and copy the contents into a text editor, such as TextPad or Notepad++. Save this text file as a .bat file in the same folder as your OS ESG CSV data and header files.
In the OS ESG/gawk GitHub repository (location in Step 4), download and extract the ZIP file named gawk-4.0.2-bin.zip. This will extract a file called Gawk.exe. Place this file in the same folder as your OS ESG data and header files.
Double-click on esg-gawk-split-script.bat file and an MS-DOS window will open. Once the process is complete, the screen will either close automatically or you will have to press any key to continue.
Running the batch file should create additional files with a similar naming convention to that of the header files. The new files should have been generated in the same location as the original data and header files. For example, there should now be an ID24_LPI_RECORDS as well as a Record_24_LPI_Header.csv in the folder.

Python

You can use Python (instead of gawk) to split the OS ESG CSV files by their record identifier and append the header files.

Note:

These instructions are based on Python 3.7.
You do not need to download the header files if you are using Python to split the OS ESG.

Instructions:

Add the OS ESG CSV files to an empty folder. It is very important to ensure that the folder does not contain any other CSV files. In addition, the folder name and the file directory path name must not contain any spaces, for example, C:\EmergencyServicesGazetteer\OS_ESG.
Go to the OS ESG/Python GitHub repository and download the esg-record-splitter-v3_7.py file.
Copy the file into the folder containing the CSV files (created in step 1).
Double click the Python script and it will automatically find the CSVs and split them into the relevant files.
When the file splitting process is complete, the following message will be displayed: 'The program will close in 10 seconds'.
Once the CSVs have been split out, they can be loaded into a GIS using a CSV import tool. There will be three main CSVs: BLPU, LPI and Classification.

Database loading

To load the data into a database, you need to first create the tables and columns required for the data; these can be found in the OS ESG GitHub repository and depend on the type of database you have.

Once you have created the tables, follow the guidance in Loading CSV files to load the data into your database.

Connecting data

Each table in the OS ESG has a UPRN (Unique Property Reference Number). This identifier is what links the rows of data together between tables.

Please follow guidance from your software provider on how to join datasets if using the CSV or GeoPackage directly (without a database load)

If you have the data in a database you can link it in the following way:

Select * from os_esg.blpu 
inner join os_esg.lpi on blpu.uprn = lpi.uprn 
inner join os_esg.classification on blpu.uprn = classification.uprn

OS ESG Classification Scheme

The OS ESG classification scheme is available to download from the OS ESG Downloads page.

Useful resources

A helpful introductory Lightning Talk on the OS ESG is available on our 'More than Maps' site (a self-serve platform that provides a one-stop shop for all your OS technical geospatial support, including tutorials, demonstrators and case studies).
OS Emergency Services Gazetteer (OS ESG) Overview
OS Emergency Services Gazetteer (OS ESG) Technical Specification