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 (GKPG and CSV formats) or Changed Tiles (CSV format only).
OS Partners are also able to access tile supplies.
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 (GKPG full supply)
AddressBaseCore_COU_2020-07-01_001.csv (CSV COU supply)
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)
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 1 km south-west corner of the 5 km chunk.
format: The format of the files received, i.e. csv.
For example:
NC4040.csv (CSV Tile supply)
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)
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)
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)
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:
Deletes (CHANGE_TYPE ‘D’) are objects that have ceased to exist in your area of interest since the last product refresh.
Inserts (CHANGE_TYPE ‘I’) are objects that have been newly inserted into your area of interest since the last product refresh.
Updates (CHANGE_TYPE ‘U’) are objects that have been updated in your area of interest since the last product refresh.
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.
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.
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.