Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Release notes listed here provide information about the current release of the AddressBase 'family' of products and the previous nine releases.
The 'AddressBase Products' release notes include information on the AddressBase, AddressBase Plus and AddressBase Premium products.
The 'AddressBase Islands' release notes include information on the AddressBase Plus Islands and AddressBase Premium Islands products.
AddressBase Core is supplied weekly and its release notes can be found on the AddressBase Core Release Notes page.
OS Open UPRN release notes can be found on the OS Open UPRN Release Notes pages.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 AddressBase product family is made up of four products:
AddressBase products are created by bringing together different address sources:
Local Authority Gazetteers for England, Wales and Scotland
Royal Mail PAF data
References to Valuation Office Agency (VOA) data
Additional addresses and coordinates from Ordnance Survey
This information is managed by GeoPlace under a joint venture partnership between Local Government Association and Ordnance Survey (OS). Scottish Local Authority address information is supplied to GeoPlace under licence between Ordnance Survey and the Improvement Service supported by the Scottish Government.
Ordnance Survey is responsible for customer management, sales, marketing and distribution of the AddressBase products.
This comparison table highlights the similarities and differences between the AddressBase products
UPRN
Local Authority current address
PAF Address – Royal Mail addresses
PAF UDPRN – Royal Mail’s delivery reference system
Single line address
Simple classification
Advanced classification
Cross-reference with third party datasets
Alternate addresses
Lifecycle data
The four AddressBase products have been designed to meet distinct customer requirements. The source data is collated, verified and quality assured by GeoPlace.
AddressBase Premium provides the most detailed view of an address and its life cycle for England, Wales and Scotland. It has approximately 40 million addresses as it records an address from creation through to retirement. All address records are provided with a Unique Property Reference Number (UPRN).
There are over 100 million cross-references which include references to VOA data and products such as OS MasterMap Topography Layer and OS Highways Layer are also included.
The product contains Local Authority, Ordnance Survey and Royal Mail addresses. This includes alternative addresses for current records where available, indicating variations on the official addresses and/or addresses in different languages (Welsh or Gaelic); as well as including provisional addresses (proposed planning developments), and historic information (demolished properties) where available. Other addresses known as Objects Without a Postal Address (OWPAs) are also included in AddressBase Premium, these include places of worship, community centres and utilities.
AddressBase Core is a new addition to the addressing portfolio, which was released in July 2020.
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.
Customers have asked for easy file formats, so CSV and GeoPackage are available for this product, with headers included – removing the need for any post-processing. Simply load, or drag and drop into a GIS package to start analysing.
AddressBase Plus contains current properties using addresses sourced from Local Authorities, Ordnance Survey and Royal Mail for England, Wales and Scotland. The product currently contains approximately 37 million records.
The product contains all current addresses validated from Local Custodians and non-postal addresses such as ponds, electricity sub-stations and telephone boxes are also included.
The product enables the end-user to locate an address or property on a map using either X, Y coordinates supplied on a British National Grid or Latitude and Longitude coordinates provided on an ETRS89 projection, and display the Local Authority address elements or the Royal Mail address elements where matched.
AddressBase provides a current view of all Royal Mail PAF addresses that have been matched to the NLPG and OSG . The product provides Royal Mail attribution as well as enhancing PAF with X and Y coordinates on the British National Grid and ETRS89 coordinate reference system and providing the classification of an address to a primary level (see the classification scheme page for further details on classification levels). It also provides a primary level classification.
This product will provide you with a single view of an address, allow you to locate this address on a map to give you a geographic view and carry out primary analysis on the function of the address to determine, for example, residential from commercial properties.
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 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.
Records will be terminated by Carriage Return/Line Feed.
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.
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: http://www.w3.org. 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 (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.
It is an OGC Standard.
In most cases, it is a Plug and Play format.
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.
https://www.ordnancesurvey.co.uk/business-government/tools-support/orders 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 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.
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.
AddressBase products provide address data for England, Wales and Scotland.
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.
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.
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)
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.
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.
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.
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.
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.
Coordinates for all addressable objects with each AddressBase product are published with geometry given to a precision of up to two decimal places for British National Grid coordinates, and up to seven decimal places for ETRS89 coordinates.
This release note provides information about the December 2024 release of the AddressBase products. These products were released to customers on 19 December 2024.
OS OpenUPRN
40 972 229
N/A
AddressBase
30,618,207
160,698
AddressBase Plus
38,215,982
567,209
AddressBase Premium
See rows below
See rows below
Street
1,511,490
8,819
Street Descriptor
1,635,237
3,827
BLPU
40,972,229
351,639
Classification
44,804,485
156,612
LPI
46,177,196
155,834
Organisation
1,410,649
24,087
Delivery Point Address
30,726,626
75,116
Application Cross Ref.
198,600,667
735,324
Successor
0
0
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.
Change-Only Updates are not available for the OS Open UPRN product.
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.
AddressBase
30 618 207
30 618 207
0
AddressBase Plus
38 215 982
38 215 961
21
AddressBase Premium
See rows below
See rows below
See rows below
Street
1,511,490
1,511,487
3
Street Descriptor
1,635,237
1,635,234
3
BLPU
40,972,229
40,972,204
25
Classification
44,804,485
44,804,460
25
LPI
46,177,196
46,177,170
26
Organisation
1,410,649
1,410,647
2
Delivery Point Address
30,726,626
30,726,626
0
Application Cross Ref.
198,600,667
198,600,642
25
Successor
0
0
0
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.
Inserts
52 317
Updates
92 108
Deletes
16 273
COU Populated Tile Count
5 743
Inserts
47 492
Updates
498 918
Deletes
20 799
COU Populated Tile Count
7 094
Street
1,175
6,933
711
Street Descriptor
1,225
1,891
711
BLPU
40,941
299,115
11,583
Classification
49,447
77,489
29,676
LPI
54,934
88,243
12,657
Organisation
4,697
4,318
15,072
Delivery Point Address
48,355
15,438
11,323
Application Cross Ref.
203,570
460,627
71,127
The following information relates to the currency of the source data used in the creation of Epoch 115:
Royal Mail PAF
14 November 2024
National Land and Property Gazetteer
14 November 2024
One Scotland Gazetteer
28 October 2024
VOA Non-Domestic Rates
11 November 2024
VOA Council Tax
11 November 2024
OS MasterMap Topography Layer
05 November 2024
OS MasterMap Highways Network
07 November 2024
Code-Point with Polygons
01 October 2024
Boundary-Line
02 October 2024
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.
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.
Council tax
27 201 555
99.92
Non-domestic rates
2 119 490
96.49
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.
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:
The next release of AddressBase products, Epoch 116, is scheduled for 06 February 2025.
This release note provides information about the November 2024 release of the AddressBase Islands products. These products were released to customers on 07 November 2024.
AddressBase family product technical documentation (including technical specifications, release notes, getting started guides, etc.) is now available on the new OS Download Products’ Documentation Platform. 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.
Release notes for AddressBase products are available on the new platform; simply navigate to the new platform and click Addressing and location portfolio > AddressBase Core Principles > Release Notes. Static PDF release notes for the AddressBase products will be replaced by digital release notes on the new platform over the next few months.
AddressBase Plus Islands
1 152 075
7 952
AddressBase Premium Islands
See rows below
See rows below
Street
48 646
151
Street Descriptor
48 646
30
BLPU
1 235 836
9 106
Classification
1 235 836
5 652
LPI
1 245 520
3 980
Organisation
38 987
3 359
Delivery Point Address
964 605
776
Application Cross Ref.
1 301 968
1 577
Successor
0
0
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.
Inserts
869
Updates
6960
Deletes
123
Street
30
121
0
Street Descriptor
30
0
0
BLPU
619
8 444
43
Classification
619
4 990
43
LPI
735
3 202
43
Organisation
1 458
1 160
741
Delivery Point Address
538
184
54
Application Cross Ref.
749
713
115
Successor
0
0
0
The following information relates to the currency of the source data used in the creation of Epoch 114:
Pointer (Northern Ireland)
30 September 2024
DigiMap (Channel Islands)
03 October 2024
Isle of Man
03 October 2024
Royal Mail PAF
03 October 2024
There are no reported issues in this release of AddressBase Plus Islands.
Affected output formats: CSV and GML
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.
The next release of AddressBase Islands products, Epoch 115, is scheduled for 19 December 2024.
This release note provides information about the September 2024 release of the AddressBase products. These products were released to customers on 26 September 2024.
OS Open UPRN
40 909 714
N/A
AddressBase
30 552 484
137 772
AddressBase Plus
38 156 204
677 294
AddressBase Premium
See rows below
See rows below
Street
1 509 895
5 780
Street Descriptor
1 633 461
2 501
BLPU
40 909 714
355 256
Classification
44 758 076
125 856
LPI
46 089 180
182 176
Organisation
1 422 866
14 505
Delivery Point Address
30 659 580
54 376
Application Cross Ref.
198 307 242
735 178
Successor
0
0
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.
Change-Only Updates are not available for the OS Open UPRN product.
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.
AddressBase
30 552 484
30 552 484
0
AddressBase Plus
38 156 204
38 156 184
20
AddressBase Premium
See rows below
See rows below
See rows below
Street
1 509 895
1 509 892
3
Street Descriptor
1 633 461
1 633 458
3
BLPU
40 909 714
40 909 690
24
Classification
44 758 076
44 758 052
24
LPI
46 089 180
46 089 155
25
Organisation
1 422 866
1 422 864
2
Delivery Point Address
30 659 580
30 659 580
0
Application Cross Ref.
198 307 242
198 307 218
24
Successor
0
0
0
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.
Inserts
32 275
Updates
96 919
Deletes
8 578
COU Populated Tile Count
5 003
Inserts
43 451
Updates
621 151
Deletes
12 692
COU Populated Tile Count
7 088
Street
1 264
4 501
15
Street Descriptor
1 484
999
18
BLPU
39 273
312 858
3 125
Classification
47 617
59 927
18 312
LPI
51 254
127 306
3 616
Organisation
5 675
4 479
4 351
Delivery Point Address
32 839
13 224
8 313
Application Cross Ref.
183 150
520 267
31 761
The following information relates to the currency of the source data used in the creation of Epoch 113:
Royal Mail PAF
22 August 2024
National Land and Property Gazetteer
22 August 2024
One Scotland Gazetteer
05 August 2024
VOA Non-Domestic Rates
19 August 2024
VOA Council Tax
19 August 2024
OS MasterMap Topography Layer
13 August 2024
OS MasterMap Highways Network
06 August 2024
Code-Point with Polygons
01 July 2024
Boundary-Line
24 June 2024
Affected output formats: CSV and GML
There are 6 504 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 227 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.
The match rates for Council Tax and Non-Domestic Rates for Epoch 113 are detailed as follows based on Valuation Office Agency (VOA) records up to 19 August 2024. The match rate is applicable to the AddressBase Premium product.
Council tax
27 145 616
99.92
Non-domestic rates
2 122 260
96.47
Work is being undertaken to improve the classifications of records within the AddressBase products. This work has resulted in 37 159 more tertiary classifications present in Epoch 113 compared to Epoch 112. Indeed, 88.71% of these tertiary classification improvements are against residential codes.
The following graph shows the number of Postcode Address File (PAF) matched records in AddressBase by epoch:
The next release of AddressBase products, Epoch 114, is scheduled for 07 November 2024.
This release note provides information about the December 2024 release of the AddressBase Islands products. These products were released to customers on 19 December 2024.
AddressBase Plus Islands
1 153 050
4 262
AddressBase Premium Islands
See rows below
See rows below
Street
48,676
112
Street Descriptor
48,676
32
BLPU
1,236,926
4,892
Classification
1,236,926
2,348
LPI
1,246,637
3,017
Organisation
38,858
231
Delivery Point Address
965,179
1,081
Application Cross Ref.
1,302,955
2,789
Successor
0
0
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.
Inserts
1 275
Updates
2 687
Deletes
300
Street
30
82
0
Street Descriptor
30
2
0
BLPU
1,272
3,438
182
Classification
1,272
894
182
LPI
1,299
1,536
182
Organisation
37
28
166
Delivery Point Address
666
323
92
Application Cross Ref.
1,291
1,194
304
Successor
0
0
0
The following information relates to the currency of the source data used in the creation of Epoch 115:
Pointer (Northern Ireland)
14 November 2024
DigiMap (Channel Islands)
14 November 2024
Isle of Man
14 November 2024
Royal Mail PAF
14 November 2024
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.
The next release of AddressBase products, Epoch 116, is scheduled for 06 February 2025.
This release note provides information about the November 2024 (Epoch 114) release of the AddressBase products. These products were released to customers on 07 November 2024.
AddressBase family product technical documentation (including technical specifications, release notes, getting started guides, etc.) is now available on the new OS Download Products’ Documentation Platform. 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.
Release notes for AddressBase products are available on the new platform; simply navigate to the new platform and click Addressing and location portfolio > AddressBase Core Principles > Release Notes. Static PDF release notes for the AddressBase products will be replaced by digital release notes on the new platform over the next few months.
OS OpenUPRN
40 942 871
N/A
AddressBase
30 582 163
141 175
AddressBase Plus
38 189 289
575 982
AddressBase Premium
See rows below
See rows below
Street
1 511 026
10 216
Street Descriptor
1 634 723
3 405
BLPU
40 942 871
281 573
Classification
44 784 714
114 548
LPI
46 134 919
134 455
Organisation
1 421 024
13 457
Delivery Point Address
30 689 594
60 166
Application Cross Ref.
198 468 224
739 827
Successor
0
0
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.
Change-Only Updates are not available for the OS Open UPRN product.
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.
AddressBase
30 582 163
30 582 163
0
AddressBase Plus
38 189 289
38 189 268
21
AddressBase Premium
See rows below
See rows below
See rows below
Street
1 511 026
1 511 024
2
Street Descriptor
1 634 723
1 634 721
2
BLPU
40 942 871
40 942 846
25
Classification
44 784 714
44 784 689
25
LPI
46 134 919
46 134 893
26
Organisation
1 421 024
1 421 022
2
Delivery Point Address
30 689 594
30 689 594
0
Application Cross Ref.
198 468 224
198 468 199
25
Successor
0
0
0
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.
Inserts
39 785
Updates
91 284
Deletes
10 106
COU Populated Tile Count
5 139
Inserts
47 501
Updates
514 065
Deletes
14 416
COU Populated Tile Count
7 133
Street
1 372
8 603
241
Street Descriptor
1 503
1 661
241
BLPU
38 154
238 422
4 997
Classification
46 915
47 356
20 277
LPI
51 599
76 996
5 860
Organisation
3 892
3 831
5 734
Delivery Point Address
39 984
10 212
9 970
Application Cross Ref.
202 342
496 125
41 360
The following information relates to the currency of the source data used in the creation of Epoch 114:
Royal Mail PAF
03 October 2024
National Land and Property Gazetteer
03 October 2024
One Scotland Gazetteer
16 September 2024
VOA Non-Domestic Rates
01 October 2024
VOA Council Tax
01 October 2024
OS MasterMap Topography Layer
24 September 2024
OS MasterMap Highways Network
03 October 2024
Code-Point with Polygons
01 October 2024
Boundary-Line
02 October 2024
Affected output formats: CSV and GML
There are 6 038 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 211 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.
The match rates for Council Tax and Non-Domestic Rates for Epoch 114 are detailed as follows based on Valuation Office Agency (VOA) records up to 01 October 2024. The match rate is applicable to the AddressBase Premium product.
Council tax
27 171 964
99.92
Non-domestic rates
2 121 757
96.47
Work is being undertaken to improve the classifications of records within the AddressBase products. This work has resulted in 37 159 more tertiary classifications present in Epoch 114 compared to Epoch 113. Indeed, 88.71% of these tertiary classification improvements are against residential codes.
The following graph shows the number of Postcode Address File (PAF) matched records in AddressBase by epoch:
The next release of AddressBase products, Epoch 115, is scheduled for 19 December 2024.
This release note provides information about the June 2024 release of the AddressBase Islands products. These products were released to customers on 27 June 2024.
AddressBase Plus Islands
1 149 262
3 099
AddressBase Premium Islands
See rows below
See rows below
Street
48 531
102
Street Descriptor
48 531
24
BLPU
1 232 949
3 646
Classification
1 232 949
2 043
LPI
1 242 438
2 699
Organisation
38 951
130
Delivery Point Address
963 434
673
Application Cross Ref.
1 299 124
1 759
Successor
0
0
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.
Inserts
1 124
Updates
1 816
Deletes
159
Street
23
78
1
Street Descriptor
23
0
1
BLPU
1 159
2 408
79
Classification
1 159
805
79
LPI
1 236
1 384
79
Organisation
18
25
87
Delivery Point Address
466
133
74
Application Cross Ref.
1 181
463
115
The following information relates to the currency of the source data used in the creation of Epoch 111:
Pointer (Northern Ireland)
22 May 2024
DigiMap (Channel Islands)
12 May 2024
Isle of Man
23 May 2024
Royal Mail PAF
23 May 2024
There are no reported issues in this release of AddressBase Plus Islands.
Affected output formats: CSV and GML
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.
The next release of AddressBase Islands products, Epoch 112, is scheduled for 15 August 2024.
This release note provides information about the June 2024 release of the AddressBase products. These products were released to customers on 27 June 2024.
OS OpenUPRN
40 825 714
N/A
AddressBase
30 492 698
123 335
AddressBase Plus
38 082 637
2 269 935
AddressBase Premium
See rows below
See rows below
Street
1 507 301
5 983
Street Descriptor
1 630 431
3 057
BLPU
40 825 714
345 400
Classification
44 684 909
124 243
LPI
45 978 659
140 285
Organisation
1 422 087
17 612
Delivery Point Address
30 598 226
59 126
Application Cross Ref.
197 964 510
4 430 729
Successor
0
0
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.
Change-Only Updates are not available for the OS Open UPRN product.
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.
AddressBase
30 492 698
30 492 698
0
AddressBase Plus
38 082 637
38 082 617
20
AddressBase Premium
See rows below
See rows below
See rows below
Street
1 507 301
1 507 299
2
Street Descriptor
1 630 431
1 630 429
2
BLPU
40 825 714
40 825 690
24
Classification
44 684 909
44 684 885
24
LPI
45 978 659
45 978 634
25
Organisation
1 422 087
1 422 085
2
Delivery Point Address
30 598 226
30 598 226
0
Application Cross Ref.
197 964 510
197 964 486
24
Successor
0
0
0
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.
Inserts
33 506
Updates
80 002
Deletes
9 827
COU Populated Tile Count
5 140
Inserts
45 949
Updates
2 210 934
Deletes
13 052
COU Populated Tile Count
7 162
Street
1 515
4 445
23
Street Descriptor
1 715
1 318
24
BLPU
45 313
296 305
3 782
Classification
54 659
51 341
18 243
LPI
60 087
75 180
5 018
Organisation
7 895
4 900
4 817
Delivery Point Address
33 606
16 076
9 444
Application Cross Ref.
2 114 566
373 554
1 942 609
The following information relates to the currency of the source data used in the creation of Epoch 111:
Royal Mail PAF
23 May 2024
National Land and Property Gazetteer
23 May 2024
One Scotland Gazetteer
06 May 2024
VOA Non-Domestic Rates
20 May 2024
VOA Council Tax
20 May 2024
OS MasterMap Topography Layer
14 May 2024
OS MasterMap Highways Network
07 May 2024
Code-Point with Polygons
04 January 2024
Boundary-Line
01 May 2023
Affected output formats: CSV and GML
There are 6 189 Unique Property Reference Numbers (UPRNs) which reference a Parent UPRN which 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 254 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 product.
The match rates for Council Tax and Non-Domestic Rates for Epoch 111 are detailed as follows based on Valuation Office Agency (VOA) records up to 20th May 2024. The match rate is applicable to the AddressBase Premium product.
Council Tax
27 084 483
99.94
Non-Domestic Rates
2 123 193
96.48
Work is being undertaken to improve the classifications of records within the AddressBase products. This work has resulted in 40 932 more tertiary classifications present in Epoch 111 compared to Epoch 110. Indeed, 88.74% of these tertiary classification improvements are against residential codes.
The following graph shows the number of Postcode Address File (PAF) matched records in AddressBase by epoch:
The next release of AddressBase products, Epoch 112, is scheduled for 15 August 2024.
This release note provides information about the May 2024 release of the AddressBase Islands products. These products were released to customers on 16 May 2024.
AddressBase Plus Islands
1 148 297
6 260
AddressBase Premium Islands
See rows below
See rows below
Street
48 509
177
Street Descriptor
48 509
39
BLPU
1 231 869
6 886
Classification
1 231 869
4 164
LPI
1 241 281
5 197
Organisation
39 020
523
Delivery Point Address
963 042
846
Application Cross Ref.
1 298 058
2 522
Successor
0
0
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.
Inserts
1 688
Updates
4 057
Deletes
515
Street
35
141
1
Street Descriptor
35
3
1
BLPU
1 283
5 369
234
Classification
1 283
2 647
234
LPI
1 324
3 639
234
Organisation
93
85
345
Delivery Point Address
454
189
203
Application Cross Ref.
1 347
787
388
The following information relates to the currency of the source data used in the creation of Epoch 110:
Pointer (Northern Ireland)
10 April 2024
DigiMap (Channel Islands)
11 April 2024
Isle of Man
11 April 2024
Royal Mail PAF
11 April 2024
There are no reported issues in this release of AddressBase Plus Islands.
Affected output formats: CSV and GML
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.
The next release of AddressBase Islands products, Epoch 111, is scheduled for 27 June 2024.
This release note provides information about the April 2024 release of the AddressBase products. These products were released to customers on 05 April 2024.
OS OpenUPRN
40 744 085
N/A
AddressBase
30 440 058
141 664
AddressBase Plus
38 013 634
641 116
AddressBase Premium
See rows below
See rows below
Street
1 504 346
5 403
Street Descriptor
1 627 151
2 603
BLPU
40 744 085
1 651 993
Classification
44 612 110
167 219
LPI
45 869 982
152 914
Organisation
1 415 880
17 270
Delivery Point Address
30 544 920
69 763
Application Cross Ref.
197 640 540
614 650
Successor
0
0
Change-Only Updates are not available for the OS Open UPRN product.
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.
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.
AddressBase
30 440 058
30 440 058
0
AddressBase Plus
38 013 634
38 013 615
19
AddressBase Premium
See rows below
See rows below
See rows below
Street
1 504 346
1 504 345
1
Street Descriptor
1 627 151
1 627 150
1
BLPU
40 744 085
40 744 062
23
Classification
44 612 110
44 612 087
23
LPI
45 869 982
45 869 958
24
Organisation
1 415 880
1 415 878
2
Delivery Point Address
30 544 920
30 544 920
0
Application Cross Ref.
197 640 540
197 640 517
23
Successor
0
0
0
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.
Inserts
38 002
Updates
91 196
Deletes
12 466
COU Populated Tile Count
5 410
Inserts
55 152
Updates
571 494
Deletes
14 470
COU Populated Tile Count
7 157
Street
1 560
3 826
17
Street Descriptor
1 603
982
18
BLPU
54 407
1 594 091
3 495
Classification
68 978
75 921
22 320
LPI
67 818
80 668
4 428
Organisation
7 066
5 090
5 114
Delivery Point Address
38 799
18 094
12 870
Application Cross Ref.
225 972
348 380
40 298
The following information relates to the currency of the source data used in the creation of Epoch 109:
Data Source
Date
Royal Mail PAF
01 March 2024
National Land and Property Gazetteer
01 March 2024
One Scotland Gazetteer
12 February 2024
VOA Non-Domestic Rates
26 February 2024
VOA Council Tax
26 February 2024
OS MasterMap Topography Layer
20 February 2024
OS MasterMap Highways Network
06 February 2024
Code-Point with Polygons
04 January 2024
Boundary-Line
03 October 2023
Affected output formats: CSV and GML
There are 5 021 Unique Property Reference Numbers (UPRNs) which reference a Parent UPRN which 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 254 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 product.
The match rates for Council Tax and Non-Domestic Rates for Epoch 109 are detailed as follows based on Valuation Office Agency (VOA) records up to 26 February 2024. The match rate is applicable to the AddressBase Premium product.
Data Source
Records Received
% Matched
Council Tax
27 033 727
99.95
Non-Domestic Rates
2 120 769
96.58
Work is being undertaken to improve the classifications of records within the AddressBase products. This work has resulted in 47 161 more tertiary classifications present in Epoch 109 compared to Epoch 108. Indeed, 88.77% of these tertiary classification improvements are against residential codes.
The following graph shows the number of Postcode Address File (PAF) matched records in AddressBase by epoch:
This release includes an enhancement in the clarity and consistency of lifecycle representation within product.
A conformance improvement has been delivered for BLPU State attribute for records where the BLPU Logical Status was 8 (historic) and BLPU State was null; for increased completeness, BLPU State Code has been populated with value 4 (no longer existing) and date stamped for the change applied.
The BLPU state identifies the current lifecycle stage of a property (or object) and is additional to the mandatory LOGICAL_ STATUS field.
The BLPU code is an optional attribute for Local Authority Custodians to complete and therefore this attribute may be NULL in product.
An improvement to the completeness of the BLPU State Code was identified as a quality enhancement for lifecycle information as values for BLPU state code 4 can be accurately inferred from a Logical Status of 8. This enhancement allows the data to be interpreted more easily by removing conflict between addresses with a historic logical status and no BLPU state.
All nations within GB and the Islands product regions will benefit from this improvement, as such, it impacts approximately 1.2 million records for a Full Supply.
This quality improvement means a larger than usual supply of COUs in this release.
The next release of AddressBase products, Epoch 110, is scheduled for 16 May 2024.
This release note provides information about the September 2024 release of the AddressBase Islands products. These products were released to customers on 26 September 2024.
AddressBase Plus Islands
1 151 329
4 703
AddressBase Premium Islands
See rows below
See rows below
Street
48 616
162
Street Descriptor
48 616
45
BLPU
1 235 260
5 216
Classification
1 235 260
2 378
LPI
1 244 828
3 229
Organisation
38 270
181
Delivery Point Address
964 121
1 018
Application Cross Ref.
1 301 334
3 067
Successor
0
0
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.
Inserts
1 531
Updates
2 916
Deletes
256
Street
45
117
0
Street Descriptor
45
0
0
BLPU
1 523
3 481
212
Classification
1 523
643
212
LPI
1 587
1 430
212
Organisation
53
25
103
Delivery Point Address
605
293
120
Application Cross Ref.
1 538
1 261
268
Successor
0
0
0
The following information relates to the currency of the source data used in the creation of Epoch 113:
Data Source
Date
Pointer (Northern Ireland)
22 August 2024
DigiMap (Channel Islands)
22 August 2024
Isle of Man
21 August 2024
Royal Mail PAF
22 August 2024
There are no reported issues in this release of AddressBase Plus Islands.
Affected output formats: CSV and GML
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.
The next release of AddressBase Islands products, Epoch 114, is scheduled for 07 November 2024.
This release note provides information about the February 2024 (Epoch 108) release of the AddressBase products. These products were released to customers on 22 February 2024.
OS Open UPRN
40 693 173
N/A
AddressBase
30 414 522
136 905
AddressBase Plus
37 972 952
514 790
AddressBase Premium
See rows below
See rows below
Street
1 502 803
4 442
Street Descriptor
1 625 566
2 273
BLPU
40 693 173
324 380
Classification
44 565 452
166 679
LPI
45 806 592
148 634
Organisation
1 413 928
18 423
Delivery Point Address
30 518 991
69 821
Application Cross Ref.
197 454 866
681 108
Successor
0
0
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.
Change-Only Updates are not available for the OS Open UPRN product.
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.
AddressBase
30 414 522
30 414 522
0
AddressBase Plus
37 972 952
37 972 933
19
AddressBase Premium
See rows below
See rows below
See rows below
Street
1 502 803
1 502 800
3
Street Descriptor
1 625 566
1 625 563
3
BLPU
40 693 173
40 693 150
23
Classification
44 565 452
44 565 429
23
LPI
45 806 592
45 806 568
24
Organisation
1 413 928
1 413 926
2
Delivery Point Address
30 518 991
30 518 991
0
Application Cross Ref.
197 454 866
197 454 843
23
Successor
0
0
0
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.
Inserts
40 648
Updates
83 486
Deletes
12 771
COU Populated Tile Count
5 305
Inserts
60 179
Updates
438 033
Deletes
16 578
COU Populated Tile Count
7 274
Street
1 072
3 357
13
Street Descriptor
1 247
1 011
15
BLPU
53 653
265 882
4 845
Classification
68 326
74 757
23 596
LPI
68 513
74 368
5 753
Organisation
7 404
5 298
5 721
Delivery Point Address
41 237
15 780
12 804
Application Cross Ref.
225 943
414 146
41 019
The following information relates to the currency of the source data used in the creation of Epoch 108:
Royal Mail PAF
18 January 2024
National Land and Property Gazetteer
18 January 2024
One Scotland Gazetteer
18 December 2023
VOA Non-Domestic Rates
14 January 2024
VOA Council Tax
14 January 2024
OS MasterMap Topography Layer
09 January 2024
OS MasterMap Highways Network
08 January 2024
Code-Point with Polygons
04 January 2024
Boundary-Line
03 October 2023
Affected output formats: CSV and GML
There are 6 781 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 279 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.
The match rates for Council Tax and Non-Domestic Rates for Epoch 108 are detailed as follows based on Valuation Office Agency (VOA) records up to 15 January 2024. The match rate is applicable to the AddressBase Premium product.
Council tax
27 021 839
99.92
Non-domestic rates
2 127 215
96.36
Work is being undertaken to improve the classifications of records within the AddressBase products. This work has resulted in 49 778 more tertiary classifications present in Epoch 108 compared to Epoch 107. Indeed, 88.78% of these tertiary classification improvements are against residential codes.
The following graph shows the number of Postcode Address File (PAF) matched records in AddressBase by epoch:
The release will enhance clarity and consistency of lifecycle representation within product.
A conformance improvement will be delivered for BLPU State attribute for records where the BLPU Logical Status is 8 (historic) and BLPU State is null; for increased completeness, BLPU State Code will be populated with value 4 (no longer existing) and date stamped for the change applied.
The BLPU state identifies the current lifecycle stage of a property (or object) and is additional to the mandatory LOGICAL_ STATUS field.
The BLPU code is an optional attribute for Local Authority Custodians to complete and therefore this attribute may be NULL in product.
An improvement to the completeness of the BLPU State Code was identified as a quality enhancement for lifecycle information as values for BLPU state code 4 can be accurately inferred from a Logical Status of 8. This will allow the data to be interpreted more easily by removing conflict between addresses with a historic logical status and no BLPU state.
All nations within GB and the Islands product regions will benefit from this improvement, as such, it will impact approximately 1.2 million records for a Full Supply.
This quality improvement will be delivered in the next release, Epoch 109, and will mean a larger than usual supply of changes.
No special action will be required to load the release differently.
The next release of AddressBase products, Epoch 109, is scheduled for Tuesday 05 April 2024.
This release note provides information about the January 2024 (Epoch 107) release of the AddressBase products. These products were released to customers on 05 January 2024.
OS Open UPRN
40 644 365
N/A
AddressBase
30 386 645
114 610
AddressBase Plus
37 929 351
524 249
AddressBase Premium
See rows below
See rows below
Street
1 501 744
6 055
Street Descriptor
1 624 334
3 329
BLPU
40 644 365
275 951
Classification
44 520 722
134 122
LPI
45 743 832
216 160
Organisation
1 412 245
16 196
Delivery Point Address
30 490 558
55 388
Application Cross Ref.
197 269 942
627 070
Successor
0
0
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.
Change-Only Updates are not available for the OS Open UPRN product.
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.
AddressBase
30 386 645
30 386 645
0
AddressBase Plus
37 929 351
37 929 332
19
AddressBase Premium
See rows below
See rows below
See rows below
Street
1 501 744
1 501 743
1
Street Descriptor
1 624 334
1 624 333
1
BLPU
40 644 365
40 644 342
22
Classification
44 520 722
44 520 699
23
LPI
45 743 832
45 743 808
24
Organisation
1 412 245
1 412 243
2
Delivery Point Address
30 490 558
30 490 558
0
Application Cross Ref.
197 269 942
197 269 919
23
Successor
0
0
0
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.
Inserts
37 526
Updates
68 614
Deletes
8 470
COU Populated Tile Count
5 275
Inserts
54 062
Updates
458 759
Deletes
11 428
COU Populated Tile Count
7 261
Street
2 426
3 610
19
Street Descriptor
2 636
674
19
BLPU
52 904
220 510
2 537
Classification
63 653
51 535
18 934
LPI
68 427
144 366
3 367
Organisation
6 628
4 466
5 102
Delivery Point Address
37 813
9 405
8 170
Application Cross Ref.
227 465
370 122
29 483
The following information relates to the currency of the source data used in the creation of Epoch 107:
Royal Mail PAF
30 November 2023
National Land and Property Gazetteer
30 November 2023
One Scotland Gazetteer
30 November 2023
VOA Non-Domestic Rates
27 November 2023
VOA Council Tax
27 November 2023
OS MasterMap Topography Layer
21 November 2023
OS MasterMap Highways Network
06 November 2023
Code-Point with Polygons
02 October 2023
Boundary-Line
03 October 2023
Affected output formats: CSV and GML
There are 7 416 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 273 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.
The match rates for Council Tax and Non-Domestic Rates for Epoch 107 are detailed as follows based on Valuation Office Agency (VOA) records up to 27 November 2023. The match rate is applicable to the AddressBase Premium product.
Council tax
26 995 187
99.92
Non-domestic rates
2 129 321
96.33
Work is being undertaken to improve the classifications of records within the AddressBase products. This work has resulted in 56 205 more tertiary classifications present in Epoch 107 compared to Epoch 106. Indeed, 88.79% of these tertiary classification improvements are against residential codes.
The following graph shows the number of Postcode Address File (PAF) matched records in AddressBase by epoch:
We have introduced new tertiary and quaternary classification codes to the AddressBase classification scheme. The new tertiary classification for pharmacies and a number of additional quaternary classifications provides a more granular view for pubs, supermarkets, convenience stores and electric vehicle charging points. This makes these classes easier to filter in AddressBase.
We have also introduced additional classifications for bridges within AddressBase to represent the type of feature the bridge spans over. This helps to facilitate effective decision making for customers who use bridge features.
C
M
06
Pharmacy
–
–
C
R
06
–
BA
Bar
C
R
06
–
PH
Public House
C
R
06
–
NC
Nightclub
C
R
08
–
SM
Supermarket
C
R
08
–
CS
Convenience Store
C
R
09
–
BS
Betting Shop
C
R
09
–
OL
Off-licence
C
R
02
–
EV
Electric Car Charging Station
C
T
11
–
CA
Road Bridge Over Canal
C
T
11
–
MU
Road Bridge Over Multiple
C
T
11
–
NN
Road Bridge Over No Network
C
T
11
–
PA
Road Bridge Over Path
C
T
11
–
RA
Road Bridge Over Railway
C
T
11
–
RO
Road Bridge Over Road
C
T
11
–
WA
Road Bridge Over Water
This change to the classification schema was implemented in Epoch 100, which was published on 30 March 2023. From this date, these new tertiary and quaternary classification codes have been included in AddressBase products.
In our addressing products, we provide information detailing which local authority an address is within. From 01 April 2023, several local authorities reorganised to form new authorities. This means that the local authority code for all addresses within the affected authorities changed from the old authority to the new one, resulting in approximately 1.3 million records being updated. These changes will be seen in product from Epoch 101 onwards. The table below maps the changes:
Allerdale – 905
Cumberland – 940
Carlisle – 915
Cumberland – 940
Copeland – 920
Cumberland – 940
Barrow-in-Furness – 910
Westmorland and Furness – 935
Eden – 925
Westmorland and Furness – 935
South Lakeland – 930
Westmorland and Furness – 935
Scarborough – 2730
North Yorkshire – 2745
Ryedale – 2725
North Yorkshire – 2745
Selby – 2735
North Yorkshire – 2745
Hambleton – 2710
North Yorkshire – 2745
Richmondshire – 2720
North Yorkshire – 2745
Harrogate – 2715
North Yorkshire – 2745
Craven – 2705
North Yorkshire – 2745
Mendip – 3305
Somerset – 3300
Sedgemoor – 3310
Somerset – 3300
Somerset West and Taunton – 3330
Somerset – 3300
South Somerset – 3325
Somerset – 3300
The next release of AddressBase products, Epoch 108, is scheduled for Thursday 22 February 2024.
This release note provides information about the November 2023 (Epoch 106) release of the AddressBase products. These products were released to customers on 23 November 2023.
OS Open UPRN
40 593 998
N/A
AddressBase
30 357 589
138 214
AddressBase Plus
37 886 717
642 897
AddressBase Premium
See rows below
See rows below
Street
1 499 337
4 548
Street Descriptor
1 621 717
1 649
BLPU
40 593 998
326 208
Classification
44 476 003
150 495
LPI
45 678 772
139 837
Organisation
1 410 719
14 194
Delivery Point Address
30 460 915
66 081
Application Cross Ref.
197 071 960
896 913
Successor
0
0
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.
Change-Only Updates are not available for the OS Open UPRN product.
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.
AddressBase
30 357 589
30 357 589
0
AddressBase Plus
37 886 717
37 886 697
20
AddressBase Premium
See rows below
See rows below
See rows below
Street
1 499 337
1 499 336
1
Street Descriptor
1 621 717
1 621 716
1
BLPU
40 593 998
40 593 974
24
Classification
44 476 003
44 475 979
24
LPI
45 678 772
45 678 747
25
Organisation
1 410 719
1 410 717
2
Delivery Point Address
30 460 915
30 460 915
0
Application Cross Ref.
197 071 960
197 071 936
24
Successor
0
0
0
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.
Inserts
40 457
Updates
85 345
Deletes
12 412
COU Populated Tile Count
5 846
Inserts
50 344
Updates
578 627
Deletes
13 926
COU Populated Tile Count
7 335
Street
1 067
3 443
38
Street Descriptor
1 123
486
40
BLPU
49 289
274 081
2 838
Classification
60 725
70 547
19 223
LPI
65 573
70 173
4 091
Organisation
5 928
4 512
3 754
Delivery Point Address
39 147
16 146
10 788
Application Cross Ref.
392 254
384 136
120 523
The following information relates to the currency of the source data used in the creation of Epoch 106:
Royal Mail PAF
19 October 2023
National Land and Property Gazetteer
19 October 2023
One Scotland Gazetteer
19 October 2023
VOA Non-Domestic Rates
15 October 2023
VOA Council Tax
15 October 2023
OS MasterMap Topography Layer
10 October 2023
OS MasterMap Highways Network
06 October 2023
Code-Point with Polygons
02 October 2023
Boundary-Line
03 October 2023
Affected output formats: CSV and GML
There are 7 419 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 268 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.
The match rates for Council Tax and Non-Domestic Rates for Epoch 106 are detailed as follows based on Valuation Office Agency (VOA) records up to 16 October 2023. The match rate is applicable to the AddressBase Premium product.
Council tax
26 964 499
99.92
Non-domestic rates
2 130 955
96.32
Work is being undertaken to improve the classifications of records within the AddressBase products. This work has resulted in 55 276 more tertiary classifications present in Epoch 106 compared to Epoch 105. Indeed, 88.8% of these tertiary classification improvements are against residential codes..
The following graph shows the number of Postcode Address File (PAF) matched records in AddressBase by epoch:
We have introduced new tertiary and quaternary classification codes to the AddressBase classification scheme. The new tertiary classification for pharmacies and a number of additional quaternary classifications provides a more granular view for pubs, supermarkets, convenience stores and electric vehicle charging points. This makes these classes easier to filter in AddressBase.
We have also introduced additional classifications for bridges within AddressBase to represent the type of feature the bridge spans over. This helps to facilitate effective decision making for customers who use bridge features.
C
M
06
Pharmacy
–
–
C
R
06
–
BA
Bar
C
R
06
–
PH
Public House
C
R
06
–
NC
Nightclub
C
R
08
–
SM
Supermarket
C
R
08
–
CS
Convenience Store
C
R
09
–
BS
Betting Shop
C
R
09
–
OL
Off-licence
C
R
02
–
EV
Electric Car Charging Station
C
T
11
–
CA
Road Bridge Over Canal
C
T
11
–
MU
Road Bridge Over Multiple
C
T
11
–
NN
Road Bridge Over No Network
C
T
11
–
PA
Road Bridge Over Path
C
T
11
–
RA
Road Bridge Over Railway
C
T
11
–
RO
Road Bridge Over Road
C
T
11
–
WA
Road Bridge Over Water
This change to the classification schema was implemented in Epoch 100, which was published on 30 March 2023. From this date, these new tertiary and quaternary classification codes have been included in AddressBase products.
In our addressing products, we provide information detailing which local authority an address is within. From 01 April 2023, several local authorities reorganised to form new authorities. This means that the local authority code for all addresses within the affected authorities changed from the old authority to the new one, resulting in approximately 1.3 million records being updated. These changes will be seen in product from Epoch 101 onwards. The table below maps the changes:
Allerdale – 905
Cumberland – 940
Carlisle – 915
Cumberland – 940
Copeland – 920
Cumberland – 940
Barrow-in-Furness – 910
Westmorland and Furness – 935
Eden – 925
Westmorland and Furness – 935
South Lakeland – 930
Westmorland and Furness – 935
Scarborough – 2730
North Yorkshire – 2745
Ryedale – 2725
North Yorkshire – 2745
Selby – 2735
North Yorkshire – 2745
Hambleton – 2710
North Yorkshire – 2745
Richmondshire – 2720
North Yorkshire – 2745
Harrogate – 2715
North Yorkshire – 2745
Craven – 2705
North Yorkshire – 2745
Mendip – 3305
Somerset – 3300
Sedgemoor – 3310
Somerset – 3300
Somerset West and Taunton – 3330
Somerset – 3300
South Somerset – 3325
Somerset – 3300
The next release of AddressBase products, Epoch 107, is scheduled for Friday 05 January 2024.
This release note provides information about the August 2024 release of the AddressBase Islands products. These products were released to customers on 15 August 2024.
AddressBase Plus Islands
1 150 054
4433
AddressBase Premium Islands
See rows below
See rows below
Street
48 571
165
Street Descriptor
48 571
40
BLPU
1 233 949
5281
Classification
1 233 949
2 967
LPI
1 243 453
3 693
Organisation
38 320
804
Delivery Point Address
963 636
1 252
Application Cross Ref.
1 300 064
1 812
Successor
0
0
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.
Inserts
1 106
Updates
3 013
Deletes
314
Street
40
125
0
Street Descriptor
40
0
0
BLPU
1 185
3 911
185
Classification
1 185
1 597
185
LPI
1 200
2 308
185
Organisation
52
69
683
Delivery Point Address
601
252
399
Application Cross Ref.
1 162
428
222
Successor
0
0
0
The following information relates to the currency of the source data used in the creation of Epoch 112:
Pointer (Northern Ireland)
11 July 2024
DigiMap (Channel Islands)
04 July 2024
Isle of Man
11 July 2024
Royal Mail PAF
11 July 2024
There are no reported issues in this release of AddressBase Plus Islands.
Affected output formats: CSV and GML
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.
The next release of AddressBase Islands products, Epoch 113, is scheduled for 26 September 2024.
Through collaborative working between Ordnance Survey, GeoPlace, the Local Government Agency and Improvement Service, a single definitive spatial address database for Great Britain has been created and maintained since September 2011 for England and Wales, and April 2012 for Scotland.
This initiative supports the UK Location Strategy concept of a 'core reference geography', including the key principles of the European Union INSPIRE directive, that data should only be collected once and kept where it can be maintained most effectively.
The creation of AddressBase products brings together the best parts of:
The National Land and Property Gazetteer (NLPG) provides the most up-to-date addresses including street names and numbers from each Local Authority’s LLPG in England and Wales. This data also provides a Unique Property Reference Number (UPRN) for each address encompassing residential, commercial and public infrastructure such as fire stations.
One Scotland Address Gazetteer (OSG) provides the most up-to-date addresses including street names and numbers from each Scottish Local Authority’s CAG. This data also provides a Unique Property Reference Number (UPRN) for each address encompassing residential, commercial and public infrastructure such as fire stations.
Ordnance Survey provides a wide range of additional addresses including Objects Without a Postal Address (OWPAs) such as Telephone Exchanges, a wider spatial context by including references for both the OS MasterMap Topography Layer and OS MasterMap Highways Networks Layer which the address feature is related to and additional classification information.
PAF contains approximately 30 million Royal Mail addresses that are identified as receiving post in Great Britain. Addresses from the NLPG and OSG are matched to the PAF addresses to provide the Unique Delivery Point Reference Number (UDPRN) into product and supplement the Local Authority address with information such as organisation name, postal town and postcode.
The Valuation Office Agency (VOA) gives the government the valuations and property advice needed to support taxation and benefits within England and Wales. Addresses from the NLPG are matched to the VOA address to provide the Unique Address Reference Number (UARN), VOA Special Category and Primary Description classification codes in product.
GeoPlace is a limited liability partnership jointly owned by the Local Government Association and Ordnance Survey and is the centre of excellence for spatial address and street information in Great Britain. GeoPlace brings together local government's address and streets gazetteers with information from Ordnance Survey, Improvement Service, Royal Mail’s PAF dataset and VOA addresses into a central spatial address data hub. The database hub is updated by GeoPlace based upon the receipt of data from all the contributing data sources.
GeoPlace manage this hub and provide address and street information to be utilised in the AddressBase products.
At present, there are 314 local authorities in England and Wales, inputting updates to their Local Land and Property Gazetteers (LLPG). These changes are submitted to the GeoPlace Hub daily, weekly or monthly as part of their update schedule.
On receipt of these updates, they are checked to ensure that they have been produced in accordance with the NLPG Data Entry Conventions and they are in compliance with the national standard for the representation of address information – BS 7666 Parts 1 and 2.
There are currently 32 local authorities in Scotland which update their local address gazetteers on a daily, weekly or monthly as part of their update schedule to the OSG. The Improvement Service check each
update to ensure compliance with the national standard for addressing (BS7666.2006) and the Scottish Gazetteer Conventions 1-3.
One of the key strengths of AddressBase products is the collection and verification of data at the local level. A real benefit is the capture of addresses at the earliest point in their lifecycle, and then this address being maintained by the local authority.
To do this the Local Custodians will utilise the wealth of information at their disposal until the address is demolished (when it becomes a historical record).
Local Custodians will use information such as:
Building and Development control
Planning and Land Charges
Waste Collection
Electoral Roll
LLPG custodians (England and Wales) are allocated sequential batches of UPRNs by GeoPlace, which are assigned by the LLPG custodian at the creation of a new address.
The OSG (Scotland) custodians are allocated sequential batches of UPRNs by the Improvement Service, which are assigned by the OSG custodian at the creation of a new address.
This release note provides information about the April 2024 release of the AddressBase Islands products. These products were released to customers on 05 April 2024.
AddressBase Plus Islands
1 147 124
172 849
AddressBase Premium Islands
See rows below
See rows below
Street
48 475
150
Street Descriptor
48 475
49
BLPU
1 230 820
181 155
Classification
1 230 820
2 205
LPI
1 240 191
2 448
Organisation
39 272
117
Delivery Point Address
962 791
2 622
Application Cross Ref.
1 297 099
2 408
Successor
0
0
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.
Inserts
994
Updates
171 443
Deletes
412
Street
49
101
0
Street Descriptor
49
0
0
BLPU
1 412
179 670
73
Classification
1 412
720
73
LPI
1 424
951
73
Organisation
7
21
89
Delivery Point Address
1 205
652
765
Application Cross Ref.
1 400
872
136
The following information relates to the currency of the source data used in the creation of Epoch 108:
Pointer (Northern Ireland)
28 February 2024
DigiMap (Channel Islands)
29 February 2024
Isle of Man
29 February 2024
Royal Mail PAF
28 February 2024
There are no reported issues in this release of AddressBase Plus Islands.
Affected output formats: CSV and GML
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.
This release includes an enhancement in the clarity and consistency of lifecycle representation within product.
A conformance improvement has been delivered for BLPU State attribute for records where the BLPU Logical Status was 8 (historic) and BLPU State was null; for increased completeness, BLPU State Code has been populated with value 4 (no longer existing) and date stamped for the change applied.
The BLPU state identifies the current lifecycle stage of a property (or object) and is additional to the mandatory LOGICAL_ STATUS field.
The BLPU code is an optional attribute for Local Authority Custodians to complete and therefore this attribute may be NULL in product.
An improvement to the completeness of the BLPU State Code was identified as a quality enhancement for lifecycle information as values for BLPU state code 4 can be accurately inferred from a Logical Status of 8. This enhancement allows the data to be interpreted more easily by removing conflict between addresses with a historic logical status and no BLPU state.
All nations within GB and the Islands product regions will benefit from this improvement, as such it impacts approximately 1.2 million records for a Full Supply.
This quality improvement means a larger than usual supply of COUs.
The next release of AddressBase Islands products, Epoch 110, is scheduled for Thursday 16 May 024.
This release note provides information about the November 2023 (Epoch 106) release of the AddressBase Islands products. These products were released to customers on 23 November 2023.
AddressBase Plus Islands
1 145 156
3 624
AddressBase Premium Islands
See rows below
See rows below
Street
48 358
122
Street Descriptor
48 358
33
BLPU
1 227 295
9 223
Classification
1 227 295
7 246
LPI
1 236 596
7 676
Organisation
39 434
518
Delivery Point Address
961 646
1 091
Application Cross Ref.
1 293 771
6 576
Successor
0
0
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.
Inserts
1 283
Updates
2 147
Deletes
194
Street
32
89
1
Street Descriptor
32
0
1
BLPU
6 265
2 915
43
Classification
6 265
938
43
LPI
6 342
1 291
43
Organisation
417
11
90
Delivery Point Address
550
432
109
Application Cross Ref.
6 293
235
48
The following information relates to the currency of the source data used in the creation of Epoch 106:
Pointer (Northern Ireland)
19 October 2023
DigiMap (Channel Islands)
19 October 2023
Isle of Man
19 October 2023
Royal Mail PAF
19 October 2023
There are no reported issues in this release of AddressBase Plus Islands.
Affected output formats: CSV and GML
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.
The next release of AddressBase Islands products, Epoch 107, is scheduled for Friday 05 January 2024.
Explore documentation and guides for OS Premium and OpenData Download products, such as AddressBase Premium, OS MasterMap Topography Layer, Boundary-Line and OS Open Zoomstack.
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 Product Refresh Dates page that details product update schedules, and a PSGA Product Summary page, 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).
There are two types of Download data product: OS Premium and OS OpenData.
When we refer to Premium products we mean paid-for datasets – whether they’re paid for by businesses, purchased through an OS Partner, or accessed free at the point of use under the Public Sector Geospatial Agreement (PSGA).
The OS Premium Download data products are available to download in a range of formats, with a variety of ordering options, through the OS Data Hub on our Premium, Public Sector and Energy and Infrastructure plans.
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.
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 OS Data Hub.
The terms and conditions on which the OS Premium Download data products are made available can be found via the applicable links on the legal information pages of the OS Data Hub.
The terms and conditions on which the OS OpenData Download products are made available are contained within the Open Government Licence and can be found via the applicable links under each OS OpenData geospatial dataset available for download from the OS Data Hub. The OS copyright attribution statement required under the Open Government Licence can be found in the licence file downloaded with the data from the OS Data Hub.
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 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.
As we approach the publication date and prepare to release a new epoch, any new requests placed for data will be paused to ensure data integrity. These requests will be processed as soon as this pause is lifted.
AddressBase product 'family' release notes (for all AddressBase products bar AddressBase Core) are available from the AddressBase Core Principles pages of this site.
AddressBase Core is a weekly supply and information is covered in a separate AddressBase Core release note.
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
Tertiary Level Classification RD02: Detached House CH01: Boarding/Guest House/ Bed And Breakfast/Youth Hostel
Quaternary Level CH01YH: Youth Hostel
The level of classification varies across all addressable objects and across the different products.
There are only certain classification codes that extend to the quaternary classification level as shown above. A full list of the classification codes can be found on our Product Support page on the OS website.
The full classification scheme is available in CSV and .xlsx formats for download in the following zip file.
This enumeration is used in association with the attribute blpuState/BLPU_STATE. This enumeration describes the physical nature of the address record.
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.
This code list is used in association with the attribute country/COUNTRY found on the BLPU table. The code list describes within which country the address feature falls within.
This release note provides information about the February 2024 (Epoch 108) release of the AddressBase Islands products. These products were released to customers on 22 February 2024.
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.
The following information relates to the currency of the source data used in the creation of Epoch 108:
There are no reported issues in this release of AddressBase Plus Islands.
Affected output formats: CSV and GML
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.
The release will enhance clarity and consistency of lifecycle representation within product.
A conformance improvement has been delivered for BLPU State attribute for records where the BLPU Logical Status was 8 (historic) and BLPU State was null; for increased completeness, BLPU State Code has been populated with value 4 (no longer existing) and date stamped for the change applied.
The BLPU state identifies the current lifecycle stage of a property (or object) and is additional to the mandatory LOGICAL_ STATUS field.
The BLPU code is an optional attribute for Local Authority Custodians to complete and therefore this attribute may be NULL in product.
An improvement to the completeness of the BLPU State Code was identified as a quality enhancement for lifecycle information as values for BLPU state code 4 can be accurately inferred from a Logical Status of 8. This enhancement allows the data to be interpreted more easily by removing conflict between addresses with a historic logical status and no BLPU state.
All nations within GB and the Islands product regions will benefit from this improvement, as such it impacts approximately 1.2 million records for a Full Supply.
This quality improvement will be delivered in the next release, Epoch 109, and will mean a larger than usual supply of changes.
No special action will be required to load the release differently.
The next release of AddressBase Islands products, Epoch 109, is scheduled for Tuesday 05 April 2024.
This release note provides information about the January 2024 (Epoch 107) release of the AddressBase Islands products. These products were released to customers on 03 January 2024.
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.
The following information relates to the currency of the source data used in the creation of Epoch 107:
There are no reported issues in this release of AddressBase Plus Islands.
Affected output formats: CSV and GML
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.
The next release of AddressBase Islands products, Epoch 108, is scheduled for Thursday 22 February 2024.
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.
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 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.
BLPU records will not have a logical status value of 3, whereas LPI records can have all of the values expressed above.
1
under construction
2
In use
3
Unoccupied /vacant/derelict
4
No longer existing
6
Planning permission granted
I
Insert
U
Update
D
Delete
E
This record is within England
W
This record is within Wales
S
This record is within Scotland
N
This record is within Northern Ireland
L
This record is within the Channel Islands
M
This record is within the Isle of Man
J
This record is not assigned to a country as it falls outside of the land boundaries used.
AddressBase Plus Islands
1 146 542
2 581
AddressBase Premium Islands
See rows below
See rows below
Street
48 426
91
Street Descriptor
48 426
34
BLPU
1 229 481
3 308
Classification
1 229 481
1 827
LPI
1 238 840
1 804
Organisation
39 354
175
Delivery Point Address
962 351
820
Application Cross Ref.
1 295 835
1 460
Successor
0
0
Inserts
576
Updates
1 834
Deletes
171
Street
34
57
0
Street Descriptor
34
0
0
BLPU
1 031
2 215
62
Classification
1 031
734
62
LPI
1 059
683
62
Organisation
41
33
101
Delivery Point Address
428
224
168
Application Cross Ref.
1 006
352
102
Pointer (Northern Ireland)
14 January 2024
DigiMap (Channel Islands)
18 January 2024
Isle of Man
17 January 2024
Royal Mail PAF
18 January 2024
AddressBase Plus Islands
1 146 137
4 058
AddressBase Premium Islands
See rows below
See rows below
Street
48 392
145
Street Descriptor
48 390
34
BLPU
1 228 512
4 504
Classification
1 228 512
2 320
LPI
1 237 843
3 070
Organisation
39 414
126
Delivery Point Address
962 091
1 087
Application Cross Ref.
1 294 931
2 062
Successor
0
0
Inserts
1 155
Updates
2 729
Deletes
174
Street
34
111
0
Street Descriptor
34
0
0
BLPU
1 344
3 033
127
Classification
1 344
849
127
LPI
1 374
1 569
127
Organisation
40
26
60
Delivery Point Address
589
354
144
Application Cross Ref.
1 349
524
189
Pointer (Northern Ireland)
28 November 2023
DigiMap (Channel Islands)
30 November 2023
Isle of Man
30 November 2023
Royal Mail PAF
30 November 2023
2024-10-24
Date
Date columns will follow the structure: CCYY-MM-DD
D
A record which is linked to PAF
N
Not a postal address
C
A record which is postal and has a parent record which is linked to PAF
L
A record which is identified as postal based on Local Authority information
1
Approved
3
Alternative
6
Provisional
8
Historical
This enumeration is used in association with the attribute fileType/FILE_TYPE found in the Header record. This enumeration allows the identification of either a change-only update (COU) supply or a full supply.
F
Signifies the supply is a full supply
C
Signifies the supply is a COU file
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.
1
Official designated Street Name
2
Street Description
3
Numbered Street
4
Unofficial Street Description
9
Description used for LLPG Access
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.
S
A small user, for example, a residential property
L
A large user, for example, a large commercial company
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.
1
Metalled
2
UnMetalled
3
Mixed
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.
4
Pedestrian way or footpath
6
Cycletrack or cycleway
8
All vehicles
9
Restricted byway
10
Bridleway
This enumeration is used in association with the LANGUAGE attribute found in the Street Descriptor and LPI tables; and also the Metadata table for CSV supply. This enumeration identifies the language of the address displayed.
This is not required for the GML supply as the Language is specified in the GML tag ‘xml:lang’.
ENG
English
CYM
Welsh
GAE
Gaelic (Scottish)
BIL
Bilingual
This enumeration is used in association with the rpc/RPC attribute. This enumeration identifies the accuracy value of the coordinates allocated to the address.
1
Central Internal Position
The address seed is contained within an OS MasterMap Topography Layer building and within 2.5m of its calculated centre.
Or
The seed is in the best possible position based on the nature of the premises, for example, Development Land, House Boat, Wind Farm.
2
General Internal Position
The address seed is contained within an OS MasterMap Topography Layer building but is more than 2.5m away from its calculated centre.
Or
The seed is in an internal position based on the nature of the premises, for example, Development Land, House Boat.
3
Transitional Position
The address seed has been changed from provisional to live in the last six months. It has been captured to a high level of positional accuracy, but the OS MasterMap Topography Layer feature is not yet captured.
Please note the address seed will only be moved pending any imminent mapping updates.
4
Street Location
The address seed is plotted in accordance with the declared street start or end coordinates.
Please note this is the highest accuracy possible for Street Records.
5
Postcode Unit Position
The address seed has been captured to Postcode Unit level. It will be updated when more information becomes available.
9
Low accuracy – marked for priority review
This address seed has been captured to a lower level of accuracy and will be updated as a priority over the coming releases.
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.
14:11:15
Time
Time will follow the structure of HH:MM:SS based on a 24-hour clock.
When you receive an order via hard media (DVD), the following files will be supplied for the contracted area of interest (AOI):
Data
Doc
Order_Details.txt
Within the Data directory, data files will be found in their compressed format.
Within the Doc folder, a text file called Label Information.txt will contain information that is printed on the DVD.
The Order_Details text file will provide information about the order, including the order date, currency date and file structure.
When you receive an order of a Managed Great Britain Set (MGBS) via hard media (DVD), the following files will be supplied:
Data
Doc
Resources
readme.txt
There are several items contained within your supply:
Data folder – This folder contains all of your data supply.
Doc folder – This folder contains the Medialis.txt file, which outlines the contents of the data you have been supplied.
Resources folder – This folder contains lookup tables for the local custodian code and AddressBase classification scheme as well as the Header files for the product.
The readme text file – This document provides guidance notes on matters such as the filename referencing used and the directory structure of the DVD.
Public Sector Geospatial Agreement (PSGA) customers can download their geographic chunk data for AddressBase and AddressBase Plus as well as a full supply of AddressBase Plus Islands via our download service.
The data is supplied as chunked files that cover your selected area. These files are named according to the convention shown below.
When you open your data, you will see a series of zip folders:
Using AddressBase Plus and Islands as an example:
AddressBasePlus_FULL_2020-01-21_001_csv.zip (Full supply of GB CSV)
AddressBasePlus_ISL_FULL_2020-01-21_001_csv.zip (Full supply of Islands CSV) or
AddressBasePlus_COU_2020-01-21_001_gml.zip (COU supply of GB GML)
AddressBasePlus_ISL_COU_2020-01-21_001_gml.zip (COU supply of Islands GML)
Using AddressBase Plus as an example:
AddressBasePlus_FULL_2011-07-29_TQ2020_csv.zip (Full supply of CSV) or
AddressBasePlus_COU_2011-07-29_TQ2020_gml.zip (COU supply of GML)
The AddressBase Plus Islands product is not available in geographic chunks.
The GML and CSV data is supplied in a compressed form (ZIP). Some software can access these files directly, while other software will require the files to be unzipped.
To unzip the zipped data files (.zip extension), use an unzipping utility found on most PCs, for example, WinZip. Alternatively, open-source zipping/unzipping software can be downloaded from the Internet, for example, 7-Zip.
When you unzip the files, the data will be extracted as CSV files, which are ready to use. For example, unzipping AddressBase Plus will extract files similar to the chunks below:
AddressBasePlus_FULL_2020-01-21_001.csv
AddressBasePlus_ISL_FULL_2020-01-21_001.csv
AddressBasePlus_2011-07-29_NC4040.csv
This address record follows the lifecycle of a Postcode Address File (PAF) record matched to a Local Authority record. As a matched record is inserted, deleted and updated within PAF, these changes are incorporated into the AddressBase product. Similarly, if the matched Local Authority address record updates an attribute contained within the AddressBase product, this change will be reflected.
The following sub-sections provide details about the attributes included with this feature, their data types in the different output formats, and other important metadata about them.
The following sub-sections provide details about the attributes included with the Address feature type.
Unique Property Reference Number (UPRN) assigned by the LLPG Custodian or Ordnance Survey.
Attribute Name: uprn (GML), UPRN (CSV)
Data Type: Integer (GML), Integer (CSV)
Multiplicity: [1]
Size: 12
Source: Contributing Local Authority / Ordnance Survey
Unique identifier provided by Ordnance Survey.
Attribute Name: osAddressTOID (GML), OS_ADDRESS_TOID (CSV)
Data Type: LocalisedCharacterString (GML), char (CSV)
Multiplicity: [0..1]
Size: 20
Source: Ordnance Survey
Royal Mail’s Unique Delivery Point Reference Number (UDPRN).
Attribute Name: udprn (GML), UDPRN (CSV)
Data Type: Integer (GML), Integer (CSV)
Multiplicity: [1]
Size: 8
Source: Royal Mail
The organisation name is the business name given to a delivery point within a building or small group of buildings. For example: TOURIST INFORMATION CENTRE
This field could also include entries for churches, public houses and libraries.
Attribute Name: organisationName (GML), ORGANISATION_NAME (CSV)
Condition: Organisation Name or PO Box Number must be present if Building Name or Building Number are all not present.
Data Type: LocalisedCharacterString (GML), char (CSV)
Multiplicity: [0..1]
Size: 60
Source: Royal Mail
For some organisations, department name is indicated because mail is received by subdivisions of the main organisation at distinct delivery points. For example, Organisation Name: ABC COMMUNICATIONS or RM Department Name: MARKETING DEPARTMENT
Attribute Name: departmentName (GML), DEPARTMENT_NAME (CSV)
Condition: If a Department Name is present, an Organisation Name must also be present.
Data Type: LocalisedCharacterString (GML), char (CSV)
Multiplicity: [0..1]
Size: 60
Source: Royal Mail
Post Office Box (PO Box) number.
Attribute Name: poBoxNumber (GML), PO_BOX_NUMBER (CSV)
Condition: Organisation Name or PO Box Number must be present if Building Name or Building Number are all not present.
Data Type: CharacterString (GML), char (CSV)
Multiplicity: [0..1]
Size: 6
Source: Royal Mail
The sub-building name and/or number are identifiers for subdivisions of properties.
For example: Sub-building Name: FLAT 3, Building Name: POPLAR COURT, Thoroughfare: LONDON ROAD
If the above address is styled 3 POPLAR COURT, all the text will be shown in the Building Name attribute and the Sub-building Name will be empty. The building number will be shown in this field when it contains a range, decimal or non-numeric character (see Building Number).
Attribute Name: subBuildingName (GML), SUB_BUILDING_NAME (CSV)
Condition: If a Sub Building Name is present, a Building Name or Building Number must also be present.
Data Type: LocalisedCharacterString (GML), char (CSV)
Multiplicity: [0..1]
Size: 30
Source: Royal Mail
The building name is a description applied to a single building or a small group of buildings, such as Highfield House. This also includes those building numbers that contain non-numeric characters, such as 44A.
Some descriptive names, when included with the rest of the address, are sufficient to identify the property uniquely and unambiguously, for example, MAGISTRATES COURT.
Sometimes the building name will be a blend of distinctive and descriptive naming, for example, RAILWAY TAVERN (PUBLIC HOUSE) or THE COURT ROYAL (HOTEL).
Attribute Name: buildingName (GML), BUILDING_NAME (CSV)
Condition: Building Name must be present if Organisation Name or Building Number or PO Box Number are all not present.
Data Type: LocalisedCharacterString (GML), char (CSV)
Multiplicity: [0..1]
Size: 50
Source: Royal Mail
The building number is a number given to a single building or a small group of buildings, thus identifying it from its neighbours, for example, 44. Building numbers that contain a range, decimals or non-numeric characters do not appear in this field but will be found in the buildingName or the sub-BuildingName fields.
Attribute Name: buildingNumber (GML), BUILDING_NUMBER (CSV)
Condition: Building Number must be present if Organisation Name or Building Name or PO Box Number are all not present.
Data Type: Integer (GML), Integer (CSV)
Multiplicity: [0..1]
Size: 4
Source: Royal Mail
A thoroughfare in AddressBase is fundamentally a road, track or named access route on which there are Royal Mail delivery points, for example, HIGH STREET.
Attribute Name: thoroughfare (GML), THOROUGHFARE (CSV)
Data Type: LocalisedCharacterString (GML), char (CSV)
Multiplicity: [0..1]
Size: 80
Source: Royal Mail
The town or city in which the Royal Mail sorting office is located which services this record. There may be more than one, possibly several, sorting offices in a town or city.
Attribute Name: postTown (GML), POST_TOWN (CSV)
Data Type: LocalisedCharacterString (GML), char (CSV)
Multiplicity: [1]
Size: 30
Source: Royal Mail
This is used to distinguish between similar thoroughfares or the same thoroughfare within a dependent locality. For example, Millbrook Industrial Estate and Cranford Estate in this situation: BRUNEL WAY, MILLBROOK INDUSTRIAL ESTATE, MILLBROOK, SOUTHAMPTON and BRUNEL WAY, CRANFORD ESTATE, MILLBROOK, SOUTHAMPTON.
Attribute Name: doubleDependentLocality (GML), DOUBLE_DEPENDENT_LOCALITY (CSV)
Data Type: LocalisedCharacterString (GML), char (CSV)
Condition: If a Double Dependent Locality is present, a Dependent Locality must also be present.
Multiplicity: [0..1]
Size: 35
Source: Royal Mail
Dependent locality areas define an area within a post town. These are only necessary for postal purposes and are used to aid differentiation where there are thoroughfares of the same name in the same locality. For example, HIGH STREET in SHIRLEY and SWAYTHLING in this situation: HIGH STREET, SHIRLEY, SOUTHAMPTON and HIGH STREET, SWAYTHLING, SOUTHAMPTON.
Attribute Name: dependentLocality (GML), DEPENDENT_LOCALITY (CSV)
Data Type: LocalisedCharacterString (GML), char (CSV)
Multiplicity: [0..1]
Size: 35
Source: Royal Mail
A postcode is an abbreviated form of address made up of combinations of between five and seven alphanumeric characters. These are used by Royal Mail to help with the automated sorting of mail. A postcode may cover between 1 and 100 addresses.
There are two main components of a postcode, for example, NW6 4DP:
The outward code (or ‘outcode’). The first two–four characters of the postcode constituting the postcode area and the postcode district, for example, NW6. It is the part of the postcode that enables mail to be sent from the accepting office to the correct area for delivery.
The inward code (or ‘incode’). The last three characters of the postcode constituting the postcode sector and the postcode unit, example, 4DP. It is used to sort mail at the local delivery office.
Attribute Name: postcode (GML), POSTCODE (CSV)
Data Type: CharacterString (GML), char (CSV)
Multiplicity: [1]
Size: 8
Source: Royal Mail
Describes the address as a small or large user as defined by Royal Mail.
Attribute Name: postcodeType (GML), POSTCODE_TYPE (CSV)
Condition: If PO Box number is present Postcode Type must be ‘L’.
Multiplicity: [1]
Size: 1
Source: Royal Mail
A value in metres defining the x and y location in accordance with the British National Grid.
Attribute Name: position (GML), X_COORDINATE, Y_COORDINATE (CSV)
Data Type: GM_Point (GML), Float (CSV)
Multiplicity: [1]
Size: X_COORDINATE (precision, scale) – (8, 2), Y_COORDINATE (precision, scale) – (9, 2)
Source: Contributing Local Authority/Ordnance Survey
A value defining the Longitude and Latitude location in accordance with the ETRS89 coordinate reference system.
Attribute Name: positionLatLong (GML), LATITUDE, LONGITUDE (CSV)
Data Type: GM_Point (GML), Float (CSV)
Multiplicity: [1]
Size: LATITUDE (precision, scale) – (9, 7), LONGITUDE (precision, scale) – (8, 7)
Source: Ordnance Survey
Representative Point Code. This code is used to reflect positional accuracy.
Attribute Name: rpc (GML), RPC (CSV)
Multiplicity: [1]
Size: 1
Source: Contributing Local Authority
The country in which a record can be found.
Attribute Name: country (GML), COUNTRY (CSV)
Multiplicity: [1]
Size: 1
Type of Record Change – please see Section 4 for more information.
Attribute Name: changeType (GML), CHANGE_TYPE (CSV)
Multiplicity: [1]
Size: 1
The date on which the address record was inserted into the database in the CCYY-MM-DD format.
Attribute Name: laStartDate (GML), LA_START_DATE (CSV)
Data Type: Date (GML), Date (CSV)
Multiplicity: [1]
Source: Contributing Local Authority
Date on which the Royal Mail address was loaded into the NAG (National Address Gazetteer in the CCYY-MM-DD format – as maintained by Geoplace) hub.
Attribute Name: rmStartDate (GML), RM_START_DATE (CSV)
Data Type: Date (GML), Date (CSV)
Multiplicity: [1]
Source: Royal Mail
The date on which any of the attributes on this record were last changed in the CCYY-MM-DD format.
Attribute Name: lastUpdateDate (GML), LAST_UPDATE_DATE (CSV)
Data Type: Date (GML), Date (CSV)
Multiplicity: [1]
Primary classification of the address record. For example, identifying the record as commercial (value of ‘C’) or residential (value of ‘R’).
Attribute Name: class (GML), CLASS (CSV)
Data Type: CharacterString (GML), char (CSV)
Multiplicity: [1]
Size: 1
Source: Contributing Local Authority
A new page detailing any newsworthy announcements for the Download data products.
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 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.
You are advised to copy the supplied data to a backup medium.
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:
This getting started guide provides instructions for using AddressBase in different software applications. Users with limited technical knowledge will be able to follow this guide.
These instructions show you how to get started with , and .
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:
AddressBase provides a current view of all Royal Mail Postcode Address File (PAF) addresses that have been matched to the National Land and Property Gazetteer (NLPG) and One Scotland Gazetteer (OSG). The product provides Royal Mail attribution as well as enhancing the Royal Mail Postcode Address File (PAF) data with X and Y coordinates on the British National Grid and ETRS89 coordinate reference system and providing the classification of an address to a primary level. It also provides a primary level classification.
This product will provide you with a single view of an address, allow you to locate this address on a map to give you a geographic view and carry out primary analysis on the function of the address to determine, for example, residential from commercial properties.
This product is updated every six weeks.
Identify a property and locate it on a map with precision – using the X and Y coordinates we’ve assigned to the Royal Mail Postcode Address File (PAF) data.
Every address geo data record provides Royal Mail address information from PAF, the Unique Delivery Point Reference Number (UDPRN) and X and Y coordinates.
Using the basic classifications in AddressBase you can quickly filter between residential and commercial addresses, which is ideal for marketing purposes.
Our basic classifications – residential or commercial – will reduce the costs and increase the effectiveness of your direct marketing.
In customer services, the need for accuracy is paramount. Have confidence in your front-line staff’s ability to look up addresses on a database of millions, quickly and efficiently.
Access: Download
Data theme: Address
Data structure: Vector – Points
Coverage: Great Britain
Scale: 1:1 250 to 1: 10 000
Format: CSV, GML 3.2.1
Ordering area: All of Great Britain or customisable area (5km² tiles or user-defined polygon)
OS Data Hub plan: Public Sector Plan, Premium Plan, Energy & Infrastructure Plan
To find out details such as houses that have been converted to flats, you'll need AddressBase Plus. it includes current properties and addresses sourced from local authorities, Ordnance Survey and Royal Mail. These are all matched to the UPRN and structured in a flat-file model.
AddressBase Plus has more records than AddressBase as it includes objects without postal addresses such as places of worship and community centres – as well as sub-divided properties. It lets you locate an address or property on a map, through the assigned X and Y coordinates.
Crucially, the cross-referencing information with OS MasterMap products via Topographic Identifiers (TOIDs) means you can view address data within a wider context.
Royal Mail royalties are included in the licence fee. A separate Royal Mail royalty fee applies if you license the AddressBase data on External Transaction Solution (ETS) terms.
If the file size of your order is smaller than 2Gb, you can get it from our FTP server. in addition, public sector customers can download 5km chunk orders via our download service.
The database is a vital component of the single address gazetteer database and is in each of the AddressBase products where there has been a match confirming the address to the LLPG address.
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:
All the AddressBase products are available as a full supply or a COU. A COU means you will only be supplied with the features which have changed since your last supply. The following sections provide guidance on how you could potentially manage a COU supply of AddressBase and AddressBase Plus data.
If you receive a tile supply, you will receive Change Chunks. This means if a record within your tile has changed, all of the records in that tile will be provided to you as inserts, and no updates or deletes will be issued.
Tiles are only available for GB supplies, so this does not apply to AddressBase Plus Islands.
At a high-level, there are three types of change found within a COU:
Deletes (CHANGE_TYPE ‘D’) are objects that have ceased to exist in your AOI since the last product refresh.
Inserts (CHANGE_TYPE ‘I’) are objects that have been newly inserted into your AOI since the last product refresh.
Updates (CHANGE_TYPE ‘U’) are objects that have been updated in your AOI since the last product refresh.
The diagram below shows how to implement an AddressBase, AddressBase Plus and AddressBase Plus Islands COU within a database.
Before a COU is applied, there may be a business requirement to archive existing address records. The table below shows how to implement archiving with an AddressBase COU within a database.
Within AddressBase and AddressBase Plus there will be no records with the same UPRN. This can be tested by checking the number of records that have the same UPRN. The following SQL code would notify you of any duplicates:
This query should return 0 rows, and this confirms that there are no duplicates. As there are no duplicate records, we can use the UPRN to apply the COU.
Once confirmed, the following steps can be taken to apply the COU (without archiving):
Initially delete the existing records that will be updated and deleted:
Insert the new updated records and the new inserted records:
Where there is a business requirement to keep the records that are being Updated and Deleted in a separate archive table, the following SQL will create an Archive Table. It will populate with records that are being Updated and Deleted from the live AddressBase or AddressBase Plus table.
The following command creates an archive table of the records that are being updated and deleted from the existing table.
If this table already exists, you can simply use INSERT INTO rather than CREATE TABLE.
The following command then deletes the records from the existing table, which are either updates or deletions:
The following command then inserts the new insert records and the new updated records into the live table:
These instructions describe how to prepare the CSV format of AddressBase, AddressBase Plus and AddressBase Plus Islands data for processing.
These instructions describe how to load the CSV format of AddressBase, AddressBase Plus and AddressBase Plus Islands data. In these examples, AddressBase Plus data will be used to describe the procedures in various GI systems.
It is assumed that the preparation of the AddressBase, AddressBase Plus or AddressBase Plus Islands CSV data has been carried out as instructed in before attempting to load the data. If it has not been done, the full set of data will not load, and data loaded will not contain header information.
This section describes how to load AddressBase products into a few common databases.
ArcMap, ArcGIS Desktop and ArcGIS Server software do not support the BIGINT/NUMBER data type as an Object ID. Bear this in mind if the expectation is to use this data type directly with these ESRI products. An alternative method to facilitate using ESRI software is to store this data as a string and add a new Serial ID to act as the Object ID. If you are loading AddressBase data directly into a database, you may need to increase the column length to accommodate language characters such as '^'. Some databases treat this as an additional character and therefore, if you define the column length according to our specification, there is a chance that the load may fail. Please bear in mind such adjustments may be required depending on the database you use to load the data.
If a UPRN is deleted and then reinserted, this does not compromise the integrity of the UPRN and its use as a primary key. If a delete is issued for a UPRN, this does not mean it will not reappear in subsequent supplies.
These are the reasons why this may happen:
The record has moved in location more than once, moving it out of your Area of Interest (AOI), hence the deletion, but then moved back into your AOI in the future. This would also occur if you altered your AOI.
A record has failed data validation upon a change being made. This can result, dependent on the change being made, in the record being deleted and then reintroduced when the error is fixed by the data supplier.
If a UPRN is deleted, it will not be reallocated to a different property and it therefore remains the unique identifier for a property.
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.
The following page details the current local custodian codes of all local custodians contributing to the AddressBase products.
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.
Definition: This address record follows the lifecycle of a Postcode Address File (PAF) record matched to a Local Authority record. As a matched record is inserted, deleted and updated within PAF, these changes are incorporated into the AddressBase product. Similarly, if the matched Local Authority address record updates an attribute contained within the AddressBase product, this change will be reflected.
The UML model of AddressBase in CSV format can be seen in the UML diagram below; classes from the Ordnance Survey product specification are coloured orange; all code lists are coloured blue, while enumerations are coloured green.
Definition: This address record follows the lifecycle of a Postcode Address File (PAF) record matched to a Local Authority record. As a matched record is inserted, deleted and updated within PAF, these changes are incorporated into the AddressBase product. Similarly, if the matched Local Authority address record updates an attribute contained within the AddressBase product, this change will be reflected.
The UML model of AddressBase in GML format can be seen in the diagram below. In the UML diagram, classes from the Ordnance Survey product specification are orange, all code lists are coloured blue and enumerations are green.
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.
The CSV supply of AddressBase means:
There will be one record per line in each file.
Fields will be separated by commas.
String fields will be delimited by double quotes.
No comma will be placed at the end of each row in the file.
Records will be terminated by Carriage Return / Line Feed.
Double quotes inside strings will be escaped by doubling.
Where a field has no value in a record, two commas will be placed together in the record (one for the end of the previous field and one for the end of the null field). Where the null field is a text field double quotes will be included between the two commas, for example - , “”,
AddressBase CSV data will be transferred using Unicode encoded in UTF-8. Unicode includes all the characters in ISO-8859-14 (Welsh characters). Some accented characters are encoded differently.
The transfer will normally be in a single file, but the data can be split into multiple files using volume numbers. Most files will only be split where there are more than one million records.
The header row for the CSV is supplied separately and can be downloaded from the product support pages.
The 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.1 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.
A GML document is described using a GML Schema. The AddressBase schema document (addressbase.xsd), defines the features in AddressBase GML.
The application schema uses the following XML namespaces, for which definitions are available as given here:
Each feature within the AddressBaseSupplySet:FeatureCollection is encapsulated in the following member element according to its feature type:
The UPRN of the feature is provided in the XML attribute of the gml:id
In the GML supply you can determine the extent of your supply by the <gml: Envelope>. For example:
A common requirement for customers using the AddressBase products is to search for properties using full or partial addresses. Address searches may return a large number of addresses, a short list of possibilities, a single match or no results, depending on the search criteria.
There are many methods of implementing an address search, from free text queries through to structured address component searches. This guide will step through two such approaches that may be used when working with AddressBase and/or AddressBase Plus.
These methods are not intended as recommendations; they are merely examples of how to get maximum value out of the product when implementing an address search function.
One type of search implementation involves a single ‘search engine’ style text box, into which a user can type all or some of an address. For example:
In this scenario, the user can choose to type anything in Find address, which may be just one component of an address (for example, a postcode, street name or building name), several parts of an address (for example, street name + town name, house name + postcode, etc.) or even (rarely) a complete address.
There may or may not be commas between search items, or address components can be entered with or without capitalised letters, etc. In short, with this search method, there is no structure to the user input and the search methodology must be designed with this in mind.
The other common type of implementation for address searches involves entering search criteria in a structured way (for example, with a different text box for each major address component).
This method guides the user to enter known components of an address and creates a predictable user input structure around which to build a search function. While generally simpler to use and implement, it can be less user-friendly, particularly in cases where it is not obvious which box to type an address component into, for example, is Richmond Terrace a building name or a street?
This guide suggests how to implement the two search methods described above. Both should be used alongside the instructions on formatting single address labels.
The methods described here may be adapted to work with both AddressBase Plus, AddressBase Plus Islands and AddressBase; however, in the case of AddressBase, only Delivery Point Addresses are searchable, so the geographic guidance will not apply to this product.
An address search operation typically requires two stages of interaction from a user and several processing steps from the underlying IT system. These steps can be summarised in the following diagram:
The second user interaction can be omitted if there is only one result returned from the query. In almost all cases, there should be an option to ‘search again’ at the second and third stages in case no results are returned, or if none of the options shown is the required address.
Of course, different applications require different approaches; however, the general principles of the above process apply in all cases where an address is searched for based on user-entered criteria.
Within an interface that accepts structured user input for an address search, it is necessary to ‘map’ the fields presented to the user with those found within AddressBase or AddressBase Plus. In particular, any query will need to test multiple fields for a given input and will need to combine result sets from the two different address formats of AddressBase Plus (or the single address format of AddressBase) in order to produce the most complete result set.
Generally, a search form will describe a simplified view of an address in order to keep the user interface tidy and intuitive. Users may be given a set of text boxes to fill in, generally including building name, building number, street name, locality name, town name and postcode. The relationships between some common search fields and the fields found in AddressBase Plus are as follows:
The above mapping is an example only, and it is possible to breakdown the search fields differently, in which case, a different mapping would be required. The important thing is to consider all possibilities for how data might be recorded. For example, a business name can sometimes appear as an organisation name or a building/PAO name depending on circumstances, so both must be checked when creating a search query.
Numbers need to be handled very carefully due to the presence of suffixes and ranges. There are two options for structuring the search input in these cases:
A single ‘number’ box can be used (as shown above in Flat/Subdivision Number and Building Number), which will then require some string manipulation to split the input into the appropriate numeric range and suffix components in order to search the geographic addresses; or
Four boxes can be provided for each number (start number, start suffix, end number and end suffix), which would then need to be combined into an appropriate string to search the Delivery Point Addresses.
The basic rules to adhere to when generating a search query from structured input are as follows:
Ignore any search boxes that are not filled in with values.
Where a value is entered, assume that a match on at least one of the mapped fields is essential.
In SQL query terms, this means that each search term should generate a sub-query that searches each of the mapped fields (using OR), and that these sub-queries should then be combined together (using AND) into a single search query. The following SQL code illustrates this (for the Delivery Point Address search only) for an example where a street, locality and town name have been entered by the user:
On top of this, for a complete query, the two different types of addresses should be queried separately (Geographic and Delivery Point Addresses), and the two result sets should be amalgamated into a single set using a UNION. The following example builds upon the previous example to include Geographic Addresses as well as Delivery Point Addresses.
The SQL UNION operator will combine the two result sets, discarding any exact duplicates. (Retaining the exact duplicates requires the use of UNION ALL, but that is not desirable in this example.)
The resulting output from this query will be a set of search results as formatted addresses along with their UPRN. Exact duplicates will be omitted, but all ‘variations’ of the same address will be output (one row for each variation, with the same UPRN repeated more than once potentially). It may be wise to return the Postal Address Flag values against each to enable further filtering, for example, to restrict the results to postal addresses only. Note that the Postal Address Flag is only available in AddressBase Plus. All records in AddressBase are deemed postal as they are from Royal Mail’s PAF data.
A flaw in the above examples is the use of equality operators. In practice, because people do not tend to be consistent with capitalisation of letters, the SQL ‘LIKE’ operator might work better, and depending on the nature of the application, a ‘%’ wildcard could be appended to the end of each search term to allow only the first few letters of an address component to be entered. For example:
Alternatively, if exact matches are required but case sensitivity is not, then the UPPER() or LOWER() SQL functions can be used on each side of the equals sign in comparisons (a solution that should work in all databases):
Finally, to combine all of the approaches, the following would work for maximum flexibility:
When offering a ‘search engine’ style search feature with just a single text box to enter search terms, a wholly different approach is required. No assumptions can be made about the order, format or style of the user input, and the data will need to be ‘indexed’ in a way that facilitates searches of this type.
Search engine style searches are likely to require the creation of an additional index/lookup table for addresses. Such a table is likely to consist of just two main columns: a key value (UPRN) and a formatted address string. Additional columns may be required to allow filtering of results (such as the AddressBase Postal flag values from AddressBase Plus, which would allow the results to be filtered by different address statuses).
The following table shows a possible address index table structure:
Note how the addresses have been formatted as a single text string with a single space between each word (although leaving commas in would do no harm). All forms of each address (both PAF and geographic) have been added to the index, so there can be several rows with the same UPRN. To speed up complex searching, an appropriate index could be added to the Address Text field, such as a full text search index.
Once a suitable search index is in place, the query itself can be put together. The basic idea is to split the user input into search terms by removing commas, double spaces, and other unnecessary whitespace and then splitting it at each single space, as follows:
User input: 4, High Street, westville, wv17
Capitalised, with commas and double-spaces removed:
4 HIGH STREET WESTVILLE WV17
Split into separate search terms:
4
HIGH
STREET
WESTVILLE
WV17
Once the user input has been pre-processed into separate search terms, a query can be generated. The key assumption in this example will be that ALL search terms must be matched against the index table to be considered as a result. This implies a query where each value is matched using an ‘AND’ operator. In order to search the whole index, the ‘LIKE’ operator will need to be used along with a ‘%’ wildcard on either side of the search text. A suitable search query for the above example would be as follows:
This query would return all rows from the index table that contain all of the search terms, along with the appropriate UPRNs. The following table shows how the index table would be used in the above example to return relevant results:
This result set can then be presented to the user, who can select the most appropriate record, which can then be retrieved in full using the UPRN.
Of course, in a practical implementation, the above query would need to be dynamically generated, with a separate condition added for each search term. This example is quite a strict search query that requires all search terms to be present. Many layers of complexity could be added to allow partial and ‘fuzzy’ matches, and to return confidence scores, for example, but such enhancements are beyond the scope of this guide.
This guide is intended as an introduction to implementing address search functionality using AddressBase, AddressBase Plus and AddressBase Plus Islands. The following list is a summary of the main points:
A user front-end for an address search may contain a single, search engine style text box or multiple text boxes representing different parts of an address.
A typical address search function takes place in three stages:
A user enters search text.
A query is run, returning a set of possible matches.
The user selects the address of interest and the full record is then returned.
With a structured search interface, the addresses can be queried directly by mapping the various address fields to the text boxes supplied.
For an unstructured (single text box) interface, it is necessary to create an index table with fully formatted address strings against each UPRN. Queries can then be run against this index table by splitting the user input into individual search terms and requiring them all to be present.
It is possible to filter results by status in AddressBase Plus (for example, postal or non-postal).
Any search function should search all forms of an address (both Geographic and Delivery Point Addresses).
Careful consideration should be given to the use of ‘fuzzy’ search algorithms (such as using wildcard or sound-alike searches).
The AddressBase products provide a variety of data fields, allowing you to construct different forms of an address for a given addressable object, dependent on how the address is to be used.
AddressBase contains the Delivery Point Address which is sourced from Royal Mail’s Postcode Address File (PAF) – a non-geocoded list of addresses. These addresses are used primarily as a ‘mailing list’ for postal purposes.
There are two types of address contained in the AddressBase Plus products:
Delivery Point Address
Geographic Address
These two address types come from different sources and are matched together by GeoPlace.
As noted above, the Delivery Point Address is sourced from Royal Mail’s PAF data. Geographic Addresses are maintained by contributing Local Authorities. The structure of a Geographic Address is based on the British Standard BS7666. These addresses are used to provide an accurate geographic locator for an object to support, for example, service delivery, asset management, or command and control operations. They also represent the legal form of addresses as created under street naming and numbering legislation.
Each UPRN in AddressBase Plus provides the Geographic Address and, where matched, the Delivery Point Address in a one-to-one relationship. If there is no match, then the following fields will be left empty:
A common requirement for customers using the AddressBase products is to build a single address label from core address elements.
There are two types of address label. The simplest is a full address on a single line with different elements separated by commas and spaces. This type of label is suited for displaying a full address within a tabular display, such as within an on-screen data grid or spreadsheet, or where a single-line printed address is most appropriate (such as within the text, header or footer of a letter):
ROSE COTTAGE, 5 MAIN STREET, ADDRESSVILLE, LONDON, SE99 9EX
The other type of formatted address is a multi-line address label. These are most often used on envelopes or at the tops of letters, where different parts of an address are separated onto different lines:
The rules in this guide are suggestions only and can be used for visual display of full addresses. It is strongly recommended that address components are stored in the format in which they are provided in order to allow maximum flexibility of use and derived value.
A Delivery Point Address contains information sourced from Royal Mail (PAF). Stringent rules are used to match these addresses to the Geographic Address and assign a common UPRN to link addresses from the two addressing sources together in the data model.
To construct a single address label based purely on the Royal Mail PAF address fields, the following attributes can be used to build a Delivery Point Address label.
The table below provides details of the Delivery Point Address Components.
These address components are listed in the correct order in which they should appear on an address label. There may be a business need to replace the thoroughfare, locality and post_town attributes with the Welsh equivalent. The following examples use the English version of these attributes only.
It should be noted that most of the PAF fields are optional and may contain null values (or zero, in the cases of ‘BUILDING NUMBER’ and ‘PO BOX NUMBER’). In these cases, those fields should be omitted.
The following (entirely fictional) example shows all of the PAF fields filled in (apart from the PO Box number) and indicates how they should be ordered in a single address label.
In cases where a PO BOX NUMBER is present, it will only be described in the data as an integer. In order to properly format these addresses when generating an address label, these integers should be prefixed with the text ‘PO BOX’, as shown in the following example:
Where null or empty, string values exist (for character fields) or zeros or nulls (for integer fields), those fields should be entirely omitted from the output. However, the order in which the fields should be concatenated always remains the same.
Building a single-line, formatted address for a Delivery Point is relatively straightforward. All the fields should be checked in the order shown previously in Table 1, and those that have values should be concatenated together into a single line. Generally, address components should be separated by a comma followed by a single space (‘, ’), although sometimes only a space is used between a building number and a thoroughfare name. You can use your preference.
The SQL operator for concatenating text is a double pipe (‘||’).
CASE blocks have been used to test each of the fields for null values before concatenating its contents (along with a suitable separator – either ‘, ’ or ‘ ’).
The field names and table names used are illustrative and may vary between databases.
Depending on the database schema and data loading method used, it may be necessary to test some fields for empty strings (‘’) or zero values (for integer fields) instead of, or as well as, testing for NULLs.
If you are using PostGres (PostGIS), it might be beneficial to substitute the ‘IS NOT NULL’ with != ‘’. This should improve the overall appearance of the output.
Splitting a Delivery Point Address into multiple lines is more complicated. There are several rules to consider in order to avoid having very short lines (for example, just a building number) or very long lines within the formatted address. A summary of these rules is as follows:
Generally, if there is a building number, it should appear on the same line as the thoroughfare (or dependent thoroughfare) name. If there is no thoroughfare name information, it should appear on the same line as the first locality name.
In cases where building numbers have been placed in the building name field due to the presence of a letter suffix (for example, ‘11A’) or a number range separator (for example, ‘3–5’), these should be detected and placed on the same line as the thoroughfare name in the same way as a building number (or on the first locality line if no thoroughfare name is present).
In most other cases, the building name, if present, should appear on a separate line above the thoroughfare (or dependent thoroughfare) name. If there is no thoroughfare name present, it should appear on the same line as the first locality name.
Similar tests should be applied to the SUB_BUILDING_NAME field: if this field contains a number, a number with a suffix, or a numeric range, it should precede the building name on the same line. In most other cases, it should appear on a separate line above the building name.
The structure of a Geographic Address is based on the British Standard BS7666 and is split into several components. This means that in order to construct a complete address label (for example, on an envelope, database form or GIS display), the components need to be constructed according to a set of rules.
Within the AddressBase Plus products, the core property level address information is stored within the Primary Addressable Object (PAO) and Secondary Addressable Object (SAO) fields. The additional attribution required to build a full address label are the la_organisation, street_description, locality, town_name, administrative_area and postcode_locator.
For a full description of PAOs and SAOs, and the complete set of AddressBase Plus fields, please refer to the Technical Specification on your respective product:
To construct a single address label based purely on the BS7666 address fields, the following attributes should be used to build a Geographic Address label.
*ADMINISTRATIVE_AREA is optional because it is common for this field to be the same as the TOWN_NAME. Sometimes, however, this field will help users construct a more complete address.
These address components are listed in the correct order in which they should appear on an address label. There may be a business need to use alternate language fields for the SAO_TEXT, PAO_TEXT and STREET_DESCRIPTION, which are also listed in the correct order above.
When building a single address label, it may be necessary to concatenate the various SAO fields and PAO fields together respectively. These fields contain any property names, numbers, number ranges or suffixes that apply to an address.
A PAO number/range string should be constructed from the PAO_START_NUMBER, PAO_START_SUFFIX, PAO_ END_NUMBER and PAO_END_SUFFIX fields, as illustrated in the following table.
Similarly, a SAO number/range string should be constructed from the SAO_START_NUMBER, SAO_START_SUFFIX, SAO_END_NUMBER and SAO_END_SUFFIX fields, as illustrated in the following table.
In addition to the numeric range fields described above, there are also PAO_text and SAO_text fields. These fields may be populated instead of, or as well as, the numeric range fields. In both cases, if both text and a numeric range string are present, the text should appear before the numeric range in any formatted address.
For PAOs, there will always be either a text entry or a numeric/range entry, or both. This is not the case for SAOs, which may be entirely absent for a given address.
The street description and administrative area names are always present, while the locality name and town name may be empty.
The ADMINISTRATIVE_AREA field always contains a value; however, this value will not always enhance an address, but in some cases it will. In particular, check that it is not the same as the value in the TOWN_NAME field, as this is often the case.
In other cases, the administrative area name will simply contain the local authority name, which would not traditionally form part of a single or multi-line address but can be included to add additional information to an address label. Its inclusion is largely down to business requirements or personal preference; however, it may also be useful to 'de-duplicate' some Geographic Addresses.
The following (entirely fictional) example shows all of the BS7666 Geographic Address fields filled in and how they should be ordered in a single address label.
*The number/range strings are built from the relevant PAO/SAO START_NUMBER, START_SUFFIX, END_NUMBER and END_SUFFIX fields, as described above, and formatted as character strings.
Where an administrative area matches the town name, it should always be omitted.
Where null or empty string values exist (for character fields) or zeros or nulls (for integer fields), those fields should be entirely omitted from the output; however, the order in which the fields should be concatenated always remains the same.
The SQL operator for concatenating text is a double pipe (‘||’).
CASE blocks have been used to test each of the fields for null values before concatenating its contents (along with a suitable separator – either ‘, ’ or ‘ ’).
The field names and table names used are illustrative and may vary between databases.
Depending on the database schema and data loading method used, it may be necessary to test some fields for empty strings (‘’) or zero values (for integer fields) instead of or as well as testing for NULLs.
Splitting a Geographic Address into multiple lines is more complex. As with Delivery Point Addresses, there are several rules to consider in order to avoid having very short lines (for example, just a building number) or very long lines within the formatted address.
A summary of these rules is as follows:
Generally, if there is a PAO number/range string, it should appear on the same line as the Street Description. For example: 11A MAIN STREET
If there is a PAO_text value, it should always appear on the line above the Street Name (or on the line above the <PAO number string> + <Street Name> where there is a PAO number/range).
If there is a SAO_text value, it should appear on a separate line above the PAO_text line (or the PAO number/range + Street Name where there is no PAO_text value).
If there is a SAO number/range value, it should be inserted either on the same line as the PAO_text (if there is a PAO_text value), or on the same line as the PAO number/range + Street Name (if there is only a PAO number/range value and no PAO_text value). If there are both PAO_text and a PAO number/range, then the SAO number/range should appear on the same line as the PAO_text, and the PAO number/range should appear on the street line.
If there is a SAO_text value, it should always appear on its own line.
If there is an Organisation Name, it should always appear alone as the top line of the address.
The Locality (if present) should appear on a separate line beneath the Street Description, followed by the Town Name on the line below it. If there is no Locality, the Town Name should appear alone on the line beneath the Street Description.
If the Administrative Area name is required and it is not a duplicate of the Town Name, it can optionally be included on a separate line beneath the Town Name.
Finally, the Postcode Locator should be inserted on the final line of the address.
Given that AddressBase Plus contains two different types of address, a decision needs to be made as to whether to use the Geographic or Delivery Point Addresses, or a mixture.
The following two options should be considered:
Use Delivery Point Addresses whenever they are available, and when they are not, use a Geographic Address.
Use Geographic Addresses in all cases.
Depending on business requirements, in some user interfaces it may be worth considering displaying both forms of an address where possible, since this will provide the maximum information available about a given UPRN.
‘Mixing and matching’ components from the two different forms of address into a single address label is not recommended as this is likely to cause confusion in some instances.
AddressBase Plus offers other attributes that could be used in conjunction with address labels. For example, classification can be used to target certain types of property, or OS MasterMap Topography TOID cross references can be used to link address labels to Topographic objects and viewed in a GIS.
TOID cross references are not available in AddressBase Plus Islands.
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.
This feature is formally known as the GML feature collection and is used to define a collection of features.
This is not supplied as part of the CSV supply. Please see and for more information.
The following sub-sections provide details about the attributes included with this feature, their data types in the different output formats, and other important metadata about them.
Time the data was extracted from the database.
Attribute Name: queryTime (GML), Not provided (CSV)
Data Type: DateTime (GML)
Multiplicity: [1]
Size: 1
The date given as part of a change-only query.
Attribute Name: queryChangeSinceDate (GML), Not provided (CSV)
Data Type: Date (GML)
Multiplicity: [1]
Size: 1
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.
This product is updated weekly.
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.
Customers have asked for easy file formats, so CSV and GeoPackage are available for this product, with headers included – removing the need for any post-processing. Simply load, or drag and drop into a GIS package to start analysing.
AddressBase Core provides approved addressing records for England, Wales and Scotland based on Local Authority holdings of the National Land and Property Gazetteer (NLPG) and One Scotland Address Gazetteer (OSG). Other attribution includes property-level coordinates and secondary level classifications (detailing the use and type of an address).
Through property classification attributes, you can quickly understand, locate and perform analysis on the type of addresses you want to interact with.
AddressBase Core's primary source of addressing information is local authority data. They have the legal responsibility to capture and maintain address data for Great Britain, so you can be sure of its authenticity and legal nature.
AddressBase Core is released weekly, keeping you more up to date with changes.
Making the most of the property classification attributes, you can quickly understand, locate and perform analysis on the type of addresses you want to interact with.
AddressBase Core makes it easier to locate, match and gain insights from other location data with the benefit of having key identifiers referenced throughout. The Unique Property Reference Number (UPRN), Unique Street Reference Number (USRN) and Topographic Identifier (TOID) allow users to reference to other OS products.
Access: Download
Data theme: Address
Data structure: Vector – Points
Coverage: Great Britain
Scale: 1:1 250 to 1:10 000
Format: CSV, GML 3.2.1
Ordering area: All of Great Britain or customisable area (5km² tiles or user-defined polygon)
OS Data Hub plan: Public Sector Plan, Premium Plan, Energy & Infrastructure Plan
AddressBase Core takes many of the high importance items from the other AddressBase products, such as coordinates, classifications (type of address) and links to other important identifiers; but it also includes a single attribute for an address line, is updated weekly, and is offered in an easier to digest format to make the product as easy to access and use as possible.
Properties yet to be built, or those which have been demolished, do not appear in AddressBase Core. In order to keep AddressBase Core as simple as possible, these records are not present. If these are critical to you, please look at AddressBase Premium.
AddressBase Core is released weekly and has a different data extraction date compared to the 6-weekly release schedule of the other AddressBase products. Due to these differences, AddressBase Core will not correspond to any of the Epochs.
AddressBase Core covers Great Britain only, i.e. England, Wales and Scotland. It does not include Northern Ireland and the Channel Islands.
The database is a vital component of the single address gazetteer database and is in each of the AddressBase products where there has been a match confirming the address to the LLPG address.
This release note provides information about the release of the AddressBase Core product on 10 December 2024.
*. These counts are based on a Managed Great Britain Set (MGBS). If you ordered your national coverage via the online ordering system using a polygon outline, your counts may differ.
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.
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:
The following information relates to the currency of the source data used in the creation of this release of AddressBase Core:
Release notes listed here provide information about the current release of AddressBase Core and the previous nine releases.
Please note: There will be no release of AddressBase Core on 31 January 2024 due to a company-wide shutdown over the festive period. Releases on 24 December 2024 and 07 January 2025 remain unaffected.
This release note provides information about the 23 December 2024 release of AddressBase Core.
This release note provides information about the 17 December 2024 release of AddressBase Core.
This release note provides information about the 10 December 2024 release of AddressBase Core.
This release note provides information about the 03 December 2024 release of AddressBase Core.
This release note provides information about the 26 November 2024 release of AddressBase Core.
This release note provides information about the 19 November 2024 release of AddressBase Core.
This release note provides information about the 12 November 2024 release of AddressBase Core.
This release note provides information about the 05 November 2024 release of AddressBase Core.
This release note provides information about the 29 October 2024 release of AddressBase Core.
This release note provides information about the 22 October 2024 release of AddressBase Core.
This release note provides information about the release of the AddressBase Core product on 03 December 2024.
[*] These counts are based on a Managed Great Britain Set (MGBS). If you ordered your national coverage via the online ordering system using a polygon outline, your counts may differ.
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.
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:
The following information relates to the currency of the source data used in the creation of this release of AddressBase Core:
This release note provides information about the release of the AddressBase Core product on 26 November 2024.
*These counts are based on a Managed Great Britain Set (MGBS). If you ordered your national coverage via the online ordering system using a polygon outline, your counts may differ.
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.
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:
The following information relates to the currency of the source data used in the creation of this release of AddressBase Core:
This release note provides information about the release of the AddressBase Core product on 12 November 2024.
*These counts are based on a Managed Great Britain Set (MGBS). If you ordered your national coverage via the online ordering system using a polygon outline, your counts may differ.
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.
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:
The following information relates to the currency of the source data used in the creation of this release of AddressBase Core:
With a Secure File Transfer Protocol (SFTP) order, the same folder structure is supplied as in . The filenames will be slightly different, reflecting the SFTP order number, and the Docs folder will be empty.
When you have placed an order for a product, the data will become available as a series of zipped data files. To unzip these files, please refer to .
Code List Name:
Code List Name:
Code List Name:
Code List Name:
Product Announcements
Please see for instructions on how to load and work with AddressBase data; this is a composite guide for , and .
Access to this product is free for Public Sector Geospatial Agreement (PSGA) Members. Find out if you are a PSGA Member or download a sample of AddressBase data by accessing the , which has links to all of the relevant resources. Alternatively, you can try out the full product by applying for .
AddressBase, AddressBase Plus and AddressBase Plus Islands are also available from Ordnance Survey as a supply in GML format. Loading GML into most GIS applications requires the use of third-party translation software, which is not covered in this guide. If more information is required in the loading of GML format, please
Note - When using CSV data in ArcGIS Pro, it is necessary to have column headings. Please ensure that headings have already been prepared as instructed .
Navigate to the location with the merged AddressBase or AddressBase Plus CSV file with the appended headers that you created in . Select the file and click OK.
Change the Coordinate System to British_National_Grid by clicking the globe icon .
Note - When using CSV data in ArcGIS , it is necessary to have column headings. Please ensure that headings have already been prepared as instructed .
Note - When using CSV data in MapInfo, it is not a critical requirement to have column headings. However, for ease of use we recommend using the headings supplied by Ordnance Survey. Instructions on how to merge the data and append the header files can be found in .
Click Browse next to the filename and locate the CSV file that was created in , containing the merged header files and AddressBase data.
Note - These steps describe how to load AddressBase into a PostGreSQL database using the text files created by following the instructions in to merge the CSV files.
Prepare the text files as described in .
Depending on the data to be loaded, download the SQL file from either the AddressBase or AddressBase_Plus_and_Island folder on:
Click the edit icon .
Once the data is copied, the next stage is to unzip the *.zip files to *.csv. This can be done using a package such as Winzip or 7Zip. Please see the for more information.
Go to the OS GitHub repository:
Note - The following instructions assume that users have basic knowledge of Microsoft SQL Server and that the CSV data is already prepared as described in .
Your CSV file should have a header row already prepared in . Ensure the Column names in the first data row is ticked.
It imports the GML 3.2.1 schemas which rely on XML as defined by W3C at:
Information about Unicode and UTF-8, the character encoding we have chosen, is available on the Unicode Consortium website:
See for specific GML examples.
In the above example, streetsearchtext, localitysearchtext, and townsearchtext represent user- entered search terms (which could be parameters within an SQL function) and the GetFormattedAddress(*) function is a hypothetical user-defined function that returns the formatted address as a single string (suitable for display in the user interface). For more information on formatting addresses, please see .
This guide outlines a methodology for structuring and layering a single address label, providing suggested logic to build both the Delivery Point and Geographic Address. The logic in is applicable to AddressBase, AddressBase Plus and AddressBase Plus Islands. The logic in is only applicable to AddressBase Plus and AddressBase Plus Islands.
An example of SQL logic to create a single-line Delivery Point Address is on our GitHub repository which should be used under the following considerations:
Building a single-line, formatted address for a Geographic Address is slightly more complicated than for a Delivery Point Address due to the need to preformat the SAO and PAO number/range strings. However, once this is done, the process is largely the same as before: the calculated fields should be checked in the order shown previously in , and those that have values should be concatenated together into a single line. Generally, address components should be separated by a comma followed by a single space (‘, ’), although sometimes only a space is used between a PAO number/range string and a street description. This is down to personal preference.
Example SQL logic to create a single-line Geographic Address can be found , which should be used under the following considerations:
Access to this product is free for Public Sector Geospatial Agreement (PSGA) Members. Find out if you are a PSGA Member or download a sample of AddressBase Core data by accessing the , which has with links to all of the relevant resources. Alternatively, you can try out the full product by applying for .
1
Matched manually to the nearest accessible Street.
2
Matched spatially to the nearest USRN. Not necessarily the access street.
1535
EPPING FOREST DISTRICT COUNCIL
English Shire District
Y
N
1540
HARLOW DISTRICT COUNCIL
English Shire District
Y
N
1545
MALDON DISTRICT COUNCIL
English Shire District
Y
N
1550
ROCHFORD DISTRICT COUNCIL
English Shire District
Y
N
1560
TENDRING DISTRICT COUNCIL
English Shire District
Y
N
1570
UTTLESFORD DISTRICT COUNCIL
English Shire District
Y
N
1585
ESSEX COUNTY COUNCIL
English County
N
Y
1590
SOUTHEND-ON-SEA CITY COUNCIL
English Unitary
Y
Y
1595
THURROCK COUNCIL
English Unitary
Y
Y
1600
GLOUCESTERSHIRE COUNTY COUNCIL
English County
N
Y
1605
CHELTENHAM BOROUGH COUNCIL
English Shire District
Y
N
1610
COTSWOLD DISTRICT COUNCIL
English Shire District
Y
N
1615
FOREST OF DEAN DISTRICT COUNCIL
English Shire District
Y
N
1620
GLOUCESTER CITY COUNCIL
English Shire District
Y
N
1625
STROUD DISTRICT COUNCIL
English Shire District
Y
N
1630
TEWKESBURY BOROUGH COUNCIL
English Shire District
Y
N
1705
BASINGSTOKE AND DEANE BOROUGH COUNCIL
English Shire District
Y
N
1710
EAST HAMPSHIRE DISTRICT COUNCIL
English Shire District
Y
N
1715
EASTLEIGH BOROUGH COUNCIL
English Shire District
Y
N
1720
FAREHAM BOROUGH COUNCIL
English Shire District
Y
N
1725
GOSPORT BOROUGH COUNCIL
English Shire District
Y
N
1730
HART DISTRICT COUNCIL
English Shire District
Y
N
1735
HAVANT BOROUGH COUNCIL
English Shire District
Y
N
1740
NEW FOREST DISTRICT COUNCIL
English Shire District
Y
N
1750
RUSHMOOR BOROUGH COUNCIL
English Shire District
Y
N
1760
TEST VALLEY BOROUGH COUNCIL
English Shire District
Y
N
1765
WINCHESTER CITY COUNCIL
English Shire District
Y
N
1770
HAMPSHIRE COUNTY COUNCIL
English County
N
Y
1775
PORTSMOUTH CITY COUNCIL
English Unitary
Y
Y
1780
SOUTHAMPTON CITY COUNCIL
English Unitary
Y
Y
1805
BROMSGROVE DISTRICT COUNCIL
English Shire District
Y
N
1820
MALVERN HILLS DISTRICT COUNCIL
English Shire District
Y
N
1825
REDDITCH BOROUGH COUNCIL
English Shire District
Y
N
1835
WORCESTER CITY COUNCIL
English Shire District
Y
N
1840
WYCHAVON DISTRICT COUNCIL
English Shire District
Y
N
1845
WYRE FOREST DISTRICT COUNCIL
English Shire District
Y
N
1850
HEREFORDSHIRE COUNCIL
English Unitary
Y
Y
1855
WORCESTERSHIRE COUNTY COUNCIL
English County
N
Y
1900
HERTFORDSHIRE COUNTY COUNCIL
English County
N
Y
1905
BROXBOURNE BOROUGH COUNCIL
English Shire District
Y
N
1910
DACORUM BOROUGH COUNCIL
English Shire District
Y
N
1915
EAST HERTFORDSHIRE DISTRICT COUNCIL
English Shire District
Y
N
1920
HERTSMERE BOROUGH COUNCIL
English Shire District
Y
N
1925
NORTH HERTFORDSHIRE DISTRICT COUNCIL
English Shire District
Y
N
1930
ST ALBANS CITY AND DISTRICT COUNCIL
English Shire District
Y
N
1935
STEVENAGE BOROUGH COUNCIL
English Shire District
Y
N
1940
THREE RIVERS DISTRICT COUNCIL
English Shire District
Y
N
1945
WATFORD BOROUGH COUNCIL
English Shire District
Y
N
1950
WELWYN HATFIELD BOROUGH COUNCIL
English Shire District
Y
N
2001
EAST RIDING OF YORKSHIRE COUNCIL
English Unitary
Y
Y
2002
NORTH EAST LINCOLNSHIRE COUNCIL
English Unitary
Y
Y
2003
NORTH LINCOLNSHIRE COUNCIL
English Unitary
Y
Y
2004
HULL CITY COUNCIL
English Unitary
Y
Y
2114
ISLE OF WIGHT COUNCIL
English Unitary
Y
Y
2205
ASHFORD BOROUGH COUNCIL
English Shire District
Y
N
2210
CANTERBURY CITY COUNCIL
English Shire District
Y
N
2215
DARTFORD BOROUGH COUNCIL
English Shire District
Y
N
2220
DOVER DISTRICT COUNCIL
English Shire District
Y
N
2230
GRAVESHAM BOROUGH COUNCIL
English Shire District
Y
N
2235
MAIDSTONE BOROUGH COUNCIL
English Shire District
Y
N
2245
SEVENOAKS DISTRICT COUNCIL
English Shire District
Y
N
2250
FOLKESTONE & HYTHE DISTRICT COUNCIL
English Shire District
Y
N
2255
SWALE BOROUGH COUNCIL
English Shire District
Y
N
2260
THANET DISTRICT COUNCIL
English Shire District
Y
N
2265
TONBRIDGE & MALLING BOROUGH COUNCIL
English Shire District
Y
N
2270
TUNBRIDGE WELLS BOROUGH COUNCIL
English Shire District
Y
N
2275
KENT COUNTY COUNCIL
English County
N
Y
2280
MEDWAY COUNCIL
English Unitary
Y
Y
2315
BURNLEY BOROUGH COUNCIL
English Shire District
Y
N
2320
CHORLEY BOROUGH COUNCIL
English Shire District
Y
N
2325
FYLDE BOROUGH COUNCIL
English Shire District
Y
N
2330
HYNDBURN BOROUGH COUNCIL
English Shire District
Y
N
2335
LANCASTER CITY COUNCIL
English Shire District
Y
N
2340
PENDLE BOROUGH COUNCIL
English Shire District
Y
N
2345
PRESTON CITY COUNCIL
English Shire District
Y
N
2350
RIBBLE VALLEY BOROUGH COUNCIL
English Shire District
Y
N
2355
ROSSENDALE BOROUGH COUNCIL
English Shire District
Y
N
2360
SOUTH RIBBLE BOROUGH COUNCIL
English Shire District
Y
N
2365
WEST LANCASHIRE BOROUGH COUNCIL
English Shire District
Y
N
2370
WYRE BOROUGH COUNCIL
English Shire District
Y
N
2371
LANCASHIRE COUNTY COUNCIL
English County
N
Y
2372
BLACKBURN WITH DARWEN BOROUGH COUNCIL
English Unitary
Y
Y
2373
BLACKPOOL BOROUGH COUNCIL
English Unitary
Y
Y
2405
BLABY DISTRICT COUNCIL
English Shire District
Y
N
2410
CHARNWOOD BOROUGH COUNCIL
English Shire District
Y
N
2415
HARBOROUGH DISTRICT COUNCIL
English Shire District
Y
N
2420
HINCKLEY & BOSWORTH BOROUGH COUNCIL
English Shire District
Y
N
2430
MELTON BOROUGH COUNCIL
English Shire District
Y
N
2435
NORTH WEST LEICESTERSHIRE DISTRICT COUNCIL
English Shire District
Y
N
2440
OADBY AND WIGSTON BOROUGH COUNCIL
English Shire District
Y
N
2460
LEICESTERSHIRE COUNTY COUNCIL
English County
N
Y
2465
LEICESTER CITY COUNCIL
English Unitary
Y
Y
2470
RUTLAND COUNTY COUNCIL
English Unitary
Y
Y
2500
LINCOLNSHIRE COUNTY COUNCIL
English County
N
Y
2505
BOSTON BOROUGH COUNCIL
English Shire District
Y
N
2510
EAST LINDSEY DISTRICT COUNCIL
English Shire District
Y
N
2515
CITY OF LINCOLN COUNCIL
English Shire District
Y
N
2520
NORTH KESTEVEN DISTRICT COUNCIL
English Shire District
Y
N
2525
SOUTH HOLLAND DISTRICT COUNCIL
English Shire District
Y
N
2530
SOUTH KESTEVEN DISTRICT COUNCIL
English Shire District
Y
N
2535
WEST LINDSEY DISTRICT COUNCIL
English Shire District
Y
N
2600
NORFOLK COUNTY COUNCIL
English County
N
Y
2605
BRECKLAND DISTRICT COUNCIL
English Shire District
Y
N
2610
BROADLAND DISTRICT COUNCIL
English Shire District
Y
N
2615
GREAT YARMOUTH BOROUGH COUNCIL
English Shire District
Y
N
2620
NORTH NORFOLK DISTRICT COUNCIL
English Shire District
Y
N
2625
NORWICH CITY COUNCIL
English Shire District
Y
N
2630
SOUTH NORFOLK DISTRICT COUNCIL
English Shire District
Y
N
2635
BOROUGH OF KING'S LYNN AND WEST NORFOLK
English Shire District
Y
N
2741
CITY OF YORK COUNCIL
English Unitary
Y
Y
2745
NORTH YORKSHIRE COUNCIL
English Unitary
Y
Y
2840
NORTH NORTHAMPTONSHIRE COUNCIL
English Unitary
Y
Y
2845
WEST NORTHAMPTONSHIRE COUNCIL
English Unitary
Y
Y
2935
NORTHUMBERLAND COUNTY COUNCIL
English Unitary
Y
Y
3005
ASHFIELD DISTRICT COUNCIL
English Shire District
Y
N
3010
BASSETLAW DISTRICT COUNCIL
English Shire District
Y
N
3015
BROXTOWE BOROUGH COUNCIL
English Shire District
Y
N
3020
GEDLING BOROUGH COUNCIL
English Shire District
Y
N
3025
MANSFIELD DISTRICT COUNCIL
English Shire District
Y
N
3030
NEWARK & SHERWOOD DISTRICT COUNCIL
English Shire District
Y
N
3040
RUSHCLIFFE BOROUGH COUNCIL
English Shire District
Y
N
3055
NOTTINGHAMSHIRE COUNTY COUNCIL
English County
N
Y
3060
NOTTINGHAM CITY COUNCIL
English Unitary
Y
Y
3100
OXFORDSHIRE COUNTY COUNCIL
English County
N
Y
3105
CHERWELL DISTRICT COUNCIL
English Shire District
Y
N
3110
OXFORD CITY COUNCIL
English Shire District
Y
N
3115
SOUTH OXFORDSHIRE DISTRICT COUNCIL
English Shire District
Y
N
3120
VALE OF WHITE HORSE DISTRICT COUNCIL
English Shire District
Y
N
3125
WEST OXFORDSHIRE DISTRICT COUNCIL
English Shire District
Y
N
3240
TELFORD & WREKIN COUNCIL
English Unitary
Y
Y
3245
SHROPSHIRE COUNCIL
English Unitary
Y
Y
3300
SOMERSET COUNCIL
English Unitary
Y
Y
3405
CANNOCK CHASE DISTRICT COUNCIL
English Shire District
Y
N
3410
EAST STAFFORDSHIRE BOROUGH COUNCIL
English Shire District
Y
N
3415
LICHFIELD DISTRICT COUNCIL
English Shire District
Y
N
3420
NEWCASTLE-UNDER-LYME BOROUGH COUNCIL
English Shire District
Y
N
3425
STAFFORD BOROUGH COUNCIL
English Shire District
Y
N
3430
SOUTH STAFFORDSHIRE COUNCIL
English Shire District
Y
N
3435
STAFFORDSHIRE MOORLANDS DISTRICT COUNCIL
English Shire District
Y
N
3445
TAMWORTH BOROUGH COUNCIL
English Shire District
Y
N
3450
STAFFORDSHIRE COUNTY COUNCIL
English County
N
Y
3455
STOKE-ON-TRENT CITY COUNCIL
English Unitary
Y
Y
3500
SUFFOLK COUNTY COUNCIL
English County
N
Y
3505
BABERGH DISTRICT COUNCIL
English Shire District
Y
N
3515
IPSWICH BOROUGH COUNCIL
English Shire District
Y
N
3520
MID SUFFOLK DISTRICT COUNCIL
English Shire District
Y
N
3540
EAST SUFFOLK COUNCIL
English Shire District
Y
N
3545
WEST SUFFOLK COUNCIL
English Shire District
Y
N
3600
SURREY COUNTY COUNCIL
English County
N
Y
3605
ELMBRIDGE BOROUGH COUNCIL
English Shire District
Y
N
3610
EPSOM AND EWELL BOROUGH COUNCIL
English Shire District
Y
N
3615
GUILDFORD BOROUGH COUNCIL
English Shire District
Y
N
3620
MOLE VALLEY DISTRICT COUNCIL
English Shire District
Y
N
3625
REIGATE AND BANSTEAD BOROUGH COUNCIL
English Shire District
Y
N
3630
RUNNYMEDE BOROUGH COUNCIL
English Shire District
Y
N
3635
SPELTHORNE BOROUGH COUNCIL
English Shire District
Y
N
3640
SURREY HEATH BOROUGH COUNCIL
English Shire District
Y
N
3645
TANDRIDGE DISTRICT COUNCIL
English Shire District
Y
N
3650
WAVERLEY BOROUGH COUNCIL
English Shire District
Y
N
3655
WOKING BOROUGH COUNCIL
English Shire District
Y
N
3700
WARWICKSHIRE COUNTY COUNCIL
English County
N
Y
3705
NORTH WARWICKSHIRE BOROUGH COUNCIL
English Shire District
Y
N
3710
NUNEATON AND BEDWORTH BOROUGH COUNCIL
English Shire District
Y
N
3715
RUGBY BOROUGH COUNCIL
English Shire District
Y
N
3720
STRATFORD-ON-AVON DISTRICT COUNCIL
English Shire District
Y
N
3725
WARWICK DISTRICT COUNCIL
English Shire District
Y
N
3800
WEST SUSSEX COUNTY COUNCIL
English County
N
Y
3805
ADUR DISTRICT COUNCIL
English Shire District
Y
N
3810
ARUN DISTRICT COUNCIL
English Shire District
Y
N
3815
CHICHESTER DISTRICT COUNCIL
English Shire District
Y
N
3820
CRAWLEY BOROUGH COUNCIL
English Shire District
Y
N
3825
HORSHAM DISTRICT COUNCIL
English Shire District
Y
N
3830
MID SUSSEX DISTRICT COUNCIL
English Shire District
Y
N
3835
WORTHING BOROUGH COUNCIL
English Shire District
Y
N
3935
SWINDON BOROUGH COUNCIL
English Unitary
Y
Y
3940
WILTSHIRE COUNCIL
English Unitary
Y
Y
4205
BOLTON METROPOLITAN BOROUGH COUNCIL
English Unitary
Y
Y
4210
BURY METROPOLITAN BOROUGH COUNCIL
English Unitary
Y
Y
4215
MANCHESTER CITY COUNCIL
English Unitary
Y
Y
4220
OLDHAM METROPOLITAN BOROUGH COUNCIL
English Unitary
Y
Y
4225
ROCHDALE BOROUGH COUNCIL
English Unitary
Y
Y
4230
SALFORD CITY COUNCIL
English Unitary
Y
Y
4235
STOCKPORT METROPOLITAN BOROUGH COUNCIL
English Unitary
Y
Y
4240
TAMESIDE METROPOLITAN BOROUGH COUNCIL
English Unitary
Y
Y
4245
TRAFFORD METROPOLITAN BOROUGH COUNCIL
English Unitary
Y
Y
4250
WIGAN METROPOLITAN BOROUGH COUNCIL
English Unitary
Y
Y
4305
KNOWSLEY METROPOLITAN BOROUGH COUNCIL
English Unitary
Y
Y
4310
LIVERPOOL CITY COUNCIL
English Unitary
Y
Y
4315
ST. HELENS COUNCIL
English Unitary
Y
Y
4320
SEFTON METROPOLITAN BOROUGH COUNCIL
English Unitary
Y
Y
4325
WIRRAL BOROUGH COUNCIL
English Unitary
Y
Y
4405
BARNSLEY METROPOLITAN BOROUGH COUNCIL
English Unitary
Y
Y
4410
CITY OF DONCASTER COUNCIL
English Unitary
Y
Y
4415
ROTHERHAM METROPOLITAN BOROUGH COUNCIL
English Unitary
Y
Y
4420
SHEFFIELD CITY COUNCIL
English Unitary
Y
Y
4505
GATESHEAD METROPOLITAN BOROUGH COUNCIL
English Unitary
Y
Y
4510
NEWCASTLE CITY COUNCIL
English Unitary
Y
Y
4515
NORTH TYNESIDE COUNCIL
English Unitary
Y
Y
4520
SOUTH TYNESIDE COUNCIL
English Unitary
Y
Y
4525
SUNDERLAND CITY COUNCIL
English Unitary
Y
Y
4605
BIRMINGHAM CITY COUNCIL
English Unitary
Y
Y
4610
COVENTRY CITY COUNCIL
English Unitary
Y
Y
4615
DUDLEY METROPOLITAN BOROUGH COUNCIL
English Unitary
Y
Y
4620
SANDWELL METROPOLITAN BOROUGH COUNCIL
English Unitary
Y
Y
4625
SOLIHULL METROPOLITAN BOROUGH COUNCIL
English Unitary
Y
Y
4630
WALSALL METROPOLITAN BOROUGH COUNCIL
English Unitary
Y
Y
4635
CITY OF WOLVERHAMPTON COUNCIL
English Unitary
Y
Y
4705
CITY OF BRADFORD METROPOLITAN DISTRICT COUNCIL
English Unitary
Y
Y
4710
CALDERDALE METROPOLITAN BOROUGH COUNCIL
English Unitary
Y
Y
4715
KIRKLEES COUNCIL
English Unitary
Y
Y
4720
LEEDS CITY COUNCIL
English Unitary
Y
Y
4725
CITY OF WAKEFIELD METROPOLITAN DISTRICT COUNCIL
English Unitary
Y
Y
5030
CITY OF LONDON CORPORATION
English Unitary
Y
Y
5060
LONDON BOROUGH OF BARKING AND DAGENHAM
English Unitary
Y
Y
5090
LONDON BOROUGH OF BARNET
English Unitary
Y
Y
5120
LONDON BOROUGH OF BEXLEY
English Unitary
Y
Y
5150
LONDON BOROUGH OF BRENT
English Unitary
Y
Y
5180
LONDON BOROUGH OF BROMLEY
English Unitary
Y
Y
5210
LONDON BOROUGH OF CAMDEN
English Unitary
Y
Y
5240
LONDON BOROUGH OF CROYDON
English Unitary
Y
Y
5270
LONDON BOROUGH OF EALING
English Unitary
Y
Y
5300
LONDON BOROUGH OF ENFIELD
English Unitary
Y
Y
5330
ROYAL BOROUGH OF GREENWICH
English Unitary
Y
Y
5360
LONDON BOROUGH OF HACKNEY
English Unitary
Y
Y
5390
LONDON BOROUGH OF HAMMERSMITH & FULHAM
English Unitary
Y
Y
5420
LONDON BOROUGH OF HARINGEY
English Unitary
Y
Y
5450
LONDON BOROUGH OF HARROW
English Unitary
Y
Y
5480
LONDON BOROUGH OF HAVERING
English Unitary
Y
Y
5510
LONDON BOROUGH OF HILLINGDON
English Unitary
Y
Y
5540
LONDON BOROUGH OF HOUNSLOW
English Unitary
Y
Y
5570
LONDON BOROUGH OF ISLINGTON
English Unitary
Y
Y
5600
ROYAL BOROUGH OF KENSINGTON AND CHELSEA
English Unitary
Y
Y
5630
ROYAL BOROUGH OF KINGSTON UPON THAMES
English Unitary
Y
Y
5660
LONDON BOROUGH OF LAMBETH
English Unitary
Y
Y
5690
LONDON BOROUGH OF LEWISHAM
English Unitary
Y
Y
5720
LONDON BOROUGH OF MERTON
English Unitary
Y
Y
5750
LONDON BOROUGH OF NEWHAM
English Unitary
Y
Y
5780
LONDON BOROUGH OF REDBRIDGE
English Unitary
Y
Y
5810
LONDON BOROUGH OF RICHMOND UPON THAMES
English Unitary
Y
Y
5840
LONDON BOROUGH OF SOUTHWARK
English Unitary
Y
Y
5870
LONDON BOROUGH OF SUTTON
English Unitary
Y
Y
5900
LONDON BOROUGH OF TOWER HAMLETS
English Unitary
Y
Y
5930
LONDON BOROUGH OF WALTHAM FOREST
English Unitary
Y
Y
5960
LONDON BOROUGH OF WANDSWORTH
English Unitary
Y
Y
5990
CITY OF WESTMINSTER
English Unitary
Y
Y
6805
ISLE OF ANGLESEY COUNTY COUNCIL
Welsh Unitary
Y
Y
6810
GWYNEDD COUNCIL
Welsh Unitary
Y
Y
6815
CITY OF CARDIFF COUNCIL
Welsh Unitary
Y
Y
6820
CEREDIGION COUNTY COUNCIL
Welsh Unitary
Y
Y
6825
CARMARTHENSHIRE COUNTY COUNCIL
Welsh Unitary
Y
Y
6830
DENBIGHSHIRE COUNTY COUNCIL
Welsh Unitary
Y
Y
6835
FLINTSHIRE COUNTY COUNCIL
Welsh Unitary
Y
Y
6840
MONMOUTHSHIRE COUNTY COUNCIL
Welsh Unitary
Y
Y
6845
PEMBROKESHIRE COUNTY COUNCIL
Welsh Unitary
Y
Y
6850
POWYS COUNTY COUNCIL
Welsh Unitary
Y
Y
6855
CITY AND COUNTY OF SWANSEA COUNCIL
Welsh Unitary
Y
Y
6905
CONWY COUNTY BOROUGH COUNCIL
Welsh Unitary
Y
Y
6910
BLAENAU GWENT COUNTY BOROUGH COUNCIL
Welsh Unitary
Y
Y
6915
BRIDGEND COUNTY BOROUGH COUNCIL
Welsh Unitary
Y
Y
6920
CAERPHILLY COUNTY BOROUGH COUNCIL
Welsh Unitary
Y
Y
6925
MERTHYR TYDFIL COUNTY BOROUGH COUNCIL
Welsh Unitary
Y
Y
6930
NEATH PORT TALBOT COUNTY BOROUGH COUNCIL
Welsh Unitary
Y
Y
6935
NEWPORT CITY COUNCIL
Welsh Unitary
Y
Y
6940
RHONDDA CYNON TAF COUNTY BOROUGH COUNCIL
Welsh Unitary
Y
Y
6945
TORFAEN COUNTY BOROUGH COUNCIL
Welsh Unitary
Y
Y
6950
VALE OF GLAMORGAN COUNCIL
Welsh Unitary
Y
Y
6955
WREXHAM COUNTY BOROUGH COUNCIL
Welsh Unitary
Y
Y
8130
ANTRIM AND NEWTOWNABBEY
Islands
Y
N
8131
ARMAGH BANBRIDGE AND CRAIGAVON
Islands
Y
N
8132
BELFAST
Islands
Y
N
8133
CAUSEWAY COAST AND GLENS
Islands
Y
N
8134
DERRY AND STRABANE
Islands
Y
N
8135
FERMANAGH AND OMAGH
Islands
Y
N
8136
LISBURN AND CASTLEREAGH
Islands
Y
N
8137
MID AND EAST ANTRIM
Islands
Y
N
8138
MID ULSTER
Islands
Y
N
8139
NEWRY MOURNE AND DOWN
Islands
Y
N
8140
NORTH DOWN AND ARDS
Islands
Y
N
8200
JERSEY
Islands
Y
N
8205
GUERNSEY
Islands
Y
N
9000
ORKNEY ISLANDS COUNCIL
Scottish Unitary
Y
N
9010
SHETLAND ISLANDS COUNCIL
Scottish Unitary
Y
N
9020
WESTERN ISLES COUNCIL (COMHAIRLE NAN EILEAN SIAR)
Scottish Unitary
Y
N
9051
ABERDEEN CITY COUNCIL
Scottish Unitary
Y
N
9052
ABERDEENSHIRE COUNCIL
Scottish Unitary
Y
N
9053
ANGUS COUNCIL
Scottish Unitary
Y
N
9054
ARGYLL & BUTE COUNCIL
Scottish Unitary
Y
N
9055
SCOTTISH BORDERS COUNCIL
Scottish Unitary
Y
N
9056
CLACKMANNANSHIRE COUNCIL
Scottish Unitary
Y
N
9057
WEST DUNBARTONSHIRE COUNCIL
Scottish Unitary
Y
N
9058
DUMFRIES AND GALLOWAY COUNCIL
Scottish Unitary
Y
N
9059
DUNDEE CITY COUNCIL
Scottish Unitary
Y
N
9060
EAST AYRSHIRE COUNCIL
Scottish Unitary
Y
N
9061
EAST DUNBARTONSHIRE COUNCIL
Scottish Unitary
Y
N
9062
EAST LOTHIAN COUNCIL
Scottish Unitary
Y
N
9063
EAST RENFREWSHIRE COUNCIL
Scottish Unitary
Y
N
9064
CITY OF EDINBURGH COUNCIL
Scottish Unitary
Y
N
9065
FALKIRK COUNCIL
Scottish Unitary
Y
N
9066
FIFE COUNCIL
Scottish Unitary
Y
N
9067
GLASGOW CITY COUNCIL
Scottish Unitary
Y
N
9068
HIGHLAND COUNCIL
Scottish Unitary
Y
N
9069
INVERCLYDE COUNCIL
Scottish Unitary
Y
N
9070
MIDLOTHIAN COUNCIL
Scottish Unitary
Y
N
9071
MORAY COUNCIL
Scottish Unitary
Y
N
9072
NORTH AYRSHIRE COUNCIL
Scottish Unitary
Y
N
9073
NORTH LANARKSHIRE COUNCIL
Scottish Unitary
Y
N
9074
PERTH & KINROSS COUNCIL
Scottish Unitary
Y
N
9075
RENFREWSHIRE COUNCIL
Scottish Unitary
Y
N
9076
SOUTH AYRSHIRE COUNCIL
Scottish Unitary
Y
N
9077
SOUTH LANARKSHIRE COUNCIL
Scottish Unitary
Y
N
9078
STIRLING COUNCIL
Scottish Unitary
Y
N
9079
WEST LOTHIAN COUNCIL
Scottish Unitary
Y
N
9065
FALKIRK COUNCIL
Scottish Unitary
Y
STREET_SUBMITTER_FLAG
9066
FIFE COUNCIL
Scottish Unitary
Y
N
9067
GLASGOW CITY COUNCIL
Scottish Unitary
Y
Y
9068
HIGHLAND COUNCIL
Scottish Unitary
Y
Y
9069
INVERCLYDE COUNCIL
Scottish Unitary
Y
Y
9070
MIDLOTHIAN COUNCIL
Scottish Unitary
Y
Y
9071
MORAY COUNCIL
Scottish Unitary
Y
Y
9072
NORTH AYRSHIRE COUNCIL
Scottish Unitary
Y
Y
9073
NORTH LANARKSHIRE COUNCIL
Scottish Unitary
Y
Y
9074
PERTH & KINROSS COUNCIL
Scottish Unitary
Y
Y
9075
RENFREWSHIRE COUNCIL
Scottish Unitary
Y
Y
9076
SOUTH AYRSHIRE COUNCIL
Scottish Unitary
Y
Y
9077
SOUTH LANARKSHIRE COUNCIL
Scottish Unitary
Y
Y
9078
STIRLING COUNCIL
Scottish Unitary
Y
Y
9079
WEST LOTHIAN COUNCIL
Scottish Unitary
Y
Y
9065
FALKIRK COUNCIL
Scottish Unitary
Y
Y
9066
FIFE COUNCIL
Scottish Unitary
Y
Y
9067
GLASGOW CITY COUNCIL
Scottish Unitary
Y
N
9068
HIGHLAND COUNCIL
Scottish Unitary
Y
N
9069
INVERCLYDE COUNCIL
Scottish Unitary
Y
N
9070
MIDLOTHIAN COUNCIL
Scottish Unitary
Y
N
9071
MORAY COUNCIL
Scottish Unitary
Y
N
9072
NORTH AYRSHIRE COUNCIL
Scottish Unitary
N
Y
9073
NORTH LANARKSHIRE COUNCIL
Scottish Unitary
Y
Y
9074
PERTH & KINROSS COUNCIL
Scottish Unitary
Y
Y
9075
RENFREWSHIRE COUNCIL
Scottish Unitary
Y
Y
9076
SOUTH AYRSHIRE COUNCIL
Scottish Unitary
Y
Y
9077
SOUTH LANARKSHIRE COUNCIL
Scottish Unitary
Y
Y
9078
STIRLING COUNCIL
Scottish Unitary
Y
Y
9079
WEST LOTHIAN COUNCIL
Scottish Unitary
Y
Y
9076
SOUTH AYRSHIRE COUNCIL
Scottish Unitary
Y
Y
9077
SOUTH LANARKSHIRE COUNCIL
Scottish Unitary
Y
Y
9078
STIRLING COUNCIL
Scottish Unitary
Y
Y
9079
WEST LOTHIAN COUNCIL
Scottish Unitary
Y
Y
gml
xsi
Built into XML – http://www.w3.org/TR/xmlschema-1/
xlink
Xlink – http://www.w3.org/1999/xlink
<abpl:addressMember>
Address
Rose Cottage, Main Street, Fieldtown, Addressville, SW99 9ZZ
Rose Cottage, Main Street, Ashford, AS45 9PP
Rose Cottage, Main Street, Buxtew, Monley, MO88 4TY
And so on...
Business Name
Organisation_Name
Organisation
PAO_Text
SAO_Text
Flat/Subdivision Name
Sub_Building_Name Department_Name
SAO_Text
Flat/Subdivision Number
Sub_Building_Name
SAO_StartNumber SAO_StartSuffix SAO_EndNumber
SAO_EndSuffix
Building Name
Building_Name
PAO_Text
Building Number
Building_Number
Building_Name (in cases where a suffix or range is present)
PAO_StartNumber PAO_StartSuffix PAO_EndNumber
PAO_EndSuffix
Street
Thoroughfare Dependent_Thoroughfare
Street PAO_Text
Locality
Dependent_Locality Double_Dependent_Locality
Locality Town Street
Town
Dependent_Locality Post_Town
Town Locality
Postcode
Postcode
Postcode_Locator
123456789012
4 THE MEADOWS HIGH STREET WALTHAMSDALE BURRIDGE BU27 9UB
Local Authority
123456789012
FLAT 4 THE MEADOWS HIGH STREET WALTHAMSDALE BURRIDGE BU27 9UB
PAF
123456789013
4 HIGH STREET WALTHAMSDALE BURRIDGE BU27 9UB
Non-postal
894756389092
4 HIGH STREET WESTVILLE SUNNYTOWN WV17 7HL
Geographic + PAF
894756389132
ROSE COTTAGE 4 HIGH STREET WESTVILLE SUNNYTOWN WV17 7HL
Geographic
274859037849
FLAT 4 HIGHBURY COURT HIGH STREET WESTVILLE SUNNYTOWN WV17 7HL
Geographic + PAF
482974769830
MAPS4U LTD HIGH STREET WESTVILLE SUNNYTOWN WV17 7HL
Geographic + PAF
ORGANISATION_NAME
SUB_BUILDING_NAME
BUILDING_NAME
BUILDING_NUMBER
PO_BOX_NUMBER
DEPENDENT_THOROUGHFARE (and WELSH_DEPENDENT_THOROUGHFARE)
THOROUGHFARE (and WELSH_THOROUGHFARE)
DOUBLE_DEPENDENT_LOCALITY (and WELSH_DOUBLE_DEPENDENT_LOCALITY)
DEPENDENT_LOCALITY (and WELSH_DEPENDENT_LOCALITY)
POST_TOWN (and WELSH_POST_TOWN)
POSTCODE
ROSE COTTAGE
5 MAIN STREET
ADDRESSVILLE LONDON
SE99 9EX
DEPARTMENT_NAME
Character
ORGANISATION_NAME
Character
SUB_BUILDING_NAME
Character
BUILDING_NAME
Character
BUILDING_NUMBER
Integer
PO_BOX_NUMBER
Integer
DEPENDENT_THOROUGHFARE (or WELSH_DEPENDENT_THOROUGHFARE)
Character
THOROUGHFARE (or WELSH_THOROUGHFARE)
Character
DOUBLE_DEPENDENT_LOCALITY (or WELSH_DOUBLE_DEPENDENT_LOCALITY)
Character
DEPENDENT_LOCALITY (or WELSH_DEPENDENT_LOCALITY)
Character
POST_TOWN (or WELSH_POST_TOWN)
Character
POSTCODE
Character
DEPARTMENT_NAME
CUSTOMER SERVICE DEPARTMENT
ORGANISATION_NAME
JW SIMPSON LTD.
SUB_BUILDING_NAME
UNIT 3
BUILDING_NAME
THE OLD FORGE 7
BUILDING_NUMBER
7
PO_BOX_NUMBER
DEPENDENT_THOROUGHFARE
RICHMOND TERRACE
THOROUGHFARE
MAIN STREET
DOUBLE_DEPENDENT_LOCALITY
HOOK
DEPENDENT_LOCALITY
WARSASH
POST_TOWN
SOUTHAMPTON
POSTCODE
SO99 9ZZ
ORGANISATION_NAME
‘JWS CONSULTING’
JWS CONSULTING
PO_BOX_NUMBER
5422
PO BOX 5422
THOROUGHFARE
‘HIGH STREET’
HIGH STREET
POST_TOWN
'SPRINGFIELD’
SPRINGFIELD
POSTCODE
‘SP77 0SF’
SP77 0SF
DEPARTMENT_NAME
Null
ORGANISATION_NAME
‘TM MOTORS’
TM MOTORS
SUB_BUILDING_NAME
Null
BUILDING_NAME
‘THE OLD BARN’
THE OLD BARN
BUILDING_NUMBER
0 (or null)
PO_BOX_NUMBER
0 (or null)
DEPENDENT_THOROUGHFARE
Null
THOROUGHFARE
‘HORSHAM LANE’
HORSHAM LANE
DOUBLE_DEPENDENT_LOCALITY
Null
DEPENDENT_LOCALITY
Null
POST_TOWN
‘HORSHAM’
HORSHAM
POSTCODE
‘RH12 1EQ’
RH12 1EQ
LA_ORGANISATION
Character
SAO_TEXT (or ALT_LANGUAGE_SAO_TEXT)
Character
SAO_START_NUMBER
Integer
SAO_START_SUFFIX
Character
SAO_END_NUMBER
Integer
SAO_END_SUFFIX
Character
PAO_TEXT (or ALT_LANGUAGE_PAO_TEXT)
Character
PAO_START_NUMBER
Integer
PAO_START_SUFFIX
Character
PAO_END_NUMBER
Integer
PAO_END_SUFFIX
Character
STREET_DESCRIPTION (or ALT_LANGUAGE_STREET_DESCRIPTION)
Character
LOCALITY
Character
TOWN_NAME
Character
ADMINISTRATIVE_AREA*
Character
POSTCODE_LOCATOR
Character
PAO_START_NUMBER PAO_START_SUFFIX PAO_END_NUMBER PAO_END_SUFFIX
1
1
A
1
5
1
A 5 C
Rendered PAO range
1
1A
1-5
1A-5C
PAO (number string) PAO (text)
1
1A
1A
Rose Cottage
Rose Cottage
Rendered PAO (showing street name location)
1 <street>
1A <street>
Rose Cottage, 1A
<street>
Rose Cottage,
<street>
34, CROW LANE, RAMSBOTTOM, BL0 9BR
34, CROW LANE, RAMSBOTTOM, BURY, BL0 9BR
LA_ORGANISATION SAO_TEXT
SAO (number/range string)* PAO_TEXT
PAO (number/range string)* STREET_DESCRIPTION LOCALITY
TOWN_NAME ADMINISTRATIVE_AREA
POSTCODE_LOCATOR
JW SIMPSON LTD THE ANNEXE
1A
THE OLD MILL 7–9
MAIN STREET HOOK WARSASH SOUTHAMPTON
SO99 9ZZ
PAO_TEXT
‘HIGHBURY HOUSE’
HIGHBURY HOUSE
STREET_DESCRIPTION
‘HIGH STREET’
HIGH STREET
TOWN_NAME
‘SOUTHAMPTON’
SOUTHAMPTON
ADMINISTRATIVE_AREA
‘SOUTHAMPTON’
POSTCODE_LOCATOR
‘SO77 0SF’
SO77 0SF
ORGANISATION
‘TM MOTORS’
TM MOTORS
SAO_TEXT
null
SAO (number/range string)*
null
PAO_TEXT
‘THE OLD BARN’
THE OLD BARN
PAO (number/range string)*
‘1’
1
STREET_DESCRIPTION
‘HORSHAM LANE’
HORSHAM LANE
LOCALITY
null
TOWN_NAME
‘HORSHAM’
HORSHAM
ADMINISTRATIVE_AREA
‘HORSHAM’
* Duplicate name omitted
POSTCODE_LOCATOR
‘RH12 1EQ’
RH12 1EQ
PAO_text only
PAO_text and PAO number or range
ROSE COTTAGE, MAIN STREET
ROSE COTTAGE, 11A MAIN STREET
SAO_text value only, with PAO_text value only
SAO_text value only, with PAO number/range only
THE ANNEXE, ROSE COURT, MAIN STREET
THE ANNEXE, 11A MAIN STREET
SAO number/range value only, and PAO_text value only
SAO number/range value only, and PAO number/range value only
SAO number/range value only, and both PAO_text and PAO number/range values
1A ROSE COURT, MAIN STREET
1-3, 11A MAIN STREET
1A ROSE COURT,
11A MAIN STREET
SAO_text value only with PAO_text only
SAO_text and SAO number/range and PAO_text and PAO number/range
THE ANNEXE, ROSE COTTAGE, MAIN STREET
WARDEN’S FLAT,
1A ROSE COURT,
11A MAIN STREET
Organisation Name along with all PAO + SAO fields
COTTAGE INDUSTRY LTD, THE ANNEXE,
1A ROSE COURT,
11A MAIN STREET
Locality and Town Name present
Town Name only
[first part of address, formatted as described above] MAIN STREET,
HIGHFIELD, SOUTHAMPTON
[first part of address, formatted as described above] HIGH STREET,
SOUTHAMPTON
Administrative Area name included
[first part of address, formatted as described above] MAIN STREET,
WINDSOR,
ROYAL BOROUGH OF WINDSOR AND MAIDENHEAD
With Postcode_Locator on final line
[first part of address, formatted as described above] HIGH STREET,
MILTON, ML99 0WW
2007-10-24
Date
Date columns will follow the structure: CCYY-MM-DD
Royal Mail Postcode Address File (PAF)
06 December 2024
National Land and Property Gazetteer
06 December 2024
One Scotland Gazetteer
18 November 2024
OS MasterMap Topography Layer
05 September 2024
Royal Mail Postcode Address File (PAF)
29 November 2024
National Land and Property Gazetteer
29 November 2024
One Scotland Gazetteer
18 November 2024
OS MasterMap Topography Layer
05 September 2024
Royal Mail Postcode Address File (PAF)
22 November 2024
National Land and Property Gazetteer
22 November 2024
One Scotland Gazetteer
18 November 2024
OS MasterMap Topography Layer
05 September 2024
Royal Mail Postcode Address File (PAF)
08 November 2024
National Land and Property Gazetteer
08 November 2024
One Scotland Gazetteer
28 October 2024
OS MasterMap Topography Layer
05 September 2024
AddressBase
6Gb
32Gb
AddressBase Plus
16Gb
78Gb
AddressBase Plus Islands
450Mb
2Gb
This getting started guide provides instructions for using AddressBase Core in different software applications. Users with limited technical knowledge will be able to follow this guide.
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's primary source of addressing information is Local Authorities who have the statutory responsibility to capture and maintain Great Britain's address data. This ensures that the data is both authentic and authoritative in nature. Records are supplemented with Royal Mail Postal Address File (PAF) information and additional Ordnance Survey information on the usage of the address and unique identifiers that allow links to other OS and third-party datasets. Please read Data sources in AddressBase general for further details.
Access to AddressBase Core data via a Public Sector Plan, Premium Plan, or Energy & Infrastructure plan.
Basic technical knowledge of Geographic Information Systems (GIS) and databases.
These instructions show you how to use AddressBase Core and include:
This section of the getting started guide takes you through the process of downloading and extracting your AddressBase Core supply.
AddressBase Core is supplied in two optional offerings:
As a Managed Great Britain Set (MGBS) which provides national Great Britain data in one of two formats: Comma Separated Values (CSV) and GeoPackage (GPKG).
In 5km tiles in one of two formats: CSV and GPKG. CSVs are supplied as individual tiles where multiples are selected, whereas GPKG are only ever supplied as one file.
We recommend that you copy your data supply to a backup medium, particularly if you take a COU supply to keep an archive of records. Please read Applying COU to tables > With archiving for more Information on how to do this.
For reading purposes, we recommend you store the data on a single hard disc. This speeds up your computer's ability to read the data.
Unzipped file sizes for a full supply of the product are as follows:
CSV 8GB
GPKG 12GB
Unzipped file sizes of the COU will vary upon each release as this will be dependent on the number of changes or records within a given tile.
PSGA customers can download full supply and COU of AddressBase Core via our download service.
In the OS Data Hub click Download data, you will be required to enter a password to access the PSGA members’ area. On successful entry to the download service, you will be able to view all your orders in the members’ area and download your data.
If you have ordered your data from our online portal, you will be sent an email with a link to a download page.
Within the PSGA members’ area, you can order and download the data that you require by clicking on Order Data, which is found under the Map Data heading.
Once you have selected Order Data, you will be presented with the Order page. From here, you can manage all your orders, including those for AddressBase products.
When you have placed an order for a product, the data will become available as a zipped data file.
The CSV and GPKG data are supplied in a compressed form (zip). Some software can access these files directly, while others will require it to be unzipped.
To unzip the zipped data files (.zip extension), use an unzipping utility found on most PCs, for example, WinZip. Alternatively, open-source zipping/unzipping software can be downloaded from the Internet, for example, 7-Zip.
The first level zip folder will contain the following:
Order Details.txt – a summary of the order including order type, format and information on files supplied.
Zipped folder with the product inside – this will be named as follows: AddressBaseCore_{variant}_{order_date_YYYY-MM-DD}_{file_number_NNN}.{format}.zip
variant: FULL or COU
order_date: Date the order was received, for example, 2020-02-11
file_number: Three-digit zero padded file number, for example, 001
format: csv, gpkg
Example:
AddressBaseCore_FULL_2020-01-30_001.gpkg.zip or
AddressBaseCore_COU_2020-01-30_001.csv.zip
The product within the ZIP folder will use the same naming convention as above but without the .zip at the end.
The header files for AddressBase are available for download from the AddressBase product page of the OS website.
AddressBase Core
34 526 145
88 612
AddressBase Core
34 526 145
34 526 138
7
Change type
Count
Inserts
10 471
Updates
75 416
Deletes
11 074
COU populated 5km tile count
2 725
This technical specification provides detailed technical information about AddressBase Core. It is targeted at technical users and software developers.
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:
All AddressBase products include the Unique Property Reference Number (UPRN) and are based on same coordinate reference systems.
Please see the General AddressBase information section for additional information that applies across all AddressBase products.
It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in 'Working with COU data' in the AddressBase Getting Started Guide.
It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in 'Working with COU data' in the AddressBase Getting Started Guide.
It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in 'Working with COU data' in the AddressBase Getting Started Guide.
It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in 'Working with COU data' in the AddressBase Getting Started Guide.
It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in 'Working with COU data' in the AddressBase Getting Started Guide.
It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in 'Working with COU data' in the AddressBase Getting Started Guide.
It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in 'Working with COU data' in the AddressBase Getting Started Guide.
It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in 'Working with COU data' in the AddressBase Getting Started Guide.
It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in 'Working with COU data' in the AddressBase Getting Started Guide.
It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in 'Working with COU data' in the AddressBase Getting Started Guide.
It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in 'Working with COU data' in the AddressBase Getting Started Guide.
It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in 'Working with COU data' in the AddressBase Getting Started Guide.
It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in 'Working with COU data' in the AddressBase Getting Started Guide.
It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in 'Working with COU data' in the AddressBase Getting Started Guide.
It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in 'Working with COU data' in the AddressBase Getting Started Guide.
It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in 'Working with COU data' in the AddressBase Getting Started Guide.
It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in 'Working with COU data' in the AddressBase Getting Started Guide.
It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in 'Working with COU data' in the AddressBase Getting Started Guide.
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 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)
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.
116
06 February 2025
03 January 2025
117
20 March 2025
14 February 2025
118
01 May 2025
28 March 2025
119
13 June 2025
09 May 2025
120
31 July 2025
27 June 2025
115
19 December 2024
14 November 2024
114
07 November 2024
03 October 2024
113
26 September 2024
23 August 2024
112
15 August 2024
11 July 2024
111
27 June 2024
23 May 2024
110
16 May 2024
11 April 2024
109
05 April 2024
29 February 2024
108
22 February 2024
18 January 2024
107
05 January 2024
30 November 2023
106
23 November 2023
19 October 2023
105
12 October 2023
07 September 2023
The following sub-sections provide details about the attributes included in AddressBase Core, their data types in the different output formats, and other important metadata about them.
A non-persistent integer which is autogenerated and is required within the OGC GPKG format.
Attribute Name: Not provided (CSV), fid (GKPG)
Data Type: Integer
Multiplicity: [1]
Unique Property Reference Number (UPRN) assigned by the LLPG Custodian or Ordnance Survey.
Attribute Name: UPRN (CSV), uprn (GKPG)
Data Type: Integer
Size: 12
Multiplicity: [1]
UPRN of the parent Record if a parent-child relationship exists.
Attribute Name: PARENT_UPRN (CSV), parent_uprn (GKPG)
Data Type: Integer
Size: 12
Multiplicity: [0..1]
Royal Mail’s Unique Delivery Point Reference Number (UDPRN).
Attribute Name: UDPRN (CSV), udprn (GKPG)
Data Type: Integer
Size: 8
Multiplicity: [0..1]
Unique Street Reference Number assigned by the Street Name and Numbering Custodian OR Ordnance Survey depending on the address record.
Attribute Name: USRN (CSV), usrn (GKPG)
Data Type: Integer
Size: 8
Multiplicity: [1]
The Topographic Identifier taken from OS MasterMap Topography Layer. This TOID is assigned to the UPRN by performing a spatial intersection between the two identifiers. It consists of the letters ‘osgb’ and is followed by up to sixteen digits.
Attribute Name: TOID (CSV), toid (GKPG)
Data Type: varchar
Size: 20
Multiplicity: [0..1]
A code that describes the classification of the address record to a maximum of a secondary level.
Attribute Name: CLASSIFICATION_CODE (CSV), classification_code (GKPG)
Data Type: varchar
Size: 4
Multiplicity: [1]
You can download a complete list of classification codes at Classification codes.
A value in metres defining the x location in accordance with the British National Grid.
Attribute Name: EASTING (CSV), easting (GKPG)
Data Type: Float
Size: (precision, scale) – (8, 2)
Multiplicity: [1]
A value in metres defining the y location in accordance with the British National Grid.
Attribute Name: NORTHING (CSV), northing (GKPG)
Data Type: Float
Size: (precision, scale) – (9, 2)
Multiplicity: [1]
A value defining the Latitude location in accordance with the ETRS89 coordinate reference system.
Attribute Name: LATITUDE (CSV), latitude (GKPG)
Data Type: Float
Size: (precision, scale) – (9, 7)
Multiplicity: [1]
A value defining the Longitude location in accordance with the ETRS89 coordinate reference system.
Attribute Name: LONGITUDE (CSV), longitude (GKPG)
Data Type: Float
Size: (precision, scale) – (8, 7)
Multiplicity: [1]
Representative Point Code: this describes the accuracy of the coordinate that has been allocated to the UPRN as indicated by the Local Authority and enhanced using large scale OS data.
Attribute Name: RPC (CSV), rpc (GKPG)
Code List Name: RPCCode
Data Type: Integer
Size: 1
Multiplicity: [1]
The latest date on which any of the attributes on this record were last changed in CCYY-MM-DD format.
Attribute Name: LAST_UPDATE_DATE (CSV), last_update_date (GKPG)
Data Type: Date
Multiplicity: [1]
A single attribute containing text concatenation of the address elements separated by a comma.
Attribute Name: SINGLE_LINE_ADDRESS (CSV), single_line_address (GKPG)
Data Type: varchar
Size: 500
Multiplicity: [1]
Text concatenation of ‘PO BOX’ and the Post Office Box (PO Box) number or ‘BFPO’ and the British Forces Post Office number.
Attribute Name: PO_BOX (CSV), po_box (GKPG)
Data Type: varchar
Size: 13
Multiplicity: [0..1]
The organisation name is the business name given, when appropriate, to an address record.
Attribute Name: ORGANISATION (CSV), organisation (GKPG)
Data Type: varchar
Size: 100
Multiplicity: [0..1]
The sub-building name and/or number for the address record.
Attribute Name: SUB_BUILDING (CSV), sub_building (GKPG)
Data Type: varchar
Size: 110
Multiplicity: [0..1]
The building name is a description applied to a single address or a group of addresses.
Attribute Name: BUILDING_NAME (CSV), building_name (GKPG)
Data Type: varchar
Size: 110
Multiplicity: [0..1]
The building number is a number or range of numbers given to a single address or a group of addresses.
Attribute Name: BUILDING_NUMBER (CSV), building_number (GKPG)
Data Type: varchar
Size: 13
Multiplicity: [0..1]
Street/Road name for the address record.
Attribute Name: STREET_NAME (CSV), street_name (GKPG)
Data Type: varchar
Size: 100
Multiplicity: [0..1]
A locality defines an area or geographical identifier within a town, village or hamlet. Locality represents the lower level geographical area. The locality field should be used in conjunction with the town name and street description fields to uniquely identify geographic area where there may be more than one within an administrative area.
Attribute Name: LOCALITY (CSV), locality (GKPG)
Data Type: varchar
Size: 35
Multiplicity: [0..1]
Geographical town name assigned by the Local Authority. Please note this can be different from the Post Town value assigned by Royal Mail.
Attribute Name: TOWN_NAME (CSV), town_name (GKPG)
Data Type: varchar
Size: 35
Multiplicity: [0..1]
The town or city in which the Royal Mail sorting office is located which services this address record.
Attribute Name: POST_TOWN (CSV), post_town (GKPG)
Condition: POST_TOWN is not populated if this is the same as TOWN_NAME
Data Type: varchar
Size: 30
Multiplicity: [0..1]
Third level of geographic area name to record island names where appropriate.
Attribute Name: ISLAND (CSV), island (GKPG)
Data Type: varchar
Size: 50
Multiplicity: [0..1]
Third level of geographic area name to record island names where appropriate.
Attribute Name: POSTCODE (CSV), postcode (GKPG)
Data Type: varchar
Size: 8
Multiplicity: [1]
A two-character code uniquely identifying an individual delivery point within a postcode, assigned by Royal Mail.
Attribute Name: DELIVERY_POINT_SUFFIX (CSV), delivery_point-suffix (GKPG)
Data Type: varchar
Size: 2
Multiplicity: [0..1]
The Office for National Statistics Governmental Statistical Service (GSS) code representing the contributing Local Authority.
Attribute Name: GSS_CODE (CSV), gss_code (GKPG)
Data Type: varchar
Size: 9
Multiplicity: [0..1]
You can download a complete list of GSS codes at Government Statistical Services codes.
Type of record change.
Attribute Name: CHANGE_CODE (CSV), change_code (GKPG)
Code List Name: ChangeTypeCode
Data Type: varchar
Size: 1
Multiplicity: [1]
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:
AddressBase Core
34 546 767
35 014
AddressBase Core
34 546 767
34 546 760
7
Inserts
8 314
Updates
24 688
Deletes
2 012
COU populated 5km tile count
3 081
It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the 'Working with COU data' page in the AddressBase Core Getting Started Guide.
AddressBase Core
34 540 465
32 496
AddressBase Core
34 540 465
34 540 458
7
Inserts
6 774
Updates
23 293
Deletes
2 429
COU populated 5km tile count
2 918
It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the 'Working with COU data' page in the AddressBase Core Getting Started Guide.
AddressBase Core
34 536 120
36 907
AddressBase Core
34 536 120
34 536 113
7
Inserts
8 998
Updates
24 847
Deletes
3 062
COU populated 5km tile count
3 464
It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the 'Working with COU data' page in the AddressBase Core Getting Started Guide.
It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the 'Working with COU data' page in the AddressBase Core Getting Started Guide.
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:
If referencing a schema, <schema_name>, can be placed in front of any <table_name>, for example:
At a high level, there are three types of change found within COU:
Deletes (CHANGE_TYPE ‘D’) are objects that have ceased to exist in the product since the last product refresh.
Inserts (CHANGE_TYPE ‘I’) are objects that have been newly inserted into the product since the last product refresh.
Updates (CHANGE_TYPE ‘U’) are objects that have been updated in the product since the last product refresh.
Before a COU is applied, there may be a business requirement to archive existing address records. The diagram below shows how to implement archiving with an AddressBase Core COU within a database.
Within AddressBase Core there will be no records with the same UPRN. You can test this by checking the number of records that have the same UPRN. The following SQL query notifies you of any duplicates.
This query should return 0 rows, and this confirms that there are no duplicates. As there are no duplicate records, we can use the UPRN to apply the COU.
Where there is a business requirement to keep the records that are being Updated and Deleted in a separate archive table, the following SQL will create an Archive Table. It will populate with records that are being Updated and Deleted from the live AddressBase Core table.
The following commands create an archive table of the records that are being updated and deleted from the existing table, for example, addressbase_core_archive.
Use the steps in Working with CSV data > Loading AddressBase Core into a database to load the COU CSV into a new or existing table, for example, addressbase_core_cou.
If this table already exists, you can use INSERT INTO <abcore_archive_table_name>, rather than CREATE TABLE <abcore_archive_table_name> AS.
The following commands deletes the records from the existing table, which are either updates or deletions.
The following command inserts the new insert records and the new updated records into the live BLPU table.
You can check that this has been successful by re-checking that there are no duplicate UPRNs.
If there is no requirement for archiving, follow these steps:
Use the steps in Working with CSV data > Loading AddressBase Core into a database to load the COU CSV into a new or existing table, for example, addressbase_core_cou.
Now, delete the existing records that will be updated, for example, Updates and Deletions.
Insert the new updated records.
You can check that this has been successful by re-checking that there are no duplicate UPRNs.
28
ISLE OF MAN
Islands
Y
N
114
BATH AND NORTH EAST SOMERSET COUNCIL
English Unitary
Y
Y
116
BRISTOL CITY COUNCIL
English Unitary
Y
Y
119
SOUTH GLOUCESTERSHIRE COUNCIL
English Unitary
Y
Y
121
NORTH SOMERSET COUNCIL
English Unitary
Y
Y
230
LUTON BOROUGH COUNCIL
English Unitary
Y
Y
235
BEDFORD BOROUGH COUNCIL
English Unitary
Y
Y
240
CENTRAL BEDFORDSHIRE COUNCIL
English Unitary
Y
Y
335
BRACKNELL FOREST COUNCIL
English Unitary
Y
Y
340
WEST BERKSHIRE COUNCIL
English Unitary
Y
Y
345
READING BOROUGH COUNCIL
English Unitary
Y
Y
350
SLOUGH BOROUGH COUNCIL
English Unitary
Y
Y
355
ROYAL BOROUGH OF WINDSOR AND MAIDENHEAD
English Unitary
Y
Y
360
WOKINGHAM BOROUGH COUNCIL
English Unitary
Y
Y
435
MILTON KEYNES CITY COUNCIL
English Unitary
Y
Y
440
BUCKINGHAMSHIRE COUNCIL
English Unitary
Y
Y
505
CAMBRIDGE CITY COUNCIL
English Shire District
Y
N
510
EAST CAMBRIDGESHIRE DISTRICT COUNCIL
English Shire District
Y
N
515
FENLAND DISTRICT COUNCIL
English Shire District
Y
N
520
HUNTINGDONSHIRE DISTRICT COUNCIL
English Shire District
Y
N
530
SOUTH CAMBRIDGESHIRE DISTRICT COUNCIL
English Shire District
Y
N
535
CAMBRIDGESHIRE COUNTY COUNCIL
English County
N
Y
540
PETERBOROUGH CITY COUNCIL
English Unitary
Y
Y
650
HALTON BOROUGH COUNCIL
English Unitary
Y
Y
655
WARRINGTON BOROUGH COUNCIL
English Unitary
Y
Y
660
CHESHIRE EAST COUNCIL
English Unitary
Y
Y
665
CHESHIRE WEST AND CHESTER COUNCIL
English Unitary
Y
Y
724
HARTLEPOOL BOROUGH COUNCIL
English Unitary
Y
Y
728
REDCAR AND CLEVELAND BOROUGH COUNCIL
English Unitary
Y
Y
734
MIDDLESBROUGH BOROUGH COUNCIL
English Unitary
Y
Y
738
STOCKTON-ON-TEES BOROUGH COUNCIL
English Unitary
Y
Y
835
COUNCIL OF THE ISLES OF SCILLY
English Unitary
Y
Y
840
CORNWALL COUNCIL
English Unitary
Y
Y
935
WESTMORLAND AND FURNESS COUNCIL
English Unitary
Y
Y
940
CUMBERLAND COUNCIL
English Unitary
Y
Y
1005
AMBER VALLEY BOROUGH COUNCIL
English Shire District
Y
N
1010
BOLSOVER DISTRICT COUNCIL
English Shire District
Y
N
1015
CHESTERFIELD BOROUGH COUNCIL
English Shire District
Y
N
1025
EREWASH BOROUGH COUNCIL
English Shire District
Y
N
1030
HIGH PEAK BOROUGH COUNCIL
English Shire District
Y
N
1035
NORTH EAST DERBYSHIRE DISTRICT COUNCIL
English Shire District
Y
N
1040
SOUTH DERBYSHIRE DISTRICT COUNCIL
English Shire District
Y
N
1045
DERBYSHIRE DALES DISTRICT COUNCIL
English Shire District
Y
N
1050
DERBYSHIRE COUNTY COUNCIL
English County
N
Y
1055
DERBY CITY COUNCIL
English Unitary
Y
Y
1105
EAST DEVON DISTRICT COUNCIL
English Shire District
Y
N
1110
EXETER CITY COUNCIL
English Shire District
Y
N
1115
NORTH DEVON DISTRICT COUNCIL
English Shire District
Y
N
1125
SOUTH HAMS DISTRICT COUNCIL
English Shire District
Y
N
1130
TEIGNBRIDGE DISTRICT COUNCIL
English Shire District
Y
N
1135
MID DEVON DISTRICT COUNCIL
English Shire District
Y
N
1145
TORRIDGE DISTRICT COUNCIL
English Shire District
Y
N
1150
WEST DEVON BOROUGH COUNCIL
English Shire District
Y
N
1155
DEVON COUNTY COUNCIL
English County
N
Y
1160
PLYMOUTH CITY COUNCIL
English Unitary
Y
Y
1165
TORBAY COUNCIL
English Unitary
Y
Y
1260
BOURNEMOUTH, CHRISTCHURCH AND POOLE COUNCIL
English Unitary
Y
Y
1265
DORSET COUNCIL
English Unitary
Y
Y
1350
DARLINGTON BOROUGH COUNCIL
English Unitary
Y
Y
1355
DURHAM COUNTY COUNCIL
English Unitary
Y
Y
1410
EASTBOURNE BOROUGH COUNCIL
English Shire District
Y
N
1415
HASTINGS BOROUGH COUNCIL
English Shire District
Y
N
1425
LEWES DISTRICT COUNCIL
English Shire District
Y
N
1430
ROTHER DISTRICT COUNCIL
English Shire District
Y
N
1435
WEALDEN DISTRICT COUNCIL
English Shire District
Y
N
1440
EAST SUSSEX COUNTY COUNCIL
English County
N
Y
1445
BRIGHTON & HOVE CITY COUNCIL
English Unitary
Y
Y
1505
BASILDON BOROUGH COUNCIL
English Shire District
Y
N
1510
BRAINTREE DISTRICT COUNCIL
English Shire District
Y
N
1515
BRENTWOOD BOROUGH COUNCIL
English Shire District
Y
N
1520
CASTLE POINT BOROUGH COUNCIL
English Shire District
Y
N
1525
CHELMSFORD CITY COUNCIL
English Shire District
Y
N
1530
COLCHESTER CITY COUNCIL
English Shire District
Y
N
CLOVER AVENUE, SW99 9ZZ
1, Clover Avenue, Fieldtown, Addressville, SW99 9ZZ
2, Clover Avenue, Fieldtown, Addressville, SW99 9ZZ
3, Clover Avenue, Fieldtown, Addressville, SW99 9ZZ
4, Clover Avenue, Fieldtown, Addressville, SW99 9ZZ
5, Clover Avenue, Fieldtown, Addressville, SW99 9ZZ
6, Clover Avenue, Fieldtown, Addressville, SW99 9ZZ
7, Clover Avenue, Fieldtown, Addressville, SW99 9ZZ
This release note provides information about the release of the AddressBase Core product on 05 November 2024.
AddressBase Core
34 518 399
54 822
*These counts are based on a Managed Great Britain Set (MGBS). If you ordered your national coverage via the online ordering system using a polygon outline, your counts may differ.
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.
AddressBase Core
34 518 399
34 518 392
7
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.
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:
Inserts
6 952
Updates
36 796
Deletes
11 074
COU populated 5km tile count
4 362
It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the .
There has been one new issue identified in this release of AddressBase Core. A Scottish record has been incorrectly matched to a Royal Mail record. As a result of this, the Scottish record (UPRN = 35030393) has been incorrectly assigned a ‘POST_TOWN’ value of ‘NEWCASTLE’ and incorrect ‘POSTCODE’ of ‘BT33 0GT’. The nine other addresses on this street remain unaffected.
The following information relates to the currency of the source data used in the creation of this release of AddressBase Core:
Royal Mail Postcode Address File (PAF)
01 November 2024
National Land and Property Gazetteer
01 November 2024
One Scotland Gazetteer
28 October 2024
OS MasterMap Topography Layer
05 September 2024
This release note provides information about the release of the AddressBase Core product on 29 October 2024.
AddressBase Core
34 522 521
31 545
*These counts are based on a Managed Great Britain Set (MGBS). If you ordered your national coverage via the online ordering system using a polygon outline, your counts may differ.
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.
AddressBase Core
34 522 521
34 522 514
7
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.
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:
Inserts
7 035
Updates
22 671
Deletes
1 839
COU populated 5km tile count
2 586
It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the .
The following information relates to the currency of the source data used in the creation of this release of AddressBase Core:
Royal Mail Postcode Address File (PAF)
25 October 2024
National Land and Property Gazetteer
25 October 2024
One Scotland Gazetteer
07 October 2024
OS MasterMap Topography Layer
05 September 2024
This release note provides information about the release of the AddressBase Core product on 22 October 2024.
AddressBase Core
34 517 325
32 059
*These counts are based on a Managed Great Britain Set (MGBS). If you ordered your national coverage via the online ordering system using a polygon outline, your counts may differ.
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.
AddressBase Core
34 517 325
34 517 318
7
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.
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:
Inserts
6 966
Updates
22 919
Deletes
2 174
COU populated 5km tile count
2 735
It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the .
The following information relates to the currency of the source data used in the creation of this release of AddressBase Core:
Royal Mail Postcode Address File (PAF)
18 October 2024
National Land and Property Gazetteer
18 October 2024
One Scotland Gazetteer
07 October 2024
OS MasterMap Topography Layer
05 September 2024
This release note provides information about the release of the AddressBase Core product on 23 December 2024.
Please note: There will be no release of AddressBase Core on 31 January 2024 due to a company-wide shutdown over the festive period. The next release of AddressBase Core will be on 07 January 2025.
AddressBase Core
34 559 204
98 188
Please note that the Full Supply record count is based on a Managed Great Britain Set (MGBS). If you ordered your national coverage via the online ordering system using a polygon outline, your counts may differ.
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.
AddressBase Core
34 559 204
34 559 197
7
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.
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:
Inserts
8 535
Updates
87 373
Deletes
2 280
COU populated 5km tile count
3 960
It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the .
One new issue has been identified in this release of AddressBase Core, causing an English record to be incorrectly matched to a Northern Irish POST_TOWN and POSTCODE. The UPRN = 10094417972 has been incorrectly assigned a ‘POST_TOWN’ of ‘BELFAST’ and an incorrect ‘POSTCODE’ of ‘BT12 4EA’. This address is affected in isolation, and the match will be fixed for the next AddressBase Core release.
The following information relates to the currency of the source data used in the creation of this release of AddressBase Core:
Royal Mail Postcode Address File (PAF)
20 December 2024
National Land and Property Gazetteer
20 December 2024
One Scotland Gazetteer
09 December 2024
OS MasterMap Topography Layer
28 November 2024
This release note provides information about the release of the AddressBase Core product on 19 November 2024.
AddressBase Core
34 530 184
28 008
*These counts are based on a Managed Great Britain Set (MGBS). If you ordered your national coverage via the online ordering system using a polygon outline, your counts may differ.
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.
AddressBase Core
34 530 184
34 530 177
7
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.
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:
Inserts
6 365
Updates
19 317
Deletes
2 326
COU populated 5km tile count
2 760
It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the .
The following information relates to the currency of the source data used in the creation of this release of AddressBase Core:
Royal Mail Postcode Address File (PAF)
15 November 2024
National Land and Property Gazetteer
15 November 2024
One Scotland Gazetteer
28 October 2024
OS MasterMap Topography Layer
05 September 2024
This is not an extensive list of the applications AddressBase Core can be used in; many other GIS software applications and/or databases can be used to load the product.
Ordnance Survey does not recommend specific suppliers or software products, as the most appropriate system will depend on many factors, for example, 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
This section provides step-by-step instructions on how to load the GPKG format of AddressBase Core into commonly-used GIS software.
Tiled orders allow you to select a small region of Great Britain (GB), rather than having to order the whole of GB. Ordering tiles, as opposed to full GB coverage, reduces the amount of data supplied. This reduces data storage size and the time it takes to process the data.
AddressBase Core tiles can be downloaded through Ordnance Survey’s download service. See Downloading a dataset for full details about accessing this service. To order tiles:
Access the OS orders site and select AddressBase Core – 5km DOWNLOAD.
Select either a self-drawn polygon, a rectangle or a postcode/place. These options are available in the toolbar above the map. Once you have selected your area of interest (AOI), you can proceed to place your order.
Dependent on whether you are a PSGA customer or an OS Partner, the tiles are supplied as either GKPG or CSV.
You are provided with all 5km tiles that intersect the drawn polygon. The diagram below shows what is supplied when completing a tile order. An area of interest is drawn (blue lines) and a tile is provided for anywhere the drawn area of interest intersects (green lines).
For a GPKG download, you receive tiled data incorporated into one single GKPG file. For CSV tile supplies, individual 5km tiles are supplied for each tile which intersects your AOI.
The diagram below illustrates the format, coverage and supply type of AddressBase Core, specifically highlighting the tile supply options.
Each supply type is covered in the sections that follow.
Both GB coverage and tiled supply of GKPG is produced as a full supply only. Both product variants result in you receiving one consolidated GPKG file for your order.
To use this in your GIS software, please refer to Getting started with AddressBase Core > GPKG data, which provides instructions to load GPKG into ArcGIS Pro, ArcMap, QGIS, MapInfo Professional and CadCorp Map Modeller.
Tiled orders are also an option for CSV supplies of AddressBase Core. The CSV is divided into 5km tiles with an individual CSV produced for each tile. This is the case for both full supply and COU. Each CSV is also be provided with a header, which needs to be considered if you want to consolidate multiple individual tiles into one single file.
One use case for taking tiled coverage is if you only need a small subset of addresses within GB, as this provides you with a smaller data holding than taking all of GB .
If you are planning on using the tile supplies for COU purposes, you need to understand the data structure of the full supply and COU files you will download.
If you select to receive COU tile supplies, if any record within a selected 5km tile is changed between two releases of data (each week), you will receive the entire 5km tile in your next supply containing all of the latest live records for that tile.
For example, as demonstrated in the table below, the original full supply contains the address 17 THE BROADS, PAMPHILL, WIMBORNE, BH21 4DR, and the next COU data does not . However, the full supply does include an additional record, 37 THE BADGERS, PAMPHILL, BH21 4SH. This means that the 17 THE BROADS address has been deleted between the two releases, and 37 THE BADGERS is a new address.
BUNGALOW, BLANDFORD ROAD, WIMBORNE MINSTER, BH21 4DS
BUNGALOW, BLANDFORD ROAD, WIMBORNE MINSTER, BH21 4DS
I (INSERT)
17 THE BROADS, PAMPHILL, WIMBORNE, BH21 4DR
No data supplied
Not applicable
33 THE BROADS, PAMPHILL, WIMBORNE, BH21 4DR
33 THE BROADS, PAMPHILL, WIMBORNE, BH21 4DR
I (INSERT)
No data supplied
37 THE BADGERS, PAMPHILL, BH21 4SH
I (INSERT)
To implement COU, we recommend that you process the full supply and the COU data files into a common structure to be used in conjunction with SQL. You can do this by appending a tilename column onto the full supply and COU data when the CSVs are merged, as shown in the table below.
AddressBaseCore_COU_2020-01-30_SU2075.csv.zip
SN4 0HJ
1A
E06000030
I
SU2075
MARLBOROUGH
SN8 1SZ
1A
E06000054
I
SU2075
MARLBOROUGH
SN8 1SZ
1B
E06000054
I
SU2075
Ordnance Survey provides FME Workbench and NodeJS scripts to help to pre-process the data as described in the sections that follow. You can access these scripts in our GitHub repository:
A README file with usage instructions is provided for both scripts.
You do not need you to unzip the data before processing.
The data, either full supply or COU, should now be combined in one CSV file, under one header, with an appended tilename column. Once the data has been pre-processed, it can be loaded into any database. The next sub-sections will detail the different loads of full supply and COU.
Once the full supply CSV has been pre-processed, the COPY load method can be used to load the data into your primary database table:
In this example, addressbase_core is the name of the table. You may use a different name. To use this table in a geospatial setting, geometry columns will need to be inserted using the following SQL:
A similar method can be used to insert the COU data into a database. Similarly, addressbase_core_cou is the name given to the database table. You may use a different name.
If you are applying COU to your primary table, you should now have two tables in your selected database:
A primary table which contains some out-of-date data.
A COU table with the live data.
To update your primary table, there are two basic steps to follow using SQL commands:
Delete all rows that contain tilenames that match the tilenames of the incoming COU.
Insert all rows from the COU table to the primary table.
The following SQL commands will complete the application of COU into the primary table:
Index the tilename column on to the primary table:
Index the tilename column on to the COU table: CREATE INDEX ON addressbase_core_cou (tilename);
Delete from the primary table any records which have a tilename that matches a tilename from your COU table:
Insert the live COU data into the primary table:
This is not an extensive list of the applications AddressBase Core can be used in; many other GIS software applications and/or databases can be used to load the product.
Ordnance Survey does not recommend specific suppliers or software products, as the most appropriate system will depend on many factors, for example, 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.
This section provides step-by-step instructions on how to load the CSV format of AddressBase Core into commonly-used GIS software.
BIGINT/NUMBER: The ESRI products, ArcMap, ArcGIS Desktop and ArcGIS Server, do not support the BIGINT/NUMBER data type as an Object ID. Bear this in mind if the expectation is to use this data type directly with these products. As an alternative method to facilitate using ESRI software, you can store this data as a string and add a new Serial ID to act as the Object ID.
Column length: If you are loading AddressBase Core data directly into a database, you may need to increase the column length to accommodate language characters such as ^. Some databases treat this as an additional character and therefore if you define the column length according to our specification there is a chance the load may fail. Please bear in mind such adjustments may be required depending on the database you use to load the data.
UPRN deletions: It is important to note if a UPRN is deleted and then reinserted, this does not compromise the integrity of the UPRN and its use as a primary key. If a delete is issued for a UPRN, this does not mean it will not reappear in subsequent supplies. There are several reasons this may happen:
The record has moved in location more than once, moving it out of your area of interest (AOI; therefore the record is deleted) but then back into your AOI in the future. This could also occur if you alter your AOI.
A record has failed data validation upon a change being made. This can result dependent on the change being made in the record being deleted and then reintroduced when the error is fixed by the data supplier.
If a UPRN is deleted, it will not be reallocated to a different property and it therefore remains the unique identifier for a property.
The following sections describes how to load AddressBase Core into two popular databases.
This product is available to try out online using one of our three sets of sample data (Exeter, Newport and Inverness) through the OS MasterMap Product Viewer:
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.
These pages should be used in conjunction with the detailed technical specifications for each product (which can be found under the top-level product guide page for each individual product from the left-hand-side menu).
This release note provides information about the August 2024 release of the AddressBase products. These products were released to customers on 15 August 2024.
OS Open UPRN
40 873 566
N/A
AddressBase
30 528 787
164 532
AddressBase Plus
38 125 445
864 998
AddressBase Premium
See rows below
See rows below
Street
1 508 646
7531
Street Descriptor
1 631 995
5970
BLPU
40 873 566
462 545
Classification
44 728 771
175 302
LPI
46 041 542
231 655
Organisation
1 421 542
25 452
Delivery Point Address
30 635 054
74 237
Application Cross Ref.
198 155 853
843 499
Successor
0
0
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.
Change-Only Updates are not available for the OS Open UPRN product.
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.
AddressBase
30 528 787
30 528 787
0
AddressBase Plus
38 125 445
38 125 425
20
AddressBase Premium
See rows below
See rows below
See rows below
Street
1 508 646
1 508 643
3
Street Descriptor
1 631 995
1 631 992
3
BLPU
40 873 566
40 873 542
24
Classification
44 728 771
44 728 747
24
LPI
46 041 542
46 041 517
25
Organisation
1 421 542
1 421 540
2
Delivery Point Address
30 635 054
30 635 054
0
Application Cross Ref.
198 155 853
198 155 829
24
Successor
0
0
0
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.
Inserts
46 546
Updates
107 529
Deletes
10 457
COU Populated Tile Count
5 390
Inserts
58 383
Updates
791 040
Deletes
15 575
COU Populated Tile Count
7 931
Street
1 527
5 822
182
Street Descriptor
1 751
4 032
187
BLPU
51 831
406 735
3 979
Classification
64 820
89 524
20 958
LPI
67 711
159 116
4 828
Organisation
9 398
6 111
9 943
Delivery Point Address
46 773
17 519
9 945
Application Cross Ref.
237 145
560 552
45 802
The following information relates to the currency of the source data used in the creation of Epoch 112:
Royal Mail PAF
11 July 2024
National Land and Property Gazetteer
11 July 2024
One Scotland Gazetteer
17 June 2024
VOA Non-Domestic Rates
08 July 2024
VOA Council Tax
08 July 2024
OS MasterMap Topography Layer
25 June 2024
OS MasterMap Highways Network
04 July 2024
Code-Point with Polygons
01 July 2024
Boundary-Line
24 June 2024
Affected output formats: CSV and GML
There are 5 675 Unique Property Reference Numbers (UPRNs) which reference a Parent UPRN which 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 220 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 product.
The match rates for Council Tax and Non-Domestic Rates for Epoch 112 are detailed as follows based on Valuation Office Agency (VOA) records up to 8th July 2024. The match rate is applicable to the AddressBase Premium product.
Data Source
Records Received
% Matched
Council Tax
27 116 559
99.92
Non-Domestic Rates
2 123 229
96.47
Work is being undertaken to improve the classifications of records within the AddressBase products. This work has resulted in 48 610 more tertiary classifications present in Epoch 112 compared to Epoch 111. Indeed, 88.72% of these tertiary classification improvements are against residential codes.
The following graph shows the number of Postcode Address File (PAF) matched records in AddressBase by epoch:
The next release of AddressBase products, Epoch 113, is scheduled for 26 September 2024.
This release note provides information about the May 2024 release of the AddressBase products. These products were released to customers on 16 May 2024.
OS Open UPRN
40 784 183
N/A
AddressBase
30 469 019
134 626
AddressBase Plus
38 049 740
578 629
AddressBase Premium
See rows below
See rows below
Street
1 505 809
7 967
Street Descriptor
1 628 740
2 522
BLPU
40 784 183
324 106
Classification
44 648 493
127 133
LPI
45 923 590
137 049
Organisation
1 419 009
16 669
Delivery Point Address
30 574 064
69 329
Application Cross Ref.
197 792 553
716 937
Successor
0
0
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.
Change-Only Updates are not available for the OS Open UPRN product.
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.
AddressBase
30 469 019
30 469 019
0
AddressBase Plus
38 049 740
38 049 721
19
AddressBase Premium
See rows below
See rows below
See rows below
Street
1 505 809
1 505 808
1
Street Descriptor
1 628 740
1 628 739
1
BLPU
40 784 183
40 784 160
23
Classification
44 648 493
44 648 470
23
LPI
45 923 590
45 923 566
24
Organisation
1 419 009
1 419 007
2
Delivery Point Address
30 574 064
30 574 064
0
Application Cross Ref.
197 792 553
197 792 530
23
Successor
0
0
0
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.
Inserts
40 382
Updates
82 823
Deletes
11 421
COU Populated Tile Count
5 315
Inserts
49 477
Updates
515 781
Deletes
13 371
COU Populated Tile Count
7 232
Street
1 489
6 452
26
Street Descriptor
1 615
881
26
BLPU
43 791
276 622
3 693
Classification
57 868
47 780
21 485
LPI
57 875
74 907
4 267
Organisation
7 721
4 356
4 592
Delivery Point Address
40 777
16 919
11 633
Application Cross Ref.
197 994
472 962
45 981
The following information relates to the currency of the source data used in the creation of Epoch 110:
Royal Mail PAF
11 April 2024
National Land and Property Gazetteer
11 April 2024
One Scotland Gazetteer
25 March 2024
VOA Non-Domestic Rates
08 April 2024
VOA Council Tax
08 April 2024
OS MasterMap Topography Layer
03 April 2024
OS MasterMap Highways Network
06 March 2024
Code-Point with Polygons
04 January 2024
Boundary-Line
03 October 2023
Affected output formats: CSV and GML
There are 5 420 Unique Property Reference Numbers (UPRNs) which reference a Parent UPRN which 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 240 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 product.
The match rates for Council Tax and Non-Domestic Rates for Epoch 110 are detailed as follows based on Valuation Office Agency (VOA) records up to 08 April 2024. The match rate is applicable to the AddressBase Premium product.
Council Tax
27 058 858
99.92
Non-Domestic Rates
2 123 768
96.44
Work is being undertaken to improve the classifications of records within the AddressBase products. This work has resulted in 38 568 more tertiary classifications present in Epoch 110 compared to Epoch 109. Indeed, 88.75% of these tertiary classification improvements are against residential codes.
The following graph shows the number of Postcode Address File (PAF) matched records in AddressBase by epoch:
The next release of AddressBase products, Epoch 111, is scheduled for 27 June 2024.
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 for more information.
It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in.
It's important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Further guidance on this can be found in.
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.
Please be aware that the UPRN is not the Primary Key for all tables within the AddressBase Premium and AddressBase Premium Islands supply. Please see the relational models in AddressBase Premium structure and AddressBase Premium Islands structure for more information.
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.
AddressBase_Core.gbd in the Catalog pane
This enumeration is used in association with the officialFlag/OFFICIAL_FLAG attribute. This enumeration is an indicator of whether an address record corresponds to an entry in the official Street Name and Numbering register.
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 state/STATE attribute found in the street table. This enumeration identifies at which point the street record is within its lifecycle.
N
Unofficial Address
Y
Official Address
1
Under construction
2
In use
3
Unoccupied / vacant / derelict
4
No longer existing
6
Planning permission granted
1
Under construction
2
Open
4
Permanently closed (STREET_END_DATE must be entered)
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.
The name of the attribute and what it is describing.
A condition associated with this attribute (optional).
The nature of the attribute, for example a numeric value or a code list value.
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.
This technical specification provides detailed technical information about AddressBase. It is targeted at technical users and software developers.
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:
All AddressBase products include the Unique Property Reference Number (UPRN) and are based on same coordinate reference systems.
Please see the General AddressBase information section for additional information that applies across all AddressBase products.
The primary supply mechanism of AddressBase data is referred to as non-geographic chunks. This is a way of dividing up the data into chunks that are supplied in separate volumes, which have a fixed maximum number of records. The supply is not supplied with any reference to the geographic position of records.
Public Sector Geospatial Agreement (PSGA) customers can order Geographic chunks (5km tiles) as well as non-geographic chunks, although geographic chunks are not considered the main form of supply.
All customers are also able to take a complete supply (referred to as a Managed Great Britain Set: MGBS) or an Area of Interest (AOI) as a full supply or a COU supply.
If you receive your data as non-geographic chunks, the filename will be constructed as follows:
productName_supply_ccyy-mm-dd_vvv.format
Where:
ProductName is AddressBase.
supply is defined as FULL or COU.
ccyy-mm-dd is the date the file was generated.
vvv is the volume number of the file.
format is the format of the files received, for example, csv or gml.
For example:
AddressBase_FULL_2013-05-28_001.gml (GML full supply)
AddressBase_COU_2013-05-28_001.csv (CSV COU supply)
If the data has been provided in a ZIP file, the filename will be constructed as follows:
productName_supply_ccyy-mm-dd_vvv_format.zip
For example:
AddressBase_FULL_2013-05-28_001_gml.zip (GML full supply zipped)
If you receive your data as geographic chunks (PSGA customers only), the filename will be constructed as follows:
productName_supply_ccyy-mm-dd_ngxxyy.format
Where:
ProductName is AddressBase.
supply is defined as FULL or COU.
ccyy-mm-dd is the date the file was generated.
ngxxyy is the four-digit grid reference belonging to the 1km south-west corner of the 5km chunk.
format is the format of the files received, for example, csv or gml.
For example:
AddressBase_FULL_2013-05-28_NC4040.gml (GML full supply)
AddressBase_COU_2013-05-28_NC4040.csv (CSV COU supply)
If the data has been provided in a ZIP file, the filename will be constructed as follows:
productName_supply_ccyy-mm-dd_ngxxyy_format.zip
For example:
AddressBase_COU_2013-05-28_NC4040_csv.zip (CSV COU supply zipped)
AddressBase is available as a full or COU supply.
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 data volumes are smaller therefore reducing the amount of data that requires processing when compared to a full supply.
COU data enables a user to identify three types of change:
Deletes (CHANGE_TYPE ‘D’) are objects that have ceased to exist in your AOI since the last product refresh.
Inserts (CHANGE_TYPE ‘I’) are objects that have been newly inserted into your AOI since the last product refresh.
Updates (CHANGE_TYPE ‘U’) are objects that have been updated in your AOI since the last product refresh.
A COU file for non-geographic chunked data can be identified by its naming convention. Any change record will be provided as a full record with the appropriate change type, as listed above.
A geographic chunked COU is not supplied as per the non-geographic chunked COU outlined above. Its file naming convention can be found above. If a single 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.
The following section provides example records for both the CSV and GML supplies. Please note that the data given is to provide an example only and should not to be used as accurate data.
Please note how not all attributes are provided where the field is null.
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.
CountryCode
RPCCode
PostcodeTypeCode
ChangeTypeCode
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.
UPRN
uprn
OS_ADDRESS_TOID
osAddressTOID
UDPRN
udprn
ORGANISATION_NAME
organisationName
DEPARTMENT_NAME
departmentName
PO_BOX_NUMBER
poBoxNumber
SUB_BUILDING_NAME
subBuildingName
BUILDING_NAME
buildingName
BUILDING_NUMBER
buildingNumber
DEPENDENT_THOROUGHFARE
dependentThoroughfare
THOROUGHFARE
thoroughfare
POST_TOWN
postTown
DOUBLE_DEPENDENT_LOCALITY
doubleDependentLocality
DEPENDENT_LOCALITY
dependentLocality
POSTCODE
postcode
POSTCODE_TYPE
postcodeType
X_COORDINATE
position
Y_COORDINATE
LATITUDE
positionLatLong
LONGITUDE
RPC
rpc
COUNTRY
country
CHANGE_TYPE
changeType
LA_START_DATE
laStartDate
RM_START_DATE
rmStartDate
LAST_UPDATE_DATE
lastUpdateDate
CLASS
class
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.
The CSV format of AddressBase Core means:
Column headers are included in the file.
There is one record per line in each file.
Fields are separated by commas.
No comma is placed at the end of each row in the file.
Records are terminated by carriage return/line feed.
For MGBS orders, one file containing all records is produced.
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:
The single file is easy to transfer and offers the end-user a rich experience.
Attribute names are not limited in length making it customer 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.
Conforms to OGC standard.
In most cases, it is a Plug and Play format.
For both MGBS and tile supplies, GeoPackage supplies will be provided as one file.
This release note provides information about the release of the AddressBase Core product on 17 December 2024.
AddressBase Core
34 552 949
31 804
*. These counts are based on a Managed Great Britain Set (MGBS). If you ordered your national coverage via the online ordering system using a polygon outline, your counts may differ.
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.
AddressBase Core
34 552 949
34 552 942
7
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.
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:
Inserts
8 609
Updates
20 768
Deletes
2 427
COU populated 5km tile count
2 816
It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the .
The following information relates to the currency of the source data used in the creation of this release of AddressBase Core:
Royal Mail Postcode Address File (PAF)
13 December 2024
National Land and Property Gazetteer
13 December 2024
One Scotland Gazetteer
18 November 2024
OS MasterMap Topography Layer
05 September 2024
