> 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/addressbase-core/addressbase-core-technical-specification/data-formats.md).

# Data formats

The AddressBase Core product is distributed as a Comma Separated Value (CSV) file or GeoPackage (GPKG). CSV files can be supplied as a Full Supply or Change Only Update (COU) when taking Managed Great Britain Sets (MGBS); or Full Supply or changed tiles when taking tile supplies. GPKG is only available as Full Supply for both MGBS and tile supplies.

## CSV <a href="#id-1.1.1_csv" id="id-1.1.1_csv"></a>

The CSV format of AddressBase Core means:

1. Column headers are included in the file.
2. There is one record per line in each file.
3. Fields are separated by commas.
4. No comma is placed at the end of each row in the file.
5. Records are terminated by carriage return/line feed.

For MGBS orders, one file containing all records is produced.

## GPKG <a href="#id-1.1.2_geopackage" id="id-1.1.2_geopackage"></a>

GPKG is an open, standards-based, platform-independent data format for transferring geospatial information as defined by the Open Geospatial Consortium (OGC). It is designed to be a lightweight format that can contain large amounts of varied and complex data in a single, easy-to-distribute and ready-to-use file.

GPKG offers the following benefits:

1. The single file is easy to transfer and offers the end-user a rich experience.
2. Attribute names are not limited in length making it customer friendly.
3. No file size limit, so lots of data can be easily accommodated.
4. Supports raster, vector and database formats making it a highly versatile solution.
5. Conforms to OGC standard.
6. In most cases, it is a Plug and Play format.

For both MGBS and tile supplies, GeoPackage supplies will be provided as one file.


---

# 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/addressbase-core/addressbase-core-technical-specification/data-formats.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.