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