Epoch 115

This release note provides information about the December 2024 (Epoch 115) release of AddressBase products.

This release note provides information about the December 2024 (Epoch 115) release of AddressBase Islands products.

Epoch 114

This release note provides information about the November 2024 (Epoch 114) release of AddressBase products.

This release note provides information about the November 2024 (Epoch 114) release of AddressBase Islands products.

Epoch 113

This release note provides information about the September 2024 (Epoch 113) release of AddressBase products.

This release note provides information about the September 2024 (Epoch 113) release of AddressBase Islands products.

Epoch 112

This release note provides information about the August 2024 (Epoch 112) release of AddressBase products.

This release note provides information about the August 2024 (Epoch 112) release of AddressBase Islands products.

Epoch 111

This release note provides information about the June 2024 (Epoch 111) release of AddressBase products.

This release note provides information about the June 2024 (Epoch 111) release of AddressBase Islands products.

Epoch 110

This release note provides information about the May 2024 (Epoch 110) release of AddressBase products.

This release note provides information about the May 2024 (Epoch 110) release of AddressBase Islands products.

Epoch 109

This release note provides information about the April 2024 (Epoch 109) release of AddressBase products.

This release note provides information about the April 2024 (Epoch 109) release of AddressBase Islands products.

Epoch 108

This release note provides information about the February 2024 (Epoch 108) release of AddressBase products.

This release note provides information about the February 2024 (Epoch 108) release of AddressBase Islands products.

Epoch 107

This release note provides information about the January 2024 (Epoch 107) release of AddressBase products.

This release note provides information about the January 2024 (Epoch 107) release of AddressBase Islands products.

Epoch 106

This release note provides information about the November 2023 (Epoch 106) release of AddressBase products.

This release note provides information about the November 2023 (Epoch 106) release of AddressBase Islands products.

The following AddressBase core principles pages provide an overview of the 'family' of AddressBase products. They cover core elements of design for AddressBase products, including data formats, coordinate reference systems, currency, precision, and data sources, amongst other topics.

The Unique Property Reference Number (UPRN) is the persistent identifier providing consistency across the AddressBase products range.

Each address record has a UPRN, which provides a reference key to join related address records across different datasets.

Throughout its life cycle, information on the address of a property can change. This may be due to a change of name, change of use, or the eventual demolition of the property. All these changes are reflected against the same UPRN meaning that users are aware that it is the same physical property.

What's available on this site?

This is a self-serve site containing documentation and guides relating to Ordnance Survey (OS) Premium and OpenData Download products available to download through the OS Data Hub.

The Download products are grouped by portfolio: Addressing and Location, Contextual or Derived, Networks, Topography, Identifiers, and Height.

On the left-hand-side menu, under each product listing, we've arranged the documents from high-level Overview to low-level Technical Specification. A Getting Started Guide and Release Notes are available for most products. We've also added links to any additional files (for example, CSV header files, stylesheets and XML schemas) available for some products but held on separate OS sites on product-specific 'Downloads' pages.

There's a Product Announcements page for notable product news, a that details product update schedules, and a , which lists all of the OS data products available to Public Sector Geospatial Agreement (PSGA) Members on an unlimited basis across the downloadable products, APIs and OS National Geographic Database (OS NGD).

✨ What's new?

There are two types of Download data product: OS Premium and OS OpenData.

What are OS Premium Download data products?

When we refer to Premium products we mean paid-for datasets – whether they’re paid for by businesses, purchased through an , or accessed free at the point of use under the .

The OS Premium Download data products are available to download in a range of formats, with a variety of ordering options, through the on our .

Our Premium Download data products work in a range of software, including ESRI ArcGIS, QGIS, Mapbox, Cadcorp SIS, MapInfo, Tableau, Kepler.gl and many more.

What are OS OpenData Download products?

OS OpenData Download products are free to use by anyone for any purpose – including for services from which you make a profit.

The OS OpenData Download products are available to download in a variety of formats, with a variety of ordering options, through the .

Download product portfolios

This code list is used in association with the attribute addressbasePostalCode/ADDRESSBASE_POSTAL_CODE found on the BLPU table. The code list describes the record as postal or not as defined by Addressbase logic.

This enumeration is used in association with the stateCode/STATE_CODE attribute. This enumeration describes the physical nature of the address record.

This enumeration is used in association with the postcodeType/POSTCODE_TYPE attribute. This enumeration identifies the code used by Royal Mail to describe the user as a small or large user. This is defined for postal services based on the number of letters delivered to that user.

There are many Date columns within the AddressBase product. Where a type format of Date has been used in the above attribute tables, the data will be defined in the following format.

AddressBase provides an address product containing both residential and commercial addresses where a Local Authority address has been matched to a Royal Mail PAF address. This allows users to link additional information about a property to a single address. The product also provides enhancements to the Royal Mail PAF data by assigning an X and Y coordinate on British National Grid and an ETRS89 projection, as well as a primary level classification, and a representative point code describing the positional quality.

This technical specification includes the following sections:

• Data formats

• Supply and update

System requirements

AddressBase data is an addressing gazetteer that can be used within GIS and database systems. For details of Ordnance Survey’s licensed partners, who can incorporate the AddressBase products in their systems, please see the systems/software page on the Ordnance Survey website.

Ordnance Survey does not recommend either suppliers or software products as the most appropriate system depends on many factors, such as the amount of data being taken, resources available within the organisation, the existing and planned information technology infrastructure and the applications that AddressBase products can be used for.

However, as a minimum, the following elements will be required in any system:

• A means of reading the data, either in its native format, or by translating it into a file format or for storage in a database.

• A means of storing and distributing the data, perhaps in a database or through a web-based service.

• A way of visualising and querying the data, typically a GIS.

Backup provision of the product

You are advised to copy the supplied data to a backup medium.

Typical data volumes

For reading purposes, it is recommended to store the data on a single hard disc. This will speed up the ability of your computer to read the data. Unzipped file sizes for the full supply of each product are as follows:

AddressBase, AddressBase Plus, AddressBase Premium and AddressBase Islands are updated every six weeks. This six week period of time is known as an epoch.​

Our AddressBase products are currently available as a Full Supply or Change-Only Update (COU) for each epoch.​

Future AddressBase epoch publication dates

Future dates are provided as an indication only and are subject to change. Data cut dates are estimates; these are given to provide an indication of the last point at which changes will reach the epoch. ​

Past AddressBase epoch publication dates

This section describes the features (one for CSV and two for GML) which make up the AddressBase product, giving the following information about each attribute.

AddressBase attribute information

Name and Definition

The name of the attribute and what it is describing.

Condition

A condition associated with this attribute (optional).

Attribute Type

The nature of the attribute, for example a numeric value or a code list value.

Multiplicity

Describes how many times this element is expected to be populated in the data. An attribute may be optional or mandatory within the AddressBase product. These are denoted by:

• ‘1’ – there must be a value.

• ‘0..1’ – population is optional but a maximum of one attribute will be returned These values may be used in combination.

AddressBase feature types

This enumeration is used in association with the streetClassification/STREET_CLASSIFICATION attribute found in the Street table. The enumeration provides a value denoting the primary classification of the street record.

Record counts

This enumeration is used in association with the logicalStatus/LOGICAL_STATUS attribute found in the BLPU and LPI table. This enumeration provides a value to show the lifecycle stage of the address record.

The AddressBase Classification Scheme provides varying levels of classification for addressable objects which are captured and maintained by the Local Authorities and Ordnance Survey. This allows searches to be limited on residential or commercial addresses or be more specific to find all the flats or all fast-food outlets. The varying levels of classification are as follows:

• Primary Level Classification R: Residential C: Commercial

  • Secondary Level Classification RD: Residential Dwelling CH: Hotel/Motel/ Boarding/ Guest House

This enumeration is used in association with the streetSurface/STREET_SURFACE attribute found in the Street table. This enumeration identifies the surface finish of the street.

This enumeration is used in association with the rpc/RPC attribute. This enumeration identifies the accuracy value of the coordinates allocated to the address.

A code list or enumeration is a controlled set of values which can be used to populate a specific column. The code list and enumeration UML models associated with AddressBase are shown in the diagram below.

AddressBase code lists and enumerations

• CountryCode

This enumeration is used in association with the recordType/RECORD_TYPE attribute found in the Street table. This enumeration identifies the record type of the street record.

AddressBase is structured as a flat file. The data structure in this document is described by means of Unified Modeling Language (UML) class diagrams.

The AddressBase product is constructed as per the following UML diagrams.

Model overview CSV

AddressBase Core is an easy-to-use, accessible addressing data product that gives plug-and-play access to complete and accurate address data. It combines key elements from existing AddressBase products into a simplified product.

AddressBase Core is a simple, accessible addressing data product giving Plug and Play access to Great Britain addressing data and additional attribution, without being time-consuming or complex. It provides live addressing records for England, Wales and Scotland based on Local Authority holdings of the Local Land and Property Gazetteer (LLPG). Other attribution includes secondary level classifications (detailing the use and type of an address) and a representative point code describing the positional quality of coordinates.

This technical specification includes the following sections:

Loading GML

GML is an XML dialect which can be used to model geographic features. It was designed by the Open Geospatial Consortium (OGC) as a means for people to share information regardless of the applications or technology that they use.

In the first instance, GML was used to overcome the differences between different GIS applications by providing a neutral file format as an alternative to proprietary formats. Because it is independent of applications, it can also be moved between databases or other types of application, which allows a wider application than just GIS data transfer.

GML data can be viewed and loaded into a database using software such as Safe FME:

This enumeration is used in association with the attribute blpuState/BLPU_STATE. This enumeration describes the physical nature of the address record.

Original feature – AddressBase CSV

COU feature – AddressBase CSV

This enumeration is used in association with the usrnMatchIndicator/USRN_MATCH_INDICATOR attribute found in the LPI table. This enumeration identifies how the USRN has been allocated to an address record.

Record counts

1. These counts are based on a Managed Great Britain Set (MGBS). If you have ordered your national coverage via the online ordering system using a polygon outline, then your counts may differ.

2. Change-Only Updates are not available for the OS Open UPRN product.

Product supply comparison

There is a difference in product counts between taking a national Managed Great Britain Set (MGBS) and a national Area of Interest (AOI). This is because the two supplies use different selection criteria. The differences are shown in the following table, allowing for you to validate your data holdings once you have loaded the latest release of AddressBase data.

The national AOI refers to the pre-selection GB polygon from our download store. Therefore, if you have drawn your own AOI, the count will vary.

If you are unsure of your supply type, please check this with your OS Relationship Manager.

Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the numbers of these records which can be expected in an MGBS supply,and also how many tiles are affected if you take your supply as Changed Chunks.

AddressBase

AddressBase Plus

AddressBase Premium

Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 115:

Data issues

AddressBase Plus

Affected output formats: CSV and GML

• There are 6 552 Unique Property Reference Numbers (UPRNs) which reference a Parent UPRN that cannot be found in the product. This is because the Parent UPRN is either provisional or historic and is not matched to the Royal Mail Postcode Address File (PAF) or Valuation Office Agency (VOA) record, meaning that it is not included in the AddressBase Plus product as per the existing background logic rules.

• There are 219 records with a sao_start_no or sao_text that have no Parent UPRN in the product. This is because the Parent UPRN is a historical record which is included as part of the logic for record inclusion in the AddressBase Plus products.

Improvements in Epoch 115

Valuation Office Agency matching

The match rates for Council Tax and Non-Domestic Rates for Epoch 115 are detailed as follows based on Valuation Office Agency (VOA) records up to 11 November 2024. The match rate is applicable to the AddressBase Premium product.

Tertiary classifications

Work is being undertaken to improve the classifications of records within the AddressBase products. This work has resulted in 38 207 more tertiary classifications present in Epoch 115 compared to Epoch 114. A total of 88.71% of these tertiary classification improvements are against residential codes.

PAF matching

AddressBase, AddressBase Plus and AddressBase Premium

Increased PAF matches shown in product – 14 102 PAF records had been previously withheld from product due to a processing constraint which omitted UPRNs with multiple candidate PAF matches from showing in product as a one-one match. This was resolved on the 25/10/24.

The following graph shows the number of Postcode Address File (PAF) matched records in AddressBase by epoch:

Next release

The next release of AddressBase products, Epoch 116, is scheduled for 06 February 2025.

Record counts

Product supply comparison

There is a difference in record counts between taking a national Managed Great Britain Set (MGBS) and the national 5km-tile supply. This is because the two supplies use different selection criteria. The difference in record counts is shown in the following table, allowing you to validate your data holdings once you have loaded the latest release of AddressBase Core.

A small difference in record counts is expected due to there being several features supplied in the MGBS which fall outside of the tiled area.

Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase Core product, you will receive Insert, Update and Delete records within the supplied file. The following table details the numbers of these records which can be expected in the COU supply of the product:

Source data currency

The following information relates to the currency of the source data used in the creation of this release of AddressBase Core:

AddressBase products are created by bringing together different address sources:

• Local Authority Gazetteers across Great Britain, Northern Ireland, the Channel Islands and the Isle of Man

• Royal Mail PAF data

• References to Valuation Office Agency (VOA) data

• Additional addresses and coordinates from Ordnance Survey

The data is supplied as comma-separated values (CSV) or Geography Markup Language (GML).

This getting started guide shows you how to obtain a data supply, load and work with AddressBase data. It includes the following sections:

Record counts

Product supply comparison

There is a difference in record counts between taking a national Managed Great Britain Set (MGBS) and the national 5km-tile supply. This is because the two supplies use different selection criteria. The difference in record counts is shown in the following table, allowing you to validate your data holdings once you have loaded the latest release of AddressBase Core.

A small difference in record counts is expected due to there being several features supplied in the MGBS which fall outside of the tiled area.

Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase Core product, you will receive Insert, Update and Delete records within the supplied file. The following table details the numbers of these records which can be expected in the COU supply of the product:

Source data currency

The following information relates to the currency of the source data used in the creation of this release of AddressBase Core:

CSV supply

Original Supply

UPRN,PARENT_UPRN,UDPRN,USRN,TOID,CLASS,EASTING,NORTHING,LATITUDE,LONGITUDE,RPC,LAST_UPDATE_DATE,SINGLE_LINE_ADDRESS,PO_BOX,ORGANISATION,SUB_BUILDING,BUILDING_NAME,BUILDING_NUMBER,STREET_NAME,LOCALITY,TOWN_NAME,POST_TOWN,ISLAND,P OSTCODE,DELIVERY_POINT_SUFFIX,GSS_CODE,CHANGE_CODE
200010019924,,52126562,40020087,"osgb1000002682081995","C",437318,115539,50.9380858,-1.4702581,2,2020-01-06,"ORDNANCE SURVEY, 4 ADANAC DRIVE, NURSLING, SOUTHAMPTON, SO16 0AS","","ORDNANCE SURVEY","","","4","ADANAC
DRIVE","","NURSLING","SOUTHAMPTON","","SO16 0AS","1A","E07000093","I"

COU Supply

Changed fields are annotated (underlined).

Update to the location of AddressBase technical documentation and release notes

AddressBase family product technical documentation (including technical specifications, release notes, getting started guides, etc.) is now available on the new . This platform is the new central location for all technical documentation for OS Premium and OpenData Download products (such as AddressBase, OS MasterMap Topography Layer, OS Open UPRN, etc.).

Over the next few months, the old PDFs containing product technical documentation will be removed from the product pages of the OS website and replaced by links to the refreshed documentation on the new platform.

; simply navigate to the new platform and click Addressing and location portfolio >

The AddressBase product family is made up of four products:

The naming of attributes between GML and CSV will be different due to the requirements of the file formats. For convenience the following table maps the CSV attribute name to the GML attribute name.

Record counts

Record counts

Available supply formats

All four of the AddressBase products are available as Comma-Separated Value (CSV) files. AddressBase, AddressBase Plus and AddressBase Premium are also available as Geography Markup Language (GML). AddressBase Core is also available as a GeoPackage.

Comma-Separated Values (CSV)

Comma-separated value (CSV) files are a delimited text file that use commas or other characters to separate individual elements of a feature. It is used to store data, often in the form of a table. These tables can be freely loaded into databases and programs allowing for the easy loading and updating of data holdings.

The supply of AddressBase products in the CSV format means:

• There will be one record per line in each file.

• Fields will be separated by commas.

• Character strings will be encapsulated with double quotation marks.

• No comma will be placed at the end of each row in the file.

For AddressBase Core the first line of the CSV file will be the Header row. Other AddressBase products have a separate Header file that is available on the product support page and can be combined with the data to give a structure tabular view. Instructions to do this are provided in the relevant Getting Started Guides on the Product Support pages.

Geography Markup Language (GML) version 3.2

The Geography Markup Language (GML) Encoding standard is an Extensible Markup Language (XML) grammar for expressing geographical features. XML schemas are used to define and validate the format and content of GML. The XML specifications that GML is based on are available from the World Wide Web Consortium (W3C) website: More information can be found in the Open Geospatial Consortium (OGC) document, Geography Markup Language v3.2.1.

The GML 3.2 specification provides a set of schemas that define the GML feature constructs and geometric types. These are designed to be used as a basis for building application-specific schemas, which define the data content.

More information on the XML schemas can be found in the product technical specification.

GeoPackage

GeoPackage (GPKG) is an open, standards-based data format 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. Please be advised that older versions of GIS software may need updating before being able to display and interact with GeoPackage files.

GeoPackage offers the following benefits:

• The single file is easy to transfer and offers the end-user a rich experience.

• Attribute names are not limited in length making it user-friendly.

• No file size limit so lots of data can be easily accommodated.

• Supports raster, vector and database formats making it a highly versatile solution.

Supply media and file structure

AddressBase products incorporate a web-based ordering system that allows customers to order initial data supply and updates, obtain price estimates and view details of their data holdings on demand.

AddressBase products can be ordered via DVD or Secure File Transfer Protocol (SFTP).

AddressBase Core is provided as a single file which will contain all records regardless of format and supply option: full supply or COU.

The AddressBase, AddressBase Plus and AddressBase Premium products have been split into chunks of smaller data. The primary supply mechanism is referred to as non-geographic chunks. This is the main mechanism for the delivery of data.

Public Sector Geospatial Agreement (PSGA) customers are able to order all AddressBase products via geographic chunks (5km tiles). Address records are provided in individual files, which represent each 5km tile ordered.

Non-geographic chunking

Non-geographic chunking is a way of dividing up data into chunks that are supplied in separate volumes that have a fixed maximum number of records, as opposed to a given geographic National Grid area. For this reason, it is possible for features from various geographic locations to appear in one volume and for adjacent features to appear in different volumes.

Non-geographic chunk volumes are designed to be loaded into spatial databases, but can be used in a file format as long as all chunks are translated or imported into the system at the same time.

CSV files can supply a maximum of one million complete address records within one volume, when this limit is reached, a new volume will be started.

For the GML supply a maximum of 200 000 features will be provided in one volume before the next one is started.

Geographic chunking

For data that is supplied in 5km-by-5km chunks, the file name will reference the 1km tile in the south-west corner of the 5km tile.

Based on your area of interest (AOI), for example the boundary of your local authority, a 5km-by-5km grid covering the area of interest is generated.

All features within each 5km grid that intersects the AOI are added to a geographic chunk file. Geographic chunking is performed using the standard Ordnance Survey National Grid.

Coverage

AddressBase products provide address data for England, Wales and Scotland.

National sets

A national set of AddressBase, known as a Managed GB Set (MGBS) service is a way of processing identical orders faster, which improves delivery times. All records within England, Wales and Scotland will be provided. If you are signed up to an MGBS service you will benefit from:

• Data arriving faster and in a more predictable manner.

• Seeing the same version of features as other organisations.

• Easier data management – no need to manage your order beyond signing up.

For Public Sector Geospatial Agreement (PSGA) customers, MGBS will be supplied as geographic or non-geographic chunks. For non-PSGA users, MGBS will be supplied as non-geographic chunks.

Customer defined areas of interest

Customers may provide their own area of interest (AOI) in any standard GIS format.

You can supply us with a polygon or you can digitise a polygon within our online ordering service.

Product updates

Customers are able to take a full supply for all AddressBase products. An easier way to manage the addressing data which each product release is to take change-only updates (COU)

Full Supply

A Full Supply is a resupply of all addressable features in each product each time it is released. This may require you to delete to current holding and replace this with the newly supplied product on each product refresh.

AddressBase Core in GeoPackage format is only available as a Full Supply each week.

COU

Change-only update (COU) is a supply of features which have been created, changed or deleted in a customer’s area of interest since their last supply.

Any feature which has not undergone one of the above changes since a customer’s last supply will not be supplied as part of a COU.

COU will be supplied on a weekly basis for AddressBase Core CSV or a six-weekly basis for AddressBase, AddressBase Plus and AddressBase Premium.

A Geographic chunked COU is not supplied as per the Non-Geographic chunked COU outlined above. For a specified 5km tile, all features within the tile will be supplied should any of the individual features change.

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.

Local Authority data is at the heart of AddressBase Core. This data provides you with a complete address product; access to over 33 million addresses each unique referenced with the Unique Property Reference Number (UPRN) and property level coordinates.

AddressBase Core takes many of the important elements from the other AddressBase products, such as coordinates, classification and cross-references to connect address information to other products via key identifiers.

AddressBase Core's primary source of addressing information is Local Authority data from the National Land and Property Gazetteer (NLPG) and One Scotland Gazetteer (OSG). They have the legal responsibility to capture and maintain address data for Great Britain, so you are assured of its authenticity and legal nature.

Address information is provided in an easy-to-use format alongside a single line attribute which concatenates all the address elements into what you would expect to see on an envelope. It is updated weekly and is offered in an easier to digest format to make the product as easy to access and use as possible.

Record Counts

The AddressBase product will be distributed as a comma-separated values (CSV) file or Geography Markup Language (GML) version 3.2. Both of these formats can either be supplied as a full supply or a change-only update (COU) supply.

CSV

The CSV supply of AddressBase means:

• There will be one record per line in each file.

Record counts

All AddressBase products are available as a full supply or a Change Only Update (COU).

A COU means you will only be supplied with the features which have changed since your last supply.

The following sub-sections provide guidance on how you could potentially manage a COU supply of AddressBase Core using PostgreSQL.

• Where angle brackets (<>) are used, you should be replace the entire string with your content. For example:

  Becomes:

This enumeration is used in association with the attribute ChangeType/CHANGE_TYPE. This enumeration identifies the type of change that has been made to a feature.

Header files

The header files for AddressBase are available for download from the AddressBase product page of the OS website.

A code list is a controlled set of allowable labels or codes represented as an alphanumeric attribute. The sub-pages in this section show the code lists used within the AddressBase 'family' of products. Some of the code lists apply to attributes of multiple feature types, whereas others will only apply to attributes of one feature type.

A critical step in the creation of an address is undertaken within each Local Authority by the dedicated Street Name and Numbering (SNN) custodian and the Scottish Local Street Gazetteer (LSG) custodians, who allocates the official street name and building information.

The SNN/LSG custodian has a statutory obligation to provide SNN/LSG information for all addresses within their administrative area. Once the SNN/LSG custodian has fulfilled their statutory obligation for initial capture, the LLPG/OSG custodian will maintain the address for the life of the address record.

The official street name and building information for new properties captured by the SNN/LSG custodians is provided to Royal Mail who then allocate a postcode to the address.

Record counts

Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase Islands product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the count of these records.

AddressBase Plus Islands

AddressBase Premium Islands

Source data currency

The following information relates to the currency of the source data used in the creation of Epoch 115:

Data issues

AddressBase Premium Islands

• Street incorrect coordinates – There are two Streets which have incorrect start or end coordinates of 000000. The unique identifiers can be provided upon request through your OS Relationship Manager.

• AddressBase Premium Islands, AddressBase Plus Islands

• 14 102 PAF records (across GB and Islands product) had been previously withheld from product due to a processing constraint, which omitted UPRNs with multiple candidate PAF matches from showing in product as a one-one match. This was resolved on the 25/10/24.

Next release

The next release of AddressBase products, Epoch 116, is scheduled for 06 February 2025.

Record counts

Record counts

This release note provides information about the 04 January 2025 release of AddressBase Core.

There are many Date columns within the AddressBase product. Where a type format of Date has been used in the above attribute tables the data will be defined in the following format.

There are columns within the AddressBase product which provide a Time value. Where this is declared, the data will be provided in the following format.

Currency

Updates are continuously made to the central spatial address data hub, which is managed by GeoPlace. These are used to produce the AddressBase Core product, which is supplied on a weekly basis. An extract is taken for the creation of AddressBase, AddressBase Plus and AddressBase Premium on a 6-weekly basis.

Completeness

Quality control procedures are undertaken at all stages of production to ensure that the data is as accurate and complete as possible and conforms to the specification. These quality control checks include automated data testing against the product specification and visual checks by operators.

A code list or enumeration is a controlled set of values which can be used to populate a specific column.

AddressBase Core code lists an enumerations:

• RPCCode

• ChangeTypeCode

AddressBase products have two coordinate reference systems (CRS) present within the data:

• British National Grid (BNG): BNG uses the OSGB36 geodetic datum and a single Transverse Mercator projection for the whole of Great Britain. Positions on this projection are described using Easting and Northing coordinates in units of metres. The BNG is a horizontal spatial reference system only; it does not specify a vertical (height) reference system.

• European Terrestrial Reference System 89 (ETRS89): ETRS89 is the EU-recommended frame of reference for European data and is represented as Latitude and Longitude values. ETRS89 is a horizontal spatial reference system only; it does not specify a vertical (height) reference system.

View our guide to coordinate systems in Great Britain for more information.

Record counts

Changed records

If you receive a Change-Only Update (COU) supply for your AddressBase Islands product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the count of these records.

AddressBase Plus Islands

AddressBase Premium Islands