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 Open Linked Identifiers product
This release note provides information about the October 2024 release of OS Open Linked Identifiers.
This release note provides information about the August 2024 release of OS Open Linked Identifiers.
This release note provides information about the July 2024 release of OS Open Linked Identifiers.
This release note provides information about the May 2024 release of OS Open Linked Identifiers.
This release note provides information about the April 2024 release of OS Open Linked Identifiers.
This release note provides information about the February 2024 release of OS Open Linked Identifiers.
This release note provides information about the April 2024 release (Epoch 34) of OS Open Linked Identifiers.
This release note provides information about the July 2024 release (Epoch 36) of OS Open Linked Identifiers.
This release note provides information about the August 2024 release (Epoch 37) of OS Open Linked Identifiers.
This release note provides information about the October 2024 release (Epoch 38) of OS Open Linked Identifiers.
This release note provides information about the May 2024 release (Epoch 35) of OS Open Linked Identifiers.
Each of the relationships provided have their own unique use cases depending on the features that are being related to each other. The following section provides suggested use cases for each relationship.
Relating the RoadLink feature to a TopographicArea enables the visualisation of data collected and linked to RoadLinks (pollution counts, accidents, traffic speed) and visualises it by colour coding the relevant road surface area. Additionally, it can be useful for analysis enabling the road surface area to be calculated for a given road section.
Having links between Road with TopographicArea allows for the full extent of the road to be joined to all the TopographicArea features that represent it. This can be useful to calculate the full surface area for that named road and for displaying data linked to the road name by colour coding the road surface area.
Being able to relate a Street USRN to a TopographicArea TOID is useful for calculating the total road surface area for a given USRN. It can also be useful to display data related to the USRN such as maintenance history and schedule.
Having a link from the BLPU UPRN to a TopographicArea TOID is useful for calculating the area of the building footprint related to an address. It can also be useful to colour code building TopographicAreas for displaying related data for that address, such as council tax band.
Being able to relate each section of road to its road name is very useful for validation and can also be useful for aggregating data collected at the RoadLink level for sharing at the Road name level.
The RoadLink TOID to Street USRN is useful for aggregating data collected at a RoadLink level to a USRN for reporting. It is also useful for validating that the USRN is the one you are expecting.
Knowing which RoadLink accesses a property UPRN is useful during conveyancing to determine if the road is private or not, and if it is carrying any maintenance liabilities. It is also useful to be able to relate
a RoadLink to all the property UPRNs accessed by it in case you need to notify them about upcoming roadworks.
The primary use case for relating a Road TOID to Street USRN is to validate that the USRN you have is related to the road name you’re expecting. It’s also useful for identifying where a single named road is
maintained by two different administration areas.
Roadworks are often scheduled using the USRN. Being able to relate a USRN to easily identify the UPRN addresses that are accessed by the road, is useful to aid notifying residents of possible upcoming disruption.
These two tables have a very specific use case which is to enable data that is published against an OS MasterMap Highways RoadLink TOID (such as pollution counts, traffic accidents or average vehicle speed )to be visualised with the OS Open Roads product. This enables public data to be visualised for free.
This getting started guide provides instructions for using OS Open Linked Identifiers in different software applications. Users with limited technical knowledge will be able to follow this guide.
OS Open Linked Identifiers is a dataset containing the authoritative relationships between Unique Property Reference Numbers (UPRNs), Unique Street Reference Numbers (USRNs) and Topographic Identifiers (TOIDs), and metadata. Identifiers are labels that are assigned to representations in a dataset. They are at the heart of how data can be effectively published, retrieved, reused and linked.
OS Open Linked Identifiers enables you to connect the variety of relationships between UPRN, USRNs and TOIDs. These are synchronised with comprehensive premium products to provide you with the most up-to- date feature metadata sourced from AddressBase, OS MasterMap Highways Network and OS MasterMap Topography Layer. The more an identifier is used in other datasets, the more valuable the primary data becomes.
For example, OS Open Identifiers enables visualisation of data linked to the Highways RoadLink and Open Roads products. By sharing the road link mapping between Highways and Open Roads it enables data that has been collected and shared against the Highways’ premium products to be visualised in the open geometry.
Identifiers are crucial to the process of sharing information and linking together datasets, allowing them to fit into many workflows in many different types of workplace to provide powerful insights and support analytics.
This release note provides information about the February 2024 release (Epoch 33) of OS Open Linked Identifiers.
BLPU_UPRN_ROADLINK_TOID_9
40 666 419
BLPU_UPRN_STREET_USRN_11
41 392 052
BLPU_UPRN_TOPOGRAPHICAREA_TOID_5
40 701 908
ORROADLINK_GUID_ROADLINK_TOID_12
6 637 746
ORROADNODE_GUID_ROADLINK_TOID_13
40 611
ROAD_TOID_STREET_USRN_10
1 295 331
ROAD_TOID_TOPOGRAPHICAREA_TOID_3
6 189 380
ROADLINK_TOID_ROAD_TOID_7
5 971 551
ROADLINK_TOID_STREET_USRN_8
8 860 815
ROADLINK_TOID_TOPOGRAPHICAREA_TOID_2
14 469 124
STREET_USRN_TOPOGRAPHICAREA_TOID_4
9 392 130
Grand total
175 617 067
BLPU_UPRN_ROADLINK_TOID_9
40796598
BLPU_UPRN_STREET_USRN_11
41482142
BLPU_UPRN_TOPOGRAPHICAREA_TOID_5
40779000
ORROADLINK_GUID_ROADLINK_TOID_12
6667008
ORROADNODE_GUID_ROADLINK_TOID_13
40730
ROAD_TOID_STREET_USRN_10
1296996
ROAD_TOID_TOPOGRAPHICAREA_TOID_3
6194817
ROADLINK_TOID_ROAD_TOID_7
5975893
ROADLINK_TOID_STREET_USRN_8
8874418
ROADLINK_TOID_TOPOGRAPHICAREA_TOID_2
14480760
STREET_USRN_TOPOGRAPHICAREA_TOID_4
9404398
Grand total
175992760
BLPU_UPRN_ROADLINK_TOID_9 | 40838338 |
BLPU_UPRN_STREET_USRN_11 | 41534792 |
BLPU_UPRN_TOPOGRAPHICAREA_TOID_5 | 40816748 |
ORROADLINK_GUID_ROADLINK_TOID_12 | 6653265 |
ORROADNODE_GUID_ROADLINK_TOID_13 | 40689 |
ROAD_TOID_STREET_USRN_10 | 1298037 |
ROAD_TOID_TOPOGRAPHICAREA_TOID_3 | 6202292 |
ROADLINK_TOID_ROAD_TOID_7 | 5981550 |
ROADLINK_TOID_STREET_USRN_8 | 8886997 |
ROADLINK_TOID_TOPOGRAPHICAREA_TOID_2 | 14499305 |
STREET_USRN_TOPOGRAPHICAREA_TOID_4 | 9414115 |
Grand total | 176166128 |
BLPU_UPRN_ROADLINK_TOID_9 | 40 875 768 |
BLPU_UPRN_STREET_USRN_11 | 41 574 039 |
BLPU_UPRN_TOPOGRAPHICAREA_TOID_5 | 40 869 800 |
ORROADLINK_GUID_ROADLINK_TOID_12 | 6 646 814 |
ORROADNODE_GUID_ROADLINK_TOID_13 | 40 669 |
ROAD_TOID_STREET_USRN_10 | 1 298 650 |
ROAD_TOID_TOPOGRAPHICAREA_TOID_3 | 6 205 588 |
ROADLINK_TOID_ROAD_TOID_7 | 5 982 926 |
ROADLINK_TOID_STREET_USRN_8 | 8 890 635 |
ROADLINK_TOID_TOPOGRAPHICAREA_TOID_2 | 14 505 999 |
STREET_USRN_TOPOGRAPHICAREA_TOID_4 | 9 419 815 |
Grand total | 176 310 703 |
Feature | Feature count |
BLPU_UPRN_ROADLINK_TOID_9 | 40 741 452 |
BLPU_UPRN_STREET_USRN_11 | 41 436 497 |
BLPU_UPRN_TOPOGRAPHICAREA_TOID_5 | 40 752 548 |
ORROADLINK_GUID_ROADLINK_TOID_12 | 6 671 677 |
ORROADNODE_GUID_ROADLINK_TOID_13 | 40 734 |
ROAD_TOID_STREET_USRN_10 | 1 295 855 |
ROAD_TOID_TOPOGRAPHICAREA_TOID_3 | 6 192 716 |
ROADLINK_TOID_ROAD_TOID_7 | 5 973 817 |
ROADLINK_TOID_STREET_USRN_8 | 8 866 593 |
ROADLINK_TOID_TOPOGRAPHICAREA_TOID_2 | 14 477 078 |
STREET_USRN_TOPOGRAPHICAREA_TOID_4 | 9 396 693 |
Grand total | 175 845 660 |
BLPU_UPRN_ROADLINK_TOID_9 | 40 666 653 |
BLPU_UPRN_STREET_USRN_11 | 41 337 627 |
BLPU_UPRN_TOPOGRAPHICAREA_TOID_5 | 40 660 436 |
ORROADLINK_GUID_ROADLINK_TOID_12 | 6 651 067 |
ORROADNODE_GUID_ROADLINK_TOID_13 | 40 646 |
ROAD_TOID_STREET_USRN_10 | 1 295 031 |
ROAD_TOID_TOPOGRAPHICAREA_TOID_3 | 6 180 118 |
ROADLINK_TOID_ROAD_TOID_7 | 5 958 510 |
ROADLINK_TOID_STREET_USRN_8 | 8 845 666 |
ROADLINK_TOID_TOPOGRAPHICAREA_TOID_2 | 14 443 931 |
STREET_USRN_TOPOGRAPHICAREA_TOID_4 | 9 383 803 |
Grand total | 175 463 488 |
This section provides the following information about each attribute of the CSV product:
The name of the attribute and what it is describing.
The nature of the attribute, for example a numeric value or a code list value.
Describes how many times this element is expected to be populated in the data. An attribute may be optional or mandatory; these are denoted by:
‘1’ – Mandatory - There must be a value.
‘0..1’ – Optional – If populated a maximum of one attribute will be returned. These values may be used in combination.
Unique identifier for the relationship. Made up of a concatenated string in the format: {Data Identifier 1}{Feature Identifier 1}{Data Identifier 2}{Feature Identifier 2}{CorrelationType Number}
Type: text
Multiplicity: [1]
The primary identifier of Source Dataset 1.
Type: text
Multiplicity: [1]
Version number of the primary identifier of Source Dataset 1. Where available, NULL otherwise.
Type: integer
Multiplicity: [0..1]
Version date of the primary identifier of Source Dataset 1. Where available, NULL otherwise.
Type: date time
Multiplicity: [0..1]
The primary identifier of Source Dataset 2.
Type: text
Multiplicity: [1]
Version number of the primary identifier of Source Dataset 2. Where available, NULL otherwise.
Type: integer
Multiplicity: [0..1]
Version date of the primary identifier of Source Dataset 2. Where available, NULL otherwise.
Type: date time
Multiplicity: [0..1]
Confidence value based on a comparison of feature dates between the two source features. Can be one of:
Version information is correct
Version information has potentially changed
Version information has changed
Type: text
Multiplicity: [1]
Notes: May be a constant value of the possible ones for certain relationships.
The OS Open Linked Identifier data package also contains Product Version Information files. These are contained inside each relationship zip package as JavaScript Object Notation (JSON) format.
JSON is an open-standard file and data interchange format that uses human-readable text to store and transmit data objects consisting of attribute-value pairs and array data types.
The general structure of the metadata JSON is detailed below:
The name of the Linked_ID CSV file
Type: text
Multiplicity: [1]
The product publication date.
Type: date
Format: YYYY/MM
Multiplicity: [1]
The Linked_ID Epoch Number that the JSON file refers to. (In the format “Epoch {number}”.)
Type: text
Multiplicity: [1]
Type: Object
Multiplicity: [1]
The product name of the source product for identifier 1.
Type: text
Multiplicity: [1]
The publication date of the source product for identifier 1.
Type: date
Format: YYYY/MM
Multiplicity: [1]
The epoch number of the source product for identifier 1. If provided, in the format “Epoch {number}”.
Type: text
Multiplicity: [0..1]
Notes: Not supplied if null value.
The feature type of the source for identifier 1. Can be one of:
BLPU
Road
RoadLink
Street
TopographicArea
Type: text
Multiplicity: [1]
The identifier type of the source for identifier 1. Can be one of:
GUID
TOID
UPRN
USRN
Type: text
Multiplicity: [1]
Type: Object
Multiplicity: [1]
The product name of the source product for identifier 2.
Type: text
Multiplicity: [1]
The publication date of the source product for identifier 2.
Type: date
Format: YYYY/MM
Multiplicity: [1]
The epoch number of the source product for identifier 2. If provided, in the format “Epoch {number}”.
Type: text
Multiplicity: [0..1]
Notes: Not supplied if null value.
The feature type of the source for identifier 2. Can be one of:
BLPU
Road
RoadLink
Street
TopographicArea
Type: text
Multiplicity: [1]
The identifier type of the source for identifier 2. Can be one of:
GUID
TOID
UPRN
USRN
Type: text
Multiplicity: [1]
An open dataset of cross-referenced identifiers between various OS data products.
This product is updated every six weeks.
OS Open Linked Identifiers provides authoritative relationship between Unique Property Reference Numbers (UPRNs), Unique Street Reference Numbers (USRNs), Topographic Object Identifiers (TOIDs) and metadata to enable reliable matching and for greater data connectivity.
OS Open Linked Identifiers is a dataset containing the authoritative relationships between UPRNs, USRNs and TOIDs.
Connecting addresses with road features enables more related data to be joined together which simplifies a number of valuable workflows. Linking these features to graphical elements of OS MasterMap products enables better visualisation of the data related to them.
Link data related to an address with its building footprint. Validate an address's UPRN with the name of the road that accesses it. Validate a street's USRN with the name of the road it relates to.
The relationships UPRN and USRN are provided by the bodies responsible for the identifier schemes, and these are spatially matched to OS MasterMap features by Ordnance Survey. This means you can have confidence that you're accessing an authoritative source of these relationships.
The relationships are taken from our Premium Download data products and have been made open so that everyone can access them from one trusted source.
The OS Open Linked Identifiers product provides the relationships between the following features found in OS MasterMap products (Note that Topographic Areas are limited to address and road features):
TopographicArea* (TOID): OS MasterMap Topographic Layer
RoadLink(TOID): OS MasterMap Highways Networks – Roads
Road(TOID): OS MasterMap Highways Networks – Roads
ORRoadLink/ORRoadNode(GUID): OS Open Roads
Street(USRN): OS MasterMap Highways Networks – Roads
BLPU(UPRN): AddressBase Premium
*restricted to address and road features.
Access: Download
Data theme: Multiple
Data structure: Vector - Identifiers
Coverage: Great Britain
Scale: 1:1 250 to 1:10 000
Format: CSV
Ordering area: All of Great Britain
OS Data Hub plan: Energy & Infrastructure Plan, OS OpenData Plan (FREE), Premium Plan, Public Sector Plan
Open Linked Identifiers includes the latest version information for all the respective features that are referred to. In some cases, this might be a different version of the feature than what was used to form the relationship. This means that in some cases the relationship might not still be valid. To help resolve this we’ve also included a confidence value, indicating if the feature has changed since the relationship was formed, which can be used to resolve errors.
Geometry is not included in OS Open Linked Identifiers. You can get the geometry you need from either OS Open UPRN, OS Open USRN or OS Open TOID.
OS Open Linked Identifiers does not contain UDPRN, as there is 3rd party IP associated with the UDPRN.
Access to this product is free through the OS Data Hub.
OS Open Identifiers Family Information – This page gives context and information about the OS Open Identifiers 'Family' of products, including explaining what identifiers are and introducing the OS identifiers (TOID, UPRN and USRN). We recommend referring to this page in combination with the Overview and Technical Specification documents for OS Open Linked Identifiers.
OS Open Linked Identifiers is part of the OS Open Identifiers 'Family' of products, which includes four OpenData products: OS Open Linked Identifiers, OS Open TOID, OS Open UPRN and OS Open USRN. The products within this family allow you to easily share information held against a range of identifiers and to link together information associated with these identifiers.
It is highly recommended that the Linked ID data be loaded into a database application for use. It is not possible to illustrate within this guide the loading of these datasets into every database application available. Therefore, users should familiarise themselves with the operations of both loading the data and then indexing it so that performance can be improved.
For the purposes of this guide, an example will be shown illustrating the loading of the Road_TOID_Street_USRN Linked ID CSV file into a PostgreSQL (Open Source) database.
In this example version 11 of PostgreSQL is being used. It is expected that a later release (version 12) should also behave in a similar manner. Pg_Admin 4 or any other free database manager can be used to carry out the procedures. Pg_Admin 4 is the database manager front-end application installed with PostgreSQL, and PostGIS for tables with geometry, will be used to illustrate the procedures.
It is assumed that the end user has already created a database within Postgres to hold other data. The other data held by the user will be held in different schemas. It is recommended that a new schema be created to hold the Linked ID data, especially if the user intends to use most or all the Linked IDs available.
In Pg_Admin right-click on Schemas under the database listing
Select ‘Create Schema’.
Give the schema a name in the Name box.
Click ‘Save’
The new schema now appears in the listing of schemas within the database.
The next procedure will show you how to create a table within the schema to hold the Linked ID data for the individual Linked ID that the user is seeking to load. The table will need to have columns created corresponding to the fields within the Liked ID .CSV file. The user will either need to use an advanced text editor (e.g. UltraEdit) to view the CSV data, or refer to the technical specification document to see what fields are contained within the Linked ID data, and the what are the data types within the fields. In this example, we will define all the fields within the Linked ID data as text fields.
Using UltraEdit Text editor, which can open very large CSV files, we can view the column headings within the CSV file. The example below shows the opening of the Road_Toid_street_USRN_10.CSV file, which is the example Linked ID file we will be using to illustrate the loading procedure in this guide.
We have identified the column headers and can now use a script like the one below which will carry out the table creation operation. This includes both dropping any pre-existing table of the same name, and then creating a table to hold the data.
Please note this code will need to be modified to account for the variables in the user's own environment, but the column names and data types will remain the same.
In Pg_Admin, under ‘Tools’, select ‘Query Tool’ to open a SQL query window
Copy and paste the code from a Text file (recommended) into the SQL window.
When satisfied, click the ‘run’ button to execute the query.
The query should now run, creating the table, and loading the data into the created table. A success message should appear when the query has run.
In Pg_Admin, under the LinkedIDs schema a new table should now be visible.
In this example the new table is called road_toid_street. We will now use the import data function within Pg_Admin_4 to load the data into the created table.
Right-Click on the road_toid_street table just created and select ‘import/export’.
In the window that appears, select the import/export to 'import'.
Select the filename of the CSV file which is being imported.
Set the encoding to UTF-8.
Set the header box to ‘Yes’ because we know that the CSV file contains header information.
Select the delimiter to comma.
Click ‘OK when finished. The data will now load into the created table.
Right-clicking on the road_toid_street table and viewing the top 100 rows shows a result similar to that shown below. This indicates that the Linked ID data for the Road_Toid_street_USRN_10.CSV has been successfully loaded into the database.
The data should now be indexed, which can be done by adding an index to one of the fields in the data or by adding OIDs as unique IDs to the data. This can be achieved by typing in a code string like the one shown below into the query window and then running the query.
Adding this new field will enable any joining and querying to be achieved much more quickly. Looking at the data table now, we can see that PostgreSQL has added a unique OID field to the data.
Other database applications will have similar methods for the creation and loading of data tables. The data is now ready for use and table-joins can now be made with the end user's own data held either within a database or outside the database in a GI application
This overview introduces OS Open Linked Identifiers & gives context for all users – highlighting key features, giving examples of potential uses, & listing details on file sizes, supply formats, etc.
OS Open Linked Identifiers is a dataset containing the authoritative relationships between Unique Property Reference Numbers (UPRNs), Unique Street Reference Numbers (USRNs) and Topographic Identifiers (TOIDs).
These relationships have been extracted from the AddressBase Premium and OS MasterMap Highways Networks products. The Product aims to provide all the valuable relationships between addresses, roads and OS MasterMap features.
The following diagram and table show all the feature types that we have included such as address records, building outlines, road surface area, road names, road sections and street records, and the relationships between them that we provide links for.
The product consists of 11 relationships as shown in the diagram above. Each relationship is available to download individually from the OS Data Hub. These relationships support a number of data processing workflows and specific use cases for each are listed in Uses of OS Open Linked Identifiers.
The product is supplied in the form of join tables in the CSV file format and is intended to be loaded into database products. Please see the OS Open Linked Identifiers - Getting Started Guide for details on how to import the join tables into a database.
Once the relationship table has been imported into a database it can be used to join two dataset tables each using different identifiers. For example, if you had data that listed properties which used the Unique Property Reference Number (UPRN) as its primary key, and you also had data related to the streets which used the Unique Street Reference Number (USRN), then you could join these data tables allowing you to lookup information about the street that a property is on. This is just an example for one of the eleven tables. Each table has specific use cases depending on the feature tables that are being linked.
These relationships have been extracted from our premium data products and provided in OS Open Linked Identifiers under open license to enable more public data to be linked together.
This is purely a data product which provides the identifiers being joined with version information to enable reliable data linking. There is no geometry provided in this product. Each relationship file provides full coverage for Great Britain. The product is intended for use with a database only as the lack of spatial information (spatial indexes) and large files make it unsuitable for use in GIS packages.
A UPRN is a unique numeric identifier for every addressable location in Great Britain. The identifier is critical for property related information and can be found throughout OS's AddressBase products. An addressable location may be any kind of building, residential or commercial, or it may be an object that might not have a ‘normal’ address – such as a bus shelter or an electricity substation. UPRNs provide these addressable locations with a consistent, persistent identifier never being reused.
A USRN is a unique and persistent identifier for every street, road, track, path, cycletrack or way in Great Britain. It can be found in the OS MasterMap Highways Network products and is also a key component in OS’s AddressBase suite of products.
A TOID is a unique identifier issued by Ordnance Survey, consisting of the letters ‘osgb’ and followed by up either thirteen or sixteen digits, associated with every feature in many of Ordnance Survey’s large-scale products. For this to be functional across all OS MasterMap products, this must never be altered or changed.
The TOID is based upon the Digital National Framework concept and the principles that underpin it.
The Correlation Method ID is a unique identifier for a specific relationship between the featureTypes. The generalised naming convention for each Correlation Method ID is:
{Feature Type 1}_{Identifier Scheme 1}_{Feature Type 2}_{Identifier Scheme 2}_{Correlation Method Number}
This means you can easily identify the feature tables and related identifier schemes which are being linked together by each relationship. The correlation method number is also unique to each relationship.
For example, the Correlation Method ID “RoadLink_TOID_TopographicArea_TOID_2” references:
Identifier 1:
Feature Type: RoadLink
Identifier scheme: TOID
Identifier 2:
Feature Type: TopographicArea
Identifier scheme: TOID
Correlation Method Number: 2
With each identifier we have provided associated version information to enable reliable linking to your data. This version information is extracted from the most recent release of the premium product the feature type has been extracted from.
A Confidence Value is assigned to each identifier pairing to indicate the reliability of the version information provided in this product in relation to the version of the features used to form the correlation in the original product. The Confidence Value is given for each relationship, which is defined as:
Knowing that the feature might have been updated since a relationship was formed helps identify where a relationship may no longer be valid.
| Feature Type | Identifier Type | Source Product | Description |
|---|---|---|---|
Please refer to the source product documentation for details of each feature that is being related.
Each feature uses a specific identifier scheme for its identifier. These are as follows:
Unique Property Reference Number (UPRN)
A UPRN is a unique numeric identifier for every address in Great Britain. The identifier is critical and can be found throughout OS's AddressBase products. It provides a complete and consistent
identifier throughout a property’s life cycle. This means the UPRN is assigned to an address at the earliest opportunity and is never reused, even after the property has been demolished.
Unique Street Reference Number (USRN)
A USRN is a unique and persistent identifier for every street, road, track, path, cycletrack or way in Great Britain and can be found in OS’s Highways Network products and is also a key component in OS’s AddressBase suite of products.
Topographic Identifier (TOID)
A TOID is a unique identifier, consisting of the letters ‘osgb’ and followed by either thirteen or sixteen digits, associated with every feature in many of Ordnance Survey’s large-scale products. No amends can be made to this code as it may no longer be functional with other OS MasterMap products.
The TOID is based on the Digital National Framework concept and the principles that underpinned it.
These identifiers contain no attribution or information, for example coordinate position. If you need this to visualise your data, we offer a family of Open Identifier products for you to download and freely use under Open Government Licence.
The following table lists each of the relationships provided and the premium product the relationship has been extracted from.
Please refer to the OS Open Linked Identifiers Technical Specification for details on how these relationships were extracted and how the original relationships were formed.
The Open Linked Identifier data product is supplied in Comma-Separated Value (CSV) format, which comes with Product Version Information files formatted as JavaScript Object Notation (JSON).
Upon downloading the data, you will receive zip files of the eleven Linked Identifier relationships. The generalised naming convention for each Relationship ID is:
{Data Identifier 1}_{Feature Identifier 1}_{Data Identifier 2}_{Feature Identifier 2}_{CorrelationType Number}
For example: BLPU_UPRN_RoadLink_TOID_9
Upon downloading the CSV data, you will have 11 zip packages for each relationship. Each zip package contains 4 files, for example BLPU_UPRN_RoadLink_TOID_9.zip extracts:
OS Open Linked Identifiers will be updated through a full supply on a six-weekly basis in line with AddressBase Premium. Each OS Open Linked Identifiers release will follow shortly after the corresponding AddressBase Premium release.
The product is released with full Great Britain coverage. As the product has been separated into individual zip files per relationship, each zip file size is dependent on the relationship it holds. The sizes range from a few hundred megabytes to 5-8 giga bytes. Please see the product listing on the OS Data Hub for accurate individual file sizes.
OS Open Linked Identifiers is aimed for use within database products only and consists of join tables that are supplied in the Comma Separated Variable (CSV) format. These files are not suitable for GIS packages as they are very large and do not contain any spatial information. This guide will cover the loading of an example linked ID CSV file into a typical database application.
Upon downloading the data, you will receive zip files of the 11 Linked Identifier relationships (see table below). The generalised naming convention for each Relationship ID is:
{Data Identifier 1}_{Feature Identifier 1}_{Data Identifier 2}_{Feature Identifier 2}_{CorrelationType Number}
For example: BLPU_UPRN_RoadLink_TOID_9
| Relationship IDs | Relationship |
|---|---|
It is up to the end user to choose which Linked ID they wish to use. For further information for the purpose of each join table, please refer to the OS Linked Identifiers Overview document. This will depend on which dataset they wish to link to elements within OS data. It is NOT recommended to attempt to open the uncompressed .CSV files in an application such as Microsoft Excel, as the application will simply either hang or not load the data at all.
This is also the case if the user tries to load the Linked IDs directly into a GI application. The GI application will quite likely hang because the Linked IDs are large and contain no spatial information (geometry) and will therefore not be spatially indexed.
Using these Linked Identifiers from within a database will allow the user to achieve end results such as shown below. The results will depend on which user data they wish to link, and which OS dataset is being linked.
The use of Linked Identifiers will also be made available through an API service which is not covered in this guide.
Within each ZIP file containing the Linked Identifier data in CSV format, there is a JSON file. This file contains important information providing the epoch or publication date of the differing datasets used to create the Linked Identifiers. This information can be used to ensure synchronicity between the Ordnance Survey datasets that are being linked.
The Open Linked Identifier data product is supplied in Comma-Separated Value (CSV) format, which comes with Product Version Information files formatted as JavaScript Object Notation (JSON).
Upon downloading the data you will receive zip files of the 11 Linked Identifier relationships. The generalised naming convention for each Relationship ID is:
{Data Identifier 1}_{Feature Identifier 1}_{Data Identifier 2}_{Feature Identifier 2}_{CorrelationType Number}
For example: BLPU_UPRN_RoadLink_TOID_9
| Relationship IDs | Relationship |
|---|---|
Upon downloading the CSV data, you will have 11 zip packages for each relationship. Each zip package contains four files, for example BLPU_UPRN_RoadLink_TOID_9.zip extracts:
This page aims to provide all the information to evaluate if the method of associating the respective identifiers is suitable for your needs. These identifier relationships have been extracted from existing premium products and are presented in a standalone table for easy and open access to the information. It describes which product the information was extracted from, what information was extracted and how the source product derived the original association between the identifiers.
This relationship is between the Unique Street Reference Number (USRN) of the Street features in OS MasterMap Highways Network and the TOID of the TopographicArea of the corresponding road surface area in OS MasterMap Topography Layer.
A USRN is a unique, persistent identifier for every street, assigned in the National Street Gazetteer (NSG) to any road, footway, path, cycle track, track or passageway that forms a highway. Where possible, the geometry of streets provided in the National Street Gazetteer is spatially matched to the geometry of OS RoadLinks to provide the additional attribution captured in the NSG against detailed OS geometry.
This relationship is extracted from the relatedRoadArea attribute on the matched RoadLink(s) within OS MasterMap Highways Network – Roads product following its release. This means that this relationship will not include all USRNs in OS MasterMap Highways Network, as Street features that have not been matched to an OS RoadLink will be omitted.
Where Street features have been successfully matched to OS RoadLinks, the Street features in OS MasterMap Highways Network are aggregate features composed of one or more RoadLinks. The relationship is determined by a line in a polygon intersection between the centre line geometry of matched RoadLink(s) and the topographic area polygon. The relationship is performed by Ordnance Survey.
The two source products used to extract this relationship are on different refresh cycles. OS MasterMap Highways Network is updated monthly, whereas OS MasterMap Topography Layer is updated every six weeks. Therefore, some of the version information in the product may have changed, meaning that the relationship is out of sync. A Confidence Value is assigned to indicate the reliability of the version information provided in this product in relation to the version of the features used to form the correlation in the original product. The Confidence Value is given for each relationship, which is defined in this relationship as:
This page aims to provide all the information to evaluate if the method of associating the respective identifiers is suitable for your needs. These identifier relationships have been extracted from existing premium products and are presented in a standalone table for easy and open access to the information. It describes which product the information was extracted from, what information was extracted and how the source product derived the original association between the identifiers.
This relationship is between the Topographic Identifier (TOID) of the RoadLink features in OS MasterMap Highways Network and the TOID of the TopographicArea of the corresponding road surface area in OS MasterMap Topography Layer.
The relationship is extracted from the relatedRoadArea attribute on the RoadLink features in OS MasterMap Highways Network - Roads product following its release.
This relationship is determined by a line in a polygon intersection between the RoadLink centre line geometry and the TopographicArea polygon(s). Specifications of capture can vary between the two source products, therefore not every RoadLink in OS MasterMap Highways Network will be represented by a TopographicArea. The relationship is performed by Ordnance Survey while creating the OS MasterMap Highways Network – Roads product.
The two source products for these identifiers are on different refresh cycles. OS MasterMap Highways Network - Roads is updated monthly, whereas OS MasterMap Topography Layer is updated every six weeks. Therefore, some of the version information in the product may have changed and mean that the relationship is out of sync.
A Confidence Value is assigned to indicate the reliability of the version information provided in this product in relation to the version of the features used to form the correlation in the original product. The Confidence Value is given for each relationship, which is defined in this relationship as:
This page aims to provide all the information to evaluate if the method of associating the respective identifiers is suitable for your needs. These identifier relationships have been extracted from existing premium products and are presented in a standalone table for easy and open access to the information. It describes which product the information was extracted from, what information was extracted and how the source product derived the original association between the identifiers.
The relationship between the Unique Property Reference Number (UPRN) of AddressBase Premium and the Topographic Identifier (TOID) of the TopographicArea feature in the OS MasterMap Topography Layer product is extracted for all live, provisional and historic BLPU records in AddressBase Premium.
Data from the OS MasterMap Topography Layer TopographicArea feature and AddressBase Premium BLPU table are joined where the TOID equals the CROSS_REFERENCE of the AddressBase Premium Cross- Reference table and the source is equal to ‘7666MT’.
The relationship is extracted from AddressBase Premium after the release of each six weekly Epoch. Further information on the relationship extraction, including the date of extraction and product version information, are provided in the Product Version Information File.
AddressBase Premium and OS MasterMap Topography Layer are updated every six weeks but on different release cycles. Therefore, some of the version information in the product may have changed and mean that the relationship is out of sync.
A Confidence Value is assigned to indicate the reliability of the version information provided in this product in relation to the version of the features used to form the correlation in the original product. The Confidence Value is given for each relationship, which is defined in this relationship as:
This page aims to provide all the information to evaluate if the method of associating the respective identifiers is suitable for your needs. These identifier relationships have been extracted from existing premium products and are presented in a standalone table for easy and open access to the information. It describes which product the information was extracted from, what information was extracted and how the source product derived the original association between the identifiers.
This relationship is between the Topographic Identifier (TOID) of the Road features in OS MasterMap Highways Network and the TOID of the Topographic Area of the corresponding road surface area in OS MasterMap Topography Layer.
A Road feature is a link set which represents a collection of RoadLink features that share the same name (e.g. Bilston Road) or classification number (e.g. A41). The relationship is extracted from the relatedRoadArea attribute on the RoadLink feature(s) of which each Road feature is composed within the OS MasterMap Highways Network – Roads product following its release.
The relationship is determined by a line in a polygon intersection between the centre line geometry of the referenced RoadLinks of each Road feature and the TopographicArea polygon(s). The relationship is performed by Ordnance Survey while creating the OS MasterMap Highways Network – Roads product.
The two source products for these identifiers are on different refresh cycles. OS MasterMap Highways Network - Roads is updated monthly, whereas OS MasterMap Topography Layer is updated every six weeks. As this product utilises published source products, the current data available for each identifier might have changed and therefore the relationship may not still be valid.
To provide an indication of the reliability of the version information provided in this product in relation to that of the version of the features used to form the correlation in the original product, a Confidence Value is given for each relationship, which is defined as follows:
This page aims to provide all the information to evaluate if the method of associating the respective identifiers is suitable for your needs. These identifier relationships have been extracted from existing premium products and are presented in a standalone table for easy and open access to the information. It describes which product the information was extracted from, what information was extracted and how the source product derived the original association between the identifiers.
This relationship is between the Topographic Identifier (TOID) of the RoadLink features and the TOID of Road features in OS MasterMap Highways Network.
A Road feature is a link set which represents a collection of RoadLink features that share the same name (e.g. Bilston Road) or classification number (e.g. A41). The relationship is extracted using the reference to the
RoadLinks which make up each Road feature in the ‘link’ attribute within OS MasterMap Highways Network – Roads product following its release.
The relationship is determined by the link reference within OS MasterMap Highways Network - Roads, demonstrating the RoadLinks of which the Road features are composed.
As this relationship is determined using a single source product the version information provided will always be the same as the version of the feature used to create the correlation.
A Confidence Value is assigned to indicate the reliability of the version information provided in this product in relation to the version of the features used to form the correlation in the original product. The Confidence Value is given for each relationship, which will always be defined in this relationship as:
This technical specification provides detailed technical information about OS Open Linked Identifiers. It is targeted at technical users and software developers.
OS Open Linked Identifiers is a dataset containing the authoritative relationships between Unique Property Reference Numbers (UPRNs), Unique Street Reference Numbers (USRNs) and Topographic Identifiers (TOIDs), and metadata. Identifiers are labels that are assigned to representations in a dataset. They are at the heart of how data can be effectively published, retrieved, reused and linked.
| Feature Type | Identifier Type | Source Product | Description |
|---|
OS Open Linked Identifiers enables you to connect the variety of relationships between UPRN, USRNs and TOIDs. These are extracted from premium products to provide you with the most up-to-date feature metadata sourced from AddressBase, OS MasterMap Highways Network and OS MasterMap Topography Layer. The more an identifier is used in other datasets, the more valuable the primary data becomes.
For example, OS Open Identifiers enables visualisation of data linked to the Highways RoadLink and Open Roads products. By sharing the road link mapping between Highways and Open Roads it enables data that has been collected and shared against the Highways’ premium products to be visualised in the open geometry.
Identifiers are crucial to the process of sharing information and linking together datasets, allowing them to fit into many workflows in many different types of workplace to provide powerful insights and support analytics.
A UPRN is a unique numeric identifier for every addressable location in Great Britain. The identifier is critical for property related information and can be found throughout OS's AddressBase products. An addressable location may be any kind of building, residential or commercial, or it may be an object that might not have a ‘normal’ address – such as a bus shelter or an electricity substation. UPRNs provide these addressable locations with a consistent, persistent identifier never being reused.
A USRN is a unique and persistent identifier for every street, road, track, path, cycletrack or way in Great Britain. It can be found in the OS MasterMap Highways Network products and is also a key component in OS’s AddressBase suite of products.
A TOID is a unique identifier, consisting of the letters ‘osgb’ and followed by either thirteen or sixteen digits, associated with every feature in many of Ordnance Survey’s large-scale products. The TOID is based upon the Digital National Framework concept and the principles that underpin it. In order for the TOID to be effective, it is essential that the reference given to it by OS remain unaltered in any way.
| Feature Type | Identifier Type | Source Product | Description |
|---|---|---|---|
| Confidence Value | Definition |
|---|---|
| Correlation Method ID | Source Product for relationship |
|---|---|
| Relationship IDs | Relationship |
|---|---|
| Confidence Value | Definition |
|---|
| Confidence Value | Definition |
|---|
The relationship is determined by a point in a polygon intersection between the Address seed location and the TopographicArea polygon. The relationship is performed by a joint venture between Ordnance Survey and Local Government Association (LGA) who produce AddressBase.
| Confidence Value | Definition |
|---|
| Confidence Value | Definition |
|---|
| Confidence Value | Definition |
|---|
TopographicArea
TOID
OS MasterMap Topographic Layer
Polygon limited to either a building outline or road surface area.
RoadLink
TOID
OS MasterMap Highways
Section of road from junction to junction.
Road
TOID
OS MasterMap Highways
Collection of RoadLink with a given name.
BLPU
(Building Land Parcel Unit)
UPRN
(Unique Property Reference Number)
AddressBase Premium
An address location with postal address.
Street
USRN
(Unique Street Reference Number)
OS MasterMap Highways
An identifier allocated to a street by a local authority.
ORRoadLink/ ORRoadNode
GUID
Open Roads
Road sections and junctions from our open data product. These features are referred to in OS Open Roads as RoadLink and RoadNode. In this product they are referred to as ORRoadLink and ORRoadNode respectively to distinguish them from the OS MasterMap Highways Networks RoadLink and RoadNode features.
Version information is correct
The version information provided is the same as the version of the feature used to create the correlation.
Version information has potentially changed
The version information could be different from the version of the feature that was used to create the correlation.
Version information has changed
The version information provided is different from the version of the feature used to create the correlation.
TopographicArea
TOID
OS MasterMap Topographic Layer
Polygon limited to either a building outline or road surface area.
RoadLink
TOID
OS MasterMap Highways
Section of road from junction to junction.
Road
TOID
OS MasterMap Highways
Collection of RoadLink with a given name.
BLPU
(Building Land Parcel Unit)
UPRN
(Unique Property Reference Number)
AddressBase Premium
An address location with postal address.
Street
USRN
(Unique Street Reference Number)
OS MasterMap Highways
An identifier allocated to a street by a local authority.
ORRoadLink/ ORRoadNode
GUID
Open Roads
Road sections and junctions from our open data product. These features are referred to in OS Open Roads as RoadLink and RoadNode. In this product they are referred to as ORRoadLink and ORRoadNode respectively to distinguish them from the OS MasterMap Highways Networks RoadLink and RoadNode features.
RoadLink_TOID_TopographicArea_TOID_2
OS MasterMap Highways Networks - Roads
Road_TOID_TopographicArea_TOID_3
OS MasterMap Highways Networks - Roads
Street_USRN_TopographicArea_TOID_4
OS MasterMap Highways Networks - Roads
BLPU_UPRN_TopographicArea_TOID_5
AddressBase Premium
RoadLink_TOID_Road_TOID_7
OS MasterMap Highways Networks - Roads
RoadLink_TOID_Street_USRN_8
OS MasterMap Highways Networks - Roads
BLPU_UPRN_RoadLink_TOID_9
AddressBase Premium
Road_TOID_Street_USRN_10
OS MasterMap Highways Networks - Roads
BLPU_UPRN_Street_USRN_11
AddressBase Premium
ORRoadLink_GUID_RoadLink_TOID_12
OS MasterMap Highways Networks - Roads
ORRoadNode_GUID_RoadLink_TOID_13
OS MasterMap Highways Networks - Roads
RoadLink_TOID_TopographicArea_TOID_2
RoadLink <-> TopographicArea
Road_TOID_TopographicArea_TOID_3
Road <-> TopographicArea
Street_USRN_TopographicArea_TOID_4
Street <-> TopographicArea
BLPU_UPRN_TopographicArea_TOID_5
BLPU <-> TopographicArea
RoadLink_TOID_Road_TOID_7
RoadLink <-> Road
RoadLink_TOID_Street_USRN_8
RoadLink <-> Street
BLPU_UPRN_RoadLink_TOID_9
BLPU <-> RoadLink
Road_TOID_Street_USRN_10
Road <-> Street
BLPU_UPRN_Street_USRN_11
BLPU <-> Street
ORRoadLink_GUID_RoadLink_TOID_12
Open Roads RoadLink <-> OSMM Highways RoadLink
ORRoadNode_GUID_RoadLink_TOID_13
Open Roads RoadNode <-> OSMM Highways RoadLink
File
Description
BLPU_UPRN_RoadLink_TOID_9.csv
Linked Identifier data (CSV)
BLPU_UPRN_RoadLink_TOID_9_versions.json
Product version information
Licence.txt
OGL Licence
UPRN_RoadLink_TOID_9_202001_description.pdf
Product description
BLPU_UPRN_RoadLink_TOID_9.csv
Linked Identifier data (CSV)
BLPU_UPRN_RoadLink_TOID_9_versions.json
Product version information
Licence.txt
OGL Licence
UPRN_RoadLink_TOID_9_202001_description.pdf
Product description
Version information is correct | The version information provided is the same as the version of the feature used to create the correlation. |
Version information has potentially changed | The version information could be different from the version of the feature that was used to create the correlation. |
Version information has changed | The version information provided is different from the version of the feature used to create the correlation. |
Version information is correct | The version information provided is the same as the version of the feature used to create the correlation. |
Version information has potentially changed | The version information could be different from the version of the feature that was used to create the correlation. |
Version information has changed | The version information provided is different from the version of the feature used to create the correlation. |
Version information is correct | The version information provided is the same as the version of the feature used to create the correlation. |
Version information has potentially changed | The version information could be different from the version of the feature that was used to create the correlation. |
Version information has changed | The version information provided is different from the version of the feature used to create the correlation. |
Version information is correct | The version information provided is the same as the version of the feature used to create the correlation. |
Version information has potentially changed | The version information could be different from the version of the feature that was used to create the correlation. |
Version information has changed | The version information provided is different from the version of the feature used to create the correlation. |
Version information is correct | The version information provided is the same as the version of the feature used to create the correlation. |
Street | USRN (Unique Street Reference Number) | OS MasterMap Highways | An identifier allocated to a street by a local authority. |
ORRoadLink/ ORRoadNode | GUID | Open Roads | Road sections and junctions from our open data product. These features are referred to in OS Open Roads as RoadLink and RoadNode. In this product they are referred to as ORRoadLink and ORRoadNode respectively to distinguish them from the OS MasterMap Highways Networks RoadLink and RoadNode features. |
RoadLink_TOID_TopographicArea_TOID_2
RoadLink <-> TopographicArea
Road_TOID_TopographicArea_TOID_3
Road <-> TopographicArea
Street_USRN_TopographicArea_TOID_4
Street <-> TopographicArea
BLPU_UPRN_TopographicArea_TOID_5
BLPU <-> TopographicArea
RoadLink_TOID_Road_TOID_7
RoadLink <-> Road
RoadLink_TOID_Street_USRN_8
RoadLink <-> Street
BLPU_UPRN_RoadLink_TOID_9
BLPU <-> RoadLink
Road_TOID_Street_USRN_10
Road <-> Street
BLPU_UPRN_Street_USRN_11
BLPU <-> Street
ORRoadLink_GUID_RoadLink_TOID_12
Open Roads RoadLink <-> OSMM Highways RoadLink
ORRoadNode_GUID_RoadLink_TOID_13
Open Roads RoadNode <-> OSMM Highways RoadLink
RoadLink_TOID_TopographicArea_TOID_2
RoadLink <-> TopographicArea
Road_TOID_TopographicArea_TOID_3
Road <-> TopographicArea
Street_USRN_TopographicArea_TOID_4
Street <-> TopographicArea
BLPU_UPRN_TopographicArea_TOID_5
BLPU <-> TopographicArea
RoadLink_TOID_Road_TOID_7
RoadLink <-> Road
RoadLink_TOID_Street_USRN_8
RoadLink <-> Street
BLPU_UPRN_RoadLink_TOID_9
BLPU <-> RoadLink
Road_TOID_Street_USRN_10
Road <-> Street
BLPU_UPRN_Street_USRN_11
BLPU <-> Street
ORRoadLink_GUID_RoadLink_TOID_12
Open Roads RoadLink <-> OSMM Highways RoadLink
ORRoadNode_GUID_RoadLink_TOID_13
Open Roads RoadNode <-> OSMM Highways RoadLink
TopographicArea | TOID | OS MasterMap Topographic Layer | Polygon limited to either a building outline or road surface area. |
RoadLink | TOID | OS MasterMap Highways | Section of road from junction to junction. |
Road | TOID | OS MasterMap Highways | Collection of RoadLink with a given name. |
BLPU (Building Land Parcel Unit) | UPRN (Unique Property Reference Number) | AddressBase Premium | An address location with postal address. |
This document aims to provide all the information to evaluate if the method of associating the respective identifiers is suitable for your needs. These identifier relationships have been extracted from existing premium products and are presented in a standalone table for easy and open access to the information. It describes which product the information was extracted from, what information was extracted and how the source product derived the original association between the identifiers.
This relationship is between the Topographic Identifier (TOID) of the RoadLink features and the Unique Street Reference Number (USRN) of Street features in OS MasterMap Highways Network.
A USRN is an 8-digit unique and persistent identifier for a street assigned by a Roads Authority or Highway Authority. Where possible, the geometry of Streets provided by the Roads or Highway Authorities is spatially matched to the geometry of OS RoadLink(s) and an aggregated geometry of the RoadLink(s) will be provided in the OS MasterMap Highways Network.
This relationship is extracted using the reference to the RoadLink(s) which have been matched to the Street
feature in the ‘link’ attribute within the OS MasterMap Highways Network – Roads product following its
release. This means that this relationship will not include all USRNs in OS MasterMap Highways, as Street features that have not been matched to an OS RoadLink will be omitted.
The relationship is determined by the link reference within OS MasterMap Highways Network, demonstrating the RoadLink feature(s) of which the matched Street features are composed. Where possible, the geometry of Streets provided by the Roads or Highway Authorities is spatially matched to the geometry of OS RoadLink(s) and an aggregated geometry of the RoadLink(s) will be provided in the OS MasterMap Highways Network.
As this relationship is determined using a single source product, the version information provided will always be the same as the version of the feature used to create the correlation.
A Confidence Value is assigned to indicate the reliability of the version information provided in this product in relation to the version of the features used to form the correlation in the original product. The Confidence Value is given for each relationship, which will always be defined in this relationship as:
This page aims to provide all the information to evaluate if the method of associating the respective identifiers is suitable for your needs. These identifier relationships have been extracted from existing premium products and are presented in a standalone table for easy and open access to the information. It describes which product the information was extracted from, what information was extracted and how the source product derived the original association between the identifiers.
The relationship between the Unique Property Reference Number (UPRN) and the Topographic Identifier (TOID) of OS MasterMap Highways Network - Roads is extracted for all live, provisional and historic BLPU records in AddressBase Premium. Data from the OS MasterMap Highways Network - Roads and AddressBase Premium BLPU table are joined where the TOID equals the CROSS_REFERENCE of the AddressBase Premium Cross-Reference table and the source is equal to ‘7666MI’.
The relationship is extracted from AddressBase Premium after the release of each six weekly Epoch. Further information on the relationship extraction, including the date of extraction and product version information, are provided in the Product Version Information File.
The relationship is determined by finding the closest RoadLink TOID from OS MasterMap Highways Network – Roads, to every BLPU of AddressBase Premium that references a USRN. The relationship is performed by GeoPlace, a joint venture between Ordnance Survey and Local Government Association (LGA) who produce AddressBase.
AddressBase Premium is updated every six weeks and OS MasterMap Highways – Roads is updated every four weeks. Therefore, some of the version information in the product may have changed and mean that the relationship is out of sync. To provide an indication of the reliability of the version information provided in this product in relation to that of the version of the features used to form the correlation in the original product, a Confidence Value is given for each relationship, which is defined as follows:
This document aims to provide all the information to evaluate if the method of associating the respective identifiers is suitable for your needs. These identifier relationships have been extracted from existing premium products and are presented in a standalone table for easy and open access to the information. It describes which product the information was extracted from, what information was extracted and how the source product derived the original association between the identifiers.
This relationship is between the unique identifier (GUID) of the RoadLink features in OS Open Roads and the Topographic Identifier (TOID) of RoadLink features in OS MasterMap Highways Network which represent the same feature.
The relationship is extracted from the OS Open Roads Lookup table which is supplied with the OS Master Map Highways Network – Roads. This table provides the TOID of the RoadLink feature in the OS MasterMap Highways Network and the GUID of the ORRoadLink feature in OS Open Roads which represent the same feature in OS Open Roads.
This relationship is determined using the OS Open Roads Lookup table which is supplied with the OS Master Map Highways Network – Roads. This table provides the TOID of the RoadLink feature in the OS MasterMap Highways Network and the GUID of the ORRoadLink feature in OS Open Roads which represent the same feature in OS Open Roads. This relationship is created by Ordnance Survey using a spatial match between systematically sampled points along the two line feature datasets.
The two source products for these identifiers are on different refresh cycles. OS MasterMap Highways Network - Roads is updated monthly, whereas OS Open Roads is updated every six months. As this product utilises published source products, the current data available for each identifier might have changed and therefore the relationship may not still be valid.
A Confidence Value is assigned to indicate the reliability of the version information provided in this product in relation to the version of the features used to form the correlation in the original product. The Confidence Value is given for each relationship, which is defined as follows:
This document aims to provide all the information to evaluate if the method of associating the respective identifiers is suitable for your needs. These identifier relationships have been extracted from existing premium products and are presented in a standalone table for easy and open access to the information. It describes which product the information was extracted from, what information was extracted and how the source product derived the original association between the identifiers.
This relationship is between the Topographic Identifier (TOID) of the Road features and the Unique Street Reference Number (USRN) of Street features in OS MasterMap Highways Network.
A Road feature is a link set which represents a collection of RoadLink features that share the same name (e.g. Bilston Road) or classification number (e.g. A41). A USRN is an 8-digit unique and persistent identifier for a street assigned by a Roads Authority or Highway Authority. Where possible, the geometry of Streets provided by the Roads or Highway Authorities is spatially matched to the geometry of OS RoadLink(s) and an aggregated geometry of the RoadLink(s) will be provided in the OS MasterMap Highways Network.
The relationship is extracted using the following:
The reference to the RoadLinks which make up each Road feature in the ‘link’ attribute of the Road
feature table.
The reference to the RoadLink(s) which have been matched to each Street feature in the ‘link’ attribute in the Street feature table within the OS MasterMap Highways Network – Roads product following its release.
Where the Road and Street features reference common RoadLink(s), the relationship is extracted.
The relationship is determined by two link references within OS MasterMap Highways Network - Roads, demonstrating where Road and Street features reference common RoadLink(s).
As this relationship is determined using a single source product the version information provided will always be the same as the version of the feature used to create the correlation. A Confidence Value is assigned to indicate the reliability of the version information provided in this product in relation to the version of the features used to form the correlation in the original product. The Confidence Value is given for each relationship, which will always be defined in this relationship as:
This page aims to provide all the information to evaluate if the method of associating the respective identifiers is suitable for your needs. These identifier relationships have been extracted from existing premium products and are presented in a standalone table for easy and open access to the information. It describes which product the information was extracted from, what information was extracted and how the source product derived the original association between the identifiers.
The relationship between the Unique Property Reference Number (UPRN) and the Unique Street Reference Number (USRN) is extracted for all live, provisional and historic BLPU records and all open roads in AddressBase Premium. All information for the associated relationship is extracted from AddressBase Premium by joining the Street table to the LPI table based on USRN, and the LPI table to the BLPU table based on UPRN. Further information on the relationship extraction, including the date of extraction and product version information, are provided in the Product Version Information File.
The relationship is determined by the Local Authorities who are responsible for Addressing and Street Name and Numbering. The Local Authorities supply this information to GeoPlace, a joint venture between Ordnance Survey and Local Government Association (LGA) who produce AddressBase.
A Confidence Value is assigned to indicate the reliability of the version information provided in this product in relation to the version of the features used to form the correlation in the original product. The Confidence Value is given for each relationship, which will always be defined in this relationship as:
This document aims to provide all the information to evaluate if the method of associating the respective identifiers is suitable for your needs. These identifier relationships have been extracted from existing premium products and are presented in a standalone table for easy and open access to the information. It describes which product the information was extracted from, what information was extracted and how the source product derived the original association between the identifiers.
This relationship is between the non-persistent unique identifier (GUID) of the RoadNode features in OS Open Roads and the Topographic Identifier (TOID) of RoadLink features in OS MasterMap Highways Network, which represent the same feature.
The relationship is extracted from the OS Open Roads Lookup table which is supplied with the OS Master Map Highways Network – Roads. This table provides the TOID of the RoadLink feature in the OS MasterMap Highways Network and the GUID of the ORRoadNode feature in OS Open Roads which represent the same feature in OS Open Roads. This will be used where a RoadLink in OS MasterMap Highways has been simplified in the OS Open Roads product to an ORRoadNode (for example, a collapsed roundabout).
This relationship is determined using the OS Open Roads Lookup table which is supplied with the OS Master Map Highways Network – Roads. This table provides the TOID of the RoadLink feature in the OS MasterMap Highways Network and the GUID of the ORRoadNode feature in OS Open Roads which represent the same feature in OS Open Roads. This relationship is created by Ordnance Survey using a spatial match between the point and line features.
The two source products for these identifiers are on different refresh cycles. OS MasterMap Highways Network - Roads is updated monthly, whereas OS Open Roads is updated every six months. Therefore, some of the version information in the product may have changed and mean that the relationship is out of sync.
A Confidence Value is assigned to indicate the reliability of the version information provided in this product in relation to the version of the features used to form the correlation in the original product. The Confidence Value is given for each relationship, which is defined in this relationship as:
| Confidence Value | Definition |
|---|---|
| Confidence Value | Definition |
|---|---|
| Confidence Value | Definition |
|---|---|
| Confidence Value | Definition |
|---|---|
| Confidence Value | Definition |
|---|---|
| Confidence Value | Definition |
|---|---|
Version information is correct
The version information provided is the same as the version of the feature used to create the correlation.
Version information is correct
The version information provided is the same as the version of the feature used to create the correlation.
Version information has potentially changed
The version information could be different from the version of the feature that was used to create the correlation.
Version information has changed
The version information provided is different from the version of the feature used to create the correlation.
Version information is correct
The version information provided is the same as the version of the feature used to create the correlation.
Version information has potentially changed
The version information could be different from the version of the feature that was used to create the correlation.
Version information has changed
The version information provided is different from the version of the feature used to create the correlation.
Version information is correct
The version information provided is the same as the version of the feature used to create the correlation.
Version information is correct
The version information provided is the same as the version of the feature used to create the correlation.
Version information is correct
The version information provided is the same as the version of the feature used to create the correlation.
Version information has changed
The version information provided is different from the version of the feature used to create the correlation.
