> 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/addresses-and-names-portfolio/os-open-names/os-open-names-overview/product-supply.md).

# Product supply

## Available formats <a href="#id-3.1-available-formats" id="id-3.1-available-formats"></a>

OS Open Names is available in the following formats:

* Comma-separated values (CSV)
* Geography Markup Language (GML) 3.2.1
* GeoPackage

## Supply mechanism <a href="#id-3.2-supply-mechanism" id="id-3.2-supply-mechanism"></a>

OS Open Names is supplied as an online download from the [OS Data Hub](https://osdatahub.os.uk/).

In addition to the data product, OS Open Names content is available to PSGA (Public Sector Geospatial Agreement) Members and OS Partners through the OS Names API, which is accessible via the [OS Data Hub](https://osdatahub.os.uk/).

## Product update schedule <a href="#id-3.3-product-update-schedule" id="id-3.3-product-update-schedule"></a>

OS Open Names is updated from Ordnance Survey’s data content stores and released to customers every three months (in January, April, July and October) to ensure the latest named features are published.

## Coverage and file sizes <a href="#id-3.4-coverage-and-file-sizes" id="id-3.4-coverage-and-file-sizes"></a>

Coverage for OS Open Names is Great Britain. File sizes for the formats are as follows:

* CSV: 96MB
* GML 3.2.1: 184MB
* GeoPackage: 256MB


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.os.uk/os-downloads/products/addresses-and-names-portfolio/os-open-names/os-open-names-overview/product-supply.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.