Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Release notes for the OS MasterMap Highways Network products.
This release note provides information about the November 2024 release of OS MasterMap Highways Network.
This release note provides information about the October 2024 release of OS MasterMap Highways Network.
This release note provides information about the September 2024 release of OS MasterMap Highways Network.
This release note provides information about the August 2024 release of OS MasterMap Highways Network.
This release note provides information about the July 2024 release of OS MasterMap Highways Network.
This release note provides information about the June 2024 release of OS MasterMap Highways Network.
This release note provides information about the May 2024 release of OS MasterMap Highways Network.
This document contains additional theoretical information related to OS MasterMap Highways Network. All users will find the Product Information document useful and informative.
The OS MasterMap Highways Network product family provides an authoritative road and path network for Great Britain. The products are the result of collaboration between Ordnance Survey, GeoPlace and Improvement Service 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).
The Highways Network integrates the Unique Street Reference Number (USRN) from the gazetteers with the most detailed definitive geometry from Ordnance Survey. The OS MasterMap Highways Network was produced in partnership with GeoPlace and the Local Government Association, and as of March 2021, it contains data created and maintained by Scottish Local Government.
The OS MasterMap Highways Network product family includes a road network, a path network, connectivity across British islands through a ferry network, routing and asset management information, as well as detailed speed information on all roads.
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
In addition to these three core products, the OS MasterMap Highways Network product family is enhanced by three speed data products:
OS MasterMap Highways Network with Routing and Asset Management Information and Average Speed
OS MasterMap Highways Network with Routing and Asset Management Information and Speed Limits
OS MasterMap Highways Network with Routing and Asset Management Information and Average Speed and Speed Limits
These three speed data products are supplied with an additional data file which will be either Average Speed, Speed Limits or a combination of both.
The OS MasterMap Highways Network with Speed products are not available under the PSGA Contract, but are available via our Partner channel.
GeoPlace is a limited liability partnership jointly owned by the Local Government Association and Ordnance Survey. It is responsible for compiling and maintaining the National Street Gazetteer (NSG).
This is the definitive referencing system used in the notification process and the coordination of street works. Under legislation, each highway authority in England and Wales is required to create and maintain its own Local Street Gazetteer (LSG) and Associated Street Data (ASD). These are then compiled into the only master index built to the national standard (BS 7666).
The OS MasterMap Highways Network has been designed to be INSPIRE compliant. INSPIRE is the Infrastructure for Spatial Information in Europe. It is designed to ensure that the spatial data infrastructures of the Member States of the European Community are compatible and usable between member states to improve decision making and operations. The INSPIRE Transport Networks Data Specification forms the basis of the specifications for the Roads, Routing and Asset Management Information and Paths products.
OS MasterMap Highways Network specifications have also been extended to include additional properties included in British Standard 7666-1:2006, Spatial datasets for geographical referencing.
The coordinate reference system used by OS MasterMap Highways Network is the British National Grid. The British National Grid (BNG) spatial reference system uses the OSGB36 geodetic datum and a single Transverse Mercator projection for the whole of Great Britain. Positions on this projection are described using easting and northing coordinates in units of metres. The BNG is a horizontal spatial reference system only; it does not include a vertical (height) reference system.
In the Geography Markup Language (GML) data, this is represented by reference to its entry in the EPSG registry, as http://www.opengis.net/def/crs/EPSG/0/27700.
OS MasterMap Highways Network products contain several features, including the following:
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
Vehicle height, weight, width and length restrictions information
Special designations
Road reinstatement information
Connected network across Great Britain, including islands, through the Ferry Network
Average Speed information broken down into six time periods for each day
Speed Limits
One of the key strengths of the products is the collection of street information at the local highway authority level. The benefit of this is that the data capture is at the earliest point of creation within a local highway authority and there is detailed local knowledge driven by statutory requirements.
OS MasterMap Highways Network is designed to be used as a single source of highway asset management by private and public sectors alike. It can be used for the following applications:
As a source for legal road identifications.
To estimate costs or benefits of road policies.
For efficient funding allocations and evidence-based policy making, including:
Managing policies
Producing statistics
Allocating funding
Supporting legislation
Asset management
Journey planning, routing and navigation
Emergency service and civil contingency planning
Transport planning
Smart cities
For speed data calculations and analysis:
Congestion analysis and drive time studies.
Environmental analysis to monitor emissions and carry out standing time analysis.
Routing and route optimisation.
Planning emergency response routing.
Planning and development using traffic and infrastructure modelling.
Autonomous vehicles' usage of speed limits.
A Path feature is like a Road feature as it holds information about path names which have been captured by Ordnance Survey. A Path feature is a link set which will reference the Path Links which share the same name, irrespective of which local authority is responsible for it. A Path Link could be referenced by multiple Path features.
OS MasterMap Highways Network products' features are classified into feature types. Each feature type has associated attribution, and further detail of this can be found in each product's technical specification.
The following table details the feature types present within the OS MasterMap Highways Network products. The letter Y indicates that a feature type is present in a product, whereas the letter N indicates that a feature type is not present in a product.
Road Link
Road Node
Road
Street
Road Junction
Ferry Link
Ferry Node
Ferry Terminal
Road Link
Road Node
Road
Street
Road Junction
Ferry Link
Ferry Node
Ferry Terminal
Access Restrictions
Turn Restrictions
Restrictions For Vehicles
Hazards
Structures
Maintenance
Reinstatement
Highways Dedication
Special Designation
Path Link
Path Node
Connecting Link
Connecting Node
Path
Street
Ferry Link
Ferry Node
Ferry Terminal
Maintenance
Reinstatement
Highways Dedication
Special Designation
Road Link
Road Node
Road
Street
Road Junction
Ferry Link
Ferry Node
Ferry Terminal
Access Restrictions
Turn Restrictions
Restrictions For Vehicles
Hazards
Structures
Maintenance
Reinstatement
Highways Dedication
Special Designation
Average Speed
Speed Limits
The following table details the feature types present within the OS MasterMap Highways Network products. The letter Y indicates that a feature type is present in a product, whereas the letter N indicates that a feature type is not present in a product.
This release note provides information about the August 2024 release of OS MasterMap Highways Network.
The following information relates to the currency of the source data used in the creation of this release of OS MasterMap Highways Network:
Data source | Date |
---|---|
In the August 2024 release of OS MasterMap Highways Network:
There are 5 instances of overlapping road links.
There are 216 instances of overlapping path links.
There are 34 instances where a road link and a path link overlap, representing the same real-world feature.
There are 191 road links disconnected from main network or not properly connected at a node; these are not on major parts of the network.
There are 3 road links which are less than 1m in length.
There are 292 connecting links which are less than 1m in length.
There is 1 path link which is less than 1m in length.
There are 9 features in the Street table which have a street type of either Designated Street Name or Officially Described Street and have no associated maintenance record.
There are 2 instances of connecting nodes referencing a motorway.
The Trans-European Transport (TEN-T) network forms a set of road, rail, air and water transport networks spanning the European Union. As a result of the UK withdrawing from the European Union, the UK is no longer a part of the TEN-T network; therefore, the TEN-T lookup table has been withdrawn as of October 2023.
The next release of OS MasterMap Highways Network is scheduled for September 2024.
This release note provides information about the October 2024 release of OS MasterMap Highways Network.
The following information relates to the currency of the source data used in the creation of this release of OS MasterMap Highways Network:
Data source | Date |
---|
OS MasterMap Highways Network feature counts
Roads’ feature | Count |
---|
In the September 2024 release of OS MasterMap Highways Network:
There are 4 instances of overlapping road links.
There are 140 instances of overlapping path links.
There are 25 instances where a road link and a path link overlap, representing the same real-world feature.
There are 199 road links disconnected from main network or not properly connected at a node; these are not on major parts of the network.
There are 3 road links which are less than 1m in length.
There are 290 connecting links which are less than 1m in length.
There is 1 path link which is less than 1m in length.
There are 12 features in the Street table which have a street type of either Designated Street Name or Officially Described Street and have no associated maintenance record.
There are 0 instances of connecting nodes referencing a motorway.
The Trans-European Transport (TEN-T) network forms a set of road, rail, air and water transport networks spanning the European Union. As a result of the UK withdrawing from the European Union, the UK is no longer a part of the TEN-T network; therefore, the TEN-T lookup table has been withdrawn as of October 2023.
The next release of OS MasterMap Highways Network is scheduled for November 2024.
A Road Link is a line segment representing the general alignment of the road carriageway. It can represent single carriageways, dual carriageways, slip roads, roundabouts and indicative trajectories across traffic squares. It defines the geometry and connectivity of a road network between two points. Road Links hold information on the road name, classification, form, length and other attributes which are specified in the .
A Path Node is a topological node connecting to at least one Path Link, providing network connectivity. It is a point used to represent connectivity between path links or the end of a road.
A Path Link is a line segment representing the alignment of a path. Path links hold information about the name of the path, its length and its nature, alongside other attribution which is detailed in the . Path Links define the geometry and connectivity of the Path Network between two points.
Path Links will be captured where:
They provide a route that cannot be inferred from the Road Network.
They provide connectivity between road networks.
There is a canal path or tow path
There are paths over footbridges and under subways Path Links will not be captured where:
They run parallel to the Road Network, for example, a pavement.
They are within school boundaries and cemeteries where there are closing times.
They are connected to a Motorway.
There is a physical obstruction which prevents connectivity.
There are multiple paths that essentially serve the same purpose when some rationalisation is applied.
This release note provides information about the November 2024 release of OS MasterMap Highways Network.
The following information relates to the currency of the source data used in the creation of this release of OS MasterMap Highways Network:
Data source | Date |
---|
Roads’ feature | Count |
---|
In the November 2024 release of OS MasterMap Highways Network:
There are 4 instances of overlapping road links.
There are 133 instances of overlapping path links.
There are 25 instances where a road link and a path link overlap, representing the same real-world feature (example below).
There are 204 road links disconnected from main network or not properly connected at a node; these are not on major parts of the network.
There are 3 road links which are less than 1m in length.
There are 290 connecting links which are less than 1m in length.
There is 1 path link which is less than 1m in length.
There are 17 features in the Street table which have a street type of either Designated Street Name or Officially Described Street and have no associated maintenance record.
The next release of OS MasterMap Highways Network is scheduled for December 2024.
This release note provides information about the July 2024 release of OS MasterMap Highways Network.
The following information relates to the currency of the source data used in the creation of this release of OS MasterMap Highways Network:
Data source | Date |
---|
Roads’ feature | Count |
---|
In the July 2024 release of OS MasterMap Highways Network:
There are 6 instances of overlapping road links.
There are 242 instances of overlapping path links.
There are 40 instances where a road link and a path link overlap, representing the same real-world feature.
There are 179 road links disconnected from main network or not properly connected at a node; these are not on major parts of the network.
There are 3 road links which are less than 1m in length.
There are 293 connecting links which are less than 1m in length.
There is 1 path link which is less than 1m in length.
There are 2 features in the Street table which have a street type of either Designated Street Name or Officially Described Street and have no associated maintenance record.
There are 5 instances of connecting nodes referencing a motorway.
The Trans-European Transport (TEN-T) network forms a set of road, rail, air and water transport networks spanning the European Union. As a result of the UK withdrawing from the European Union, the UK is no longer a part of the TEN-T network; therefore, the TEN-T lookup table has been withdrawn as of October 2023.
The next release of OS MasterMap Highways Network is scheduled for August 2024.
This release note provides information about the May 2024 release of OS MasterMap Highways Network.
The following information relates to the currency of the source data used in the creation of this release of OS MasterMap Highways Network:
Data source | Date |
---|
Roads’ feature | Count |
---|
In the May 2024 release of OS MasterMap Highways Network:
There are 10 instances of overlapping road links.
There are 316 instances of overlapping path links.
There are 50 instances where a road link and a path link overlap, representing the same real-world feature.
There are 152 road links disconnected from main network or not properly connected at a node; these are not on major parts of the network.
There are 3 road links which are less than 1m in length.
There are 294 connecting links which are less than 1m in length.
There is 1 path link which is less than 1m in length.
There are 2 features in the Street table which have a street type of either Designated Street Name or Officially Described Street and have no associated maintenance record.
There are 5 instances of connecting nodes referencing a motorway.
The Trans-European Transport (TEN-T) network forms a set of road, rail, air and water transport networks spanning the European Union. As a result of the UK withdrawing from the European Union, the UK is no longer a part of the TEN-T network; therefore, the TEN-T lookup table has been withdrawn as of October 2023.
The next release of OS MasterMap Highways Network is scheduled for June 2024.
This release note provides information about the June 2024 release of OS MasterMap Highways Network.
The following information relates to the currency of the source data used in the creation of this release of OS MasterMap Highways Network:
Data source | Date |
---|
Roads’ feature | Count |
---|
In the May 2024 release of OS MasterMap Highways Network:
There are 10 instances of overlapping road links.
There are 316 instances of overlapping path links.
There are 50 instances where a road link and a path link overlap, representing the same real-world feature.
There are 152 road links disconnected from main network or not properly connected at a node; these are not on major parts of the network.
There are 3 road links which are less than 1m in length.
There are 294 connecting links which are less than 1m in length.
There is 1 path link which is less than 1m in length.
There are 2 features in the Street table which have a street type of either Designated Street Name or Officially Described Street and have no associated maintenance record.
There are 5 instances of connecting nodes referencing a motorway.
The Trans-European Transport (TEN-T) network forms a set of road, rail, air and water transport networks spanning the European Union. As a result of the UK withdrawing from the European Union, the UK is no longer a part of the TEN-T network; therefore, the TEN-T lookup table has been withdrawn as of October 2023.
The next release of OS MasterMap Highways Network is scheduled for July 2024.
The Road and Path Network are topologically structured together. Connecting Links enable this connection between the Road Network and the Path Network. A Connecting Link is a line segment which represents a logical connection between the Path Network and the Road Network; it does not represent a real-world feature.
A Connecting Node is a point feature which identifies where a Path connects to the Road Network. The Connecting Node connects to the start or end of one or more RoadLinks and are spatially coincident with RoadNodes.
A Rode Node is a topological node connecting to at least one Road Link, providing network connectivity. It is a point used to represent connectivity between road links or the end of a road. A Road Node will hold information on its classification, and if it forms a part of a numbered junction, then the Road Node will provide this number.
The Street feature is the definition of the street as defined in the National or Scottish Street Gazetteer. Local authorities have a statutory responsibility which means that they are the source of information for both street naming and managing the highways/roads network.
Each Street feature has a USRN, a unique and persistent identifier for a street contained in either the National or Scottish Street Gazetteer. Every street, road, track, path, cycle track or way is assigned a USRN by a Roads Authority, Local Highway Authority or Highways England. Each authority is provided a USRN range that is centrally allocated and managed by GeoPlace in England and Wales and by Improvement Service in Scotland.
A Street feature encompasses both Roads and Paths. Therefore, a Street feature will reference the Road Links or Path Links. Where a Street crosses an administrative boundary, a new Street feature will be created. A Road Link or Path Link could be referenced by multiple Street features.
The Street features which are supplied with the Routing and Asset Management Information product will contain all Street features which have either been matched to at least one Road Link or have not been matched. The Street features which are supplied with the Paths product will only contain Street features which have only been matched to a Path Link.
A Road feature holds information about road names and road numbers which have been captured by Ordnance Survey. A Road feature will reference the Road Links which share the same name (for example, Wellington Road in the image below) or number (for example, the A41 in the lower image), irrespective of which local authority is responsible for it. The link set may not be contiguous across junctions or where a road consists of separate sections, which may be separated by some considerable distance. A Road Link could be referenced by multiple Road features.
Paths’ feature | Count |
---|---|
Paths’ feature | Count |
---|
Paths’ feature | Count |
---|
Paths’ feature | Count |
---|
Paths’ feature | Count |
---|
Paths’ feature | Count |
---|
GeoPlace Streets Data
04 July 2024
Improvement Service Streets Data
05 July 2024
OS Road, Path, and Routing Content
03 July 2024
Roads’ feature
Count
AccessRestriction
35 054
FerryLink
99
FerryNode
128
FerryTerminal
128
Hazard
41 616
HighwayDedication
3 581 037
Maintenance
1 313 493
Reinstatement
1 527 330
RestrictionForVehicles
12 019
Road
850 690
RoadLink
8 474 308
RoadNode
7 508 825
RoadJunction
6 819
SpecialDesignation
774 121
Street
1 480 895
Structure
1 369 540
TurnRestriction
1 044 552
ConnectingLink
1 991 885
ConnectingNode
1 849 987
FerryLink
38
FerryNode
73
FerryTerminal
73
HighwayDedication
400 260
Maintenance
203 632
Path
25 306
PathLink
3 255 168
PathNode
3 856 288
Reinstatement
209 091
SpecialDesignation
12 537
Street
253 491
GeoPlace Streets Data | 04 September 2024 |
Improvement Service Streets Data | 04 September 2024 |
OS Road, Path, and Routing Content | 05 September 2024 |
AccessRestriction | 35 253 |
FerryLink | 101 |
FerryNode | 131 |
FerryTerminal | 131 |
Hazard | 41 680 |
HighwayDedication | 3 586 783 |
Maintenance | 1 315 309 |
Reinstatement | 1 529 074 |
RestrictionForVehicles | 12 059 |
Road | 851 582 |
RoadLink | 8 478 035 |
RoadNode | 7 511 587 |
RoadJunction | 6 823 |
SpecialDesignation | 781 717 |
Street | 1 482 332 |
Structure | 1 373 178 |
TurnRestriction | 1 045 290 |
ConnectingLink | 1 992 908 |
ConnectingNode | 1 850 545 |
FerryLink | 87 |
FerryNode | 163 |
FerryTerminal | 163 |
HighwayDedication | 401 678 |
Maintenance | 204 204 |
Path | 25 306 |
PathLink | 3 280 634 |
PathNode | 3 881 952 |
Reinstatement | 209 508 |
SpecialDesignation | 12 745 |
Street | 254 213 |
Feature type | Roads | RAMI | Paths | RAMI and Speed |
Road Link | Y | Y | N | Y |
Road Node | Y | Y | N | Y |
Path Link | N | N | Y | N |
Path Node | N | N | Y | N |
Connecting Link | N | N | Y | N |
Connecting Node | N | N | Y | N |
Road | Y | Y | N | Y |
Path | N | N | Y | N |
Street | Y | Y | Y | Y |
Road Junction | Y | Y | N | Y |
Ferry Link | Y | Y | Y | Y |
Ferry Node | Y | Y | Y | Y |
Ferry Terminal | Y | Y | Y | Y |
Access Restrictions | N | Y | N | Y |
Turn Restrictions | N | Y | N | Y |
Restrictions For Vehicles | N | Y | N | Y |
Hazards | N | Y | N | Y |
Structures | N | Y | N | Y |
Maintenance | N | Y | Y | Y |
Feature type | Roads | RAMI | Paths | RAMI and Speed |
Reinstatement | N | Y | Y | Y |
Highways Dedication | N | Y | Y | Y |
Special Designation | N | Y | Y | Y |
Average Speed | N | N | N | Y |
Speed Limits | N | N | N | Y |
Feature Validation Data Set | Y | Y | Y | Y |
OS Open Roads lookup table | Y | Y | N | Y |
GeoPlace Streets Data | 04 October 2024 |
Improvement Service Streets Data | 04 October 2024 |
OS Road, Path, and Routing Content | 03 October 2024 |
AccessRestriction | 35 291 |
FerryLink | 101 |
FerryNode | 131 |
FerryTerminal | 131 |
Hazard | 41 735 |
HighwayDedication | 3 590 160 |
Maintenance | 1 316 423 |
Reinstatement | 1 529 978 |
RestrictionForVehicles | 12 054 |
Road | 852 013 |
RoadLink | 8 482 692 |
RoadNode | 7 515 837 |
RoadJunction | 6 824 |
SpecialDesignation | 783 563 |
Street | 1 486 504 |
Structure | 1 375 194 |
TurnRestriction | 1 045 569 |
ConnectingLink | 1 993 547 |
ConnectingNode | 1 851 111 |
FerryLink | 91 |
FerryNode | 170 |
FerryTerminal | 170 |
HighwayDedication | 402 092 |
Maintenance | 204 191 |
Path | 25 317 |
PathLink | 3 297 131 |
PathNode | 3 898 474 |
Reinstatement | 209 491 |
SpecialDesignation | 12 800 |
Street | 255 339 |
GeoPlace Streets Data | 05 June 2024 |
Improvement Service Streets Data | 05 June 2024 |
OS Road, Path, and Routing Content | 06 June 2024 |
AccessRestriction | 34 993 |
FerryLink | 99 |
FerryNode | 128 |
FerryTerminal | 128 |
Hazard | 41 570 |
HighwayDedication | 3 578 077 |
Maintenance | 1 312 664 |
Reinstatement | 1 526 463 |
RestrictionForVehicles | 12 010 |
Road | 850 204 |
RoadLink | 8 467 093 |
RoadNode | 7 502 019 |
RoadJunction | 6 781 |
SpecialDesignation | 772 431 |
Street | 1 479 968 |
Structure | 1 367 819 |
TurnRestriction | 1 044 007 |
ConnectingLink | 1 991 260 |
ConnectingNode | 1 849 544 |
FerryLink | 36 |
FerryNode | 69 |
FerryTerminal | 69 |
HighwayDedication | 399 526 |
Maintenance | 203 389 |
Path | 25 304 |
PathLink | 3 241 653 |
PathNode | 3 842 558 |
Reinstatement | 208 845 |
SpecialDesignation | 12 520 |
Street | 253 079 |
GeoPlace Streets Data | 05 April 2024 |
Improvement Service Streets Data | 05 April 2024 |
OS Road, Path, and Routing Content | 05 April 2024 |
AccessRestriction | 34 900 |
FerryLink | 101 |
FerryNode | 128 |
FerryTerminal | 128 |
Hazard | 41 478 |
HighwayDedication | 357 2507 |
Maintenance | 1 311 206 |
Reinstatement | 1 526 115 |
RestrictionForVehicles | 11 979 |
Road | 849 187 |
RoadLink | 8 453 894 |
RoadNode | 7 489 965 |
RoadJunction | 6 646 |
SpecialDesignation | 769 210 |
Street | 1 475 423 |
Structure | 1 364 319 |
TurnRestriction | 1 042 828 |
ConnectingLink | 1 990 036 |
ConnectingNode | 1 848 579 |
FerryLink | 36 |
FerryNode | 69 |
FerryTerminal | 69 |
HighwayDedication | 397 267 |
Maintenance | 202 440 |
Path | 25 288 |
PathLink | 3 213 683 |
PathNode | 3 814 163 |
Reinstatement | 207 896 |
SpecialDesignation | 12 264 |
Street | 249 890 |
GeoPlace Streets Data | 03 May 2024 |
Improvement Service Streets Data | 03 May 2024 |
OS Road, Path, and Routing Content | 03 May 2024 |
AccessRestriction | 34 900 |
FerryLink | 101 |
FerryNode | 128 |
FerryTerminal | 128 |
Hazard | 41 478 |
HighwayDedication | 357 2507 |
Maintenance | 1 311 206 |
Reinstatement | 1 526 115 |
RestrictionForVehicles | 11 979 |
Road | 849 187 |
RoadLink | 8 453 894 |
RoadNode | 7 489 965 |
RoadJunction | 6 646 |
SpecialDesignation | 769 210 |
Street | 1 475 423 |
Structure | 1 364 319 |
TurnRestriction | 1 042 828 |
ConnectingLink | 1 990 036 |
ConnectingNode | 1 848 579 |
FerryLink | 36 |
FerryNode | 69 |
FerryTerminal | 69 |
HighwayDedication | 397 267 |
Maintenance | 202 440 |
Path | 25 288 |
PathLink | 3 213 683 |
PathNode | 3 814 163 |
Reinstatement | 207 896 |
SpecialDesignation | 12 264 |
Street | 249 890 |
OS MasterMap Highways Network integrates Ordnance Survey's detailed road and path information with the authoritative sources of the National Street Gazetteer (NSG), the Trunk Road Street Gazetteer (TRSG) and the Scottish Street Gazetteer (SSG). These sources contain the definitive information provided by the Local and National Roads and Highways Authorities.
To bring this information together, where possible the geometry of streets captured by a Roads or Highway Authority is spatially matched to the geometry of OS RoadLinks and PathLinks. Where this match is successful, the Ordnance Survey geometry is the base geometry used for the Highways Network, enabling the amalgamation of the NSG, SSG and TRSG with Ordnance Survey data. Where spatial matching cannot match the geometry captured by the Roads or Highway Authority to OS geometry, the Roads or Highway Authority geometry is used as the source geometry to represent the extent of the Street, ensuring that all USRNs and associated data provided are included in the product.
Additionally, OS MasterMap Highways Network is enriched with third-party information on speed data which is connected to the Ordnance Survey road network and will provide detailed information on average speed and speed limits across Great Britain.
The Roads product provides a topologically structured link and node representation of the road network and gives connectivity across Great Britain through Ferry features. It provides information on names associated with the road network, being either the legal definitive view of a road name or the plated road name, plus road numbering, junction names and junction numbers. In addition to naming information, the product also provides information on road classification, road function, primary routes and road node classification.
The Routing and Asset Management Information product provides the same functionality as the Roads product, with additional information on both managing the road as an asset and routing information, which aids navigation. The routing and asset management information integrates data from Ordnance Survey's large-scale information and the Additional Street Data held within the NSG and SSG. The routing information covers such aspects as vehicle restrictions, covering access, manoeuvres, and physical characteristics. The asset management information, on the other hand, provides details on the authority responsible for maintaining a road, how a road should be restored following street works and if there are any unusual conditions that the local highway authority have associated with a road.
New OS MasterMap Highways Network With Speed Data contracts cannot be entered into after 29 March 2023. Supply of product updates to customers with existing contracts continues until March 2024.
Average speed and indicative speed limits are now available to access directly from the OS National Geographic Database (OS NGD) Transport Theme. These datasets are available under the PSGA and make it easier to analyse travel times and provide more accurate insight for safety and infrastructure policy decisions.
The Speed data is made available alongside the OS MasterMap Highways Network – Routing and Asset Management Information (RAMI) product and is supplied in three separate products which will provide Average Speed, Speed Limits and the combined version of both Average Speed and Speed Limits.
OS MasterMap Highways Network with Routing and Asset Management Information and Average Speed will provide detailed historical speed information on the average speed travelled for the entire road network in Great Britain. The average speed is provided for each road link and for six distinct times of each day, in both directions of travel. This dataset is based on a year’s worth of information and will aid in calculating congestion and drive times, routing optimisation and planning.
OS MasterMap Highways Network with Routing and Asset Management Information and Speed Limits will provide the speed limit for each road link in Great Britain based on road traffic signs. This dataset will enable you to determine speed restrictions on the road, optimise routing and calculate congestion and drive times.
Both Average Speed and Speed Limits data are linked to the corresponding OS MasterMap Highways Network Road Link feature to which it belongs, identified by the Road Link topographic identifier (TOID).
The Paths product provides a topologically structured link and node representation of the pedestrian path and ferry network throughout Great Britain. The path network will provide connectivity between the road network but will not provide a route which can be inferred from the road network. Instead, the path network can be connected to the road network within the Roads or Routing and Asset Management Information products. The Paths product provides information on names associated with the path network, the path function and its surface type. In addition to the network information, the product also provides asset management information which identifies the authority responsible for maintaining the path, how the path should be restored following street works and if there are any unusual conditions that the local highways or roads authority have associated to the path.
A Ferry Node is a point feature which identifies where the Ferry Network terminates. They will always be referenced by at least one Ferry Link.
The road and path networks are connected to the ferry network through the Ferry Terminal feature, which acts as a network connection feature. The Ferry Terminal is a logical connection and therefore no geometry is supplied. In addition to connecting the networks together, the Ferry Terminal feature will also provide the terminal name and the three-letter NaPTAN code used by the Government to identify terminals uniquely.
A Road Junction holds information about junction names and numbers. The feature will reference all the Road Nodes which correspond to the junction the feature is representing. Multiple Road Junction features could reference a Road Node. In the current release, the Road Junction feature will only identify Numbered Motorway Junctions.
A Turn Restriction is a restriction based upon a vehicle manoeuvre. The types of restriction include a prohibitive driving instruction, a mandatory driving instruction and implicit restrictions. Prohibited instructions are indicated by road signs within a red circle; examples include No U-turns, No Right Turn and No Left Turn. These can include exceptions to the instruction and are typically elements like Except for Buses. Mandatory driving instructions are indicated by road signs within a blue circle or are painted on the roadway; examples include Turn Right and Ahead Only. Implicit restrictions occur where a turn is not signed as prohibited but would not be a normal manoeuvre, for example, where a road splits around a traffic island or at complex junctions where additional geometry has been captured to reflect the traffic flow. These are not differentiated from actual signed restrictions.
Hazards are locations which are hazardous and where caution should be taken to ensure safe travel. Hazards are usually signed using a warning sign. Hazards include Fords and Dangerous Bends.
Maintenance provides information about whether a path is maintained at public expense by a national or local highway authority, by a road authority or is maintained by another responsible organisation (i.e., not maintained at public expense). If a path is prospectively maintainable at public expense, then this is not currently maintained by a road or highway authority, but the responsible organisation has started the process for a highway or road authority to become responsible for the maintenance of the street at public expense.
Maintenance responsibility is not an indication of ownership.
Structures are the location of key built features that relate to the highway network. The types of features provided include bridges; barriers which can control, obstruct or prevent passage or access; tunnels, and equipment which would control the flow of traffic.
Reinstatement defines the standard to which the highway must be restored to, following opening due to works in the highway, as defined in the New Roads and Street Works Act Specification for the Reinstatement of Openings in Highways in England and Walesand the New Roads and Street Works Act 1991 Specification for the Reinstatement of Openings in Roads in Scotland.
An Access Restriction is a feature where access to a road or area by vehicles can be legally prohibited. Prohibited access restrictions are indicated by regulatory signs with a red circle or a no entry sign. In addition, access could be limited for use by particular classes of vehicle; these are indicated by regulatory signs with a blue circle. Access restrictions may also include exemptions to the restriction. The Access Restriction feature type comprises these types of restrictions.
A Ferry Link is a line segment that connects the road network and path networks across bodies of water. The link can represent the route a ferry may take between terminals; otherwise, the link will be a straight line between two terminals. In addition to connectivity information, a Ferry Link also provides data on who operates the service and if the service is limited to pedestrians. A Ferry Link will only be captured where both terminals are within Great Britain and where there is a timetabled service available to the public.
Restrictions For Vehicles are restrictions that apply to the physical characteristics of vehicles. These are required to protect structures such as bridges and tunnels from damage, or to restrict/prohibit use by vehicles that exceed dimensions, usually for physical reasons. In addition, Restrictions For Vehicles includes exemption to the restriction when specific use conditions apply (for example, loading and unloading). The restrictions include:
Maximum Height
Maximum Width
Maximum Length
Maximum Weight
Height, width, length and weight restrictions may be defined using either regulatory signs or warning signs. By default, the restriction is always provided in the metric unit, and the imperial measure will be provided where it is signed.
When a customer receives an order from the OS Data Hub, the product will be packaged with the following elements:
The data folder will contain the GML, Geopackage or Vector tiles files which make up the ordered product. The data folder will have been compressed to data.zip to enable a single download of the product. Once this has been downloaded, the data.zip file will contain all the data files which make up the ordered product and these files will have been compressed using gzip.
For GML, the doc folder will contain a summary.gml file which will contain specific information about the customer order, including:
The order number
Query extent polygon(s) of the order
The order type: Full supply or COU
For COU orders, the change-since date
The doc folder will have been compressed to doc.zip to enable a single download of the associated documents.
The Geopackage and Vector Tiles formats will have the same folder structure but will be available for GB coverage only so will not contain COU files.
The resources folder will contain the product’s Feature Validation Data Set (FVDS), and a lookup table to the OS Open Roads product. For further information on these resources, please refer to the Feature validation data set, and OS Open Roads lookup table sections within this document. The folder will have been compressed to resource.zip to enable a single download of the resources; within the zipped folder, the contents will have been compressed.
When a partner receives an order from the OS Data Hub, the product will be packaged as follows:
The data folder will contain the CSV (for Average Speed product) or shapefile (for Speed Limits product) which make up the ordered product. The data folder will have been compressed to either hnavsp_csv_gb.zip (for Average Speed) or hnsplm_shp_gb.zip (for Speed Limits) to enable a single download of the product.
Once this has been downloaded, the zip file will contain the corresponding CSV (Highways_AverageSpeed_GB.csv) or shapefiles (Highways_SpeedLimits_GB.shp) which make up the ordered product, and these files will have been compressed using zip.
A text file named Readme.txt will contain notes on the product supply and release information.
Highway Dedications provide an indication of the type of user who has access to that particular section of the Highway. Highway Dedications may reference public rights of way but are not a definitive record of such.
Every section of geometry supplied by a local highway authority will have a type of dedication associated, in line with the Highways Act 1980 and the Countryside and Rights of Way Act 2000, which determine the highway user access.
Average Speed is the detailed historical speed information collected by in-vehicle telematics devices that collect data for all major roads. The Average Speed information is based on a year’s worth of collected data and is given for six distinct times of each day and for both directions of a road link. The Average Speed is provided in kilometres per hour (km/h) for each road link.
The file naming for the OS MasterMap Highways Network GML will be constructed as Highways_ProductName_FeatureType_SupplyType_NullorDelete_volumenumber.gml.gz, where:
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 or COU.
NullorDelete 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_RoadsAndRAM_AccessRestriction_Full_001.gml.gz
Highways_Paths_Maintenance_Full_001.gml.gz
Highways_Roads_RoadNode_COU_001.gml.gz
Highways_Roads_RoadNode_COU_Delete_001.gml.gz
Highways_RoadsAndRAM_RoadLink_COU_001.gml.gz
Highways_RoadsAndRAM_RoadLink_COU_Delete_001.gml.gz
Highways_Paths_PathLink_COU_001.gml.gz
Highways_Paths_PathLink_COU_Delete_001.gml.gz
The file naming for the OS MasterMap Highways Network Geopackage will be constructed as OSMasterMapHighwaysNetworkProductName_gb.gpkg
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
OSMasterMapHighwaysNetworkRoad_gb.mbtiles
OSMasterMapHighwaysNetworkPath_gb.mbtiles
OS MasterMap Highways Network with Routing and Asset Management Information and Average Speed is supplied within a zip file with the following name: hnavsp_csv_gb.zip. Within the zip file, you will find the CSV file which will contain all records and will have the following name: Highways_AverageSpeed_GB.csv.
OS MasterMap Highways Network with Routing and Asset Management Information and Speed Limits is supplied within a zip file with the following name: hnsplm_shp_gb.zip. Within the zip file, you will find the shapefile which will contain all records and will have the following named file extensions:
Highways_SpeedLimits_GB.shp
Highways_SpeedLimits_GB.prj
Highways_SpeedLimits_GB.qpj
Highways_SpeedLimits_GB.dbf
Highways_SpeedLimits_GB.shx
All products will cover Great Britain.
OS MasterMap Highways Network core 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 if 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 Volume feature count.
OS Open Roads is part of Ordnance Survey’s open data portfolio and is a structured road network which has been generalised to 1:15 000 scale. The OS Open Roads lookup table provides the ID of the OS MasterMap Highways Network RoadLink feature and the ID of the feature which represents the same feature in the OS Open Roads product which could be either a RoadLink or a RoadNode. The lookup table will enable a customer to share information they have calculated and pinned to the OS MasterMap Highways Network easily through the OS Open Roads product. Not all RoadLink IDs from OS MasterMap Highways Network are included in the lookup table, particularly where the RoadLinks are shorter than 20m.
The lookup table has been provided as a comma-separated value (.csv) file so the attributes are separated by a comma. Each row will be terminated by Carriage Return / Line Feed, and where an attribute has no value in a record, two commas will be placed together in the record (one for the end of the previous attribute and one for the end of the null attribute). The file will be supplied with headers, and the information is detailed in the following table.
The file will be supplied with all orders of OS MasterMap Highways Network – Roads or OS MasterMap Highways Network – Routing and Asset Management Information and will be a national set, including with area of interest (AOI) orders. The lookup table is updated every six months, aligned to when OS Open Roads is released. During this period, some of the OS MasterMap Highways Network RoadLink IDs could change, be removed from the product or have new IDs inserted which will not be represented in the lookup table because the OS Open Roads product has not been updated to reflect this change. The version of OS MasterMap Highways Network with which the OS Open Roads lookup table is aligned can be identified in the file name.
The file is named OSOpenRoadLookUpTable_YYYY_MM.csv, where YYYY is the four-digit year and MM is the two-digit month (for example, OSOpenRoadLookUpTable_2017_09.csv).
When OSOpenRoads_RoadLinkIdentifier
is null, OSOpenRoads_RoadNodeIdentifier
cannot be null.
When OSOpenRoads_RoadNodeIdentifier
is null, OSOpenRoads_RoadLinkIdentifier
cannot be null.
The ID of the OS MasterMap Highways Network RoadLink feature being represented in OS Open Roads.
Size: 20
Multiplicity: [1]
The RoadLink identifier in OS Open Roads that the Highways feature has been generalised to.
Size: 38
Multiplicity: [0..1]
The RoadNode identifier in OS Open Roads which the Highways feature has been generalised to (for example, a collapsed roundabout).
Size: 38
Multiplicity: [0..1]
Special Designations are statutory and advisory designations that can be applied to protect a highway when street works are to be undertaken. Special Designations exist to reduce the bureaucracy involved in managing street works, with an emphasis on minimising delay and inconvenience to road users, whilst protecting the integrity of the street and any apparatus on it.
The Speed Limits feature identifies the speed limit for each stretch of road in Great Britain and is based on road traffic signs. The speed limit is provided in miles per hour (mph).
A feature validation data set (FVDS) reports on all the data it expects to find in the customer’s holding after the application of the supply. It does not identify what is contained in the supply if the order is not full supply. This enables a customer to validate that the data holding contains the correct set of features after loading the data with which it was supplied. All orders of the OS MasterMap Highways Network products will be supplied with a FVDS.
A FVDS is divided into files on a non-geographic basis, and each FVDS will contain up to 4 million rows in a single volume. Where a file will exceed 4 million rows, a new FVDS volume will be created. The FVDS is a comma-separated value (.csv) file that provides the ID, version date and feature type of every feature that should exist in the current data holding; the fields are separated by a comma. Each row will be terminated by Carriage Return / Line Feed, and where a field has no value in a record, two commas will be placed together in the record (one for the end of the previous field and one for the end of the null field). The FVDS will not contain any header information, but the following table identifies the different columns within the file. Each file is compressed using gzip.
The ID (gml:id) of the OS MasterMap Highways Network feature.
The 'beginLifespanVersion' attribute of the feature. This is the date when this feature came into existence, and it will be formatted as follows: YYYY-MM-DD. For example, 2016-06-12.
A textual description of the feature type that the record refers to.
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
This release note provides information about the September 2024 release of OS MasterMap Highways Network.
The following information relates to the currency of the source data used in the creation of this release of OS MasterMap Highways Network:
Data source | Date |
---|---|
Roads’ feature | Count |
---|---|
In the September 2024 release of OS MasterMap Highways Network:
There are 5 instances of overlapping road links.
There are 169 instances of overlapping path links.
There are 30 instances where a road link and a path link overlap, representing the same real-world feature.
There are 203 road links disconnected from main network or not properly connected at a node; these are not on major parts of the network.
There are 3 road links which are less than 1m in length.
There are 290 connecting links which are less than 1m in length.
There is 1 path link which is less than 1m in length.
There are 10 features in the Street table which have a street type of either Designated Street Name or Officially Described Street and have no associated maintenance record.
There are 0 instances of connecting nodes referencing a motorway.
The Trans-European Transport (TEN-T) network forms a set of road, rail, air and water transport networks spanning the European Union. As a result of the UK withdrawing from the European Union, the UK is no longer a part of the TEN-T network; therefore, the TEN-T lookup table has been withdrawn as of October 2023.
The next release of OS MasterMap Highways Network is scheduled for October 2024.
The OS MasterMap Highways Network products are only being supplied as non-geographic chunks, so the data will be supplied in volumes based on a feature count. The following table identifies the volume feature count used for each volume per feature type (maximum number of features per GML file):
Feature type | Volume feature count |
---|---|
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 formats are compressed into a regular zip file (.ZIP).
OS MasterMap Highways Network – RAMI is supplied in two formats: Geography Markup Language (GML 3.2.1) and Geopackage. All formats are compressed into a regular zip file (.ZIP).
OS MasterMap Highways Network with Routing and Asset Management Information and Average Speed is available in comma-separated value (CSV) file format only. The CSV file will be supplied with headers. The data is provided zipped as single file (.zip). Data is provided as full supply only and is refreshed annually (in May).
OS MasterMap Highways Network with Routing and Asset Management Information and Speed Limits is available in shapefile format only. The data is provided zipped as single file (.zip). Data is provided as full supply only and is refreshed quarterly (in April, July, October and January).
OS MasterMap Highways Network core products (Roads, Routing and Asset Management Information, and Paths) are available to PSGA, commercial customers and partners through the . 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 GB Set. The products are available as a download for all customers, and DVD for customers ordering a Managed GB Set.
OS MasterMap Highways Network with Routing and Asset Management Information and Average Speed data is supplied as download only. OS MasterMap Highways Network with Routing and Asset Management Information and Speed Limits data is also supplied as download only. Both speed products are available for partners only and can be ordered from the . New OS MasterMap Highways Network with Speed contracts cannot be entered into after 29th March 2023.
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 .
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 . 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.
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.
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 .
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
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:
Paths’ feature | Count |
---|---|
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 .
Product name | Suggested application |
---|
GeoPlace Streets Data
06 August 2024
Improvement Service Streets Data
05 August 2024
OS Road, Path, and Routing Content
06 August 2024
AccessRestriction
35 170
FerryLink
99
FerryNode
128
FerryTerminal
128
Hazard
41 636
HighwayDedication
3 583 849
Maintenance
1 314 311
Reinstatement
1 528 181
RestrictionForVehicles
12 044
Road
851 148
RoadLink
8 479 240
RoadNode
7 513 293
RoadJunction
6 823
SpecialDesignation
778 320
Street
1 481 716
Structure
1 371 324
TurnRestriction
1 044 930
ConnectingLink
1 992 644
ConnectingNode
1 850 506
FerryLink
87
FerryNode
163
FerryTerminal
163
HighwayDedication
400 965
Maintenance
203 978
Path
25 302
PathLink
3 267 538
PathNode
3 868 931
Reinstatement
209 414
SpecialDesignation
12 656
Street
253 927
Access Restrictions
66 000
Connecting Link
118 000
Connecting Node
138 000
Ferry Link
108 000
Ferry Node
126 000
Ferry Terminal
136 000
Hazards
94 000
Maintenance
82 000
Path
138 000
Path Link
72 000
Path Node
126 000
Reinstatement
120 000
Restrictions For Vehicles
74 000
Road
88 000
Road Link
46 000
Road Node
120 000
Special Designations
60 000
Street
36 000
Structures
104 000
Turn Restrictions
114 000
OS MasterMap Highways Network – Roads |
|
OS MasterMap Highways Network – Routing and Asset Management Information (RAMI) |
|
OS MasterMap Highways Network – Paths |
|
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.
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.
Query the Streets table using this string:
Special designations contains references to which streets are gritted.
This information can be displayed against either the street geometry or road link.
Understanding which is the best route to use in winter avoiding untreated roads where possible
Emervency services
Logistics
Roads Specification
Roadlink
Street
StreetNetworkRef
RAMI Specification
SpecialDesingation_Area
SpecialDesingation_Line
SpecialDesingation_Point
SpecialDesingation_NoGeom
Translation software is required to convert data from GML into chosen format. FME workbenches are available on GitHub to help with this.
Data storage – once translated the data will need to be stored in a format compatible with your systems, this may be on your file system as a shape file, geopackage or tab file or in a database.
GIS or web application to manipulate and display your results.
Information on Gritting routes is held in the Special Designation tables. This can be viewed with a simple query for example:
However as Special Designation is split into 4 tables depending on geometry type. The results can be merged into 1 table by querying all 4 with UNION ALL and dropping the geometry from the query output.
If you are working with a large data set it may be easier to create a new table of the results. (CREATE TABLE AS…)
The results can be linked using USRN to the Street table and use the geometry to display.
However you may want to add these to RoadLink as this includes classifications as well as road name and number.
This can be achieved by linking the USRN using the StreetNetworkRef table containing TOIDS:
Use the TOID to then join the data to RoadLink, the example limits the information returned:
The output can then be displayed on a map or used as part of routable network to add a priority to roads that have been treated.
When FME writes to some databases it writes the geometry as geometry and not point, line or area.
This creates a problem for some software reading the metadata as it does not fully understand the data type.
This can be resolved by cleaning the metadata table – In PostGIS use: SELECT Populate_Geometry_Columns()
Or by pre-creating the table and in the FME writer set table handling to either ‘Use Existing’ or ‘Create If Needed’.
An SQL script can be used within FME to create the table if necessary
OS MasterMap Highways contains the information needed to build network data sets taking into consideration the features that control where we can drive such as one-way streets, no entry etc. The data can be used to create routes for emergency response, refuse collection or delivering goods. Adding the Path data set extends the network capabilities allowing you to generate walking routes and look at access to services such as schools and health practices.
There are a number of options for use in routing and some systems will have this built in. The most popular across the Public Sector are:
RouteFinder – Produced by a 3rd party to provide a routing engine for MapInfo Pro. Has a translator which supports Highways.
Network Analyst – The beta version in ArcGIS Pro provides support for Highways.
pgRouting – An open-source routing extension to PostGreSQL/PostGIS. Results can be displayed in any software that can supports the database however QGIS has tools for this.
CadCorp MapModeller – Has a built-in routing engine with support for Highways.
Emergency Service command and dispatch
Routes to school
Public transport planning
Optimising waste collection
Service reviews and optimisation
There are a number of options for use in routing and some systems will have this built it. The most popular across the Public Sector are:
RouteFinder – Produced by a 3rd party to provide a routing engine for MapInfo Pro. Has a translator which supports Highways.
Network Analyst – The beta version in ArcGIS Pro provides support for Highways.
pgRouting – An open-source routing extension to PostGreSQL/PostGIS. Results can be displayed in any software that can supports the database however QGIS has tools for this.
CadCorp MapModeller – Has a built-in routing engine with support for Highways.
Data
RAMI Specification
Roadlink
Roadnode
TurnRestrictions
AccessRestrictions
FerryLink
FerryNode
Hazards
Structures
And to go one step further:
Path Specification
PathLink
PathNode
ConnectingLink
ConnectingNode
Software
Translation software is required to convert data from GML into your chosen format. FME workbenches are available on GitHub to help with this.
Data storage – once translated the data will need to be stored in a format compatible with your systems, this may be on your file system as a shape file, geopackage or tab file or in a database.
Routing application to perform the routing analysis and display the results in a meaningful way.
Using your preferred method translate the GML, this will also depend on the routing application used, some have their own translators.
Build a routable network – your software will have tools to do this for incorporating the restrictions etc. For pgRouting a useful guide can be found here - https://github.com/mixedbredie/highways-for-pgrouting.
Add additional information to your network such as road speed.
You can enhance this output even further with the addition of PathLinks to make a walking network. Add these to the RoadLinks to create a new data set and then use the same steps to create a network.
Maintenance, Reinstatement and Special Designation can have different geometry (point, line or area) or no geometry. In a non-spatial database this is not a problem and they can easily be merged into one. A spatial database will not allow mixed geometry types. It is suggested to create a new table, dropping the geometry. Link to geometry can then be preserved if required.
RAMI Specification
Maintenance
Reinstatement
Special Designation
Translation software is required to convert data from GML into chosen format. FME workbenches are available on GitHub to help with this.
Data storage – once translated the data will need to be stored in a format compatible with your systems, this may be on your file system as a shape file, geopackage or tab file or in a database.
GIS or web application to manipulate and display your results.
Create table statement with UNION ALL:
RoadLine – includes name, number and alternative name
Road – includes designated name and who has designated it
Street – designated name, descriptor and local name
Street contains designated name given by name and numbering authority. Where matched this will be in the name field on the road link. Roadlink name comes from name plate from survey this will be alternative on matched streets and name on unmatched.
Adding street names to mapping
Directions for routing
Gazetter searching and identifying the correct street
Roads Specification
Roadlink
Road
Street
Translation software is required to convert data from GML into chosen format. FME workbenches are available on GitHub to help with this.
Data storage – once translated the data will need to be stored in a format compatible with your systems, this may be on your file system as a shape file, geopackage or tab file or in a database.
GIS or web application to manipulate and display your results.
Local name contains other names the authority may know a street by.
The GML and may contain multiple values for each e.g.
Note a language field is also present to indicate the language of the name, e.g. English, Welsh or Gallic. These can either be held as one or split into multiple fields.
Once translated the road names can be added to either roadlink or street geometry using the labelling tools within your chosen software.
You may want to combine names across tables, for instance, to display the local name with the road name on the roadlink There are a number of ways to do this:
Construct are query in your labelling tool.
Append local name from street to roadlink.
Create a new table of roadlinks with the columns containing the labels.
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.
OS MasterMap Highways contains USRN as a unique reference for each street. This is really important as this provides a better link to addressing than the TOID information in the AddressBase Premium cross-reference table. This also gives more accurate results to users planning and using services by allowing them to link more effectively to a road. This improves a user's ability to identify properties, for use in routing; planning services such as waste management; calculating routes to school; reviewing service location and provision; identifying those affected by street works.
Identify delivery/collection addresses
Optimising waste collection
Metering
Service review and optimisation
A: AddressBase will give you a basic answer, but OSMM Highways can tell you much more… By linking across the relational mode using the unique keys in the data you can link the Roadlink geometry to AddressBase data. This will give a more reliable match than using the Cross Reference table in AddressBase as it is based upon gazetteer data.
TOID | USRN |
---|---|
Roads Specification
Roadlink
RoadLink_FormsPartof *
Roadlink TOID
And to go one step further:
Road
Street
* = SQL wildcard. This will display all columns in the data in the query result. As an alternative you can list only the columns you need separated by a comma e.g. column1, column2, column3….
Translation software is required to convert data from GML into your chosen format. FME workbenches are available on GitHub to help with this.
Data storage – once translated the data will need to be stored in a format compatible with your systems, this may be on your file system as a shape file, geopackage or tab file or in a database.
GIS or web application to manipulate and display your results.
Using your preferred method translate the GML for Roadlink, Road and Street into a format of your choosing.
To join the RoadLink geometry to addresses in AddressBase the USRN* can be used as a cross-reference. In the technical specification the USRN of the Street the RoadLink forms part is held in the RoadLink table. However, some translators will split this out into a separate table to avoid duplication into a RoadLink_FormsPartOf.
Either in your database or GIS query select the RoadLink you want to find the addresses for. In the example I want to select all properties along the A3026
Next is to link to RoadLink_FormsPartOF on TOID in both tables.
This will return a list or RoadLinks with a reference to both the Street and Road it forms part of. As the USRN is a reference to the Street we can exclude Road from our query. In the GML formsPartOf includes these references, some translators may join these in one field or create a separate column.
The final step is to link to either AddressBase Plus or Premium using the USRN. (AddressBase does not contain the USRN).
* USRN not currently populated in Scotland
Remember…
USRN in AddressBase is an integer
To remain INSPIRE compliant, OSMM Highways needs to have the USRN integer value prefixed by ‘USRN’
Solution:
Create a lookup table to combine values from AddressBase with a character field with USRN added or
Concatenate the 2 fields within your SQL query something like CONCAT(‘usrn’, usrn)
Completed SQL query:
Example output:
With an output similar to this depending on which columns you choose to return.
You can enhance this output even further by considering Road and Street features. Road feature – this represents a collection of RoadLinks that share the same name or classification number and can be used to create a list of all RoadLink TOIDs for a feature and then linked to a USRN. Street feature - Additional information on the street is contained in the Street record and can be linked to the RoadLink using the RoadLink_FormsPartOf reference.
Additional information includes:
Street Type: The type of Gazetteer record for which the USRN relates
Operational State: indicates whether the Street is proposed, under construction, open, or closed (permanently or temporarily)
Responsible Authority: reference to the authority who performs an administrative function – notably naming and numbering
Local name: Unofficial local name associated to the highway
Identify which features change and how that affects other information related to it.
Identify physical change to the road network.
Identify roads under construction and affects on service provision.
Common attribute is across all features
Gives the reason why a feature has changed using these values
Code | Description |
---|---|
Back up your data.
Use feature validation data set (FVDS) to check which features are affected and how (TOID value and UPDATE, INSERT or DELETION).
Connect data to either TOID or USRN as this are persistent with a finite life cycle.
Further useful information:
BeginLifespanVersion – gives date of when the object was inserted or changed in the data
Validfrom – data when the custodian entered the data into LSG (Street records)
TOIDS are persistent across both products and have not changed
Data linked to ITN using TOID should link to Highways
FVDS can be used to identify where a reference may have changed
Operational State – indicates the construction status of the street
Streets – all values are permitted, default is open
RoadLink – Operational status defaults to open, although may occasionally be under construction
Special designations table – provides additional information and can be linked directly to Street by USRN.
Code | Description |
---|---|
Relates to tables of restrictions and other information in RoadLink and Road tables
Relates maintenance and reinstatement in streets table
* USRN not currently populated in Scotland
New
New feature has been added
Modified Geometry
The geometry of the feature has been altered
Modified Attributes
One or more attribute properties have been altered
Modified Geometry and Attributes
Geometry and attribution properties have been altered
Prospective
Plans have been submitted for development but construction has not commenced.
Under Construction
Construction has commenced but the road cannot be used.
Open
Open
Temporarily Closed
The way has been temporarily closed for a specified reason under Road Traffic Regulation Act 1984 Section 14 1(b):
• Streetworks
• likelihood of danger to public
• Litter clearing or cleaning (duty imposed by section 89(1)(a) or (2) of the Environmental Protection Act 1990 (litter clearing and cleaning) to be discharged)
Note: The operationalState shall only be set to Temporarily Closed when the duration of the closure is intended to last more than 4 weeks.
Permanently Closed
A Street that has been permanently blocked up according to a Stopping Up Order
Constraint: If the Street operationalState = Permanently Closed then the endLifespanVersion shall be set.
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
The following OS MasterMap Highways Network core principle pages provide an overview of MasterMap Highways Network products. They cover core elements of the product such as product supply, coverage, file naming, and feature validation amongst other topics.
These pages should be used in conjunction with the detailed technical specifications found under the top-level product pages for each product.
This playbook provides simple ways to tackle common questions about OS MasterMap Highways
Focus on the core job that you ultimately trying to get done.
Consider what other products will help to meet your goals
Don’t overcomplicate the task.
Start by doing a data backup.
Translate the data using our FME workbenches.
Follow the steps outline in the scenarios below to success.
The OS MasterMap Highways playbook is broken down into a series of data scenarios that might be used in data projects and step-by-step instructions on how to solve these challenges. These are:
Predefined stylesheets for OS MasterMap Highways Network are available for download from the Ordnance Survey OS-MasterMap-Highways-Network-stylesheets GitHub repository here.
To download a ZIP containing all stylesheets, navigate to Code > Download ZIP.