# Product structure

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

## Comma-Separated Values <a href="#bookmark2" id="bookmark2"></a>

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:

<figure><img src="/files/bQH4k1qjVXtFP5aPDi4j" alt="Four files extracted from the zip archive showing the CSV file, PDF, .json, and license txt" width="464"><figcaption><p>Four files extracted from the zip archive showing the CSV file, PDF, .json, and license txt</p></figcaption></figure>

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


---

# Agent Instructions: 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:

```
GET https://docs.os.uk/os-downloads/products/buildings-and-infrastructure-portfolio/os-open-linked-identifiers/os-open-linked-identifiers-technical-specification/product-structure.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.