Only this pageAll pages
Powered by GitBook
Couldn't generate the PDF for 1540 pages, generation stopped at 100.
Extend with 50 more pages.
1 of 100

OS Downloads

Loading...

Addressing and Location

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

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.

Epoch 118

This release note provides information about the May 2025 (Epoch 118) release of AddressBase products.

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

Epoch 117

This release note provides information about the March 2025 (Epoch 117) release of AddressBase products.

This release note provides information about the March 2025 (Epoch 117) release of AddressBase Islands products.

Epoch 116

This release note provides information about the February 2025 (Epoch 116) release of AddressBase products.

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

Epoch 115

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

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

Epoch 114

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

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

Epoch 113

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

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

Epoch 112

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

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

Epoch 111

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

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

Epoch 110

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

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

Epoch 109

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

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

AddressBase Core is supplied weekly and its release notes can be found on the .

OS Open UPRN release notes can be found on the .

AddressBase Core Release Notes page
OS Open UPRN Release Notes pages
AddressBase products – May 2025 release note
AddressBase Islands products – May 2025 release note
AddressBase products – March 2025 release note
AddressBase Islands products – March 2025 release note
AddressBase products – February 2025 release note
AddressBase Islands products – February 2025 release note
AddressBase products – December 2024 release note
AddressBase Islands products – December 2024 release note
AddressBase products – November 2024 release note
AddressBase Islands products – November 2024 release note
AddressBase products – September 2024 release note
AddressBase Islands products – September 2024 release note
AddressBase products – August 2024 release note
AddressBase Islands products – August 2024 release note
AddressBase products – June 2024 release note
AddressBase Islands products – June 2024 release note
AddressBase products – May 2024 release note
AddressBase Islands products – May 2024 release note
AddressBase products – April 2024 release note
AddressBase Islands – April 2024 release note

OS Download Products' Documentation

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.

What's available on this site?

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 are two types of Download data product: OS Premium and OS OpenData.

What are OS Premium Download data products?

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

What are OS OpenData Download products?

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


Download product portfolios


AddressBase Products May 2025 – Epoch 118

This release note provides information about the May 2025 (Epoch 118) release of the AddressBase products. These products were released to customers on 01 May 2025.

Object Without Postal Address (OWPA) enhancement in Epoch 118 for AddressBase Premium and AddressBase Plus

There is a small uplift in this release of both AddressBase Premium and AddressBase Plus due to an improvement in the Object Without Postal Address (OWPA) features contained within these two products. As a result of this uplift, COU counts are around 30% larger, in comparison to the 3 previous releases. This may result in slower processing times.

Record counts

Product
Full Supply Record Count
Change-Only Update Record Count

OS Open UPRN

41 196 104

N/A

AddressBase

30 705 430

152 191

AddressBase Plus

38 390 448

1 085 737

AddressBase Premium

See rows below

See rows below

Street

1 515 628

4 732

Street Descriptor

1 639 498

3 233

BLPU

41 196 104

790 039

Classification

45 017 696

446 122

LPI

46 450 006

620 587

Organisation

1 398 046

19 314

Delivery Point Address

30 816 296

64 760

Application Cross Ref.

199 441 353

1 235 928

Successor

0

0

  • The Full Supply record 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.

  • Please note that Change-Only Updates (COUs) are not available for the OS Open UPRN product.

Product supply comparison

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

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

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

Product
MGBS Full Count
National AOI Full Count
Difference

AddressBase

30 705 430

30 705 430

0

AddressBase Plus

38 390 448

38 390 426

22

AddressBase Premium

See rows below

See rows below

See rows below

Street

1 515 628

1 515 625

3

Street Descriptor

1 639 498

1 639 495

3

BLPU

41 196 104

41 196 078

26

Classification

45 017 696

45 017 670

4

LPI

46 450 006

46 449 979

27

Organisation

1 398 046

1 398 044

2

Delivery Point Address

30 816 296

30 816 296

0

Application Cross Ref.

199 441 353

199 441 327

26

Successor

0

0

0

Changed records

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

AddressBase

Change Type
Count

Inserts

39 607

Updates

103 385

Deletes

9 199

COU Populated Tile Count

5 450

AddressBase Plus

Change Type
Count

Inserts

146 606

Updates

896 728

Deletes

42 403

COU Populated Tile Count

8 520

AddressBase Premium

AddressBase Premium Table
Inserts
Updates
Deletes

Street

1 524

3 177

31

Street Descriptor

1 572

1 627

34

BLPU

146 717

640 377

2 945

Classification

172 147

242 226

31 749

LPI

168 697

448 093

3 797

Organisation

5 785

5 762

7 767

Delivery Point Address

40 444

14 910

9 406

Application Cross Ref.

564 892

636 931

34 105

Source data currency

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

Data Source
Date

Royal Mail PAF

27 March 2025

National Land and Property Gazetteer

27 March 2025

One Scotland Gazetteer

10 March 2025

VOA Non-Domestic Rates

25 March 2025

VOA Council Tax

25 March 2025

OS MasterMap Topography Layer

27 February 2025

OS MasterMap Highways Network

07 March 2025

Code-Point with Polygons

02 January 2025

Boundary-Line

02 October 2024

Data issues

AddressBase

AddressBase Plus issues

AddressBase Premium

Improvements in Epoch 118

Valuation Office Agency matching

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

Data Source
Records Received
% Matched

Council Tax

27 251 204

99.91

Non-Domestic Rates

2 120 750

96.46

Next release

The next release of AddressBase products, Epoch 119, is scheduled for 12 June 2025.

Addressing and Location Portfolio Information

This page provides an overview of the OS downloadable products in the Addressing and Location Portfolio.

Addressing and location products

Addressing and location products provide authoritative and accurate address, property and land data, with comprehensive location-based directories for users to draw from. The following downloadable products are available within the Addressing and Location Portfolio:

AddressBase Products March 2025 – Epoch 117

This release note provides information about the March 2025 Epoch 117 release of the AddressBase products. These products were released to customers on 20 March 2025.

Record counts

  • The Full Supply record 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.

  • Please note that Change-Only Updates (COUs) are not available for the OS Open UPRN product.

Product supply comparison

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

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

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

Changed records

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

AddressBase

AddressBase Plus

AddressBase Premium

Source data currency

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

Data issues

AddressBase Plus issues

Affected output formats: CSV and GML

  • There are 7 966 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 231 records with a sao_start_no or sao_text that have no Parent UPRN in the product. This is because the Parent UPRN is a historical record which is included as part of the logic for record inclusion in the AddressBase Plus products.

Improvements in Epoch 117

Valuation Office Agency matching

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

Tertiary classifications

Work is being undertaken to improve the classifications of records within the AddressBase products. This work has resulted in 69 348 more tertiary classifications present in Epoch 117 compared to Epoch 116. Indeed, 88.6 % of these tertiary classification improvements are against residential codes.

Next release

The next release of AddressBase products, Epoch 118, is scheduled for 01 May 2025.

This is a self-serve site containing documentation and guides relating to Ordnance Survey (OS) Premium and OpenData Download products .

The Download products are grouped by : , , , , , and .

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

What's new?

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

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

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

The terms and conditions on which the OS Premium Download data products are made available can be found via the applicable links on the .

The terms and conditions on which the OS OpenData Download products are made available are contained within the and can be found via the applicable links under each OS OpenData geospatial dataset available for download from the . 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.

Details of live and resolved data issues for AddressBase will be communicated on the . This page will provide details of their impacts and updates on the expected time frame for their resolution.

Details of live and resolved data issues for AddressBase Plus will be communicated on the . This page will provide details of their impacts and updates on the expected time frame for their resolution.

Details of live and resolved data issues for AddressBase Premium will be communicated on the . This page will provide details of their impacts and updates on the expected time frame for their resolution.

Product
Full Supply Record Count
Change-Only Update Record Count
Product
MGBS Full Count
National AOI Full Count
Difference
Change Type
Count
Change Type
Count
AddressBase Premium Table
Inserts
Updates
Deletes
Data Source
Date
Data Source
Records Received
% Matched
✨
available to download through the OS Data Hub
Product Announcements page
Product Refresh Dates page
PSGA Product Summary page
OS Partner
Public Sector Geospatial Agreement (PSGA)
OS Data Hub
Premium, Public Sector and Energy and Infrastructure plans
OS Data Hub
legal information pages of the OS Data Hub
Open Government Licence
OS Data Hub
AddressBase Known Data Issues page
AddressBase Plus Known Data Issues page
AddressBase Premium Known Data Issues page
Addressing and Location
Contextual or Derived Mapping
Networks
Topography
Identifiers
Height and Imagery
portfolio

OS Open UPRN

41 052 332

N/A

AddressBase

30 675 022

138 394

AddressBase Plus

38 286 245

721 346

AddressBase Premium

See rows below

See rows below

Street

1 514 135

4 127

Street Descriptor

1 637 960

4 765

BLPU

41 052 332

348 127

Classification

44 877 298

198 513

LPI

46 285 106

149 761

Organisation

1 400 028

27 007

Delivery Point Address

30 785 258

57 204

Application Cross Ref.

198 910 566

717 312

Successor

0

0

AddressBase

30 675 022

30 675 022

0

AddressBase Plus

38 286 245

38 286 223

22

AddressBase Premium

See rows below

See rows below

See rows below

Street

1 514 135

1 514 132

3

Street Descriptor

1 637 960

1 637 957

3

BLPU

41 052 332

41 052 306

26

Classification

44 877 298

44 877 272

26

LPI

46 285 106

46 285 079

27

Organisation

1 400 028

1 400 026

2

Delivery Point Address

30 785 258

30 785 258

0

Application Cross Ref.

198 910 566

198 910 540

26

Successor

0

0

0

Inserts

32 301

Updates

96 676

Deletes

9 417

COU Populated Tile Count

5 412

Inserts

47 638

Updates

659 891

Deletes

13 817

COU Populated Tile Count

7 297

Street

1 071

3 031

25

Street Descriptor

1 114

3 616

35

BLPU

44 401

299 702

4 024

Classification

68 269

102 102

28 142

LPI

59 085

85 866

4 810

Organisation

5 710

8 051

13 246

Delivery Point Address

33 073

14 982

9 149

Application Cross Ref.

191 523

486 447

39 342

Royal Mail PAF

13 February 2025

National Land and Property Gazetteer

13 February 2025

One Scotland Gazetteer

27 January 2025

VOA Non-Domestic Rates

10 February 2025

VOA Council Tax

10 February 2025

OS MasterMap Topography Layer

16 January 2025

OS MasterMap Highways Network

06 February 2025

Code-Point with Polygons

02 January 2025

Boundary-Line

02 October 2024

Council Tax

27 247 539

99.9

Non-Domestic Rates

2 120 424

96.48

AddressBase Products February 2025 – Epoch 116

This release note provides information about the February 2025 (Epoch 116) release of the AddressBase products. These products were released to customers on 06 February 2025.

Known issues will now be displayed on the 'Product Known Data Issues' subpages under each product.

Record counts

Product
Full Supply Record Count
Change-Only Update Record Count

OS Open UPRN

41,011,955

N/A

AddressBase

30,652,138

157,150

AddressBase Plus

38,252,424

582,353

AddressBase Premium

See rows below

See rows below

Street

1,513,089

5,202

Street Descriptor

1,636,881

2,918

BLPU

41,011,955

320,110

Classification

44,837,171

154,389

LPI

46,230,831

129,683

Organisation

1,407,564

16,239

Delivery Point Address

30,761,334

69,996

Application Cross Ref.

198,758,385

736,674

Successor

0

0

  • The Full Supply record 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.

  • Please note that Change-Only Updates (COUs) are not available for the OS Open UPRN product.

Product supply comparison

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

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

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

Product
MGBS Full Count
National AOI Full Count
Difference

AddressBase

30,652,138

30,652,138

0

AddressBase Plus

38,252,424

38,252,403

21

AddressBase Premium

See rows below

See rows below

See rows below

Street

1,513,089

1,513,086

3

Street Descriptor

1,636,881

1,636,878

3

BLPU

1,011,955

41,011,930

25

Classification

44,837,171

44,837,146

25

LPI

6,230,831

46,230,805

26

Organisation

407,564

1,407,562

2

Delivery Point Address

30,761,334

30,761,334

0

Application Cross Ref.

198,758,385

198,758,360

25

Successor

0

0

0

Changed records

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

AddressBase

Change Type
Count

Inserts

43,892

Updates

103,297

Deletes

9,961

COU Populated Tile Count

5,743

AddressBase Plus

Change Type
Count

Inserts

48,887

Updates

521,021

Deletes

12,445

COU Populated Tile Count

6,909

AddressBase Premium

AddressBase Premium Table
Inserts
Updates
Deletes

Street

1,633

3,535

34

Street Descriptor

1,684

1,194

40

BLPU

42,757

274,322

3,031

Classification

52,337

82,401

19,651

LPI

57,853

67,612

4,218

Organisation

4,337

4,480

7,422

Delivery Point Address

44,752

15,200

10,044

Application Cross Ref.

192,512

509,368

34,794

Source data currency

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

Data Source
Date

Royal Mail PAF

02 January 2025

National Land and Property Gazetteer

02 January 2025

One Scotland Gazetteer

09 December 2024

VOA Non-Domestic Rates

23 December 2024

VOA Council Tax

23 December 2024

OS MasterMap Topography Layer

28 November 2024

OS MasterMap Highways Network

05 December 2024

Code-Point with Polygons

02 January 2025

Boundary-Line

02 October 2024

Improvements in Epoch 116

Valuation Office Agency matching

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

Data Source
Records Received
% Matched

Council Tax

27,227,905

99.92

Non-Domestic Rates

2,120,341

96.44

Tertiary classifications

Work is being undertaken to improve the classifications of records within the AddressBase products. This work has resulted in 49 241 more tertiary classifications present in Epoch 116 compared to Epoch 115. Indeed, 88.69 % of these tertiary classification improvements are against residential codes.

Next release

The next release of AddressBase products, Epoch 117, is scheduled for 20 March 2025.

AddressBase Fundamentals

The following AddressBase Fundamentals pages provide an overview of the 'family' of AddressBase products. They cover key elements of design for AddressBase products, including data formats, classification scheme, product supply, 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 page for each individual product from the left-hand-side menu).

AddressBase Islands May 2025 – Epoch 118

This release note provides information about the May 2025 (Epoch 118) release of the AddressBase Islands products. These products were released to customers on 01 May 2025.

Object Without Postal Address (OWPA) enhancement in Epoch 118 for AddressBase Premium Islands and AddressBase Plus Islands

There is a small uplift in this release of both AddressBase Premium Islands and AddressBase Plus Islands due to an improvement in the Object Without Postal Address (OWPA) features contained within these products. As a result of this uplift, COU counts are around 30% larger, in comparison to the 3 previous releases; this may result in slower processing times.

Record counts

Changed records

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

AddressBase Plus Islands

AddressBase Premium Islands

Source data currency

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

Data issues

AddressBase Plus Islands issues

AddressBase Premium Islands issues

Next release

The next release of AddressBase Islands products, Epoch 119, is scheduled for 12 June 2025.

AddressBase Products November 2024 – Epoch 114

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.

Update to the location of AddressBase technical documentation and release notes

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.

Record counts

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

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

Product supply comparison

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

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

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

Changed records

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

AddressBase

AddressBase Plus

AddressBase Premium

Source data currency

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

Data issues

AddressBase Plus issues

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.

Improvements in Epoch 114

Valuation Office Agency matching

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.

Tertiary classifications

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.

PAF matching

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

Next release

The next release of AddressBase products, Epoch 115, is scheduled for 19 December 2024.

A new page detailing any newsworthy announcements for the Download data products.

Product
Full Supply Record Count
Change-Only Update Record Count
Change Type
Count
AddressBase Premium Islands Table
Inserts
Updates
Deletes
Data Source
Date

Details of live and resolved data issues for AddressBase Plus Islands will be communicated on the . This page will provide details of their impacts and updates on the expected time frame for their resolution.

Details of live and resolved data issues for AddressBase Premium Islands will be communicated on the . This page will provide details of their impacts and updates on the expected time frame for their resolution.

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

; simply navigate to the new platform and click Addressing and location portfolio > AddressBase Fundamentals > 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.

Product
Full Supply Record Count[1]
Change-Only Update Record Count[2]
Product
MGBS Full Count
National AOI Full Count
Difference
Change Type
Count
Change Type
Count
AddressBase Premium Table
Inserts
Updates
Deletes
Data Source
Date
Data Source
Records Received
% Matched

Product Announcements

📣

AddressBase Plus Islands

1 162 955

17 958

AddressBase Premium Islands

See rows below

See rows below

Street

48 792

321

Street Descriptor

48 792

32

BLPU

1 241 870

17 908

Classification

1 241 870

3 589

LPI

1 251 678

4 131

Organisation

38 842

254

Delivery Point Address

979 023

14 044

Application Cross Ref.

1 307 510

3 429

Successor

0

0

Inserts

8 257

Updates

9 464

Deletes

237

Street

32

289

0

Street Descriptor

32

0

0

BLPU

2 806

14 937

165

Classification

2 806

618

165

LPI

2 825

1 141

165

Organisation

156

42

56

Delivery Point Address

13 190

213

641

Application Cross Ref.

2 773

360

296

Successor

0

0

0

Pointer (Northern Ireland)

27 March 2025

DigiMap (Channel Islands)

27 March 2025

Isle of Man

27 March 2025

Royal Mail PAF

27 March 2025

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

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

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

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

Council tax

27 171 964

99.92

Non-domestic rates

2 121 757

96.47

Release notes
AddressBase product family
Future and past publication dates
Unique Property Reference Number (UPRN)
Coordinate reference systems
Classification scheme
Data sources
Street names and numbering
Currency, completeness and precision
Product supply
Code lists and enumerations
AddressBase local custodian codes
AddressBase Islands local custodian codes
AddressBase Plus Islands Known Data Issues page
AddressBase Premium Islands Known Data Issues page
OS Download Products’ Documentation Platform
Release notes for AddressBase products are available on the new platform

AddressBase Islands February 2025 – Epoch 116

This release note provides information about the February 2025 (Epoch 116) release of the AddressBase Islands products. These products were released to customers on 06 February 2025.

Known issues will now be displayed on the 'Product Known Data Issues' subpages under each product.

Record counts

Product
Full Supply Record Count
Change-Only Update Record Count

AddressBase Plus Islands

1,154,084

3,135

AddressBase Premium Islands

See rows below

See rows below

Street

48,727

179

Street Descriptor

48,727

55

BLPU

1,238,230

4,281

Classification

1,238,230

2,461

LPI

1,247,950

3,075

Organisation

38,827

250

Delivery Point Address

965,970

1,124

Application Cross Ref.

1,304,112

2,138

Successor

0

0

Changed records

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

AddressBase Plus Islands

Change Type
Count

Inserts

1,315

Updates

1,539

Deletes

281

AddressBase Premium Islands

AddressBase Premium Islands Table
Inserts
Updates
Deletes

Street

52

126

1

Street Descriptor

52

2

1

BLPU

1,535

2,515

231

Classification

1,535

695

231

LPI

1,544

1,300

231

Organisation

55

109

86

Delivery Point Address

886

143

95

Application Cross Ref.

1,499

297

342

Successor

0

0

0

Source data currency

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

Data Source
Date

Pointer (Northern Ireland)

02 January 2025

DigiMap (Channel Islands)

02 January 2025

Isle of Man

02 January 2025

Royal Mail PAF

02 January 2025

Next release

The next release of AddressBase Islands products, Epoch 117, is scheduled for 20 March 2025.

AddressBase Islands August 2024 – Epoch 112

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.

Record Counts

Changed Records

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

AddressBase Plus Islands

AddressBase Premium Islands

Source Data Currency

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

Data Issues

AddressBase Plus Islands Issues

There are no reported issues in this release of AddressBase Plus Islands.

AddressBase Premium Islands issues

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.

Next Release

The next release of AddressBase Islands products, Epoch 113, is scheduled for 26 September 2024.

AddressBase Islands March 2025 – Epoch 117

This release note provides information about the March 2025 Epoch 117 release of the AddressBase Islands products. These products were released to customers on 20 March 2025

Record counts

Changed records

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

AddressBase Plus Islands

AddressBase Premium Islands

Source data currency

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

Data issues

AddressBase Plus Islands issues

There are no reported issues in this release of AddressBase Plus Islands.

AddressBase Premium Islands issues

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.

Next release

The next release of AddressBase Islands products, Epoch 118, is scheduled for 01 May 2025.

Product
Full Supply Record Count
Change-Only Update Record Count
Change Type
Count
AddressBase Premium Islands Table
Inserts
Updates
Deletes
Data Source
Date
Product
Full Supply Record Count
Change-Only Update Record Count
Change Type
Count
AddressBase Premium Islands Table
Inserts
Updates
Deletes
Data Source
Date

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

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

Pointer (Northern Ireland)

11 July 2024

DigiMap (Channel Islands)

04 July 2024

Isle of Man

11 July 2024

Royal Mail PAF

11 July 2024

AddressBase Plus Islands

1 154 935

3 461

AddressBase Premium Islands

See rows below

See rows below

Street

48 760

127

Street Descriptor

48 760

49

BLPU

1 239 229

3 933

Classification

1 239 229

2 023

LPI

1 249 018

2 597

Organisation

38 742

258

Delivery Point Address

966 474

1 129

Application Cross Ref.

1 305 033

1 692

Successor

0

0

Inserts

1 039

Updates

2 234

Deletes

188

Street

35

90

2

Street Descriptor

35

12

2

BLPU

1 124

2 684

125

Classification

1 124

774

125

LPI

1 193

1 279

125

Organisation

58

57

143

Delivery Point Address

654

325

150

Application Cross Ref.

1 114

385

193

Successor

0

0

0

Pointer (Northern Ireland)

13 February 2025

DigiMap (Channel Islands)

13 February 2025

Isle of Man

13 February 2025

Royal Mail PAF

13 February 2025

AddressBase Products September 2024 – Epoch 113

This release note provides information about the September 2024 release of the AddressBase products. These products were released to customers on 26 September 2024.

Record counts

Product
Full Supply Record Count[1]
Change-Only Update Record Count[2]

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

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

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

Product supply comparison

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

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

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

Product
MGBS Full Count
National AOI Full Count
Difference

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

Changed records

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

AddressBase

Change Type
Count

Inserts

32 275

Updates

96 919

Deletes

8 578

COU Populated Tile Count

5 003

AddressBase Plus

Change Type
Count

Inserts

43 451

Updates

621 151

Deletes

12 692

COU Populated Tile Count

7 088

AddressBase Premium

AddressBase Premium Table
Inserts
Updates
Deletes

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

Source data currency

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

Data Source
Date

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

Data issues

AddressBase Plus issues

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.

Improvements in Epoch 113

Valuation Office Agency matching

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.

Data Source
Records Received
% Matched

Council tax

27 145 616

99.92

Non-domestic rates

2 122 260

96.47

Tertiary classifications

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.

PAF matching

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

Next release

The next release of AddressBase products, Epoch 114, is scheduled for 07 November 2024.

AddressBase Islands June 2024 – Epoch 111

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.

Record Counts

Changed Records

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

AddressBase Plus Islands

AddressBase Premium Islands

Source Data Currency

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

Data Issues

AddressBase Plus Islands Issues

There are no reported issues in this release of AddressBase Plus Islands.

AddressBase Premium Islands issues

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.

Next Release

The next release of AddressBase Islands products, Epoch 112, is scheduled for 15 August 2024.

AddressBase Islands May 2024 – Epoch 110

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.

Record Counts

Changed Records

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

AddressBase Plus Islands

AddressBase Premium Islands

Source Data Currency

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

Data Issues

AddressBase Plus Islands Issues

There are no reported issues in this release of AddressBase Plus Islands.

AddressBase Premium Islands issues

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.

Next Release

The next release of AddressBase Islands products, Epoch 111, is scheduled for 27 June 2024.

AddressBase Products April 2024 – Epoch 109

This release note provides information about the April 2024 release of the AddressBase products. These products were released to customers on 05 April 2024.

Record Counts

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

  2. 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.

Product Supply Comparison

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

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

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

Changed Records

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

AddressBase

AddressBase Plus

AddressBase Premium

Source Data Currency

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

Data Issues

AddressBase Plus Issues

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.

Improvements in Epoch 109

Valuation Office Agency Matching

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.

Tertiary Classifications

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.

PAF Matching

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

Notification of Epoch 109’s Improvement in Historic BLPU State Code Completeness and Large Release Size

Summary

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.

Issue description

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.

Impact

This quality improvement means a larger than usual supply of COUs in this release.

Next Release

The next release of AddressBase products, Epoch 110, is scheduled for 16 May 2024.

Product
Full Supply Record Count
Change-Only Update Record Count
Change Type
Count
AddressBase Premium Islands Table
Inserts
Updates
Deletes
Data Source
Date
Product
Full Supply Record Count
Change-Only Update Record Count
Change Type
Count
AddressBase Premium Islands Table
Inserts
Updates
Deletes
Data Source
Date
Product
Full Supply Record Count[1]
Change-Only Update Record Count[2]
Product
MGBS Full Count
National AOI Full Count
Difference
Change Type
Count
Change Type
Count
AddressBase Premium Table
Inserts
Updates
Deletes

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

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

Pointer (Northern Ireland)

22 May 2024

DigiMap (Channel Islands)

12 May 2024

Isle of Man

23 May 2024

Royal Mail PAF

23 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

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

Pointer (Northern Ireland)

10 April 2024

DigiMap (Channel Islands)

11 April 2024

Isle of Man

11 April 2024

Royal Mail PAF

11 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

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

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

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

Data Source

Records Received

% Matched

Council Tax

27 033 727

99.95

Non-Domestic Rates

2 120 769

96.58

Street names and numbering

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 Islands April 2024 – Epoch 109

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.

Record Counts

Product
Full Supply Record Count
Change-Only Update Record Count

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

Changed Records

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

AddressBase Plus Islands

Change Type
Count

Inserts

994

Updates

171 443

Deletes

412

AddressBase Premium Islands

AddressBase Premium Islands Table
Inserts
Updates
Deletes

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

Source Data Currency

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

Data Source
Date

Pointer (Northern Ireland)

28 February 2024

DigiMap (Channel Islands)

29 February 2024

Isle of Man

29 February 2024

Royal Mail PAF

28 February 2024

Data Issues

AddressBase Plus Islands Issues

There are no reported issues in this release of AddressBase Plus Islands.

AddressBase Premium Islands issues

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.

Notification of Epoch 109’s Improvement in Historic BLPU State Code Completeness and Large Release Size

Summary

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.

Issue description

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.

Impact

This quality improvement means a larger than usual supply of COUs.

Next Release

The next release of AddressBase Islands products, Epoch 110, is scheduled for Thursday 16 May 024.

AddressBase Products June 2024 – Epoch 111

This release note provides information about the June 2024 release of the AddressBase products. These products were released to customers on 27 June 2024.

Record Counts

Product
Full Supply Record Count[1]
Change-Only Update Record Count[2]

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

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

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

Product Supply Comparison

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

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

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

Product
MGBS Full Count
National AOI Full Count
Difference

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

Changed Records

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

AddressBase

Change Type
Count

Inserts

33 506

Updates

80 002

Deletes

9 827

COU Populated Tile Count

5 140

AddressBase Plus

Change Type
Count

Inserts

45 949

Updates

2 210 934

Deletes

13 052

COU Populated Tile Count

7 162

AddressBase Premium

AddressBase Premium Table
Inserts
Updates
Deletes

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

Source Data Currency

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

Data Source
Date

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

Data Issues

AddressBase Plus Issues

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.

Improvements in Epoch 111

Valuation Office Agency Matching

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.

Data Source
Records Received
% Matched

Council Tax

27 084 483

99.94

Non-Domestic Rates

2 123 193

96.48

Tertiary Classifications

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.

PAF Matching

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

Next Release

The next release of AddressBase products, Epoch 112, is scheduled for 15 August 2024.

AddressBase Products December 2024 – Epoch 115

This release note provides information about the December 2024 release of the AddressBase products. These products were released to customers on 19 December 2024.

Record counts

Product
Full Supply Record Count[1]
Change-Only Update Record Count[2]

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

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

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

Product supply comparison

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

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

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

Product
MGBS Full Count
National AOI Full Count
Difference

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

Changed records

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

AddressBase

Change Type
Count

Inserts

52 317

Updates

92 108

Deletes

16 273

COU Populated Tile Count

5 743

AddressBase Plus

Change Type
Count

Inserts

47 492

Updates

498 918

Deletes

20 799

COU Populated Tile Count

7 094

AddressBase Premium

AddressBase Premium Table
Inserts
Updates
Updates

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

Source data currency

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

Data Source
Date

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

Data issues

AddressBase Plus

Affected output formats: CSV and GML

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

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

Improvements in Epoch 115

Valuation Office Agency matching

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

Data Source
Records Received
% Matched

Council tax

27 201 555

99.92

Non-domestic rates

2 119 490

96.49

Tertiary classifications

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

PAF matching

AddressBase, AddressBase Plus and AddressBase Premium

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

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

Next release

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

Unique Property Reference Number (UPRN)

Future and past publication dates

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

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

Future AddressBase epoch publication dates

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

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.

Past AddressBase epoch publication dates

Classification scheme

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:

  • The AddressBase Classification Scheme is applicable to all of the AddressBase products

  • The level of classification varies across all addressable objects and across the different AddressBase products. AddressBase provides primary level classification for addressable objects, AddressBase Core provides up to secondary level, while AddressBase Plus, AddressBase Plus Islands, AddressBase Premium and AddressBase Premium Islands provide up to tertiary / quaternary level.

  • There are only certain classification codes that extend to the quaternary classification level as shown above.

AddressBase Classification Scheme download

The full AddressBase Classification Scheme is available in CSV (comma-separated values) and .xlsx formats for download in the following zip file.

AddressBase Islands November 2024 – Epoch 114

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.

Update to the location of AddressBase technical documentation and release notes

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.

Record counts

Changed records

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

AddressBase Plus Islands

AddressBase Premium Islands

Source data currency

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

Data issues

AddressBase Plus Islands issues

There are no reported issues in this release of AddressBase Plus Islands.

AddressBase Premium Islands issues

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.

Next release

The next release of AddressBase Islands products, Epoch 115, is scheduled for 19 December 2024.

AddressBase Products August 2024 – Epoch 112

This release note provides information about the August 2024 release of the AddressBase products. These products were released to customers on 15 August 2024.

Record Counts

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

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

Product Supply Comparison

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

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

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

Changed Records

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

AddressBase

AddressBase Plus

AddressBase Premium

Source Data Currency

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

Data Issues

AddressBase Plus Issues

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.

Improvements in Epoch 112

Valuation Office Agency Matching

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.

Tertiary Classifications

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.

PAF Matching

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

Next Release

The next release of AddressBase products, Epoch 113, is scheduled for 26 September 2024.

AddressBase Products May 2024 – Epoch 110

This release note provides information about the May 2024 release of the AddressBase products. These products were released to customers on 16 May 2024.

Record Counts

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

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

Product Supply Comparison

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

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

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

Changed Records

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

AddressBase

AddressBase Plus

AddressBase Premium

Source Data Currency

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

Data Issues

AddressBase Plus Issues

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.

Improvements in Epoch 110

Valuation Office Agency Matching

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.

Tertiary Classifications

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.

PAF Matching

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

Next Release

The next release of AddressBase products, Epoch 111, is scheduled for 27 June 2024.

AddressBase Islands September 2024 – Epoch 113

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.

Record counts

Changed records

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

AddressBase Plus Islands

AddressBase Premium Islands

Source data currency

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

Data issues

AddressBase Plus Islands issues

There are no reported issues in this release of AddressBase Plus Islands.

AddressBase Premium Islands issues

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.

Next release

The next release of AddressBase Islands products, Epoch 114, is scheduled for 07 November 2024.

Currency, completeness and precision

AddressBase product family

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

Ordnance Survey is responsible for customer management, sales, marketing and distribution of the AddressBase products.

Comparison of AddressBase products

This comparison table highlights the similarities and differences between the AddressBase products

Product summaries

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

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

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

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

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.

Data sources

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.

AddressBase Data Inputs

The creation of AddressBase products brings together the best parts of:

Valuation Office Agency

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.

Roles and Responsibilities

GeoPlace

England and Wales

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.

Scotland

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.

Local Authority Custodians

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.

Please be aware that the UPRN is not the Primary Key for all tables within the and supply. Please see the relational models in and for more information.

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

; simply navigate to the new platform and click Addressing and location portfolio > AddressBase Fundamentals > 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.

Product
Full Supply Record Count
Change-Only Update Record Count
Change Type
Count
AddressBase Premium Islands Table
Inserts
Updates
Deletes
Data Source
Date
Product
Full Supply Record Count[1]
Change-Only Update Record Count[2]
Product
MGBS Full Count
National AOI Full Count
Difference
Change Type
Count
Change Type
Count
AddressBase Premium Table
Inserts
Updates
Deletes
Data Source
Date
Product
Full Supply Record Count[1]
Change-Only Update Record Count[2]
Product
MGBS Full Count
National AOI Full Count
Difference
Change Type
Count
Change Type
Count
AddressBase Premium Table
Inserts
Updates
Deletes
Data Source
Date
Data Source
Records Received
% Matched
Product
Full Supply Record Count
Change-Only Update Record Count
Change Type
Count
AddressBase Premium Islands Table
Inserts
Updates
Deletes

This information is managed by 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.

AddressBase
AddressBase Core
AddressBase Plus
AddressBase Premium

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 for further details on classification levels). It also provides a primary level classification.

AddressBase Premium
AddressBase Premium Islands
AddressBase Premium structure
AddressBase Premium Islands structure
AddressBase product 'family' release notes
AddressBase Core release note

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

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

Pointer (Northern Ireland)

30 September 2024

DigiMap (Channel Islands)

03 October 2024

Isle of Man

03 October 2024

Royal Mail PAF

03 October 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

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

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

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

Data Source

Records Received

% Matched

Council Tax

27 116 559

99.92

Non-Domestic Rates

2 123 229

96.47

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

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

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

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

Council Tax

27 058 858

99.92

Non-Domestic Rates

2 123 768

96.44

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

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

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

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

AddressbasePostalCode

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.

Value
Description

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

ChangeTypeCode

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.

Value
Description

I

Insert

U

Update

D

Delete

CountryCode

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.

Value
Description

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.

LanguageCode

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’.

Value
Description

ENG

English

CYM

Welsh

GAE

Gaelic (Scottish)

BIL

Bilingual

OS Download Products’ Documentation Platform
Release notes for AddressBase products are available on the new platform
GeoPlace
classification scheme page
AddressBase
AddressBase Core
AddressBase Plus
AddressBase Premium

Code lists and enumerations

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.

Coordinate reference systems

Product supply

Available supply formats

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

Comma-Separated Values (CSV)

Geography Markup Language (GML) version 3.2

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

Supply media and file structure

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

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

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

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

Non-geographic chunking

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

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

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

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

Geographic chunking

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

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

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

Coverage

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

National sets

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

  • Data arriving faster and in a more predictable manner.

  • Seeing the same version of features as other organisations.

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

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

Customer defined areas of interest

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

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

Product updates

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

Full Supply

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

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

COU

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

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

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

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

This means the user will need to remove all features that previously existed in the provided tile(s) and insert the entire new tile(s) in its place.

AddressBase Islands December 2024 – Epoch 115

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.

Record counts

Product
Full Supply Record Count
Change-Only Update Record Count

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

Changed records

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

AddressBase Plus Islands

Change Type
Count

Inserts

1 275

Updates

2 687

Deletes

300

AddressBase Premium Islands

AddressBase Premium Islands Table
Inserts
Updates
Deletes

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

Source data currency

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

Data Source
Date

Pointer (Northern Ireland)

14 November 2024

DigiMap (Channel Islands)

14 November 2024

Isle of Man

14 November 2024

Royal Mail PAF

14 November 2024

Data issues

AddressBase Premium Islands

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

  • AddressBase Premium Islands, AddressBase Plus Islands

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

Next release

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

RPCCode

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

OfficialFlagCode

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.

BLPUStateCode

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

Date

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.

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

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

Value
Description
Implementation notes
Value
Description
Value
Description
Value
Type
Notes
http://www.w3.org.
https://www.ordnancesurvey.co.uk/business-government/tools-support/orders

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.

N

Unofficial Address

Y

Official Address

1

under construction

2

In use

3

Unoccupied /vacant/derelict

4

No longer existing

6

Planning permission granted

2024-10-24

Date

Date columns will follow the structure: CCYY-MM-DD

LogicalStatusCode

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.

Value
Description

1

Approved

3

Alternative

6

Provisional

8

Historical

BLPU records will not have a logical status value of 3, whereas LPI records can have all of the values expressed above.

FileTypeCode

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.

Value
Description

F

Signifies the supply is a full supply

C

Signifies the supply is a COU file

StreetClassificationCode

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.

Value
Description

4

Pedestrian way or footpath

6

Cycletrack or cycleway

8

All vehicles

9

Restricted byway

10

Bridleway

StreetStateCode

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.

Value
Description

1

Under construction

2

Open

4

Permanently closed (STREET_END_DATE must be entered)

PostcodeTypeCode

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.

Value
Description

S

A small user, for example, a residential property

L

A large user, for example, a large commercial company

Time

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.

Value
Type
Notes

14:11:15

Time

Time will follow the structure of HH:MM:SS based on a 24-hour clock.

StreetSurfaceCode

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.

Value
Description

1

Metalled

2

UnMetalled

3

Mixed

AddressBase Islands local custodian codes

The following page details the current local custodian codes of all local custodians contributing to AddressBase Plus Islands and AddressBase Premium Islands products.

The local custodian codes listed in the zip file and table below are applicable to the AddressBase Plus Islands and AddressBase Premium Islands products.

Islands local custodian codes download

Local custodian code data is available to download in CSV format in the following zip file:

Islands local custodian codes table

Local Custodian Code
Local Custodian Name

28

Isle of Man

8130

Antrim and Newtownabbey

8131

Armagh, Banbridge and Craigavon

8132

Belfast

8133

Causeway Coast and Glens

8134

Derry and Strabane

8135

Fermanagh and Omagh

8136

Lisburn and Castlereagh

8137

Mid and East Antrim

8138

Mid Ulster

8139

Newry Mourne and Down

8140

North Down and Ards

8200

Jersey

8205

Guernsey

They are not applicable to the AddressBase, AddressBase Core, AddressBase Plus and AddressBase Premium products; local custodian codes for these products are available from the .

AddressBase local custodian codes page

USRNMatchIndicatorCode

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.

Value
Description

1

Matched manually to the nearest accessible Street.

2

Matched spatially to the nearest USRN. Not necessarily the access street.

StateCode

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

Value
Description

1

Under construction

2

In use

3

Unoccupied / vacant / derelict

4

No longer existing

6

Planning permission granted

AddressBase

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.

Precision identification

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.

Understand the nation with PAF

Every address geo data record provides Royal Mail address information from PAF, the Unique Delivery Point Reference Number (UDPRN) and X and Y coordinates.

Track customer data

Using the basic classifications in AddressBase you can quickly filter between residential and commercial addresses, which is ideal for marketing purposes.

Reduce marketing costs

Our basic classifications – residential or commercial – will reduce the costs and increase the effectiveness of your direct marketing.

Confidence in data

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.

Reduce marketing costs

Our basic classifications – residential or commercial – will reduce the costs and increase the effectiveness of your direct marketing.

Confidence in data

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

House to flat conversions

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.

Paying Royal Mail royalties as a commercial customer

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.

File size

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.

Data from Royal Mail’s PAF

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.

How to get this product

Sample data

Download AddressBase sample data

Visualise AddressBase sample data online

What's next?

To access documentation and resources relating to this product, please refer to the following:

New users should start with the Fundamentals pages to gain high-level insight into AddressBase products. The Getting Started Guide will help you to begin using product data in different software systems. The Technical Specification contains detailed technical insights.

Please see the 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 PSGA (Public Sector Geospatial Agreement) Members. You can .

The has advice on how to get the product for businesses, developers, Partners and PSGA Members (i.e. government and the public sector).

Alternatively, you can try out the full product by applying for .

You can download sample data for the product for free from the . The sample data are available in CSV format and cover one area (Exeter).

AddressBase Getting Started Guide
AddressBase
AddressBase Plus
AddressBase Plus Islands
check if your organisation is a member of the PSGA on the OS website
AddressBase product page on the OS website
a Data Exploration license
OS Data Hub

AddressBase Getting Started Guide

This getting started guide provides instructions for using three AddressBase products in different software applications. Users with limited technical knowledge will be able to follow this guide.

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:

These instructions show you how to get started with , and .

AddressBase
AddressBase Plus
AddressBase Plus Islands
Prerequisites
Data supply
Working with CSV data
Working with GML data
Working with COU data
Creating a single-line or multi-line address
Searching for addresses

Data supply

DVD Supply of area of interest

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.

DVD supply of Managed Great Britain Sets

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.

Secure File Transfer Protocol

Download

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.

Download instructions
  1. When you click Download data, you will be required to enter a password to access the PSGA Member’s Area. On successful entry to the download service, you will be able to view all your orders in the Member’s Area and download your data.

  2. If you have ordered your data from our online portal, you will be sent an email with a link to a download page.

  3. Within the PSGA Member’s Area, you can order and download the data that you require by clicking on Order Data, which can be found under the Map Data heading.

  4. 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.

Chunked files

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:

Non-geographic chunks

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)

Geographic chunks

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.

Unzipping the data

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:

Non-geographic chunks

  • AddressBasePlus_FULL_2020-01-21_001.csv

  • AddressBasePlus_ISL_FULL_2020-01-21_001.csv

Geographic chunks

  • AddressBasePlus_2011-07-29_NC4040.csv

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 .

DVD Supply of area of interest
Unzipping the data
541B
addressbase-islands-local-custodian-codes.zip
archive
690KB
addressbase-product-classification-scheme.zip
archive

Prerequisites

System requirements

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

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

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

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

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

Backup provision of the product

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

Typical data volumes

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

Product
Unzipped CSV file size
Unzipped GML file size

AddressBase

6Gb

32Gb

AddressBase Plus

16Gb

78Gb

AddressBase Plus Islands

450Mb

2Gb

Working with CSV data

Preparing the CSV data

These instructions describe how to prepare the CSV format of AddressBase, AddressBase Plus and AddressBase Plus Islands data for processing.

Merging multiple CSV files
  1. Unzip all the CSV files into a single folder. Ensure there are no spaces in your chosen folder path, for example: C:\AddressBase_Data or C:\AddressBase_Plus_Data or C:\AddressBase_Plus_Islands_Data.

  2. We recommend merging all the CSV files together to save time importing individual files. You can do this manually using a text editor such as Notepad or TextPad, but it is much faster to use a .bat batch file or an MS-DOS command as described below.

  3. To use the .bat batch function, copy the following text and paste it into a new Notepad document: copy *.csv mergedABdata.csv In this example, mergedABdata.csv is the output name of the merged file which will be created, but this can be any user-defined filename with the extension .csv.

  4. Save the Notepad document with the file extension .bat (for example, mergedABdata.bat) in the same directory as the CSV files unzipped previously (for example, C:\AddressBase_Data or C:\AddressBase_Plus_Data).

  5. Close the .bat file and navigate to the directory where you just saved it. Double-click on the .bat file (for example, mergedABdata.bat) and an MS-DOS window will run. Once the process is complete, the MS-DOS screen will close automatically.

  6. If you look in the directory containing the AddressBase CSV files and batch file, you’ll see that there is now an additional single file called mergedABdata.csv (or the user-defined filename you picked when creating your batch file).

Loading CSV into GIS software

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.

Loading CSV into ArcGIS Pro

Note - These instructions are based on ArcGIS Pro version 2.3.3.

  1. Launch ArcGIS Pro and start a new blank project.

  2. Select a folder to save the project to.

  3. Name your project and click OK. The project will then be created. Note - ArcGIS Pro automatically creates a new File Geodatabase (.gdb) within the project folder created. This is different to the creation process in the older ESRI application ArcMap.

  4. You can add a backdrop map for contextual purposes from the available backdrop maps supplied by ESRI or add one of your own from a different File Geodatabase. In this example, we have added a light grey backdrop map canvas supplied by ESRI.

  5. Open the Catalog pane on the right-hand side of the window and expand the listing to see the File Geodatabase created with the project.

  6. To import the AddressBase or AddressBase Plus data, right-click the File Geodatabase, then select Import and from that sub-menu, select Table. A new Geoprocessing window will display in the right-hand pane.

  7. Click the folder icon on the right-hand side of the Input Rows field. A new dialog will open.

  8. Back in the Geoprocessing window, type a name in the Output Name field, then click Run at the bottom of the window.

  9. Once the process has run, a green box will display at the bottom of the Geoprocessing window and the new AddressBase table will be listed in the left-hand panel.

    The data has loaded as a non-geometry table.

  10. To make the data visible against the mapping backdrop, the XY Coordinate fields need to be specified.

    • In the Contents pane, right-click the AB_Plus table (or the output name you chose) and in the dropdown click Display XY data.

  11. In the Geoprocessing window, the XY Table To Point parameters will be displayed.

    • Using the dropdown options, change the X Field to X_COORDINATE or Longitude and the Y Field to Y_COORDINATE or Latitude.

    • Then select Projected Co-ordinate Systems > National Grids > Europe > British National Grid. Note – If you selected X and Y as Longitude and Latitude in the step above, then you need to select ETRS89 [EPSG: 4258] instead.

  12. Click Run.

  13. Once the process has run, a green box will appear at the bottom of the Geoprocessing window and the output XYTableToPoint map layer should appear ticked on the left-hand Contents pane. In the Map window, the addresses will now be displayed as point features.

    You have now successfully loaded the data in ArcGIS Pro.

Loading CSV into ArcGIS Desktop

Note - These instructions are based on ArcGIS Desktop versions 9.3 and 10.

  1. Launch ArcCatalog as a separate program, or within ArcMap if you are using version 10.

  2. Connect to a folder where the AddressBase data you wish to use can be accessed, for example, C:\AddressBase_Data or C:\AddressBase_Plus_Data. To do this:

    • Click File, or select Folder Connections if you are using version 10.

    • Click Connect Folder, or in version 10, right-click on Folder connections > Connect Folder and navigate to the relevant folder.

    • From the main window, select the folder to connect to and click OK.

  3. The folder should now appear in the navigation window to the left of the screen, or within your Catalog window if you have opened it within ArcGIS Map.

  4. Create a File Geodatabase to store the address data. Using the file tree, go to folder connections and navigate to the directory where you wish to create the File Geodatabase, for example: C:\AddressBase_Geodatabase\AddressBase_Plus. This may need to be set up as a new connection as per the above.

  5. Right-click on the folder where you the File Geodatabase should to be contained, then select New and File Geodatabase.

  6. A File Geodatabase will be created and named by default as New File Geodatabase. Rename the File Geodatabase to a name of your choice.

  7. Right-click on your new File Geodatabase, and select Import > Table (single)…

    • For Input Rows, navigate to the location of the CSV data file that contains the merged header and AddressBase or AddressBase Plus data file.

    • The Output Location should automatically populate with the location of the File Geodatabase that is to be updated; this should be the File Geodatabase you created above.

    • Insert a relevant name for the Output Table, for example: AddressBase_data. Ensure that there are no spaces in the table name. This name will appear under your geodatabase.

  8. Click OK.

  9. To create a map of the locations of the AddressBase records, they need to be geocoded.

    • Right-click on the AddressBase table in the geodatabase that you have just created and select Create Feature Class.

    • In the XY Table… window, you can use the dropdowns to change the X Field to either X_COORDINATE or Longitude, and the Y Field to Y_COORDINATE or Latitude.

    • Click on the Input Coordinates icon and navigate to Projected Co-ordinate Systems > National Grids > Europe > British National Grid. Note – If you selected X and Y as Longitude and Latitude in the step above, then you need to select ETRS89 [EPSG: 4258] instead.

  10. Double-click on the chosen Coordinate System, then click Apply and OK.

  11. Click on the folder icon alongside the Output field and navigate to the File Geodatabase you just created above. If you cannot see the File Geodatabase, ensure that the Save as type box at the bottom of the dialog box is set to File and Personal Geodatabase feature classes.

  12. Type in a name for it and click Save.

  13. Leave the Configuration keyword dropdown menu as DEFAULTS. Click OK. Note – You may need to right-click on the Personal Geodatabase where it was saved and select Refresh in order to see your points. At this stage, if you have completed the steps above in ArcCatalog and not within ArcMap, please continue to follow the steps below. Otherwise, if you have been using version 10 with the catalog inside ArcMap, the data can now be loaded into ArcMap.

  14. In ArcMap, select File > Add Data and navigate to the folder where the File Geodatabase was created above.

  15. Double-click on the File Geodatabase to open it, then select all the files inside.

  16. Click Add.

  17. Once the data has been loaded into ArcMap, you may wish to display more than the ESRI-defined Object ID in the Info tool. To change this:

    • Double-click on the spatial dataset.

    • Select the Fields tab.

    • Change the Primary Display Field to your desired field, for example, UPRN.

Loading CSV into MapInfo Pro

Note - These instructions are based on MapInfo Pro version 12.

Note – MapInfo has a size limit of 2Gb on each table. This equates to a maximum number of approximately 4 million AddressBase records.

  1. Launch MapInfo.

  2. Cancel the Quick Start prompt.

  3. Click File > Open and navigate to the folder that contains the AddressBase data.

  4. In the Files of Type dropdown menu, select Comma delimited CSV (*.csv), then click on the AddressBase data to be loaded. Click Open.

  5. In the next window, tick the Use First Line for Column Titles box and select the character set INSERT CHARACTER SET. Click OK. Note – When adding data this way, the field type classifications and field sizes of each column automatically try to fit the type of data that MapInfo believes is contained within the column and the largest value of that classification found within that column. This means that the classifications and field sizes of some attributes may not match the field types and sizes stated in the Technical Specification. The following instructions outline how to change these columns to match those values:

  6. Select File > Save Copy As… and select the AddressBase table that was loaded. Select Save As… and name the table to be created, then click Save.

  7. Open the table that was just created via File > Open. Navigate to and select the copy of the table you just named. Click Open.

  8. Navigate to Table > Maintenance > Table Structure and select the table to be edited. Click OK.

  9. Here you can change the Type and Width of each attribute to match the ones stated in the technical specification:

  10. Type and Width should be changed for all attributes, apart from the following (due to software-specific dependencies):

    • UPRN should be classified as Float.

    • All attributes that have a Field Type of Date in the technical specification should be classified as Character with a length of 10.

  11. After all changes have been made, click OK.

  12. To create a map of the location of the AddressBase records, they need to be geocoded:

    • Ensure the table of AddressBase records that you wish to geocode is open, then navigate to Table > Create Points.

    • Select the table you wish to geocode from the Create Points for Table dropdown menu.

    • Expand the Get X Coordinates from Column dropdown menu and select either X_Coordinate or Longitude.

    • Expand the Get Y Coordinates from Column dropdown menu and select either Y_Coordinate or Latitude.

    • Click on the Projection icon, then select the British Coordinate Systems option from the Category dropdown menu. Select the British National Grid [EPSG: 27700], or if you selected Longitude and Latitude in the steps above, select ETRS89 [EPSG: 4258].

    • Click OK to close that window and OK again to close the next window.

    • Finally, click Window > New Map Window to view the loaded geocoded points.

Loading CSV into QGIS

Note - These instructions are based on QGIS version 2.6.

  1. Launch QGIS and click Settings > Options.

  2. Select CRS from the left-hand menu and check that the Coordinate Reference System is set to British National Grid. Note - Check this is set for both Default CRS for new projects and the CRS for new layers sections. If these are not already set, click Select at the end of each section and type 27700 into the Filter Box to find and select British National Grid. Alternatively, if you intend to use Latitude and Longitude columns, select ETRS89 [EPSG: 4258].

  3. Click OK.

  4. Back in the QGIS UI, go to Layer and select Add Delimited Text Layer.

  5. Select the CSV file and click Open.

  6. Accept the default or create a new layer name for the dataset.

  7. Ensure that the First record has field names box is ticked.

  8. For Field Options, select Decimal separator is comma.

  9. For Geometry Definition, select Point Coordinates.

  10. You should now be able to select the X_Coordinate field for the X Field dropdown and the Y_Coordinate field for the Y Field dropdown if this was not done automatically. Alternatively, if you wish to use the Latitude and Longitude columns, the Longitude column needs to be inserted into the X_COORDINATE field, and the Latitude column needs to be inserted into the Y_COORDINATE field.

  11. Click OK.

Loading CSV into a database

This section describes how to load AddressBase products into a few common databases.

Software dependencies:

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.

UPRN deletions:

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.

Loading CSV into a PostGreSQL database

Note - These instructions are based on PostGreSQL version 1.12.3 and assume that you have set-up your database with the PostGIS spatial extension. It is recommended that you have basic understanding of database terminology before following this guide.

  1. Check that there are no carriage returns (extra rows) at the end of the CSV output file as this will result in errors. To do this, open the CSV file and hit End on your keyboard. Your cursor should now be at the end of the last line, and not on any extra line below. If it is on the line below, hit Delete to remove the extra empty row.

  2. Open the PGAdmin tool (this can be found in Windows Start Menu > PostGreSQL).

  3. Either connect to an existing database or create a new database. It is recommended that the encoding is set to UTF-8.

  4. Open the public schema (although in a production environment, it is advised to use a different schema) and create the tables using the following steps:

    • Open the SQL query tool.

    • This SQL file can be opened in a text editor, and the SQL scripts within it can be copied and pasted into the SQL query tool within PostGreSQL.

  5. Once the table has been created, the data can be loaded into each table using the SQL COPY. Adding the CSV option as the first line contains a header record for each table. Please note that the examples below are for AddressBase, then AddressBase Plus and AddressBase Plus Islands, respectively. The path and filename may need to be changed to reflect your data set-up: COPY addressbase FROM 'C:/Address/AddressBase.csv' DELIMITER ', ' CSV HEADER; COPY addressbase_plus FROM 'C:/Address/AddressBase_Plus.csv' DELIMITER ', ' CSV HEADER; COPY addressbase_plus_islands FROM 'C:/Address/AddressBase_Plus_Islands.csv' DELIMITER ', ' CSV HEADER;

  1. Once loaded, you may want to add Primary Keys to the data. However, these can only be added on columns where the data values are unique. Where there are no unique data values, an index may be added which will aid searching. The UPRN provides the only unique value in AddressBase and AddressBase Plus. Primary Keys are added using the following steps:

  • Right-click on the table name and select Properties.

  • Select the Constraints tab.

  • Click the + to add a new primary key.

  • Enter a name to call the key under the general tab (for example, Key1).

  • Under the definition tab, select UPRN or any other unique value from the dropdown under columns.

  1. Click Save.

  1. You can also index the data by following these steps:

  • Right-click on the table name and select Create > Index.

  • Under general, enter a name (for example, Idx1).

  • Under the definition tab > Columns, click the +.

  • Select the UPRN for example, or any other unique value.

  • Click Save.

Converting coordinates to geometry

A PostGIS extension is required to create geometries. The AddressBase products contain both British National Grid (BNG) and ETRS89 coordinates. The SQL below shows how to create a column for BNG, but it can be altered to utilise the ETRS89 data.

  1. Add a geometry column called geom to make the data usable in a GIS: SELECT AddGeometryColumn ('public', 'addressbase_plus', 'geom', 27700, 'POINT', 2);

  2. Load the data into your new geometry column: UPDATE public.addressbase_plus SET geom = ST_GeomFromText('POINT(' || x_coordinate || ' ' || y_coordinate || ') ', 27700); This sets the geom column in the table to equal the values from the X_coordinate and Y_coordinate columns, with the spatial reference defined as 27700.

  3. Create a spatial index on the data using: CREATE INDEX idx_abp_geom ON public.addressbase_plus USING gist(geom); This adds the index name idx_abp_geom to the same table on the geom column.

Loading CSV into an Oracle database

Note - These instructions assume a basic knowledge of Oracle databases and SQLLDR (the package used to load the CSV files into the database). Other options are available for loading data into Oracle databases.

Using SQLLDR it is not necessary to merge all the AddressBase files into a single file, but it can load the data directly from the file provided as long as it has been unzipped first.

The following steps describe one method for loading a full supply of the data. Sections in italics denote where changes will need to be made to accommodate local file naming.

  1. Copy the data files from the disk to an appropriate location. It is worth noting that the files will need to be unzipped and therefore you will need in the region of 43Gb of free space.

  2. With all the files unzipped, the latter stages are easier if you create a list of all the CSV files to be loaded. This can be done using a batch file that writes all the files out to a text file: dir *.csv /b/s >filelisting.txt pause This file will form the basis for loading the control file in a later step.

  3. Open the folder of your chosen product and you should see three files. Open the file ending createtable.sql in a text editor.

  4. Within the provided SQL there are references to <TablespaceName>, which need to be changed to the tablespace that is being worked in. When these are changed, copy and paste the SQL into Oracle to create the tables.

  5. Next, create a SQLLDR control file. An example of one of these files is Oracle AddressBase_Control.ctl, which is provided in the folder of the GitHub repository in Step 4 above. Open the SQLLDR control file for your chosen product in a text editor.

  6. Within the file you will see lines referencing INFILE. Populate these INFILE lines with the file listing created in Step 3, with one INFLE command for each file. This tells the process to open each of the files and carry out the other tasks listed below it. Note – The last section of the control file creates the Geometry for the X and Y coordinate (British National Grid) if you want to create a Geometry for the Latitude and Longitude values, this will need to be created separately.

  7. Once this file is created, it can be called from a .bat file to run it on the box that holds the database rather than a remote machine. If you wish to run it from a remote machine, contact your Oracle Administrator who will be able to advise on the best way to do this within your environment. The contents of the .bat file should be similar to the following: @sqlldr <username>/<password>@<service name> control= <name of ctl file created previously> Pause

  8. Once the load has completed the relevant indexes need to be built. The SQL statements to create the indexes can be found in the same GitHub repository linked in Step 4 above. As before, you can copy and paste the SQL statements from a text editor into Oracle to create the indexes. The example table name provided may be different to yours, so check if this needs to be changed before use.

Loading CSV into Microsoft SQL Server

Note – There are many ways to load AddressBase products into Microsoft SQL Server; this is just one suggested method for guidance.

  1. Open the SQL Server Management Studio (SSMS).

  2. Right-click on the database you are loading into and select Properties.

  3. Select Options on the left-hand side.

  4. Expand the dropdown box for Recovery Model and select Bulk-logged. This minimises the logfile size, otherwise the default logging for Microsoft SQL Server can cause logfiles to grow over 20Gb and this can cause issues with loading.

  5. Open the SQL Server Management Studio (SSMS) and right-click your database from the left-hand panel.

  6. Navigate to Tasks and click Import Data. This will open the SQL Server Import and Export Wizard.

  7. Click Next.

  8. On the next screen, change your Data Source to Flat File Source.

  9. Use the Browse button to navigate to your CSV file and select it. If you cannot see your files, ensure that the bottom right dropdown box has CSV files (*.csv) selected.

  10. Click Open.

  11. Check that the Text Qualifier is set to a double quote (“). This is to make sure that the quotations in the raw data supply are removed upon loading but that the data remains intact.

  12. On the left-hand side of this screen, select Columns and check that the Column delimiter is set to Comma.

  13. On the left-hand side of the screen, select Advanced.

  14. For each column of data you are loading, you will need to specify a DataType. The Microsoft SQL Server loader defaults each column to a String. The correct Data Type for each column is given in the technical specification:

  15. Once you have changed the Data Types for each column to match those given in the technical specification, click Next.

  16. Check that your table is going to be imported into the correct database and click Next.

  17. On this screen, you can edit the default table name that Microsoft SQL Server has chosen by clicking in the destination box. For example, for AddressBase Plus renaming to [dbo].[ADDRESSBASE_PLUS].

  18. Select Edit Mappings in the bottom right-hand corner.

  19. In the new window, you must remove the tick in the checkbox against the UPRN column, which needs to be the Primary Key of the table. Click OK once the Primary Key alterations have been completed.

  20. Click Next. On this screen, you can check that the Source column and Destination columns are correct.

  21. Click Next. A summary of your import will display. If you want to continue, click Finish.

  22. A report will be generated as your data is imported. Success should appear at the top once complete.

  23. You may need to right-click on your database and click Refresh to see your new table listed.

Setting Primary Keys

To create a Primary Key field, you can run an SQL statement, such as this example for AddressBase Plus below. Note - the columns you are creating these constraints on cannot be null or allowed to be null.

Creating the point geometry

You can also create point geometry using the X and Y coordinates or the Latitude and Longitude coordinate values. This is achieved by running the following SQL statement:

Note – This is using British National Grid coordinates, with 27700 representing the spatial reference of the data. To use the Latitude and Longitude coordinate, the spatial reference should be set to 4258 for ETRS89.

StreetRecordTypeCode

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.

Working with GML data

Loading GML

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

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

Working with COU data

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.

Types of change

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.

High-level COU implementation model

The diagram below shows how to implement an AddressBase, AddressBase Plus and AddressBase Plus Islands COU within a database.

High-level COU implementation model – with archiving

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.

Applying COU to tables

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:

Representation of AddressBase data.
The number of Postcode Address File (PAF) matched records in AddressBase by epoch. The number of PAF matched records in AddressBase has increased steadily over time, from 30 353 039 in Epoch 102 to 30 689 609 in Epoch 114.
The number of Postcode Address File (PAF) matched records in AddressBase by epoch. The number of PAF matched records in AddressBase has increased steadily over time, from 30 353 039 in Epoch 102 to 30 659 595 in Epoch 113.
Graph showing the number of Postcode Address File (PAF) matched records in AddressBase by epoch
BLPU State Code Enumeration
BLPU State Code Enumeration
POF matched in addressbase chart showing epoch 102 to 111 on the bottom axis with figures steadily rising from 30,353,039 to 30,597,448
A graph showing the number of Postcode Address File (PAF) matched records in AddressBase by epoch.
A line graph showing the number of Postcode Address File matched records in AddressBase by Epoch. The data shows a steadily rising trend from 30.3 million in epoch 102 to 30.6 million in epoch 112.
Graph showing the number of Postcode Address File (PAF) matched records in AddressBase by epoch

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.

Downloading header files

AddressBase and AddressBase Plus contain different attributes. This means that there is a separate header file for each of product. Download the file that matches your product using the links below. You will use this file in the section.

Appending a header file to the CSV
  1. Download and save the appropriate product CSV header file into the same folder as the merged AddressBase.csv file created in .

  2. For AddressBase data, copy the relevant text below and paste it into a new Notepad document: copy addressbase-header.csv+ mergedABdata.csv AB_Data.csv For AddressBase Plus and AddressBase Plus Islands data, copy the relevant text below and paste it into a new Notepad document: copy addressbase-plus-header.csv+ mergedAB_Plusdata.csv AB_Plus_Data.csv copy addressbase-plus-header.csv+ mergedAB_Plus_Islands_data.csv AB_Plus_Islands_Data.csv These examples use the name mergedABdata.csv or mergedAB_Plusdata.csv as the file that contains the AddressBase data merged into a single CSV file created above. If you have named this something else, amend that text above accordingly. The order that the documents are referred to in the above text is also important as it states which file is appended to the other. In this instance, the headers CSV file comes first so that the column headers are the first line of the final AddressBase file and the merged data is appended to the column headers.

  3. Save the above Notepad document with the file extension .bat (for example, append.bat) in the same directory as the column headers and the merged AddressBase data (for example, C:\AddressBase_Data or C:\AddressBase_Plus_Data or C:\AddressBase_Plus_Islands_Data).

  4. Close the .bat file and navigate to the directory where it was saved to (for example, C:\AddressBase_Data or C:\AddressBase_Plus_Data). Double-click on the new .bat file (for example, append.bat) and an MS-DOS window will open. Once the process is complete, the MS-DOS screen will close automatically.

  5. Navigate to the directory where the column headers and the merged AddressBase data are located. You will see that a new CSV file has been created, which is the merged column headers and AddressBase data (for example, AddressBase.csv or AddressBase_Plus.csv).

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.

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.

Value
Description

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

systems/software page
alter table dbo.ADDRESSBASE_PLUS add primary key ([UPRN]);
alter table dbo.ADDRESSBASE_PLUS
add geometry_column as geometry::Point([X_Coordinate],[Y_Coordinate], 27700); 

1

Official designated Street Name

2

Street Description

3

Numbered Street

4

Unofficial Street Description

9

Description used for LLPG Access

SELECT uprn, COUNT(uprn) AS NumOccurrences FROM addressbase_plus
GROUP BY uprn
HAVING ( COUNT(uprn) > 1 );
DELETE FROM addressbaseplus WHERE uprn IN (SELECT uprn FROM addressbaseplus_cou WHERE change_type != 'I');
INSERT INTO addressbaseplus SELECT * FROM addressbaseplus _cou WHERE change_type != 'D';
CREATE TABLE addressbaseplus_archive AS SELECT * FROM addressbaseplus
WHERE uprn IN (SELECT uprn FROM addressbaseplus_cou WHERE change_type != 'I');
DELETE FROM addressbaseplus
WHERE uprn IN (SELECT uprn FROM addressbaseplus_cou WHERE change_type!= 'I');
INSERT INTO addressbaseplus SELECT * FROM addressbaseplus_cou WHERE change_type != 'D';

AddressBase Lightning Talk

A helpful introductory article hosted on our More than Maps platform providing additional information and context about using AddressBase data.

AddressBase Fundamentals

The AddressBase Fundamentals pages provide an overview of the 'family' of AddressBase products, covering key elements of design for AddressBase products.

Getting Started Guide

The getting started guide provides instructions for using three AddressBase products in different software applications. Users with limited technical knowledge will be able to follow this guide.

Technical Specification

The technical specification provides detailed technical information about AddressBase. It is targeted at technical users and software developers.

Downloads

The downloads page provides links and resources to support the application of AddressBase within your environment.

Cover
Cover
Cover
Cover
Cover

OS Emergency Services Gazetteer

A new gazetteer which contains the locations of names, places and objects to support use cases related to the Protection of Life.

OS Multi-modal Routing Network

A new routable network product which integrates and connects OS road network and routing information, path network and rail network to create a multi-modal routing network.

Cover
Cover

AddressBase

Access to a current view of all Royal Mail Postcode Address File (PAF) addresses with additional location-based data featuring residential or commercial classifications.

AddressBase Core

Access to over 33 million addresses sourced from Local Authority data and supplied with a Unique Property Reference Number (UPRN) and property-level coordinates.

AddressBase Plus

Access to over 37 million postal and non-postal addresses sourced from Local Authorities, Ordnance Survey and Royal Mail for England, Wales and Scotland.

AddressBase Plus Islands

An addressing gazetteer offering full lifecycle information of a property for Northern Ireland, Isle of Man and the Channel Islands.

AddressBase Premium

Provides the most detailed view available of an address and its lifecycle from creation through to retirement in England, Wales and Scotland.

AddressBase Premium Islands

Provides the most detailed view of an address and its lifecycle for Northern Ireland, Channel Islands and the Isle of Man.

Boundary-Line

An open dataset that represents every administrative and electoral boundary and their names for England, Scotland and Wales.

Code-Point

A postcode locator that locates over 1.7 million postcode units in Great Britain and Northern Ireland – providing information about delivery points, positional quality, type and district codes amongst other data points.

Code-Point Open

An open dataset of all 1.7 million postcode units in Great Britain.

Code-Point with Polygons

A dataset providing the notional extent of every postcode in Great Britain for visualisation and analysis at a national scale.

OS Emergency Services Gazetteer (OS ESG)

Provides a national, consistent, and maintained view of the locations of names, places and objects in Great Britain to support the Emergency Services.

OS Open Built Up Areas

Provides a dataset representing Built Up Areas of Great Britain designed to underpin statistical analysis and contribute to policy enablement across the public sector.

OS Open Names

A comprehensive open dataset of place names, road numbers and postcodes for Great Britain.

Points of Interest

Provides a comprehensive location-based directory of all public and privately owned businesses, educational institutions and leisure services in Great Britain.

Cover
Cover
Cover
Cover
Cover
Cover
Cover
Cover
Cover
Cover
Cover
Cover
Cover
Cover
Representation of AddressBase data showing address data as red dots against a background map
The number of Postcode Address File (PAF) matched records in AddressBase by epoch. The number of PAF matched records in AddressBase has increased steadily over time, from 30 353 039 in Epoch 102 to 30 689 609 in Epoch 114.
The number of Postcode Address File (PAF) matched records in AddressBase by epoch. The number of PAF matched records in AddressBase has increased steadily over time, from 30 353 039 in Epoch 102 to 30 659 595 in Epoch 113.
Graph showing the number of Postcode Address File (PAF) matched records in AddressBase by epoch
BLPU State Code Enumeration
BLPU State Code Enumeration values and descriptions.
POF matched in addressbase chart showing epoch 102 to 111 on the bottom axis with figures steadily rising from 30,353,039 to 30,597,448
A graph showing the number of Postcode Address File (PAF) matched records in AddressBase by epoch starting from 30,353,039 in Epoch 102 and rising linearly to 30,726,641 in epoch 115.
Graph showing the number of Postcode Address File (PAF) matched records in AddressBase by epoch
ArcGIS Pro Select a folder dialog
ArcGIS Pro Select a folder dialog
ArcGIS Pro Create a New Project dialog
ArcGIS Pro Create a New Project dialog
ArcGIS Pro UI showing backdrop map
ArcGIS Pro UI showing backdrop map
ArcGIS Pro UI showing File Geodatabase Catalog pane
ArcGIS Pro UI showing File Geodatabase Catalog pane
ArcGIS Pro UI showing Geoprocessing window
ArcGIS Pro UI showing Geoprocessing window
ArcGIS Pro Input Rows dialog
ArcGIS Pro Input Rows dialog
ArcGIS Pro UI showing Geoprocessing window
ArcGIS Pro UI showing Geoprocessing window
ArcGIS Pro UI showing new table in Geoprocessing window
ArcGIS Pro UI showing new table in Geoprocessing window
ArcGIS Pro UI showing Contents pane
ArcGIS Pro UI showing Contents pane
ArcGIS Pro UI showing Geoprocessing window showing XY Table To Point parameters
ArcGIS Pro UI showing Geoprocessing window showing XY Table To Point parameters
ArcGIS Pro UI showing address data on the backdrop map
QGIS Options | CRS dialog
QGIS Options | CRS dialog
SQL Server Database Properties dialog
SQL Server Database Properties dialog
High-level COU implementation model
High-level COU implementation model
High-level COU implementation model on how to create archive tables and apply a COU
High-level COU implementation model on how to create archive tables and apply a COU
LogoAddressBase | Data Products | Ordnance SurveyOrdnance Survey

Supply and update

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.

Non-geographic chunks (unzipped)

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)

Non-geographic chunks (zipped)

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)

Geographic chunks (unzipped)

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)

Geographic chunks (zipped)

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)

COU Supply

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.

Non-geographic chunked COU

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.

Geographic chunked COU (tile-based)

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.

Archiving

When users are deleting, inserting or updating features, it is up to the user to consider their archiving requirements. If deleted records are important to your business requirements, you must take appropriate action to archive previous records.

contact Ordnance Survey.
AddressBase technical specification
AddressBase Plus technical specification
AddressBase Plus Islands technical specification
https://github.com/OrdnanceSurvey/AddressBase/tree/master/Loading_Scripts/PostgreSQL.
data supply page
https://github.com/OrdnanceSurvey/AddressBase/tree/master/Loading_Scripts/Oracle.
AddressBase technical specification
AddressBase Plus technical specification
AddressBase Plus Islands technical specification
https://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_ReadersWriters/gml/gml.htm
Merging multiple CSV files
Preparing the CSV data
Preparing the CSV data
Preparing the CSV data
Preparing the CSV data
Preparing the CSV data
Preparing the CSV data
Preparing the CSV data
Preparing the CSV data
Preparing the CSV data
Preparing the CSV data

Addressing and Location

Addressing and location products provide authoritative and accurate address, property and land data, with comprehensive location-based directories for users to draw from.

Contextual or Derived Mapping

Contextual or derived mapping products make OS data more accessible, customisable and easier to use for use for web, mobile and desktop applications.

Networks

Network products provide detailed and accurate network datasets for highways, roads, paths and waterways.

Topography

Topography products allow users to visualise geographic data to make clearer location-based decisions about assets, risks and services.

Identifiers

Identifier products provide a dataset of unique identifiers for a wide range of landscapes and built environment features for projects that require greater data connectivity.

Height and Imagery

Height products provide digital terrain models (DTMs) to assist users in evaluating the landscapes of Great Britain.

Cover
Cover
Cover
Cover
Cover
Cover

Data formats

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

CSV

The CSV supply of AddressBase means:

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

  • 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.

GML

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:

Prefix
Namespace Identifier
Definition available at

gml

xsi

xlink

Features

Each feature within the AddressBaseSupplySet:FeatureCollection is encapsulated in the following member element according to its feature type:

Member Element
Feature Type

<abpl:addressMember>

Address

The UPRN of the feature is provided in the XML attribute of the gml:id

<abpl:addressMember>
<abpl:Address gml:id=”uk.geoplace.uprn.1000011535314”>
………………..
</abpl:Addrress>
</abpl:addressMember>

Envelope

In the GML supply you can determine the extent of your supply by the <gml: Envelope>. For example:

<gml:boundedBy>
<gml:Envelope srsName=”urn:ogc:def:crs:EPSG::27700”>
<gml:lowerCorner>82643.6 5333.6</gml:lowerCorner>
<gml:upperCorner>655989 657599.5</gml:upperCorner>
</gml:Envelope>
</gml:boundedBy>

Searching for addresses

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.

Free text search

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:

Find address
Results

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

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.

Structured component search

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).

Results

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...

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?

The search operation

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.

Generating a search query from structured user input

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:

Search Box
Mapped Delivery Point fields
Mapped geographic fields

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

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:

  1. 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

  2. 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.

Structuring the query for a structured address search

The basic rules to adhere to when generating a search query from structured input are as follows:

  1. Ignore any search boxes that are not filled in with values.

  2. 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:

SELECT dp.UPRN, GetFormattedAddress(dp.*) FROM abp dp

WHERE (dp.thoroughfare = streetsearchtext OR dp.dependent_thoroughfare = streetsearchtext) AND (dp.dependent_locality = localitysearchtext OR dp.double_dependent_locality = localitysearchtext) AND (dp.dependent_locality = townsearchtext OR dp.post_town = townsearchtext)

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.

SELECT UPRN, GetFormattedAddress(*) FROM abp

WHERE (thoroughfare = streetsearchtext OR dependent_thoroughfare = streetsearchtext) AND (dependent_locality = localitysearchtext OR double_dependent_locality = localitysearchtext) AND (dependent_locality = townsearchtext OR post_town = townsearchtext)

UNION

SELECT uprn, GetFormattedAddress(*) FROM abp WHERE (.street_name = streetsearchtext OR .pao_text = streetsearchtext) AND
(.locality = localitysearchtext OR .town = localitysearchtext OR .street_name = localitysearchtext) AND (.town = townsearchtext OR .locality = townsearchtext)

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.

Supporting case-insensitive queries and partial matches

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:

post_town LIKE townsearchtext -- Case insensitive search in some databases ;
post_town LIKE (townsearchtext || ‘%’) -- Matches post towns that start with the search text ;
post_town LIKE (‘%’ || townsearchtext || ‘%’) -- Matches post towns that contain the search text;

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):

UPPER(post_town) = UPPER(townsearchtext) -- Case insensitive equality;

Finally, to combine all of the approaches, the following would work for maximum flexibility:

UPPER(post_town) LIKE (‘%’ || UPPER(townsearchtext) || ‘%’)

Generating a search query from unstructured user input

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.

Creating a search index for addresses

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:

UPRN
Address Text
Statuses (multiple fields)

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

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.

Structuring the query for an unstructured address search

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:

SELECT UPRN, AddressText FROM AddressSearchIndex 
WHERE
AddressText LIKE ‘%4%’ AND 
AddressText LIKE ‘%HIGH%’ AND 
AddressText LIKE ‘%STREET%’ AND 
AddressText LIKE ‘%WESTVILLE%’ AND 
AddressText LIKE ‘%WV17%’;

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:

Address text
Statuses (multiple fields)

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

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.

Summary

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:

  1. 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.

  2. 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.

  3. With a structured search interface, the addresses can be queried directly by mapping the various address fields to the text boxes supplied.

  4. 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.

  5. It is possible to filter results by status in AddressBase Plus (for example, postal or non-postal).

  6. Any search function should search all forms of an address (both Geographic and Delivery Point Addresses).

  7. Careful consideration should be given to the use of ‘fuzzy’ search algorithms (such as using wildcard or sound-alike searches).

Creating a single-line or multi-line address

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:

DEPARTMENT_NAME

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

Background

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:

ROSE COTTAGE

5 MAIN STREET

ADDRESSVILLE LONDON

SE99 9EX

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.

Delivery Point Address (PAF Address)

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.

Delivery Point Address Component
Type

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

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.

Delivery Point Address Component
Example

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

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:

Delivery Point Address Component
Data Content
Formatted output

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

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.

Delivery Point Address Component
Data content
Formatted output

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

Building a single-line Delivery Point Address

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.

Building a multi-line Delivery Point Address

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.

Geographic Address (Local Authority Address)

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:

Constructing a single address label from the Geographic Address fields

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.

Geographic Address Component
Type

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

*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.

Rendering SAOs and PAOs

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.

Attribute
Example 1
Example 2
Example 3
Example 4

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

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.

Attribute
Example 1
Example 2
Example 3
Example 4

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>

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.

Street description, town, locality and administrative area names

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.

Administrative area not included
vs
Administrative area included (BURY)

34, CROW LANE, RAMSBOTTOM, BL0 9BR

34, CROW LANE, RAMSBOTTOM, BURY, BL0 9BR

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.

Geographic Address Component
Example

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

*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.

Delivery Point Address Component
Data content
Formatted output

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

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.

Delivery Point Address Component
Data content
Formatted output

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

Building a single-line Geographic Address

  • 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.

Building a multi-line Geographic Address

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:

  1. 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

  2. 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).

    PAO_text only

    PAO_text and PAO number or range

    ROSE COTTAGE, MAIN STREET

    ROSE COTTAGE, 11A MAIN STREET

  3. 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).

    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

  4. 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.

    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

  5. If there is a SAO_text value, it should always appear on its own line.

    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

  6. If there is an Organisation Name, it should always appear alone as the top line of the address.

    Organisation Name along with all PAO + SAO fields

    COTTAGE INDUSTRY LTD, THE ANNEXE,

    1A ROSE COURT,

    11A MAIN STREET

  7. 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.

    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

  8. 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.

    Administrative Area name included

    [first part of address, formatted as described above] MAIN STREET,

    WINDSOR,

    ROYAL BOROUGH OF WINDSOR AND MAIDENHEAD

  9. Finally, the Postcode Locator should be inserted on the final line of the address.

    With Postcode_Locator on final line

    [first part of address, formatted as described above] HIGH STREET,

    MILTON, ML99 0WW

Creating mailing lists

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:

  1. Use Delivery Point Addresses whenever they are available, and when they are not, use a Geographic Address.

  2. 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.

Other filters

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.

AddressBase structure

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

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

Model overview CSV

AddressBase CSV

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.

UML model of AddressBase in CSV format

Model overview GML

AddressBase GML

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.

UML model of AddressBase in GML format

Feature types

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

AddressBase attribute information

Name and Definition

The name of the attribute and what it is describing.

Condition

A condition associated with this attribute (optional).

Attribute Type

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

Multiplicity

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

  • ‘1’ – there must be a value.

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

AddressBase feature types

CSV to GML mapping

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.

Code list and enumerations

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

AddressBase code list and enumerations

AddressBase Supply Set

This feature is formally known as the GML feature collection and is used to define a collection of features.

Feature type attributes

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.

Query time

Time the data was extracted from the database.

  • Attribute Name: queryTime (GML), Not provided (CSV)

  • Data Type: DateTime (GML)

  • Multiplicity: [1]

  • Size: 1

Query change since date

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

AddressBase local custodian codes

The following page details the current local custodian codes of all local custodians contributing to the AddressBase, AddressBase Core, AddressBase Plus and AddressBase Premium products.

The local custodian codes listed in the zip file and table below are applicable to the AddressBase, AddressBase Core, AddressBase Plus and AddressBase Premium products.

Local custodian codes download

Local custodian code data is available to download in CSV format in the following zip file:

Local custodian codes table

Appending a header file to the CSV

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.

It imports the GML 3.2.1 schemas which rely on XML as defined by W3C at:

Built into XML –

Xlink –

Information about Unicode and UTF-8, the character encoding we have chosen, is available on the Unicode Consortium website:

See for specific GML examples.

Example Search UI with text boxes for each address component
Diagram showing typical processing steps when search for an address

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:

High level data model representing the address feature (CSV).
UML model showing AddressBase feature types, enumerations and code lists for the CSV supply.
High level data model representing the address relationships (GML).
UML model showing AddressBase feature types, enumerations and code lists for the GML supply.

CSV
GML

This is not supplied as part of the CSV supply. Please see and for more information.

They are not applicable to the AddressBase Plus Islands or AddressBase Premium Islands products; local custodian codes for these two islands products are available from the .

Local Custodian Code
Local Custodian Name
Local Custodian Type
Submits Address data
Submits Street data
Local Custodian Code
Local Custodian Name
Local Custodian Type
Submits Address data
Submits Street data
Local Custodian Code
Local Custodian Name
Local Custodian Type
Submits Address data
Submits Street data
Local Custodian Code
Local Custodian Name
Local Custodian Type
Submits Address data
Submits Street data
Local Custodian Code
Local Custodian Name
Local Custodian Type
Submits Address data
Submits Street data
Local Custodian Code
Local Custodian Name
Local Custodian Type
Submits Address data
Submits Street data
http://www.w3.org.
https://portal.ogc.org/files/?artifact_id=20509.
http://www.w3.org/XML/1998/namespace.html.
http://www.unicode.org/.
the example records page
https://github.com/OrdnanceSurvey/AddressBase/tree/master/SQL,
AddressBase technical specification
AddressBase Plus technical specification
AddressBase Plus Islands technical specification
on our GitHub repository
Creating a single-line or multi-line address
Delivery Point Address
Geographic Address
Constructing a single address label from the Geographic Address fields

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

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

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

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

N

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

Example Search UI with text boxes for each address component
Diagram showing typical processing steps when search for an address
High level data model representing the address feature (CSV).
UML model showing AddressBase feature types, enumerations and code lists for the CSV supply.
High level data model representing the address relationships (GML).
UML model showing AddressBase feature types, enumerations and code lists for the GML supply.
4KB
addressbase-local-custodian-codes.zip
archive
UML diagram providing details of the code list and enumerations in the AddressBase product
UML diagram providing details of the code list and enumerations in the AddressBase product.

CSV

Original feature – AddressBase CSV

100100077917,"osgb1000002283010753",4201646,"","", "","","",166,"","LLANDAFF
ROAD","CARDIFF","","","CF11 9PX","S",316348.00,177163.00, 50.7268511, -3.5366289, 1,"E","I",2001-05- 10,2001-05-10,2007-08-29,"R"

COU feature – AddressBase CSV

100100077917,"osgb1000002283010753",4201646,"","", "","","",166,"","LLANDAFF
ROAD","CARDIFF","","","CF11 9PX","S",316348.00,177163.00, 50.7268511,- 3.5366289, 2,"E","U",2001-05- 10,2001-05-10,2010-06-04,"R"

Example 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.

CSV supply

Original feature – AddressBase CSV

100100077917,"osgb1000002283010753",4201646,"","", "","","",166,"","LLANDAFF
ROAD","CARDIFF","","","CF11 9PX","S",316348.00,177163.00, 50.7268511, -3.5366289, 1,"E","I",2001-05- 10,2001-05-10,2007-08-29,"R"

COU feature – AddressBase CSV

Changed fields are highlighted in red. 100100077917,"osgb1000002283010753",4201646,"","", "","","",166,"","LLANDAFF
ROAD","CARDIFF","","","CF11 9PX","S",316348.00,177163.00, 50.7268511,- 3.5366289, 2,"E","U",2001-05- 10,2001-05-10,2010-06-04,"R"

GML supply

Original feature – AddressBase GML

Please note how not all attributes are provided where the field is null.

<abs:addressMember>
  <abs:Address gml:id="uk.addressbase.uprn.100040205844">
    <abs:uprn>100040205844</abs:uprn>
    <abs:osAddressTOID>osgb1000002274362298</abs:osAddressTOID>
    <abs:udprn>8782432</abs:udprn>
    <abs:subBuildingName xml:lang="en">FLAT C</abs:subBuildingName>
    <abs:buildingName xml:lang="en">PEMBROKE HOUSE</abs:buildingName>
    <abs:buildingNumber>4</abs:buildingNumber>
    <abs:thoroughfare xml:lang="en">BYSTOCK TERRACE</abs:thoroughfare>
    <abs:postTown xml:lang="en">EXETER</abs:postTown>
    <abs:postcode>EX4 4HY</abs:postcode>
    <abs:postcodeType>S</abs:postcodeType>
    <abs:position>
      <gml:Point srsName="urn:ogc:def:crs:EPSG::27700" gml:id="uk.addressbase.uprn.p.100040205844">
        <gml:pos>291640.00 93040.00</gml:pos>
      </gml:Point>
    </abs:position>
    <abs:positionLatLong>
      <gml:Point srsName="urn:ogc:def:crs:EPSG::4258" gml:id="uk.addressbase.uprn.pl.100040205844">
        <gml:pos>50.7268511 -3.5366289</gml:pos>
      </gml:Point>
    </abs:positionLatLong>
    <abs:rpc>1</abs:rpc>
    <abs:country>E</abs:country>
    <abs:changeType>I</abs:changeType>
    <abs:laStartDate>2001-04-04</abs:laStartDate>
    <abs:rmStartDate>2001-04-04</abs:rmStartDate>
    <abs:lastUpdateDate>2001-04-04</abs:lastUpdateDate>
    <abs:class>R</abs:class>
  </abs:Address>
</abs:addressMember>

COU feature – AddressBase GML

Changed fields are highlighted in red.
<abs:addressMember>
  <abs:Address gml:id="uk.addressbase.uprn.100040205844">
    <abs:uprn>100040205844</abs:uprn>
    <abs:osAddressTOID>osgb1000002274362298</abs:osAddressTOID>
    <abs:udprn>8782432</abs:udprn>
    <abs:subBuildingName xml:lang="en">FLAT C</abs:subBuildingName>
    <abs:buildingName xml:lang="en">PEMBROKE HOUSE</abs:buildingName>
    <abs:buildingNumber>4</abs:buildingNumber>
    <abs:thoroughfare xml:lang="en">BYSTOCK TERRACE</abs:thoroughfare>
    <abs:postTown xml:lang="en">EXETER</abs:postTown>
    <abs:postcode>EX4 4HY</abs:postcode>
    <abs:postcodeType>S</abs:postcodeType>
    <abs:position>
      <gml:Point srsName="urn:ogc:def:crs:EPSG::27700" gml:id="uk.addressbase.uprn.p.100040205844">
        <gml:pos>291640.00 93040.00</gml:pos>
      </gml:Point>
    </abs:position>
    <abs:positionLatLong>
      <gml:Point srsName="urn:ogc:def:crs:EPSG::4258" gml:id="uk.addressbase.uprn.pl.100040205844">
        <gml:pos>50.7268511 -3.5366289</gml:pos>
      </gml:Point>
    </abs:positionLatLong>
    <abs:rpc>2</abs:rpc>
    <abs:country>E</abs:country>
    <abs:changeType>U</abs:changeType>
    <abs:laStartDate>2001-04-04</abs:laStartDate>
    <abs:rmStartDate>2001-04-04</abs:rmStartDate>
    <abs:lastUpdateDate>2010-06-04</abs:lastUpdateDate>
    <abs:class>R</abs:class>
  </abs:Address>
</abs:addressMember>

GML

Original feature – AddressBase GML

Please note how not all attributes are provided where the field is null.

<abs:addressMember>
  <abs:Address gml:id="uk.addressbase.uprn.100040205844">
    <abs:uprn>100040205844</abs:uprn>
    <abs:osAddressTOID>osgb1000002274362298</abs:osAddressTOID>
    <abs:udprn>8782432</abs:udprn>
    <abs:subBuildingName xml:lang="en">FLAT C</abs:subBuildingName>
    <abs:buildingName xml:lang="en">PEMBROKE HOUSE</abs:buildingName>
    <abs:buildingNumber>4</abs:buildingNumber>
    <abs:thoroughfare xml:lang="en">BYSTOCK TERRACE</abs:thoroughfare>
    <abs:postTown xml:lang="en">EXETER</abs:postTown>
    <abs:postcode>EX4 4HY</abs:postcode>
    <abs:postcodeType>S</abs:postcodeType>
    <abs:position>
      <gml:Point srsName="urn:ogc:def:crs:EPSG::27700" gml:id="uk.addressbase.uprn.p.100040205844">
        <gml:pos>291640.00 93040.00</gml:pos>
      </gml:Point>
    </abs:position>
    <abs:positionLatLong>
      <gml:Point srsName="urn:ogc:def:crs:EPSG::4258" gml:id="uk.addressbase.uprn.pl.100040205844">
        <gml:pos>50.7268511 -3.5366289</gml:pos>
      </gml:Point>
    </abs:positionLatLong>
    <abs:rpc>1</abs:rpc>
    <abs:country>E</abs:country>
    <abs:changeType>I</abs:changeType>
    <abs:laStartDate>2001-04-04</abs:laStartDate>
    <abs:rmStartDate>2001-04-04</abs:rmStartDate>
    <abs:lastUpdateDate>2001-04-04</abs:lastUpdateDate>
    <abs:class>R</abs:class>
  </abs:Address>
</abs:addressMember>

COU feature – AddressBase GML

Changed fields are highlighted in red.
<abs:addressMember>
  <abs:Address gml:id="uk.addressbase.uprn.100040205844">
    <abs:uprn>100040205844</abs:uprn>
    <abs:osAddressTOID>osgb1000002274362298</abs:osAddressTOID>
    <abs:udprn>8782432</abs:udprn>
    <abs:subBuildingName xml:lang="en">FLAT C</abs:subBuildingName>
    <abs:buildingName xml:lang="en">PEMBROKE HOUSE</abs:buildingName>
    <abs:buildingNumber>4</abs:buildingNumber>
    <abs:thoroughfare xml:lang="en">BYSTOCK TERRACE</abs:thoroughfare>
    <abs:postTown xml:lang="en">EXETER</abs:postTown>
    <abs:postcode>EX4 4HY</abs:postcode>
    <abs:postcodeType>S</abs:postcodeType>
    <abs:position>
      <gml:Point srsName="urn:ogc:def:crs:EPSG::27700" gml:id="uk.addressbase.uprn.p.100040205844">
        <gml:pos>291640.00 93040.00</gml:pos>
      </gml:Point>
    </abs:position>
    <abs:positionLatLong>
      <gml:Point srsName="urn:ogc:def:crs:EPSG::4258" gml:id="uk.addressbase.uprn.pl.100040205844">
        <gml:pos>50.7268511 -3.5366289</gml:pos>
      </gml:Point>
    </abs:positionLatLong>
    <abs:rpc>2</abs:rpc>
    <abs:country>E</abs:country>
    <abs:changeType>U</abs:changeType>
    <abs:laStartDate>2001-04-04</abs:laStartDate>
    <abs:rmStartDate>2001-04-04</abs:rmStartDate>
    <abs:lastUpdateDate>2010-06-04</abs:lastUpdateDate>
    <abs:class>R</abs:class>
  </abs:Address>
</abs:addressMember>
http://www.opengis.net/gml
http://schemas.opengis.net/gml/3.2.1/gml.xsd
http://www.w3.org/2001/XMLSchema-
instance
http://www.w3.org/TR/xmlschema-1/
http://www.w3.org/1999/xlink
http://www.w3.org/1999/xlink.xsd
Address
AddressBase Supply Set
CountryCode
RPCCode
ChangeTypeCode
PostcodeTypeCode
AddressBase Islands local custodian codes page
Model Overview CSV
Model Overview GML

Address

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.

Feature type attributes

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.

UPRN

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

TOID:

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

UDPRN

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

Organisation name

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

Department name

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

Po box number

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

Sub building name

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

Building name

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

Building number

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

Thoroughfare

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

Post town

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

Double dependent locality

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

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

Postcode

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

Postcode type

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

Position

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

Position lat long

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

RPC

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

Country

The country in which a record can be found.

  • Attribute Name: country (GML), COUNTRY (CSV)

  • Multiplicity: [1]

  • Size: 1

Change type

Type of Record Change – please see Section 4 for more information.

  • Attribute Name: changeType (GML), CHANGE_TYPE (CSV)

  • Multiplicity: [1]

  • Size: 1

LA start date

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

RM start date

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

Last update date

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]

Class

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

AddressBase Technical Specification

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:

AddressBase Downloads

Classification scheme

Header files

The header files for AddressBase are available for download as a CSV file:

361B
addressbase-header (1).csv

Local custodian codes

AddressBase Known Data Issues

This page provides the details of known data issues in the AddressBase product. Once resolved, details of a known data issue will be held on the page until the next release of the product.

Live known data issues

There are no live known data issues for AddressBase at this time.

15 April 2025

This release note provides information about the release of the AddressBase Core product on 15 April 2025.

Record counts

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.

Product supply comparison

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

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

Changed records

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

Source data currency

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

Known data issues

Release Notes

Release notes listed here provide information about the current release of AddressBase Core and the previous nine releases.

This release note provides information about the 07 May 2025 release of AddressBase Core.

This release note provides information about the 29 April 2025 release of AddressBase Core.

This release note provides information about the 23 April 2025 release of AddressBase Core.

This release note provides information about the 15 April 2025 release of AddressBase Core.

This release note provides information about the 08 April 2025 release of AddressBase Core.

This release note provides information about the 01 April 2025 release of AddressBase Core.

This release note provides information about the 25 March 2025 release of AddressBase Core.

This release note provides information about the 18 March 2025 release of AddressBase Core.

This release note provides information about the 11 March 2025 release of AddressBase Core.

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

23 April 2025

This release note provides information about the release of the AddressBase Core product on 23 April 2025.

Record counts

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.

Product supply comparison

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

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

Changed records

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

Source data currency

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

Known data issues

AddressBase Core

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.

Approved addressing records

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).

Property classification

Through property classification attributes, you can quickly understand, locate and perform analysis on the type of addresses you want to interact with.

Authoritative data

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.

Weekly updates

AddressBase Core is released weekly, keeping you more up to date with changes.

Property classification

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.

Easy cross-referencing

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, GeoPackage

  • 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

Advantage of AddressBase Core over other AddressBase products

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 have been demolished

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 epoch correspondence

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.

Coverage of AddressBase Core

AddressBase Core covers Great Britain only, i.e. England, Wales and Scotland. It does not include Northern Ireland and the Channel Islands.

Data from Royal Mail’s PAF

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.

How to get this product

Sample data

Download AddressBase Core sample data

Visualise AddressBase Core sample data online

What's next?

To access documentation and resources relating to this product, please refer to the following:

New users should start with the Overview to gain high-level insight into the product. The Getting Started Guide will help you to begin using product data in different software systems. The Technical Specification contains detailed technical insights.

07 May 2025

This release note provides information about the release of the AddressBase Core product on 07 May 2025.

Record counts

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.

Product supply comparison

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

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

Changed records

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

Source data currency

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

Known data issues

29 April 2025

This release note provides information about the release of the AddressBase Core product on 29 April 2025.

Record counts

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.

Product supply comparison

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

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

Changed records

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

Source data currency

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

Known data issues

18 March 2025

This release note provides information about the release of the AddressBase Core product on 18 March 2025.

Record counts

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.

Product supply comparison

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

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

Changed records

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

Source data currency

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

11 March 2025

This release note provides information about the release of the AddressBase Core product on 11 March 2025.

Record counts

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.

Product supply comparison

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

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

Changed records

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

Source data currency

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

04 March 2025

This release note provides information about the release of the AddressBase Core product on 04 March 2025.

Record counts

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.

Product supply comparison

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

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

Changed records

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

Source data currency

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

25 March 2025

This release note provides information about the release of the AddressBase Core product on 25 March 2025.

Record counts

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.

Product supply comparison

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

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

Changed records

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

Source data currency

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

01 April 2025

This release note provides information about the release of the AddressBase Core product on 01 April 2025.

Record counts

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.

Product supply comparison

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

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

Changed records

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

Source data currency

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

Known data issues

AddressBase Header files

Code List Name:

Code List Name:

Code List Name:

Code List Name:

All AddressBase products include the and are based on same .

Please see the for additional information that applies across all AddressBase products.

The product classification scheme is available to download as a zip file (in CSV and .xlsx formats) from the in the AddressBase Fundamentals section.

Local custodian codes for the product are available to download as a zip file (in CSV format) from the in the AddressBase Fundamentals section.

Product
Full Supply Record Count
Change-Only Update Record Count
Product
MGBS Full Count
National 5km Tiled Supply
Difference
Change Type
Count
Data Source
Date

Details of data issues for AddressBase Core will be communicated on the . This page will provide details of their impacts and updates on the expected time frame for their resolution.

Product
Full Supply Record Count
Change-Only Update Record Count
Product
MGBS Full Count
National 5km Tiled Supply
Difference
Change Type
Count
Data Source
Date

Details of data issues for AddressBase Core will be communicated on the . This page will provide details of their impacts and updates on the expected time frame for their resolution.

Access to this product is free for PSGA (Public Sector Geospatial Agreement) Members. You can .

The has advice on how to get the product for businesses, developers, Partners and PSGA Members (i.e. government and the public sector).

Alternatively, you can try out the full product by applying for .

You can download sample data for the product for free from the . The sample data are available in CSV format and cover one area (Exeter).

Product
Full Supply Record Count
Change-Only Update Record Count
Product
MGBS Full Count
National 5km Tiled Supply
Difference
Change Type
Count
Data Source
Date

Details of data issues for AddressBase Core will be communicated on the . This page will provide details of the impacts of any data issues, plus updates on the expected time frame for resolution.

Product
Full Supply Record Count
Change-Only Update Record Count
Product
MGBS Full Count
National 5km Tiled Supply
Difference
Change Type
Count
Data Source
Date

Details of data issues for AddressBase Core will be communicated on the . This page will provide details of the impacts of any data issues, plus updates on the expected time frame for resolution.

Product
Full Supply Record Count
Change-Only Update Record Count
Product
MGBS Full Count
National 5km Tiled Supply
Difference
Change Type
Count
Data Source
Date
Product
Full Supply Record Count
Change-Only Update Record Count
Product
MGBS Full Count
National 5km Tiled Supply
Difference
Change Type
Count
Data Source
Date
Product
Full Supply Record Count
Change-Only Update Record Count
Product
MGBS Full Count
National 5km Tiled Supply
Difference
Change Type
Count
Data Source
Date
Product
Full Supply Record Count
Change-Only Update Record Count
Product
MGBS Full Count
National 5km Tiled Supply
Difference
Change Type
Count
Data Source
Date
Product
Full Supply Record Count
Change-Only Update Record Count
Product
MGBS Full Count
National 5km Tiled Supply
Difference
Change Type
Count
Data Source
Date

Details of data issues for AddressBase Core will be communicated on the . This page will provide details of their impacts and updates on the expected time frame for their resolution.

PostcodeTypeCode
RPCCode
CountryCode
ChangeTypeCode
Data formats
Supply and update
AddressBase Premium structure
Feature types
Code list and enumerations
CSV to GML mapping
Example records
Unique Property Reference Number (UPRN)
coordinate reference systems
AddressBase Fundamentals section
classification scheme page
AddressBase local custodian codes page

AddressBase Core

34 623 64

40 514

AddressBase Core

34 623 642

34 623 633

9

Inserts

6 693

Updates

29 956

Deletes

3 865

COU populated 5km tile count

3 785

Royal Mail Postcode Address File (PAF)

11 April 2025

National Land and Property Gazetteer

11 April 2025

One Scotland Gazetteer

31 March 2025

OS MasterMap Topography Layer

27 February 2025

AddressBase Core

34 626 638

34 854

AddressBase Core

34 626 638

34 626 629

9

Inserts

5 074

Updates

27 702

Deletes

2 078

COU populated 5km tile count

3 211

Royal Mail Postcode Address File (PAF)

17 April 2025

National Land and Property Gazetteer

17 April 2025

One Scotland Gazetteer

31 March 2025

OS MasterMap Topography Layer

27 February 2025

AddressBase Core

34 633 600

71 927

AddressBase Core

34 633 600

34 633 591

9

Inserts

7 682

Updates

60 920

Deletes

3 325

COU populated 5km tile count

4 138

Royal Mail Postcode Address File (PAF)

02 May 2025

National Land and Property Gazetteer

02 May 2025

One Scotland Gazetteer

21 April 2025

OS MasterMap Topography Layer

10 April 2025

AddressBase Core

34 629 243

35 585

AddressBase Core

34 629 243

34 629 234

9

Inserts

4 902

Updates

28 386

Deletes

2 297

COU populated 5km tile count

2 860

Royal Mail Postcode Address File (PAF)

25 April 2025

National Land and Property Gazetteer

25 April 2025

One Scotland Gazetteer

31 March 2025

OS MasterMap Topography Layer

27 February 2025

AddressBase Core

34 607 765

44 207

AddressBase Core

34 607 765

34 607 757

8

Inserts

8 166

Updates

33 546

Deletes

2 495

COU populated 5km tile count

3 130

Royal Mail Postcode Address File (PAF)

14 March 2025

National Land and Property Gazetteer

14 March 2025

One Scotland Gazetteer

10 March 2025

OS MasterMap Topography Layer

16 January 2025

AddressBase Core

34 602 094

40 895

AddressBase Core

34 602 094

34 602 086

8

Inserts

6 600

Updates

31 511

Deletes

2 784

COU populated 5km tile count

3 498

Royal Mail Postcode Address File (PAF)

07 March 2025

National Land and Property Gazetteer

07 March 2025

One Scotland Gazetteer

17 February 2025

OS MasterMap Topography Layer

16 January 2025

AddressBase Core

34 598 278

51 210

AddressBase Core

34 598 278

34 598 270

8

Inserts

7 172

Updates

40 730

Deletes

3 308

COU populated 5km tile count

3 752

Royal Mail Postcode Address File (PAF)

28 February 2025

National Land and Property Gazetteer

28 February 2025

One Scotland Gazetteer

17 February 2025

OS MasterMap Topography Layer

16 January 2025

AddressBase Core

34 613 292

87 717

AddressBase Core

34 613 292

34 613 284

8

Inserts

8 351

Updates

76 542

Deletes

2 824

COU populated 5km tile count

3 818

Royal Mail Postcode Address File (PAF)

21 March 2025

National Land and Property Gazetteer

21 March 2025

One Scotland Gazetteer

10 March 2025

OS MasterMap Topography Layer

27 February 2025

AddressBase Core

34 617 296

28 918

AddressBase Core

34 617 296

34 617 288

8

Inserts

5 619

Updates

21 684

Deletes

1 615

COU populated 5km tile count

2 801

Royal Mail Postcode Address File (PAF)

28 March 2025

National Land and Property Gazetteer

28 March 2025

One Scotland Gazetteer

10 March 2025

OS MasterMap Topography Layer

27 February 2025

Representation of AddressBase Core data showing several types of address classifications clustered in a single area
Representation of AddressBase Core data showing several types of address classifications.

Downloads

The downloads page provides links and resources to support the application of AddressBase Core within your environment.

Cover

AddressBase Core Lightning Talk

A helpful introductory article hosted on our More than Maps platform providing additional information and context about using AddressBase Core data.

Cover

Overview

The Overview introduces AddressBase Core, giving context for all users – highlighting key features, providing examples of potential uses, and listing details such as file sizes, supply formats, etc.

Cover

Getting Started Guide

The 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.

Cover

Technical Specification

The technical specification provides detailed technical information about AddressBase Core. It is targeted at technical users and software developers.

AddressBase Core Known Data Issues page
AddressBase Core – 07 May 2025 release note
AddressBase Core – 29 April 2025 release note
AddressBase Core – 23 April 2025 release note
AddressBase Core – 15 April 2025 release note
AddressBase Core – 08 April 2025 release note
AddressBase Core – 01 April 2025 release note
AddressBase Core – 25 March 2025 release note
AddressBase Core – 18 March 2025 release note
AddressBase Core – 11 March 2025 release note
AddressBase Core – 04 March 2025 release note
AddressBase Core Known Data Issues page
check if your organisation is a member of the PSGA on the OS website
AddressBase Core product page on the OS website
a Data Exploration license
OS Data Hub
AddressBase Core Known Data Issues page
AddressBase Core Known Data Issues page
AddressBase Core Known Data Issues page

Coordinate reference systems

Classification

The AddressBase product suite provides records of varying levels of classification and are based on classifications from the Local Authorities and OS. The varying levels of classification are as follows:

GeoPlace

Data capture and sources

The creation of AddressBase Core brings together the best parts of:

  • Local Government’s National Land and Property Gazetteer (NLPG)

  • The One Scotland Address Gazetteer (OSG)

  • Ordnance Survey-owned large-scale data and coordinates

  • Royal Mail Postcode Address File (PAF)

Address source

The address provided in AddressBase Core is captured by the Local Authority Street Naming and Numbering (SNN) custodian and Scottish Local Street Gazetteer (LSG) custodian, who allocate the official street name and building information. The SNN / LSG custodian has a statutory obligation to provide this information for all addresses within their administrative area. This information forms the legal authoritative representation of an address.

Elements of the provided address in AddressBase Core such as PO Box, Organisation, Post Town and Postcode are provided from Royal Mail PAF, where it has been matched to a local authority address.

AddressBase Core Overview

This overview introduces AddressBase Core, giving context for all users – highlighting key features, providing examples of potential uses, and listing details such as file sizes, supply formats, etc.

AddressBase Core is a simple and accessible addressing data product designed to remove the need for pre-processing and complexity. It provides Plug and Play access for addressing data and additional attribution in Great Britain.

AddressBase Core includes 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 secondary level classifications (detailing the use and type of an address) and a representative point code describing the positional quality of coordinates.

  • All approved addresses for where you can work, rest or play.

  • Each address is given a Unique Property Reference Number (UPRN) which will remain with that address throughout its lifecycle.

  • Property level coordinates.

  • Secondary level classifications for each property, for example, residential dwelling, commercial office.

  • Identifiers for other OS products and third party datasets, including the Royal Mail Postcode Address File (PAF), Unique Delivery Point Reference Number (UDPRN) and Office for National Statistics Governmental Statistical Service (GSS) codes.

  • Address data sourced from local authorities, which are legally responsible for the naming and numbering of all addresses in the UK.

  • Addresses complemented with Royal Mail PAF information such as Organisation name, Post Town and Postcode, where matched.

  • Single Line address – A concatenation of all provided address elements into a comma separated single attribute ready to be printed onto an envelope, loaded into a CRM or provided within an address look-up service.

AddressBase Core can be loaded into a database or directly into a GIS software package. It has been designed to make either of these processes as easy as possible, with the GeoPackage file format offering ‘drag and drop’ functionality for some software packages.

You can:

  • View addresses for approved properties across Great Britain, including the granular detail provided by the local authorities.

  • Determine the use of the address, for example, determine between commercial retail and commercial office addresses.

  • Load and display the address location in a GIS software package using the GeoPackage format, with no need for any pre-processing.

  • Display address information as either a single line address or split into individual elements, with no need for any pre-processing.

You can't:

  • Access lifecycle information for an address.

  • Determine the most granular level of information about an address, for example, distinguish detached and semi-detached residential dwellings.

Index

This overview includes the following sections:

Unique Property Reference Number (UPRN)

The UPRN acts as the primary key of the AddressBase Core product.

08 April 2025

This release note provides information about the release of the AddressBase Core product on 08 April 2025.

Record counts

Product
Full Supply Record Count
Change-Only Update Record Count

AddressBase Core

34 620 814

33 345

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.

Product supply comparison

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

Product
MGBS Full Count
National 5km Tiled Supply
Difference

AddressBase Core

34 620 814

34 620 806

8

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

Changed records

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

Change Type
Count

Inserts

5 812

Updates

25 239

Deletes

2 294

COU populated 5km tile count

3 093

Source data currency

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

Data Source
Date

Royal Mail Postcode Address File (PAF)

04 April 2025

National Land and Property Gazetteer

04 April 2025

One Scotland Gazetteer

31 March 2025

OS MasterMap Topography Layer

27 February 2025

Known data issues

AddressBase Core Getting Started Guide

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.

What you need?

  • 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.

Instructions

These instructions show you how to use AddressBase Core and include:

Downloading a dataset

This section of the getting started guide takes you through the process of downloading and extracting your AddressBase Core supply.

Data 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.

Backing up the data

Typical data volumes

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.

Downloading instructions

PSGA customers can download full supply and COU of AddressBase Core via our download service.

  1. If you have ordered your data from our online portal, you will be sent an email with a link to a download page.

  2. 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.

  3. 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.

  4. When you have placed an order for a product, the data will become available as a zipped data file.

Unzipping the data

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.

Currency, completeness and precision

Product supply

On this page you'll find product supply information for AddressBase Core, including available formats, the supply mechanism, coverage and currency.

Available formats

The AddressBase Core product is available as a Comma-Separated Value (CSV) file or GeoPackage (GPKG) via a URL download.

Comma-Separated Values (CSV) overview

GeoPackage overview

Supply and update

This product is updated weekly.

The primary supply mechanism of AddressBase Core will be a full Great Britain Set. A single file will be provided containing all records with headers already included (CSV) or the structure already defined (GeoPackage). This supply is known as a Managed Great Britain Set (MGBS).

All customers are also able to take a Full Supply or Change-only update (COU).

COU is a supply of features which have been created (inserted), changed (updated) or deleted in the product 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.

Please note, COUs are only available with the CSV file format.

Coverage

The coverage of the product is Great Britain (i.e. England, Scotland and Wales).

File sizes

AddressBase Core is provided as one file, regardless of format chosen. The file sizes for Great Britain are approximately:

  • CSV 2Gb

  • GeoPackage 12Gb

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 '' 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 '' 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 '' 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 '' 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 '' 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 '' 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 '' 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 '' 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 '' 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 '' 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 '' 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 '' 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 '' 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 '' 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 '' 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 '' 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 '' 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 '' 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 '' 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 '' 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 '' 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 '' 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 '' 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 '' 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 '' 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 '' 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 '' 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 '' 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 '' in the AddressBase Getting Started Guide.

The information supplied here is replicated in full on the page, alongside publication information for all of our other Premium and OpenData products.

In AddressBase Core, classification is given to Secondary Level where possible. You can therefore determine types of addresses, for example, different types of commercial addresses. Further details of the Classification Scheme for AddressBase products are available to view and download from the .

Additional information on the AddressBase product family, including a feature comparison of the AddressBase products is available in the within the Addressing and Location Portfolio.

An image of a map showing the following AddressBase Core classifications: ZW: Object of Interest/Place of Worship RD: Residential/Dwelling LD: Land/Development CR: Commercial/Retail CL: Commercial/Leisure

Link to other OS products such as and or third-party products such as Royal Mail PAF using the Unique Delivery Point Reference Number (UDRPN) or Office for National Statistics using the Government Statistical Service (GSS) codes.

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 '' in the AddressBase Getting Started Guide.

Details of data issues for AddressBase Core will be communicated on the . This page will provide details of their impacts and updates on the expected time frame for their resolution.

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 for more Information on how to do this.

In the 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.

Classification Scheme page in the AddressBase Fundamentals guide
AddressBase Fundamentals guide
OS MasterMap Topography Layer
OS MasterMap Highways Network
Data capture and sources
GeoPlace
Unique Property Reference Number (UPRN)
Coordinate reference systems
Classification
Currency, completeness, and precision
Product supply
AddressBase Core Known Data Issues page
LogoAddressBase Core | Data Products | Ordnance SurveyOrdnance Survey
An image of a map showing the following AddressBase Core classifications: ZW: Object of Interest/Place of Worship RD: Residential/Dwelling LD: Land/Development CR: Commercial/Retail CL: Commercial/Leisure

Currency

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

Completeness

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

Precision

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.

Currency

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

Completeness

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

Precision

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.

Epoch Number
Publication Date
Data Cut Date

117

20 March 2025

14 February 2025

116

06 February 2025

03 January 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

Epoch Number
Publication Date
Data Cut Date

118

01 May 2025

28 March 2025

119

12 June 2025

09 May 2025

120

31 July 2025

27 June 2025

  • 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

  • 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

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's Downloads page; this Header file can be combined with the data to give a structure tabular view. Instructions to do this are provided in each product's Getting Started Guide.

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's Downloads page; this Header file can be combined with the data to give a structure tabular view. Instructions to do this are provided in each product's Getting Started Guide.

Working with COU data
Working with COU data
Working with COU data
Working with COU data
Working with COU data
Working with COU data
Working with COU data
Working with COU data
Working with COU data
Working with COU data
Working with COU data
Working with COU data
Working with COU data
Working with COU data
Working with COU data
Working with COU data
Working with COU data
Working with COU data
Working with COU data
Working with COU data
Working with COU data
Working with COU data
Working with COU data
Working with COU data
Working with COU data
Working with COU data
Working with COU data
Working with COU data
Working with COU data
Working with COU data
Downloading a dataset
Working with CSV data
Working with GPKG data
Working with COU data
Working with tiled data
OS Data Hub
Product Refresh Dates

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.

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.

Diagram showing the relationship between GeoPlace, Ordnance Survey, LLPGs, Royal Mail, Scottish LGs
Diagram showing the relationship between GeoPlace, Ordnance Survey, LLPGs, Royal Mail and Scottish LGs.
Diagram showing the relationship between GeoPlace, Ordnance Survey, LLPGs, Royal Mail, Scottish LGs
Diagram showing the relationship between GeoPlace, Ordnance Survey, LLPGs, Royal Mail and Scottish LGs.

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.

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.

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 lifecycle, 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.

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 lifecycle, 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.

Local Government’s National Land and Property Gazetteer (NLPG)

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.

The One Scotland Address Gazetteer (OSG)

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 owned large-scale data and coordinates

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.

Royal Mail Postcode Address File (PAF)

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.

Local Government’s National Land and Property Gazetteer (NLPG)

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.

The One Scotland Address Gazetteer (OSG)

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 owned large-scale data and coordinates

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.

Royal Mail Postcode Address File (PAF)

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.

AddressBase Plus Header files
Applying COU to tables > With archiving

This product is available to try out free online using one of our three sets of sample data (Exeter, Newport and Inverness) through the OS MasterMap Product Viewer:

This product is available to try out free online using one of our three sets of sample data (Exeter, Newport and Inverness) through the OS MasterMap Product Viewer:

To report an issue not currently listed here, please visit the .

'Contact us' page on the OS website

OS MasterMap Product Viewer

Interactive demonstrator of OS MasterMap Generation data

Cover

OS MasterMap Product Viewer

Interactive demonstrator of OS MasterMap Generation data

Cover

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.

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.

guide to coordinate systems in Great Britain
guide to coordinate systems in Great Britain