> 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/supply-and-update.md). # Supply and update The primary supply mechanism of AddressBase Core is a Managed Great Britain Set (MGBS). A MGBS supply is a supply of data for the whole of Great Britain; it is provided as a single file containing all records with headers already included (CSV) or the structure already defined (GPKG). Public Sector Geospatial Agreement (PSGA) customers are also able to order individual or multiple 5km tiles of interest rather than a MGBS if they wish. This can be ordered as a Full Supply (GPKG and CSV formats) or Changed Tiles (CSV format only). OS Partners are also able to access tile supplies. ## **Managed Great Britain Set (Unzipped)** If you receive your data as a MGBS; the filename will be constructed as (unzipped): *productName\_supply\_ccyy-mm-dd\_vvv.format* Where: * **productName**: AddressBaseCore supply is defined as `FULL` or `COU` * **ccyy-mm-dd**: The date the file was generated * **vvv**: The volume number of the file * **format**: The format of the files received, for example, `csv` or `gkpg` For example: * `AddressBaseCore_FULL_2020-07-01_001.gkpg` (GPKG full supply) * `AddressBaseCore_COU_2020-07-01_001.csv` (CSV COU supply) ## **Managed Great Britain Set (zipped)** If the data has been provided in a ZIP file the following convention will be followed: *productName\_supply\_ccyy-mm-dd\_vv.format.zip* For example: * `AddressBaseCore_FULL_2020-07-01_001.csv.zip` (CSV full supply zipped) ## **5km tile supplies (Unzipped CSV)** If you order a CSV format for one tile or a selection tiles, the filename of each tile will be: *ngxxyy.format* Where: * **ngxxyy**: The four-digit grid reference belonging to the 1km south-west corner of the 5km chunk. * **format**: The format of the files received, i.e. `csv`. For example: * `NC4040.csv` (CSV Tile supply) ## **5km Tile Supplies (zipped CSV)** If the data has been provided in a ZIP file the following convention will be followed for each tile: *ngxxyy.zip* For example: * `NC4040.zip` (Tile supply zipped) ## **5km Tile Supplies (Unzipped GPKG)** If you order a GPKG format for one tile or a selection tiles, the filename will be constructed as: *OrderID.format* Where: * **OrderID**: The ID that is assigned to each order * **format**: The format of the files received, that is, `gkpg` For example: * `1002-1700-RAND-1000.gpkg` (CSV Tile Supply) ## **Geographic chunks (zipped GPKG)** If the data has been provided in a ZIP file the following convention will be followed: *OrderID.format.zip* For example: * `1002-1700-RAND-1000.gpkg.zip` (Tile supply zipped) ## COU supply AddressBase Core is available as a Full Supply or Change Only Update (COU) for MGBS supplies. A COU supply of data contains records or files that have changed between product refresh cycles. The primary benefit in supplying data in this way is that volumes are smaller reducing the amount of data that requires processing when compared to a Full Supply. COU data enables you to identify three types of change if they are using the Managed Great Britain Sets of data: 1. Deletes (CHANGE\_TYPE ‘D’) are objects that have ceased to exist in your area of interest since the last product refresh. 2. Inserts (CHANGE\_TYPE ‘I’) are objects that have been newly inserted into your area of interest since the last product refresh. 3. Updates (CHANGE\_TYPE ‘U’) are objects that have been updated in your area of interest since the last product refresh. ### Managed Great Britain Set (MGBS) COU A COU file for MGBS data can be identified by its naming convention as detailed in previous sections. Any change record will be provided as a full record with the appropriate change type, as listed above. ### Tile supply COU A tile-based COU is supplied differently to the MGBS supplies. If a single address record has changed within a specified 5km tile, the entire 5km tile containing all features will be supplied. This means the user will need to remove all features that previously existed in the provided tile(s) and insert the entire new tile(s) in its place. ### Archiving When users are Deleting, Inserting or Updating features it is up to the user to consider their archiving requirements. If deleted records are important to your business requirements you must take appropriate action to archive previous records. --- # 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/supply-and-update.md?ask=&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.