# Product Supply

## Supply format <a href="#bookmark7" id="bookmark7"></a>

The OS Open TOIDs and Associated Geometry data will be provided in 100km tiles and distributed in two product formats using British National Grid (EPSG 27700) projection:

* Comma-Separated Value (CSV)
* GeoPackage (GPKG)

These formats allow the data to be easily integrated and ingested with either a database or a GIS application, respectively. Each tile will contain unique features that will not be shared across multiple tiles, as such there is not a 1:1 feature relationship between the OS Open TOID tiles and those in OSMM Topography Layer.

### GeoPackage <a href="#bookmark8" id="bookmark8"></a>

GeoPackage is an open data format as is defined by the Open Geospatial Consortium (OGC). It is designed to be a lightweight format that contains both spatial (vector) and metadata tables in a single, ready-to-use file. Please note that older versions of GIS software may need updating before being able to display and interact with GeoPackage files.

### Comma-Separated Value <a href="#bookmark9" id="bookmark9"></a>

CSVs are a simple file format used to store data, often in the form of a table or spreadsheet. These tables can be freely loaded into databases and programs allowing for the easy loading and updating of data holdings.

## Supply update <a href="#bookmark10" id="bookmark10"></a>

OS Open TOID will be updated on a 6-weekly basis, in line with the OS MasterMap Topography Layer COU (Change Only Update) releases and will maintain consistency with OS MasterMap products.


---

# 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-toid/os-open-toid-technical-specification/product-supply.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.