On this page
Introduction
The OS Transport Layer is the definitive Network data supplied by the Ordnance Survey through the National Geographic Database (NGD).
Whilst it contains all of the data from the OS Highways product, it has been extended to contain much more information about the road and path network in the UK and includes speed limit data and average speed data.
The tool included with the UK Data Loader will load the data from the source files, in geopackage format, into a geodatabase and create a routable network dataset.
Which datasets to use
The tools we have written will work with all three collections provided by the Ordnance Survey within the OS Transport Layer: Transport Features, Transport Network, and Routing and Asset Management.
If you wish to create a network from the data you should ensure you include the Routing and Asset Management data.
Using the tool
Locate the OS Transport Layer Toolset and run the tool called “Process OS Transport Layer Data”.
The first parameter you need to enter is the location of your source data. You will need to select the folder which contains the geopackage files from the Ordnance Survey. The tool will only process files directly inside of that folder, it will not search sub-folders for files to process. This file should contain all the data you wish to load and use in your network, it is not currently possible to combine datasets after they are loaded.
Select the Destination Workspace where the data is to be loaded. You can select either a folder or a database connection
- Where you have selected a folder, you will then be asked to give names to the two file geodatabases that the tool will create.
- Where you have selected an enterprise geodatabase, the feature classes will be created directly under that connection.
You can decide what to do if there are existing datasets with the same name, you can choose to delete all existing data or to append to those datasets.
If you choose to delete the existing data, once the new data is loaded into a featureclass or table any previously existing feature or rows will be removed. If you choose to append the data both existing and new data will remain.
You can also select where to store the log file that will be created.
If you do not wish to create a network dataset and only wish to load the raw data into feature classes and tables then there is the option to select “Data Load Only: Do Not Build A Network”.
Optional Parameters
Name Prefix
There is the option to designate a prefix for the feature class names. This will prefix all of the featureclasses, tables and network datasets created.
Urban Area
The default speeds applied to a network are based on the road types and classification. This means that an A road will be assigned the same speed whether it is in a rural area or running through a town.
This option can be used to provide an urban area polygon so that different speeds can be applied to roads in urban or rural areas. The OS Zoomstack dataset provide a polygon featureclass which can be used in this tool for free.
Network schema file
If you have previously loaded data and subsequently modified the network dataset with ,for example, alternative speed calculations, you are able to export that configuration to an xml file using a geoprocessing tool.
If you have previously adjusted the network dataset with your own parameters, such as custom speed calculations, you can export that schema as an xml using the Geoprocessing tool in ArcGIS Pro. You can then use this to apply these changes to the network created in this load.
The xml you provide will reference specific dataset names and so you will need to ensure that any dataset prefix you use is consistent between your data loads.
Use Average Speed Data To Build A Network
This option will use the average speed data (if present) to build additional travel modes that will allow you to specific the time at which you wish to calculate a travel cost. This will then use the average speed recorded for that time period as the travel speed on that roadlink.
Details of the Travel modes are detailed below.
What does the tool do?
How it loads the data
The tool gathers a list of the files to process from the folder and then passes them in batches to the relevant translation tool.
These tools extract the data from the geopackage files copies them into the relevant feature classes or tables. The data schema it follows can be found on the OS website.
Spatial Indexes are built on the feature classes after the data has finished loading to aid performance.
How it creates the Network
Links and Nodes
The tool extracts the link information from the relevant featureclass and creates a feature classes inside the Network Dataset adding additional information derived from related tables such as whether the link is one way or the grade separation at either end of the link.
Turn Restrictions
In an ArcGIS Network Dataset turn restrictions are set up as geometries that cannot be traversed.
The OS Transport Layer supplies the Turn Restriction information as a set of tables defining the types of restrictions and the RoadLinks involved in those restrictions.
For a simple restriction the tool takes the RoadLinks involved and creates a turn restriction geometry from those and inserts the restriction feature into the NoTurns featureclass in the Network Dataset.
Mandatory turns
Some turn restrictions in the OS Transport Layer dataset define a turn that must be taken. For example, at a cross roads you may be required to pass straight over and not take any other exit.
There is no option within an ArcGIS Network to define a turn that must be taken, we can only specify turns that cannot be taken. Therefore, the tool calculates all the possible turns involved at that intersection, creates turn restriction features for all the manoeuvres that cannot be performed and adds these to the InferredTurns featureclass in the Network Dataset.
The default network configuration
ArcGIS Pro supplies a tool that allows creation of Network Dataset from an XML template. Default network configurations which cover the various combinations of road, ferry and paths data have been supplied in the Resources folder.
Travel modes for driving, cycling and for walking have been included in the templates, and which one is used will depend upon the data present in the data load.
Speeds
If you have included the average speed and speed limit data geopackage in your list of files to load (This is called trn_rami_averageandindicativespeed in the OS data) then the tools will extract the relevant speed limit information for each road link and use that within the network calculation.
If no speed data is provided then the default Network dataset has speeds defined for the all the links based on whether you are walking, cycling or driving.
The driving speeds are set based on the type and designation of the road as defined in the table below.
Driving
| Form of way | RouteHierarchy | Speed (mph) | Urban Speed (mph) |
| All | Motorway | 67 | 67 |
| All | A Road/ A Road Primary | 57 | 25 |
| All | B Road/ B Road Primary | 45 | 25 |
| All | Minor Road | 45 | 24 |
| All | Local Road | 20 | 20 |
| All | other | 10 | 10 |
| Track | All | 5 | 5 |
| Layby | All | 5 | 5 |
Walking speeds have been set to 3mph, cycling has been set to 10mph and the speed on a ferry has been set to 5mph.
Urban/Rural split
Where an urban area featureclass has been specified the tool will calculate how much of each road link is within those urban areas. When calculating the speed along that link it will be proportioned appropriately with the urban or rural speeds quoted above.
Using the Average speed data
If you chose to use the average speed data then the tool will create a set of travel modes which will allow you to specify the time of day during you wish to calculate the travel costs.
The travel modes created and the average speed data used is listed below.
| Travel mode name | Corresponding Time period |
| Drive_Time_AMPeak | 7am to 9am |
| Drive_Time_OffPeak | 9am to 4pm |
| Drive_Time_PMPeak | 4pm to 7pm |
| Drive_Time_Evening | 7pm to 10pm |
| Drive_Time_Night | 10pm to 7am |
| Drive_Time_Weekend | Saturday and Sunday |
Changing speeds
If you wish to modify the calculations used for speeds after the network is created you can do so. This can be done by modifying the scripts used within the “Costs” section of the network setup.
The modified network will then need to be rebuilt.
Full details of the options available in the Network dataset properties dialog can be found in the ArcGIS pro help.
The modified network dataset can then be exported as a template for use in future data loads.
How long will it take to process the data
The table below gives indicative times for how long it will take to process data and how long it may take to rebuild the network if it is modified after loading.
The examples below are for loading the full Transport Layer data including Roads, Routing and Asset Management, Paths and speed data into a file geodatabase.
| Area | Hardware | Data Load | Network Creation and build | Total | Rebuild network |
| GB | Virtual Machine
8 Cores 16GB RAM
|
20 hours | 16 hours | 36 hours | 30 minutes |
The output
Once the tool has processed the data you will have a set of feature classes and tables containing the raw data. These can be used for visualisation and spatial analysis using the tools available in the ArcGIS Platform.
See the online help for information how to add this data into maps and utilise it in analysis.
The tool will also produce a Network Dataset which can be used in Network analysis in ArcGIS Desktop. It is also suitable for publishing as a Network Analysis service if you have the appropriate installation and licensing of ArcGIS Enterprise.
There is a utility available in ArcGIS Enterprise that will aid you in publishing the Routing services for use in your own portal.
Note: When publishing the Network Dataset created by UK Data Loader to ArcGIS Enterprise 12.0 using the Routing services utility above, some service types require the dataset to include a Time Zone attribute. If this attribute is missing, Enterprise may return error 030353: Network has no time zone attribute. To resolve this, configure a single time zone for the Network Dataset in ArcGIS Pro using the guidance here.