Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
OS MasterMap Highways Network – Roads and OS MasterMap Highways Network – Paths are supplied in three formats: Geography Markup Language (GML 3.2.1), GeoPackage and vector tiles. All three formats are compressed into a regular zip file (.ZIP).
OS MasterMap Highways Network – RAMI is supplied in two formats: GML 3.2.1 and GeoPackage. Both formats are compressed into a regular zip file (.ZIP).
OS MasterMap Highways Network core products (Roads, RAMI, and Paths) are available to Public Sector Geospatial Agreement (PSGA) Members, commercial customers and OS Partners through the OS Data Hub. The products are available as both Full Supply and change-only update (COU) and customers can order an area of interest (AOI) or a Managed Great Britain Set (MGBS). The products are available as a download for all customers, and as a DVD for customers ordering a MGBS.
The products cover Great Britain. Information from the National Street Gazetteer will only be provided for England and Wales. Information from the Scottish Street Gazetteer will only be provided for Scotland.
OS MasterMap Highways Network products will only be supplied as non-geographic chunks. Non- geographic chunking is a way of dividing up data into chunks that are supplied in separate volumes that have a feature count, as opposed to a given geographic National Grid area. For this reason, it is possible for features from various geographic locations to appear in one volume and for adjacent features to appear in different volumes.
Non-geographic chunk volumes are designed to be loaded into spatial databases but can be used in a file format, provided all chunks are translated or imported into the system at the same time. For information on the volume feature counts for each feature type in OS MasterMap Highways Network, please see the in the .
RoadLink | Linear Network | RoadLink | Y | TOID | N/A | N/A |
RoadLinkAlternativeIdentifier | Linear Network | RoadLink | N | TOID (id in GML/technical spec) | RoadLink | TOID |
RoadLinkFormsPartOf | Linear Network | RoadLink | N | TOID | Road or Street | formsPartOf - Will be either Road TOID or Street USRN |
RoadLink_TopoTOIDRef | Linear Network | RoadLink | N | TOID | Topo Area | RelatedRoadAreaTOID - Will be the TOID of the Topo area(s) that represent the RoadLink |
AccessRestriction_NetworkRef | Routing and Asset Management Information | AccessRestriction | N | TOID | RoadLink | RoadLink_TOID - The TOID in the RoadLink table |
AccessRestriction | Routing and Asset Management Information | AccessRestriction | N | TOID | AccessRestriction_NetworkRef, AccessRestriction_Inclusion, AccessRestriction_Exemption | TOID |
AccessRestriction_Inclusion | Routing and Asset Management Information | AccessRestriction | N | TOID | AccessRestriction | TOID |
AccessRestriction_Exemption | Routing and Asset Management Information | AccessRestriction | N | TOID | AccessRestriction | TOID |
Hazard_NetworkRef | Routing and Asset Management Information | Hazard | Y | TOID | RoadLink and RoadNode | RoadLink_TOID and RoadNode _TOID - The TOID in the respective tables |
Hazard | Routing and Asset Management Information | Hazard | Y | TOID | Hazard_NetworkRef | TOID |
Hazard_NodeReference_LinkReference | Routing and Asset Management Information | Hazard | N | TOID | RoadLink | RoadLink_TOID |
RestrictionForVehicles_NetworkRef | Routing and Asset Management Information | VehicleRestriction, RestrictionForVehicles | N | TOID | RoadLink and RoadNode | RoadLink_TOID and RoadNode _TOID - The TOID in the respective tables |
RestrictionForVehicles | Routing and Asset Management Information | VehicleRestriction, RestrictionForVehicles | Y | TOID | RestrictionForVehicles_NetworkRef | TOID |
RestrictionForVehicles_NodeReference_LinkReference | Routing and Asset Management Information | VehicleRestriction, RestrictionForVehicles | N | TOID | RoadLink | RoadLinkTOID |
Road | Linear Network | Road | N | TOID | Road_NetworkRef | TOID |
Road_NetworkRef | Linear Network | Road | N | TOID | RoadLink | RoadLink_TOID - Is the TOID of the RoadLink table |
RoadNode | Linear Network | RoadNode | Y | TOID | N/A | N/A |
RoadNode_RelatedRoadArea | Linear Network | RoadNode | N | TOID | Topo Area | RelatedRoadAreaTOID - Will be the TOID of the Topo area(s) that represent the RoadNode |
Street_NetworkRef | Linear Network | Street | N | USRN | RoadLink | RoadLink_TOID - Will be the TOID of the RoadLink table |
Street | Linear Network | Street | N | USRN | Street_NetworkRef | USRN |
Structure_NetworkRef | Routing and Asset Management Information | Structure | N | TOID | RoadLink and RoadNode | RoadLink_TOID and RoadNode _TOID - The TOID in the respective tables |
Structure | Routing and Asset Management Information | Structure | Y | TOID | Structure_NetworkRef | TOID |
Structure_NodeReference_LinkReference | Routing and Asset Management Information | Structure | N | TOID | RoadLink | RoadLink_TOID |
TurnRestriction_NetworkRef | Routing and Asset Management Information | TurnRestriction | N | TOID | RoadLink | RoadLink_TOID - The TOID in the RoadLink table |
TurnRestriction | Routing and Asset Management Information | TurnRestriction | N | TOID | TurnRestriction_NetworkRef, TurnRestriction_Exemption, TurnRestriction_Inclusion | TOID |
TurnRestriction_Exemption | Routing and Asset Management Information | TurnRestriction | N | TOID | TurnRestriction | TOID |
TurnRestriction_Inclusion | Routing and Asset Management Information | TurnRestriction | N | TOID | TurnRestriction | TOID |
Maintenance Point | Routing and Asset Management Information | Maintenance | Y | ID | Street | Reference_To_StreetUSRN - The USRN in the Street table |
Maintenance Line | Routing and Asset Management Information | Maintenance | Y | ID | Street | Reference_To_StreetUSRN - The USRN in the Street table |
Maintenance Area | Routing and Asset Management Information | Maintenance | Y | ID | Street | Reference_To_StreetUSRN - The USRN in the Street table |
Maintenance No Geometry | Routing and Asset Management Information | Maintenance | N | ID | Street | Reference_To_StreetUSRN - The USRN in the Street table |
Reinstatement Point | Routing and Asset Management Information | Reinstatement | Y | ID | Street | Reference_To_StreetUSRN - The USRN in the Street table |
Reinstatement Line | Routing and Asset Management Information | Reinstatement | Y | ID | Street | Reference_To_StreetUSRN - The USRN in the Street table |
Reinstatement Area | Routing and Asset Management Information | Reinstatement | Y | ID | Street | Reference_To_StreetUSRN - The USRN in the Street table |
Reinstatement No Geometry | Routing and Asset Management Information | Reinstatement | Y | ID | Street | Reference_To_StreetUSRN - The USRN in the Street table |
Junction | Linear Network | RoadJunction | N | TOID | RoadNode | TOID, RoadNode_TOIDs (the junction can reference back to multiple road nodes) |
Highways Dedication | Routing and Asset Management Information | Dedication | Y | ID | Road, Street or Path | NetworkRef - TOID in RoadLink and PathLink table and USRN in the Street table |
Special Designation Point | Routing and Asset Management Information | SpecialDesignation | Y | networkRef | Street | NetworkRef - USRN in the Street table |
Special Designation Line | Routing and Asset Management Information | SpecialDesignation | Y | networkRef | Street | NetworkRef - USRN in the Street table |
Special Designation Area | Routing and Asset Management Information | SpecialDesignation | Y | networkRef | Street | NetworkRef - USRN in the Street table |
Special Designation No Geometry | Routing and Asset Management Information | SpecialDesignation | N | networkRef | Street | NetworkRef - USRN in the Street table |
Ferrylink | Linear Network | FerryLink | Y | TOID | N/A | N/A |
Ferrylink | Linear Network | FerryLink | N | TOID | FerryNode | FerryNode_TOID (one for startNode and one for endNode) |
FerryNode | Linear Network | FerryNode | Y | TOID | N/A | N/A |
FerryTerminal | Linear Network | FerryTerminal | N | refToFuncationalSite,roadNodeRef, pathNodeRef | Road Node, Path Node and Functional Site | TOID |
PathLink | Paths | PathLink | Y | TOID | N/A | N/A |
PathLinkAlternativeIdentifier | Paths | PathLink | N | TOID | PathLink | TOID |
PathLinkFormsPartOf | Paths | PathLink | N | TOID | Path or Street | formsPartOf - Will be either Path TOID or Street USRN |
PathLink_TopoTOIDRef | Paths | PathLink | N | TOID | Topo Area | RelatedPathAreaTOID - Will be the TOID of the Topo area(s) that represent the PathLink |
PathLink | Paths | PathLink | N | TOID | PathNode | PathNode_TOID (one for startNode and one for endNode) |
Path | Paths | Path | N | TOID | Path_NetworkRef | TOID |
Path_Ref_PathLink | Paths | Path | N | TOID | PathLink | PathLink_TOID - Is the TOID of the PathLink table |
PathNode | Paths | PathNode | Y | TOID | N/A | N/A |
PathNode_RelatedRoadArea | Paths | PathNode | N | TOID | Topo Area | RelatedPathAreaTOID - Will be the TOID of the Topo area(s) that represent the PathNode |
ConnectingLink | Paths | ConnectingLink | Y | TOID | PathNode and ConnectingNode | TOID |
ConnectingNode | Paths | ConnectingNode | Y | TOID | RoadLink | TOID |
OS MasterMap Highways Network is designed for use in a geographical information system (GIS). For details of Ordnance Survey’s Licensed Partners who can assist you with incorporating the product in their systems, please see the GIS mapping page on the OS website.
Ordnance Survey does not recommend either suppliers or software products, as the most appropriate system will depend on many factors, such as the amount of data being taken, resources available within the organisation, the existing and planned information technology infrastructure and last but by no means least, the applications that the data will be used for.
However, the following minimum elements will be required in any system:
A means of reading the data, either in its native format, or by translating it into a file format or for storage in a database.
A means of storing and distributing the data, perhaps in a database or through a web-based service.
A way of visualising and/or querying the data, typically a GIS.
You are advised to copy the supplied data to a backup medium before following the steps in this guide.
For reading purposes, it is recommended that users store the data on a single hard disc. This will speed up the ability of your computer to read the data.
Uncompressed file sizes for the Full Supply of England, Scotland and Wales are as follows:
OS MasterMap Highways Network – Roads: 29GB
OS MasterMap Highways Network – RAMI: 43GB
OS MasterMap Highways Network – Paths: 11GB
OS MasterMap Highways Network – Roads: 8.5GB
OS MasterMap Highways Network – RAMI: 3GB
OS MasterMap Highways Network – Paths: 5GB
OS MasterMap Highways Network – Roads: 1.5GB
OS MasterMap Highways Network – Paths: 0.4GB
Schema files are used to interpret the GML and translate it into a suitable data format by your chosen software. However, we are aware that some firewalls will block access to these. In these instances, it is suggested that you download the schemas from the OS MasterMap Highways Network GitHub repository.
The file naming for the OS MasterMap Highways Network GML will be constructed as:
Highways_ProductName_FeatureType_SupplyType_NullorDelete_volumenumber.gml.gz.
The name is composed of the following elements:
Highways: Identifies that the GML is from the OS MasterMap Highways Network product family.
ProductName: Is the name of the product that is being supplied, for example, Roads.
FeatureType: Is the name of the feature type that is being supplied in the GML file, for example, RoadLink.
SupplyType: Is the type of supply the GML is, for example, Full Supply or COU.
NullorDelete: This will not be present in any GML file names if the GML forms part of a Full Supply. If the GML forms part of a COU supply, then 'Delete' will identify if the file contains all the features which need removing from the customer holding as a part of the COU application.
Volumenumber: Will be the volume number for the file which will be three digits and the first volume will be 001.
Highways_Roads_RoadLink_Full_001.gml.gz
Highways_Rrami_AccessRestriction_Full_001.gml.gz
Highways_Paths_Maintenance_Full_001.gml.gz
The file naming for the OS MasterMap Highways Network GeoPackage will be constructed as:
OSMasterMapHighwaysNetworkProductName_gb.gpkg.
Examples of GeoPackage file names:
OSMasterMapHighwaysNetworkRoad_gb.gpkg
OSMasterMapHighwaysNetworkPath_gb.gpkg
OSMasterMapHighwaysNetworkRAMI_gb.gpkg
The file naming for the OS MasterMap Highways Network vector tiles will be constructed as:
OSMasterMapHighwaysNetworkProductName_gb.mbtiles
Examples of the vector tiles file names:
OSMasterMapHighwaysNetworkRoad_gb.mbtiles
OSMasterMapHighwaysNetworkPath_gb.mbtiles
The Highways GML data is supplied in a compressed form (gzip). Some software can access these files directly; others will require it to be uncompressed. To uncompress the zipped data files (.gz extension), use an unzipping utility found on most PCs, for example, WinZip. Open-source zipping / unzipping software can be downloaded from the Internet, for example, 7-Zip.
Before loading the data, you will need to unzip it by using any of the regular zip programs available or via the facility within the Windows 10 operating system.
When a customer receives an order, the product will be packaged as follows:
Data folder: Contains the GML, GeoPackage or vector tiles files which make up the ordered product.
Doc folder: Contains a summary.gml file which will contain specific information about the customer order, including the order number, extent and order type information (‘Full Supply’ or ‘COU’).
Resources folder: Contains the product’s Feature Validation Data Set (FVDS). For further information on these resources, please refer to the .
The GeoPackage and vector tiles formats will be available for GB coverage only, so will not contain COU files.
This getting started guide focuses solely on loading the product in GML format. For guidance on using the products in GeoPackage or vector tiles formats, please see the following two format-specific getting started guides:
GML is an XML dialect, which can be used to model geographic features. It was designed by the Open Geospatial Consortium (OGC) as a means for people to share information regardless of the applications or technology that they use. In the first instance, GML was used to overcome the differences between different GIS applications by providing an open standards file format as an alternative to proprietary formats.
The data can be loaded into several GIS. This section describes how to translate the GML and load it into some commonly used GIS. However, as the data is based on a relational data model, not all GIS formats will support this and storing the data in a relational database is recommended. For more information about other GIS that OS MasterMap Highways Network is compatible with, please speak to your OS Relationship Manager.
The common GIS software applications covered in this section are:
QGIS
ArcMap
MapInfo Professional
Cadcorp SIS Desktop
Software for loading into a database:
Go Loader – PostGreSQL
Some software will successfully read the GML, including both geometry and textual information. However, where a data field contains multiplicity, these elements will be ignored.
You can find .
Select the Add Data button (black cross on a yellow diamond) from the top ribbon.
Connect to Folder button (yellow rectangular folder with a black cross on top of it).
Highways Network data by clicking the Connect to Folder button (black cross on top of a yellow rectangle).
In the FME Quick Translator dialog, either select File > Translate or click the Translate Data button (side-by-side upended brown and orange cylinders connected by a green arrow).
Halfway down the GML (Geography Markup Language) Parameters dialog, click the ellipsis button to the right of the Application Schema box, then navigate to the schema location and select GeneralNetwork.xsd. (The schemas can be downloaded from the OS.
Use the file browser to navigate to the Highways data file (usually a .bds file) and click Next.
Select the OS MasterMap Highways Network Path data you would like to add to the .bds file. (Click on the three dots to open the file browser).
Click Next > Load to begin loading the OS MasterMap Highways Network Paths data.
This getting started guide provides instructions for using OS MasterMap Highways Network in different software applications. Users with limited technical knowledge will be able to follow this guide.
Ordnance Survey, GeoPlace and Improvement Service have collaborated to bring together Ordnance Survey’s detailed road and path information, the National Street Gazetteer (NSG), the Trunk Road Street Gazetteer (TRSG), and the Scottish Street Gazetteer (SSG) to create an authoritative road and path network for Great Britain: OS MasterMap Highways Network.
OS MasterMap Highways Network integrates the Unique Street Reference Number (USRN) from the gazetteers with the most detailed definitive geometry from Ordnance Survey. It is produced in partnership with GeoPlace and the Local Government Association, and as of March 2021, contains data created and maintained by Scottish Local Government.
The OS MasterMap Highways Network product family includes three core products:
OS MasterMap Highways Network – Roads
OS MasterMap Highways Network – Routing and Asset Management Information (RAMI)
OS MasterMap Highways Network – Paths
OS MasterMap Highways Network products contain a wide range of features, including:
Unique Street Reference Number (USRN).
Road names from the naming and numbering authority.
Department for Transport (DfT) road classifications.
Road maintenance authority.
Motorway junction to junction information.
Routing information.
Information on height, weight, width and length restrictions.
Special designations.
Road reinstatement information.
Connected network across Great Britain (GB), including islands through the Ferry Network.
OS MasterMap Highways Network is a single authoritative view of the road and path network that underpins decision making across government as it:
Reduces duplication of effort on maintaining highways information across multiple departments and datasets.
Facilitates data-sharing.
The product provides OS detailed geometry and routing information on highways together with the best asset management information from authoritative sources into one central location.
It enables planning, routing and navigation for a variety of vehicle types.
The USRN as the key identifier for a Street enables systems to share information about the same entities without the need to match multiple datasets. With the USRN, you can also easily link to OS's AddressBase products, which lets you search for or navigate to an address and find the property access and delivery points.
The product provides accurate and precise asset management information on who maintains the road network, special designations and the type of surface reinstatement value.
OS MasterMap Highways Network is designed to be used as a single source of highway asset management by private and public sectors alike. The following table describes some of the key product applications:
Snowflake Software provides standard project templates for several OS products. Users can use these templates to load data to a standard data model to meet the requirements of most end-users.
Snowflake has created a standard project to support the new OS MasterMap Highways Network dataset. This can be downloaded from the Snowflake support portal.
The project also includes columns to help support styling / MapInfo styling if needed.
Open GO Loader, File/Download Templates, and download the new standard GO Loader project for Highways, from the Customer portal (Products/GO Loader/Resources/Project Templates).
Save the file to your drive and unzip it.
In GO Loader, open the new extracted OS_Highways.glp GO Loader Standard project (or drag it into the Project File area of the screen).
Select the Loader Configuration tab to set your target database details.
Set a directory location on your hard drive for ‘load lists’ (choose any valid local location).
Create all the tables defined in the GO Loader Highways project (ideally choose a new database or schema without other existing tables).
Load all your Highways data files.
Create the Spatial Indexes and other indexes.
Product name | Suggested application |
---|---|
OS MasterMap Highways Network – Roads
Source for legal road identifications
Costings or benefits of road policies
Calculating funding allocations
For evidence-based policy making
Journey and transport planning
Emergency service planning
Enforcement regulation
Traffic statistics
School allocation
Smart cities
OS MasterMap Highways Network – Routing and Asset Management Information (RAMI)
Source for legal road identifications
Costings or benefits of road policies
Calculating funding allocations
Policy making
Asset management
Journey planning, routing, and navigation
Emergency service planning
Transport planning
Enforcement regulation
Traffic statistics
Delivery
Waste management
Planned works
Projects on the resilience of infrastructure
Lane rental schemes
Smart cities
OS MasterMap Highways Network – Paths
To estimate costs or benefits of road and paths policies
Calculating funding allocations
Policy making
Asset management
Journey planning, routing, and navigation
Emergency service planning
Transport planning
Delivery
Enforcement regulation
School allocation
Sustainable travel
Planned works
Projects on the resilience of infrastructure
Smart cities