> For the complete documentation index, see [llms.txt](https://docs.os.uk/os-downloads/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.os.uk/os-downloads/products/buildings-and-infrastructure-portfolio/os-open-linked-identifiers/os-open-linked-identifiers-overview/uses-of-os-open-linked-identifiers.md). # Uses 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. ## RoadLink\_TOID\_TopographicArea\_TOID\_2

RoadLink feature type related to a Topographic feature type for data visualisation

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. ## Road\_TOID\_TopographicArea\_TOID\_3

A data visualisation of a road feature type linked to a TopographicArea feature type

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. ## Street\_USRN\_TopographicArea\_TOID\_4

A visualisation of a street feature type related to a Topographic area feature type

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. ## BLPU\_UPRN\_TopographicArea\_TOID\_5

Visual representation of BLPU feature type linked to a TopographicArea feature type

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. ## RoadLink\_TOID\_Road\_TOID\_7

A visual representation of road and RoadLink feature types

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. ## RoadLink\_TOID\_Street\_USRN\_8

A visual representation of Street and RoadLink feature types

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. ## BLPU\_UPRN\_RoadLink\_TOID\_9

A visual representation of the RoadLink feature type showing access to property UPRNs

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. ## Road\_TOID\_Street\_USRN\_10

A visual representation of the Street feature type linked to Road

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. ## BLPU\_UPRN\_Street\_USRN\_11

Visualisation of Street and BLPU feature types linking property addresses to streets by UPRN

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. ## ORRoadLink\_GUID\_RoadLink\_TOID\_12 & ORRoadNode\_GUID\_RoadLink\_TOID\_13

Two visualisations showing RoadLink and RoadNode feature types alongside RoadLink features within the OS Open Roads product.

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. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.os.uk/os-downloads/products/buildings-and-infrastructure-portfolio/os-open-linked-identifiers/os-open-linked-identifiers-overview/uses-of-os-open-linked-identifiers.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.