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

osngd

Loading...

INTRODUCTION TO OS NGD

Loading...

Loading...

Loading...

Loading...

GETTING STARTED

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

OS NGD NEWS

Loading...

Loading...

Loading...

Loading...

Data and Service Status

Loading...

Loading...

Loading...

Loading...

DATA STRUCTURE

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

Live Service Disruption and Maintenance

This page will be updated to note downtime due to planned or emergency maintenance or shutdown periods. Unexpected interruptions to product availability, releases and updates will be displayed here.

No live service disruptions are affecting OS NGD at this time.

No maintenance events are currently scheduled that will impact the availability of OS NGD.

API service status and OS NGD data issues

  • Any live interruptions to the availability of OS NGD API – Features and OS NGD API – Tiles will be documented on the Service Availability Dashboard on the OS Data Hub.

  • Please see the Current Known Data Issues page for details about current known data issues.

  • Please see the Resolved Data Issues page for details about resolved data issues.

OS NGD live service disruption

OS NGD planned maintenance

Getting started with CSV

What is a CSV file?

A comma-separated values (CSV) file is a common interchange format for spreadsheets and databases which facilitates a simplistic use of data. Each field is either textual or numeric. Within the CSV, each field is separated from the next by a comma. CSV file format is universally supported for easy ingestion into all major database products.

Please be aware that CSV files are designed to be opened in a database or GI system, and opening them in other software applications could corrupt the data. In particular, Excel has a row limit which might be exceeded by some of our CSV files containing OS NGD data, depending on the order you placed and its size. We recommend that you load CSV files containing OS NGD data directly into a database or GI system, rather than trying to open these files in Excel.

Change-Only Update (COU) files are only available for CSV data supplies of the OS NGD.

If you are using a large Area of Interest (AOI) or a full GB supply of data, for performance reasons we would suggest you load the CSV data into a database rather than trying to open directly in a GI system.

Key features of OS NGD CSV format

CSV offers users the following key features:

  • Change-Only Update (COU) files are only supplied in CSV format (they are not supplied in GeoPackage format)

  • Geometry provided as Well-Known Text (WKT)

  • Header rows included in the file

  • There will be one record per line in each file

  • Fields will be separated by commas

  • Where string fields contain commas, they will be delimited by double quotes

  • Double quotes inside strings will be escaped by doubling

  • Records will be terminated by Carriage Returns and Line Feeds

  • CSV files will be Unicode encoded in UTF-8

OS NGD Documentation

Welcome to OS NGD documentation! Here you can learn how to get started using OS NGD data via OS Select+Build and the OS NGD APIs.

What's the OS NGD?

The OS National Geographic Database (OS NGD) is a structured database containing authoritative geospatial data for Great Britain. It provides the most current, comprehensive and richly attributed data describing Great Britain ever produced by OS in non-proprietary data formats that are easily integrated into a wide array of customer systems and workflows.

What's available on this site?

This self-serve site is where you will find documentation to help you get started using OS NGD data via the download service of OS Select+Build and the two OS NGD APIs. Using the left-hand-side navigation menu, you can select and view pages and sections of interest, including:

Explore OS NGD

In-depth information on OS NGD data, including structure, applications and news:

Introduction to OS NGD

This section explains what the OS NGD is and who can access it, outlines the key benefits to customers, and details how to download sample data or visualise it online.


Explore OS NGD

In-depth information on OS NGD data, including structure, applications and news:

Get OS NGD

Try out OS NGD sample data, download it via OS Select+Build or access it through the OS NGD APIs:

COU supplies

Change-Only Updates (COUs) are only available for CSV data supplies of the OS NGD. The benefit of taking COU supplies is that you only receive the features which have changed since your last supply, reducing the overall size of the files you receive.

There are some restrictions on when you can choose to take COUs; these restrictions are dependent on the selections you make when ordering OS NGD data. Please see the 'Data ordering and currency' page for more information.

If you choose to receive a COU supply for your CSV data, this can be provided on either a daily or monthly frequency. In both cases, your COU file will contain any changes which have been made to the underlying data within the selected time frequency. If no changes have been made to a selected feature type of your choice, then you will receive a blank COU file.

The key attribution required to use and implement a COU is detailed below:

  • Unique Identifier: The unique identifier for the feature type you are using is how you will ensure you are updating the correct records in your data holdings. In most instances the unique identifier will be the OSID, but this is not always true, therefore please check the appropriate feature type pages in our documentation.

  • Version Date: This is the date when the feature was last updated in OS product databases.

  • Version Available From Date: This is the date when the feature became the latest version and was published to customers.

  • Version Available To Date: This is the date when the feature was superseded by an update or ceased to exist.

  • Change Type: This is a code list which gives more information about the type of change which has occurred.

Unique identifiers

The unique identifiers used in the OS NGD.

Unique identifiers in the OS NGD

OSID

The OS NGD primarily uses an identifier called the OSID (OS Identifier). OSIDs uniquely identify records within a feature type and have a maintained lifecycle, enabling them to support change tracking and linkages across datasets.

It should be noted that while an OSID is unique within a feature type, it may be shared across feature types when they represent the same real-world feature. For example, a point feature in the OS NGD Geographical Names Theme representing a water body will share the same OSID as the water body feature in the OS NGD Water Theme.

🔃 UPRN, USRN, UDPRN, UMRRN and postcode

Other unique identifiers are also present in the OS NGD, including:

  • UPRN (Unique Property Reference Number) for local authority Address records.

  • USRN (Unique Street Reference Number) for local authority Street records.

  • UDPRN (Unique Delivery Point Reference Number) for Royal Mail delivery points (for example, a mailbox or business unit).

  • 🆕 UMRRN (Unique Multiple Residence Reference Number) for multiple Royal Mail addresses that share a single delivery point.

  • Postcode is the identifier assigned by Royal Mail for the purposes of mail delivery. It's the primary unique identifier for (Great Britain) and (Northern Ireland) Feature Types. Postcode is an important identifier for the Feature Type, but as the features represent postcode parts (not whole postcodes), their primary unique identifier is Feature ID.

These unique identifiers remain the authoritative identifiers for their respective domains.

For a small number of feature types in OS NGD where it is not possible or necessary to have identifiers that persist over time, the Feature ID is used as the primary unique identifier. The , , and Feature Types use this unique identifier. The notional extents of the retail area features and Postcode Unit Area features are regenerated periodically (for example, monthly for the latter), at which point all features will get a new Feature ID.

The Topographic Identifier (TOID) is also present in the OS NGD, primarily to support customer migration from OS MasterMap products to the OS NGD. This is an optional attribute and should not be relied upon to complete data linking or for implementing Change-Only Updates (COUs). The reason for this identifier being optional is the improved currency on which the OS NGD is published, meaning the TOID, which is created in our existing OS product systems, will not always be allocated to features as frequently as they will be accessible via the OS NGD.

Attribute information for feature types

On the feature type pages (which are located in the Data Structure section), the following information can be found about each attribute:

  • Name and Definition: The name of the attribute and what it is describing.

  • Data Types: The values the attribute can take. For example, a numeric value or a string. This is provided for all three data formats – GeoJSON, GeoPackage, and CSV.

  • Nullable: A True or False value to denote whether the attribute always has to be populated with a value (False) or can be NULL (True).

  • Code List Name: The name of the code list used in association with the attribute (if applicable) and a hyperlink to the page displaying that code list.

  • Max Length: Values are given here to indicate the maximum length that you will find in the attribute, to aid in developing applications.

  • Multiplicity: Describes how many times this value is expected to be populated in the data. These values may be used in combination.

    • 1: There must be a value.

    • 2: There must be two values.

    • n: There may be one or more values.

  • OS NGD API – Features Filterable: A Yes / No value to denote whether you can refine your query in OS NGD API – Features specifically on this attribute.

  • OS Select+Build Filterable: A Yes / No value to denote whether you can refine your order in OS Select+Build on this attribute.

  • Data Schema Version: The OS NGD schema version the data above applies to. Please note that concurrent schema versions may be available at one time. For more information on how data schema versioning works in the OS NGD, please refer to the .

Getting started with OS recommended recipes

Discover OS recommended recipe guides containing detailed step-by-step instructions outlining how you can create set recipes for OS NGD data using OS Select+Build.

What are OS recommended recipes?

When you order data using OS Select+Build, you create a recipe to define the data you need. Selecting the right data from OS NGD themes can be complex, so we are developing a set of recommended recipe guides to help you get started with common use cases, focussing on areas where many customers have similar requirements.

These guides are intended as a starting point and you can adapt the suggested recipes at the recipe creation or editing stage so that they fully meet your needs.

Guides for creating OS recommended recipes

Coming next

We expect to add further OS recommended recipe guides over time.

Upcoming guides include:

  • Supporting new build developments

ArcGIS Pro

Accessing GeoPackage data via ArcGIS Pro

Requirements

  • ArcGIS Pro (version 1.1 or later)

  • A GeoPackage dataset

Certain versions of ArcPro (for example, version 2.5) require GeoPackages to have a spatial index added before the data can be viewed on the map. This can be done in the Catalog by opening the Feature Class Properties window within the 'Indexes' page.

Instructions

These instructions were created using ArcGIS Pro version 2.5, but versions from 1.1 onwards will support GeoPackage.

1

Open an existing project or create a new one

To create a new project, select Map from the Blank Templates section, then enter a Name and a Location for the project in the Create a New Project section. Click OK.

2

A dialog box will appear.

3

Navigate to the GeoPackage to be added into ArcGIS Pro. Select the GeoPackage and click Open. This will open the GeoPackage to reveal the individual layers.

4

The selected layers will then be added into ArcGIS Pro.

ArcMap

Accessing GeoPackage data via ArcMap

Requirements

  • ArcMap (version 10.2.2 or later)

  • A GeoPackage dataset

Certain versions of ArcMap (for example, version 10.8.1) require GeoPackages to have a spatial index added before the data can be viewed on the map. This can be done in the Catalog by opening the Feature Class Properties window within the 'Indexes' page.

Instructions

These instructions were created using ArcMap version 10.7, but versions from 10.2.2 onwards will also support GeoPackage features.

1

Select the Add Data button from the ribbon at the top of the workspace

ArcMap Add Data button.
2

The GeoPackage file will look similar to the one in the following screenshot:

3

Select the layers you want to upload into ArcMap.

Add the relevant selected GeoPackage layers into the map by clicking the Add button.

Cadcorp SIS

Accessing GeoPackage data via CadCorp

Requirements

  • CadCorp SIS (version SIS 9 or later)

  • A GeoPackage dataset

Instructions

These instructions were created using CadCorp SIS 9 Desktop Express; however all versions of CadCorp SIS 9 or later support GeoPackage.

1

In the upper ribbon, select Add Overlay.

CadCorp SIS Add Overlay button.
2

From here, a file browser dialog box appears where you can map to where the GeoPackage has been stored locally.

3

Once the correct GeoPackage has been located, click Finish.

MapInfo Professional

Accessing GeoPackage data via MapInfo Professional

Requirements

  • MapInfo Professional (version 15.2 or later)

  • A GeoPackage dataset

Instructions

These instructions were completed using MapInfo Professional version 2019; however, any version from 15.2 onwards can be used.

1

Select Open > Table in the top ribbon.

MapInfo Open Table button.

A dialog box will appear where you can search for the appropriate GeoPackage.

2

Another dialog box will appear showing the layers available to be imported.

3

Once the layers have been selected, click OK.

QGIS

Accessing GeoPackage data via QGIS

Requirements

  • QGIS (version 2.10.1 or later)

  • A GeoPackage dataset

Instructions

These instructions were created using QGIS version 3.22. Other versions of QGIS can be used, from version 2.10.1 onwards.

1

Open a new or existing QGIS project.

2

The Data Source Manager - Vector dialog box will appear.

3

Navigate to the GeoPackage. Double-click the file or select it, then click Add. A separate dialog box will appear.

4

It is possible to add selected layers, numerous layers or all layers. Once the relevant layers have been selected, click Add Layers.

FME

Reading GeoPackage data via FME

FME is a data integration platform which can read the GeoPackage format and be used to convert and transform the data into other formats or databases. The below example shows how to read a GeoPackage into an FME workbench.

Requirements

  • FME Desktop

  • An FME license

  • A GeoPackage dataset

Instructions

1

In the FME top ribbon, click the Add Reader button

A dialog box will appear.

2

The Coordinate System should also be set appropriately.

3

Another dialog box will appear to specify OGC GeoPackage Parameters.

Here, specific layers within the GeoPackage can be selected, rather than importing the entire file. Additionally, the Search Envelope can be used to clip the GeoPackage to an extent.

4

Click OK when the required themes / layers have been selected.

Styling OS NGD Data

Resources for styling OS NGD data.

OS Select+Build and OS NGD API – Features

You can choose from a range of contextual or analytical styles to visualise OS NGD data.

Four cartographic styles – Outdoor, Road, Light, and Black & White – are available to give the data a cartographic appearance:

Analytical styles can be used to colour OS NGD data by theme and collection to support data visualisation:

Two useful tutorials are available on our (a self-serve platform that provides a one-stop shop for all your OS technical geospatial support, including tutorials, demonstrators and case studies):

OS NGD API – Tiles

If you are using OS NGD API – Tiles, all the styling resources, including JSON files and sprites, are hosted within the vector tiles endpoint.

You can now create your own custom style for OS NGD API – Tiles; please see the Creating a custom style for OS NGD API – Tiles page on the OS APIs Documentation site for a guide on how to do this.

Data and Service Status Information

This section contains pages relating to OS NGD live service disruption, planned maintenance, current data issues and resolved data issues.


What's next?

Getting Started Information

This section includes getting started guides to help you access, use and style OS NGD data. You'll also find FAQs, in-depth information on OS NGD design, and webinars, tutorials and case studies.


In-depth information on OS NGD data, including structure, applications and news:

Try out OS NGD sample data, download it via OS Select+Build or access it through the OS NGD APIs:

Islands Address Local Custodian Codes

The following page details the current local custodian codes of all local custodians contributing to the OS Islands Address Collection.

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

GB Address Local Custodian Codes

The following page details the current local custodian codes of all local custodians contributing to the OS GB Address Collection.

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

👨‍🏫 OS NGD Explained

This page details what the OS NGD is, how to access it and who can use it.

✨ OS NGD Key Benefits to Customers

This page lists the key benefits of the OS NGD to customers.

🗺️ OS NGD Sample Data

Download sample data for OS NGD collections in GeoPackage or CSV formats. Sample data always use the latest data schema version available for each collection.

🔎 OS NGD Data Viewer

The OS NGD Data Viewer lets you visualise product sample data online for three areas (Exeter, Newport and Inverness). Sample data for most OS NGD feature types are available through the tool. The sample data always use the latest data schema version available for each feature type.

🗃️ Data Structure

Data structure pages provide more detailed information about data available for OS NGD themes, collections and feature types.

📣 OS NGD News

Learn about new data and access enhancements recently released for the OS NGD.

🗺️ OS NGD Sample Data

Try out OS NGD by downloading an area of sample data or visualising it online.

📥 OS Select+Build

Download OS NGD data using our bespoke download service, OS Select+Build.

📌 OS NGD APIs

Access OS NGD data using the OS NGD APIs to get started using OS NGD within desktop, web and mobile applications.

🌳 Greenspace recipe guide

A guide with detailed step-by-step instructions outlining how you can create a greenspace recipe in OS Select+Build.

🌉 Identifying crossing points and bottlenecks recipe guide

A guide with detailed step-by-step instructions outlining how you can create a recipe in OS Select+Build to identify the location of bridges, tunnels, fords and crossing points.

🏙️ Identifying higher-risk buildings recipe guide

A guide with detailed step-by-step instructions outlining how you can create a recipe in OS Select+Build to identify higher-risk buildings.

🚸 Safer routes to schools recipe guide

A guide with detailed step-by-step instructions outlining how you can create a safer routes to schools recipe in OS Select+Build.

🏡 Town and city planning recipe guide

A guide with detailed step-by-step instructions outlining how you can create a recipe in OS Select+Build to identify the level of access to natural areas from existing addresses, both residential and commercial.

⚙️ Live Service Disruption and Planned Maintenance

This page notes planned downtime due to maintenance or shutdown periods. Unexpected interruptions to product availability, releases and updates will also be displayed.

🔧 Current Known Data Issues

This page lists known current live data issues for the OS NGD themes, collections and feature types.

✅ Resolved Data Issues

This page lists resolved data issues for the OS NGD themes, collections and feature types.

📣 OS NGD News

Learn about new data and access enhancements recently released for the OS NGD, planned future data enhancements on our roadmap, the change log, recent data improvements, and recent announcements.

🗃️ Data Structure

Learn about the OS NGD data structure and the data available for each theme, collection and feature type.

📝 Code Lists

Access all of the code lists for the OS NGD.

📖 OS NGD Fundamentals

OS NGD Fundamentals covers the core elements of OS NGD design, including available data formats and file naming, data schema versioning, access methods, data ordering and currency, attribute information for feature types, unique identifiers and coordinate reference systems.

▶️ Getting Started

Our getting started guides will help you access, use and style OS NGD data. You'll also find FAQs, in-depth information on OS NGD design, and webinars, tutorials and case studies.

🗺️ OS NGD Sample Data

Download OS NGD sample data or visualise it online.

Please note, a single feature may be updated multiple times in a single COU file. This would happen where a single feature has changes committed in our product databases more than once within your selected COU frequency. Instead of suppressing all changes other than the last edit, your COU will contain all edits we have made to that feature. This is likely to occur more commonly if you choose to take a monthly supply, compared to daily, but it could also occur in a daily COU.

You can use the OS Downloads API to manage your daily / monthly COU supply of OS NGD data.

Please be aware that a feature can move between OS NGD feature types and even between OS NGD themes when OS makes data improvements or, in some instances, when a feature undergoes a change. For example, Pre-Build Address features will naturally change to Built Address features over time.

Feature ID

Other identifiers provided in the OS NGD

TOID

Postcode Unit Point
Postcode Unit Point
Postcode Unit Area
Postcode Unit Area
Retail Area Aggregated
Retail Area Major
Retail Area Minor

0: Population is optional.

Data schema versioning page

Add a layer by selecting Layer > Add Layer > Add Vector Layer from the top ribbon of the workspace.

Select the GeoPackage that will be loaded using the three dots button located next to the Vector Dataset(s) box.

Select the layers of the GeoPackage to be added to the map

The GeoPackage layers should now be viewable in the layers list on the left-hand side of the workspace.

Screenshot showing the QGIS Add Vector Layer menu.
QGIS Add Vector Layer menu.
Screenshot showing the Data Source Manager – Vector dialog in QGIS,
Data Source Manager – Vector dialog in QGIS.
Screenshot showing the Select Items to Add dialog in QGIS.
Select Items to Add dialog in QGIS.

Local custodian codes download

addressbase-islands-local-custodian-codes.csv
635B
Open

Local custodian codes download

Last update date

Local custodian codes available on this page were last updated on 10 March 2026

addressbase-local-custodian-codes.csv
16KB
Open

Select Map > Add Data from the ribbon at the top of the project,

Adding a GeoPackage into ArcGIS Pro

Select all of the relevant layers and click OK

More than one layer can be selected at any time by holding down the Ctrl (control) key and clicking on multiple layers.

The layers added into ArcGIS Pro will appear in the contents pane on the left-hand side of the project.

Screenshot showing how to create a new project in ArcGIS Pro.
Screenshot showing how to create a new project in ArcGIS Pro.
Screenshot of the Add Data button in ArcGIS Pro.
Add Data button
Screenshot of the Add Data dialog in ArcGIS Pro.
Add Data dialog in ArcGIS Pro.
Screenshot of the Add Data layer selection dialog in ArcGIS Pro.
Add Data layer selection dialog in ArcGIS Pro.
Screenshot of the layer properties dialog in ArcPro.

Navigate to the appropriate folder containing the GeoPackage to be uploaded

Double-click on the GeoPackage file to reveal the layers within it.

More than one layer can be selected at any time by holding down the Ctrl (control) key and clicking on multiple layers.

The GeoPackage layers should now be viewable in the layers list in the Table Of Contents on the left-hand side of the workspace.

Screenshot of the Add Data dialog in ArcMap.
Add Data dialog in ArcMap.
Screenshot of the Add Data layer selection dialog in ArcMap.
Add Data layer selection dialog in ArcMap.
Screenshot of the layer properties dialog in ArcMap.
Screenshot of the ArcMap Add Data button.

In the Add Overlay dialog box select Files > File

Navigate to the GeoPackage file

The data should now appear on the map.

Screenshot of the CadCorp SIS Add Overlay dialog.
CadCorp SIS Add Overlay dialog.
Screenshot of the CadCorp SIS Add Overlay browser dialog.
CadCorp SIS Add Overlay browser dialog.
Screenshot of the CadCorp SIS Add Overlay button.

Locate the GeoPackage in the file explorer and click Open.

Select which layers to import into MapInfo Progessional from the GeoPackage

The data should now be available in your workspace.

Screenshot showing the MapInfo Professional Open Table dialog.
MapInfo Professional Open Table dialog.
Screenshot showing the MapInfo Professional Select One or More Tables to Open dialog.
MapInfo Professional Select One or More Tables to Open dialog.
Screenshot of the top ribbon in MapInfo Professional with a red box around the Open Table button.

🖥️ How do I access it?

There are two access methods for OS NGD data:

  • OS Select+Build (the download service)

  • OS NGD APIs

👥 Who can use it?

The OS NGD is available to OS Partners and to public sector organisations who are members of the Public Sector Geospatial Agreement (PSGA).

✨ OS NGD Key Benefits to Customers

Find out what the key benefits of the OS NGD are.

🗺️ OS NGD Sample Data

Download OS NGD sample data or visualise it online.

📣 OS NGD News

Learn about new data and access enhancements recently released for the OS NGD, planned future data enhancements on our roadmap, the change log, recent data improvements, and recent announcements.

⚙️ Data and Service Status

Find out about OS NGD planned maintenance, any live service disruption, current data issues and resolved data issues.

📖 OS NGD Fundamentals

OS NGD Fundamentals covers the core elements of OS NGD design, including available data formats and file naming, data schema versioning, access methods, data ordering and currency, attribute information for feature types, unique identifiers and coordinate reference systems.

▶️ Getting Started

Our getting started guides will help you access, use and style OS NGD data. You'll also find in-depth information on OS NGD design, and webinars, tutorials and case studies.

❓ FAQs

View frequently asked questions about OS NGD data and the download service of OS Select+Build.

🗃️ Data Structure

Learn about the OS NGD data structure and the data available for each theme, collection and feature type.

📝 Code Lists

Access all of the code lists for the OS NGD.

Learn about new data and access enhancements recently released for the OS NGD.

Data structure pages provide more detailed information about data available for OS NGD themes, collections and feature types.

Resources for styling OS NGD data.

Select OGC GeoPackage in the Format dropdown and click the three dots button next to the Dataset box to specify which GeoPackage you want to read

Click Parameters in the Add Reader dialog box

Select the layers to be added into the workbench

An orange reader will appear which will display the name of the GeoPackage table that has been ‘read in’.

Screenshot of the FME Add Reader button.
FME Add Reader button.
Screenshot showing the FME Add Reader dialog.
FME Add Reader dialog.
Screenshot showing the FME OGC GeoPackage Parameters dialog.
FME OGC GeoPackage Parameters dialog.
Screenshot showing the FME GeoPackage Select Tables dialog.
FME GeoPackage Select Tables dialog.

Tutorials on downloading and using OS stylesheets and styling data analytically

'More Than Maps' site
How to download and use OS stylesheets
OS NGD analytical styling

Explore OS NGD

Get OS NGD

OS NGD Fundamentals covers the core elements of OS NGD design, including available data formats and file naming, data schema versioning, access methods, data ordering and currency, attribute information for feature types, unique identifiers and coordinate reference systems.

Discover how to download OS NGD data using our bespoke download service, OS Select+Build.

Learn how to access and use OS NGD API – Features and OS NGD API – Tiles.

Resources for styling OS NGD data.

Learn more about the OS NGD through our webinars and tutorials. Case studies demonstrate how customers across numerous sectors are already using and benefiting from OS NGD data.

Frequently asked questions on OS NGD data and the download service of OS Select+Build.

Learn about new data and access enhancements recently released for the OS NGD.

Data structure pages provide more detailed information about data available for OS NGD themes, collections and feature types.

Resources for styling OS NGD data.

Try out OS NGD by downloading an area of sample data or visualising it online.

Download OS NGD data using our bespoke download service, OS Select+Build.

Access OS NGD data using the OS NGD APIs to get started using OS NGD within desktop, web and mobile applications.

OS NGD Explained

This page explains what the OS NGD is, how to access it and who can use it. Additional resources are provided with links to deeper technical content.

What is the OS NGD?

The OS National Geographic Database (OS NGD) is a structured database containing authoritative geospatial data for Great Britain. It provides the most current, comprehensive and richly attributed data describing Great Britain ever produced by OS in non-proprietary data formats that are easily integrated into a wide array of customer systems and workflows.

How do I access the OS NGD?

There are two access methods for OS NGD data:

  • (the download service)

The OS NGD is available to OS Partners and to public sector organisations who are members of the Public Sector Geospatial Agreement (PSGA). OS Select+Build and the OS NGD APIs can be accessed via the on either the .

Alternatively, you can try out OS NGD collection data for free for three to six months by applying for . This licence is available for all collections apart from the OS Islands Address and OS Functional Areas Collections.

The licence is primarily designed for organisations either considering becoming an OS Partner or who want to trial OS Premium data before working with an existing OS Partner.


Detailed documentation on OS NGD design and practical guides on how to apply OS NGD data:

In-depth information on OS NGD data, including structure, applications and news:

Try out OS NGD sample data, download it via OS Select+Build or access it through the OS NGD APIs:

OS NGD Fundamentals

OS NGD Fundamentals covers the core elements of OS NGD design, including data formats, coordinate reference systems used, data schema versioning, and data ordering and currency.

Introduction

The following pages provide an overview of the OS National Geographic Database (OS NGD); they cover the core elements of its design, including data formats, the coordinate reference systems used, and how Change-Only Updates (COUs) will be provided, amongst other topics:

  • Terminology and access

  • File formats and naming

  • Data ordering and currency


Detailed documentation on OS NGD design and practical guides on how to apply OS NGD data:

In-depth information on OS NGD data, including structure, applications and news:

Try out OS NGD sample data, download it via OS Select+Build or access it through the OS NGD APIs:

Terminology and access

OS NGD data is different from our other products because you access it from a single source where you'll find the data you need without having to download unnecessary datasets. It also has a simple data structure, designed to help you quickly answer questions and develop more intelligent solutions.

OS NGD terminology: themes, collections and feature types

OS NGD terminology: themes, collections, feature types and features.

Theme

A theme is a macro grouping of features which all represent similar geographic entities. Themes are the highest level of grouping within the OS NGD, and examples include ‘Buildings’ and ‘Transport’.

Themes allow for quick discovery and navigation when using OS Select+Build (the OS NGD download service) or the OS NGD APIs. They also give you the ability to quickly access all OS data relating to your particular theme of interest.

The nine OS NGD themes are: Address, Administrative and Statistical Units, Buildings, Geographical Names, Land, Land Use, Structures, Transport, and Water.

The nine OS NGD data themes.

Collection

A collection is a sub-grouping of the OS NGD themes. Collections group together similar types of data within a theme. Examples include ensuring network and routing data is separated from topographic features. For example, in the OS NGD Water Theme, there are two collections: OS Water Features (topographic data) and OS Water Network (network data).

This makes it easier for you to access only the data you require.

A feature type is the most granular level of grouping within the OS NGD. Feature types have their own data model and specifications which are not commonly shared with other feature types.

When you order data through OS Select+Build (the OS NGD download service), the data you receive will be provided at a feature type level.

The OS NGD is available to OS Partners and to public sector organisations who are members of the Public Sector Geospatial Agreement (PSGA). OS Select+Build and the OS NGD APIs can be accessed via the on either the .

Alternatively, you can try out OS NGD collection data for free for three to six months by applying for . This licence is available for all collections apart from the OS Islands Address and OS Functional Areas Collections.

The licence is primarily designed for organisations either considering becoming an OS Partner or who want to trial OS Premium data before working with an existing OS Partner.

The OS NGD is available via the on either the . There are three access methods to choose from once you are on the OS Data Hub:

  • OS Select+Build: A download service which enables you to choose only the data you require and select how you want to receive your data.

  • OS NGD API – Features: An OGC API – Features service.

  • OS NGD API – Tiles: A vector tiles service based on OGC API – Tiles.

Sharing OS Select+Build recipes

Step-by-step instructions on how to share your OS Select+Build recipes with other organisations.

You can share a recipe you've created with another organisation (as long as they have access to OS Select+Build on the OS Data Hub). This functionality enables collaboration between organisations.

The following sub-sections on this page cover:

How do I share a recipe?

To share a recipe:

1

Log into your account

Click Login on the OS Data Hub menu bar to log into your account.

Screenshot showing the OS Data Hub homepage.
2

Select Data from the menu bar to view your workspace.

3

Choose Downloads > OS Select+Build Recipe Library from the left hand side secondary navigation menu. You will then be taken to your organisation's OS Select+Build Recipe Library.

4

In your organisation's OS Select+Build Recipe Library, scroll or search for the recipe you want to share.

5

In this view, you will be able to see the Recipe actions dropdown (where you can share, edit or delete a recipe).

  • Click the Recipe actions dropdown.

  • Click the Share recipe button.

6

Search for the organisation with whom you wish to share the recipe. To do this, just start to type the organisation's name, then select the correct organisation from the list.

7

Add a message for the organisation receiving the recipe to provide them with context around why you are sharing the recipe with them before clicking Send.

To accept a shared recipe:

1

Click Login on the OS Data Hub menu bar to log into your account.

You will see a new notification at the top right of your screen, indicated by a bell button and a number count of any unread notifications.

2

Click the bell button. You will see details of a notification explaining You have been sent a shared recipe, which will include the name of the organisation that shared the recipe with you, along with a message if they added one when sharing the recipe.

3

To reject a recipe shared with you:

1

Click Login on the OS Data Hub menu bar to log into your account.

You will see a new notification at the top right of your screen, indicated by a bell button and a number count of any unread notifications.

2

Click the bell button. You will see details of a notification explaining You have been sent a shared recipe, which will include the name of the organisation that shared the recipe with you, along with a message if they added one when sharing the recipe.

3

Getting started with temporal filtering

This guide introduces the concept of temporal filtering in the OS NGD and gives instructions on how to add a temporal filter to a new data package.

Introducing temporal filtering

Temporal filtering allows you to order a one-off snapshot of data from the OS NGD from a current or past date.

Temporal filtering is an optional step when you create a new data package against one of your existing recipes. For further information and step-by-step instructions on creating recipes and data packages, please see the Getting started with recipes and Getting started with data packages pages.

  • You cannot apply a temporal filter to an existing data package held in your Data packages list; a temporal filter can only be added to new data packages during the data package creation stage.

  • The earliest date you can request for the majority of feature types in the OS NGD via a temporal filter is 29 September 2022.

  • As new feature types are added to the OS NGD, their temporal filter range will begin on the date they are added (for example, 28 March 2023 for the Waterbody Catchment Feature Type). Each feature type page states the earliest start date available for temporal filtering on that feature type.

How do I add a temporal filter to a new data package?

To create a new OS NGD data package and apply a temporal filter to it:

1

Log into your account

Click Login on the OS Data Hub menu bar to log into your account.

Screenshot showing the OS Data Hub homepage.
2

Select Data from the menu bar to view your workspace.

3

Choose Downloads > OS Select+Build Recipe Library from the left hand side secondary navigation menu. You will then be taken to your organisation's OS Select+Build Recipe Library.

4

In your OS NGD Select+Build Recipe Library, scroll or search for the recipe you wish to create a data package against, select that recipe, then click the Add data package button.

5

Add the following details to your data package under Add a data package in the secondary navigation menu:

  • Give your data package a name.

  • Choose the area you want to receive your data for: either 'All of Britain or Predefined Area' (this means you receive data and it will not be refined by location) or 'Draw a polygon / upload a file / use an OS polygon' (to select a smaller area for your data to be provided for).

6

Click the Create data package button.

Getting started with GeoPackage

What is GeoPackage?

GeoPackage (.gpkg) is an open, non-proprietary, platform-independent, and standard data format for geographic information systems (GIS), 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. GeoPackage is natively supported by numerous software applications.

Key features and benefits of GeoPackage

GeoPackage offers users the following key features and benefits:

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

  • Attribute names are not limited in length, making the format user-friendly.

  • The file size limit is very large at 140TB, so lots of data can be easily accommodated (please note that a file size limit may be imposed by the file system to which the file is written).

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

  • Data will be supplied in British National Grid (EPSG:27700), World Geodetic System (WGS84: EPSG: 4326), or British National Grid + ODN Height (EPSG: 7405), depending on your selection when ordering OS NGD data.

The following sub-sections provide step-by-step instructions on how to access GeoPackage data via various GIS software packages, all current versions of these support GeoPackages natively.

It is possible to use Extract, Transform, Load (ETL) tools to convert the data into different formats and to load into databases.

Accessing OS NGD APIs

Learn how to access and use OS NGD API – Features and OS NGD API – Tiles.

OS NGD APIs provide programmatic access to OS NGD data, enabling rich geospatial data to be integrated into a wide array of applications and use cases. Accessing OS NGD data via our APIs allows you to discover what data is available before using it, access the benefits of OS NGD within your applications and build new solutions with rich, consistent and current information about the real world.

Documentation for the OS NGD APIs is available on the OS APIs Documentation site alongside documentation for our other OS APIs. The pages below provide an overview of both APIs and details of how to get started with a new project.

These pages should be used in conjunction with the more detailed pages within the Data Structure section which are specifically focussed on the different OS NGD themes, collections and feature types.

Access to the OS NGD APIs is available via the OS Data Hub.


Discover OS NGD

Detailed documentation on OS NGD design and practical guides on how to apply OS NGD data:

In-depth information on OS NGD data, including structure, applications and news:

GB Address

The OS GB Address Collection is a complete, analytical and authoritative addressing dataset for Great Britain. It is designed to provide a detailed view of an address and its lifecycle.

Collection applications

The OS GB Address Collection allows you to:

  • Keep your address data current with up-to-daily updates.

  • Utilise the richness of Local Authority data and analyse addresses by their classification, postal status and build status to create a detailed picture of a given area.

  • Access all addresses in Royal Mail’s Postcode Address File (PAF), Not Yet Built (NYB) and Multiple Residence (MR) datasets, with the ability to use PAF’s Unique Delivery Point Reference Number (UDPRN) and Unique Multiple Residence Reference Number (UMRRN) alongside the authoritative Unique Property Reference Number (UPRN).

  • Easily create mail shots using the Full Address attribute on the Royal Mail Address Feature Type.

  • Carry out spatial analysis and aggregation using the accurate rooftop coordinates provided for each address.

  • Easily identify and download addresses by pre-build, built and historic lifecycle stages.

  • Use the UPRN to easily link different data sets right down to a single address.

  • A full representation of an address as you can view both the Royal Mail and Local Authority representations of it.

  • Up-to-daily updates to data.

  • The simplified data model means there’s no need to be an addressing expert to use the data.

  • Plug and play – the data is simple and quick to implement as you don't need to pre-process it before you use it.

Frequently asked questions (FAQs) about this collection and detailed answers are available from the .

Great Britain.

British National Grid (EPSG: 27700).

The earliest date on which you can request a one-off snapshot of a date in the past for data in this collection is noted at the top of the individual feature type pages.

GeoPackage or CSV (comma-separated values).

GB Address data can be accessed through the via OS Select+Build, the bespoke OS NGD download service. It can't be accessed through OS NGD API – Features or OS NGD API – Tiles.

  • Included in the (PSGA) – therefore, it's free at point of use for Public Sector organisations.

  • Available to OS Partners for commercial resell in your solutions.

  • Available for organisations to try out for free for three months under the ; this licence is primarily designed for organisations either considering becoming an OS Partner or who want to trial OS Premium data before working with an existing OS Partner.

OS NGD Key Benefits to Customers

This page lists the key benefits of the OS NGD to customers.

The key benefits of the OS National Geographic Database (OS NGD) to customers are as follows:

  • Increased data update frequency: With the new OS NGD APIs and OS Select+Build you can access themes of data which are updated up to daily.

  • Choose exactly what data you take: For the first time, you can select and build your own data package/s rather than taking pre-selected OS products. For example, if you're only interested in buildings data, then you just select the OS NGD Buildings Theme. There's no need to take a larger product and spend time filtering out the buildings data from it. You can also select data from different OS NGD collections to build your own bespoke data package/s.

Data schema versioning

Through the OS NGD, Ordnance Survey aims to iterate and release data enhancements quicker than ever before. We want to be able to do this without disrupting customers who have adopted data schemas and are heavily reliant on a specification remaining the same for a longer period of time. With this in mind, the OS NGD is able to run multiple data schema versions for a single feature type at any given time.

When we release a new data schema version in the OS NGD, the changes will be visible on the feature type pages of this documentation platform. As you can see from the image below, each attribute on a feature type page states which data schema version it is present within, with the Version Date attribute in the example below being present in both data schema versions 1.0 and 2.0:

As new enhancements are made to a given feature type in the OS NGD which require the schema to be uplifted (for example, new attributes being added, resulting in a major schema version increment from 1.0 to 2.0), the new data schema version will become available via the OS NGD access services (i.e. OS Select+Build and the OS NGD APIs).

There are two types of version increments that can be applied:

  • Minor: A non-breaking change that does not usually impact a customer’s implementation of the data, for example, the addition of an attribute value to a code list.

GDAL

Using GDAL to load a GeoPackage into a database

is a translator library for raster and vector geospatial data formats that is released under an X/MIT style Open Source by the . It comes with a variety of useful command line utilities for data translation and processing. The following section covers the loading of GeoPackage datasets into a database using the ETL tool GDAL. The process will be similar for other databases such as Oracle and SQL Server, as well as converting to other data formats.

  • A database with extension enabled

  • GDAL version 1.11.0 or above (with access to a command line interface to use it)

Loading CSV files

Loading OS NGD CSV files into databases

It is recommended that you have a basic understanding of database terminology before following the guides in the tabs below. The guides contain generic instructions, and it is recognised that there are multiple ways to load CSV files into databases which may be more suitable to your environment and existing processes.

Prior to loading the data into a database, it is necessary to create the relevant tables in the database. We have supplied the DDL statements that can be accessed in our .

These instructions are based on version 14, but should work for all supported versions. The instructions assume that you have set-up your database with the spatial extension.

Once connected to your PostgreSQL database, with the relevant schema and table created, the CSV file can be loaded with the following SQL statement using the :

These instructions are based on 2019, but should work for all supported versions.

Processing COUs

Processing OS NGD COU files.

The process to load the COU files will depend on a number of factors based on your own environment and requirements, including:

  • Database software

  • Data loading method or software

  • Feature retention and lifecycle requirements

There are two main scenarios that represent either extreme of the feature lifecycle options:

Data Structure Information

This section gives an overview of the OS NGD data structure and details the data available for each OS NGD theme, collection and feature type.

OS NGD data is different from our other products because you access it from a single source where you'll find the data you need without having to download unnecessary datasets. It also has a simple data structure, designed to help you quickly answer questions and develop more intelligent solutions.

OS NGD data has been categorised to make it easier and quicker for you to discover the data you need:

  • Themes: Geographic data of Great Britain is structured into nine themes of related items.

  • Collections: Each theme is made up of one or more collections, which in turn have feature types.

📖 OS NGD Fundamentals

📥 Downloading with OS Select+Build

📌 Accessing OS NGD APIs

🎨 Styling OS NGD Data

👩‍🏫 OS NGD Webinars, Tutorials and Case Studies

❓ FAQs

📣 OS NGD News

🗃️ Data Structure

🎨 Styling OS NGD Data

🗺️ OS NGD Sample Data

📥 OS Select+Build

📌 OS NGD APIs

QGIS

Accessing GeoPackage data via GIS software

Converting / Loading a GeoPackage to other data formats

In the OS NGD GeoPackages, the column ordering is slightly different to those listed on the individual feature types pages, and therefore the OS NGD CSV files.

The first column is an additional fid attribute, which is an INTEGER NOT NULL column. This acts as a primary key and is a requirement of the OGC GeoPackage specification.

Additionally, the geometry column will always be the second column; however, the attribute, or its value, isn't usually visible in GIS software.

The remaining ordering of columns will match the attribute listings on the feature types pages.

ArcGIS Pro
ArcMap
CadCorp SIS
MapInfo Professional
FME
GDAL

Rich attribution ensures the data is straightforward to navigate and query.

  • Persistent unique identifiers with lifecycle information.

  • The ability to select addresses from a specific lifecycle state (for example, Built Address and Pre-Build Address).

  • Full UK address coverage available via accessing the OS GB Address and OS Islands Address Collections together.

  • Cross-references make it easy for you to link data in this collection with data from other OS NGD collections.

  • Key elements

    FAQs

    Coverage

    Default coordinate reference system

    Temporal filtering

    Supply formats

    Supply mechanism

    Using our data

    FAQs page
    OS Data Hub
    Public Sector Geospatial Agreement
    Data Exploration Licence
    Examples of Built Address, Pre-Build Address and Royal Mail Address features and the attribution provided for them. The visualisation shows an image of completed house and a house under construction. Pop ups against each image show what example attribution might look like for the Built Address features, Pre-Build Address features and Royal Mail Address features.
    Examples of Built Address, Pre-Build Address and Royal Mail Address features and the attribution provided for them.

    Feature type

    Who can access the OS NGD?

    What's the PSGA?

    The PSGA (Public Sector Geospatial Agreement) sets out how Ordnance Survey (OS) provides world-leading location data and expertise to the public sector across Britain. It supports the delivery of critical infrastructure and services, as well as working to help protect our environment. 

    Find out more about the PSGA by visiting the OS website, including the benefits of joining, instructions on how to access OS data, success stories, support, registration process information and instructions, and a PSGA Member finder tool to check if your organisation is already a member.

    Data Exploration Licence

    How do you access the OS NGD?

    OS Data Hub
    Premium Plan or Public Sector Plan
    a Data Exploration Licence
    OS Data Hub
    Premium Plan or Public Sector Plan
    Infographic showing the OS NGD access methods as of May 2023. The OS NGD can be accessed via OS Select+Build or two NGD-specific APIs.
    OS NGD access methods.
    Infographic showing OS NGD terminology: themes, collections, feature types and features.
    Image showing a simple map of Great Britain. The 9 OS NGD data themes names are listed: Address, Administrative and Statistical Units, Buildings, Geographical Names, Land, Land Use, Structures, Transport, and Water.

    View details of the received recipe

    Click View recipe details. The recipe details will be displayed for you to review

    4

    Accept the shared recipe

    Click the Accept recipe button. You will be presented with a dialog box explaining: When you accept a recipe, it is added to your organisation’s recipe library. It will show as 'shared'. You can create data packages from it, but you can’t share the recipe with other organisations.

    If another team member in your organisation declines the invitation to accept a shared recipe before you view it, you may no longer have access to the shared recipe.

    Shared recipes that you have accepted from another organisation can be identified by the presence of the Shared with me tag against them.

    View details of the received recipe

    Click View recipe details. The recipe details will be displayed for you to review

    4

    Decline the shared recipe

    If this recipe is not right for you and you want to reject it, click the Reject button.

    Once a shared recipe is rejected, you will not be able to access it again.

    Sharing recipes

    Accepting a shared recipe

    Rejecting a shared recipe

    Navigate to the OS Data Hub workspace

    Navigate to the OS Select+Build Recipe Library

    Find the recipe you want to share

    Select share recipe with your organisation from the recipe actions dropdown

    Please note that you can only share recipes created by your organisation.

    Choose the correct organisation from the recipe dialog

    Add a descriptive message about the recipe

    How do I accept a recipe shared with me?

    Log into your OS Data Hub account

    Open the notification menu

    How do I reject a recipe shared with me?

    Log into your OS Data Hub account

    Open the notification menu

    OS Data Hub
    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
    A screenshot of the OS Data Hub home page showing the sign up and log in buttons in the top right hand corner
    Screenshot showing the OS Data Hub homepage.
    A screenshot of the OS Data Hub home page showing the sign up and log in buttons in the top right hand corner
    Screenshot showing the OS Data Hub homepage.
    A screenshot of the OS Data Hub home page showing the sign up and log in buttons in the top right hand corner
    FME result showing dataset has been read in
    Select the desired coordinate reference system.
  • Select a file format: CSV or GeoPackage.

  • Select the updates you want. Instead of selecting the 'not required' or COU (Change-Only Update) frequency options (which are available under the 'Select updates' drop-down), to apply a temporal filter, you should select the option for a one-off snapshot of a current or past date by ticking the following check box:

  • Screenshot showing the one-off snapshot option when creating a new data package in OS Select+Build.
    • Select the supply date needed for the snapshot:

    Screenshot of OS Select+Build showing the one-off snapshot check box option selected and a date selected.
  • If you request a temporal filter date for your new data package that precedes the date a feature type in the data package was added to the OS NGD, then no results will be returned.

  • Navigate to the OS Data Hub workspace

    Navigate to the OS Select+Build Recipe Library

    Find the recipe you want to create a data package against

    Add details to the data package

    Finish creating your data package

    You will receive an email confirming that your data package is being created and another one when your new data package is ready to download.

    Things to note

    OS Data Hub
    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
    Screenshot showing an example of adding a data package to a recipe using OS Select+Build in the OS Data Hub.
    Screenshot showing an example of adding a data package to a recipe using OS Select+Build in the OS Data Hub.
    A screenshot of the OS Data Hub home page showing the sign up and log in buttons in the top right hand corner

    New, easier ways to access data: The download service of OS Select+Build lets you access only the data you need in the format you want. OS NGD API – Features and OS NGD API – Tiles give you online access to the OS NGD to help you quickly request data using the latest OGC API – Features and OGC API – Tiles standards, respectively.

  • Customer-friendly data formats: OS NGD data is available in four easy-to-use data formats: GeoPackage, CSV (comma-separated values), GeoJSON (via OS NGD API – Features only) and vector tiles (via OS NGD API – Tiles only).

  • More discoverable data: Improved data structures and metadata within the OS NGD, new and bespoke documentation within OS Select+Build, and an extensive online documentation platform mean you'll find the right data and support you need quicker than ever before.

  • Built with the future in mind: The OS NGD is much more flexible, allowing for changes to the data structure and enhancements to be made when needed to meet evolving customer needs.

  • Rich attribution: OS NGD data has rich attribution to ensure that it's straightforward to navigate and query. Attribute names have also been simplified to make them easier to understand.

  • Included in the Public Sector Geospatial Agreement (PSGA): Therefore, OS NGD data is free at point of use for Public Sector organisations. It's also available to OS Partners for commercial resell in your solutions.


  • Detailed documentation on OS NGD design and practical guides on how to apply OS NGD data:

    In-depth information on OS NGD data, including structure, applications and news:

    Try out OS NGD sample data, download it via OS Select+Build or access it through the OS NGD APIs:

    The eight key benefits of OS NGD to customers - these benefits are described in detail in the text on this page.
    The key benefits of OS NGD to customers.

    The OS NGD gives new and enhanced ways for customers to access the most trusted and up-to-date geographic information from OS.

    Its launch does not instigate withdrawal of any of the existing OS Premium or OS OpenData Products, including APIs. These products will continue to be managed through their product lifecycle, including withdrawal, separately to the OS NGD.

    More details are available from the .

    Discover OS NGD

    Explore OS NGD

    Get OS NGD

  • Major: A significant breaking change that usually impacts a customer’s implementation of the data, for example, the addition or removal of an attribute.

  • When a data schema undergoes a minor version increment, the previous version will no longer be available. This is because the change is deemed to be so small that there is little to no work involved in customers migrating to the latest version of the data.

    When a data schema undergoes a major version increment, the previous version will become known as being in 'maintenance' and the new data schema version will be known as the ‘latest’. This reflects an understanding of the work required for customers to move to a new version and allows time for this to happen.

    When using the OS NGD access services, you will be able to choose which data schema version you want to use for feature types when ordering or interacting with the data where more than one major version exists. You can choose from data schema versions which are in the 'latest' or 'maintenance' states.

    Older data schema versions (i.e. those in a maintenance state) will remain in the OS NGD for a period of time; it's important to note that these maintenance versions will continue to receive updates. Before any data schema version is retired for a given feature type (i.e. when it no longer receives updates and will be removed from the ordering and selection process), customer communications will be distributed, and a notice period will be issued to allow sufficient time for customers to upgrade to a newer version of a data schema.

    Code lists within the OS NGD have only one type of version increment applied: major.

    A code list will undergo a major version change when a new code list value is added to it. Values will never be removed from a code list because this would impact temporal filtering within the OS NGD.

    When a code list undergoes a major version increment, all feature types that implement the code list will undergo a minor version increment, reflecting the data change that will occur.

    In the worked example below, we demonstrate how a feature type has new major data schema versions released (v2.0 and then v3.0), while maintaining older data schema versions (v1.0 and then v2.0), before the original data schema version (v1.0) moves into end of life and is retired.

    Worked example of how data schema versioning works in the OS NGD.
    • In this example, the feature type starts with a single data schema version (v1.0), known as the latest data schema version.

    • At a point in the future, data enhancements are made which require the data schema version to be uplifted, so a second major data schema version (v2.0) is released. As there can only be one latest data schema version (v2.0), the original data schema version (v1.0) drops down into maintenance – but it still receives updates and is still accessible to customers via the OS NGD access services.

    • Further again into the future, additional new enhancements are made to the feature type, requiring a third major data schema version (v3.0) to be released. Again, as before, there can only be one latest data schema version for a feature type (v3.0), so the second data schema version (v2.0) drops down into maintenance. Two major data schema versions (v1.0 and v2.0) are now in maintenance, but again, both are still receiving updates and are accessible to customers via the OS NGD access services.

    • At a future point, and after customer communications have been distributed and a formal notification period has elapsed, it is decided to retire the original data schema version (v1.0). V1.0 moves into the end of life state, where it stops receiving updates and can no longer be accessed by customers via the OS NGD access services. V3.0 remains the latest data schema version and v2.0 remains in maintenance, with both data schema versions receiving updates and being accessible to customers via the OS NGD access services.

    If you select an Annual Full Supply frequency for your OS NGD data order in OS Select+Build, we will provide you with the data as it was on 01 January of the current year. This means if a new feature type or a new data schema version of an existing feature type was released after 01 January and you order either of these as part of your Annual Full Supply, you will receive an empty data package for the newly released feature type / new data schema version of an existing feature type. The data for the new feature type / new data schema version of an existing feature type will then be included in your supply on the next 01 January after the release.

    For example, the March 2026 OS NGD data enhancements release contained six new feature types (Retail Area Aggregated, Retail Area Major, Retail Area Minor, Postcode Unit Point, Postcode Unit Point, and Postcode Unit Area) and one new data schema version for an existing feature type (Compound Structure v3.0). The data for the new feature types and the new data schema version for the existing feature type will not be part of Annual Full Supply orders until 01 January 2027.

    For example, the October 2026 OS NGD data enhancements release contained five new data schema versions for existing feature types: Regional Authority v2.0, Royal Mail Address v1.1 and v2.0 (OS GB Address Collection), and Royal Mail Address v1.1 and v2.0 (OS Islands Address Collection). The new data schema versions for the existing feature types will not be part of Annual Full Supply orders until 01 January 2027.

    Data schema version: The specification to which OS delivers an OS NGD feature type. This includes the attributes a feature type contains, what the attributes are called, the data types of the attributes, whether they are nullable, the precision (if applicable), the scale (if applicable), whether there is a code list associated with an attribute, and the max length (if applicable).

    Please note that data schema versioning is implemented at a feature type level. Therefore, increments and withdrawals of data schema versions are done at a feature type level and not at an OS NGD wide level.

    How has data schema versioning been implemented?

    Screenshot from a feature type page on the OS NGD Documentation platform showing where data schema version information is held for an attribute.
    Data schema version information is held against each attribute listed on a feature type page.

    Latest: The latest data schema version released for a given feature type.

    Maintenance: An older data schema version for a given feature type, but one which is still receiving updates and can be accessed by customers via OS NGD access services.

    End Of Life: A retired data schema version for a given feature type which is no longer receiving updates and cannot be ordered by customers via OS NGD access services.

    If you choose not to specify a data schema version for a given feature type or if you don't change the selection from its default, then you will always be provided with the latest data schema version for that feature type.

    Code list versioning

    Worked example

    Annual Full Supply orders and data schema versioning

    A GeoPackage dataset

    1

    Use the program to list information about the GeoPackage

    ogrinfo <PATH_TO_GEOPACKAGE>

    Example:
    ogrinfo wtr_ntwk_waterlinkset.gpkg
    ogrinfo output
    INFO: Open of `C:\wtr_ntwk_waterlinkset.gpkg'
          using driver `GPKG' successful.
    1: wtr_ntwk_waterlinkset
    2: wtr_ntwk_waterlinkset_wtrlinkref (None)

    Without any arguments supplied, ogrinfo will return the layers contained within the GeoPackage.

    2

    Use ‘Summary Only’ (-so) and ‘List all features of all layers’ (-al) arguments to view summary information about the layers within the GeoPackage

    ogrinfo<PATH_TO_GEOPACKAGE>-so -al

    Combined, these arguments will provide summary information about all the layers within the GeoPackage, including projection, schema, feature count and extents.

    3

    The arguments below will load all layers from the source GeoPackage into the specified target schema in the database:

    ogr2ogr -f PostgreSQL "PG:user=<USERNAME>password=<PASSWORD> dbname=<DATABASENAME>host=<HOST>port=

    Different loading options (including renaming tables, reprojecting the data, etc.) can be found on the PostgreSQL / PostGIS — GDAL documentation page.

    Requirements

    GDAL
    License
    Open Source Geospatial Foundation
    PostgreSQL
    PostgreSQL
    PostGIS

    Instructions

    Once connected to your SQL Server database, with the relevant schema and table created, the CSV file can be loaded with the following SQL statement using the BULK INSERT command:

    However, it is possible to change the destination geometry column to a nvarchar(max) type, and then either post process the table or use a a computed column to generate a geometry type column (see code examples below).

    It is not possible to load OS NGD CSV files into an Oracle database using the default SQL*Loader utility. The geometries are supplied in Well-Known Text (WKT) format and some of them are too large for SQL*Loader to process.

    However, with the relevant schema and table created in your Oracle database, the CSV file can be loaded using ETL (extract, transform, load) tools, for example, GDAL or FME.

    PostGIS will automatically store the geometry data that is supplied in Well-Known Text (WKT) format.

    There is a known bug affecting PostgreSQL versions 11, 12 and 13 in Windows environments, where the COPY command cannot load files larger than 4GB. As a workaround, version 14 (or later) of the COPY command can be used to load data into the affected database versions.

    For reference, the error message states ERROR: could not stat file.

    OS NGD Resources GitHub repository
    PostgreSQL
    PostGIS
    COPY command
    Microsoft SQL Server
    COPY destination_schema.destination_table 
        FROM 'source_path_to_csv_file\source_name_of_csv_file.csv'
        DELIMITER ','
        CSV HEADER
        ENCODING 'UTF8';
    Computed column example
    ALTER TABLE destination_schema.destination_table
    ADD new_computed_column_name AS
        geometry::STGeomFromText(destination_table.geometry, /* EPSG_CODE_OF_GEOM */) persisted;

    It is not possible to BULK INSERT the geometries directly in their Well-Known Text (WKT) format.

    BULK INSERT destination_schema.destination_table
    FROM '
    
    Post process example
    -- Add new geometry column
    ALTER TABLE
    
  • Latest feature view

  • Full feature archive

  • In this scenario, the COU files are processed and only the current version of every feature is retained. This will result in the same data holdings that would be achieved if a new full supply was received on this date.

    To achieve this, either post-processing will have to be done once all COU data is loaded into a database, or the loading process will need to evaluate the COU data against your existing data and process accordingly. This processing will be based on the supplied attributes which detail the type of change and the dates for that version.

    Each feature type is supplied with a Change Type attribute (changetype), which is populated from a code list value (changetypevalue).

    Below is a table of the possible change types and the resultant actions required to maintain a latest feature view of the data for the specific feature type. Individual features should be targeted based on that feature type's unique identifier. In the majority of feature types, this will be the osid, but this is not always the case; therefore, please check the appropriate feature type documentation.

    changetypevalue
    Action

    New

    Insert as a new feature

    Moved From A Different Feature Type

    Insert as a new feature

    End Of Life

    Delete existing feature based on unique identifier

    Moved To A Different Feature Type

    A single feature may be updated multiple times in a single COU file when multiple changes occur within the selected COU frequency. Instead of suppressing all changes other than the last edit, the COU will contain all of the edits which have been made to that feature.

    To obtain the current 'live' view of a feature, the latest edit is required; all previous edits can be discounted. In essence, this requires the following two processes:

    1. Discarding all feature records with the exception of the latest Version Available From Date (versionavailablefromdate)

    2. Discarding all feature records that have a Version Available To Date (versionavailabletodate) populated, i.e. it is NOT NULL. These records will also have the Change Type Value (changetypevalue) of 'End Of Life' or 'Moved To A Different Feature Type'.

    In this scenario, every record is retained, giving a full lifecycle since the supply started of each feature. This will result in multiple records for each feature.

    To enable this in a database, the default primary keys (as defined in the provided DDL scripts) will have to be changed to also include the version available from and to dates (versionavailablefromdate, versionavailabletodate).

    Change-Only Update (COU) files are only available for CSV data supplies of the OS NGD. Further information about COU data supplies can be found on the COU supplies page.

    When processing COU supplies, it is essential that they are processed in the correct productVersion date order; therefore, in automated processes, we strongly recommend that you build in a test to ensure that the previous supply has been fully processed. For daily COU orders, that will be the previous day’s productVersion date; for monthly COU orders, that will be the preceding first of the month's productVersion date.

    Feature retention options

    Latest feature view

    Change type

    Version dates

    Full feature archive

    changetypevalue

    Feature types: Feature types are the most granular level, with objects (features) grouped by geometry or classification.

    The nine OS NGD data themes.

    Content in this section is ordered by themes, collections and feature types, mirroring the OS NGD data structure itself. This level of categorisation should make it easier and quicker for you to discover the data you need.

    For example, if you are interested in water or river data, then you should select 'OS NGD Water' from the card below or the left-hand-side navigation menu, then drill down through the collections to the water feature type/s that interest you.

    OS NGD themes


    Overview of the OS NGD data structure

    Infographic showing OS NGD terminology and data structure: themes, collections, feature types and features.
    OS NGD data structure: themes, collections, feature types and features.

    More in-depth information about OS NGD data terminology (themes, collections, feature types) is available from the – these pages cover core elements of OS NGD design, including available data formats and file naming, data schema versioning, access methods, data ordering and currency, attribute information for feature types, unique identifiers and coordinate reference systems.

    We recommend that you refer to the OS NGD Fundamentals pages as you work your way through this Data Structure section.

    Explore OS NGD data

    What's next?

    Getting started with an API project

    This guide walks you through using the OS Data Hub API Dashboard to create and manage API projects.

    OS NGD API – Features

    OS NGD API – Features provides access to OS NGD feature data, enabling you explore and visualise detailed OS data.

    OS NGD API – Tiles

    OS NGD API – Tiles provides access to scalable OS NGD vector tiles for a ready‑to‑use, customisable basemap you can use to build interactive maps of Great Britain.

    Explore OS NGD

    A high level summary of what the OS NGD is, how to access it and who can use it.

    Frequently asked questions on OS NGD data and the download service of OS Select+Build.

    Learn more about the OS NGD through our webinars and tutorials. Case studies demonstrate how customers across numerous sectors are already using and benefiting from OS NGD data.

    Learn about new data and access enhancements recently released for the OS NGD.

    Data structure pages provide more detailed information about data available for OS NGD themes, collections and feature types.

    Resources for styling OS NGD data.

    An example of OS API data showing a vector map of streets in turquoise, major routes in dark blue, and a central estuary in light blue.
    Example image of OS NGD API – Features data.
    Example image of OS NGD API – Tiles data.

    Who can use the OS NGD?

    What's the PSGA?

    The PSGA (Public Sector Geospatial Agreement) sets out how Ordnance Survey (OS) provides world-leading location data and expertise to the public sector across Britain. It supports the delivery of critical infrastructure and services, as well as working to help protect our environment. 

    Find out more about the PSGA by visiting the OS website, including the benefits of joining, instructions on how to access OS data, success stories, support, registration process information and instructions, and a PSGA Member finder tool to check if your organisation is already a member.

    Data Exploration Licence

    Discover OS NGD

    Explore OS NGD

    Get OS NGD

    OS Select+Build
    OS NGD APIs
    OS Data Hub
    Premium Plan or Public Sector Plan
    a Data Exploration Licence

    A list of the key benefits of OS NGD to customers.

    Our getting started guides will help you access, use and style OS NGD data.

    You'll also find in-depth information on OS NGD design, tutorials, webinars, and case studies.

    OS NGD Fundamentals covers the core elements of OS NGD design, including data formats, ordering and currency, and coordinate reference systems amongst other topics.

    Data structure pages provide more detailed information about data available for OS NGD themes, collections and feature types.

    Learn about new data and access enhancements recently released for the OS NGD.

    Try out OS NGD by downloading an area of sample data or visualising it online.

    Download OS NGD data using our bespoke download service, OS Select+Build.

    Access OS NGD data using the OS NGD APIs to get started using OS NGD within desktop, web and mobile applications.

    These pages should be used in conjunction with the more detailed pages available within the Data Structure section which are specifically focussed on the different OS NGD themes, collections and feature types.

    Discover OS NGD

    Explore OS NGD

    Get OS NGD

    COU supplies
    Data schema versioning
    Unique identifiers
    Coordinate reference systems
    Attribute information for feature types

    A high level summary of what the OS NGD is, how to access it and who can use it.

    Frequently asked questions on OS NGD data and the download service of OS Select+Build.

    Learn more about the OS NGD through our webinars and tutorials. Case studies demonstrate how customers across numerous sectors are already using and benefiting from OS NGD data.

    Learn about new data and access enhancements recently released for the OS NGD.

    Data structure pages provide more detailed information about data available for OS NGD themes, collections and feature types.

    Resources for styling OS NGD data.

    Try out OS NGD by downloading an area of sample data or visualising it online.

    Download OS NGD data using our bespoke download service, OS Select+Build.

    Access OS NGD data using the OS NGD APIs to get started using OS NGD within desktop, web and mobile applications.

    📣 OS NGD News

    🗃️ Data Structure

    🎨 Styling OS NGD Data

    Getting started with recipes

    What is a recipe?

    A recipe is a bespoke selection of OS NGD data which is made by a user within OS Select+Build. Recipes allow you to choose the OS NGD data that best fits your requirements.

    OS NGD data is structured by themes, collections, and feature types; the main advantage to this data structure is that you can easily find and select individual feature types across different themes and build your own recipes and data package/s containing only the data you are interested in. There's also the option to select all or only a few feature types from a single theme.

    Every new recipe you create will be stored in your OS Select+Build Recipe Library. This library will be visible to other people in your organisation. It provides a central place for colleagues to view and use recipes.

    Using OS Select+Build recipes

    Things to remember

    You can:

    • Delete a recipe

    • Edit an existing recipe (i.e. add or remove themes / feature types, or change attribute filtering or data schema versions)

    You can't:

    • Download the contents of an OS NGD data package using the grouped file function

    🆕 What's next?

    Once you've created your recipe, you'll need to add a data package to receive the data. Data packages allow you to select the format, update frequency and area of interest for the required data. The following guide will help you to create a data package from your new recipe:

    You might also like to try creating one of our recommended recipes:

    Editing OS Select+Build recipes

    Step-by-step instructions on how to edit OS Select+Build recipes.

    You can edit the content of an existing recipe to add or remove specific themes and feature types, or change attribute filters and data schema versions to pick a specific version of the data you need. You can also edit the name or description of an existing recipe to better represent what it provides.

    The following sub-sections on this page cover:

    How do I edit the name of my recipe?

    To edit a recipe's name:

    1

    Log into your account

    Click Login on the OS Data Hub menu bar to log into your account.

    Screenshot showing the OS Data Hub homepage.
    2

    Select Data from the menu bar to view your workspace.

    3

    Choose Downloads > OS Select+Build Recipe Library from the left hand side secondary navigation menu. You will then be taken to your organisation's OS Select+Build Recipe Library.

    4

    In your organisation's OS Select+Build Recipe Library, scroll or search for the recipe you want to edit.

    5

    Click on the name of the recipe to view the recipe details.

    6

    Click on the pencil icon next to the recipe name.

    7

    Enter the required changes to the recipe name in the dialog box.

    8

    To save your changes, simply click away from the edit box. The recipe's change log at the bottom of the page will update to reflect the change to the recipe name.

    To edit a recipe's description:

    1

    Click Login on the OS Data Hub menu bar to log into your account.

    2

    Select Data from the menu bar to view your workspace.

    3

    Choose Downloads > OS Select+Build Recipe Library from the left hand side secondary navigation menu. You will then be taken to your organisation's OS Select+Build Recipe Library.

    You can edit the content of a recipe to add or remove themes and feature types, change attribute filtering or switch between data schema versions. However, you can't edit a recipe if it has data packages linked to it that receive change-only updates (COUs) – please see the warning note below for instructions on how to solve this issue and create a copy of a recipe.

    To edit a recipe that doesn't have data packages linked to it that receive COUs:

    1

    Click Login on the OS Data Hub menu bar to log into your account.

    2

    Select Data from the menu bar to view your workspace.

    3

    Choose Downloads > OS Select+Build Recipe Library from the left hand side secondary navigation menu. You will then be taken to your organisation's OS Select+Build Recipe Library.

    Islands Address

    The OS Islands Address Collection is a complete, analytical and authoritative addressing dataset for Northern Ireland, the Channel Islands and the Isle of Man. It is designed to provide a detailed view of an address and its lifecycle.

    Collection applications

    The OS Islands Address Collection allows you to:

    • Keep your address data current with up-to-daily updates.

    • Utilise the richness of additional attribution about each address and analyse addresses by their classification, postal status and build status to create a detailed picture of a given area.

    • Access all addresses in Royal Mail’s Postcode Address File (PAF), Not Yet Built (NYB) and Multiple Residence (MR) datasets, with the ability to use PAF’s Unique Delivery Point Reference Number (UDPRN) and Unique Multiple Residence Reference Number (UMRRN) alongside the authoritative Unique Property Reference Number (UPRN).

    • Easily create mail shots using the Full Address attribute on the Royal Mail Address Feature Type.

    • Carry out spatial analysis and aggregation using the accurate rooftop coordinates provided for each address.

    • Easily identify and download addresses by pre-build, built and historic lifecycle stages.

    • Use the UPRN to easily link different data sets right down to a single address.

    • A full representation of an address as you can view both the Royal Mail and Local Authority representations of it.

    • Up-to-daily updates to data.

    • The simplified data model means there’s no need to be an addressing expert to use the data.

    • Plug and play – the data is simple and quick to implement as you don't need to pre-process it before you use it.

    Frequently asked questions (FAQs) about this collection and detailed answers are available from the .

    Northern Ireland, the Channel Islands, and the Isle of Man.

    European Terrestrial Reference System 89 (EPSG: ETRS89).

    The earliest date on which you can request a one-off snapshot of a date in the past for data in this collection is noted at the top of the individual feature type pages.

    GeoPackage or CSV (comma-separated values).

    Islands Address data can be accessed through the via OS Select+Build, the bespoke OS NGD download service. It can't be accessed through OS NGD API – Features or OS NGD API – Tiles.

    • Included in the (PSGA) – therefore, it's free at point of use for Public Sector organisations.

    • Available to OS Partners for commercial resell in your solutions.

    OS NGD Sample Data

    Download OS NGD sample data or visualise it online.

    An is available that lets you visualise product sample data online for three areas (Exeter, Newport and Inverness).

    Sample data for most OS NGD feature types are available. The sample data always use the latest data schema version available for each feature type.

    Sample data are available to download from the for the following OS NGD collections:

    OS NGD Collection
    Available Formats
    Sample Data Coverage

    Other Alias

    The Other Alias Component provides alternate names for counties, localities and thoroughfares. County aliases provide alternate names for a county, including Traditional, Administrative and Former Postal County information. Locality aliases include old short-form names, local names and Postally Not Required (PNR) Localities. Thoroughfare Alias information provides replacement Thoroughfare names for a given Locality, Thoroughfare or Dependent Thoroughfare combination.

    For more information about components of the Other Alias table, please consult chapter six 'Alias' of the .

    The earliest date on which you can request a one-off snapshot of a date in the past for data in this feature type is 08 October 2026.

    Any data temporally filtered earlier than the specified earliest date noted above for the data schema version may contain data inconsistencies.

    More information about temporal filtering is available from the .

    The following sub-sections provide details about the attributes included with this related component, their data types in the different output formats, and other important metadata about them.

    Ordnance Survey derived primary key providing a unique row identifier assigned to enable indexing for efficient querying.

    Delivery Point Alias

    The Delivery Point Alias Component provides alias data related to a delivery point address. It sources data from Royal Mail's Delivery Point Alias (DPA) table. DPA information provides additional Delivery Point Information, including Trading Names and Building Name details where a Building Number is the official building identifier.

    For more information about the DPA table, please consult chapter six 'Alias' of the .

    The earliest date on which you can request a one-off snapshot of a date in the past for data in this feature type is 08 October 2026.

    Any data temporally filtered earlier than the specified earliest date noted above for the data schema version may contain data inconsistencies.

    More information about temporal filtering is available from the .

    The following sub-sections provide details about the attributes included with this related component, their data types in the different output formats, and other important metadata about them.

    Ordnance Survey derived primary key providing a unique row identifier assigned to enable indexing for efficient querying.

    OS NGD Administrative and Statistical Units

    Administrative and Statistical Units are the geographical extent of administrative, legislative, regulatory, electoral, statistical, governance, service delivery and activity management areas. OS NGD Administrative and Statistical Units Theme data is the most comprehensive and high-quality set of area data available for Great Britain ever produced by OS. You can use the datasets to perform quick and accurate searches as well as high-level visualisation and spatial analysis of features.

    The provides a definitive dataset of administrative and electoral boundaries and their names for England, Wales and Scotland. Government Statistical Service (GSS) codes are contained within the data and are supplied by the Office for National Statistics (ONS) and the National Records of Scotland (NRS).

    As of the end of March 2026, the theme now also includes the , and Collections. These are notional geographies which have been algorithmically derived from other OS NGD data.

    • The three new retail areas feature types in the OS Functional Areas Collection define the notional geographic extents of retail locations across Great Britain, identifying clusters of buildings with retail addresses.

    Boundaries

    The OS Boundaries Collection provides a definitive dataset of administrative and electoral boundaries and their names for England, Wales and Scotland. Government Statistical Service (GSS) codes are contained within the data and supplied by the Office for National Statistics (ONS) and the National Records of Scotland (NRS).

    The OS Boundaries Collection allows you to:

    • Access a seamless coverage of administrative and electoral boundaries across Great Britain.

    • Utilise the key boundaries for Great Britain, which have been designed to be used in multiple applications including GIS and web mapping applications.

    source_path_to_csv_file\source_name_of_csv_file.csv
    '
    WITH (
    FORMAT = 'CSV',
    FIRSTROW = 2
    );
    destination_schema
    .
    destination_table
    ADD new_geometry_column_name geometry;
    -- Set new geometry column using existing WKT column
    UPDATE destination_schema.destination_table
    SET [new_geometry_column_name] = geometry::STGeomFromText(destination_table.geometry, /* EPSG_CODE_OF_GEOM */);
    -- Optional drop original WKT column
    ALTER TABLE destination_schema.destination_table
    DROP COLUMN geometry;

    Delete existing feature based on unique identifier

    Modified Attributes

    Update the record (see section below)

    Modified Geometry

    Update the record (see section below)

    Modified Geometry And Attributes

    Update the record (see section below)

    📖 OS NGD Explained

    ❓ FAQs

    👩‍🏫 OS NGD Webinars, Tutorials and Case Studies

    📣 OS NGD News

    🗃️ Data Structure

    🎨 Styling OS NGD Data

    🗺️ OS NGD Sample Data

    📥 OS Select+Build

    📌 OS NGD APIs

    📖 OS NGD Explained

    ❓ FAQs

    👩‍🏫 OS NGD Webinars, Tutorials and Case Studies

    📣 OS NGD News

    🗃️ Data Structure

    🎨 Styling OS NGD Data

    👨‍🏫 OS NGD Explained

    Covering what the OS NGD is, how to access it and who can use it.

    ▶️ Getting started

    Our getting started guides will help you access, use and style OS NGD data.

    You'll also find in-depth information on OS NGD design, tutorials, webinars, and case studies.

    📖 OS NGD Fundamentals

    OS NGD Fundamentals covers the core elements of OS NGD design, including data formats, ordering and currency, and coordinate reference systems amongst other topics.

    🗃️ Data Structure

    Data structure pages provide more detailed information about data available for OS NGD themes, collections and feature types.

    📣 OS NGD News

    Learn about new data and access enhancements recently released for the OS NGD.

    🗺️ OS NGD Sample Data

    Try out OS NGD by downloading an area of sample data or visualising it online.

    📥 OS Select+Build

    Download OS NGD data using our bespoke download service, OS Select+Build.

    📌 OS NGD APIs

    Access OS NGD data using the OS NGD APIs to get started using OS NGD within desktop, web and mobile applications.

    OS Product Roadmap

    Rich attribution ensures the data is straightforward to navigate and query.

  • Persistent unique identifiers with lifecycle information.

  • The ability to select addresses from a specific lifecycle state (for example, Built Address and Pre-Build Address).

  • Full UK address coverage available via accessing the OS GB Address and OS Islands Address Collections together.

  • Cross-references make it easy for you to link data in this collection with data from other OS NGD collections.

  • Key elements

    FAQs

    Coverage

    Default coordinate reference system

    Temporal filtering

    Supply formats

    Supply mechanism

    Using our data

    FAQs page
    OS Data Hub
    Public Sector Geospatial Agreement
    Examples of Built Address, Pre-Build Address and Royal Mail Address features and the attribution provided for them. The visualisation shows an image of completed house and a house under construction. Pop ups against each image show what example attribution might look like for the Built Address features, Pre-Build Address features and Royal Mail Address features.
    Examples of Built Address, Pre-Build Address and Royal Mail Address features and the attribution provided for them.
    Screenshot showing the one-off snapshot check box option when creating a new data package in OS Select+Build in the OS Data Hub.
    Screenshot of OS Select+Build during the new data package creating stage showing the one-off snapshot check box option selected and a date selected.
    Diagram showing a worked example of data schema versioning in the OS NGD. The diagram is explained fully in the accompanying text on the page.

    OS NGD Address

    OS NGD Administrative and Statistical Units

    OS NGD Buildings

    OS NGD Geographical Names

    OS NGD Land

    OS NGD Land Use

    OS NGD Structures

    OS NGD Transport

    OS NGD Water

    📝 Code Lists

    Access all of the code lists for the OS NGD.

    📖 OS NGD Fundamentals

    OS NGD Fundamentals covers the core elements of OS NGD design, including available data formats and file naming, data schema versioning, access methods, data ordering and currency, attribute information for feature types, unique identifiers and coordinate reference systems.

    ▶️ Getting Started

    Our getting started guides will help you access, use and style OS NGD data. You'll also find FAQs, in-depth information on OS NGD design, and webinars, tutorials and case studies.

    📣 OS NGD News

    Learn about new data and access enhancements recently released for the OS NGD, planned future data enhancements on our roadmap, the change log, recent data improvements, and recent announcements.

    ⚙️ Data and Service Status

    Find out about OS NGD planned maintenance, any live service disruption, current data issues and resolved data issues.

    🗺️ OS NGD Sample Data

    Download OS NGD sample data or visualise it online.

    OS NGD Fundamentals pages
    Image showing a simple map of Great Britain. The 9 OS NGD data themes names are listed: Address, Administrative and Statistical Units, Buildings, Geographical Names, Land, Land Use, Structures, Transport, and Water.
    Example image showing OS NGD Address data. A background map is included for context.
    Example image showing data from the OS NGD Administrative and Statistical Units Theme. A background map is included for context.
    Example image showing data from the OS NGD Buildings Theme. A background map is included for context.
    Example image showing data from the OS NGD Geographical Names Theme. A background map is included for context.
    Example image showing data from the OS NGD Land Theme. A background map is included for context.
    Example image showing data from the OS NGD Land Use Theme. A background map is included for context.
    Example image showing data from the OS NGD Structures Theme. A background map is included for context.
    Example image showing data from the OS NGD Transport Theme. A background map is included for context.
    Example image showing data from the OS NGD Water Theme. A background map is included for context.
    <PORTNUMBER>
    active_schema=
    <TARGETSCHEMA>
    "
    <PATHTOGEOPACKAGE>

    This will create twp tables in the example_schema schema:

    Load the GeoPackage into a PostgreSQL database using the ogr2ogr program

    ogrinfo

    <USERNAME>, <PASSWORD>, <DATABASENAME>, <HOST>, <PORTNUMBER> are the connection details of the target PostgreSQL database.

    <TARGETSCHEMA> is the schema in the database that the layers should be loaded into. If this doesn’t exist or if it is omitted, they will be loaded into the default schema, the default is usually the ‘public’ schema.

    Example:
    ogrinfo wtr_ntwk_waterlinkset.gpkg -so -al
    ogrinfo detailed output
    INFO: Open of `C:\wtr_ntwk_waterlinkset.gpkg'
          using driver `GPKG' successful.
    Layer name: wtr_ntwk_waterlinkset
    Geometry: Unknown (any)
    Feature Count: 116
    Extent: (209562.134000, 79229.510000) - (341688.834000, 853194.875000)
    Layer SRS WKT:
    PROJCRS["OSGB 1936 / British National Grid",
    [...]
    ogr2ogr -f PostgreSQL "PG:user=example_user password=example_password dbname=postgres host=localhost port=5432 active_schema=example_schema" wtr_ntwk_waterlinkset.gpkg
    schemaname     | tablename
    ---------------+---------------------------------
    example_schema | wtr_ntwk_waterlinkset
    example_schema | wtr_ntwk_waterlinkset_wtrlinkref
    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
    4

    Select the recipe you want to edit

    In your organisation's OS Select+Build Recipe Library, scroll or search for the recipe you want to edit.

    5

    View recipe details

    Click on the name of the recipe to view the recipe details.

    6

    Click the edit icon next to the recipe name

    Click on the pencil icon next to the recipe name.

    7

    Change the description of the recipe

    Enter the required changes to the recipe description in the dialog box.

    8

    Save changes to the recipe

    To save your changes, simply click away from the edit box. The recipe's change log at the bottom of the page will update to reflect the change to the recipe description.

    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
    4

    Select the recipe you want to edit from the list

    In your organisation's Recipe Library, scroll or search for the recipe you want to edit.

    5

    Edit recipe data

    Click on the recipe you plan to edit to add and remove themes and feature types, or change attribute filtering or data schema versions.

    Screenshot of the OS Select+Build Recipe details screen with the Recipe actions dropdown open, showing where you can share, edit or delete a recipe.
    6

    Save changes to your recipe

    Add a description of the change you have made, then select Save changes.

    Editing recipe names

    Editing recipe descriptions

    Editing the content of recipes

    Navigate to the OS Data Hub workspace

    Navigate to the OS Select+Build Recipe Library

    Select the recipe you want to edit

    View recipe details

    Click the edit icon next to the recipe name

    Change the name of the recipe

    Save changes to the recipe

    How do I edit the description of my recipe?

    Log into your OS Data Hub account

    Navigate to the OS Data Hub workspace

    Navigate to the OS Select+Build Recipe Library

    How do I edit a recipe?

    Log into your OS Data Hub account

    Navigate to the OS Data Hub workspace

    Navigate to the OS Select+Build Recipe Library

    Recipes with data packages linked to them that receive COUs

    You can't edit a recipe if it has data packages linked to it that receive change-only updates (COUs). To get round this issue, you'll need to create a copy of the recipe and then edit that copy.

    To create a copy of a recipe:

    • Log into your OS Data Hub account.

    • Select Data from the main menu.

    • Choose Downloads > OS Select+Build Recipe Library from the secondary navigation menu.

    • From your list of recipes, click on the name of the recipe you wish to edit, then click on the Recipe actions dropdown and select Edit recipe.

    • When the 'Recipe cannot be edited' warning pop up appears, click the Copy recipe button.

    • Choose a suitable name for your copied recipe, then click Create recipe.

    The copied recipe will appear in your OS Select+Build Recipe Library and you can now edit it following the .

    OS Data Hub
    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
    A screenshot of the OS Data Hub home page showing the sign up and log in buttons in the top right hand corner
    Screenshot showing the OS Data Hub homepage.
    A screenshot of the OS Data Hub home page showing the sign up and log in buttons in the top right hand corner
    Screenshot showing the OS Data Hub homepage.
    A screenshot of the OS Data Hub home page showing the sign up and log in buttons in the top right hand corner
    Edit the name or description of a recipe
  • Create multiple data packages from a single recipe

  • Delete a data package

  • Search through your organisation's recipes in the OS Select+Build Recipe Library using the recipe name, description, or content (i.e. themes, collections, or feature types)

  • Search through your organisation's data packages in the Data packages list screen using the data package name, data package number, or product name

  • Collect your data package(s) via the OS Data Hub or the OS Downloads API

  • Share a recipe with another organisation that has access to OS Select+Build

  • ▶️ Getting started with attribute filtering

    Use attribute filtering to narrow down data selection beyond the feature type level, creating bespoke recipes of OS NGD data:

    Check if filters are used in a recipe

    Add attribute filters to a new recipe

    Add attribute filters to an existing recipe

    Worked example of creating a simple filter

    Worked example of creating a nested filter

    📋 Managing recipes

    Create and manage OS Select+Build recipes within your organisation:

    Create a new recipe

    Find my Recipe Library

    Check what's in a recipe

    Delete a recipe

    ✏️ Editing recipes

    Edit your OS Select+Build recipes to improve your recipe library:

    Edit the name of a recipe

    Edit the description of a recipe

    Edit a recipe

    📔 Sharing recipes

    Share OS Select+Build recipes with external organisations to improve collaboration:

    Share a recipe

    Accept a shared recipe

    Reject a shared recipe

    📚 Getting started with data packages guide

    🆕

    GeoPackage, CSV

    Three 5km x 5km areas

    GeoPackage, CSV

    Three 5km x 5km areas

    GeoPackage, CSV

    Three 5km x 5km areas

    GeoPackage, CSV

    Three 5km x 5km areas

    GeoPackage, CSV

    Three 5km x 5km areas

    • Sample data always use the latest data schema version available for each collection.

    • Sample data for the collections are available in GeoPackage and CSV (comma-separated values) formats.

    • One zip file of sample data is provided per collection. Within each of these zip files, the individual feature types for each collection are separated into their own folder.

    • Sample data are not available for the OS Boundaries, OS Islands Address or OS NI Postcodes Collections.

    • The standard sample data areas for each collection typically cover three 5km x 5km areas in Great Britain: Exeter (England), Newport (Wales) and Inverness (Scotland). Exceptions to the standard areas are highlighted in the note below.


    In-depth information on OS NGD data, including structure, applications and news:

    There are now two options available for you to interact with OS NGD sample data:

    • You can visualise sample data online through the OS NGD Data Viewer.

    • You can download sample data (in GeoPackage or CSV formats) from the OS Data Hub.

    OS NGD Data Viewer

    Downloadable sample data

    OS NGD Data Viewer
    OS Data Hub

    Things to note

    • OS Transport Network Collection sample data are available for Sheffield, Newport and Inverness; there are no sample data for Exeter.

    • OS Water Features Collection sample data are available for Plymouth, Newport and Inverness; there are no sample data for Exeter.

    Please note that as we're publishing three relatively small (5km x 5km) sample data areas for most of the collections, the following three feature types are not represented within these areas and their record counts will therefore be zero in the sample data:

    • Landform Point (OS Land Features Collection)

    • Maintenance Point (OS RAMI Collection)

    Explore OS NGD

    Data Types: String (GPKG), String (CSV)
  • Nullable: false

  • Max Length: 36

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.0

  • Unique Delivery Point Reference Number (UDPRN) assigned by Royal Mail as a persistent identifier, belonging to the feature of which the alias relates to.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0

    Date of the feature version to which this related component applies. This is used along with the Feature Type ID attribute to join the component to the Royal Mail Address Feature Type.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0

    Contains alias name text, derived from either Thoroughfare, Locality or County source tables.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 150

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0

    Indicates the source alias table from which the record has been derived.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 25

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0

    Indicates the alias subdivision applicable to the record.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 30

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0

    Royal Mail raw alias component information, containing concatenated components and codes as a single string attribute.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 150

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0

    Other Alias Component for Royal Mail Address Feature Type data schema version 2.0 onward

    Customers taking data schema version 2.0 onward of the Royal Mail Address Feature Type in GeoPackage format will receive the following in their data package:

    • Feature type: Royal Mail Address

    • Related components: Multiple Residence, Delivery Point Alias and Other Alias

    However, the three related components (Multiple Residence, Delivery Point Alias and Other Alias) will only be provided for Royal Mail Address features if the Description attribute is 'Postcode Address File'. Against all other Royal Mail Address features, the related components will be populated as null.

    Please note that the Delivery Point Alias and Other Alias Related Component tables are included in product design for future compatibility but are not currently populated; customers should expect these files to be empty until a future data enhancement enables OS to supply the Royal Mail alias data. Please see the for more information.

    Temporal filtering

    Related component attributes

    aliasid

    Royal Mail Programmer's Guide
    Getting started with temporal filtering guide

    udprn

    featuretypeversiondate

    alias

    aliasrecordtype

    aliastype

    aliascode

    Data Types:
    String (GPKG), String (CSV)
  • Nullable: false

  • Max Length: 36

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.0

  • Unique Delivery Point Reference Number (UDPRN) assigned by Royal Mail as a persistent identifier, belonging to the feature of which the alias relates to.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0

    Date of the feature version to which this related component applies. This is used along with the Feature Type ID attribute to join the component to the Royal Mail Address Feature Type.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0

    Contains alias name text, derived from the Delivery Point Alias (DPA) source table.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 75

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0

    Indicates the source alias table from which the record has been derived.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 25

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0

    Describes the subdivisions of Delivery Point Alias (DPA) table.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0

    Describes the currency of the Delivery Point Alias (DPA) provided.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 10

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0

    Royal Mail raw alias component information, containing concatenated components and codes as a single string attribute.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 150

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0

    Delivery Point Alias Component for Royal Mail Address Feature Type data schema version 2.0 onward

    Customers taking data schema version 2.0 onward of the Royal Mail Address Feature Type in GeoPackage format will receive the following in their data package:

    • Feature type: Royal Mail Address

    • Related components: Multiple Residence, Delivery Point Alias and Other Alias

    However, the three related components (Multiple Residence, Delivery Point Alias and Other Alias) will only be provided for Royal Mail Address features if the Description attribute is 'Postcode Address File'. Against all other Royal Mail Address features, the related components will be populated as null.

    Please note that the Delivery Point Alias and Other Alias Related Component tables are included in product design for future compatibility but are not currently populated; customers should expect these files to be empty until a future data enhancement enables OS to supply the Royal Mail alias data. Please see the for more information.

    Temporal filtering

    Related component attributes

    aliasid

    Royal Mail Programmer's Guide
    Getting started with temporal filtering guide

    udprn

    featuretypeversiondate

    alias

    aliasrecordtype

    aliascategory

    aliascurrency

    aliascode

    The two postcodes collections provide complete, analytical and authoritative postcode datasets for Great Britain and Northern Ireland; they are designed to provide a detailed view of postcodes. Full UK postcode coverage is available if you combine data from the two collections as the identical schemas enable compatibility.

    The OS NGD Administrative and Statistical Units Theme is made up of four collections, which in turn are comprised of 23 feature types. The four collections are OS Boundaries, OS Functional Areas, OS GB Postcodes and OS NI Postcodes.

    OS NGD Administrative and Statistical Units Theme data structure diagram showing the theme name, collection names and feature type names.

    At least one of the following four unique identifiers is provided with each feature within the OS NGD Administrative and Statistical Units Theme:

    • OSID (Ordnance Survey Identifier): The primary identifier and unique key for feature types in the OS Boundaries Collection.

    • TOID (Topographic Identifier): An additional secondary identifier for feature types in the OS Boundaries Collection which can aid further data linking. TOIDs are an optional attribute and therefore will not always be provided with every feature.

    • Feature ID: For a small number of feature types in OS NGD where it is not possible or necessary to have identifiers that persist over time, the Feature ID is used as the primary identifier. The Postcode Unit Area, Retail Area Aggregated, Retail Area Major and Retail Area Minor Feature Types in this theme use this unique identifier. The notional extents of the retail area features and Postcode Unit Area features are regenerated periodically (for example, monthly for the latter), at which point all features will get a new Feature ID.

    • Postcode: The primary identifier for the Postcode Unit Point Feature Types and an important identifier for the Postcode Unit Area Feature Type in this theme (Postcode Unit Area features represent postcode parts, not whole postcodes, so their primary identifier is Feature ID). Postcode is the identifier assigned by Royal Mail for the purposes of mail delivery. A postcode is an abbreviated form of address, made up of combinations of between five and seven alphanumeric characters. These alphanumeric characters are used by Royal Mail to help with the automated sorting of mail. A postcode may cover between 1 and 100 addresses.

    • Geometry ID: A non-persistent identifier currently used in the Postcode Unit Area Feature Type only, to identify where postcode part geometries are coincident. Some of the OS NGD feature types are designed for multiple features to have exactly the same polygon, called coincident geometries. For example, a residential tower block represented by a single building may have hundreds of addresses located in it with several different postcodes. In this scenario, a Postcode Unit Area feature would represent each postcode as an area (called a postcode part), all of which would share the same geometry (derived from the building representing the tower block). All of the coincidental geometries would have the same Geometry ID. The Geometry ID is used to identify which other features share that same geometry and it can support key use cases (for example, it can be used to create a full surface representation of postcode unit areas). Metadata about the number of coincident geometries is supplied.

    • GSS (Government Statistical Service) codes: A system of referencing for administrative, electoral, and statistical geographies.

    • The following introductory guides (covering the benefits, key features and attribution available for each collection) are available on our More than Maps site:

      • Introductory guide to OS Boundaries Collection data

      • Introductory guide to OS Functional Areas Collection data

      • Introductory guide to OS NGD Postcodes data

    • Find out how new can help you to unlock new insights and build a richer postcode picture for Great Britain and Northern Ireland, including combining improved geometries with clearer connections to postal areas, districts and sectors, as well as addresses, buildings, and land cover.

    • : Find out how the new retail areas data is useful for central government in the creation of policy relating to local neighbourhoods and can be used to show how investment impacts areas with similar characteristics. Discover how local authorities can use this foundational dataset for evidence-gathering and to define patterns of economic activity.

    Introduction to the theme

    OS Boundaries Collection
    OS Functional Areas
    OS GB Postcodes
    OS NI Postcodes

    Data structure

    Unique identifiers

    Please note that Boundary High Water Mark, Ceremonial County, Historic County, Historic European Region, and Polling District features in the OS Boundaries Collection do not have GSS codes or TOIDs allocated to them; however, they do have OSIDs allocated to them. Polling District features have an additional unique identifier of Polling District Identifier.

    Useful links

    View and interrogate the full hierarchy of boundaries across Great Britain, from 'Parish Or Community' to 'Country'.

  • Use GSS codes (where available) to link OS Boundaries Collection polygons with other geographies, helping you perform detailed statistical analysis to better support your decision and policy making.

  • Identify areas of sea water and land present within coastal boundary polygons to get a better understanding of the land areas of a boundary.

  • Perform powerful analytics, underpinned by unrivalled OS accuracy, using additional enriched attribution (detailed below).

    • The data is updated twice a year in May and October.

    • Plug and play – the data is simple and quick to implement as you don't need to pre-process it before you use it.

    • Persistent unique identifiers with lifecycle information.

    • New Country Feature Type included, giving polygons for England, Wales and Scotland.

    • New Upper and Lower Tier Local Authority Feature Types included, which improve alignment between OS data and ONS data.

    • Rich attribution ensures the data is straightforward to navigate and query. The enriched, additional attribution includes, but is not limited to, the following:

      • Boundary Parent reference values (where appropriate) to indicate the hierarchy of boundaries (for example, a District Ward will reference the District).

      • Land area, tidal area and total area values in hectares.

      • An 'Is Borough' attribute to identify boundaries which are also boroughs.

    Frequently asked questions (FAQs) about this collection and detailed answers are available from the FAQs page.

    Great Britain.

    British National Grid (EPSG: 27700).

    The earliest date on which you can request a one-off snapshot of a date in the past for data in this collection is noted at the top of the individual feature type pages.

    GeoPackage, CSV (comma-separated values) or vector tiles.

    Accessed through the OS Data Hub via:

    • OS Select+Build (the bespoke OS NGD download service)

    • OS NGD API – Tiles

    It can't be accessed through OS NGD API – Features.

    • Included as part of OS OpenData and therefore can be used for free.

    • Also available for organisations to try out for free for six months under the Data Exploration Licence; this licence is primarily designed for organisations either considering becoming an OS Partner or who want to trial OS data before working with an existing OS Partner.

    Collection applications

    Example image showing what a selection of the feature types in the OS Boundaries Collection look like in the data. A background map has been included to provide context.
    Example image showing what a selection of the feature types in the OS Boundaries Collection look like in the data. A background map has been included to provide context.

    Key elements

    FAQs

    Coverage

    Default coordinate reference system

    Temporal filtering

    Supply formats

    Supply mechanism

    Using our data

    ✨ OS NGD Key Benefits to Customers

    ▶️ Getting started

    📖 OS NGD Fundamentals

    🗃️ Data Structure

    📣 OS NGD News

    🗺️ OS NGD Sample Data

    📥 OS Select+Build

    📌 OS NGD APIs

    Coordinate reference systems

    Find out what coordinate reference systems are available for OS Select+Build and the OS NGD APIs.

    Coordinate reference systems available for OS Select+Build

    OS Select+Build is the download service that gives you access to OS NGD data; it's available via the OS Data Hub.

    The GeoPackage and CSV formats accessible via OS Select+Build are available in four different CRSs dependent on your data selection:

    • British National Grid (BNG: EPSG: 27700)

    • British National Grid + ODN Height (EPSG: 7405)

    • European Terrestrial Reference System (ETRS89: EPSG: 4258)

    • World Geodetic System (WGS84: EPSG: 4326)

    The following table outlines the default CRS used by each OS NGD collection in OS Select+Build:

    Collection
    Default Coordinate Reference System for OS Select+Build

    When , you can choose what CRS you'd like to receive the data in.

    If you don't choose a particular CRS for your data package, OS Select+Build will automatically select the default CRSs for the feature types in your data package for you.

    The GeoJSON format accessible via OS NGD API – Features is available in four different CRSs:

    • British National Grid (BNG: EPSG: 27700).

    • World Geodetic System (WGS84: EPSG: 4326)

    • British National Grid + ODN Height (EPSG: 7405)

    • Web Mercator (EPSG: 3857)

    The vector tiles format accessible via OS NGD API – Tiles is available in two different CRSs:

    • British National Grid (BNG: EPSG: 27700)

    • Web Mercator (EPSG: 3857)

    Coordinate Reference System
    Definition

    Where OS provides the option to receive data with geometries expressed in latitude and longitude format, they will be transformed into the ETRS89 (European Terrestrial Reference System 1989, EPSG: 4258). Where the option is stated to provide WGS84 (World Geodetic System 1984, EPSG: 4326), the embedded coordinate reference system (CRS) value of 4326 will be provided; however, the data will actually be in ETRS89 (EPSG: 4258).

    In practice, the difference will be negligible – that is, significantly smaller than the stated accuracy of the data being transformed. Both OS NGD APIs offer data as Web Mercator (EPSG: 3857), but this will be a projection using the same ETRS89 data, labelled as WGS84, as the base CRS.

    The reason OS does this is due to the shifting nature of WGS84, which is adjusted yearly (to account for global tectonic motion) and would therefore require additional date metadata to be a faithful representation of this CRS. ETRS89 is a 'plate fixed' static system that allows for a consistent transformation to be performed. Many software applications / libraries require data to be provided in WGS84 however, so by embedding the WGS84 CRS, we are facilitating these use cases without compromising the positional accuracy of our data.

    Downloading with OS Select+Build

    Discover how to download OS NGD data using our bespoke download service, OS Select+Build.

    What is OS Select+Build?

    OS Select+Build is our download service that gives you access to OS NGD data. You can use it to choose the OS NGD data you need (by theme, collection and feature type) and select how you want to download your data as a data package. OS Select+Build is available via the OS Data Hub.

    Infographic showing the steps involved when using OS Select+Build on the OS Data Hub.

    OS NGD data from OS Select+Build can be downloaded in two file formats: GeoPackage and CSV. Detailed information on the supply options available can be found on the in the .

    What's different about OS Select+Build?

    For the first time, you can select only the data you need rather than taking off-the-shelf OS products, such as AddressBase or OS MasterMap Topography Layer. For example, if you're only interested in buildings information, then you just create a recipe featuring only the OS NGD Buildings Theme and the content (feature types) you require within it.

    OS Select+Build also allows you to combine data from different OS NGD collections. For example, you could select the Building and Building Access Location Feature Types (which are both in the OS Building Features Collection of the OS NGD Buildings Theme) and the Land Point and Landform Feature Types (which are both in the OS Land Features Collection of the OS NGD Land Theme):

    Screenshot showing an example of creating a new recipe using OS Select+Build in the OS Data Hub.

    The screenshot above shows what selecting this data would look like using OS Select+Build. The secondary navigation menu on the left-hand side of the screen is where you select the feature types you want from the tree view of the OS NGD themes, collections, and feature types, and where you can apply filters to the feature types (if needed). The right-hand side panel displays the definition for the feature type you've selected and lists all the attributes present within it.

    Learn more about recipes in the .

    Adding a data package to your recipe allows you to select the area, format, and update frequency to receive for your data. Learn more about this in the .

    Take a look at the following getting started guides to begin using OS Select+Build to access OS NGD data:


    Detailed documentation on OS NGD design and practical guides on how to apply OS NGD data:

    In-depth information on OS NGD data, including structure, applications and news:

    Managing OS Select+Build recipes

    Step-by-step instructions on how to create and manage your OS Select+Build recipes.

    This guide will help you get started with creating, managing and deleting recipes in your OS Select+Build Recipe Library.

    The following sub-sections on this page cover:

    🔃 How do I create a new recipe?

    Before you create a data package to receive your OS NGD data, you'll need to create a recipe.

    To create a new recipe:

    1

    Log into your account

    Click Login on the OS Data Hub menu bar to log into your account.

    Screenshot showing the OS Data Hub homepage.
    2

    Select Data from the menu bar to view your workspace.

    3

    Choose Downloads > OS Select+Build Recipe Library from the left-hand-side secondary navigation menu.

    4

    Click the Create a new recipe button at the top right-hand-side of the screen.

    5
    • Give your recipe a descriptive name.

    • Add a detailed description for your recipe.

    • Select your OS NGD data by choosing the themes, collections and feature types you want to include in your recipe.

    6

    Click the Create recipe button. Your new recipe will now instantly be available in your OS Select+Build Recipe Library.

    Any recipes created by your organisation will be stored in your OS Select+Build Recipe Library in the OS Data Hub.

    To find your OS Select+Build Recipe Library:

    1

    Click Login on the OS Data Hub menu bar to log into your account.

    2

    Select Data from the menu bar to view your workspace.

    3

    Choose Downloads > OS Select+Build Recipe Library from the secondary navigation menu. You will then be taken to your organisation's OS Select+Build Recipe Library.

    You can easily check details about any of your organisation's existing recipes, including a recipe's name, description, creation date, author, the filters used (if applicable), and what OS NGD themes, collections and feature types are included in a recipe.

    To check what's in an existing recipe:

    1

    Click Login on the OS Data Hub menu bar to log into your account.

    2

    Select Data from the menu bar to view your workspace.

    3

    Choose Downloads > OS Select+Build Recipe Library from the secondary navigation menu. You will then be taken to your organisation's OS Select+Build Recipe Library.

    A recipe can be deleted within your recipe library. You can do this if you are the author of the recipe or an admin user.

    To delete a recipe:

    1

    Click Login on the OS Data Hub menu bar to log into your account.

    2

    Select Data from the menu bar to view your workspace.

    3

    Choose Downloads > OS Select+Build Recipe Library from the secondary navigation menu. You will then be taken to your organisation's OS Select+Build Recipe Library.

    Town and city planning recipe guide

    A guide with detailed step-by-step instructions outlining how you can create a recipe in OS Select+Build to identify the level of access to natural areas from existing addresses.

    What is the town and city planning recipe?

    The guide below provides a geospatial toolkit to help you identify the level of access to natural areas from existing addresses, both residential and commercial; its step-by-step instructions outline how to select relevant pieces of addressing, administrative and statistical units, buildings, geographical names, land use and water data from the OS NGD and weave them into a recipe.

    You can adapt the suggested town and city planning recipe at the recipe creation or editing stage so that it fully meets your needs. No filters are used in this recipe (you can filter the data later on in your GIS of choice).

    For this recipe guide, we define a natural area as a location where a member of the public can access an unbuilt area for the purpose of leisure; this includes playing fields, parks, woodland, grassland, trails and rivers.

    Use cases

    The recipe will be useful for town and city planners who want to assess access to natural areas from existing commercial and residential addresses, and provide evidence to help inform compliance with Natural England's Green Infrastructure Framework. Access to natural areas for residential properties should ideally be available within a radius of 300m (roughly a 5 minute walk).

    Suggested feature types

    We suggest you include the following 10 feature types in the town and city planning recipe:

    Theme
    Collection
    Feature Type(s)

    To create the town and city planning recipe in OS Select+Build:

    1

    Click Log in on the OS Data Hub menu bar to log into your account.

    2

    Select Data from the menu bar to view your workspace.

    3

    Choose Downloads > OS Select+Build Recipe Library from the left-hand-side secondary navigation menu.

    More information on creating, editing and deleting recipes in OS Select+Build and on adding attribute filters to recipes can be found in the following guides:

    Once you've created your recipe, you'll need to add a data package to receive the data. Data packages allow you to select the format, update frequency and area of interest for the required data.

    The following guide will help you to create a data package from your new recipe:

    Once you've created your recipe and added a data package to it to receive the data, you can import the data into your chosen GIS to analyse it or create maps.

    The following guide shows you how to identify the level of access to natural areas from existing residential and commercial addresses; it demonstrates how to use QGIS to standardise the geometry of datasets you've downloaded and, if required, standardise the data into one layer using common attributes:

    Other Classification

    The Other Classification Related Component provides additional classification data beyond that held by Local Authorities for an address record. This data type contains VOA Council Tax and Non-Domestic Rate classification information in the form of Special Category Codes (SCAT) and Primary Descript\ion codes where VOA information has been matched to a Local Authority address. Note that VOA classifications are only available for England and Wales.

    Data schema versioning

    The following table provides details about this related component’s data schema versions, including the reasons behind the changes and the related launch date when each version went live.

    Data schema version table

    Version ↓
    Launch Date
    Latest Date
    Change

    3.0

    Please see for in-depth information about data schema versioning in the OS NGD.

    Temporal filtering allows you to order a one-off snapshot of data from the OS NGD from a current or past date. It is an optional step when you create a new data package in OS Select+Build (the OS NGD download service).

    The earliest and latest dates on which you can request a one-off snapshot of a date in the past for this related component's data schema versions are indicated in the above. Please note that any data temporally filtered earlier than the specified launch date indicated in the table for the data schema versions may contain data inconsistencies.

    More information about temporal filtering is available from the .

    The following sub-sections provide details about the attributes included with this related component, their data types in the different output formats, and other important metadata about them.

    Primary key providing a unique row identifier assigned to enable indexing for efficient querying.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 36

    • OS Select+Build Filterable: No

    Unique Property Reference Number (UPRN) assigned by a local custodian or Ordnance Survey as a persistent identifier.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Date of the feature version to which this related component applies.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Alphanumeric code used to classify the object using Valuation Office Agency's (VOA’s) Primary Description code and Special Category code, and the AddressBase Classification Scheme. VOA classification schemes are available on the and OS NGD Address classifications are available on the .

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 6

    • OS Select+Build Filterable: No

    Description of the classification code as defined in the AddressBase Classification Scheme, which is available to download from the .

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 230

    • OS Select+Build Filterable: No

    Name of the classification schema.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 60

    • OS Select+Build Filterable: No

    Version of the classification schema.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 2

    • Scale: 1

    The date on which any attribute of the record was last changed.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Address Related Components

    What are related components?

    The address related components provide supplementary non-geospatial information or context about addresses.

    Addressable object related components

    There are three addressable object related components in the OS NGD Address Theme; they can be linked to a local authority address record in a feature type using the Unique Property Reference Number (UPRN) as the foreign key. Data schema version 3.0 onward of the Built Address, Historic Address, Non-Addressable Object and Pre-Build Address Feature Types in the OS GB Address and OS Islands Address Collections are supported by the three addressable object related components:

    • Alternate Address: These provide alternative address labels where they exist for the ‘current’ address represented on a given feature type.

    • Other Classification: These provide additional Valuation Office Agency (VOA) classification information.

    • : These contain cross-reference relationship information between addresses and features in other OS NGD themes (such as buildings, sites, roads and boundaries) or third-party data sets.

    There are three Royal Mail related components in the OS NGD Address Theme; they can be linked to an address record in a feature type using the Unique Delivery Point Reference Number (UDPRN) as the foreign key. Data schema version 2.0 onward of the Royal Mail Address Feature Type in the OS GB Address and OS Islands Address Collections is supported by the three Royal Mail related components:

    • : These provide data developed to identify addresses that are delivered to a shared delivery point; this means premises with one front door, or delivery point, that has been subdivided into flats, units or other separate occupancies. Multiple residence data provide a detailed address structure for these properties.

    • : These provide alias data related to a delivery point address, sourcing data from Royal Mail's Delivery Point Alias (DPA) table. DPA information provides additional Delivery Point Information, including Trading Names and Building Name details where a Building Number is the official building identifier.

    • : These provide alternate names for counties, localities and thoroughfares.

    The OS NGD Address Theme data structure diagram below is applicable to the latest data schema versions of all address feature types, that is data schema version 3.0 of Built Address, Historic Address, Non-Addressable Object and Pre-Build Address, data schema version 1.0 of Street Address, and data schema version 2.0 of Royal Mail Address:

    Please see for information on data schema versioning in the OS NGD. are available on the OS NGD Address Theme page.

    The related components do not contain geometry and therefore need to be joined to the relevant feature type table using:

    • UPRN for the Built Address, Historic Address, Non-Addressable Object and Pre-Build Address Feature Types

    • UDPRN or UMRRN for the Royal Mail Address Feature Type data schema version 2.0 onward

    When data is supplied, you will receive related component data split out by feature type.

    For example, customers taking data schema version 1.0 or 2.0 of the Pre-Build Address Feature Type in GeoPackage format will receive:

    • Feature type: Pre-Build Address

    • Related component: Pre-Build Alternate Address

    • Related component: Pre-Build Postal Address

    • Related component: Pre-Build Related Entity

    • Related component: Pre-Build Other Classification

    For example, customers taking data schema version 3.0 of the Pre-Build Address Feature Type in GeoPackage format will receive:

    • Feature type: Pre-Build Address

    • Related component: Pre-Build Alternate Address

    • Related component: Pre-Build Related Entity

    • Related component: Pre-Build Other Classification

    🆕 For example, customers taking data schema version 2.0 of the Royal Mail Address Feature Type in GeoPackage format will receive:

    • Feature type: Royal Mail Address

    • Related component: Multiple Residence

    • Related component: Delivery Point Alias

    • Related component: Other Alias

    OS NGD Webinars, Tutorials and Case Studies

    Learn more about the OS NGD through our webinars and tutorials. Case studies demonstrate how customers across numerous sectors are already using and benefiting from OS NGD data.

    If you are a PSGA Member or OS Partner and you'd like to know more about how to get the most out of the OS NGD, head to the or the and watch the recordings of our recent webinars, including 'An introduction to the OS NGD' and 'Maximising the benefits of ordering OS NGD data using OS Select+Build'. New webinars are added to both areas periodically.

    To help make getting started easier with OS Select+Build and the OS NGD APIs, we have created the following tutorial videos (available from our YouTube channel) to give you step-by-step guidance:

    'Is Detached' attribute values are applied to portions of local government and parliamentary constituency areas that are separated from the main area and are completely surrounded by other areas.

    👩‍🍳 Guides for creating OS recommended recipes

    FAQs
    FAQs

    Data Schema Version: 1.0, 2.0, 3.0

    Data Schema Version: 1.0, 2.0, 3.0

    Data Schema Version: 1.0, 2.0, 3.0

    Data Schema Version: 1.0, 2.0, 3.0

    OS Select+Build Filterable: No

  • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 60

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0

    30 September 2025

    Ongoing

    Major version increment to align with concurrent major version increments made to four feature types in the GB Address and Islands Address Collections: Built Address, Historic Address, Non-Addressable Object, and Pre-Build Address. (Related components follow the versioning of the addressing feature types they are associated with.) Data type updated for Scheme Version attribute from string to number.

    2.0

    28 March 2023

    Ongoing

    Major version increment to align with concurrent major version increments made to four feature types in the GB Address and Islands Address Collections: Built Address, Historic Address, Non-Addressable Object, and Pre-Build Address. (Related components follow the versioning of the addressing feature types they are associated with.)

    1.0

    02 November 2022

    Ongoing

    Initial launch of the Other Address Related Component.

    Temporal filtering

    Related component attributes

    otherclassificationid

    uprn

    featuretypeversiondate

    classificationcode

    classificationdescription

    classificationscheme

    schemeversion

    updatedate

    Data schema versioning
    Data schema version table
    Getting started with temporal filtering guide
    VOA website
    AddressBase Classification Scheme page of the OS Download Products’ Documentation site
    AddressBase Classification Scheme page of the OS Download Products’ Documentation site

    Railway Link Set (OS Transport Network Collection)

    OS Land Use Features

    GeoPackage, CSV

    Three 5km x 5km areas

    OS Named Features

    GeoPackage, CSV

    Three 5km x 5km areas

    OS Routing and Asset Management Information (RAMI)

    GeoPackage, CSV

    Three 5km x 5km areas

    OS Structure Features

    GeoPackage, CSV

    Three 5km x 5km areas

    OS Transport Features

    GeoPackage, CSV

    Three 5km x 5km areas

    OS Transport Network

    GeoPackage, CSV

    Three non-standard 5km x 5km areas: Sheffield, Newport & Inverness

    OS Water Features

    GeoPackage, CSV

    Three non-standard 5km x 5km areas: Plymouth, Newport & Inverness

    OS Water Network

    GeoPackage, CSV

    Three 5km x 5km areas

    🗃️ Data Structure

    Data structure pages provide more detailed information about data available for OS NGD themes, collections and feature types.

    📣 OS NGD News

    Learn about new data and access enhancements recently released for the OS NGD.

    Exceptions to the standard sample data areas

    Record counts will be zero for three feature types in sample data

    OS GB Address
    OS GB Postcodes
    OS Building Features
    OS Functional Areas
    OS Land Features

    🆕 Royal Mail related components

    Delivery Point Alias and Other Alias Related Component tables will be empty initially

    Please note that the Delivery Point Alias and Other Alias Related Component tables are included in product design for future compatibility but are not currently populated; customers should expect these files to be empty until a future data enhancement enables OS to supply the Royal Mail alias data. Please see the FAQs for more information.

    🔃 Data structure

    Postal Address Related Component

    • Until September 2025, Postal Address Related Component was the fourth related component in the OS NGD. It has been discontinued in the latest data schema version 3.0 of the Built Address, Historic Address, Non-Addressable Object and Pre-Build Address Feature Types in the OS GB Address and OS Islands Address Collections, which released in September 2025.

    • The Postal Address Related Component contained delivery point data from the Royal Mail Postcode Address File (PAF). This information is now available in the Royal Mail Address Feature Type (which launched in September 2025), which can be found in the OS GB Address and OS Islands Address Collections.

    • The Postal Address Related Component is still provided against the older (maintenance) data schema versions 1.0 and 2.0 of the Built Address, Historic Address, Non-Addressable Object and Pre-Build Address Feature Types in the OS GB Address and OS Islands Address Collections. These data schema versions are available for customers to use, but they are now older and in maintenance mode. (Data schema version 3.0 is the latest and recommended data schema version to use for these feature types.)

    🔃 When will related components be provided?

    Related components will always be provided if you have chosen to receive any of the five following feature types from the OS NGD Address Theme:

    • Built Address, Historic Address, Non-Addressable Object or Pre-Build Address; the primary identifier for these four feature types is the URPN (Unique Property Reference Number).

    • Royal Mail Address data schema version 2.0 onward if the Description attribute is down as 'Postcode Address File'. When the Description attribute is down as 'Not Yet Built' for Royal Mail Address Feature Type data schema version 2.0 onward, you will be provided with related components, but they will be 'Null'. The primary identifiers to associate the related component tables to the Royal Mail Address Feature Type are the Royal Mail's Unique Delivery Point Reference Number (UDPRN) and Unique Multiple Residence Reference Number (UMRRN).

    • Related components will not be provided for the Street Address Feature Type as its primary identifier is Unique Street Reference Number (USRN), not UPRN, UDPRN or UMRRN.

    • Related components will not be provided for Royal Mail Address Feature Type data schema version 1.0 and 1.1. (The three Royal Mail related components were added to this feature type from data schema version 2.0 onward.)

    🔃 How to handle related components

    Related Entity
    Multiple Residence
    Delivery Point Alias
    Other Alias
    Data schema versioning
    Superseded data structure diagrams for the OS NGD Address Theme
    OS NGD Address Theme data structure diagram showing the theme name, collection names, feature type names, and related component names. The data structure diagram is applicable to the latest data schema versions of all address feature types.
    OS NGD Address Theme data structure diagram showing the theme name, collection names, feature type names, and related component names; it's applicable to the latest data schema versions of all address feature types.
    Short YouTube video explaining what the OS NGD is.
    'How do I edit a recipe?' steps outlined above
    Screenshot of the OS Data Hub 'Recipe cannot be edited' warning pop up in OS Select+Build.
    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
    Screenshot of the OS Select+Build Recipe details screen in the OS Data Hub, with the Recipe actions dropdown showing where you can share, edit or delete a recipe.
    OS postcodes data
    Identify retail locations
    Tree diagram showing the data structure of the OS NGD Administrative and Statistical Units Theme. It lists the theme name, collection names, and feature type names.

    OS GB Address

    British National Grid (EPSG: 27700)

    OS GB Postcodes

    British National Grid (EPSG: 27700)

    OS Islands Address

    European Terrestrial Reference System (EPSG: 4258)

    OS Named Features

    British National Grid (EPSG: 27700)

    OS Land Features

    British National Grid (EPSG: 27700)

    OS Land Use Features

    British National Grid (EPSG: 27700)

    OS NI Postcodes

    European Terrestrial Reference System (ETRS89: EPSG: 4258)

    OS Structure Features

    British National Grid (EPSG: 27700)

    OS Routing and Asset Management Information (RAMI)

    British National Grid (EPSG: 27700) for all feature types, except the Average And Indicative Speed Feature Type which is British National Grid + ODN Height (EPSG: 7405)

    OS Transport Features

    British National Grid (EPSG: 27700)

    OS Transport Network

    British National Grid + ODN Height (EPSG: 7405) for most feature types in the collection; British National Grid (EPSG: 27700) for the Ferry Terminal, Path, Road, Road Junction, Street and Pavement Link Feature Types

    OS Water Features

    British National Grid (EPSG: 27700)

    OS Water Network

    British National Grid + ODN Height (EPSG: 7405) for the Water Link and Water Node Feature Types; British National Grid (EPSG: 27700) for the Water Link Set Feature Type

    Web Mercator (EPSG: 3857)

    Web Mercator is not a recognised geodetic system, but it is used for many visualisation and web mapping use cases. It uses the WGS84 geodetic datum, and positions on this projection are described as easting and northing, all in units of metres.

    OS Boundaries

    British National Grid (EPSG: 27700)

    OS Building Features

    British National Grid (EPSG: 27700)

    OS Functional Areas

    British National Grid (EPSG: 27700)

    British National Grid (BNG: EPSG: 27700)

    The British National Grid (BNG) spatial reference system uses the OSGB36 geodetic datum and a single Modified 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 include a vertical (height) reference system.

    British National Grid + ODN Height (EPSG: 7405)

    The BNG with ODN height reference uses the OSGB36 geodetic datum and a modified Transverse Mercator projection for the whole of Great Britain. Positions in this system are described by easting and northing coordinates plus a height value, all in units of metres. Please note, this will only be available for some OS NGD feature types.

    European Terrestrial Reference System

    (ETRS89: EPSG: 4258)

    The European Terrestrial Reference System uses the ETRS89 geodetic reference system which is the EU-recommended frame of reference for European data. Positions on this projection are described using latitude and longitude, and coordinates are provided in degrees. ETRS89 is a horizontal spatial reference system only; it does not specify a vertical (height) reference system.

    Please note, this coordinate system is used for the OS Islands Address Collection due to the coverage of this data only being Northern Ireland, Isle of Man, and the Channel Islands. Similarly, this coordinate system is used for the OS NI Postcodes Collection due to the coverage of this data being Northern Ireland.

    World Geodetic System (WGS84: EPSG: 4326)

    Default coordinate reference systems for OS Select+Build

    Selecting a coordinate reference system

    Coordinate reference systems available for the OS NGD APIs

    OS NGD API – Features

    OS NGD API – Tiles

    Definitions for the coordinate reference systems available in the OS NGD

    🆕 Use of geographic coordinate reference systems in the OS NGD

    Guide to coordinate reference systems in Great Britain

    An in-depth guide to coordinate systems in Great Britain is available from our More Than Maps site.

    creating a new data package in OS Select+Build

    The WGS84 spatial reference system uses the WGS84 geodetic datum. Positions on this projection are described as latitude and longitude, and coordinates are provided in decimal degrees. There will also be an option to receive this reference system via CRS 84, meaning the coordinates will be provided as longitude / latitude rather than latitude / longitude.

    (Optional) Add filters to the feature types, if needed; more information about this is available on the Getting started with attribute filtering page.
    Screenshot showing an example of selecting a data schema version for a feature type in a new recipe using OS Select+Build in the OS Data Hub.
    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
    4

    Navigate to the recipe you'd like to find out more about

    Select the recipe you're interested in from the menu. In this view, you can see the following high-level details about a recipe:

    • The recipe's name

    • The recipe's author

    • The date the recipe was created

    • A description of the recipe, if one has been added

    • OS NGD theme tags to show which themes are included in the recipe

    In the screenshot below, you can see that the example recipe includes the following OS NGD themes: Land, Buildings, and Structures:

    5

    Find out what OS NGD themes, collections and feature types are in a recipe

    Clicking on a recipe opens the detailed information view, where you can find more information about the recipe, including:

    • The recipe's name

    • A description of the recipe, if one has been added

    • An option to view all of the filters applied to feature types in the recipe (if applicable)

    • The date the recipe was created

    • The recipe's author

    • An option to show the data schema version of each feature type in the recipe

    • A recipe tree detailing the OS NGD themes, collections, and feature types included in the recipe

    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
    4

    Find the recipe you want to delete

    In your organisation's OS Select+Build Recipe Library, scroll or search for the recipe you want to delete.

    5

    Open the detailed recipe view

    Click on the name of the recipe to view the recipe details. In this view, you will be able to see the Recipe actions dropdown (where you can share, edit or delete a recipe).

    6

    Open the recipe actions dropdown

    7

    Delete the recipe

    • Click on the name of the recipe to view the recipe details.

      • If there are no data packages associated with the recipe, you will be asked to confirm the deletion of the recipe.

      • Where there are data packages associated, you will see the following warning:

    • Click the Delete recipe button.

    Creating new recipes

    Finding your OS Select+Build Recipe Library

    Checking what's in a recipe

    Deleting recipes

    Navigate to the OS Data Hub workspace

    Navigate to the OS Select+Build Recipe Library

    Choose Create a new recipe

    Add details to the recipe

    Finish creating the recipe

    Please note

    • We recommend defining a naming convention for your organisation before creating OS NGD recipes and / or data packages.

    • Adding filters to feature types is an optional step for those with advanced OS data knowledge; see the Getting started with attribute filtering page for more information on applying filters and step-by-step instructions.

    • Selecting a data schema version for a feature type is an optional step; if you don't choose a particular data schema version for a feature type, OS Select+Build will always select the latest available data schema version for you for each feature type by default. We recommend using the pre-selected latest data schema version for feature types unless you have a specific need to use an earlier one. See the for more information.

    What's next?

    How do I find my OS Select+Build Recipe Library?

    Log into your OS Data Hub account

    Navigate to the OS Data Hub workspace

    Navigate to the OS Select+Build Recipe Library

    How do I check what's in a recipe?

    Log into your OS Data Hub account

    Navigate to the OS Data Hub workspace

    Navigate to the OS Select+Build Recipe Library

    How do I delete a recipe?

    Log into your OS Data Hub account

    Navigate to the OS Data Hub workspace

    Navigate to the OS Select+Build Recipe Library

    OS Data Hub
    Screenshot of the OS Data Hub, showing the OS Select+Build Recipe Library screen.
    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.

    Once you've created a recipe, you'll need to add a data package against it to receive your OS NGD data. This guide takes you through creating a new data package to apply against your new recipe.

    A screenshot of the OS Data Hub home page showing the sign up and log in buttons in the top right hand corner
    Screenshot showing the OS Data Hub homepage.
    A screenshot of the OS Data Hub home page showing the sign up and log in buttons in the top right hand corner
    Screenshot showing the OS Data Hub homepage.
    A screenshot of the OS Data Hub home page showing the sign up and log in buttons in the top right hand corner
    Screenshot showing the OS Data Hub homepage.
    A screenshot of the OS Data Hub home page showing the sign up and log in buttons in the top right hand corner

    If you wish to choose which schema version (where applicable) you'd like to receive the data in for a feature type, click on the feature type name within the tree view in the secondary navigation menu, then choose a data schema version from the drop-down box in the right-hand side panel.

    OS NGD Water

    OS Water Features

    4

    Choose Create a new recipe

    Click the Create a new recipe button at the top right-hand side of the screen.

    5

    Give the recipe a name and description

    • Give your recipe a descriptive name in the Recipe name dialog box on the left-hand side of the screen.

    • Add a detailed description for your recipe (this is optional, but it's useful if other team members will be accessing it).

    6

    Select the feature types

    Select your OS NGD data by choosing the themes, collections and feature types you want to include in your recipe. You'll need to select the following 10 suggested feature types from the Themes panel on the left-hand side of the screen:

    • Built Address (found within Address > GB Address > Built Address)

    • Parish Or Community (found within Administrative and Statistical Units > Boundaries > Parish Or Community)

    • Upper Tier Local Authority (found within Administrative and Statistical Units > Boundaries > Upper Tier Local Authority)

    • Retail Area Major (found within Administrative and Statistical Units > Functional Areas > Retail Area Major)

    • Retail Area Minor (found within Administrative and Statistical Units > Functional Areas > Retail Area Minor)

    • Building (found within Buildings > Building Features > Building)

    • Named Area (found within Geographical Names > Named Features > Named Area)

    • Site (found within Land Use > Land Use Features > Site)

    • Site Access Location (found within Land Use > Land Use Features > Site Access Location)

    • Water (found within Water > Water Features > Water)

    7

    (Optional) Choose a data schema version

    Selecting a data schema version for a feature type is an optional step; if you don't choose a particular data schema version for a feature type, OS Select+Build will always select the latest available data schema version for you for each feature type by default. We recommend using the pre-selected latest data schema version for feature types unless you have a specific need to use an earlier one. (See the Data schema versioning page for more information on data schema versioning in the OS NGD.)

    If you wish to choose which schema version (where applicable) you'd like to receive the data in for a feature type, click on the feature type name within the tree view in the secondary navigation menu, then choose a data schema version from the Choose Data Schema drop-down box in the right-hand side panel.

    Screenshot showing the tree view in the secondary navigation menu that opens when you create a recipe in OS Select+Build in the OS Data Hub. The Building Feature Type has been selected in this screenshot, and the Choose Schema Version drop-down menu is visible in the right-hand side panel, which lets you select the data schema version you want to use for the feature type.
    8

    Finish creating the recipe

    Once you've selected the 10 suggested feature types, click the Create recipe button to complete the recipe creation process. Your new recipe will now instantly be available in your OS Select+Build Recipe Library.

    You can view a summary of the completed town and city planning recipe, including the required feature types, if you click Data > Downloads > OS Select+Build Recipe Library > *your recipe's name*.

    The recipe summary should look like the screenshot below:

    Screenshot of the OS Select+Build Recipe details screen showing a summary of the town and city planning recipe, including the selected feature types.

    OS NGD Address

    OS GB Address

    Built Address

    OS NGD Administrative and Statistical Units

    OS Boundaries

    Parish Or Community and Upper Tier Local Authority

    OS NGD Administrative and Statistical Units

    OS Functional Areas

    Retail Area Major and Retail Area Minor

    OS NGD Buildings

    OS Building Features

    Building

    OS NGD Geographical Names

    OS Named Features

    Named Area

    OS NGD Land Use

    OS Land Use Features

    Creating the recipe

    Log into your OS Data Hub account

    Navigate to the OS Data Hub workspace

    Navigate to the OS Select+Build Recipe Library

    What's next?

    Further guidance on creating, editing and deleting recipes

    Add a data package to your recipe

    Creating maps using QGIS and standardising geometry

    Definition

    A screenshot of the OS Data Hub home page showing the sign up and log in buttons in the top right hand corner
    Screenshot showing the OS Data Hub homepage.

    and

    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
  • OS Select+Build: How to add attribute filters to a new recipe

  • How to use OS NGD API – Features

  • How to use OS NGD API – Tiles

  • Additional useful OS NGD data tutorials:

    • Using OS's new buildings data attribute: Number of Floors

    • Filtering and the Common Query Language (CQL)

    • Edit vector tile styles in Maputnik

    Find out how customers across numerous sectors are using and benefiting from OS NGD data:

    • Emergency Services: Find out how new data on pedestrian and vehicular access points to key public buildings will help the Emergency Services to enhance their emergency planning and response times and improve their situational awareness.

    • Emergency Services: Find out how data for number of floors, sites, and bridge interactions will help the Emergency Services.

    • British Army case study: Discover how the British Army use OS NGD API – Features for battlefield training.

    • North Wales Cave Rescue Organisation case study: Discover how the North Wales Cave Rescue Organisation has used OS NGD data to enable faster responses to underground incidents in North Wales.

    • : Find out how North Yorkshire Fire & Rescue Service used OS Select+Build to reduce data analysis timeframes.

    • Helping financial institutions meet the Bank of England's climate standards: Find out why financial institutions should integrate accurate location data from the OS NGD Address, Buildings, Land Use and Water Themes into their climate risk frameworks.

    • Optimising mortgage applications using authoritative property and location data: Discover how OS NGD Address and Buildings Themes' data can provide mortgage lenders with a clear, consistent view of each property, delivering precise property identification, location, age and physical state of buildings information. OS NGD Land Use Theme data offers comprehensive land classification data that can help assess environmental and planning factors that could impact property value or mortgage risk.

    • Identify retail locations: Find out how the new retail areas data is useful for central government in the creation of policy relating to local neighbourhoods and can be used to show how investment impacts areas with similar characteristics. Discover how local authorities can use this foundational dataset for evidence-gathering and to define patterns of economic activity.

    • Analysing roof attribution data: Discover how enhanced roof attribution data can benefit a wide range of sectors, including sustainability and energy, insurance and property, and Emergency Services.

    • Solar panel presence case study: Discover how to use Building Feature Type data to locate and map solar panels on roofs across Great Britain.

    • : Learn how OS NGD Buildings Theme data provided detailed insights into building age, construction materials and location, enabling OS to model heat-loss risk at scale and identify hard to heat homes across Great Britain.

    • : Discover how OS NGD data can support better planning and future modelling for new housing developments.

    • : Learn how ONS is using OS NGD data to provide up-to-date estimates of the value that green and blue spaces add to house prices.

    • : Learn how the OS NGD Land, Buildings, Land Use, Structures, Transport and Water Themes are providing authoritative, innovative and trusted data to support agriculture, land management and telecoms.

    • : Find out how Crown Estate Scotland are using OS NGD data to conduct more efficient, cost-effective land management.

    • : Learn how Torfaen County Borough Council is using OS NGD data to more efficiently maintain the areas of land it covers.

    • : Learn how the OS NGD is supporting nature conservation in Greater Manchester and saving ecologists lots of time.

    • : Discover how tidal boundary data can support coastal erosion and flooding modelling, flood risk monitoring and climate change assessments.

    • : Learn how OS NGD Transport Theme data was combined with the latest Environment Agency flood data to map the commuter corridors, economic routes and access points most vulnerable to river and sea flooding.

    • : Discover how data from the OS NGD Address, Buildings, Land Use and Water Themes provides the trusted foundation water companies need to plan future and current water infrastructure at scale.

    • : Find out how Scottish Canals used the OS NGD to help them managing and maintain Scotland’s historic 141-mile canal network.

    • Supporting Active Travel and public safety: Discover how cycle lane data support local authorities and central government in promoting Active Travel and public safety.

    • Street light data supporting Active Travel: Learn how OS NGD street light data can be used to identify safer walking and cycling routes, find areas where street lighting needs improvement, and even highlight potential crime hotspots.

    • OS and Office for National Statistics case study: Learn how OS and the ONS worked together to measure travel times and access to amenities.

    • Analysing pavement widths using OS Select+Build case study: Learn how to determine pavement widths in OS NGD data.

    • : Find out more about how the OS NGD speed datasets make it easier to analyse travel times, enhance routing analytics and provide accurate insight for safety and infrastructure policy decisions.

    🖥️ Webinars

    👩‍🏫 Tutorials

    PSGA Members area
    Partner Portal
    OS Select+Build: How to build a recipe

    Numerous are available on our (a self-serve learning hub that acts as a one-stop shop for all your OS technical geospatial support needs, offering interactive demonstrators, step-by-step tutorials, and case studies). These tutorials and demonstrators introduce the OS NGD data themes, collections and feature types and show you what can be achieved using OS NGD data and how. New tutorials and demonstrators are added to the More than Maps site periodically.

    The same tutorials and demonstrators are available to PSGA (Public Sector Geospatial Agreement) Members and OS Partners from the and the , respectively (just search for 'Lightning Talks').

    📔 Case studies

    National security and resilience

    Financial services

    Land and property

    Transport

    OS Select+Build: How to download a data package

    🔃 Using OS Select+Build

    Discover OS NGD

    Explore OS NGD

    File formats available with OS Select+Build

    Getting started with recipes guide
    Getting started with data packages guide
    data ordering and currency page
    OS NGD Fundamentals guide

    A guide to creating a bespoke selection of OS NGD data within OS Select+Build, covering:

    A guide to applying data packages to your OS Select+Build recipes, covering:

    Guides to creating OS recommended recipes in OS Select+Build:

    A guide to accessing GeoPackage data GeoPackage data via popular GIS software packages.

    A guide to accessing OS NGD data in CSV (comma-separated values) format.

    A high level summary of what the OS NGD is, how to access it and who can use it.

    Frequently asked questions on OS NGD data and the download service of OS Select+Build.

    Learn more about the OS NGD through our webinars and tutorials. Case studies demonstrate how customers across numerous sectors are already using and benefiting from OS NGD data.

    Learn about new data and access enhancements recently released for the OS NGD.

    Data structure pages provide more detailed information about data available for OS NGD themes, collections and feature types.

    Resources for styling OS NGD data.

    Infographic showing the steps involved when using OS Select+Build in the OS Data Hub. The first step is OS Select+Build, the next step is creating a recipe, and the final step is adding then downloading data packages.
    Screenshot of the OS Select+Build Recipe creator screen within the OS Data Hub, showing an example of creating a new recipe. Several themes, collections and feature types have been selected from the secondary navigation menu on the left-hand side of the screen.

    Getting started with data packages

    Step-by-step instructions on how to create new data packages, find and download existing ones, and delete data packages.

    Adding a data package to your OS Select+Build recipe allows you to select the area, format, and update frequency to receive for your data.

    The following sub-sections on this page cover:

    🔃 How do I create a new data package?

    Once you've created a recipe, you'll then need to create a data package against it to receive your OS NGD data.

    To create a new OS NGD data package:

    1

    Log into your account

    Click Login on the OS Data Hub menu bar to log into your account.

    Screenshot showing the OS Data Hub homepage.
    2

    Select Data from the menu bar to view your workspace.

    3

    Choose Downloads > OS Select+Build Recipe Library from the left hand side secondary navigation menu. You will then be taken to your organisation's OS Select+Build Recipe Library.

    4

    In your OS NGD Select+Build Recipe Library, scroll or search for the recipe you wish to create a data package against, select that recipe, then click the Add data package button.

    5

    Add the following details to your data package under Add a data package in the secondary navigation menu:

    • Give your data package a name.

    • Choose the area you want to receive your data for: Either 'All of Britain or Predefined Area' (this means you receive data and it will not be refined by location) or 'Draw a polygon / upload a file / use an OS polygon' (to select a smaller area of interest for your data to be provided for).

    6

    Click the Create data package button.

    All OS NGD, OS OpenData and OS Premium data packages created and ordered by your organisation will be catalogued in your Data Packages list in the OS Data Hub.

    To find and download an existing data package:

    1

    Click Login on the OS Data Hub menu bar to log into your account.

    2

    Select Data from the menu bar to view your workspace.

    3

    Choose Downloads > Data packages from the secondary navigation menu. You will then be taken to your data package list.

    Feature types downloaded via OS Select+Build will be supplied with an Order Summary File, a small JSON manifest that provides key metadata about the supplied file. You can use this file to validate the data to ensure the currency, record counts (feature counts), schema version, feature name and coordinate reference system (CRS) match your expected order.

    The following file naming convention will be applied to each Order Summary File you receive:

    • collection_featuretype_orderSummary.json

    For example, the file name for the Building Line Feature Type Order Summary File would look like this:

    • bld_fts_buildingline_orderSummary.json

    The example below shows the information an Order Summary File contains:

    The following table provides a brief description of each field:

    Field
    Description
    Use

    To delete an existing OS NGD data package:

    1

    Click Login on the OS Data Hub menu bar to log into your account.

    2

    Select Data from the menu bar to view your workspace.

    3

    Choose Downloads > Data packages from the secondary navigation menu. You will then be taken to your data package list.

    OS NGD Improvements

    A high-level summary of data improvements implemented throughout the year for the OS NGD.

    2026 OS NGD improvements

    June 2026 – Improved thatched roof identification in the Building Feature Type

    We've enhanced roof material attribution for the Building Feature Type (within the OS Building Features Collection) through a targeted manual capture and verification programme to improve the identification and quality of thatched-roof properties across Great Britain.

    This update in June 2026 provides customers with more accurate roof material data for applications such as insurance risk assessment, heritage management and retrofit planning.

    June 2026 – Improvements to basement presence modelling in the OS NGD Buildings Theme

    Improvements are being made to the modelling of basement presence attribution for the Building Feature Type within the OS NGD Buildings Theme to improve the accuracy and consistency of basement representation across Great Britain.

    This update by Verisk enhances the underlying modelling approach by incorporating additional data sources and identifying areas where basement counts may have previously been under- or over-represented. The revised model increases overall coverage and reduces inconsistencies in basement features.

    As a result of this update, a small number of Building features will receive changes to their Basement Presence attribute value, and a significantly larger volume of Building features will see updates to their Basement Presence Update Date attribute value, where evidence dates for modelled values are recalculated based on the new modelling inputs. As basement presence is modelled for around 97% of buildings, this will result in metadata updates affecting approximately 20 million OS Identifiers (OSIDs).

    These changes are scheduled for release in the week commencing 22 June 2026. Customers receiving daily updates may notice a higher than usual volume of change during this period due to the scale of metadata updates.

    The was added to the OS NGD in March 2024.

    In March 2025, we introduced improvements to the automated method used to identify field boundary data; this update incorporated machine learning techniques to increase the accuracy and consistency of field boundary classification.

    As part of our process, the output of all automatically classified field boundary features undergo a quality review. In March 2025, our thematic accuracy assessment showed that 7.7% of field boundary national coverage was classified as requiring improvement. Following the implementation of machine learning, this figure has reduced to 2.1% as of March 2026, raising classification performance and overall data quality.

    Supplementary information covering how field boundary data is created, highlights of the attribution available, and the known limitations is available from the of this site. A full list of the attribution provided for Field Boundary features can be found on the page in the Data Structure section.

    Improvements were made to the OS NGD during a planned maintenance period in February 2026 to improve the accuracy, consistency, and validation of topographic data, as well as preparing for future product releases.

    These improvements included:

    • A new method has been implemented for populating existing metadata Geometry Capture Method, Description Capture Method, OS Land Cover Capture Method and OS Land Use Capture Method attribution on Building Part, Land, Structure, Rail, Road Track Or Path, Water and Site Feature Types, which impacts the v2.0 and v3.0 schemas where this metadata is present. This may result in some one-off changes for some features in the OS NGD.

    • The description values of 'Ford' and 'Tidal Ford' were previously applied the wrong way around on Water Point features. This fix ensures that they are assigned correctly.

    There was partial data coverage across Great Britain for the and Feature Types between September 2025 (when the two feature types were released into the OS NGD) and March 2026, with iterative increases in coverage released monthly.

    Full data coverage for Great Britain for the two feature types was achieved by March 2026.

    The data went through thorough testing ahead of initial release in September 2025, followed by additional quality testing ahead of achieving full Great Britain-wide coverage in March 2026.

    There was partial data coverage across Great Britain for the and Feature Types between September 2025 (when the two feature types were released into the OS NGD) and March 2026, with iterative increases in coverage released monthly.

    Full data coverage for Great Britain for the two feature types was achieved by March 2026.

    The data went through thorough testing ahead of initial release in September 2025, followed by additional quality testing ahead of achieving full Great Britain-wide coverage in March 2026.

    The following improvements will be implemented into the OS NGD during a planned maintenance period in July 2025.

    Improvements on 'Industry And Business' and 'Business Or Industrial Park' Land Use Sites and related attribution on Topographic Areas

    As a result, customers will see improvements to over 400 000 ‘Industry and Business’ and ‘Business or Industrial Park’ sites in the OS Land Use Features Collection and their corresponding topographic area feature (Building, Building Part, Land, Structure, and Water Feature Types). These enhancements will be visible in the OS Land Use Tier A attribute.

    We have also improved the following OS Land Use Tier A definitions to improve clarity and the accuracy of classifications:

    Related Entity

    The Related Entity Related Component provides cross-reference information to key identifiers from other datasets, allowing for the UPRN (Unique Property Reference Number) to be linked to them.

    Data schema versioning

    The following table provides details about this related component’s data schema versions, including the reasons behind the changes and the related launch date when each version went live.

    Data schema version table

    Version ↓
    Launch Date
    Latest Date
    Change

    3.0

    30 September 2025

    Ongoing

    Please see for in-depth information about data schema versioning in the OS NGD.

    Temporal filtering allows you to order a one-off snapshot of data from the OS NGD from a current or past date. It is an optional step when you create a new data package in OS Select+Build (the OS NGD download service).

    The earliest and latest dates on which you can request a one-off snapshot of a date in the past for this related component's data schema versions are indicated in the above. Please note that any data temporally filtered earlier than the specified launch date indicated in the table for the data schema versions may contain data inconsistencies.

    More information about temporal filtering is available from the .

    The following sub-sections provide details about the attributes included with this related component, their data types in the different output formats, and other important metadata about them.

    Primary key providing a unique row identifier assigned to enable indexing for efficient querying.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 36

    • OS Select+Build Filterable: No

    Unique Property Reference Number (UPRN) assigned by a local custodian or Ordnance Survey as a persistent identifier.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Date of the feature version to which this related component applies.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Description of the related dataset that the cross reference refers to, for example, VOA Council Tax.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version: 2.0

    Identifier of the related data entity or feature type instance that is the target of the reference or link.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 36

    • OS Select+Build Filterable: No

    Type of relationship which has been formed between the source and target features, for example, 'Within' or 'Same As'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Code List Version: 1.0

    Name of the originating data provider that defined the reference or link.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 110

    • OS Select+Build Filterable: No

    The date on which any attribute of the record was last changed.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The date on which this relationship was first added into the database.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0, 3.0

    The date on which the relationship ceased to exist.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0, 3.0

    Boundary High Water Mark

    In the OS Boundaries Collection, the mean high water (springs) mark is shown to the normal tidal limit (NTL). Areas of salt marsh, mudflats and so on often have extremely complicated tide lines. For ease of digitising and to reduce data volumes, mean high water may be generalised in these areas (not Scotland). The mean high water (springs) mark is represented in the OS Boundaries Collection by a polyline feature. The mean high water (springs) mark is subject to continuous change, but the captured alignment of a tide line is a snapshot on one day. It is not practical to revise tide lines frequently.

    Data schema versioning

    The following table provides details about this feature type’s data schema versions, including the reasons behind the changes and the related launch date when each version went live.

    Data schema version table

    Version ↓
    Launch Date
    Latest Date
    Change

    Please see for in-depth information about data schema versioning in the OS NGD.

    Temporal filtering allows you to order a one-off snapshot of data from the OS NGD from a current or past date. It is an optional step when you create a new data package in OS Select+Build (the OS NGD download service).

    The earliest and latest dates on which you can request a one-off snapshot of a date in the past for this feature type's data schema versions are indicated in the above. Please note that any data temporally filtered earlier than the specified launch date indicated in the table for the data schema versions may contain data inconsistencies.

    More information about temporal filtering on OS NGD feature types is available from the .

    The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

    Primary identifier for the feature. The OSID is a Globally Unique Identifier (GUID) and requires no centralised authority to ensure uniqueness. Note that the same OSID can occur in more than one feature type when a single feature is represented multiple times in the OS NGD.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 36

    • OS Select+Build Filterable: No

    Date when the version was last updated.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The date this version of the feature became the latest version.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The date this version of the feature was superseded by an update or ceased to exist.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The type of change that generated a new version of the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    Geometry for the feature.

    • Data Types: Geometry (GPKG), WKT (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The measured length of the geometry in metres.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 18

    • Scale: 6

    The OS NGD theme to which this feature belongs.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 40

    A single descriptive value intended for a quick understanding of what the feature represents.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    A single description value for boundary type.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    Short YouTube video explaining what the OS NGD is.
    osngd-resources/styling at main · OrdnanceSurvey/osngd-resourcesGitHub

    Greenspace recipe guide

    A guide with detailed step-by-step instructions outlining how you can create a greenspace recipe in OS Select+Build.

    The term 'greenspace' is used in urban planning, environmental management and public health policy, and refers to land covered by vegetation or areas of water (also known as 'bluespace'). It's now well recognised that green spaces deliver social, economic and environmental benefits. Consequently, greenspace is a concept used to frame discussion and deliver progress for improving quality of life, mitigating climate change and enhancing biodiversity.

    The use cases for greenspace are many and varied, but include:

    • Evaluating access to nature and recreational areas

    • Improving air quality

    Safer routes to schools recipe guide

    A guide with detailed step-by-step instructions outlining how you can create a safer routes to schools recipe in OS Select+Build.

    The guide below provides a geospatial toolkit for helping you calculate safer routes to schools across Great Britain; its step-by-step instructions outline how to select relevant pieces of addressing, routing and transport network data from the OS NGD and weave them into a recipe.

    Various powerful OS NGD attribution can be considered when assessing safer routes to school. The feature types included in this recipe guide contain useful attribution on:

    • Street light presence – More well-lit routes are likely to be safer to walk along.

    • Presence of pavement – It will be safer if a child can spend a significant portion of their journey walking along a pavement, rather than on a roadside.

    Data Schema Version: 1.0, 2.0, 3.0

    Max Length: 40

  • OS Select+Build Filterable: No

  • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: dataentitycatalogue

    • Code List Version: 1.0

    • Max Length: 40

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0

    Data Schema Version: 1.0, 2.0, 3.0

    Max Length: 30

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0

  • Data Schema Version: 1.0, 2.0, 3.0

    Major version increment to align with concurrent major version increments made to four feature types in the GB Address and Islands Address Collections: Built Address, Historic Address, Non-Addressable Object, and Pre-Build Address. (Related components follow the versioning of the addressing feature types they are associated with.)

    Modified the associated code list (Data Entity Catalogue Code List) for the Cross Reference Feature attribute.

    2.0

    28 March 2023

    Ongoing

    Major version increment to align with concurrent major version increments made to four feature types in the GB Address and Islands Address Collections: Built Address, Historic Address, Non-Addressable Object, and Pre-Build Address. (Related components follow the versioning of the addressing feature types they are associated with.) New attribution added to related component for Effective Start Date and Effective End Date.

    1.0

    02 November 2022

    Ongoing

    Initial launch of the Related Entity Related Component.

    Temporal filtering

    Related component attributes

    relatedentityid

    uprn

    featuretypeversiondate

    crossreferencefeature

    crossreferenceid

    relationshiptype

    source

    updatedate

    effectivestartdate

    effectiveenddate

    Data schema versioning
    Data schema version table
    Getting started with temporal filtering guide
    dataentitycatalogue
    relationshiptypevalue

    Data Schema Version: 1.1

    OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • Geometry Type: LineString

    OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.1

  • 1.1

    28 July 2025

    Ongoing

    Minor version increment that removes the query and download filters from the Description attribute as this attribute supports only a single value.

    1.0

    29 September 2022

    27 July 2025

    Initial launch of the Boundary High Water Mark Feature Type.

    Temporal filtering

    Feature type attributes

    Loading OS NGD CSV files into databases

    Comma-separated values (CSV) file format is universally supported for easy ingestion into all major database products. Before loading OS NGD data contained in CSV files into a database, it is necessary to create relevant tables. Data definition language (DDL) statements for PostgreSQL, SQL Server and Oracle can be accessed in our OS NGD Resources GitHub repository.

    For instructions on loading CSV files, see the Getting Started with CSV guide.

    osid

    versiondate

    versionavailablefromdate

    versionavailabletodate

    changetype

    geometry

    geometry_length

    theme

    description

    boundarytype

    Data schema versioning
    Data schema version table
    Getting started with temporal filtering guide
    changetypevalue
    themevalue
    boundaryhighwatermarkdescriptionvalue
    boundarytypevalue

    📖 Getting started with OS Select+Build recipes

    📚 Getting started with data packages

    👩‍🍳 Getting started with OS recommended recipes

    🗺️ Getting started with GeoPackage

    📑 Getting started with CSV

    📖 OS NGD Explained

    ❓ FAQs

    👩‍🏫 OS NGD Webinars, Tutorials and Case Studies

    📣 OS NGD News

    🗃️ Data Structure

    🎨 Styling OS NGD Data

    Managing OS Select+Build recipes
    Editing OS Select+Build recipes
    Sharing OS Select+Build recipes
    Applying attribute filtering
    Creating a new data package
    Finding and downloading a data package
    Viewing an Order Summary file
    Deleting a data package
    Adding temporal filters
    Greenspace recipe guide

    OS NGD tutorials and demonstrators on More than Maps

    North Yorkshire Fire & Rescue Service case study
    Identifying hard to heat homes case study
    Supporting planning and new housing developments
    Office for National Statistics case study
    Land management, agriculture and telecoms
    More efficient, cost-effective land management
    More efficient land management
    Greater Manchester Ecology Unit case study
    Supporting environmental monitoring and regulation
    Identifying and mapping areas most vulnerable to climate-related flooding events
    Supporting the water industry in locating new reservoirs
    Scottish Canal's case study
    Speed data case study
    OS NGD tutorials and demonstrators
    'More than Maps' site
    PSGA Members area
    Partner Portal

    Note: Only these 10 individual feature types are needed for this recipe – do not select all feature types from the OS GB Address, OS Boundaries, OS Building Features, OS Functional Areas, OS Land Use Features, OS Named Features and OS Water Features Collections.

    You can, of course, tweak the recipe at the recipe creation or editing stage to include or exclude feature types depending on your use case.

    📖 Getting started with recipes guides

    🎯 Getting started with attribute filtering guide

    📚 Getting started with data packages guide

    🏡 Town and city planning looking at facilities and access to natural areas and environment

    Site
    Site Access Location
    Water
    Screenshot showing the tree view in the secondary navigation menu that opens when you create a recipe in OS Select+Build in the OS Data Hub. Three of the ten feature types needed for the town and city planning recipe are shown to have been selected in this screenshot: Retail Area Major, Retail Area Minor, and Building; the other seven feature types have also been selected, but aren't visible in the screenshot.
    Screenshot showing the tree view in the secondary navigation menu that opens when you create a recipe in OS Select+Build in the OS Data Hub. Three of the ten feature types needed for the town and city planning recipe are shown to have been selected in this screenshot: Retail Area Major, Retail Area Minor, and Building; the other seven feature types have also been selected but aren't visible in the screenshot.
    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
    Screenshot showing the tree view in the secondary navigation menu that opens when you create a recipe in OS Select+Build in the OS Data Hub. The Building Feature Type has been selected in this screenshot and the Choose Schema Version drop-down menu is visible in the right-hand-side panel, which lets you select the data schema version you want to use for the feature type.
    Screenshot of the OS Select+Build Recipe details screen showing a summary of the town and city planning recipe, including the selected feature types.
    Short YouTube video showing the OS NGD access methods of OS Select+Build and the OS NGD APIs.
    Select the desired
    .
  • Select a file format: CSV or GeoPackage.

  • Select the updates you want: Either not required or COU (Change-Only Update) frequency. There is also an option to select a one-off snapshot of a current or past date.

  • Set your initial supply date.

  • 4

    Find the data package you're looking for

    Scroll through the list to find a particular data package or use the search bar to search by data package name, data package number, or product name.

    Screenshot showing an example of the Data packages list screen in the OS Data Hub.

    Data packages linked to an OS NGD recipe can be identified by their prefix of 'OS NGD Recipe' against the recipe name in the Product column in the Data packages list.

    Screenshot showing an example of the 'OS NGD Recipe' prefix.
    5

    Download the desired data package

    • Once you have found the data package you want from the list, click the Download button in the Status column.

    • You are now within the Data package summary screen, where you can view and download files. Under 'Individual file downloads' in the bottom left-hand side of your screen, you will see a .zip file for every feature type in your data package order. Click on a file to download it.

    The start date of coverage for this supply.

    Validate the currency of your data to ensure the earliest date aligns with the expected supply window for your order frequency.

    validToDate

    The end date of coverage for this supply.

    Validate the currency of your data to ensure the latest date aligns with the expected supply window for your order frequency.

    recordCount

    The total number of records delivered in the file.

    Check that delivered entries match the number of records expected for your download.

    4

    Find the data package you are looking for

    Scroll through the list to find a particular data package or use the search bar to search by data package name, data package number, or product name.

    Screenshot showing an example of the Data packages list screen in the OS Data Hub.

    Data packages linked to an OS NGD recipe can be identified by their prefix of 'OS NGD Recipe' against the recipe name in the Product column in the Data packages list.

    Screenshot showing an example of the 'OS NGD Recipe' prefix.
    5

    Delete the package from the data packages summary screen

    • Click the Package options dropdown in the top right-hand side of your screen.

    • Click Delete package.

    Screenshot showing an example of a Data package summary screen in the OS Data Hub with the Package options dropdown open.

    A warning pop up will appear.

    • Click the Delete package button in the pop up.

    {
     "featureName": "bld-fts-buildingline",
     "crs": "http://www.opengis.net/def/crs/EPSG/0/27700",
     "schemaVersion": "1.0",
     "validFromDate": null,
     "validToDate": "2023-03-01",
     "recordCount": 202653
    }

    featureName

    The feature type delivered in this order.

    Validate the downloaded feature against your recipe.

    crs

    The coordinate reference system used for your supply.

    Validate the coordinate reference system against the CRS selected for your recipe.

    schemaVersion

    The OS NGD data schema version provided for the feature.

    Coordinate data schema updates with changes to your data.

    Creating data packages

    Finding and downloading existing data packages

    Deleting data packages

    Viewing Order Summary files

    Navigate to the OS Data Hub workspace

    Navigate to the OS Select+Build Recipe Library

    Find the recipe you plan to add a data package against

    Add details to the data package

    Best practice for selecting areas of interest

    Best practice when selecting an area of interest (AOI) for your data package is to:

    • Keep it simple: Minimise the number of vertices and avoid complex shapes.

    • Iterate: If you are uncertain of how much data you require, take a larger bounding box and reduce the area as you identify your requirements. The smaller the dataset, the easier it is to manipulate.

    • Add a Buffer zone: This gives you confidence that you have captured everything you require and includes marginal information that may affect decision-making.

    Finish creating the data package

    You will receive an email confirming that your data package is being created and another one when your new data package is ready to download.

    Please note:

    • When you order data through OS Select+Build, the data package/s you receive will be provided at a feature type level. Each feature type you order will be available to download as a .zip file. Currently, grouped files are not available for OS NGD data packages.

    • Single or multiple data packages can be created from a single defined recipe. Creating multiple data packages from a single recipe is useful if you want to select a different file format or area of interest for a recipe.

    • The Annual Full Supply order frequency option will not be available for a data package containing one (or more) of the new feature types or new data schema versions of existing feature types released in March and / or September of the current year. If you select an Annual Full Supply frequency for your OS NGD data order in OS Select+Build, we will provide you with the data as it was on 01 January of the current year. This means if a new feature type or a new data schema version of an existing feature type was released after 01 January and you order either of these as part of your Annual Full Supply, you will receive an empty data package for the newly released feature type / new data schema version of an existing feature type. The data for the new feature type / new data schema version of an existing feature type will then be included in your supply on the next 01 January after the release, after which point, data packages containing one of these feature types will no longer contain blank files.

    How do I find and download an existing data package?

    Log into your OS Data Hub account

    Navigate to the OS Data Hub workspace

    Navigate to Data packages

    What is the Order Summary file?

    How do I delete a data package?

    Log into your OS Data Hub account

    Navigate to the OS Data Hub workspace

    Navigate to Data packages

    OS Data Hub
    Screenshot of the OS Data Hub, showing the OS Select+Build Recipe Library screen.
    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
    Screenshot of the Add a data package screen in the OS Data Hub, showing an example of adding a data package to a recipe.
    Screenshot showing an example of adding a data package to a recipe using OS Select+Build in the OS Data Hub.
    A screenshot of the OS Data Hub home page showing the sign up and log in buttons in the top right hand corner
    Screenshot showing the OS Data Hub homepage.
    A screenshot of the OS Data Hub home page showing the sign up and log in buttons in the top right hand corner
    Screenshot showing the OS Data Hub homepage.
    A screenshot of the OS Data Hub home page showing the sign up and log in buttons in the top right hand corner

    validFromDate

    coordinate reference system

    Commercial Activity: Industrial Or Manufacturing – Locations where raw materials are extracted or processed, or where component parts are made into finished items. This classification typically only applied to larger sites > 1ha in extent.

  • Commercial Activity: Other – Locations where commercial activities occur, where a more detailed classification has not been determined or are not otherwise categorised.

  • This was caused by our original background mappings which classified a commercial site as Industrial or Manufacturing by default when no further detail was available. This misleadingly resulted in retail areas or offices displaying as places where raw materials are extracted and processed where we do not currently have a data source. This will be a target area for future improvements.

    Improvements to show the full lifecycle of a building in a single theme – OS NGD Buildings Theme

    In preparation for the OS NGD product release in September 2025, we will be making some background changes to the OS NGD Buildings Theme. Approximately 39 000 features representing under-construction buildings – currently classified under the OS Land Features Collection – will be reclassified into the OS Building Features Collection. This transition will begin in June 2025, with the data initially appearing in the Building Part Feature Type. In the September 2025 OS NGD product release, the same data will also be available in the corresponding Building Feature Type.

    These changes will enable a more complete view of the building lifecycle – from construction through to dereliction – within a single collection, ultimately delivering more valuable insights to our customers.

    Improved depiction of inland water polygons no longer splitting inland water polygons with Topographic Lines

    To improve customers’ ability to query and report using OS data, we will no longer be splitting inland water polygons where Topographic Lines for Ferry Alignments cross water polygons. As a result, Ferry Alignments will show as Minor Topographic Lines in both OS MasterMap Topography Layer and OS NGD themes, where Water polygon features formerly split by a ferry will merge into more logical single features.

    Improved coverage of OS Land Use Tier B attribution on Solar Panels

    Over 27 000 ‘Solar Panels on Bare Earth Or Grass’ within the OS NGD Structures Theme will have an OS Land Use Tier B of ‘Energy Generation’ added where they currently are null to improve accuracy of reporting for renewables.

    Improvements to ‘Status’ of Roofed Castle Wall in OS NGD Building Part Feature Type

    Currently 27 Roofed Castle Wall features are incorrectly listed with a Status of ‘Derelict’ in our Building Part Feature Type data. These are being updated to have a Status of ‘Unknown’ as there is no available information to confirm whether the features are in such disrepair that they can no longer serve their original purpose.

    Improved consistency of intertidal classifications on features in the OS NGD Land and OS NGD Water Themes

    As part of our background work to improve the data quality of features within the intertidal zone, 23 features currently attributed as ‘Inter Tidal + Reeds’ located in the OS NGD Water Theme will be reclassified and published in the OS NGD Land Theme as ‘Saltmarsh’ features with Is Tidal attribute = true in the product reflecting their correct environmental context. 

    Improved consistency of Weirs in the OS NGD Structures Theme

    To enhance the customer experience, we have revised mappings to consolidate almost all ‘weir’ and ‘roofed weir’ features into the OS NGD Structures Theme. Weirs that do not make up the tidal extent will now be published as Structures in all cases. Those that are necessary for tidal boundaries will remain in the OS NGD Water Theme. As a result, approximately 8 000 new features will be added to the Structure Line Feature Type, which sits within the OS Structure Features Collection of the OS NGD Structures Theme. The Change Type attribute will therefore show as ‘Moved From A Different Feature Type.’

    Knowing the location of weirs is useful for flood planning, monitoring freshwater ecosystems and environmental modelling.

    Please note, there are 53 roofed weirs which have not moved to the OS NGD Structures Theme as part of this data improvement, and these will remain in the OS NGD Buildings Theme. 

    Improved consistency of Slipways in the OS NGD Land Theme

    Previously, slipways were categorised into two separate themes within the OS NGD product. Slipways below the tidal extent were classified as Structures, while those above the tide line were classified as Land. To enhance the customer experience, we have revised the mappings to consolidate all slipway features previously in the OS NGD Structures Theme into the OS NGD Land Theme, with the Is Tidal attribute set to 'true'. In addition, to better the customer experience, this change also allows for easier implementation of lifecycle for the OS ESG (Slipways) product. As a result, approximately 3 800 weir features will be added to the Land Feature Type, and will be removed from the Structure Feature Type.

    Improvements to ‘Grandstands’ in the Building and Building Part Feature Types

    As part of ongoing improvements to the OS NGD, approximately 60 features currently in the OS Structure Features Collection with a classification of 'Grandstand' will move to the OS Building Features Collection, where they will have other descriptions such as ‘Stand’ to improve consistency and accuracy of capture of Building Access Locations.

    June 2025 – OS NGD GSS code data improvements for OS Building Features, OS Land Features, OS Transport Features, OS Structure Features and OS Water Features Collections

    We are pleased to share a recent enhancement which improves how administrative boundary changes are reflected in the OS NGD ‘Features’ Collections.

    We have enhanced the assignment and maintenance of Government Statistical Service (GSS) codes, which are used to accurately identify a wide range of UK geographical areas for statistical and administrative purposes. This improvement increases the precision and reliability of boundary representation within our datasets.

    The feature types affected are:

    • Building Part v2.0

    • Land v3.0

    • Road Track Or Path v3.0

    • Structures v3.0

    • Water v3.0

    This improvement will be incorporated in the June 2025 OS NGD 'Features' Collections daily updates from 13/06/2025. As a result of this improvement work, customers receiving daily updates may receive larger than usual Change-Only Updates (COUs) and customers taking monthly supplies may receive larger than usual COUs in their July 2025 data package.

    We anticipate similar levels of change in October 2025 and May 2026, aligned with updates to the OS Boundaries Collection, as we continue to deliver the most up-to-date data possible.

    As a result of work in collaboration with Verisk, there will be improvements made in June 2025 to the Basement Presence, Construction Material and Building Age attribution in the . This work has involved improving the processing of energy performance certificate (EPC) data to increase accuracy; changes in some capture type and confidence levels in OS NGD data may be seen.

    As a result of this improvement work, customers may receive larger than usual Change-Only Updates (COUs) if they take a daily supply of Building Feature Type data schema versions 2.0, 3.0 and 4.0 throughout June 2025 as the data flows through. Customers taking their supply monthly of this feature type may receive larger than usual COUs in their July 2025 data package. No action is required by customers.

    If you have any questions, please get in touch.

    May 2025 – Height data enhancement for OS NGD Structures Theme and OS NGD Buildings Theme data

    At Ordnance Survey, we are modernising our data creation platforms. This includes the creation of additional height data for our building and structures datasets. A recent key improvement we've made as part of these efforts was to improve the accuracy and granularity of the height evidence date attribute, which details the date of capture for the imagery used to derive the height data.

    Previously, height metadata was derived from large imagery flight blocks (exceeding 500km²), which sometimes required several flights over multiple days. This occasionally resulted in buildings and structures being assigned an imagery date different from the actual capture date.

    Our new system allows the population of imagery date metadata to a more granular level, using the appropriate flight block. This ensures there is only one imagery date per building or structure feature, giving a more accurate representation of height evidence date for a specific feature. As a result, from 10 May 2025, some customers using Change-Only Updates (COUs) may notice that a small number of height evidence dates have changed to slightly older dates as we move to the new system. This change reflects more accurate data, not incorrect data.

    This impacts some features in the following data schema versions:

    • Structure Feature Type v1.0, v2.0 and v3.0

    • Building Part Feature Type v1.0 and v2.0

    • Building Feature Type v4.0

    Some customers may also see a larger than usual supply of COU if taking a daily supply of the above data schema versions as change begins to flow into the data from the start of our flying season, where data is captured using aerial imagery during the National Cyclic Revision (NCR) programme.

    The .xlsx file below contains a complete list of features across all feature types that have a revised height evidence date that's earlier than previously stated.

    Please see for more information about versioning in the OS NGD.

    March 2026 – Improvements to the Field Boundary Feature Type

    February 2026 – Improvements to the OS Land Features, OS Land Use Features, OS Structure Features and OS Water Features Collections

    September 2025 to March 2026 – Improvements to data coverage for Bus Lane and Cycle Lane Feature Types

    2025 OS NGD improvements

    September 2025 to December 2025 – Improvements to data coverage for Bus Lane and Cycle Lane Feature Types

    July 2025 – Improvements to the OS Building Features, OS Land Features, OS Land Use Features, OS Structures Features and OS Water Features Collections

    OS NGD planned enhancements outlined in our roadmap

    The OS Data Products Roadmap is available to view on Aha! It outlines our focus areas for enhancements and new releases for the OS NGD and our Download products (Premium and OpenData products) over the next two years. Planned improvements to existing OS NGD data are also called out on the OS Data Products Roadmap and will appear on this page when they have been completed.

    The new data enhancements for the OS NGD are expected to continue to launch twice a year in spring and autumn. Access enhancements related to the OS NGD are not tied to spring and autumn new data enhancement releases and can occur throughout the year.

    Recently delivered data and access enhancements to the OS NGD are listed on the What's New page.

    Field Boundary Feature Type
    Field Boundary pages of the Using OS NGD Data section
    Field Boundary Feature Type
    Bus Lane
    Cycle Lane
    Bus Lane
    Cycle Lane
    Creating green corridors
  • Improving public health

  • Managing flood risk

  • Evaluating climate change resilience

  • Modelling urban heat islands

  • Infrastructure planning

  • Managing assets

  • Improving public safety

  • Calculating deprivation indexes

  • Property development

  • The guide below provides a geospatial toolkit for helping you understand green spaces across Great Britain; its step-by-step instructions outline how to select relevant pieces of topographic data from the OS NGD and weave them into a greenspace recipe. The suggested recipe will help support research, management, planning, auditing and policy for the greenspace use cases outlined above.

    Applying filters (see step 8) in OS Select+Build to the four OS NGD feature types at the recipe creation (or recipe editing) stage lets you exclude features that are not relevant to greenspace use cases (for example, manmade surface).

    You can adapt the suggested greenspace recipe at the recipe creation or editing stage so that it fully meets your needs.

    OS NGD data provides full greenspace coverage for Great Britain. As can be seen in the map below, the density of green spaces varies by area, with fewer green spaces in urban areas.

    Map showing the density of green spaces across Great Britain provided by the greenspace recipe.

    You might currently be using the OS MasterMap Greenspace Layer product to get a detailed dataset of the green spaces present within urban areas in Great Britain. This product will reach its End of Life and be withdrawn on 31 March 2027. More information about the product's withdrawal is available from the End of Life Notice – OS MasterMap Greenspace Layer page.

    While there's no like-for-like replacement download product for OS MasterMap Greenspace Layer, you can get equivalent greenspace data from the OS NGD by either:

    • Creating a recipe in OS Select+Build if you'd like a data download; the guide on this page provides step-by-step instructions on how to create this recipe.

    • Using OS NGD API – Features; the Accessing greenspace data using OS NGD API – Features guide outlines how to connect to OS NGD API – Features, filter data, then load it into QGIS or ArcGIS Pro.

    A detailed comparison of OS MasterMap Greenspace Layer and the OS NGD, including improvements offered by the latter, is available on the Comparison of OS MasterMap Greenspace Layer and OS NGD page.

    The information supplied in the single feature type in OS MasterMap Greenspace Layer is provided by four corresponding feature types across three collections within the OS NGD:

    Theme
    Collection
    Feature Type

    OS NGD Land

    OS Land Features

    OS NGD Transport

    OS Transport Features

    OS NGD Transport

    OS Transport Features

    To create the greenspace recipe in OS Select+Build:

    1

    Log into your account

    Click Log in on the OS Data Hub menu bar to log into your account.

    Screenshot showing the OS Data Hub homepage.
    2

    Navigate to the OS Data Hub workspace

    Select Data from the menu bar to view your workspace.

    3

    Navigate to the OS Select+Build Recipe Library

    Choose Downloads > OS Select+Build Recipe Library from the left-hand-side secondary navigation menu.

    4

    Click the Create a new recipe button at the top right-hand-side of the screen.

    5
    • Give your recipe a descriptive name in the Recipe name dialog box on the left-hand-side of the screen.

    • Add a detailed description for your recipe (this is optional, but it's useful if other team members will be accessing the recipe).

    6

    Select your OS NGD data by choosing the themes, collections and feature types you want to include in your recipe. You'll need to select the following four feature types from the Themes panel on the left-hand-side of the screen:

    • Land (found within Land > Land Features > Land)

    • Rail (found within Transport > Transport Features > Rail)

    7

    Selecting a data schema version for a feature type is an optional step; if you don't choose a particular data schema version for a feature type, OS Select+Build will always select the latest available data schema version for you for each feature type by default. We recommend using the pre-selected latest data schema version for feature types unless you have a specific need to use an earlier one. (See the for more information on data schema versioning in the OS NGD.)

    If you wish to choose which schema version (where applicable) you'd like to receive the data in for a feature type, click on the feature type name within the tree view in the secondary navigation menu, then choose a data schema version from the Choose Data Schema drop-down box in the right-hand side panel.

    8

    To select only the required natural features, click on the filter icon next to the name of the feature type you want to add a filter to in the theme selection tree.

    The Advanced Filter Options panel will then slide into view from the right-hand side of the screen and you can begin to build your filters. To add a filter, click on +Add rule, then choose the appropriate options from the drop-down menus.

    Please refer to the table below to apply the correct the filter settings to the four feature types, taking care to select the correct operator:

    Feature Type
    Filter
    Operator
    Values
    9

    Once you have applied filters to the four feature types, click the Create recipe button to complete the recipe creation process. Your new recipe will now instantly be available in your OS Select+Build Recipe Library.

    You can view a summary of the completed greenspace recipe, including the required feature types and filters, if you click Data > Downloads > OS Select+Build Recipe Library > *your recipe's name* > View all filters.

    The recipe summary should look like the screenshot below:


    More information on creating, editing and deleting recipes in OS Select+Build and on adding attribute filters to recipes can be found in the following guides:

    Once you've created your recipe, you'll need to add a data package to receive the data. Data packages allow you to select the format, update frequency and area of interest for the required data.

    The following guide will help you to create a data package from your new recipe:

    You can also use OS NGD API – Features to access OS NGD greenspace data; this is a good alternative to creating a recipe in OS Select+Build and ordering data.

    The following guide outlines how to connect to OS NGD API – Features, filter data, then load it into QGIS or ArcGIS Pro.

    What is greenspace?

    Use cases

    What is the greenspace recipe?

    Coverage provided by the greenspace recipe

    Migration from OS MasterMap Greenspace Layer

    Creating the recipe

    What's next?

    Further guidance on creating, editing and deleting recipes

    Add a data package to your recipe

    Use OS NGD API – Features to access greenspace data

    20mph zones – It will be safer for a child to walk along roads with lower speed limits, and these roads are more likely to have traffic calming measures in place which will also make walking along pavements safer for pedestrians.

    Applying filters (see steps 8 and 9 below) in OS Select+Build to two of the feature types at the recipe creation (or recipe editing) stage lets you focus on residential and education addresses and exclude motorways and dual carriageways from the data.

    You can adapt the suggested safer routes to schools recipe at the recipe creation or editing stage so that it fully meets your needs. The filters chosen for this recipe are a suggestion and you can amend them depending on your requirements for safe routes.

    The following five feature types are included in the safer routes to schools recipe:

    Theme
    Collection
    Feature Type

    OS NGD Address

    OS GB Address

    OS NGD Transport

    OS Routing And Asset Management Information (RAMI)

    OS NGD Transport

    OS Transport Network

    To create the safer routes to schools recipe in OS Select+Build:

    1

    Log into your account

    Click Log in on the OS Data Hub menu bar to log into your account.

    Screenshot showing the OS Data Hub homepage.
    2

    Navigate to the OS Data Hub workspace

    Select Data from the menu bar to view your workspace.

    3

    Navigate to the OS Select+Build Recipe Library

    Choose Downloads > OS Select+Build Recipe Library from the left-hand-side secondary navigation menu.

    4

    Click the Create a new recipe button at the top right-hand-side of the screen.

    5
    • Give your recipe a descriptive name in the Recipe name dialog box on the left-hand-side of the screen.

    • Add a detailed description for your recipe (this is optional, but it's useful if other team members will be accessing the recipe).

    6

    Select your OS NGD data by choosing the themes, collections and feature types you want to include in your recipe. You'll need to select the following five feature types from the Themes panel on the left-hand-side of the screen:

    • Built Address (found within Address > GB Address > Built Address)

    • Average And Indicative Speed (found within Transport > RAMI > Average And Indicative Speed)

    7

    Selecting a data schema version for a feature type is an optional step; if you don't choose a particular data schema version for a feature type, OS Select+Build will always select the latest available data schema version for you for each feature type by default. We recommend using the pre-selected latest data schema version for feature types unless you have a specific need to use an earlier one. (See the for more information on data schema versioning in the OS NGD.)

    If you wish to choose which schema version (where applicable) you'd like to receive the data in for a feature type, click on the feature type name within the tree view in the secondary navigation menu, then choose a data schema version from the Choose Data Schema drop-down box in the right-hand side panel.

    8

    To add a filter to the Built Address Feature Type:

    • Click on the filter icon to the right of Built Address in the theme selection tree.

    The Advanced Filter Options panel will then slide into view from the right-hand side of the screen and you can begin to build your filter.

    In the Advanced Filter Options panel:

    • Click the + Add rule button, then select primaryClassificationDescription

    9

    To add a filter to the Road Link Feature Type:

    • Click on the filter icon to the right of Road Link in the theme selection tree.

    The Advanced Filter Options panel will then slide into view from the right-hand side of the screen and you can begin to build your filter.

    In the Advanced Filter Options panel:

    • Click the + Add rule button, then select description

    10

    Once you have applied filters to the Built Address and Road Link Feature Types, click the Create recipe button to complete the recipe creation process. Your new recipe will now instantly be available in your OS Select+Build Recipe Library.

    You can view a summary of the completed safer routes to schools recipe, including the required feature types and filters, if you click Data > Downloads > OS Select+Build Recipe Library > *your recipe's name* > View all filters.

    The recipe summary should look like the screenshot below:


    More information on creating, editing and deleting recipes in OS Select+Build and on adding attribute filters to recipes can be found in the following guides:

    Once you've created your recipe, you'll need to add a data package to receive the data. Data packages allow you to select the format, update frequency and area of interest for the required data.

    The following guide will help you to create a data package from your new recipe:

    Once you've created your recipe and added a data package to it to receive the data, you can import the data into your chosen GIS (geographic information system) to analyse it or create maps.

    The following guide will help you to create a map in QGIS:

    What is the safer routes to schools recipe?

    Feature types required

    Creating the recipe

    What's next?

    Further guidance on creating, editing and deleting recipes

    Add a data package to your recipe

    Create a safer routes to schools map from your recipe using QGIS

    A shared recipe cannot be deleted.

    📚 Getting started with data packages

    (Optional) Choose a data schema version

    Data schema versioning page
    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub. This screen shows high-level details about an example recipe, including the recipe name, its author, the creation date, a description of the recipe, and the OS NGD themes present within the recipe.
    Screenshot of the OS Select+Build Recipe Library screen, which shows high-level details about the contents of an example recipe.
    Screenshot of the OS Data Hub, showing the OS Select+Build recipe details screen. This screen shows in-depth information about an example recipe, including the recipe name, a description of the recipe, the filters used, the creation date, its author, and the OS NGD themes, collections and feature types present within it.
    Screenshot of the OS Select+Build Recipe details screen, which shows in-depth information about the contents of an example recipe.
    Screenshot of the OS Select+Build Recipe creator screen within the OS Data Hub, showing an example of creating a new recipe and selecting a data schema version for a feature type.
    Screenshot of the OS Data Hub, showing the OS Select+Build Recipe Library screen.
    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
    Screenshot of the delete recipe dialogue showing a warning about associated data packages.

    Getting started with attribute filtering

    Step-by-step instructions on how to add attribute filters to recipes in your OS Select+Build Recipe Library.

    Introducing attribute filtering

    Attribute filtering is a new concept which we have introduced as part of OS Select+Build. The filters can help you to narrow down the exact data you need from the OS NGD. If required, you can add attribute filters to individual feature types when you create a new bespoke recipe of OS NGD data using OS Select+Build. The managing OS Select+Build recipes page has step-by-step instructions on how to create a new recipe. You can also add, edit or remove attribute filters to / in / from feature types in an existing recipe of OS NGD data.

    Attribute filtering is an optional step for those with advanced OS data knowledge.

    You can:

    • Add attribute filters to feature types in a new recipe

    • Add, edit or remove attribute filters to / in / from feature types in an existing recipe

    The following sub-sections cover:

    🔃 How do I add attribute filters to a new recipe?

    To add attribute filters to a new recipe:

    1

    Click Login on the OS Data Hub menu bar to log into your account.

    2

    Select Data from the menu bar to view your workspace.

    3

    Choose Downloads > OS Select+Build Recipe Library from the left hand side secondary navigation menu. You will then be taken to your organisation's OS Select+Build Recipe Library.

    4

    Click the Create a new recipe button, adding the relevant details to your recipe.

    See the for more information on creating recipes.

    5

    Click the filter icon next to the feature type(s) you want to add a filter to in the theme selection tree.

    The Advanced Filter Options panel will then slide into view from the right and you can begin to build your filter(s):

    • For a , select +Add rule.

    • For a more complex , select +Add group.

    6

    Click the Create recipe button. Your new recipe with filters will now instantly be available in your OS Select+Build Recipe Library.

    To add attribute filters to an existing recipe:

    1

    Click Login on the OS Data Hub menu bar to log into your account.

    2

    Select Data from the menu bar to view your workspace.

    3

    Choose Downloads > OS Select+Build Recipe Library from the left hand side secondary navigation menu. You will then be taken to your organisation's OS Select+Build Recipe Library.

    In the following worked example of creating a simple filter, we will use the OS NGD Buildings Theme and select the Building Part Feature Type from the OS Building Features Collection. Our aim is to build a filter to select buildings where education is recorded as the land use.

    1

    Click Login on the OS Data Hub menu bar to log into your account.

    2

    Select Data from the menu bar to view your workspace.

    3

    Choose Downloads > OS Select+Build Recipe Library from the left hand side secondary navigation menu. You will then be taken to your organisation's OS Select+Build Recipe Library.

    What if, in addition to the simple filter above (returning results for buildings with a land use of education), we want those results to show only buildings over 15metres in height? What if you also wanted to add an additional filter to show buildings with a land use of rail? To achieve this, you could create a nested filter using the + Add group option.

    1
    2
    • In the Advanced Filter Options panel, click + Add group, then select OSLandUseTierA from the first drop-down.

    • Leave the operator in the second drop-down as: = (i.e. the equal sign), then select Education from the third drop-down.

    3

    To check what filters have been applied to feature types in an existing recipe:

    1

    Click Login on the OS Data Hub menu bar to log into your account.

    2

    Select Data from the menu bar to view your workspace.

    3

    Choose Downloads > OS Select+Build Recipe Library from the left hand side secondary navigation menu. You will then be taken to your organisation's OS Select+Build Recipe Library.

    Identifying higher-risk buildings recipe guide

    A guide with detailed step-by-step instructions outlining how you can create a recipe in OS Select+Build to identify higher-risk buildings.

    What is the identifying higher-risk buildings recipe?

    The guide below provides a geospatial toolkit that will help you use OS NGD data to identify if a building in occupation in Great Britain is classified as higher-risk by the Building Safety Act 2022 and the Higher-Risk Buildings (Descriptions and Supplementary Provisions) Regulations 2023.

    Higher-risk buildings criteria

    The criteria used to identify higher-risk buildings within this recipe guide have been drawn from official Government guidance – please see 'criteria for determining whether a building is a higher-risk building during the occupation phase of the new higher-risk regime' from the Gov.uk website for full details.

    The key criteria are:

    • Minimum of 2 residential units

    • Minimum of 7 storeys or minimum height of 18m

    The following exemptions apply:

    • Where a building meets the above criteria but is comprised entirely of one or more of the following categories, it's exempt from classification as a higher-risk building:

      • Care homes

      • Hospitals

      • Secure residential institutions

    The following two feature types are included in the identifying higher-risk buildings recipe:

    Theme
    Collection
    Feature Type

    You can adapt the suggested identifying higher-risk buildings recipe at the recipe creation or editing stage so that it fully meets your needs.

    Applying filters (see steps 8 and 9 below) in OS Select+Build to both feature types at the recipe creation (or recipe editing) stage lets you target the right types of residential and commercial addresses, buildings over a certain height, and buildings with over a certain number of floors. Filtering will also reduce the number of features being downloaded.

    You can skip the filtering steps (8 and 9) at the recipe creation stage, download all features for the two feature types, then subsequently filter the data later in your chosen geographic information system (GIS) or relational database management system (RDBMS).

    To create the identifying higher-risk buildings recipe in OS Select+Build:

    1

    Click Log in on the OS Data Hub menu bar to log into your account.

    2

    Select Data from the menu bar to view your workspace.

    3

    Choose Downloads > OS Select+Build Recipe Library from the left-hand-side secondary navigation menu.


    More information on creating, editing and deleting recipes in OS Select+Build and on adding attribute filters to recipes can be found in the following guides:

    Once you've created your recipe, you'll need to add a data package to receive the data. Data packages allow you to select the format, update frequency and area of interest for the required data.

    The following guide will help you to create a data package from your new recipe:

    Once you've created your recipe and added a data package to it to receive the data, you can import the data into your chosen GIS to analyse it or create maps.

    The following guides will help you to create maps to identify higher-risk buildings in ArcGIS Pro and QGIS:

    OS NGD Address

    Introduction to the theme

    The OS NGD Address Theme provides a complete and definitive view of UK address data. It's designed to underpin a range of analytical use cases and provide the most detailed view of an address and its lifecycle.

    The OS NGD Address Theme contains all of the address data found in the OS AddressBase Premium product:

    • Local authority addresses

    • Royal Mail postal addresses

    • Lifecycle data

    • Addresses for features that are not conventionally addressable (such as warehouses, car parks, etc.)

    • Multi-lingual addresses

    • Alternative addresses

    However, the OS NGD Address Theme builds on AddressBase Premium data by providing data with up-to-daily currency that is simple to use, understand and interrogate. This makes the data more accessible to non-address experts as it is easy to plug and play it into databases or a GIS (geographic information system).

    The OS NGD Address Theme is interoperable with other OS NGD themes through cross-reference information and the UPRN (Unique Property Reference Number) as the key identifier, allowing you to easily combine multiple datasets to answer analytical questions.

    Address data is collated from Local Land and Property Gazetteers (LLPG), which are maintained by local authorities in England and Wales, and also from local authorities in Scotland, who maintain the Corporate Address Gazetteer (CAG). These data sources are supplemented by the Royal Mail Postcode Address File (PAF), references to Valuation Office Agency (VOA) data in England and Wales, and additional addresses and coordinates from Ordnance Survey.

    In September 2025, we added the Royal Mail Address Feature Type to the two addressing collections; this feature type combines full Royal Mail PAF content with Ordnance Survey’s authoritative geospatial attribution.

    Highlights of data schema version 1.0 of the Royal Mail Address Feature Type include:

    • Full PAF content

    • Multiple UDPRN (Unique Delivery Point Reference Number) to UPRN matches

    • OS-derived enhanced attribution and geometry for PAF records

    From October 2026, the Royal Mail Address Feature Type includes additional enhancements; the key enhancements unique to data schema version 2.0 of this feature type are:

    • Full NYB content: 100% inclusion of Royal Mail’s Not Yet Built (NYB) addresses, with UDPRN as the primary key. OS-derived geometry is provided for NYB records.

    • Full MR content: 100% inclusion of Royal Mail’s Multiple Residence (MR) addresses, provided as a related component, with UMRRN (Unique Multiple Residence Reference Number) as the primary key.

    • NYB and MR matched to UPRNs: Identifying where Royal Mail's NYB and MR addresses have been associated to a UPRN.

    • Further enhanced attribution: Additional OS-derived metadata, including Royal Mail Full Address, Country, Primary UPRN Match, Postcode Area, Postcode District and Postcode Sector attribution.

    The OS NGD Address Theme is made up of the OS GB Address and OS Islands Address Collections, and each collection is comprised of six feature types: Built Address, Historic Address, Non-Addressable Object, Pre-Build Address, Royal Mail Address and Street Address.

    The OS NGD Address Theme data structure diagram below is applicable to the latest data schema versions of all address feature types (that is, data schema version 3.0 of Built Address, Historic Address, Non-Addressable Object and Pre-Build Address, data schema version 1.0 of Street Address, and data schema version 2.0 of Royal Mail Address):

    The address related components provide supplementary non-geospatial information or context about addresses; full information about them is available from the . (Please see for information on data schema versioning in the OS NGD.)

    • Data schema version 3.0 onward of the Built Address, Historic Address, Non-Addressable Object and Pre-Build Address Feature Types in each collection are supported by the following three addressable object related components, which provide supplementary information against each UPRN:

      • : These provide alternative address labels where they exist for the ‘current’ address represented on a given feature type.

      • : These provide additional VOA classification information.

    At least one of the following four unique identifiers is provided with each feature within the OS NGD Address Theme:

    • Unique Property Reference Number (UPRN): The primary identifier and unique key for this theme. A UPRN is a unique and persistent numeric identifier for every addressable location in Great Britain. Each address record has a UPRN, assigned by local authorities in England, Wales and Scotland or Ordnance Survey depending on the type of address. 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. Independent of any changes being made the UPRN associated to an address is never changed, meaning the unique identifier remains persistent and reliable.

    • Unique Street Reference Number (USRN): A USRN is a unique and persistent identifier for a street which is curated by Local Authority custodians in England, Wales or Scotland.

    • OSID (Ordnance Survey Identifier): A primary identifier and unique key used in other OS NGD themes. OSIDs are referenced in the OS NGD Address Theme for purposes of cross-refencing to other themes.

    Two unique Postcode Address File (PAF) identifiers are provided with Royal Mail Address features within the OS NGD Address Theme:

    • Unique Delivery Point Reference Number (UDPRN): A UDPRN is a unique identifier that Royal Mail assigns to identify a specific delivery point (for example, a mailbox or business unit). Each UDPRN is an up to 8-character code that can be used instead of the current address keys on PAF.

    • 🆕 Unique Multiple Residence Reference Number (UMRRN): UMRRN (Unique Multiple Residence Reference Number) for multiple Royal Mail addresses that share a single delivery point. Each UMRRN is an up to 8-character code that can be used instead of the current address keys on PAF.

    • are available on our site; these guides detail the layers, formats and attribution available for data in the OS GB Address and OS Islands Address Collections.

    • : Discover how data from the OS NGD Address, Buildings, Land Use and Water Themes provides the trusted foundation water companies need to plan future and current water infrastructure at scale.

    • : Find out why financial institutions should integrate accurate location data from the OS NGD Address, Buildings, Land Use and Water Themes into their climate risk frameworks.

    Multiple Residence

    The Multiple Residence Component (also known as MR) provides data developed to identify addresses that are delivered to a shared delivery point; this means premises with one front door, or delivery point, that has been subdivided into flats, units or other separate occupancies. Multiple residence data provide a detailed address structure for these properties.

    Example image showing how to link between unique identifiers on Royal Mail related components, Royal Mail features (PAF or NYB) and local authority records. A background map has been included for context.

    For more information about multiple residence attribution, please consult chapter 18 'Multiple Residence' of the Royal Mail Programmer's Guide.

    Customers taking data schema version 2.0 onward of the Royal Mail Address Feature Types in GeoPackage format will receive the following in their data package:

    • Feature type: Royal Mail Address

    • Related components: Multiple Residence, Delivery Point Alias and Other Alias

    However, the three related components (Multiple Residence, Delivery Point Alias and Other Alias) will only be provided for Royal Mail Address features if the Description attribute is 'Postcode Address File'. Against all other Royal Mail Address features, the related components will be populated as null.

    Temporal filtering

    The earliest date on which you can request a one-off snapshot of a date in the past for data in this feature type is 08 October 2026.

    Any data temporally filtered earlier than the specified earliest date noted above for the data schema version may contain data inconsistencies.

    More information about temporal filtering is available from the Getting started with temporal filtering guide.

    Related component attributes

    The following sub-sections provide details about the attributes included with this related component, their data types in the different output formats, and other important metadata about them.

    umrrn

    Royal Mail's Unique Multiple Residence Reference Number (UMRRN).

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • Max Length: 8

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0

    The Unique Property Reference Number (UPRN) to which a Unique Multiple Residence Reference Number (UMRRN) has been matched.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0

    Unique Delivery Point Reference Number (UDPRN) assigned by Royal Mail as a persistent identifier.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0

    Date of the feature version to which this related component applies. This is used along with the Feature Type ID attribute to join the component to the Royal Mail Address Feature Type.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0

    The name of the organisation operating from the Multiple Residence address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 60

    • OS Select+Build Filterable: No

    For some organisations, department name is indicated because mail is received by subdivisions of the main organisation at distinct delivery points.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 60

    • OS Select+Build Filterable: No

    The sub building name and / or number are identifiers for subdivisions of properties.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 30

    • OS Select+Build Filterable: No

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

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 50

    • OS Select+Build Filterable: No

    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 Building Name or the Sub Building Name fields.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 4

    • OS Select+Build Filterable: No

    In certain places, for example, town centres, there are named thoroughfares within other named thoroughfares, for example, parades of shops on a high street where different parades have their own identity. For example, KINGS PARADE, HIGH STREET and QUEENS PARADE, HIGH STREET.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 80

    • OS Select+Build Filterable: No

    A thoroughfare is a road, track or named access route on which there are Royal Mail delivery points, for example, HIGH STREET.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 80

    • OS Select+Build Filterable: No

    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.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: No

    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.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: No

    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.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 30

    • OS Select+Build Filterable: No

    The postcode unit that the Address is situated within. A postcode is an abbreviated form of address, made up of combinations of between five and seven alphanumeric characters. These alphanumeric characters are used by Royal Mail to help with the automated sorting of mail. A postcode may cover between 1 and 100 addresses. Postcodes (for example, NW6 4DP) are comprised of two components. The first component is the outward code (or ‘outcode’), which is the first two to four characters of a postcode, constituting the postcode area and the postcode district, for example, NW6. The outward code is the part of the postcode that enables mail to be sent from the accepting office to the correct area for delivery. The second component of a postcode is the inward code (or ‘incode’), which is the last three characters of the postcode, constituting the postcode sector and the postcode unit, for example, 4DP. The inward code is used to sort mail at the local delivery office.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 8

    • OS Select+Build Filterable: Yes

    Describes the address as a small or large user as defined by Royal Mail.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 10

    A two-character code uniquely identifying an individual delivery point within a postcode.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 2

    • OS Select+Build Filterable: No

    Ceremonial County

    A ceremonial county is an area that has an appointed Lord Lieutenant and High Sheriff and is used for ceremonial purposes in relation to the monarchy. These areas are referred to as ceremonial counties in England, as Scottish lieutenancy areas in Scotland, and as preserved counties in Wales.

    Legally, the ceremonial counties are defined by the Lieutenancies Act 1997 as "Counties and areas for the purposes of the lieutenancies in Great Britain" with reference to the areas used for local government.

    Ceremonial counties are not updated; therefore, the lifecycle dates will not change.

    Temporal filtering

    The earliest date on which you can request a one-off snapshot of a date in the past for data in this feature type is 29 September 2022.

    Any data temporally filtered earlier than the specified earliest date noted above for the data schema version may contain data inconsistencies.

    Feature type attributes

    The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

    Comma-separated values (CSV) file format is universally supported for easy ingestion into all major database products. Before loading OS NGD data contained in CSV files into a database, it is necessary to create relevant tables. Data definition language (DDL) statements for PostgreSQL, SQL Server and Oracle can be accessed in our .

    For instructions on loading CSV files, see the guide.

    osid

    Primary identifier for the feature. The OSID is a Globally Unique Identifier (GUID) and requires no centralised authority to ensure uniqueness. Note that the same OSID can occur in more than one feature type when a single feature is represented multiple times in the OS NGD.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 36

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Date when the version was last updated.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The date this version of the feature became the latest version.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The date this version of the feature was superseded by an update or ceased to exist.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The type of change that generated a new version of the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    Geometry for the feature.

    • Data Types: Geometry (GPKG), WKT (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The measured area of the geometry in square metres.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 18

    • Scale: 6

    The OS NGD theme to which this feature belongs.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 40

    A single descriptive value intended for a quick understanding of what the feature represents.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    Name assigned to identify the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 254

    • OS Select+Build Filterable: Yes

    The language of name1, provided as a 3-digit ISO 639-2 code ('eng, 'cym', 'gla').

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    The alternative language name assigned to identify the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 254

    • OS Select+Build Filterable: Yes

    The language of name2, provided as a 3-digit ISO 639-2 code ('eng, 'cym', 'gla').

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    A single description value for boundary type.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    The inland area of the feature in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    The non-inland area in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    The total area in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    OS NGD News

    This section contains pages covering new data and access enhancements released for the OS NGD, planned future enhancements on our roadmap, recent data improvements and the change log.

    The Autumn 2026 data enhancements releases for the OS NGD are now live. To find out more information about what these data enhancements include, please see the .

    The fifth OS recommended recipe guide has published on the site:

    • : The guide provides a geospatial toolkit to help you identify the level of access to natural areas from existing addresses, both residential and commercial; its step-by-step instructions outline how to select relevant pieces of addressing, administrative and statistical units, buildings, geographical names, land use and water data from the OS NGD and weave them into a recipe. The suggested recipe will be useful for town and city planners who want to assess access to natural areas from existing commercial and residential addresses, and provide evidence to help inform compliance with Natural England's Green Infrastructure Framework.

    The fourth OS recommended recipe guide has published on the site:

    Current Known Data Issues

    This page lists known current live data issues in relation to the OS National Geographic Database (NGD) themes, collections and feature types.

    As and when we resolve a known data issue, we will move it to the page. To report an issue that's not currently listed on these pages, please use the .

    The generic data issue in the table below impacts multiple OS NGD themes:

    Data Issue Name
    Data Issue Description
    Data Issue Identification Date

    Devolved Parliament Electoral Region

    The Scottish Parliament electoral region is a grouping of Scottish Parliament constituencies. The Welsh Parliament electoral region is a grouping of Welsh Parliament constituencies.

    The earliest date on which you can request a one-off snapshot of a date in the past for data in this feature type is 29 September 2022.

    Any data temporally filtered earlier than the specified earliest date noted above for the data schema version may contain data inconsistencies.

    The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

    Primary identifier for the feature. The OSID is a Globally Unique Identifier (GUID) and requires no centralised authority to ensure uniqueness. Note that the same OSID can occur in more than one feature type when a single feature is represented multiple times in the OS NGD.

    • Data Types: String (GPKG), String (CSV)

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Geometry Type: MultiPolygon

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0

  • Data Schema Version: 1.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Data Schema Version: 1.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • versiondate

    versionavailablefromdate

    versionavailabletodate

    changetype

    geometry

    geometry_area

    theme

    description

    name1_text

    name1_language

    name2_text

    name2_language

    boundarytype

    landareahectares

    tidalareahectares

    totalareahectares

    Loading OS NGD CSV files into databases

    changetypevalue
    themevalue
    ceremonialcountydescriptionvalue
    languagevalue
    languagevalue
    boundarytypevalue
    OS NGD Resources GitHub repository
    Getting Started with CSV

    June 2025 – Building Feature Type data improvements for Basement Presence, Construction Material and Building Age

    Building Feature Type
    Data schema versioning
    BFH_BackwardsInTime_ProdFeatures.xlsx
    12MB
    Open
    Data Schema Version: 2.0
    Data Schema Version: 2.0
    Data Schema Version: 2.0
    Data Schema Version: 2.0
    Data Schema Version: 2.0
    Data Schema Version: 2.0
    Data Schema Version: 2.0
    Data Schema Version: 2.0
    Data Schema Version: 2.0
    Data Schema Version: 2.0
    Data Schema Version: 2.0
    OS Select+Build Filterable: No
  • Data Schema Version: 2.0

  • Data Schema Version: 2.0

    Please note that the Delivery Point Alias and Other Alias Related Component tables are included in product design for future compatibility but are not currently populated; customers should expect these files to be empty until a future data enhancement enables OS to supply the Royal Mail alias data. Please see the FAQs for more information.

    uprn

    udprn

    featuretypeversiondate

    multiresorganisationname

    multiresdepartmentname

    multiressubbuildingname

    multiresbuildingname

    multiresbuildingnumber

    multiresdependentthoroughfare

    multiresthoroughfare

    multiresdoubledependentlocality

    multiresdependentlocality

    multiresposttown

    multirespostcode

    multirespostcodetype

    multiresdeliverypointsuffix

    Multiple Residence Component for Royal Mail Address Feature Type data schema version 2.0 onward

    postcodetypevalue
    Example image showing how to link between unique identifiers on Royal Mail related components, Royal Mail features (PAF or NYB) and local authority records. A background map has been included for context. An acronym key is also provided expanding the acronyms for UPRN, UDRPN and UMRRN.

    Nullable: false

  • Max Length: 36

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Topographic identifier (TOID) of the feature, as published in the OS MasterMap suite of products.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 20

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0

    Date when the version was last updated.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The date this version of the feature became the latest version.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The date this version of the feature was superseded by an update or ceased to exist.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The type of change that generated a new version of the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: changetypevalue

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Geometry for the feature.

    • Data Types: Geometry (GPKG), WKT (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    • Geometry Type: MultiPolygon

    The measured area of the geometry in square metres.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 18

    • Scale: 6

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The OS NGD theme to which this feature belongs.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: themevalue

    • Max Length: 40

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    A single descriptive value intended for a quick understanding of what the feature represents.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: devolvedparliamentelectoralregiondescriptionvalue

    • Max Length: 50

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0

    Name assigned to identify the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 254

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0

    The language of name1, provided as a 3-digit ISO 639-2 code ('eng, 'cym', 'gla').

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: languagevalue

    • Max Length: 3

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The alternative language name assigned to identify the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 254

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0

    The language of name2, provided as a 3-digit ISO 639-2 code ('eng, 'cym', 'gla').

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: languagevalue

    • Max Length: 3

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Set to the census / Government Statistical Service (GSS) Code for the boundary, for example, E10000014.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 10

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0

    A single description value for boundary type.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: boundarytypevalue

    • Max Length: 50

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0

    The inland area of the feature in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The non-inland area in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The total area in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Temporal filtering

    Feature type attributes

    Loading OS NGD CSV files into databases

    Comma-separated values (CSV) file format is universally supported for easy ingestion into all major database products. Before loading OS NGD data contained in CSV files into a database, it is necessary to create relevant tables. Data definition language (DDL) statements for PostgreSQL, SQL Server and Oracle can be accessed in our OS NGD Resources GitHub repository.

    For instructions on loading CSV files, see the Getting Started with CSV guide.

    osid

    toid

    versiondate

    versionavailablefromdate

    versionavailabletodate

    changetype

    geometry

    geometry_area

    theme

    description

    name1_text

    name1_language

    name2_text

    name2_language

    gsscode

    boundarytype

    landareahectares

    tidalareahectares

    totalareahectares

    Road Track Or Path (found within Transport > Transport Features > Road Track Or Path)

  • Water (found within Water > Water Features > Water)

  • Screenshot showing the tree view in the secondary navigation menu that opens when you create a recipe in OS Select+Build in the OS Data Hub. Three of the four feature types needed for the greenspace recipe are shown to have been selected in this screenshot: Rail, Road Track Or Path, and Water; Land has also been selected, but isn't visible in the screenshot.

    Land

    OSLandCoverTierA

    In

    Mineral, Multiple, Open Vegetation, Open Vegetation And Mineral, Trees

    Rail

    OSLandCoverTierA

    In

    Mineral, Open Vegetation, Trees

    Road Track Or Path

    OSLandCoverTierA

    In

    Mineral, Open Vegetation, Trees, Water

    Water

    description

    Not Equal

    Sea

    Screenshot of the OS Select+Build Recipe Edit recipe screen with the Advanced Filter Options panel showing, where you can add a filter to a recipe. The filter options selected for the Land Feature Type are shown in this screenshot.

    Once you have added the necessary filter settings for a feature type, click the Apply filter button to lock them in.

    Filters need to be set one at a time, with one filter per feature type for the greenspace recipe.

    Screenshot of the OS Select+Build Recipe Edit recipe screen with the Advanced Filter Options panel showing, where you can add a filter to a recipe. The filter options selected for the Water Feature Type are shown in this screenshot.

    OS NGD Water

    OS Water Features

    Water

    📖 Getting started with recipes guides

    🎯 Getting started with attribute filtering guide

    📚 Getting started with data packages guide

    🌳 Accessing greenspace data using OS NGD API – Features

    Choose Create a new recipe

    Give the recipe a name and description

    Select the feature types

    (Optional) Choose a data schema version

    Add a filter to each feature type in your recipe

    Why are filters needed in this recipe?

    • The Land, Rail, and Road Track Or Path Feature Types include both manmade and natural features. OS Select+Build provides the option to apply filters on certain attributes when creating a recipe so that only the features and attribution that are needed are included in the data. In this case, you can filter on the OS Land Cover Tier A attribute to select just the feature types used in this recipe, so that only features that have one of the natural land cover values will be included in the data. More information on the OS Land Cover Tier A attribute values is available from the Land Cover Tier A Value Code List.

    • A filter is also required on the Water Feature Type on the Description attribute to filter out areas of tidal water that are considered part of the sea; thus leaving inland water features (for example, rivers, ponds, lakes or reservoirs) plus tidal water in river estuaries and sea lochs that can be considered as an amenity in the recipe.

    Finish creating the recipe

    Data schema versioning page
    Land
    Rail
    Road Track Or Path
    OS Data Hub
    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
    Screenshot showing the tree view in the secondary navigation menu that opens when you create a recipe in OS Select+Build in the OS Data Hub. The Land Feature Type has been selected in this screenshot and the Choose Schema Version drop-down menu is visible in the right-hand-side panel, which lets you select the data schema version you want for the feature type.
    Screenshot showing the tree view in the secondary navigation menu that opens when you create a recipe in OS Select+Build in the OS Data Hub. The Land Feature Type has been selected in this screenshot and the Choose Schema Version drop-down menu is visible in the right-hand-side panel, which lets you select the data schema version you want for the feature type.
    Screenshot of the OS Select+Build Recipe details screen showing a summary of the greenspace recipe, including selected feature types and their data schema versions, plus all filters applied.
    Screenshot of the OS Select+Build Recipe details screen showing a summary of the greenspace recipe, including selected feature types and their data schema versions, plus all filters applied.
    Filter icon in OS Select+Build
    Map of Great Britain showing the density of green spaces provided by the OS NGD greenspace recipe. OS NGD data has full GB coverage. There are fewer green spaces in heavily urban areas like major cities, for example, London.
    A screenshot of the OS Data Hub home page showing the sign up and log in buttons in the top right hand corner

    Note: Only these four individual feature types are needed for this recipe – do not select all feature types from the OS Land Features, OS Transport Features and OS Water Features Collections.

    Connecting Link (found within Transport > Transport Network > Connecting Link)

  • Path Link (found within Transport > Transport Network > Path Link)

  • Road Link (found within Transport > Transport Network > Road Link)

  • Screenshot showing the tree view in the secondary navigation menu that opens when you create a recipe in OS Select+Build in the OS Data Hub. Three of the five feature types needed for the safer routes to schools recipe are shown to have been selected in this screenshot: Connecting Link, Path Link and Road Link; Average And Indicative Speed, and Built Address have also been selected, but aren't visible in the screenshot.
    from the first drop-down.
  • Leave the operator in the second drop-down as: = (i.e. the equal sign), then select Residential from the third drop-down.

  • Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build. The first rule of the filter options needed for the Built Address Feature Type is shown in this screenshot.
    • Click the + Add rule button to add a second rule below the primaryClassificationDescription rule.

    • In the second rule, select secondaryClassificationDescription from the first drop-down, set the operator in the second drop-down as = (i.e. the equal sign), then select Education from the third drop-down.

    • Before continuing, select whether you would like the rules within the group to have an And or an Or condition. In this case, you should select Or from the And / Or selector.

    Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build. The two rules filter options selected for the Built Address Feature Type are shown in this screenshot.
    • Click the Apply filter button.

    • Close the Advanced Filter Options panel.

    from the first drop-down.
  • Change the operator in the second drop-down to Not Equal, then select Dual Carriageway from the third drop-down.

  • Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build. The first rule of the filter options needed for the Road Link Feature Type is shown in this screenshot.
    • Click the + Add rule button to add a second rule below the description rule.

    • In the second rule, select roadClassification from the first drop-down, set the operator in the second drop-down as Not Equal, then select Motorway from the third drop-down.

    • Before continuing, select whether you would like the rules within the group to have an And or an Or condition. In this case, you should select And from the And / Or selector.

    Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build. The two rules filter options selected for the Road Link Feature Type are shown in this screenshot.
    • Click the Apply filter button.

    • Close the Advanced Filter Options panel.

    OS NGD Transport

    OS Transport Network

    Path Link

    OS NGD Transport

    OS Transport Network

    Road Link

    📖 Getting started with recipes guides

    🎯 Getting started with attribute filtering guide

    📚 Getting started with data packages guide

    🗺️ Guide for using QGIS to create a safer route to school map

    Choose Create a new recipe

    Give the recipe a name and description

    Select the feature types

    (Optional) Choose a data schema version

    Add a filter to the Built Address Feature Type

    Why are filters needed in this recipe?

    OS Select+Build provides the option to apply filters on certain attributes when creating a recipe so that only the features and attribution that are needed are included in the data.

    • A filter is required on the Built Address Feature Type so that only residential and education addresses appear in the data.

    • A filter is also required on the Road Link Feature Type on the Description and Road Classification attributes to filter out dual carriageways and motorways from the data.

    Filters need to be set one at a time for the feature types that need to use them.

    Add a filter to the Road Link Feature Type

    Finish creating the recipe

    Data schema versioning page
    Built Address
    Average And Indicative Speed
    Connecting Link
    OS Data Hub
    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
    Screenshot showing the tree view in the secondary navigation menu that opens when you create a recipe in OS Select+Build in the OS Data Hub. The Path Link Feature Type has been selected in this screenshot and the Choose Schema Version drop-down menu is visible in the right-hand-side panel, which lets you select the data schema version you want for the feature type.
    Screenshot showing the tree view in the secondary navigation menu that opens when you create a recipe in OS Select+Build in the OS Data Hub. The Path Link Feature Type has been selected in this screenshot and the Choose Schema Version drop-down menu is visible in the right-hand-side panel, which lets you select the data schema version you want to use for the feature type.
    Screenshot of the theme selection tree in OS Select+Build. The Address, GB Address and Built Address boxes have been selected. A filter option is visible to the right of the Built Address name.
    Screenshot of the theme selection tree in OS Select+Build.
    Screenshot of the theme selection tree in OS Select+Build. The Transport, Transport Network, Connecting Link, Path Link and Road Link boxes have been selected. A filter option is visible to the right of the Connecting Link and Road Link names.
    Screenshot of the theme selection tree in OS Select+Build.
    Screenshot of the OS Select+Build Recipe details screen showing a summary of the safer routes to schools recipe, including selected feature types and their data schema versions, plus all filters applied.
    Screenshot of the OS Select+Build Recipe details screen showing a summary of the safer routes to schools recipe, including selected feature types and their data schema versions, plus all filters applied.
    Filter icon in OS Select+Build
    Filter icon in OS Select+Build
    A screenshot of the OS Data Hub home page showing the sign up and log in buttons in the top right hand corner

    Note: Only these five individual feature types are needed for this recipe – do not select all feature types from the OS GB Address, OS RAMI and OS Transport Network Collections.

    Once you have added all of your relevant filters, click Apply Filter.
    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
    4

    Find the recipe you want to edit

    In your OS NGD Select+Build Recipe Library, scroll or search for the recipe you would like to edit. Once you've found the recipe, click on its name; you'll be taken to the Recipe details screen.

    5

    Edit the recipe

    In the Recipe details screen, click on the Recipe actions dropdown and select Edit recipe.

    Screenshot of the OS Select+Build Recipe details screen with the Recipe actions dropdown open, showing where you can share, edit or delete a recipe.

    You'll now be able to add filters (see Step 6) or remove filters (see Step 7) from feature types in the recipe.

    6

    Add a filter to a feature type

    • Click the filter icon next to the feature type you want to add a filter to in the selection tree for the recipe.

    The Advanced Filter Options panel will then slide into view from the right and you can begin to build your filter(s):

    • For a simple filter, select +Add rule.

    • For a more complex , select +Add group.

    • Once you have added all of your relevant filters, click Apply Filter.

    • Select Save changes.

    • Add a description of the change you have made, then select Save changes.

    7

    Remove a filter from a feature type

    • Click the Edit filter iconnext to the feature type you want to remove a filter from in the selection tree for the recipe.

    • When the Advanced Filter Options panel slides into view from the right, select Clear all filters.

    Screenshot of the OS Select+Build Recipe Edit recipe screen with the Advanced Filter Options panel showing. There is one filter applied to the Building Part Feature Type.
    • Select Save changes.

    • Add a description of the change you have made, then select Save changes.

    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
    4

    Create a new recipe

    Click the Create a new recipe button.

    See the Managing OS Select+Build recipes page for more information on creating recipes.

    5

    Add details to the recipe

    • Give your recipe a descriptive name.

    • Add a detailed description for your recipe

    • Select your OS NGD data by choosing the themes, collections and feature types you want to include in your recipe. For this worked example:

      • Click on the arrow to the right of Buildings within the theme selection tree to see the collections available within the theme, then click on the arrow to the right of Buildings Features to see the feature types available within that collection.

      • Click on the check box next to Building Part to select that feature type.

    6

    Add a filter to the Building Part Feature Type where the OS Land Use Tier A attribute is set to Education

    • Click on the filter icon to the right of Building Part.

    The Advanced Filter Options panel will slide into view from the right, where you can begin to build your filter(s):

    • In the Advanced Filter Options panel, click + Add rule, then select OSLandUseTierA from the first drop-down.

    Screenshot of adding a rule in the Advanced Filter Options panel in OS Select+Build.
    • Leave the operator in the second drop-down as: = (i.e. the equal sign), then select Education from the third drop-down.

    • Click the Apply filter button.

    7

    Finish creating the recipe

    Click the Create recipe button. Your new recipe will now instantly be available in your OS Select+Build Recipe Library.

    Add a nested filter to the Building Part Feature Type

    • Click + Add rule to add a second rule below the OSLandUseTierA rule.

    • In the second rule, select relativeHeightMaximum from the first drop-down, set the operator in the second drop-down as > (i.e. the more than sign), and type 15 in the input box.

    • Before continuing, select whether you would like the rules within the group to have an And or an Or condition. In this case, you should select And from the And / Or selector.

    Screenshot of creating a nested filer in the Advanced Filter Options panel in OS Select+Build.
    • Next, click + Add group.

    • The application has drawn an extra box for you. Whatever rules are contained inside this box will be evaluated together, before combining with any rules outside the box.

    • Before continuing, select whether you would like the rule in the second group to have an And or an Or condition. In this case, you should select Or from the And / Or selector.

    • In the rule in the extra box, select OSLandUseTierA from the first drop-down, leave the operator as = (i.e. the equal sign) in the second drop-down, and select Transport: Rail from the third drop-down.

    4

    Finish creating the recipe

    Click the Create recipe button. Your new recipe will now instantly be available in your OS Select+Build Recipe Library.

    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
    4

    Find the recipe you want to check for filter presence on

    In your OS NGD Select+Build Recipe Library, scroll or search for the recipe you would like to edit. Once you've found the recipe, click on its name; you'll be taken to the Recipe details screen.

    5

    Check for filter presence

    You are now within the Recipe details screen, where you can view detailed information about the recipe, including the recipe's name, the date it was created, etc. If filters have been applied to the recipe, a filter icon(i.e. a black funnel symbol) will appear under the recipe name alongside text stating: 'Filters have been applied to this recipe'.

    • Click View all filters to view all of the filters that have been applied to feature types in the recipe.

    In the example recipe below, you can see that there is a filter icon(i.e. the black funnel symbol) against the Building Part Feature Type; therefore, this feature type has filters applied to it.

    Screenshot of the OS Select+Build Recipe details screen, which shows in-depth information about the contents of an example recipe.

    Adding filters to a new recipe

    Adding filters to an existing recipe

    Creating a simple filter (worked example)

    Creating a more complex nested filter (worked example)

    Checking if filters are used in an existing recipe

    Log into your OS Data Hub account

    Navigate to the OS Data Hub workspace

    Navigate to the OS Select+Build Recipe Library

    Create a recipe

    Add filters to feature types in your recipe

    Finish creating the recipe

    How do I add attribute filters to an existing recipe?

    Log into your OS Data Hub account

    Navigate to the OS Data Hub workspace

    Navigate to the OS Select+Build Recipe Library

    Worked example of creating a simple filter

    Log into your OS Data Hub account

    Navigate to the OS Data Hub workspace

    Navigate to the OS Select+Build Recipe Library

    Your filter will return buildings where education (Education) is recorded as the land use (OS Land Use Tier A attribute).

    Worked example of creating a nested filter

    Follow the steps outlined above for creating a simple filter for Building Part until you reach the Advanced Filter Options panel step (Step 6).

    Add a simple filter to the Building Part Feature Type

    Your filter will return results for buildings (Building Part) that have either an education (Education) land use if that building is over 15 metres high or a railway land use (Transport:Rail).

    How do I check if filters are used in an existing recipe?

    Log into your OS Data Hub account

    Navigate to the OS Data Hub workspace

    Navigate to the OS Select+Build Recipe Library

    Managing OS Select+Build recipes page
    simple filter
    nested filter
    A screenshot of the OS Data Hub home page showing the sign up and log in buttons in the top right hand corner
    Screenshot showing the OS Data Hub homepage.
    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
    A screenshot of the OS Data Hub home page showing the sign up and log in buttons in the top right hand corner
    Screenshot showing the OS Data Hub homepage.
    A screenshot of the OS Data Hub home page showing the sign up and log in buttons in the top right hand corner
    Screenshot showing the OS Data Hub homepage.
    A screenshot of the OS Data Hub home page showing the sign up and log in buttons in the top right hand corner
    Screenshot showing the OS Data Hub homepage.
    Filter icon in OS Select+Build
    Hotels (serviced apartments and short-term lets do not fall within the meaning of hotel)
  • Military barracks

  • 4

    Choose Create a new recipe

    Click the Create a new recipe button at the top right-hand-side of the screen.

    5

    Give the recipe a name and description

    • Give your recipe a descriptive name in the Recipe name dialog box on the left-hand-side of the screen.

    • Add a detailed description for your recipe (this is optional, but it's useful if other team members will be accessing the recipe).

    6

    Select the feature types

    Select your OS NGD data by choosing the themes, collections and feature types you want to include in your recipe. You'll need to select the following two feature types from the Themes panel on the left-hand-side of the screen:

    • Built Address (found within Address > GB Address > Built Address)

    • Building (found within Buildings > Building Features > Building)

    Note: Only these two individual feature types are needed for this recipe – do not select all feature types from the OS GB Address and OS Building Features Collections.

    Screenshot showing the tree view in the secondary navigation menu that opens when you create a recipe in OS Select+Build in the OS Data Hub. Both of the feature types needed for the identifying higher-risk buildings recipe are shown to have been selected in this screenshot: Built Address and Building.
    7

    (Optional) Choose a data schema version

    Selecting a data schema version for a feature type is an optional step; if you don't choose a particular data schema version for a feature type, OS Select+Build will always select the latest available data schema version for you for each feature type by default. We recommend using the pre-selected latest data schema version for feature types unless you have a specific need to use an earlier one. (See the Data schema versioning page for more information on data schema versioning in the OS NGD.)

    If you wish to choose which schema version (where applicable) you'd like to receive the data in for a feature type, click on the feature type name within the tree view in the secondary navigation menu, then choose a data schema version from the Choose Data Schema drop-down box in the right-hand side panel.

    Screenshot showing the tree view in the secondary navigation menu that opens when you create a recipe in OS Select+Build in the OS Data Hub. The Building Feature Type has been selected in this screenshot and the Choose Schema Version drop-down menu is visible in the right-hand-side panel, which lets you select the data schema version you want to use for the feature type.
    8

    Add a filter to the Built Address Feature Type

    OS Select+Build provides the option to apply filters on certain attributes when creating a recipe so that only the features and attribution that are needed are included in the data. Filters need to be set one at a time for each feature type in this recipe.

    For this recipe, attribute filters will be used on both feature types to target the right types of residential and commercial addresses, buildings over a certain height, and buildings with over a certain number of floors. Filtering will also reduce the number of features being downloaded.

    However, you may wish to download all features for the two feature types instead, then subsequently filter the data later in your chosen geographic information system (GIS) or relational database management system (RDBMS) – if so, just skip steps 8 and 9.

    To add a filter to the Built Address Feature Type:

    • Click on the filter icon to the right of Built Address in the theme selection tree.

    Screenshot of the theme selection tree in OS Select+Build.

    The Advanced Filter Options panel will then slide into view from the right-hand side of the screen and you can begin to build your filter. For this filter, you'll need to add two groups, then assign rules to both groups.​

    In the Advanced Filter Options panel:

    • Click the + Add Group button twice.

    • Select whether you would like the relationship between the two groups to have an And or an Or condition. In this case, you should select Or from the And / Or selector.

    In the first group:

    • Click the + Add rule button twice, which will give you three rules in the first group.

    • In the first rule, select primaryClassificationDescription from the first drop-down. Leave the operator in the second drop-down as: = (i.e. the equal sign), then select Residential from the third drop-down.

    • In the second rule, select secondaryClassificationDescription from the first drop-down, set the operator in the second drop-down as In, then select Dwelling, House In Multiple Occupation, and Residential Institution from the third drop-down.

    In the second group:

    • Click the + Add rule button three times, which will give you four rules in the second group.

    • In the first rule, select primaryClassificationDescription from the first drop-down. Leave the operator in the second drop-down as: = (i.e. the equal sign), then select Commercial from the third drop-down.

    • In the second rule, select secondaryClassificationDescription from the first drop-down, set the operator in the second drop-down as = (i.e. the equal sign), then select Hotel / Motel / Boarding / Guest House from the third drop-down.

    • Click the Apply filter button.

    • Close the Advanced Filter Options panel.

    9

    Add a filter to the Building Feature Type

    To add a filter to the Building Feature Type:

    • Click on the filter icon to the right of Building in the theme selection tree.

    Screenshot of the theme selection tree in OS Select+Build.

    The Advanced Filter Options panel will then slide into view from the right-hand side of the screen and you can begin to build your filter. This time you'll add a rule first, followed by a group, then you'll add two rules to the group.​

    In the Advanced Filter Options panel:

    • Click the + Add rule button, then select physicalState from the first drop-down. Leave the operator in the second drop-down as: = (i.e. the equal sign), then select Built from the third drop-down.

    • Click the + Add Group button.

    • Select whether you would like the relationship between the rule and the group to have an And or an Or condition. In this case, you should select And from the And / Or selector.

    In the group:

    • In the first rule, select numberOfFloors from the first drop-down, set the operator in the second drop-down as Over Or Equal To (>=), then type 7 into the third box.

    • Click the + Add rule button to add a second rule to the group.

    • In the second rule, select height_relativeMax_m from the first drop-down, set the operator in the second drop-down as Over Or Equal To (>=), then type 18 into the third box.

    • Click the Apply filter button.

    • Close the Advanced Filter Options panel.

    10

    Finish creating the recipe

    Once you've applied filters to the two feature types, click the Create recipe button to complete the recipe creation process. Your new recipe will now instantly be available in your OS Select+Build Recipe Library.

    You can view a summary of the completed safer routes to schools recipe, including the required feature types and filters, if you click Data > Downloads > OS Select+Build Recipe Library > *your recipe's name* > View all filters.

    The recipe summary should look like the screenshot below:

    Screenshot of the OS Select+Build Recipe details screen showing a summary of the identifying higher-risk buildings recipe, including selected feature types and their data schema versions, plus all filters applied.

    OS NGD Address

    OS GB Address

    Built Address

    OS NGD Buildings

    OS Building Features

    Building

    Feature types required

    Creating the recipe

    Log into your OS Data Hub account

    Navigate to the OS Data Hub workspace

    Navigate to the OS Select+Build Recipe Library

    What's next?

    Further guidance on creating, editing and deleting recipes

    Add a data package to your recipe

    Creating maps to identify higher-risk buildings from your recipe using QGIS and ArcGIS Pro

    A screenshot of the OS Data Hub home page showing the sign up and log in buttons in the top right hand corner
    Screenshot showing the OS Data Hub homepage.
    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
    Related Entity: These contain cross-reference relationship information between addresses and features in other OS NGD themes (such as buildings, sites, roads and boundaries) or third-party data sets.
  • 🆕 Data schema version 2.0 onward of the Royal Mail Address Feature Type in each collection is supported by the following three Royal Mail related components, which provide supplementary information against each UDPRN:

    • Multiple Residence: These provide data developed to identify addresses that are delivered to a shared delivery point; this means premises with one front door, or delivery point, that has been subdivided into flats, units or other separate occupancies. Multiple residence data provide a detailed address structure for these properties.

    • Delivery Point Alias: These provide alias data related to a delivery point address, sourcing data from Royal Mail's Delivery Point Alias (DPA) table. DPA information provides additional Delivery Point Information, including Trading Names and Building Name details where a Building Number is the official building identifier.

    • : These provide alternate names for counties, localities and thoroughfares.

  • Data schema version 1.0 of the Street Address Feature Type is not supported by any related components.

  • TOID (Topographic Identifier): An additional secondary identifier which can aid further data linking. TOIDs are an optional attribute and therefore will not always be provided with every feature.

  • OS NGD Address data is not available through the APIs

    Please note that the OS NGD Address Theme is only available via OS Select+Build (the bespoke OS NGD data download service) and is not available via OS NGD API – Features or OS NGD API – Tiles. You can access OS Select+Build through the OS Data Hub.

    🔃 Recent data enhancements to the theme

    🔃 Data structure

    🔃 Data structure diagram

    🔃 Superseded data structure diagrams for the OS NGD Address Theme

    🆕 The OS NGD Address Theme data structure diagram below is applicable to the older (maintenance) data schema versions (1.0 and 1.1) of Royal Mail Address, to the latest data schema version (1.0) of Street Address, and to the latest data schema version (3.0) of Built Address, Historic Address, Non-Addressable Object and Pre-Build Address:

    Superseded OS NGD Address Theme data structure diagram showing the theme name, collection names, feature type names, and related component names. It's applicable to is applicable to the older (maintenance) data schema versions (1.0 and 1.1) of Royal Mail Address, to the latest data schema version (1.0) of Street Address, and to the latest data schema version (3.0) of Built Address, Historic Address, Non-Addressable Object and Pre-Build Address.

    The OS NGD Address Theme data structure diagram below is applicable to the older (maintenance) data schema versions of four of the address feature types (i.e. data schema versions 1.0 and 2.0 of Built Address, Historic Address, Non-Addressable Object and Pre-Build Address) and to the latest data schema version (1.0) of Street Address:

    Superseded OS NGD Address Theme data structure diagram showing the theme name, collection names, feature type names, and related component names. It's applicable to the older (maintenance) data schema versions of four of the address feature types (i.e. data schema versions 1.0 and 2.0 of Built Address, Historic Address, Non-Addressable Object and Pre-Build Address) and to the latest data schema version (1.0) of Street Address
    • Until September 2025, was the fourth related component in the OS NGD. It has been discontinued in the latest data schema version 3.0 of the Built Address, Historic Address, Non-Addressable Object and Pre-Build Address Feature Types in the OS GB Address and OS Islands Address Collections, which released in September 2025.

    • The Postal Address Related Component contained delivery point data from the Royal Mail Postcode Address File (PAF). This information is now available in the Royal Mail Address Feature Type (which launched in September 2025), which can be found in the OS GB Address and OS Islands Address Collections.

    🔃 Address related components

    Unique identifiers

    OS unique identifiers

    🔃 PAF unique identifiers

    Useful links

    Address Related Components page
    Data schema versioning
    Alternate Address
    Other Classification
    Introductory guides to OS NGD Address Theme data
    More than Maps
    Supporting the water industry in locating new reservoirs
    Helping financial institutions meet the Bank of England's climate standards
    Example image showing Royal Mail Address features (data schema version 2.0 onward) against a background map. Features with a description of Not Yet Built are highlighted by red dots, and the attribution available for one such feature is highlighted in a pop up box. Features with a description of Postcode Address File are highlighted by blue dots, and the attribution available for one such feature is highlighted in a pop up box.
    Example image showing the some of the attribution held on the Royal Mail Address features (data schema version 2.0 onward) and how to discern Postcode Address File records from Not Yet Built records. A background map has been included for context.
    OS NGD Address Theme data structure diagram showing the theme name, collection names, feature type names, and related component names. The data structure diagram is applicable to the latest data schema versions of all address feature types.
    OS NGD Address Theme data structure diagram showing the theme name, collection names, feature type names, and related component names; it's applicable to the latest data schema versions of all address feature types.
    • Identifying crossing points and bottlenecks: The guide provides a geospatial toolkit for helping you identify the location of bridges, tunnels, fords and crossing points using the OS NGD; its step-by-step instructions outline how to select relevant pieces of addressing, structures, transport and water data from the OS NGD and weave them into a recipe. The suggested recipe will be useful for organisations (particularly emergency services) that need to understand critical infrastructure and mobility restrictions for vehicles and pedestrians.

    A new 'Transport networks in the OS NGD' explainer has been added to the site; this explainer goes through transport networks in the OS NGD and how the data and feature types in the collections fit together. It covers the following topics:

    • Building routable transport networks

    • Road, path, ferry and rail networks

    • Routing information

    • Streets and asset management information

    • Other road network information

    • National street gazetteers, GeoPlace and Improvement Service

    • Transport features

    A new 'Understanding land use in the OS NGD' guide has been added to the site; this guide contains specific advice on how to make the most of OS NGD Land Use data and includes the following topics:

    • How OS represents human activity or the economic function of an area or piece of land

    • How OS Land Use Tier A and Tier B classifications are assigned and maintained

    • How Sites relate spatially to surrounding features

    • How address records are matched and summarised

    • How Site Description values map across to National Land Use Database (NLUD) values

    • How OS Land Use Tier A and Tier B classifications map across to one another

    • How Site Description values map across to OS Land Use Tier A and Tier B classifications

    • Which Sites have populated Status attribute values

    Two more OS recommended recipe guides have published on the site:

    • Identifying higher-risk buildings recipe guide – The guide contains detailed step-by-step instructions outlining how you can create a recipe in OS Select+Build to identify higher-risk buildings. It provides a geospatial toolkit that will help you use OS NGD data to identify if a building in occupation in Great Britain is classified as higher-risk by the Building Safety Act 2022 and the Higher-Risk Buildings (Descriptions and Supplementary Provisions) Regulations 2023.

    • Safer routes to schools recipe guide – The guide provides a geospatial toolkit for helping you calculate safer routes to schools across Great Britain; its step-by-step instructions outline how to select relevant pieces of addressing, routing and transport network data from the OS NGD and weave them into a recipe in OS Select+Build.

    The first OS recommended recipe guide was published on the site: Greenspace recipe guide. This guide provides a geospatial toolkit to help you understand green spaces across Great Britain; the step-by-step instructions outline how to select relevant pieces of topographic data from the OS NGD and weave them into a greenspace recipe in OS Select+Build.

    The suggested recipe will help support research, management, planning, auditing and policy for greenspace use cases.

    We expect to add further OS recommended recipe guides over time.

    The Spring 2026 data enhancements releases for the OS NGD are now live. To find out more information about what these enhancements include, please see the 'What's New?' page.

    OS NGD data enhancements releases now live

    The Autumn 2025 data enhancements releases for the OS NGD are now live. To find out more information about what these enhancements include, please see the 'What's New?' page.

    Improvements to data in the OS Building Features, OS Land Features, OS Land Use Features, OS Structure Features and OS Water Features Collections

    We are making numerous improvements to data in the OS Building Features, OS Land Features, OS Land Use Features, OS Structures Features and OS Water Features Collections in July 2025; to find out information about what these improvements include, please see the OS NGD Improvements page.

    Edit a recipe functionality added to OS Select+Build

    You can now edit a recipe in OS Select+Build to add or remove themes / feature types, or change attribute filtering or data schema versions. Please see 'How do I edit a recipe?' on the Downloading with OS Select+Build page for more details.

    OS NGD GSS code data improvements for OS Building Features, OS Structure Features, OS Land Features, OS Transport Features and OS NGD Water Features Collections

    We have enhanced the assignment and maintenance of Government Statistical Service (GSS) codes, which are used to accurately identify a wide range of UK geographical areas for statistical and administrative purposes. This improvement increases the precision and reliability of boundary representation within our datasets. To find out more information about what these improvements include, please see the .

    Building Feature Type data improvements for Basement Presence, Construction Material and Number of Floors

    As a result of work in collaboration with Verisk, there will be improvements made in June 2025 to the Basement Presence, Construction Material and Number of Floors attribution in the . To find out more information about what these improvements include, please see the .

    Height data enhancement for OS NGD Structures Theme and OS NGD Buildings Theme data

    A new enhancement to the way OS NGD Structures Theme and OS NGD Buildings Theme data is created is now live. To find out more information about what these enhancements include, please see the .

    OS NGD enhancements release now live

    The March 2025 enhancements release for the OS NGD is now live. To find out more information about what these enhancements include, please see the .

    OS NGD Address Christmas shutdown

    There will be no daily updates of OS NGD Address over the Christmas shutdown period (24/12/2024–01/01/2025). Updates will resume as normal on 02 January 2025.

    OS NGD Data Viewer now available

    We've added links to the new OS NGD Data Viewer to this site (under the 'Using OS NGD Data' section and in the OS NGD Sample Data Information page). The viewer lets you visualise product sample data online for three areas (Exeter, Newport and Inverness).

    Sample data for most OS NGD feature types are available. The sample data always use the latest data schema version available for each feature type.

    OS NGD enhancements release now live

    The September 2024 enhancements release for the OS NGD is now live. To find out more information about what these enhancements include, please see the 'What's New?' page.

    Improvement to UPRNs in the Site Feature Type, OS NGD Land Use Theme

    Improvement details

    The Site Feature Type within the OS NGD Land Use Theme includes an attribute that references the primary Unique Property Reference Number (UPRN) for the site extent. Previously, the Primary UPRN attribute was only populated when there was a single address within the site extent. The improvement introduces new logic to determine the population of this attribute with the appropriate primary UPRN when there is more than one UPRN within a site extent.

    Approximately 1.4 million sites are being improved as a result of this improvement.

    The improvement will be available to customers automatically through the OS NGD access services of OS Select+Build and OS NGD API – Features.

    Impact to customers

    Customers do not need to take any direct action as a result of this improvement. On 19 August 2024, some customers may have experienced a slight delay in receiving their daily OS Select+Build orders or on any new orders placed that day.

    Customers with an existing order that includes the Site Feature Type may have noticed an increase in the size of their change-only update (COU) file on 19 August 2024 or might notice an increase in the size of their next monthly update on 01 September 2024, as approximately 1.4 million sites are being improved.

    All of the OS NGD access services (OS Select+Build and the OS NGD APIs) will remain available to customers with no disruption to service availability.

    OS NGD Buildings Theme COU pause

    There is planned maintenance scheduled for the OS NGD Buildings Theme from Saturday 20 July 2024 to Monday 22 July 2024 to run an upgrade to one of our background systems which underpins the OS NGD. This maintenance is needed to enhance the data which will be made available in the OS NGD Buildings Theme in September 2024.

    During the planned maintenance period, the OS NGD Buildings Theme will not have any updates available and the daily Change-Only Update (COU) files received will be empty. In addition, the data within OS Select+Build and OS NGD API – Features will not be updated daily for the OS NGD Buildings Theme.

    At the end of the maintenance period, all the changes will be made available and any daily COU files are likely to be larger than normal.

    Any customers receiving monthly COU files will not be affected.

    OS NGD Features Collections bug fixes

    From 07 June to 08 June 2024, bug fixes are being applied to 1.6 million features across the OS NGD Features Collections, as part of our ongoing efforts to provide better data.

    These improvements include fixes to Associated Structure, Land Use Tier A and Land Use Tier B attribute values.

    Planned maintenance on six OS NGD themes

    Background system maintenance for the OS NGD is required to deliver the enhancements scheduled for September 2024. The planned maintenance period will be from Sunday 16 June through to Saturday 29 June, at the latest.

    Throughout the maintenance period, all the OS NGD access services (OS Select+Build and the OS NGD APIs) will remain available to customers with no disruption to the service availability. The data within these services will not be updated daily with surveyed change for the following affected OS NGD collections:

    • OS Building Features

    OS NGD enhancements release now live

    The March 2024 enhancements release for the OS NGD is now live. To find out more information about what these enhancements include, please see our .


    📣 Recent announcements

    2026 announcements

    🎉 Autumn 2026 – OS NGD data enhancements releases now live

    🏡 October 2026 – OS NGD access enhancement

    🌉 September 2026 – OS NGD access enhancement

    'What's New?' page
    Town and city planning recipe guide

    A high-level summary of new data and access enhancements recently released for the OS NGD. This page also gives a link to the OS Data Products Roadmap, which sets out planned OS NGD enhancements for the next two years.

    A high-level summary of data improvements implemented throughout the year for the OS NGD.

    This page lists all changes made to OS NGD documentation. Changes will be made for a variety of reasons, including reflecting any alterations made to the OS NGD data itself as we enhance and improve the offering, plus simple improvements to the documentation to aid understanding.

    🚘 August 2026 – OS NGD access enhancement

    🏞️ July 2026 – OS NGD access enhancement

    🧑‍🍳 June 2026 – OS NGD access enhancement

    👩‍🍳 April 2026 – OS NGD access enhancement

    🎉 Spring 2026 – OS NGD data enhancements releases now live

    2025 announcements

    2024 announcements

    What's next?

    29/09/2022

    Data Issue Name
    Data Issue Description
    Data Issue Identification Date

    Missing data update group

    We are aware of an issue affecting daily COU OS GB Address Collection orders from 16 July 2026 where one data update group was not applied. Customers receiving data schema version 3.0 of the following feature types will be impacted:

    • add-gb-builtaddress

    • add-gb-historicaddress

    • add-gb-nonaddressableobject

    • add-gb-prebuildaddress

    16/07/2026

    Small numbers of UPRNs appearing across lifecycle feature types in COUs

    We are aware of an issue that affected the OS NGD Address Theme during February and March 2026, where a small number of Unique Property Reference Numbers are appearing in more than one lifecycle feature type (i.e. present in both the Built Address Feature Type and the Pre‑Build Address Feature Type). This issue may affect customers who received either Full Supply or Change-Only Update (COU) orders containing OS NGD Address feature types across data schema versions 1.0, 2.0 or 3.0 during that time. If you believe you are affected by this issue, please .

    This issue is distinct but related to a similar issue reported and resolved within February.

    06/03/2026

    Incorrect change type for addresses moving between feature types

    In a very small number of cases, when an address moves between feature types, such as moving from Pre-Build Address to Built Address, the change type given is incorrect.

    The address 'leaving' the Pre-Build Address Feature Type is correctly marked 'Moved To', but when it enters the Built Address Feature Type, it is incorrectly marked as 'New' rather than 'Moved From'.

    This issue impacts OS NGD Address feature types in both data schema versions (i.e. data schema versions 1.0 and 2.0).

    Your COU processing will still work correctly, and your data holdings will be complete, but the address will have been incorrectly marked as 'New'.

    Data Issue Name
    Data Issue Description
    Data Issue Identification Date

    Retail Hierarchy attribute values not as expected in places

    In a small number of cases for Retail Area Aggregated features (data schema version 1.0), published values are incorrect and appear to be demotions. For example, an expected Town Centre could be published with a Retail Hierarchy attribute value of Small Town Centre. We are investigating the cause of this error, and any improvements will be made available as part of the regular releases of OS Functional Areas Collection data. The Retail Hierarchy attribute is available for Retail Area Aggregated features only.

    26/03/2026

    Data Issue Name
    Data Issue Description
    Data Issue Identification Date

    Incorrect building height values for some multi-storey properties with a single storey annexe

    Some residential two-storey properties with a large adjoining single storey are returning as a single storey when created using machine learning (due to incorrect building height values), for example, two-storey houses with attached garages or large rear extensions. This impacts data schema version 4.0 onward of the Building Feature Type.

    27/03/2025

    Minor confusion between roofs of similar appearance

    When capturing roof type data through our aerial capture program, there can be some confusion between buildings with glass roofs or an evacuated tube collector and those with solar panels present. As a result, buildings with glass roofs may be incorrectly attributed with solar panel presence.

    This is something we aim to address in future iterations of roof type data for the Building Feature Type. This impacts data schema version 4.0 onward of the Building Feature Type.

    27/03/2025

    Inconsistent caravan roof shape

    Large static caravans will have inconsistent roof shapes due to the shallow-pitched nature of their roofs, making it difficult to ascertain true shape.

    This impacts data schema version 4.0 onward of the Building Feature Type.

    27/03/2025

    Data Issue Name
    Data Issue Description
    Data Issue Identification Date

    Poor linking between Crowd Sourced Name Point features and other OS NGD features

    We are actively improving the linking between Crowd Sourced Name Point features (data schema version 1.0) and other OS NGD features, so some updates are expected; these updates will be delivered through standard change-only updates (COUs).

    27/03/2025

    Data Issue Name
    Data Issue Description
    Data Issue Identification Date

    Nullified Access Purpose attribute for certain Site Access Location features

    Some key public sites have refused access to surveyors and so will have their Access Purpose attribute nullified for the Site Access Location feature (data schema version 2.0 only as this attribute is not available for data schema version 1.0).

    27/03/2025

    No current known data issues to note for this theme.

    Data Issue Name
    Data Issue Description
    Data Issue Identification Date

    Completeness for bridge interactions

    On rare occasions where Network Over and Network Under attribution cannot be identified (i.e. disused bridges or viaducts over dry valleys) for Compound Structure Feature Type features (data schema version 2.0 onward), the attributes will not be populated (i.e. will be ‘null’).

    25/09/2024

    Mersey Railway Tunnels and Westferry Circus Tunnel missing

    The Mersey Railway Tunnels and Westferry Circus Tunnel are not included in data schema v2.0 onward of the Compound Structure Feature Type.

    25/09/2024

    Overlapping of stacked bridges

    Where bridges cross one other, it can be difficult to identify the correct networks running over and / or under each bridge. This impacts Compound Structure Feature Type features (data schema version 2.0 onward).

    Data Issue Name
    Data Issue Description
    Data Issue Identification Date

    Incorrect modal or minimum width values for Cycle Lane features

    There are a small number of Cycle Lane features (data schema version 1.0) which have a modal and minimum width values of 0m (Cycle Lane Info Modal Width M, and Cycle Lane Info Minimum Width M attributes).

    25/09/2025

    Incorrect evidence dates for Cycle Lane features

    There are a small number of Cycle Lane features (data schema version 1.0) with an incorrect Geometry Evidence Date attribute date value of 01-01-2000.

    25/09/2025

    Rail Network referencing errors

    There are a small number of Railway Link features (data schema version 1.0) which are not connected to a Railway Node feature (data schema version 1.0) at one or both ends, and a small number of Railway Node features (data schema version 1.0) that are not coincident with the start or end of the Railway Link features (data schema version 1.0) that reference them. This issue is currently being investigated.

    Data Issue Name
    Data Issue Description
    Data Issue Identification Date

    Continuous tidelines break errors

    A few Tidal Boundary Continuous High and Continuous Low features (data schema version 1.0) contain breaks, dead ends or disconnected sections due to an issue in the product generation process. This can result in tidal boundaries not being represented as fully continuous in some locations.

    02/03/2026

    Unexpected Width Derivation Method for Water Links

    There are 158 Water Link features (data schema version 2.0) that have been assigned a Width Average attribute value based on a 'Default Value For Geographic Region', when they are expected to receive a Width Average attribute value that is derived either from 'Modelled From Network' or 'Calculated from Polygon'.

    30/10/2025

    Invalid geometries in Waterbody Catchment and River Basin District Catchment features

    Very small number of features not being given the correct 'End of Life' change type

    Any live interruptions to the availability of OS NGD API – Features and OS NGD API – Tiles will be documented on the Service Availability Dashboard on the OS Data Hub.

    Generic OS NGD current known data issues

    Resolved Data Issues
    'Contact us' section of the OS website

    There are 319 features (out of 600+ million) which reside within the 'features' collections (i.e. any OS NGD collection which has a name of 'OS NGD XXX Features', for example, OS Transport Features) that have not been given the correct 'End of Life' change type. This means that these features still reside within the supply but should be deleted.

    OS NGD Address Theme current known data issues

    OS NGD Administrative and Statistical Units Theme current known data issues

    OS NGD Buildings Theme current known data issues

    OS Geographical Names Theme current known data issues

    OS NGD Land Theme current known data issues

    OS NGD Land Use Theme current known data issues

    OS NGD Structures Theme current known data issues

    OS NGD Transport Theme current known data issues

    OS NGD Water Theme current known data issues

    Data packages linked to an OS NGD recipe

    Data packages linked to an OS NGD recipe

    Screenshot of OS Data Hub, showing an example of the Data packages list screen.
    Screenshot showing an example of the OS NGD Recipe prefix on a recipe name. The OS NGD Recipe prefix on the recipe name is highlighted in yellow.
    Screenshot of OS Data Hub, showing an example of the Data packages list screen.
    Screenshot showing an example of the OS NGD Recipe prefix on a recipe name. The OS NGD Recipe prefix on the recipe name is highlighted in yellow.
    Screenshot showing an example of a Data package summary screen in the OS Data Hub, with the Package options dropdown open.

    Historic County

    The Historic counties data shows the county boundaries based on records and mapping circa 1888, using the following acts as primary sources:

    • Local Government (England and Wales) Act 1888

    • Local Government (Scotland) Act 1889

    • Sheriffs Act 1887

    The dataset shows the boundaries in place in 1888 in England and Wales, and those established a year later in Scotland. The alignments of the counties for England and Wales are derived from mapping sourced from the National Archives which dates from 1890. The most recent available county alignment mapping for Scotland is from 1940.

    Historic counties are not updated; therefore, the lifecycle dates will not change.

    The following table provides details about this feature type’s data schema versions, including the reasons behind the changes and the related launch date when each version went live.

    Version ↓
    Launch Date
    Latest Date
    Change

    Please see for in-depth information about data schema versioning in the OS NGD.

    Temporal filtering allows you to order a one-off snapshot of data from the OS NGD from a current or past date. It is an optional step when you create a new data package in OS Select+Build (the OS NGD download service).

    The earliest and latest dates on which you can request a one-off snapshot of a date in the past for this feature type's data schema versions are indicated in the above. Please note that any data temporally filtered earlier than the specified launch date indicated in the table for the data schema versions may contain data inconsistencies.

    More information about temporal filtering on OS NGD feature types is available from the .

    The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

    Primary identifier for the feature. The OSID is a Globally Unique Identifier (GUID) and requires no centralised authority to ensure uniqueness. Note that the same OSID can occur in more than one feature type when a single feature is represented multiple times in the OS NGD.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 36

    • OS Select+Build Filterable: No

    Date when the version was last updated.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The date this version of the feature became the latest version.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The date this version of the feature was superseded by an update or ceased to exist.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The type of change that generated a new version of the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    Geometry for the feature.

    • Data Types: Geometry (GPKG), WKT (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The measured area of the geometry in square metres.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 18

    • Scale: 6

    The OS NGD theme to which this feature belongs.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 40

    A single descriptive value intended for a quick understanding of what the feature represents.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    Name assigned to identify the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 254

    • OS Select+Build Filterable: Yes

    The language of name1, provided as a 3-digit ISO 639-2 code ('eng, 'cym', 'gla').

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    The alternative language name assigned to identify the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 254

    • OS Select+Build Filterable: Yes

    The language of name2, provided as a 3-digit ISO 639-2 code ('eng, 'cym', 'gla').

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    A single description value for boundary type.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    The inland area of the feature in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    The non-inland area in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    The total area in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    Historic European Region

    The exit of the United Kingdom from the European Union on 01 January 2021 resulted in the repeal of the European Regions as active electoral areas. For the purposes of Boundary Review, the original European Regions in England have been retained as nine English Regions, preserved as of 01 April 2021.

    Historic European Regions are not updated; therefore, the lifecycle dates will not change.

    Data schema versioning

    The following table provides details about this feature type’s data schema versions, including the reasons behind the changes and the related launch date when each version went live.

    Data schema version table

    Version ↓
    Launch Date
    Latest Date
    Change

    Please see for in-depth information about data schema versioning in the OS NGD.

    Temporal filtering allows you to order a one-off snapshot of data from the OS NGD from a current or past date. It is an optional step when you create a new data package in OS Select+Build (the OS NGD download service).

    The earliest and latest dates on which you can request a one-off snapshot of a date in the past for this feature type's data schema versions are indicated in the above. Please note that any data temporally filtered earlier than the specified launch date indicated in the table for the data schema versions may contain data inconsistencies.

    More information about temporal filtering on OS NGD feature types is available from the .

    The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

    Primary identifier for the feature. The OSID is a Globally Unique Identifier (GUID) and requires no centralised authority to ensure uniqueness. Note that the same OSID can occur in more than one feature type when a single feature is represented multiple times in the OS NGD.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 36

    • OS Select+Build Filterable: No

    Date when the version was last updated.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The date this version of the feature became the latest version.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The date this version of the feature was superseded by an update or ceased to exist.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The type of change that generated a new version of the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    Geometry for the feature.

    • Data Types: Geometry (GPKG), WKT (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The measured area of the geometry in square metres.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 18

    • Scale: 6

    The OS NGD theme to which this feature belongs.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 40

    A single descriptive value intended for a quick understanding of what the feature represents.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    Name assigned to identify the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 254

    • OS Select+Build Filterable: Yes

    The language of name1, provided as a 3-digit ISO 639-2 code ('eng, 'cym', 'gla').

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    The alternative language name assigned to identify the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 254

    • OS Select+Build Filterable: Yes

    The language of name2, provided as a 3-digit ISO 639-2 code ('eng, 'cym', 'gla').

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    A single description value for boundary type.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    The inland area of the feature in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    The non-inland area in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    The total area in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    Region

    Maintained set of regions to continue supporting statistical analysis. Currently there are no maintained regions for Scotland and Wales.

    Temporal filtering

    The earliest date on which you can request a one-off snapshot of a date in the past for data in this feature type is 29 September 2022.

    Any data temporally filtered earlier than the specified earliest date noted above for the data schema version may contain data inconsistencies.

    Feature type attributes

    The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

    Comma-separated values (CSV) file format is universally supported for easy ingestion into all major database products. Before loading OS NGD data contained in CSV files into a database, it is necessary to create relevant tables. Data definition language (DDL) statements for PostgreSQL, SQL Server and Oracle can be accessed in our .

    For instructions on loading CSV files, see the guide.

    osid

    Primary identifier for the feature. The OSID is a Globally Unique Identifier (GUID) and requires no centralised authority to ensure uniqueness. Note that the same OSID can occur in more than one feature type when a single feature is represented multiple times in the OS NGD.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 36

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Topographic identifier (TOID) of the feature, as published in the OS MasterMap suite of products.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 20

    • OS Select+Build Filterable: Yes

    Date when the version was last updated.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The date this version of the feature became the latest version.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The date this version of the feature was superseded by an update or ceased to exist.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The type of change that generated a new version of the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    Geometry for the feature.

    • Data Types: Geometry (GPKG), WKT (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The measured area of the geometry in square metres.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 18

    • Scale: 6

    The OS NGD theme to which this feature belongs.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 40

    A single descriptive value intended for a quick understanding of what the feature represents.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    Name assigned to identify the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 254

    • OS Select+Build Filterable: Yes

    The language of name1, provided as a 3-digit ISO 639-2 code ('eng, 'cym', 'gla').

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    The alternative language name assigned to identify the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 254

    • OS Select+Build Filterable: Yes

    The language of name2, provided as a 3-digit ISO 639-2 code ('eng, 'cym', 'gla').

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    Set to the census / Government Statistical Service (GSS) Code for the boundary, for example, E10000014.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 10

    • OS Select+Build Filterable: Yes

    A single description value for boundary type.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    The inland area of the feature in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    The non-inland area in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    The total area in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    File formats and naming

    OS NGD data is available in four easy-to-use formats: GeoPackage, CSV (comma-separated values), GeoJSON and vector tiles. The download service of OS Select+Build supports GeoPackage and CSV. OS NGD API – Features supports GeoJSON. OS NGD API – Tiles supports vector tiles.

    CSV files are delimited text files which use commas to separate each attribute from the next. CSV is one of the file formats available via OS Select+Build. A single record is commonly provided per line, with a new line being started for each new record.

    Geometry attribution will be provided as Well-Known Text (WKT).

    CSV offers the following benefits:

    • The single file is familiar to many customers and well used across GIS and data science tools.

    Country

    The countries of Great Britain.

    The following table provides details about this feature type’s data schema versions, including the reasons behind the changes and the related launch date when each version went live.

    Version ↓
    Launch Date
    Latest Date
    Change

    Upper Tier Local Authority

    This feature type has been created to provide greater alignment between OS data and Office for National Statistics (ONS) data and to support a wider range of analysis. Welsh and Scottish Unitary Authorities will have alternative name and language values.

    The earliest date on which you can request a one-off snapshot of a date in the past for data in this feature type is 29 September 2022.

    Any data temporally filtered earlier than the specified earliest date noted above for the data schema version may contain data inconsistencies.

    The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

    Primary identifier for the feature. The OSID is a Globally Unique Identifier (GUID) and requires no centralised authority to ensure uniqueness. Note that the same OSID can occur in more than one feature type when a single feature is represented multiple times in the OS NGD.

    • Data Types: String (GPKG), String (CSV)

    OS Land Features
  • OS Land Use Features

  • OS Structure Features

  • OS Transport Features

  • OS Water Features

  • Any daily Change-Only Update (COU) files for the other OS NGD collections will be unaffected during the maintenance period.

    Customers will continue to be able to access all daily COU orders during the maintenance period and any new orders. During the maintenance period, any COU files for the above affected OS NGD collections will continue to be delivered and will be smaller than normal or empty. At the end of the maintenance period, all the surveyed changes for the affected OS NGD collections will be made available, and any daily COU files are likely to be larger than normal.

    Any customers who receive monthly COU files will not be affected.

    OS NGD Address Theme

    The fix for the known data issue relating to the description of Parish and Community Government Statistical Services (GSS) codes as Ward GSS codes and vice versa will be rolled out to 4 million features (UPRNs) a day alongside the usual daily updates starting from 17 May 2024 until 27 May 2024.

    This will result in larger daily Change-Only Update (COU) files. On 01 June 2024, the OS NGD Address Theme monthly COU file will be larger than a Full Supply file as all features will have a delete record and an update record.

    ⚙️ Data and Service Status

    Find out about OS NGD planned maintenance, any live service disruption, current data issues and resolved data issues.

    ✨ OS NGD Key Benefits to Customers

    Find out what the key benefits of the OS NGD are.

    🗺️ OS NGD Sample Data

    Download OS NGD sample data or visualise it online.

    📖 OS NGD Fundamentals

    OS NGD Fundamentals covers the core elements of OS NGD design, including available data formats and file naming, data schema versioning, access methods, data ordering and currency, attribute information for feature types, unique identifiers and coordinate reference systems.

    ▶️ Getting Started

    Our getting started guides will help you access, use and style OS NGD data. You'll also find in-depth information on OS NGD design, and webinars, tutorials and case studies.

    ❓ FAQs

    Frequently asked questions on OS NGD data and the download service of OS Select+Build.

    🗃️ Data Structure

    Learn about the OS NGD data structure and the data available for each theme, collection and feature type.

    📝 Code Lists

    Access all of the code lists for the OS NGD.

    🆕 What's New?

    🔧 OS NGD Improvements

    📜 Change Log

    OS NGD Improvements page
    Building Feature Type
    OS NGD Improvements page
    OS NGD Improvements page
    'What's New' page
    'What's New?' page

    Data Schema Version: 1.1

    OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • Geometry Type: MultiPolygon

    OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • Data Schema Version: 1.1

    OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • Data Schema Version: 1.1

    OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.1

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • 1.1

    28 July 2025

    Ongoing

    Minor version increment that removes the query and download filters from the Description attribute as this attribute supports only a single value.

    1.0

    29 September 2022

    27 July 2025

    Initial launch of the Historic County Feature Type.

    Data schema versioning

    Data schema version table

    Temporal filtering

    Feature type attributes

    Loading OS NGD CSV files into databases

    Comma-separated values (CSV) file format is universally supported for easy ingestion into all major database products. Before loading OS NGD data contained in CSV files into a database, it is necessary to create relevant tables. Data definition language (DDL) statements for PostgreSQL, SQL Server and Oracle can be accessed in our OS NGD Resources GitHub repository.

    For instructions on loading CSV files, see the Getting Started with CSV guide.

    osid

    versiondate

    versionavailablefromdate

    versionavailabletodate

    changetype

    geometry

    geometry_area

    theme

    description

    name1_text

    name1_language

    name2_text

    name2_language

    boundarytype

    landareahectares

    tidalareahectares

    totalareahectares

    Data schema versioning
    Data schema version table
    Getting started with temporal filtering guide
    changetypevalue
    themevalue
    historiccountydescriptionvalue
    languagevalue
    languagevalue
    boundarytypevalue

    Data Schema Version: 1.1

    OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • Geometry Type: MultiPolygon

    OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • Data Schema Version: 1.1

    OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • Data Schema Version: 1.1

    OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.1

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • 1.1

    28 July 2025

    Ongoing

    Minor version increment that removes the query and download filters from the Description attribute as this attribute supports only a single value.

    1.0

    29 September 2022

    27 July 2025

    Initial launch of the Historic European Region Feature Type.

    Temporal filtering

    Feature type attributes

    Loading OS NGD CSV files into databases

    Comma-separated values (CSV) file format is universally supported for easy ingestion into all major database products. Before loading OS NGD data contained in CSV files into a database, it is necessary to create relevant tables. Data definition language (DDL) statements for PostgreSQL, SQL Server and Oracle can be accessed in our OS NGD Resources GitHub repository.

    For instructions on loading CSV files, see the Getting Started with CSV guide.

    osid

    versiondate

    versionavailablefromdate

    versionavailabletodate

    changetype

    geometry

    geometry_area

    theme

    description

    name1_text

    name1_language

    name2_text

    name2_language

    boundarytype

    landareahectares

    tidalareahectares

    totalareahectares

    Data schema versioning
    Data schema version table
    Getting started with temporal filtering guide
    changetypevalue
    themevalue
    historiceuropeanregiondescriptionvalue
    languagevalue
    languagevalue
    boundarytypevalue

    add-gb-royalmailaddress

    We will contact impacted customers about this issue.

    If you believe you are affected by this issue, please contact us for assistance.

    May 2023

    Additional in-scope buildings included in the Number of Floors data

    Some notable non-residential and non-office buildings that meet the scope will be included (for example, several cathedrals and arenas) and will have values for the Number of Floors attributes.

    This impacts data schema versions 3.0 and 4.0 onward of the Building Feature Type.

    25/09/2024

    Some in-scope residential buildings are excluded from the Number of Floors data

    Some in-scope residential buildings have no values for the Number of Floors attributes (for example, new builds, and buildings failing height validation rules).

    This impacts data schema versions 3.0 and 4.0 onward of the Building Feature Type.

    25/09/2024

    Some apartment block buildings are excluded from the Number of Floors data

    Apartment blocks that have their address geometry situated in the stairwell of the building and have their building geometry segregated due to the Land Use Site Feature Type will not get values for the Number of Floors attributes.

    This impacts data schema versions 3.0 and 4.0 onward of the Building Feature Type.

    25/09/2024

    25/09/2024

    Overlapping Field Boundary

    features exist

    Approximately 20 000 Field Boundary Feature Type features (data schema version 1.0) are overlapping. This issue is currently being investigated.

    27/03/2024

    01/03/2025

    Mismatches between Road Link Directionality attribution and Average Speed attribution

    There are a small number of Road Link features (data schema versions 1.0, 2.0, 3.0, 4.0 and 5.0) where the Directionality attribution of the Road Link and the attribution describing average speeds are not in sympathy (for example, the Road Link is in Both Directions, but average speed attribution is only available for one of the directions). Some instances of this are a result of the Road Network being updated monthly and speed information being updated six-monthly; however, the remaining instances where this does not apply are being investigated.

    01/04/2024

    Feature Count discrepancies compared to OS MasterMap Highways Network

    A small number of features in the following feature types are missing when compared to the comparable tables in OS MasterMap Highways Network, or have superfluous features in NGD Transport that are not present in OS MasterMap Highways Network: Connecting Link (data schema version 1.0), Connecting Node (data schema version 1.0), Path (data schema version 1.0), Path Link (data schema versions 1.0, 2.0, and 3.0), Restriction (data schema version 1.0), Road (data schema version 1.0, Routing Hazard (data schema version 1.0), Special Designation (data schema version 1.0), and Street (data schema version 1.0). This issue is currently being investigated.

    14/08/2023

    Some polygons for Waterbody Catchment and River Basin District Catchment features (data schema version 1.0) have invalid geometries in the form of self-intersections, holes, and gaps. Instances of self-intersection are primarily due to the gridded digital terrain model (DTM) used to generate the catchment data provided by the third-party data from authoritative bodies.

    28/03/2023

    Incorrect representation of a Waterbody Catchment name

    The Barlings Eau Upper catchment name is incorrectly displayed. This is as per the third-party data from the authoritative bodies.

    28/03/2023

    Non-unique Waterbody Catchment IDs

    Two instances occur where the Waterbody Catchment ID is not unique for Waterbody Catchment features (data schema version 1.0): GB109056040082 and GB104027063230. This is as per the third-party data from the authoritative bodies.

    28/03/2023

    Certain Waterbody Catchment features do not nest exactly within a River Basin District Catchment

    A total of 14 instances occur where Waterbody Catchment features (data schema version 1.0) do not nest exactly within their associated River Basin District Catchment features (data schema version 1.0). This is as per the third-party data from the authoritative bodies.

    28/03/2023

    contact us for assistance
    Retail Hierarchy attribute

    Data Schema Version: 1.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Geometry Type: MultiPolygon

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0

  • Data Schema Version: 1.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Data Schema Version: 1.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Data Schema Version: 1.0

    OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • toid

    versiondate

    versionavailablefromdate

    versionavailabletodate

    changetype

    geometry

    geometry_area

    theme

    description

    name1_text

    name1_language

    name2_text

    name2_language

    gsscode

    boundarytype

    landareahectares

    tidalareahectares

    totalareahectares

    Loading OS NGD CSV files into databases

    changetypevalue
    themevalue
    regiondescriptionvalue
    languagevalue
    languagevalue
    boundarytypevalue
    OS NGD Resources GitHub repository
    Getting Started with CSV
    YouTube video showing how to create a recipe using OS Select+Build, add filters to the recipe, then create a data package to receive your OS NGD data.
    Screenshot showing the tree view in the secondary navigation menu that opens when you create a recipe in OS Select+Build in the OS Data Hub. Three of the four feature types needed for the OS NGD greenspace recommended recipe are shown to have been selected in this screenshot: Rail, Road Track Or Path, and Water; Land has also been selected, but isn't visible in the screenshot.
    Screenshot of the OS Select+Build Recipe Edit recipe screen with the Advanced Filter Options panel showing, where you can add a filter to a recipe. The filter options selected for the Land Feature Type are shown in this screenshot.
    Screenshot showing the tree view in the secondary navigation menu that opens when you create a recipe in OS Select+Build in the OS Data Hub. Three of the five feature types needed for the safer routes to schools recipe are shown to have been selected in this screenshot: Connecting Link, Path Link and Road Link; Average And Indicative Speed, and Built Address have also been selected, but aren't visible in the screenshot.
    Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build. The first rule of the filter options needed for the Built Address Feature Type is shown in this screenshot.
    Screenshot of creating a nested filter in the Advanced Filter Options panel in OS Select+Build. The two rules filter options selected for the Built Address Feature Type are shown in this screenshot.
    Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build. The first rule of the filter options needed for the Road Link Feature Type is shown in this screenshot.
    Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build. The two rules filter options selected for the Built Address Feature Type are shown in this screenshot.

    The Postal Address Related Component is still provided against the older (maintenance) data schema versions 1.0 and 2.0 of the Built Address, Historic Address, Non-Addressable Object and Pre-Build Address Feature Types in the OS GB Address and OS Islands Address Collections. These data schema versions are available for customers to use, but they are now older and in maintenance mode. (Data schema version 3.0 is the latest and recommended data schema version to use for these feature types.)

    Postal Address Related Component

    Other Alias
    Postal Address Related Component
    Tree diagram showing the data structure of the OS NGD Address Theme. It lists the theme name, collection names, feature type names, and related component names. It's applicable to is applicable to the older (maintenance) data schema versions (1.0 and 1.1) of Royal Mail Address, to the latest data schema version (1.0) of Street Address, and to the latest data schema version (3.0) of Built Address, Historic Address, Non-Addressable Object and Pre-Build Address.
    Tree diagram showing the superseded data structure of the OS NGD Address Theme. It lists the theme name, collection names, feature type names, and related component names. It's applicable to the older (maintenance) data schema versions of four of the address feature types (i.e. data schema versions 1.0 and 2.0 of Built Address, Historic Address, Non-Addressable Object and Pre-Build Address) and to the latest data schema version (1.0) of Street Address.

    In the third rule, select buildStatus from the first drop-down. Leave the operator in the second drop-down as: = (i.e. the equal sign), then select Built Complete from the third drop-down.

  • Before continuing to the second group, select whether you would like the three rules within the first group to have an And or an Or condition. In this case, you should select And from the And / Or selector.

  • In the third rule, select tertiaryClassificationDescription from the first drop-down, set the operator in the second drop-down as = (i.e. the equal sign), then select Holiday Let / Accommodation / Short-Term Let Other Than CH01 from the third drop-down.
  • In the fourth rule, select buildStatus from the first drop-down. Leave the operator in the second drop-down as: = (i.e. the equal sign), then select Built Complete from the third drop-down.

  • Before continuing, select whether you would like the four rules within the second group to have an And or an Or condition. In this case, you should select And from the And / Or selector.

  • Before continuing, select whether you would like the two rules within the group to have an And or an Or condition. In this case, you should select Or from the And / Or selector.

    📖 Getting started with recipes guides

    🎯 Getting started with attribute filtering guide

    📚 Getting started with data packages guide

    🏢 Guide for using ArcGIS Pro to create maps to identify higher-risk buildings

    🗺️ Guide for using QGIS to create maps to identify higher-risk buildings

    Why are filters needed in this recipe?

    Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build. Two groups have been added to the filter with an Or condition between them.
    Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build. Two groups have been added to the filter with an Or condition between them.
    Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build. The first group of the filter options needed for the Built Address Feature Type is shown in this screenshot.
    Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build. The first group of the filter options needed for the Built Address Feature Type is shown in this screenshot.
    Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build showing all of the group and rule filter options selected for the Built Address Feature Type.
    Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build showing all of the group and rule filter options selected for the Built Address Feature Type.
    Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build. The first rule of the filter options needed for the Building Feature Type is shown in this screenshot.
    Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build. The first rule of the filter options needed for the Building Feature Type is shown in this screenshot.
    Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build. The first rule and the group filter options needed for the Building Feature Type are shown in this screenshot.
    Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build. The first rule and the group filter options needed for the Building Feature Type are shown in this screenshot.
    Screenshot of creating a nested filter in the Advanced Filter Options panel in OS Select+Build. The complete filter options selected for the Building Feature Type are shown in this screenshot.
    Screenshot of creating a nested filter in the Advanced Filter Options panel in OS Select+Build. The complete filter options selected for the Building Feature Type are shown in this screenshot.
    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
    Screenshot showing the tree view in the secondary navigation menu that opens when you create a recipe in OS Select+Build in the OS Data Hub. Both of the feature types needed for the identifying higher-risk buildings recipe are shown to have been selected in this screenshot: Built Address and Building.
    Screenshot showing the tree view in the secondary navigation menu that opens when you create a recipe in OS Select+Build in the OS Data Hub. The Building Feature Type has been selected in this screenshot and the Choose Schema Version drop-down menu is visible in the right-hand-side panel, which lets you select the data schema version you want to use for the feature type.
    Screenshot of the theme selection tree in OS Select+Build. The Address, GB Address and Built Address boxes have been selected. A filter option is visible to the right of the Built Address name.
    Screenshot of the theme selection tree in OS Select+Build. The Address, GB Address, Built Address, Buildings, Building Features, and Building boxes have been selected. A filter option is visible to the right of the Built Address and Building names.
    Screenshot of the OS Select+Build Recipe details screen showing a summary of the identifying higher-risk buildings recipe, including selected feature types and their data schema versions, plus all filters applied.
    Filter icon in OS Select+Build
    Filter icon in OS Select+Build

    Nullable: false

  • Max Length: 36

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Topographic identifier (TOID) of the feature, as published in the OS MasterMap suite of products.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 20

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0

    Date when the version was last updated.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The date this version of the feature became the latest version.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The date this version of the feature was superseded by an update or ceased to exist.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The type of change that generated a new version of the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: changetypevalue

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Geometry for the feature.

    • Data Types: Geometry (GPKG), WKT (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    • Geometry Type: MultiPolygon

    The measured area of the geometry in square metres.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 18

    • Scale: 6

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The OS NGD theme to which this feature belongs.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: themevalue

    • Max Length: 40

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    A single descriptive value intended for a quick understanding of what the feature represents.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: uppertierlocalauthoritydescriptionvalue

    • Max Length: 50

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0

    Name assigned to identify the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 254

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0

    The language of name1, provided as a 3-digit ISO 639-2 code ('eng, 'cym', 'gla').

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: languagevalue

    • Max Length: 3

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The alternative language name assigned to identify the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 254

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0

    The language of name2, provided as a 3-digit ISO 639-2 code ('eng, 'cym', 'gla').

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: languagevalue

    • Max Length: 3

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Set to the census / Government Statistical Service (GSS) Code for the boundary, for example, E10000014.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 10

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0

    A single description value for boundary type.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: boundarytypevalue

    • Max Length: 50

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0

    The inland area of the feature in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The non-inland area in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The total area in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    A boolean value indicating whether the feature is part of a Borough or not

    • Data Types: Integer (GPKG), String (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Temporal filtering

    Feature type attributes

    Loading OS NGD CSV files into databases

    Comma-separated values (CSV) file format is universally supported for easy ingestion into all major database products. Before loading OS NGD data contained in CSV files into a database, it is necessary to create relevant tables. Data definition language (DDL) statements for PostgreSQL, SQL Server and Oracle can be accessed in our OS NGD Resources GitHub repository.

    For instructions on loading CSV files, see the Getting Started with CSV guide.

    osid

    toid

    versiondate

    versionavailablefromdate

    versionavailabletodate

    changetype

    geometry

    geometry_area

    theme

    description

    name1_text

    name1_language

    name2_text

    name2_language

    gsscode

    boundarytype

    landareahectares

    tidalareahectares

    totalareahectares

    isborough

    YouTube video showing how to create a recipe using OS Select+Build, add filters to the recipe, then create a data package to receive your OS NGD data. (Creating data packages is discussed around seven minutes into the video.)
    Click Apply filter.
    nested filter
    Screenshot of the OS Select+Build Recipe Edit recipe screen with the Advanced Filter Options panel showing.
    Screenshot of the OS Select+Build Recipe Edit recipe screen with the Advanced Filter Options panel showing, where you can add a filter to a recipe.
    OS Data Hub screenshot, showing part of the theme selection tree in OS Select+Build. A filter icon is visible against the Building Part Feature Type. The Building Part Feature Type has been selected.
    Screenshot showing a filter icon against the selected feature type in the theme selection tree in OS Select+Build
    OS Data Hub screenshot, showing the Advanced filter options panel in OS Select+Build. In the rule, OSLandUseTierA is selected in the first drop-down, the equal sign is selected in the second drop-down, and Education is selected in the third drop-down.
    Screenshot of adding a rule in the Advanced Filter Options panel in OS Select+Build.
    OS Data Hub screenshot, showing the Advanced filter options panel in OS Select+Build. Two rules have been created in the first group, and the +Add group button has been clicked and the application has drawn an extra box.
    Screenshot of creating a nested filter in the Advanced Filter Options panel in OS Select+Build.
    OS Data Hub screenshot, showing an example of a nested filter with an And condition and an Or condition applied in the Advanced filter options panel in OS Select+Build.
    Screenshot of creating a nested filter with And and Or conditions in the Advanced Filter Options panel in OS Select+Build.
    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
    Screenshot of the OS Select+Build Recipe details screen with the Recipe actions dropdown open, showing where you can share, edit or delete a recipe.
    Screenshot of the OS Select+Build Recipe Edit recipe screen with the Advanced Filter Options panel showing. There is one filter applied to the Building Part Feature Type.
    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
    OS Data Hub screenshot, showing the Advanced filter options panel in OS Select+Build. In the rule, OSLandUseTierA is selected in the first drop-down.
    OS Data Hub screenshot, showing the Advanced filter options panel in OS Select+Build. Two rules have been created in the first group.
    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
    Screenshot of the OS Data Hub, showing the OS Select+Build recipe details screen. This screen shows in-depth information about an example recipe, including the recipe name, a description of the recipe, the filters used, the creation date, its author, and the OS NGD themes, collections and feature types present within it.
    Filter icon in OS Select+Build
    Filter icon in OS Select+Build
    Filter icon in OS Select+Build
    Filter icon in OS Select+Build
    Filter icon in OS Select+Build
    It is plug and play with most databases.
  • The ability to quickly load large datasets using COPY method rather than INSERT.

  • The following table shows how different attribute types in the OS NGD are delivered when you choose to receive a CSV format. This includes whether to expect quotes, and how NULL values are treated.

    Attribute type
    Quotes (Y/N)
    If NULL
    Example

    Integer

    N

    "

    123

    Real

    GeoPackage (GPKG) is an open standard data format as defined by the Open Geospatial Consortium (OGC). It is one of the file formats available via OS Select+Build. GeoPackage 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.

    • The file size limit is very large at 140TB, so lots of data can be easily accommodated (please note that a file size limit may be imposed by the file system to which the file is written).

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

    GeoJSON is an IETF standard designed to represent simple geographical features and their non-spatial attributes. It is used for encoding geographic data structures using JavaScript Object Notation (JSON). GeoJSON is used by OS NGD API – Features.

    More information about the GeoJSON IETF standard can be found here.

    Supported geometry types:

    • Point

    • LineString

    • Polygon

    • Multipart geometries: MultiPoints, MultiLineString, or MultiPolygon features

    Vector tiles are clipped tiles, or grid squares, composed of layers of vector features which are optimised for caching, scaling and producing map imagery quickly. They serve in a similar way to raster tiles but have the added functionality of being customisable by users. A client application requests tiles based on a zoom level and extent, and the server responds with binary data representing the vector tiles containing the layers to be visualised on that map.

    OS NGD API – Tiles serves vector tiles as raw information which is presented using compressed packets of geographic data using the Protocolbuffer Binary Format (.pbf).

    Vector tiles offer the following benefits:

    • User customisation and styling functionality – customise your map with full and dynamic design control.

    • Small file size – lightweight tiles that are efficient and quick to render in your client application.

    • Pixel perfect maps – high-resolution, beautiful mapping for all devices (web and mobile devices).

    • Snapping ability – due to the data being vector, data can be snapped to and traced.

    • Smooth zooming and scaling effect – a seamless user experience when zooming in and out of maps.

    • Advanced features – vector tiles contain geographic data (not just images) which can be interrogated and analysed.

    When you place an order for OS NGD data via OS Select+Build, the following file naming convention will be applied to the data you receive:

    themeshortcode_collectionshortcode_featuretype

    In order to keep file names manageable and not overly long, shortened file names ('short codes') have been used for both the theme and collection. Using short codes in our naming convention also ensures we have consistency in naming between OS Select+Build and the OS NGD APIs.

    An example of how these short codes are used is below, with the example showing a file name which would be created for an order of the Built Address Feature Type within the OS GB Address Collection of the OS NGD Address Theme:

    add_gb_builtaddress

    A full list of the short codes we use in OS Select+Build and the OS NGD APIs is detailed in the following table:

    Theme
    Theme Short Code
    Collection
    Collection Short Code

    OS NGD Address

    add

    OS GB Address

    gb

    Available formats for OS NGD data

    CSV overview

    If you want a file format that allows you to quickly load OS NGD data into a database / central data repository and the option to receive COU (Change-Only Update) supplies, then CSV is your best choice.

    Please be aware that CSV files are designed to be opened in a database or GI system, and opening them in other software applications could corrupt the data. In particular, Excel has a row limit which might be exceeded by some of our CSV files containing OS NGD data, depending on the order you placed and its size. We recommend that you load CSV files containing OS NGD data directly into a database or GI system, rather than trying to open these files in Excel.

    CSV structure

    GeoPackage overview

    If you want a file format that allows you to quickly load full supplies of OS NGD data into a GIS, then GeoPackage is your best option.

    GeoJSON overview

    Vector tiles overview

    File naming

    1.0

    29 September 2022

    27 July 2025

    Initial launch of the Country Feature Type.

    Please see Data schema versioning for in-depth information about data schema versioning in the OS NGD.

    Temporal filtering allows you to order a one-off snapshot of data from the OS NGD from a current or past date. It is an optional step when you create a new data package in OS Select+Build (the OS NGD download service).

    The earliest and latest dates on which you can request a one-off snapshot of a date in the past for this feature type's data schema versions are indicated in the Data schema version table above. Please note that any data temporally filtered earlier than the specified launch date indicated in the table for the data schema versions may contain data inconsistencies.

    More information about temporal filtering on OS NGD feature types is available from the Getting started with temporal filtering guide.

    The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

    Primary identifier for the feature. The OSID is a Globally Unique Identifier (GUID) and requires no centralised authority to ensure uniqueness. Note that the same OSID can occur in more than one feature type when a single feature is represented multiple times in the OS NGD.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 36

    • OS Select+Build Filterable:

    • Data Schema Version: 1.1

    Topographic identifier (TOID) of the feature, as published in the OS MasterMap suite of products.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 20

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.1

    Date when the version was last updated.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The date this version of the feature became the latest version.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The date this version of the feature was superseded by an update or ceased to exist.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The type of change that generated a new version of the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: changetypevalue

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    Geometry for the feature.

    • Data Types: Geometry (GPKG), WKT (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    • Geometry Type: MultiPolygon

    The measured area of the geometry in square metres.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 18

    • Scale: 6

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The OS NGD theme to which this feature belongs.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: themevalue

    • Max Length: 40

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    A single descriptive value intended for a quick understanding of what the feature represents.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: countrydescriptionvalue

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    Name assigned to identify the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 254

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.1

    The language of name1, provided as a 3-digit ISO 639-2 code ('eng, 'cym', 'gla').

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: languagevalue

    • Max Length: 3

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The alternative language name assigned to identify the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 254

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.1

    The language of name2, provided as a 3-digit ISO 639-2 code ('eng, 'cym', 'gla').

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: languagevalue

    • Max Length: 3

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    Set to the census / Government Statistical Service (GSS) Code for the boundary, for example, E10000014.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 10

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.1

    A single description value for boundary type.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: boundarytypevalue

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The inland area of the feature in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The non-inland area in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The total area in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    1.1

    28 July 2025

    Ongoing

    Minor version increment that removes the query and download filters from the Description attribute as this attribute supports only a single value.

    Data schema versioning

    Data schema version table

    Temporal filtering

    Feature type attributes

    Comma-separated values (CSV) file format is universally supported for easy ingestion into all major database products. Before loading OS NGD data contained in CSV files into a database, it is necessary to create relevant tables. Data definition language (DDL) statements for PostgreSQL, SQL Server and Oracle can be accessed in our .

    For instructions on loading CSV files, see the guide.

    osid

    toid

    versiondate

    versionavailablefromdate

    versionavailabletodate

    changetype

    geometry

    geometry_area

    theme

    description

    name1_text

    name1_language

    name2_text

    name2_language

    gsscode

    boundarytype

    landareahectares

    tidalareahectares

    totalareahectares

    Regional Authority

    🔃 Regional authorities, also known as strategic or combined authorities, are regional bodies formed by two or more local authorities to manage devolved powers (for example, coordinating regional transport, economic growth and strategic planning policies).

    Data schema versioning

    The following table provides details about this feature type’s data schema versions, including the reasons behind the changes and the related launch date when each version went live.

    🔃 Data schema version table

    Version ↓
    Launch Date
    Latest Date
    Change

    2.0

    01 October 2026

    Please see for in-depth information about data schema versioning in the OS NGD.

    Temporal filtering allows you to order a one-off snapshot of data from the OS NGD from a current or past date. It is an optional step when you create a new data package in OS Select+Build (the OS NGD download service).

    The earliest and latest dates on which you can request a one-off snapshot of a date in the past for this feature type's data schema versions are indicated in the Data schema version table above. Please note that any data temporally filtered earlier than the specified launch date indicated in the table for the data schema versions may contain data inconsistencies.

    More information about temporal filtering on OS NGD feature types is available from the .

    The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

    Primary identifier for the feature. The OSID is a Globally Unique Identifier (GUID) and requires no centralised authority to ensure uniqueness. Note that the same OSID can occur in more than one feature type when a single feature is represented multiple times in the OS NGD.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 36

    • OS Select+Build Filterable: No

    Topographic identifier (TOID) of the feature, as published in the OS MasterMap suite of products.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 20

    • OS Select+Build Filterable: Yes

    Date when the version was last updated.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The date this version of the feature became the latest version.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The date this version of the feature was superseded by an update or ceased to exist.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The type of change that generated a new version of the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    Geometry for the feature.

    • Data Types: Geometry (GPKG), WKT (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The measured area of the geometry in square metres.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 18

    • Scale: 6

    The OS NGD theme to which this feature belongs.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 40

    A single descriptive value intended for a quick understanding of what the feature represents.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version: 2.0

    Name assigned to identify the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 254

    • OS Select+Build Filterable: Yes

    The language of name1, provided as a 3-digit ISO 639-2 code ('eng, 'cym', 'gla').

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    The alternative language name assigned to identify the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 254

    • OS Select+Build Filterable: Yes

    The language of name2, provided as a 3-digit ISO 639-2 code ('eng, 'cym', 'gla').

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    Set to the census / Government Statistical Service (GSS) Code for the boundary, for example, E10000014.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 10

    • OS Select+Build Filterable: Yes

    A single description value for boundary type.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    The inland area of the feature in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    The non-inland area in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    The total area in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    Data ordering and currency

    Find out more about geographic filtering options, order update options, data currency information, and feature counts for certain collections.

    To get access to the OS NGD you must first log into the . The OS NGD is accessible via both the .

    There are three options within OS Select+Build (the OS NGD download service) in relation to the geographic extent of your order. These are:

    • Great Britain: Receive all data for the whole of Great Britain.

    • Customer Specified Area: Draw an area of interest (AOI) and only receive the data which intersects this area.

    Logo

    N

    "

    1.23

    Decimal

    N

    "

    1.23

    Text

    N

    "

    Some Text

    Text (including comma in string)

    Y

    "

    "Some, Text"

    Array (code list)

    Y

    "

    "item 1,item 2"

    Timestamp

    N

    "

    2022-08-17T00:00:00.000Z

    Date

    N

    "

    2022-08-31

    OS Islands Address

    isl

    OS NGD Administrative and Statistical Units

    asu

    OS Boundaries

    bdy

    OS Functional Areas

    funcarea

    OS GB Postcodes

    gbpcd

    OS NI Postcodes

    nipcd

    OS NGD Buildings

    bld

    OS Building Features

    fts

    OS NGD Geographical Names

    gnm

    OS Named Features

    fts

    OS NGD Land

    lnd

    OS Land Features

    fts

    OS NGD Land Use

    lus

    OS Land Use Features

    fts

    OS NGD Structures

    str

    OS Structure Features

    fts

    OS NGD Transport

    trn

    OS Transport Features

    fts

    OS Transport Network

    ntwk

    OS RAMI

    rami

    OS NGD Water

    wtr

    OS Water Features

    fts

    OS Water Network

    ntwk

    Data Schema Version: 1.1, 2.0

    Data Schema Version: 1.1, 2.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.0

  • Geometry Type: MultiPolygon

    OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.0

  • Max Length: 50

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.0

  • Data Schema Version: 1.1, 2.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.0

  • Data Schema Version: 1.1, 2.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.0

  • Data Schema Version: 1.1, 2.0

    OS Select+Build Filterable: Yes

  • Data Schema Version: 1.1, 2.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.0

  • Ongoing

    Major version increment that changes the geometry type of the Geometry attribute from Polygon to MultiPolygon, and adds additional values to the Regional Authority Description Value Code List to include all operative regional authorities.

    Feature type main definition updated.

    1.1

    28 July 2025

    Ongoing

    Minor version increment that removes the query and download filters from the Description attribute as this attribute supports only a single value.

    1.0

    29 September 2022

    27 July 2025

    Initial launch of the Regional Authority Feature Type.

    Temporal filtering

    Feature type attributes

    Loading OS NGD CSV files into databases

    Comma-separated values (CSV) file format is universally supported for easy ingestion into all major database products. Before loading OS NGD data contained in CSV files into a database, it is necessary to create relevant tables. Data definition language (DDL) statements for PostgreSQL, SQL Server and Oracle can be accessed in our OS NGD Resources GitHub repository.

    For instructions on loading CSV files, see the Getting Started with CSV guide.

    osid

    toid

    versiondate

    versionavailablefromdate

    versionavailabletodate

    changetype

    geometry

    geometry_area

    theme

    description

    name1_text

    name1_language

    name2_text

    name2_language

    gsscode

    boundarytype

    landareahectares

    tidalareahectares

    totalareahectares

    Data schema versioning
    Getting started with temporal filtering guide
    changetypevalue
    themevalue
    regionalauthoritydescriptionvalue
    languagevalue
    languagevalue
    boundarytypevalue

    Loading OS NGD CSV files into databases

    OS NGD Resources GitHub repository
    Getting Started with CSV
    YouTube video showing how to create a recipe using OS Select+Build, add filters to the recipe, then create a data package to receive your OS NGD data. (Attribute filtering is discussed around four minutes into the video.)

    Pre-defined Area: Select a pre-defined area, and only receive the data which intersects this area.

    When accessing the OS NGD, the following order update options will be available:

    • One Off Full Supply

    • Regular Full Supply

    • Change-Only Update (COU; after an initial Full Supply)

    • No Update

    The following frequencies will be available dependent on the type of order you place:

    • Daily Supply: This will provide you with the latest updates OS have loaded and verified for publication since the previous day as a COU file.

    • Monthly Supply: Either a Full Supply or COU Supply of all the changes which have occurred in the previous month.

    • Annual Supply: A Full Supply of the data to show how the data looked at the end of each year.

    Further details about the options available to you can be found further down on this page.

    If you choose to receive a COU supply for your CSV data, this can be provided on either a daily or monthly frequency. In both cases, your COU file will contain any changes which have been made to the underlying data within the selected time frequency. If no changes have been made to a selected feature type of your choice, then you will receive a blank COU file.

    If you use OS Select+Build to access the OS NGD, then a separate download file will be provided for each feature type you order. For example, if your selected theme has two feature types you will be supplied with two separate files (CSV or GeoPackage) as part of your order.

    The following tables summarise the different options available to you dependent on what you specify when ordering your data through OS Select+Build.

    For the purposes of the tables below, the following definitions are being used:

    • Unfiltered means a Great Britain supply with no further attribute filters applied.

    • Filtered means an order for data which either has a geographic filter applied or an attribute filter applied.

    Initial Supply
    Update Options

    Daily (filtered / unfiltered)

    N/A

    Monthly (filtered / unfiltered)

    Monthly Full Supply

    Annual (filtered / unfiltered)

    Annual Full Resupply with data from 01 January

    Initial Supply
    Update Options

    Daily (filtered)

    N/A

    Daily (unfiltered)

    Daily COU

    Monthly (filtered)

    Monthly Full Supply

    Monthly (unfiltered)

    Feature types downloaded via OS Select+Build will be supplied with an Order Summary File, a small JSON manifest that provides key metadata about the supplied file. You can use this file to validate the data to ensure the currency, record counts (feature counts), schema version, feature name and coordinate reference system (CRS) match your expected order.

    The following file naming convention will be applied to each Order Summary File you receive:

    • collection_featuretype_orderSummary.json

    For example, the file name for the Building Line Feature Type Order Summary File would look like this:

    • bld_fts_buildingline_orderSummary.json

    The example below shows the information an Order Summary File contains:

    The following table provides a brief description of each field:

    Field
    Description
    Use

    featureName

    The feature type delivered in this order.

    Validate the downloaded feature against your recipe.

    crs

    The coordinate reference system used for your supply.

    Validate the coordinate reference system against the CRS selected for your recipe.

    schemaVersion

    The OS NGD data schema version provided for the feature.

    Coordinate data schema updates with changes to your data.

    Whether accessing OS NGD data through OS Select+Build or OS NGD API – Features, the following currency of the data will apply:

    Theme
    Collection
    Update Frequency

    OS NGD Address

    OS GB Address (*N.B. Not available in OS NGD API – Features)

    Daily

    OS Islands Address (*N.B. Not available in OS NGD API – Features)

    Daily

    For collections that are not updated daily, the table below provides the date of the last update; it also shows the version of the OS MasterMap product to which the OS NGD data corresponds, if applicable:

    Collection
    Last Updated
    Corresponding OS MasterMap Product

    OS Boundaries

    01 October 2026

    Boundary-Line –

    October 2026 publication

    OS Functional Areas

    01 October 2026

    N/A

    OS GB Postcodes

    When accessing OS NGD data through OS NGD API – Tiles, the data currency is weekly for the basemap and variable for the four data overlays – please see the 'What data is available' (for OS NGD API – Tiles) page for more information on update frequency, available feature types and available attribution for this API.

    Geographic filtering

    OS Data Hub
    Premium Plan and Public Sector Plan on the OS Data Hub
    {
     "featureName": "bld-fts-buildingline",
     "crs": "http://www.opengis.net/def/crs/EPSG/0/27700",
     "schemaVersion": "1.0",
     "validFromDate": null,
     "validToDate": "2023-03-01",
     "recordCount": 202653
    }
    • Exceptions to the geographic filtering bullets above include:

      • The OS Islands Address Collection – This collection contains data for Northern Ireland, the Isle of Man, and the Channel Islands, and it will be provided as a full supply of data independent of any geographic filtering applied to your OS NGD recipe.

      • The OS NI Postcodes Collection – This collection contains data for Northern Ireland and it will be provided as a full supply of data independent of any geographic filtering applied to your OS NGD recipe.

    Order update options

    • Monthly orders provide data for the first of the month. For example, if you ordered a Monthly Supply on 20 September 2025, you would receive the data as it was on 01 September 2025.

    • If you select an Annual Full Supply frequency for your OS NGD data order in OS Select+Build, we will provide you with the data as it was on 01 January of the current year. This means if a new feature type or a new data schema version of an existing feature type was released after 01 January and you order either of these as part of your Annual Full Supply, you will receive an empty data package for the newly released feature type / new data schema version of an existing feature type. The data for the new feature type / new data schema version of an existing feature type will then be included in your supply on the next 01 January after the release.

    Update files

    File supply

    Ordering combinations

    GPKG files

    Please note that COU supplies are only available for CSV files; they are not available for GeoPackage files.

    CSV files

    You can use the to manage your daily / monthly COU supply of OS NGD data.

    Order Summary File

    Currency of OS NGD data

    OS Select+Build and OS NGD API – Features

    *Please see the for more information on what features are available in this API.

    OS NGD API – Tiles

    • The OS Functional Areas, OS GB Address, OS Islands Address, and OS NI Postcodes Collections are only available via OS Select+Build and are not available via OS NGD API – Features or OS NGD API – Tiles.

    • The OS GB Postcodes and OS RAMI Collections are only available via OS Select+Build and OS NGD API – Features and are not available via OS NGD API – Tiles.

    Identifying crossing points and bottlenecks recipe guide

    A guide with detailed step-by-step instructions outlining how you can create a recipe in OS Select+Build to identify the location of bridges, tunnels, fords and crossing points.

    What is the identifying crossing points and bottlenecks recipe?

    The guide below provides a geospatial toolkit for helping you identify the location of bridges, tunnels, fords and crossing points using the OS NGD; its step-by-step instructions outline how to select relevant pieces of addressing, structures, transport and water data from the OS NGD and weave them into a recipe.

    For this recipe guide:

    • We define a crossing point as a feature where a pedestrian or vehicle passes over or under another feature.

    • We define a bottleneck as a feature that could restrict or channel the movement of pedestrians or vehicles.

    Use cases

    The recipe will be useful for organisations (particularly emergency services) that need to understand critical infrastructure and mobility restrictions for vehicles and pedestrians.

    Use cases for the recipe include:

    • Understanding mobility constraints for pedestrians and vehicles in communities

    • Planning road closures

    • Managing evacuations

    • Predicting the movement patterns of crowds

    • Identifying choke points for exceptional loads / large vehicles

    • Identifying if services can access different communities

    • Incident response planning and situational awareness

    • Mapping critical infrastructure

    • Modelling transport routes

    In this recipe, we'll be identifying the exact location of the four types of features using point and topographic features, so we'll be excluding generic network data representations.

    The following four feature types are included in the identifying crossing points and bottlenecks recipe:

    Theme
    Collection
    Feature Type

    Types of bridges included and links to the code lists that define them:

    Type of Bridge
    Link to the Code List(s) Containing the Definition(s) for the Infrastructure Feature(s)

    Types of tunnels included and links to the code lists that define them:

    Type of Tunnels
    Link to the Code List(s) Containing the Definition(s) for the Infrastructure Feature

    Types of crossings included and links to the code lists that define them:

    Type of Crossing
    Link to the Code List(s) Containing the Definition(s) for the Infrastructure Feature

    To create the identifying crossing points and bottlenecks recipe in OS Select+Build:

    1

    Click Log in on the OS Data Hub menu bar to log into your account.

    2

    Select Data from the menu bar to view your workspace.

    3

    Choose Downloads > OS Select+Build Recipe Library from the left-hand-side secondary navigation menu.


    More information on creating, editing and deleting recipes in OS Select+Build and on adding attribute filters to recipes can be found in the following guides:

    Once you've created your recipe, you'll need to add a data package to receive the data. Data packages allow you to select the format, update frequency and area of interest for the required data.

    The following guide will help you to create a data package from your new recipe:

    Once you've created your recipe and added a data package to it to receive the data, you can import the data into your chosen GIS (geographic information system) to analyse it or create maps.

    The following guide gives an example of how to create a map in QGIS, standardise the geometry of the datasets and, if required, standardise the data into one layer using common attributes:

    Lower Tier Local Authority

    This feature type has been created to provide greater alignment between OS data and Office for National Statistics (ONS) data and to support a wider range of analysis. Welsh and Scottish Unitary Authorities will have alternative name and language values.

    Temporal filtering

    The earliest date on which you can request a one-off snapshot of a date in the past for data in this feature type is 29 September 2022.

    Any data temporally filtered earlier than the specified earliest date noted above for the data schema version may contain data inconsistencies.

    Feature type attributes

    The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

    Comma-separated values (CSV) file format is universally supported for easy ingestion into all major database products. Before loading OS NGD data contained in CSV files into a database, it is necessary to create relevant tables. Data definition language (DDL) statements for PostgreSQL, SQL Server and Oracle can be accessed in our .

    For instructions on loading CSV files, see the guide.

    osid

    Primary identifier for the feature. The OSID is a Globally Unique Identifier (GUID) and requires no centralised authority to ensure uniqueness. Note that the same OSID can occur in more than one feature type when a single feature is represented multiple times in the OS NGD.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 36

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Topographic identifier (TOID) of the feature, as published in the OS MasterMap suite of products.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 20

    • OS Select+Build Filterable: Yes

    Date when the version was last updated.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The date this version of the feature became the latest version.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The date this version of the feature was superseded by an update or ceased to exist.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The type of change that generated a new version of the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    Geometry for the feature.

    • Data Types: Geometry (GPKG), WKT (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The measured area of the geometry in square metres.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 18

    • Scale: 6

    The OS NGD theme to which this feature belongs.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 40

    A single descriptive value intended for a quick understanding of what the feature represents.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    Name assigned to identify the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 254

    • OS Select+Build Filterable: Yes

    The language of name1, provided as a 3-digit ISO 639-2 code ('eng, 'cym', 'gla').

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    The alternative language name assigned to identify the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 254

    • OS Select+Build Filterable: Yes

    The language of name2, provided as a 3-digit ISO 639-2 code ('eng, 'cym', 'gla').

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    Set to the census / Government Statistical Service (GSS) Code for the boundary, for example, E10000014.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 10

    • OS Select+Build Filterable: Yes

    A single description value for boundary type.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    Identifier for the Parent Boundary

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 36

    • OS Select+Build Filterable: No

    Further classification indicating the Parent Boundary feature type.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 50

    Further classification indicating the Parent Boundary.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 50

    Name assigned to identify the Parent Boundary. If the name is defined in multiple languages, then each name shall be provided with an associated language qualifier. If the proper name is only defined in one language, then no language qualifier will be provided.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 254

    • OS Select+Build Filterable: No

    The language type associated with name1 for the Parent Boundary. The valid values are defined in the LanguageValue codelist.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    Name assigned to identify the Parent Boundary. If the name is defined in multiple languages, then each name shall be provided with an associated language qualifier. If the proper name is only defined in one language, then no language qualifier will be provided.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 254

    • OS Select+Build Filterable: No

    The language type associated with name2 for the Parent Boundary. The valid values are defined in the LanguageValue codelist.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    The inland area of the feature in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    The non-inland area in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    The total area in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    A boolean value indicating whether the feature is part of a Borough or not

    • Data Types: Integer (GPKG), String (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    GitHub - OrdnanceSurvey/OS-NGD-Stylesheets: Ordnance Survey Repository containing stylesheets for OS NGD data in QML, QLR, LYRX, LYR and SLD formatGitHub

    Devolved Parliament Constituency

    Scotland is divided into parliamentary constituencies for voting purposes to elect Members of the Scottish Parliament (MSPs). Wales is divided into parliamentary constituencies for voting purposes to elect parliamentary members (MS) to the Welsh Parliament.

    The following table provides details about this feature type’s data schema versions, including the reasons behind the changes and the related launch date when each version went live.

    Version ↓
    Launch Date
    Latest Date
    Change

    Alternate Address

    The Alternate Address Related Component provides alternative address labels where they exist for the ‘current’ address represented on a given feature type.

    There are two principal scenarios by which an Alternate Address can be created; both of these scenarios will result in addresses being present in the Alternate Address Related Component:

    1. Official alternate addresses captured by Local Authorities

    This occurs where there is a a variation on the official address held by Local Authorities that is represented by the preferred UPRN in the Built Address Feature Type.

    For example, ‘10 High Street’ may have an Alternate Address label captured as ‘Rose Cottage’. These addresses are represented by an ‘Alternate’ classification in the Address Status attribute.

    Examples:

  • COU Supplies are not available for AOIs, monthly Full Supplies are available for AOIs.

  • For example, the March 2026 OS NGD data enhancements release contained six new feature types (Retail Area Aggregated, Retail Area Major, Retail Area Minor, Postcode Unit Point, Postcode Unit Point, and Postcode Unit Area) and one new data schema version for an existing feature type (Compound Structure v3.0). As per the bullet above, the data for the new feature types and the new data schema version for the existing feature type will not be part of Annual Full Supply orders until 01 January 2027.

  • For example, the October 2026 OS NGD data enhancements release contained five new data schema versions for existing feature types: Regional Authority v2.0, Royal Mail Address v1.1 and v2.0 (OS GB Address Collection), and Royal Mail Address v1.1 and v2.0 (OS Islands Address Collection). The new data schema versions for the existing feature types will not be part of Annual Full Supply orders until 01 January 2027.

  • The OS Boundaries Collection is only available via OS Select+Build and OS NGD API – Tiles and is not available via OS NGD API – Features.
  • The Tidal Boundary Continuous High, Tidal Boundary Continuous Low, River Basin District Catchment and Waterbody Catchment Feature Types (of the OS Water Features Collection) are not available via OS NGD API – Features, but they are available via OS Select+Build and OS NGD API – Tiles.

  • Monthly COU or Monthly Full Supply

    Annual (filtered / unfiltered)

    Annual Full Resupply with data from 01 January

    validFromDate

    The start date of coverage for this supply.

    Validate the currency of your data to ensure the earliest date aligns with the expected supply window for your order frequency.

    validToDate

    The end date of coverage for this supply.

    Validate the currency of your data to ensure the latest date aligns with the expected supply window for your order frequency.

    recordCount

    The total number of records delivered in the file.

    Check that delivered entries match the number of records expected for your download.

    OS NGD Administrative and Statistical Units

    OS Boundaries (*N.B. Not available in OS NGD API – Features)

    Biannual

    OS Functional Areas (*N.B. Not available in OS NGD API – Features)

    Biannual

    OS GB Postcodes

    Monthly

    OS NI Postcodes (*N.B. Not available in OS NGD API – Features)

    Monthly

    OS NGD Buildings

    OS Buildings Features

    Daily

    OS NGD Geographical Names

    OS Named Features

    Daily

    OS NGD Land

    OS Land Features

    Daily

    OS NGD Land Use

    OS Land Use Features

    Daily

    OS NGD Structures

    OS Structure Features

    Daily

    OS NGD Transport

    OS Transport Features

    Daily (apart from the Street Light Feature Type which is updated monthly)

    OS Transport Network

    Monthly

    OS RAMI

    Monthly

    OS NGD Water

    OS Water Features

    Daily

    OS Water Network

    Quarterly

    19 October 2026

    N/A

    OS NI Postcodes

    19 October 2026

    N/A

    OS RAMI

    06 November 2026

    OS MasterMap Highways Network – November 2026 publication

    OS Transport Features – Street Light Feature Type only

    06 November 2026

    N/A

    OS Transport Network

    06 November 2026

    OS MasterMap Highways Network – November 2026 publication

    OS Water Network

    29 September 2026

    N/A

    Exceptions

    Please note

    Please note:

    OS Downloads API
    'What data is available' (for OS NGD API – Features) page

    Data Schema Version: 1.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Geometry Type: MultiPolygon

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0

  • Data Schema Version: 1.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Data Schema Version: 1.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Data Schema Version: 1.0

    OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0

  • Data Schema Version: 1.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Data Schema Version: 1.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Data Schema Version: 1.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • toid

    versiondate

    versionavailablefromdate

    versionavailabletodate

    changetype

    geometry

    geometry_area

    theme

    description

    name1_text

    name1_language

    name2_text

    name2_language

    gsscode

    boundarytype

    boundaryparentreference_id

    boundaryparentreference_featuretype

    boundaryparentreference_classification

    boundaryparentreference_name1_text

    boundaryparentreference_name1_language

    boundaryparentreference_name2_text

    boundaryparentreference_name2_language

    landareahectares

    tidalareahectares

    totalareahectares

    isborough

    Loading OS NGD CSV files into databases

    changetypevalue
    themevalue
    lowertierlocalauthoritydescriptionvalue
    languagevalue
    languagevalue
    boundarytypevalue
    parentfeaturetypevalue
    parentboundarydescriptionvalue
    languagevalue
    languagevalue
    OS NGD Resources GitHub repository
    Getting Started with CSV

    OS Water Features

    Clapper Bridge is defined in the

    Lift Bridge

    Lift Bridge is defined in the

    Swing Bridge

    Swing Bridge is defined in the

    4

    Choose Create a new recipe

    Click the Create a new recipe button at the top right-hand-side of the screen.

    5

    Give the recipe a name and description

    • Give your recipe a descriptive name in the Recipe name dialog box on the left-hand-side of the screen.

    • Add a detailed description for your recipe (this is optional, but it's useful if other team members will be accessing the recipe).

    6

    Select the feature types

    Select your OS NGD data by choosing the themes, collections and feature types you want to include in your recipe. You'll need to select the following four feature types from the Themes panel on the left-hand-side of the screen:

    • Non Addressable Object (found within Address > GB Address > Non Addressable Object)

    • Compound Structure (found within Structures > Structure Features > Compound Structure)

    • Road Track Or Path (found within Transport > Transport Features > Road Track Or Path)

    • Water Point (found within Water > Water Features > Water Point)

    7

    (Optional) Choose a data schema version

    Selecting a data schema version for a feature type is an optional step; if you don't choose a particular data schema version for a feature type, OS Select+Build will always select the latest available data schema version for you for each feature type by default. We recommend using the pre-selected latest data schema version for feature types unless you have a specific need to use an earlier one. (See the Data schema versioning page for more information on data schema versioning in the OS NGD.)

    If you wish to choose which schema version (where applicable) you'd like to receive the data in for a feature type, click on the feature type name within the tree view in the secondary navigation menu, then choose a data schema version from the Choose Data Schema drop-down box in the right-hand side panel.

    Screenshot showing the tree view in the secondary navigation menu that opens when you create a recipe in OS Select+Build in the OS Data Hub. The Compound Structure Feature Type has been selected in this screenshot and the Choose Schema Version drop-down menu is visible in the right-hand-side panel, which lets you select the data schema version you want to use for the feature type.
    8

    Add a filter to the Non Addressable Object Feature Type

    OS Select+Build provides the option to apply filters on certain attributes when creating a recipe so that only the features and attribution that are needed are included in the data.

    • A filter is required on the Non Addressable Object Feature Type on the Classification Description attribute so that only level crossing and railway pedestrian crossing addresses appear in the data.

    • A filter is required on the Compound Structure Feature Type on the Description attribute so that 12 specified infrastructure types (for example, road tunnels, footbridges and swing bridges) appear in the data.

    To add a filter to the Non Addressable Object Feature Type:

    • Click on the filter icon to the right of Non Addressable Object in the theme selection tree (make sure you select Non Addressable Object from the GB Address drop-down, not from the Islands Address drop-down).

    Screenshot of the theme selection tree in OS Select+Build with the filter icon highlighted beside Non Addressable Object.

    The Advanced Filter Options panel will then slide into view from the right-hand side of the screen and you can begin to build your filter.

    In the Advanced Filter Options panel:

    • Click the + Add rule button twice, which will give you two rules.

    • In the first rule, select classificationDescription from the first drop-down, leave the operator in the second drop-down as: = (the equal sign), then select Level Crossing from the third drop-down.

    • In the second rule, select classificationDescription from the first drop-down, leave the operator in the second drop-down as: = (the equal sign), then select Railway Pedestrian Crossing from the third drop-down.

    • Before continuing, select whether you would like the rules within the group to have an And or an Or condition. In this case, you should select Or from the And / Or selector.

    • Click the Apply filter button.

    • Close the Advanced Filter Options panel.

    9

    Add a filter to the Compound Structure Feature Type

    To add a filter to the Compound Structure Feature Type:

    • Click on the filter icon to the right of Compound Structure in the theme selection tree.

    Screenshot of the theme selection tree in OS Select+Build with the filter icon highlighted beside Compound Structure.

    The Advanced Filter Options panel will then slide into view from the right-hand side of the screen and you can begin to build your filter.

    In the Advanced Filter Options panel:

    • Click the + Add rule button 12 times, which will give you 12 rules.

    • In the first rule, select Description from the first drop-down, leave the operator in the second drop-down as: = (the equal sign), then select Bridge from the third drop-down.

    • In the second rule, select Description from the first drop-down, leave the operator in the second drop-down as: = (the equal sign), then select Transporter Bridge from the third drop-down.

    • Repeat this process for rules 3 to 12; for each rule, select Description from the first drop-down, leave the operator in the second drop-down as: = (the equal sign), then select the following options from the third drop-down (until the Advanced Filter Options panel looks like the example screenshot below):

      • Rail Tunnel

      • Road Tunnel

      • Tube Or Metro Tunnel

    (You may also notice there is another attribute called Status, which is an indicator of whether the feature is currently performing its original function; for this recipe, we want all infrastructure, but we can filter on the Status attribute in our GIS or RDBMS after download.)

    • Before continuing, select whether you would like the rules within the group to have an And or an Or condition. In this case, you should select Or from the And / Or selector.

    • Click the Apply filter button.

    • Close the Advanced Filter Options panel.

    10

    Add a filter to the Road Track Or Path Feature Type

    To add a filter to the Road Track Or Path Feature Type:

    • Click on the filter icon to the right of Road Track Or Path in the theme selection tree.

    Screenshot of the theme selection tree in OS Select+Build with the filter icon highlighted beside Road Track Or Path.

    The Advanced Filter Options panel will then slide into view from the right-hand side of the screen and you can begin to build your filter.

    In the Advanced Filter Options panel:

    • Click the + Add rule button three times, which will give you three rules.

    • In the first rule, select Description from the first drop-down, leave the operator in the second drop-down as: = (the equal sign), then select Ford from the third drop-down.

    • In the second rule, select Description from the first drop-down, leave the operator in the second drop-down as: = (the equal sign), then select Level Crossing from the third drop-down.

    • In the third rule, select Description from the first drop-down, leave the operator in the second drop-down as: = (the equal sign), then select Pedestrian Crossing from the third drop-down.

    • Before continuing, select whether you would like the rules within the group to have an And or an Or condition. In this case, you should select Or from the And / Or selector.

    • Click the Apply filter button.

    • Close the Advanced Filter Options panel.

    11

    Add a filter to the Water Point Feature Type

    To add a filter to the Water Point Feature Type:

    • Click on the filter icon to the right of Water Point in the theme selection tree.

    Screenshot of the theme selection tree in OS Select+Build with the filter icon highlighted beside Water Point.

    The Advanced Filter Options panel will then slide into view from the right-hand side of the screen and you can begin to build your filter.

    In the Advanced Filter Options panel:

    • Click the + Add rule button twice, which will give you two rules.

    • In the first rule, select Description from the first drop-down, leave the operator in the second drop-down as: = (the equal sign), then select Ford from the third drop-down.

    • In the second rule, select Description from the first drop-down, leave the operator in the second drop-down as: = (the equal sign), then select Tidal Ford from the third drop-down.

    • Before continuing, select whether you would like the rules within the group to have an And or an Or condition. In this case, you should select Or from the And / Or selector.

    • Click the Apply filter button.

    • Close the Advanced Filter Options panel.

    12

    Finish creating the recipe

    Once you have applied filters to the four feature types, click the Create recipe button to complete the recipe creation process. Your new recipe will now instantly be available in your OS Select+Build Recipe Library.

    You can view a summary of the completed identifying crossing points and bottlenecks recipe, including the required feature types and filters, if you click Data > Downloads > OS Select+Build Recipe Library > *your recipe's name* > View all filters.

    The recipe summary should look like the screenshot below:

    Screenshot of the OS Select+Build Recipe details screen showing a summary of the identifying crossing points and bottlenecks recipe, including selected feature types and their data schema versions, plus all filters applied.

    OS NGD Address

    OS GB Address

    Non Addressable Object

    OS NGD Structures

    OS Structure Features

    Compound Structure

    OS NGD Transport

    OS Transport Features

    Road Track Or Path

    Bridge

    Bridge is defined in the Compound Structure Description Value Code List

    Transporter Bridge

    Transporter Bridge is defined in the Compound Structure Description Value Code List

    Footbridge

    Footbridge is defined in Compound Structure Description Value Code List

    Footbridge / Walkway

    Footbridge / Walkway is defined in Address Classification Description Value Code List

    Rail Tunnel

    Rail Tunnel is defined in the Compound Structure Description Value Code List

    Tube Or Metro Tunnel

    Tube Or Metro Tunnel is defined in the Compound Structure Description Value Code List

    Pedestrian Tunnel Or Subway

    Pedestrian Tunnel Or Subway is defined in the Compound Structure Description Value Code List

    Underpass

    Underpass is defined in the Compound Structure Description Value Code List

    Canal Tunnel

    Level Crossing

    Level Crossing is defined in the Address Classification Description Value Code List and Road Track Or Path Description Value Code List

    Railway Pedestrian Crossing

    Railway Pedestrian Crossing is defined in the Address Classification Description Value Code List

    Pedestrian Crossing

    Pedestrian Crossing is defined in the Road Track Or Path Description Value Code List

    Ford

    Ford is defined in the Water Point Description Value Code List and Road Track Or Path Description Value Code List

    Feature types required

    Note about adapting or skipping filtering

    • You can adapt the suggested identifying crossing points and bottlenecks recipe at the recipe creation or editing stage so that it fully meets your needs. The filters chosen for this recipe (see steps 8 to 11 below) are a suggestion and you can amend them depending on your requirements.

    • Applying filters in OS Select+Build to the four feature types at the recipe creation (or recipe editing) stage lets you target the right types of bridges, tunnels and crossings. Filtering will also reduce the number of features being downloaded as you'll just be downloading a subset of the features available for each feature type selected.

    • If preferred, you can skip the filtering steps (8 to 11 below) at the recipe creation stage, download all features for the four feature types, then subsequently filter the data later in your chosen geographic information system (GIS) or relational database management system (RDBMS).

    Types of bridges, tunnels and crossings included

    Creating the recipe

    Log into your OS Data Hub account

    Navigate to the OS Data Hub workspace

    Navigate to the OS Select+Build Recipe Library

    What's next?

    Further guidance on creating, editing and deleting recipes

    Add a data package to your recipe

    Create a map to identify crossing points and bottlenecks from your recipe

    Definitions

    A screenshot of the OS Data Hub home page showing the sign up and log in buttons in the top right hand corner
    Screenshot showing the OS Data Hub homepage.

    OS NGD Water

    Clapper Bridge

    Canal Tunnel is defined in the

    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.

    Minor version increment to make Boundary Parent Reference ID, Boundary Parent Reference Feature Type, Boundary Parent Reference Classification and Boundary Parent Reference Name 1 Text attributes nullable in line with boundary changes in Wales.

    1.0

    29 September 2022

    30 April 2026

    Initial launch of the Devolved Parliament Constituency Feature Type.

    Please see Data schema versioning for in-depth information about data schema versioning in the OS NGD.

    Temporal filtering allows you to order a one-off snapshot of data from the OS NGD from a current or past date. It is an optional step when you create a new data package in OS Select+Build (the OS NGD download service).

    The earliest and latest dates on which you can request a one-off snapshot of a date in the past for this feature type's data schema versions are indicated in the Data schema version table above. Please note that any data temporally filtered earlier than the specified launch date indicated in the table for the data schema versions may contain data inconsistencies.

    More information about temporal filtering on OS NGD feature types is available from the Getting started with temporal filtering guide.

    The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

    Primary identifier for the feature. The OSID is a Globally Unique Identifier (GUID) and requires no centralised authority to ensure uniqueness. Note that the same OSID can occur in more than one feature type when a single feature is represented multiple times in the OS NGD.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 36

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    Topographic identifier (TOID) of the feature, as published in the OS MasterMap suite of products.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 20

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.1

    Date when the version was last updated.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The date this version of the feature became the latest version.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The date this version of the feature was superseded by an update or ceased to exist.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The type of change that generated a new version of the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: changetypevalue

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    Geometry for the feature.

    • Data Types: Geometry (GPKG), WKT (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    • Geometry Type: MultiPolygon

    The measured area of the geometry in square metres.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 18

    • Scale: 6

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.1

    The OS NGD theme to which this feature belongs.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: themevalue

    • Max Length: 40

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    A single descriptive value intended for a quick understanding of what the feature represents.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: devolvedparliamentconstituencydescriptionvalue

    • Max Length: 50

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.1

    Name assigned to identify the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 254

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.1

    The language of name1, provided as a 3-digit ISO 639-2 code ('eng, 'cym', 'gla').

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: languagevalue

    • Max Length: 3

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The alternative language name assigned to identify the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 254

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.1

    The language of name2, provided as a 3-digit ISO 639-2 code ('eng, 'cym', 'gla').

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: languagevalue

    • Max Length: 3

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    Set to the census / Government Statistical Service (GSS) Code for the boundary, for example, E10000014.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 10

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.1

    A single description value for boundary type.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: boundarytypevalue

    • Max Length: 50

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.1

    Identifier for the Parent Boundary

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 36

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    Further classification indicating the Parent Boundary feature type.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: parentfeaturetypevalue

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    Further classification indicating the Parent Boundary.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: parentboundarydescriptionvalue

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    Name assigned to identify the Parent Boundary. If the name is defined in multiple languages, then each name shall be provided with an associated language qualifier. If the proper name is only defined in one language, then no language qualifier will be provided.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 254

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The language type associated with name1 for the Parent Boundary. The valid values are defined in the LanguageValue codelist.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: languagevalue

    • Max Length: 3

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    Name assigned to identify the Parent Boundary. If the name is defined in multiple languages, then each name shall be provided with an associated language qualifier. If the proper name is only defined in one language, then no language qualifier will be provided.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 254

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The language type associated with name2 for the Parent Boundary. The valid values are defined in the LanguageValue codelist.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: languagevalue

    • Max Length: 3

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The inland area of the feature in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The non-inland area in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The total area in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    1.1

    01 May 2026

    Data schema versioning

    Data schema version table

    Ongoing

    Temporal filtering

    Feature type attributes

    Comma-separated values (CSV) file format is universally supported for easy ingestion into all major database products. Before loading OS NGD data contained in CSV files into a database, it is necessary to create relevant tables. Data definition language (DDL) statements for PostgreSQL, SQL Server and Oracle can be accessed in our .

    For instructions on loading CSV files, see the guide.

    osid

    toid

    versiondate

    versionavailablefromdate

    versionavailabletodate

    changetype

    geometry

    geometry_area

    theme

    description

    name1_text

    name1_language

    name2_text

    name2_language

    gsscode

    boundarytype

    boundaryparentreference_id

    boundaryparentreference_featuretype

    boundaryparentreference_classification

    boundaryparentreference_name1_text

    boundaryparentreference_name1_language

    boundaryparentreference_name2_text

    boundaryparentreference_name2_language

    landareahectares

    tidalareahectares

    totalareahectares

    Built Address: UPRN 12345: 12 High Street, addressstatus: Approved
  • Alternate Address: UPRN 12345: Rose Cottage, addresstatus: Alternate

    1. An additional non-official address captured for lifecycle purposes

    In the case of pre-build addresses, these alternate addresses commonly represent labels attached to the plot in earlier stages in the development cycle that have subsequently been updated. Historic Address Alternate Address labels, where held, will be early iterations of the address that became live and will be alternate addresses of the ‘current’ UPRN on the Pre-Build Feature Type.

    Examples:

    • Built Address: UPRN 12345: Explorer House, Adanac Drive, SO15 0AS, addressstatus: Approved

    • Alternate Address: UPRN 12345: Development Site, addressstatus: Historic

    • Alternate Address: UPRN 12345: Plot 12, addressstatus: Historic

    The following table provides details about this related component’s data schema versions, including the reasons behind the changes and the related launch date when each version went live.

    Version ↓
    Launch Date
    Latest Date
    Change

    3.0

    30 September 2025

    Ongoing

    Major version increment to align with concurrent major version increments made to four feature types in the GB Address and Islands Address Collections: Built Address, Historic Address, Non-Addressable Object, and Pre-Build Address. (Related components follow the versioning of the addressing feature types they are associated with.) Max length increased for the Alternate Sub Name and Full Address attributes.

    2.0

    28 March 2023

    Ongoing

    Major version increment to align with concurrent major version increments made to four feature types in the GB Address and Islands Address Collections: Built Address, Historic Address, Non-Addressable Object, and Pre-Build Address. (Related components follow the versioning of the addressing feature types they are associated with.) New attribution added to related component for Full Address, Lowest Floor Level and Highest Floor Level.

    Please see Data schema versioning for in-depth information about data schema versioning in the OS NGD.

    Temporal filtering allows you to order a one-off snapshot of data from the OS NGD from a current or past date. It is an optional step when you create a new data package in OS Select+Build (the OS NGD download service).

    The earliest and latest dates on which you can request a one-off snapshot of a date in the past for this related component's data schema versions are indicated in the Data schema version table above. Please note that any data temporally filtered earlier than the specified launch date indicated in the table for the data schema versions may contain data inconsistencies.

    More information about temporal filtering is available from the Getting started with temporal filtering guide.

    The following sub-sections provide details about the attributes included with this related component, their data types in the different output formats, and other important metadata about them.

    Primary key providing a unique row identifier assigned to enable indexing for efficient querying.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 36

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Unique Property Reference Number (UPRN) assigned by a local custodian or Ordnance Survey as a persistent identifier.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Date of the feature version to which this related component applies.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The Unique Street Reference Number (USRN), a unique and persistent identifier of a Street which is assigned by the Roads or Highway Authority.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The lifecycle status of a given Address, for example, Alternative, Approved, Historic.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressstatuscode

    • Max Length: 11

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The Alternate Sub Name provides an alternative address label to the one provided in the Sub Name. An alternative address label may be present for a number of reasons, for example, retention of an old address label or an alias address label has been recorded by the Local Authority.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 500

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    The Alternate Name provides an alternative address label to the one provided in the name. An alternative address label may be present for a number of reasons, for example, retention of an old address label or an alias address label has been recorded by the Local Authority.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The Alternate Number provides an alternative address number to the one provided in the Number attribute.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 13

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Name, number or descriptor that identifies the nearest accessible Street that an Address is located on or close to.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 100

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of a populated place within a settlement that the Street is located within. Where a locality can be a suburb, housing estate or commercial estate.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the settlement that the Street is located within. Where a settlement can be a City, Town, Village or Hamlet.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the island upon which an Address is located.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The language in which the address label attribution has been captured for the alternative record.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: languagevalue

    • Max Length: 3

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The postcode unit that the Address is situated within. A postcode is an abbreviated form of address, made up of combinations of between five and seven alphanumeric characters. These alphanumeric characters are used by Royal Mail to help with the automated sorting of mail. A postcode may cover between 1 and 100 addresses. Postcodes (for example, NW6 4DP) are comprised of two components. The first component is the outward code (or ‘outcode’), which is the first two to four characters of a postcode, constituting the postcode area and the postcode district, for example, NW6. The outward code is the part of the postcode that enables mail to be sent from the accepting office to the correct area for delivery. The second component of a postcode is the inward code (or ‘incode’), which is the last three characters of the postcode, constituting the postcode sector and the postcode unit, for example, 4DP. The inward code is used to sort mail at the local delivery office. This field will contain the Royal Mail Postcode Address File (PAF) postcode where the Local Authority address has been matched to PAF. Where a match has not been made, the postcode information is sourced from Local Authority assigned data. In cases where the Local Authority do not hold a valid postcode, a spatial nearest neighbour function is used to spatially derive the postcode from the closest Address with a valid postcode.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 8

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Concatenation of the following address components: Organisation (Pre-Build and Built Address Feature Types only), Sub Name and / or Name and / or Number, Street Name, Locality, Town Name, Island Name and Postcode Locator.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 1 000

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 500

    • OS Select+Build Filterable: No

    Floor level represents either: the access point to the Address, or the floor level or levels that the Address is located on fully occupies or represents occupiable space within the property.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 30

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    In cases where the Floor Level attribute contains a list of floor levels (for example, where a commercial organisation occupies multiple levels within a building), the first value provided will be taken as the lowest floor level. For example, where Floor Level attribute values are given as -1, 0, 1, 2, 3, the Lowest Floor Level is -1. Mezzanine levels may be represented by a partial number, for example, 1.5. If the Floor Level attribute only contains one value, that value will also be used by the Lowest Floor Level attribute.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 3

    • Scale: 1

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0, 3.0

    In cases where the Floor Level attribute contains a list of floor levels (for example, where a commercial organisation occupies multiple levels within a building), the last value provided will be taken as the highest floor level. For example, where Floor Level attribute values are given as -1, 0, 1, 2, 3, the Highest Floor Level is 3. Mezzanine levels may be represented by a partial number, for example, 1.5. If the Floor Level attribute only contains one value, that value will also be used by the Highest Floor Level attribute.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 3

    • Scale: 1

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0, 3.0

    The date on which any attribute of the record was last changed.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The date on which this record was inserted into the Local Authority database.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The date on which the record ceased to exist.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Data schema versioning

    Data schema version table

    Temporal filtering

    Related component attributes

    alternateaddressid

    uprn

    featuretypeversiondate

    usrn

    addressstatus

    alternatesubname

    alternatename

    alternatenumber

    streetname

    locality

    townname

    islandname

    Note: This attribute is currently only populated in the OS Islands Address Collection.

    language

    postcode

    fulladdress

    floorlevel

    lowestfloorlevel

    This attribute is derived from Floor Level attribute data. Where the Floor Level field is NULL, Lowest Floor Level values will also be NULL.

    highestfloorlevel

    This attribute is derived from Floor Level attribute data. Where the Floor Level field is NULL, Highest Floor Level values will also be NULL.

    updatedate

    effectivestartdate

    effectiveenddate

    Postal Address

    The Postal Address Related Component provides the Royal Mail delivery point address from Royal Mail's Postcode Address File (PAF) where it has been matched to a Local Authority address in the National Land and Property Gazetteer.

    Data schema versioning

    The following table provides details about this related component’s data schema versions, including the reasons behind the changes and the related launch date when each version went live.

    Data schema version table

    Version ↓
    Launch Date
    Latest Date
    Change

    2.0

    28 March 2023

    Please see for in-depth information about data schema versioning in the OS NGD.

    Temporal filtering allows you to order a one-off snapshot of data from the OS NGD from a current or past date. It is an optional step when you create a new data package in OS Select+Build (the OS NGD download service).

    The earliest and latest dates on which you can request a one-off snapshot of a date in the past for this related component's data schema versions are indicated in the above. Please note that any data temporally filtered earlier than the specified launch date indicated in the table for the data schema versions may contain data inconsistencies.

    More information about temporal filtering is available from the .

    The following sub-sections provide details about the attributes included with this related component, their data types in the different output formats, and other important metadata about them.

    Royal Mail’s Unique Delivery Point Reference Number (UDPRN).

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0

    Unique Property Reference Number (UPRN) assigned by a local custodian or Ordnance Survey as a persistent identifier.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0

    Date of the feature version to which this related component applies.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0

    The organisation name is the business name given to an Address 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.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 60

    • OS Select+Build Filterable: No

    For some organisations, department name is indicated because mail is received by subdivisions of the main organisation at distinct delivery points.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 60

    • OS Select+Build Filterable: No

    The sub building name and / or number are identifiers for subdivisions of properties.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 30

    • OS Select+Build Filterable: No

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

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 50

    • OS Select+Build Filterable: No

    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 Building Name or the Sub Building Name fields.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 4

    • OS Select+Build Filterable: No

    In certain places, for example, town centres, there are named thoroughfares within other named thoroughfares, for example, parades of shops on a high street where different parades have their own identity. For example, KINGS PARADE, HIGH STREET and QUEENS PARADE, HIGH STREET.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 80

    • OS Select+Build Filterable: No

    A thoroughfare is a road, track or named access route on which there are Royal Mail delivery points, for example, HIGH STREET.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 80

    • OS Select+Build Filterable: No

    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.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: No

    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.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: No

    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 office in a town or city.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 30

    • OS Select+Build Filterable: No

    The postcode unit that the Address is situated within. A postcode is an abbreviated form of address, made up of combinations of between five and seven alphanumeric characters. These alphanumeric characters are used by Royal Mail to help with the automated sorting of mail. A postcode may cover between 1 and 100 addresses. Postcodes (for example, NW6 4DP) are comprised of two components. The first component is the outward code (or ‘outcode’), which is the first two to four characters of a postcode, constituting the postcode area and the postcode district, for example, NW6. The outward code is the part of the postcode that enables mail to be sent from the accepting office to the correct area for delivery. The second component of a postcode is the inward code (or ‘incode’), which is the last three characters of the postcode, constituting the postcode sector and the postcode unit, for example, 4DP. The inward code is used to sort mail at the local delivery office. This field will contain the Royal Mail Postcode Address File (PAF) postcode where the Local Authority address has been matched to PAF. Where a match has not been made, the postcode information is sourced from Local Authority assigned data. In cases where the Local Authority do not hold a valid postcode, a spatial nearest neighbour function is used to spatially derive the postcode from the closest Address with a valid postcode.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 8

    • OS Select+Build Filterable: No

    Describes the address as a small or large user as defined by Royal Mail. A large user postcode typically receives over 1 000 pieces of mail per day.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 10

    A two-character code uniquely identifying an individual delivery point within a postcode.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 2

    • OS Select+Build Filterable: No

    The Welsh translation of Dependent Thoroughfare.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 80

    • OS Select+Build Filterable: No

    The Welsh translation of Thoroughfare.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 80

    • OS Select+Build Filterable: No

    The Welsh translation of Double Dependent Locality.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: No

    The Welsh translation of Dependent Locality.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: No

    The Welsh translation of Post Town.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 30

    • OS Select+Build Filterable: No

    Post Office Box (PO Box) number or the British Forces Post Office (BFPO) number.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 6

    • OS Select+Build Filterable: No

    The date on which the PAF record was processed into the database.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0

    Name of the originating data provider that defined the reference or link.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 30

    • OS Select+Build Filterable: No

    The date on which any attribute of the record was last changed.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0

    The date on which this record was inserted into the Local Authority database.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0

    The date on which the record ceased to exist.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0

    GLA Assembly Constituency

    With the introduction of the regional government for London (referred to as the Greater London Authority or GLA by OS NGD documentation), the proportional representation voting area for this new administration is the GLA Assembly Constituency.

    Data schema versioning

    The following table provides details about this feature type’s data schema versions, including the reasons behind the changes and the related launch date when each version went live.

    Data schema version table

    Version ↓
    Launch Date
    Latest Date
    Change

    1.1

    28 July 2025

    Please see for in-depth information about data schema versioning in the OS NGD.

    Temporal filtering allows you to order a one-off snapshot of data from the OS NGD from a current or past date. It is an optional step when you create a new data package in OS Select+Build (the OS NGD download service).

    The earliest and latest dates on which you can request a one-off snapshot of a date in the past for this feature type's data schema versions are indicated in the above. Please note that any data temporally filtered earlier than the specified launch date indicated in the table for the data schema versions may contain data inconsistencies.

    More information about temporal filtering on OS NGD feature types is available from the .

    The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

    Primary identifier for the feature. The OSID is a Globally Unique Identifier (GUID) and requires no centralised authority to ensure uniqueness. Note that the same OSID can occur in more than one feature type when a single feature is represented multiple times in the OS NGD.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 36

    • OS Select+Build Filterable: No

    Topographic identifier (TOID) of the feature, as published in the OS MasterMap suite of products.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 20

    • OS Select+Build Filterable: Yes

    Date when the version was last updated.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The date this version of the feature became the latest version.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The date this version of the feature was superseded by an update or ceased to exist.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The type of change that generated a new version of the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    Geometry for the feature.

    • Data Types: Geometry (GPKG), WKT (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1

    The measured area of the geometry in square metres.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 18

    • Scale: 6

    The OS NGD theme to which this feature belongs.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 40

    A single descriptive value intended for a quick understanding of what the feature represents.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    Name assigned to identify the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 254

    • OS Select+Build Filterable: Yes

    The language of name1, provided as a 3-digit ISO 639-2 code ('eng, 'cym', 'gla').

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    The alternative language name assigned to identify the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 254

    • OS Select+Build Filterable: Yes

    The language of name2, provided as a 3-digit ISO 639-2 code ('eng, 'cym', 'gla').

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    Set to the census / Government Statistical Service (GSS) Code for the boundary, for example, E10000014.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 10

    • OS Select+Build Filterable: Yes

    A single description value for boundary type.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    Identifier for the Parent Boundary

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 36

    • OS Select+Build Filterable: No

    Further classification indicating the Parent Boundary feature type.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    Further classification indicating the Parent Boundary.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    Name assigned to identify the Parent Boundary. If the name is defined in multiple languages, then each name shall be provided with an associated language qualifier. If the proper name is only defined in one language, then no language qualifier will be provided.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 254

    • OS Select+Build Filterable: No

    The language type associated with name1 for the Parent Boundary. The valid values are defined in the LanguageValue codelist.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    Name assigned to identify the Parent Boundary. If the name is defined in multiple languages, then each name shall be provided with an associated language qualifier. If the proper name is only defined in one language, then no language qualifier will be provided.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 254

    • OS Select+Build Filterable: No

    The language type associated with name2 for the Parent Boundary. The valid values are defined in the LanguageValue codelist.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    The inland area of the feature in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    The non-inland area in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    The total area in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    Data Schema Version: 1.0, 2.0

    Data Schema Version: 2.0

    1.0

    02 November 2022

    Ongoing

    Initial launch of the Alternate Address Related Component.

    Data Schema Version: 1.0, 2.0

    Data Schema Version: 1.0, 2.0

    Data Schema Version: 1.0, 2.0

    Data Schema Version: 1.0, 2.0

    Data Schema Version: 1.0, 2.0

    Data Schema Version: 1.0, 2.0

    Data Schema Version: 1.0, 2.0

    Data Schema Version: 1.0, 2.0

    Data Schema Version: 1.0, 2.0

    Data Schema Version: 1.0, 2.0

    Data Schema Version: 1.0, 2.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0

  • Data Schema Version: 1.0, 2.0

    Data Schema Version: 1.0, 2.0

    Data Schema Version: 1.0, 2.0

    Data Schema Version: 1.0, 2.0

    Data Schema Version: 1.0, 2.0

    Data Schema Version: 1.0, 2.0

    Data Schema Version: 1.0, 2.0

    Data Schema Version: 1.0, 2.0

    Ongoing

    Major version increment to align with concurrent major version increments made to four feature types in the GB Address and Islands Address Collections: Built Address, Historic Address, Non-Addressable Object, and Pre-Build Address. (Related components follow the versioning of the addressing feature types they are associated with.)

    1.0

    02 November 2022

    Ongoing

    Initial launch of the Postal Address Related Component.

    Postal Address Related Component

    • Until September 2025, Postal Address Related Component was the fourth related component in the OS NGD. It has been discontinued in the latest data schema version 3.0 of the Built Address, Historic Address, Non-Addressable Object and Pre-Build Address Feature Types in the GB Address and Islands Address Collections, which released in September 2025.

    • The Postal Address Related Component contained delivery point data from the Royal Mail Postcode Address File (PAF). This information is now available in the new Royal Mail Address Feature Type (which launched in September 2025), which can be found in the GB Address and Islands Address Collections.

    • The Postal Address Related Component is still provided against the older (maintenance) data schema versions 1.0 and 2.0 of the Built Address, Historic Address, Non-Addressable Object and Pre-Build Address Feature Types in the GB Address and Islands Address Collections. These data schema versions are available for customers to use, but they are now older and in maintenance mode. (Data schema version 3.0 is the latest and recommended data schema version to use for these feature types.)

    Temporal filtering

    Related component attributes

    udprn

    uprn

    featuretypeversiondate

    organisationname

    departmentname

    subbuildingname

    buildingname

    buildingnumber

    dependentthoroughfare

    thoroughfare

    doubledependentlocality

    dependentlocality

    posttown

    postcode

    postcodetype

    deliverypointsuffix

    welshdependentthoroughfare

    welshthoroughfare

    welshdoubledependentlocality

    welshdependentlocality

    welshposttown

    poboxnumber

    processdate

    source

    updatedate

    effectivestartdate

    effectiveenddate

    Data schema versioning
    Data schema version table
    Getting started with temporal filtering guide
    postcodetypevalue

    Data Schema Version: 1.1

    Data Schema Version: 1.1

    OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • Geometry Type: Polygon

    OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • Data Schema Version: 1.1

    OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • Data Schema Version: 1.1

    OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • Data Schema Version: 1.1

    OS Select+Build Filterable: Yes

  • Data Schema Version: 1.1

  • Data Schema Version: 1.1

    OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • Data Schema Version: 1.1

    OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • Data Schema Version: 1.1

    OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • Ongoing

    Minor version increment that removes the query and download filters from the Description attribute as this attribute supports only a single value.

    1.0

    29 September 2022

    27 July 2025

    Initial launch of the GLA Assembly Constituency Feature Type.

    Temporal filtering

    Feature type attributes

    Loading OS NGD CSV files into databases

    Comma-separated values (CSV) file format is universally supported for easy ingestion into all major database products. Before loading OS NGD data contained in CSV files into a database, it is necessary to create relevant tables. Data definition language (DDL) statements for PostgreSQL, SQL Server and Oracle can be accessed in our OS NGD Resources GitHub repository.

    For instructions on loading CSV files, see the Getting Started with CSV guide.

    osid

    toid

    versiondate

    versionavailablefromdate

    versionavailabletodate

    changetype

    geometry

    geometry_area

    theme

    description

    name1_text

    name1_language

    name2_text

    name2_language

    gsscode

    boundarytype

    boundaryparentreference_id

    boundaryparentreference_featuretype

    boundaryparentreference_classification

    boundaryparentreference_name1_text

    boundaryparentreference_name1_language

    boundaryparentreference_name2_text

    boundaryparentreference_name2_language

    landareahectares

    tidalareahectares

    totalareahectares

    Data schema versioning
    Data schema version table
    Getting started with temporal filtering guide
    changetypevalue
    themevalue
    glaassemblyconstituencydescriptionvalue
    languagevalue
    languagevalue
    boundarytypevalue
    parentfeaturetypevalue
    parentboundarydescriptionvalue
    languagevalue
    languagevalue

    Loading OS NGD CSV files into databases

    OS NGD Resources GitHub repository
    Getting Started with CSV

    Footbridge

  • Pedestrian Tunnel Or Subway

  • Underpass

  • Clapper Bridge

  • Lift Bridge

  • Swing Bridge

  • Canal Tunnel

  • A filter is required on the Road Track Or Path Feature Type on the Description attribute so that only fords, level crossings and pedestrian crossings appear in the data.

  • A filter is required on the Water Point Feature Type on the Description attribute so that only fords and tidal fords appear in the data.

  • Filters need to be set one at a time for the feature types that need to use them.

    Note: Only these four individual feature types are needed for this recipe – do not select all feature types from the OS GB Address, OS Structure Features, OS Transport Features and OS Water Features Collections.

    📖 Getting started with recipes guides

    🎯 Getting started with attribute filtering guide

    📚 Getting started with data packages guide

    🗺️ Guide for using QGIS to standardise data for identifying crossing points and bottlenecks in OS NGD data

    Why are filters needed in this recipe?

    Water Point
    Compound Structure Description Value Code List
    Compound Structure Description Value Code List
    Compound Structure Description Value Code List
    Compound Structure Description Value Code List
    Screenshot showing the tree view in the secondary navigation menu that opens when you create a recipe in OS Select+Build in the OS Data Hub. Three of the four feature types needed for the identifying crossing points and bottlenecks recipe are shown to have been selected in this screenshot: Compound Structure, Road Track Or Path, and Water Point; Non Addressable Object has also been selected, but isn't visible in the screenshot.
    Screenshot showing the tree view in the secondary navigation menu that opens when you create a recipe in OS Select+Build in the OS Data Hub. Three of the four feature types needed for the identifying crossing points and bottlenecks recipe are shown to have been selected in this screenshot: Compound Structure, Road Track Or Path, and Water Point; Non Addressable Object has also been selected, but isn't visible in the screenshot.
    Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build. The two rules filter options selected for the Non Addressable Object Feature Type are shown in this screenshot.
    Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build. The two rules filter options selected for the Non Addressable Object Feature Type are shown in this screenshot.
    Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build. The 12 rules filter options selected for the Compound Structure Feature Type are shown in this screenshot.
    Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build. The 12 rules filter options selected for the Compound Structure Feature Type are shown in this screenshot.
    Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build. The three rules filter options selected for the Road Track Or Path Feature Type are shown in this screenshot.
    Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build. The three rules filter options selected for the Road Track Or Path Feature Type are shown in this screenshot.
    Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build. The two rules filter options selected for the Water Point Feature Type are shown in this screenshot.
    Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build. The two rules filter options selected for the Water Point Feature Type are shown in this screenshot.
    Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.
    Screenshot showing the tree view in the secondary navigation menu that opens when you create a recipe in OS Select+Build in the OS Data Hub. The Compound Structure Feature Type has been selected in this screenshot and the Choose Schema Version drop-down menu is visible in the right-hand-side panel, which lets you select the data schema version you want to use for the feature type.
    Screenshot of the theme selection tree in OS Select+Build with the filter icon highlighted beside Non Addressable Object.
    Screenshot of the theme selection tree in OS Select+Build with the filter icon highlighted beside Road Track Or Path.
    Screenshot of the theme selection tree in OS Select+Build with the filter icon highlighted beside Water Point.
    Screenshot of the OS Select+Build Recipe details screen showing a summary of the identifying crossing points and bottlenecks recipe, including selected feature types and their data schema versions, plus all filters applied.
    Filter icon in OS Select+Build
    Filter icon in OS Select+Build
    Filter icon in OS Select+Build
    Filter icon in OS Select+Build
    Logo

    Electoral Division

    For voting purposes, a county is divided into electoral divisions. In Wales, the voting area is the unitary authority electoral division; in Scotland, it is the unitary authority ward; and in England, it is the unitary authority ward or unitary authority electoral division.

    Temporal filtering

    The earliest date on which you can request a one-off snapshot of a date in the past for data in this feature type is 29 September 2022.

    Any data temporally filtered earlier than the specified earliest date noted above for the data schema version may contain data inconsistencies.

    Feature type attributes

    The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

    Comma-separated values (CSV) file format is universally supported for easy ingestion into all major database products. Before loading OS NGD data contained in CSV files into a database, it is necessary to create relevant tables. Data definition language (DDL) statements for PostgreSQL, SQL Server and Oracle can be accessed in our .

    For instructions on loading CSV files, see the guide.

    osid

    Primary identifier for the feature. The OSID is a Globally Unique Identifier (GUID) and requires no centralised authority to ensure uniqueness. Note that the same OSID can occur in more than one feature type when a single feature is represented multiple times in the OS NGD.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 36

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Topographic identifier (TOID) of the feature, as published in the OS MasterMap suite of products.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 20

    • OS Select+Build Filterable: Yes

    Date when the version was last updated.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The date this version of the feature became the latest version.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The date this version of the feature was superseded by an update or ceased to exist.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The type of change that generated a new version of the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    Geometry for the feature.

    • Data Types: Geometry (GPKG), WKT (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The measured area of the geometry in square metres.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 18

    • Scale: 6

    The OS NGD theme to which this feature belongs.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 40

    A single descriptive value intended for a quick understanding of what the feature represents.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    Name assigned to identify the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 254

    • OS Select+Build Filterable: Yes

    The language of name1, provided as a 3-digit ISO 639-2 code ('eng, 'cym', 'gla').

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    The alternative language name assigned to identify the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 254

    • OS Select+Build Filterable: Yes

    The language of name2, provided as a 3-digit ISO 639-2 code ('eng, 'cym', 'gla').

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    Set to the census / Government Statistical Service (GSS) Code for the boundary, for example, E10000014.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 10

    • OS Select+Build Filterable: Yes

    A single description value for boundary type.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    Identifier for the Parent Boundary.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 36

    • OS Select+Build Filterable: No

    Further classification indicating the Parent Boundary feature type.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    Further classification indicating the Parent Boundary.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    Name assigned to identify the Parent Boundary. If the name is defined in multiple languages, then each name shall be provided with an associated language qualifier. If the proper name is only defined in one language, then no language qualifier will be provided.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 254

    • OS Select+Build Filterable: No

    The language type associated with name1 for the Parent Boundary. The valid values are defined in the LanguageValue codelist.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    Name assigned to identify the Parent Boundary. If the name is defined in multiple languages, then each name shall be provided with an associated language qualifier. If the proper name is only defined in one language, then no language qualifier will be provided.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 254

    • OS Select+Build Filterable: No

    The language type associated with name2 for the Parent Boundary. The valid values are defined in the LanguageValue codelist.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    Identifier for the Parent Boundary.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 36

    • OS Select+Build Filterable: No

    Further classification indicating the Parent Boundary feature type.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 50

    Further classification indicating the Parent Boundary.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 50

    Name assigned to identify the Parent Boundary. If the name is defined in multiple languages, then each name shall be provided with an associated language qualifier. If the proper name is only defined in one language, then no language qualifier will be provided.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 254

    • OS Select+Build Filterable: No

    The language type associated with name1 for the Parent Boundary. The valid values are defined in the LanguageValue codelist.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    Name assigned to identify the Parent Boundary. If the name is defined in multiple languages, then each name shall be provided with an associated language qualifier. If the proper name is only defined in one language, then no language qualifier will be provided.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 254

    • OS Select+Build Filterable: No

    The language type associated with name2 for the Parent Boundary. The valid values are defined in the LanguageValue codelist.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    The inland area of the feature in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    The non-inland area in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    The total area in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    Boolean set to true if the feature applies to portions of local government or parliamentary constituency areas which are separated from the main area, being completely surrounded by other local government or parliamentary constituency areas and not connected by direct access on the ground; otherwise, Boolean set to false.

    • Data Types: Integer (GPKG), String (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Street Address

    The Street Address Feature Type provides street address information for any road, footpath, cycleway, byway, or bridleway that has been uniquely identified by the local Highway Authority, or Street Naming and Numbering authority and provides access to an address.

    The earliest date on which you can request a one-off snapshot of a date in the past for data in this feature type is 02 November 2022.

    Any data temporally filtered earlier than the specified earliest date noted above for the data schema version may contain data inconsistencies.

    The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

    The Unique Street Reference Number (USRN), a unique and persistent identifier of a Street which is assigned by the Roads or Highway Authority.

    • Data Types: Integer (GPKG), Integer (CSV)

    Street Address

    The Street Address Feature Type provides street address information for any road, footpath, cycleway, byway, or bridleway that has been uniquely identified by the local Highway Authority, or Street Naming and Numbering authority and provides access to an address.

    The earliest date on which you can request a one-off snapshot of a date in the past for data in this feature type is 02 November 2022.

    Any data temporally filtered earlier than the specified earliest date noted above for the data schema version may contain data inconsistencies.

    The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

    The Unique Street Reference Number (USRN), a unique and persistent identifier of a Street which is assigned by the Roads or Highway Authority.

    • Data Types: Integer (GPKG), Integer (CSV)

    Data Schema Version: 1.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Geometry Type: MultiPolygon

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0

  • Data Schema Version: 1.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Data Schema Version: 1.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Data Schema Version: 1.0

    OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0

  • Data Schema Version: 1.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Data Schema Version: 1.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Data Schema Version: 1.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Data Schema Version: 1.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Data Schema Version: 1.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Data Schema Version: 1.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • toid

    versiondate

    versionavailablefromdate

    versionavailabletodate

    changetype

    geometry

    geometry_area

    theme

    description

    name1_text

    name1_language

    name2_text

    name2_language

    gsscode

    boundarytype

    boundaryparentreference1_id

    boundaryparentreference1_featuretype

    boundaryparentreference1_classification

    boundaryparentreference1_name1_text

    boundaryparentreference1_name1_language

    boundaryparentreference1_name2_text

    boundaryparentreference1_name2_language

    boundaryparentreference2_id

    boundaryparentreference2_featuretype

    boundaryparentreference2_classification

    boundaryparentreference2_name1_text

    boundaryparentreference2_name1_language

    boundaryparentreference2_name2_text

    boundaryparentreference2_name2_language

    landareahectares

    tidalareahectares

    totalareahectares

    hasdetachedpart

    Loading OS NGD CSV files into databases

    changetypevalue
    themevalue
    electoraldivisiondescriptionvalue
    languagevalue
    languagevalue
    boundarytypevalue
    parentfeaturetypevalue
    parentboundarydescriptionvalue
    languagevalue
    languagevalue
    parentfeaturetypevalue
    parentboundarydescriptionvalue
    languagevalue
    languagevalue
    OS NGD Resources GitHub repository
    Getting Started with CSV

    Nullable: false

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0

  • Date when the version was last updated.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The date this version of the feature became the latest version.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The date this version of the feature was superseded by an update or ceased to exist.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The type of change that generated a new version of the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: changetypevalue

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The OS NGD theme to which this feature belongs.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: themevalue

    • Max Length: 40

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    A single descriptive value intended for a quick understanding of what the feature represents.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: streetdescriptionvalue

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Description of the street record type, for example, whether the Street has an official designated street name.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressstreettypevalue

    • Max Length: 33

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    A code for the primary street classification, for example, denoting it to be 'open to all vehicles'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: streetclassificationvalue

    • Max Length: 26

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Description of the current state of the Street, indicating which point the street record is at within its lifecycle.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: streetstatevalue

    • Max Length: 18

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Date at which the Street achieved its current state in the world, as referenced by the 'operationalState' attribute.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Name, number or descriptor that identifies the nearest accessable Street that an Address is located on or close to.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 100

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Name of the area or geographical identifier within a town, settlement, village or hamlet that an address is located within. For example, a locality may be a suburb, housing estate or commercial estate.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0

    Name of the settlement that the Street is located within. A settlement can be a City, Town, Village, Hamlet or Parish.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0

    Name of the Administrative Unit that the Address is located within.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 35

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Name of the geographical territory that the Address is located within, where a geographical territory represents either a devolved country or an island nation.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: countryvalue

    • Max Length: 16

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0

    Name, number or descriptor that identifies the nearest accessable street that an Address is located on or close to, defined in either Welsh (cym) or Gaelic / Scottish Gaelic (gla).

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Name of the area or geographical identifier within a town, settlement, village or hamlet that an address is located within, defined in either Welsh (cym) or Gaelic / Scottish Gaelic (gla). For example, a locality may be a suburb, housing estate or commercial estate.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0

    The name of the settlement that the address is located within, defined in either Welsh (cym) or Gaelic / Scottish Gaelic (gla). A settlement can be a City, Town, Village, Hamlet or Parish.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0

    Name of the Administrative Unit that the Address is located within, defined in either Welsh (cym) or Gaelic / Scottish Gaelic (gla).

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0

    ISO 3166-3 Language Code for Welsh or Gaelic / Scottish Gaelic.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: languagevalue

    • Max Length: 3

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Alphanumeric code which identifies the Street Naming and Numbering Authority or the Local Highway Authority

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 4

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0

    Name of the responsible Street Naming and Numbering Authority or Local Highways Authority

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0

    Description indicating the type of surface finish on the Street, for example, 'Metalled'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: streetsurfacevalue

    • Max Length: 10

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    X coordinate in metres for the position of the start point of the street defined in British National Grid (EPSG::27700) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 8

    • Scale: 2

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Y coordinate in metres for the position of the start point of the street defined in British National Grid (EPSG::27700) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 2

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    X coordinate in metres for the position of the end point of the street defined in British National Grid (EPSG::27700) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 8

    • Scale: 2

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Y coordinate in metres for the position of the end point of the street defined in British National Grid (EPSG::27700) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 2

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Value defining the Latitude of the position of the start point of the street defined in accordance with the ETRS89 (EPSG::4258) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 7

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Value defining the Longitude of the position of the start point of the street defined in accordance with the ETRS89 (EPSG::4258) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 7

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Value defining the Latitude of the position of the end point of the street defined in accordance with the ETRS89 (EPSG::4258) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 7

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Value defining the Longitude of the position of the end point of the street defined in accordance with the ETRS89 (EPSG::4258) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 7

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Geometry for the feature.

    • Data Types: Geometry (GPKG), WKT (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    • Geometry Type: MultiPoint

    The tolerance of the Start and End Location coordinates in metres.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The date on which this record was inserted into the Local Authority database.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The date on which the record ceased to exist

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Temporal filtering

    Feature type attributes

    Loading OS NGD CSV files into databases

    Comma-separated values (CSV) file format is universally supported for easy ingestion into all major database products. Before loading OS NGD data contained in CSV files into a database, it is necessary to create relevant tables. Data definition language (DDL) statements for PostgreSQL, SQL Server and Oracle can be accessed in our OS NGD Resources GitHub repository.

    For instructions on loading CSV files, see the Getting Started with CSV guide.

    usrn

    versiondate

    versionavailablefromdate

    versionavailabletodate

    changetype

    theme

    description

    streettype

    classification

    operationalstate

    operationalstatedate

    streetname

    locality

    townname

    administrativearea

    country

    alternatelanguagestreetname

    alternatelanguagelocality

    alternatelanguagetownname

    alternatelanguageadministrativearea

    alternatelanguage

    snnauthoritycode

    snnauthoritydescription

    surfacematerial

    starteasting

    startnorthing

    endeasting

    endnorthing

    startlatitude

    startlongitude

    endlatitude

    endlongitude

    geometry

    streettolerance

    effectivestartdate

    effectiveenddate

    Nullable: false

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0

  • Date when the version was last updated.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The date this version of the feature became the latest version.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The date this version of the feature was superseded by an update or ceased to exist.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The type of change that generated a new version of the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: changetypevalue

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The OS NGD theme to which this feature belongs.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: themevalue

    • Max Length: 40

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    A single descriptive value intended for a quick understanding of what the feature represents.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: streetdescriptionvalue

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Description of the street record type, for example, whether the Street has an official designated street name.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressstreettypevalue

    • Max Length: 33

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    A code for the primary street classification, for example, denoting it to be 'open to all vehicles'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: streetclassificationvalue

    • Max Length: 26

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Description of the current state of the Street, indicating which point the street record is at within its lifecycle.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: streetstatevalue

    • Max Length: 18

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Date at which the Street achieved its current state in the world, as referenced by the 'operationalState' attribute.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Name, number or descriptor that identifies the nearest accessable Street that an Address is located on or close to.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 100

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Name of the area or geographical identifier within a town, settlement, village or hamlet that an address is located within. For example, a locality may be a suburb, housing estate or commercial estate.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0

    Name of the settlement that the Street is located within. A settlement can be a City, Town, Village, Hamlet or Parish.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0

    Name of the Administrative Unit that the Address is located within.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 35

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Name of the geographical territory that the Address is located within, where a geographical territory represents either a devolved country or an island nation.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: countryvalue

    • Max Length: 16

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0

    Name, number or descriptor that identifies the nearest accessable street that an Address is located on or close to, defined in either Welsh (cym) or Gaelic / Scottish Gaelic (gla).

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Name of the area or geographical identifier within a town, settlement, village or hamlet that an address is located within, defined in either Welsh (cym) or Gaelic / Scottish Gaelic (gla). For example, a locality may be a suburb, housing estate or commercial estate.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0

    The name of the settlement that the address is located within, defined in either Welsh (cym) or Gaelic / Scottish Gaelic (gla). A settlement can be a City, Town, Village, Hamlet or Parish.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0

    Name of the Administrative Unit that the Address is located within, defined in either Welsh (cym) or Gaelic / Scottish Gaelic (gla).

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0

    ISO 3166-3 Language Code for Welsh or Gaelic / Scottish Gaelic.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: languagevalue

    • Max Length: 3

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Alphanumeric code which identifies the Street Naming and Numbering Authority or the Local Highway Authority

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 4

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0

    Name of the responsible Street Naming and Numbering Authority or Local Highways Authority

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0

    Description indicating the type of surface finish on the Street, for example, 'Metalled'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: streetsurfacevalue

    • Max Length: 10

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    X coordinate in metres for the position of the start point of the street defined in British National Grid (EPSG::27700) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 8

    • Scale: 2

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Y coordinate in metres for the position of the start point of the street defined in British National Grid (EPSG::27700) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 9

    • Scale: 2

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    X coordinate in metres for the position of the end point of the street defined in British National Grid (EPSG::27700) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 8

    • Scale: 2

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Y coordinate in metres for the position of the end point of the street defined in British National Grid (EPSG::27700) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 9

    • Scale: 2

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Value defining the Latitude of the position of the start point of the street defined in accordance with the ETRS89 (EPSG::4258) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 7

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Value defining the Longitude of the position of the start point of the street defined in accordance with the ETRS89 (EPSG::4258) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 7

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Value defining the Latitude of the position of the end point of the street defined in accordance with the ETRS89 (EPSG::4258) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 7

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Value defining the Longitude of the position of the end point of the street defined in accordance with the ETRS89 (EPSG::4258) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 7

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Geometry for the feature.

    • Data Types: Geometry (GPKG), WKT (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    • Geometry Type: MultiPoint

    The tolerance of the Start and End Location coordinates in metres.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The date on which this record was inserted into the Local Authority database.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The date on which the record ceased to exist

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Temporal filtering

    Feature type attributes

    Loading OS NGD CSV files into databases

    Comma-separated values (CSV) file format is universally supported for easy ingestion into all major database products. Before loading OS NGD data contained in CSV files into a database, it is necessary to create relevant tables. Data definition language (DDL) statements for PostgreSQL, SQL Server and Oracle can be accessed in our OS NGD Resources GitHub repository.

    For instructions on loading CSV files, see the Getting Started with CSV guide.

    usrn

    versiondate

    versionavailablefromdate

    versionavailabletodate

    changetype

    theme

    description

    streettype

    classification

    operationalstate

    operationalstatedate

    streetname

    locality

    townname

    administrativearea

    country

    alternatelanguagestreetname

    alternatelanguagelocality

    alternatelanguagetownname

    alternatelanguageadministrativearea

    alternatelanguage

    snnauthoritycode

    snnauthoritydescription

    surfacematerial

    starteasting

    startnorthing

    endeasting

    endnorthing

    startlatitude

    startlongitude

    endlatitude

    endlongitude

    geometry

    streettolerance

    effectivestartdate

    effectiveenddate

    Resolved Data Issues

    This page lists resolved data issues in relation to the OS NGD themes, collections and feature types.

    Please see the page for details about current live data issues issues.

    Any live interruptions to the availability of OS NGD API – Features and OS NGD API – Tiles will be documented on the .

    Generic OS NGD resolved data issues

    No current resolved data issues to note that impact multiple OS NGD themes.

    OS NGD Address Theme resolved data issues

    No current resolved data issues to note for this theme.

    OS NGD Administrative and Statistical Units Theme resolved data issues

    Data Issue Name
    Original Description for Data Issue
    Resolution Date
    Resolution Message

    GB Postcode Unit Point ward codes not updating

    No current resolved data issues to note for this theme.

    Data Issue Name
    Original Description for Data Issue
    Resolution Date
    Resolution Message

    No current resolved data issues to note for this theme.

    No current resolved data issues to note for this theme.

    No current resolved data issues to note for this theme.

    Data Issue Name
    Original Description for Data Issue
    Resolution Date
    Resolution Message

    No current resolved data issues to note for this theme.

    Resolved data issues older than six months are included in the tabs below under each OS NGD theme.

    Snapshots of OS NGD data retrieved through temporal filtering in OS Select+Build may include issues with the data that were present at the time but have since been resolved. The following tabs contain details of resolved data issues more than six months old, arranged by the OS NGD themes they apply to.

    For more information on temporal filtering within OS Select+Build, please see the .

    Data Issue Name
    Original Description for Data Issue
    Resolution Date
    Resolution Message

    Parish Or Community

    Civil parishes in England and community wards in Scotland. Unitary authorities may be divided into civil parishes or communities (except in Scotland).

    Temporal filtering

    The earliest date on which you can request a one-off snapshot of a date in the past for data in this feature type is 29 September 2022.

    Any data temporally filtered earlier than the specified earliest date noted above for the data schema version may contain data inconsistencies.

    Feature type attributes

    The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

    Comma-separated values (CSV) file format is universally supported for easy ingestion into all major database products. Before loading OS NGD data contained in CSV files into a database, it is necessary to create relevant tables. Data definition language (DDL) statements for PostgreSQL, SQL Server and Oracle can be accessed in our .

    For instructions on loading CSV files, see the guide.

    osid

    Primary identifier for the feature. The OSID is a Globally Unique Identifier (GUID) and requires no centralised authority to ensure uniqueness. Note that the same OSID can occur in more than one feature type when a single feature is represented multiple times in the OS NGD.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 36

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Topographic identifier (TOID) of the feature, as published in the OS MasterMap suite of products.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 20

    • OS Select+Build Filterable: Yes

    Date when the version was last updated.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The date this version of the feature became the latest version.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The date this version of the feature was superseded by an update or ceased to exist.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The type of change that generated a new version of the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    Geometry for the feature.

    • Data Types: Geometry (GPKG), WKT (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The measured area of the geometry in square metres.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 18

    • Scale: 6

    The OS NGD theme to which this feature belongs.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 40

    A single descriptive value intended for a quick understanding of what the feature represents.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    Name assigned to identify the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 254

    • OS Select+Build Filterable: Yes

    The language of name1, provided as a 3-digit ISO 639-2 code ('eng, 'cym', 'gla').

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    The alternative language name assigned to identify the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 254

    • OS Select+Build Filterable: Yes

    The language of name2, provided as a 3-digit ISO 639-2 code ('eng, 'cym', 'gla').

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    Set to the census / Government Statistical Service (GSS) Code for the boundary, for example, E10000014.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 10

    • OS Select+Build Filterable: Yes

    A single description value for boundary type.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    Identifier for the Parent Boundary.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 36

    • OS Select+Build Filterable: No

    Further classification indicating the Parent Boundary feature type.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    Further classification indicating the Parent Boundary.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    Name assigned to identify the Parent Boundary. If the name is defined in multiple languages, then each name shall be provided with an associated language qualifier. If the proper name is only defined in one language, then no language qualifier will be provided.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 254

    • OS Select+Build Filterable: No

    The language type associated with name1 for the Parent Boundary. The valid values are defined in the LanguageValue codelist.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    Name assigned to identify the Parent Boundary. If the name is defined in multiple languages, then each name shall be provided with an associated language qualifier. If the proper name is only defined in one language, then no language qualifier will be provided.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 254

    • OS Select+Build Filterable: No

    The language type associated with name2 for the Parent Boundary. The valid values are defined in the LanguageValue codelist.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    Identifier for the Parent Boundary.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 36

    • OS Select+Build Filterable: No

    Further classification indicating the Parent Boundary feature type.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 50

    Further classification indicating the Parent Boundary.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 50

    Name assigned to identify the Parent Boundary. If the name is defined in multiple languages, then each name shall be provided with an associated language qualifier. If the proper name is only defined in one language, then no language qualifier will be provided.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 254

    • OS Select+Build Filterable: No

    The language type associated with name1 for the Parent Boundary. The valid values are defined in the LanguageValue codelist.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    Name assigned to identify the Parent Boundary. If the name is defined in multiple languages, then each name shall be provided with an associated language qualifier. If the proper name is only defined in one language, then no language qualifier will be provided.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 254

    • OS Select+Build Filterable: No

    The language type associated with name2 for the Parent Boundary. The valid values are defined in the LanguageValue codelist.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    The inland area of the feature in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    The non-inland area in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    The total area in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    Boolean set to true if the feature is an area where the limits of the parishes concerned have not been determined and the area itself is common to (or belongs to) two or more parishes; otherwise, Boolean set to false.

    • Data Types: Integer (GPKG), String (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Boolean set to true if the feature applies to portions of local government or parliamentary constituency areas which are separated from the main area, being completely surrounded by other local government or parliamentary constituency areas and not connected by direct access on the ground; otherwise, Boolean set to false.

    • Data Types: Integer (GPKG), String (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    What's New?

    As we release new data and access enhancements for the OS NGD, we will update this page to provide you with a high-level summary of what's launched.

    Address – Bringing richer Royal Mail address data, stronger UPRN connections and deeper property insight into the OS NGD

    • More Royal Mail data, delivered through OS: The enhancement expands the with new datasets, bringing customers closer to a complete view of Royal Mail address intelligence through a single OS product.

    • Introducing Not Yet Built (NYB) addresses: Gain visibility of addresses known to Royal Mail before they become live delivery points, helping organisations plan for new developments, customer onboarding, service delivery and infrastructure investment.

    Data Schema Version: 1.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Geometry Type: MultiPolygon

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0

  • Data Schema Version: 1.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Data Schema Version: 1.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Data Schema Version: 1.0

    OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0

  • Data Schema Version: 1.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Data Schema Version: 1.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Data Schema Version: 1.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Data Schema Version: 1.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Data Schema Version: 1.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Data Schema Version: 1.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • toid

    versiondate

    versionavailablefromdate

    versionavailabletodate

    changetype

    geometry

    geometry_area

    theme

    description

    name1_text

    name1_language

    name2_text

    name2_language

    gsscode

    boundarytype

    boundaryparentreference1_id

    boundaryparentreference1_featuretype

    boundaryparentreference1_classification

    boundaryparentreference1_name1_text

    boundaryparentreference1_name1_language

    boundaryparentreference1_name2_text

    boundaryparentreference1_name2_language

    boundaryparentreference2_id

    boundaryparentreference2_featuretype

    boundaryparentreference2_classification

    boundaryparentreference2_name1_text

    boundaryparentreference2_name1_language

    boundaryparentreference2_name2_text

    boundaryparentreference2_name2_language

    landareahectares

    tidalareahectares

    totalareahectares

    hassharedarea

    hasdetachedpart

    Loading OS NGD CSV files into databases

    changetypevalue
    themevalue
    parishorcommunitydescriptionvalue
    languagevalue
    languagevalue
    boundarytypevalue
    parentfeaturetypevalue
    parentboundarydescriptionvalue
    languagevalue
    languagevalue
    parentfeaturetypevalue
    parentboundarydescriptionvalue
    languagevalue
    languagevalue
    OS NGD Resources GitHub repository
    Getting Started with CSV

    Missing records in Street to Path Link cross reference table

    95 Path Links with a Match Status of 'Matched' or 'Matched With Attribute Discrepancy' do not appear in trn_ntwk_street_pathlinkref as expected.

    17/08/2026

    This issue was resolved on 17 August 2026. Customers who take monthly updates will see this fix in the next update on 01 September 2026.

    Street to Road Link and Street to Path Link reference tables refer to non-existent features

    59 records in the Street to Road Link reference table and 16 records in the Street to Path Link reference table refer to Road Links / Path Links features which no longer exist. This issue is currently being investigated.

    24/07/2026

    This issue was resolved on 24 July 2026. Customers who take monthly updates will see this fix in the next update on 01 August 2026.

    Superfluous Road and Path Nodes

    83 superfluous Road Nodes and 6 Path Nodes are unexpectedly present in OS NGD Transport Networks. These nodes are not referenced by any existing links. This issue is currently being investigated.

    24/07/2026

    This issue was resolved on 24 July 2026. Customers who take monthly updates will see this fix in the next update on 01 August 2026.

    Restriction timeinterval exceeding schema maximum length

    1 Restriction feature (ab7bb3b3-a9e3-4604-85cc-68e3a2bec911) where the value in timeinterval exceeds the maximum length for the attribute (254 characters). This issue is currently being investigated.

    07/07/2026

    This issue was resolved on 07 July 2026. Customers who take monthly updates will see this fix in the next update on 01 August 2026.

    Highway Dedication to Network Feature cross reference table refers to non-existent features.

    20 records in the Highway Dedication to Network Feature cross reference table reference Road Link (data schema versions 2.0, 3.0, 4.0 and 5.0) features which do not exist. 114 records reference Path Link (data schema versions 1.0, 2.0, 3.0) features which do not exist and 16 records reference Street (data schema version 1.0) features which do not exist. This issue is currently being investigated.

    07/07/2026

    This issue was resolved on 07 July 2026. Customers who take monthly updates will see this fix in the next update on 01 August 2026.

    Referencing errors in the Road and Path Network

    8 Road features (data schema version 1.0) reference non-existent Road Link (data schema versions 1.0, 2.0, 3.0, 4.0 and 5.0) features.

    4 Path features (data schema version 1.0) reference non-existent Path Link (data schema versions 1.0, 2.0 and 3.0) features.

    07/07/2026

    This issue was resolved on 07 July 2026. Customers who take monthly updates will see this fix in the next update on 01 August 2026.

    Restriction referencing errors

    1 Restriction feature (data schema version 1.0) references a non-existent Road Link (data schema versions 2.0, 3.0, 4.0 and 5.0) features. This issue is currently being investigated.

    07/07/2026

    This issue was resolved on 07 July 2026. Customers who take monthly updates will see this fix in the next update on 01 August 2026.

    Streets data layers missing a small number of features

    A small number of features in the following feature types are missing when compared to the comparable tables in OS MasterMap Highways Network: Maintenance (data schema version 1.0), Reinstatement (data schema version 1.0), Highway Dedication (data schema version 1.0), Street (data schema version 1.0).

    10/05/2026

    This issue was resolved on 10 May 2026. Customers who take monthly updates will see this fix in the next update on 01 June 2026.

    We are currently deploying improvements to the Building Height data available on OS NGD Building Part (data schema v1.0 and v2.0) until 24 February 2025. During this period, daily updates to the Building Part Feature Type, such as changes captured by surveyors, will be temporarily paused. These changes will be reflected in the product data after the completion of the improvements.

    Consequently, users may observe anomalies in the consistency of the topological surface when utilising various OS NGD 'Feature' Collections (such as OS NGD Land Features). These anomalies will manifest as holes or overlaps where the Building Part feature has not been updated concurrently with the surrounding features. This impact will also be visible in OS NGD API – Features and OS NGD API – Tiles.

    Please note that we advise against using counts from the OS NGD Building Part Feature Type with a temporal filter set between 02 February 2025 and 24 February 2025 as the counts may not be accurate due to the impact on a small number of topographic features.

    24/02/2025

    The improvements were completed by 24/02/2025 as planned and Daily Updates resumed as normal for impacted feature types.

    Please note that we advise against using counts from the OS NGD Building Part Feature Type with a temporal filter set between 02 February 2025 and 24 February 2025 as the counts may not be accurate due to the impact of the improvement work on a small number of topographic features.

    3D geometry missing in GeoPackage format for some feature types in the OS NGD Transport Network and Water Network Collections

    In the OS NGD Transport Network Collection and OS NGD Water Network Collection, there are multiple feature types that contain 3D geometry. We are aware of an issue where 3D geometry is not being supplied in the GeoPackage format. This issue impacts the following feature types: Connecting Link, Connecting Node, Ferry Link, Ferry Node, Path Link, Path Node, Road Link, Road Node, Water Link and Water Node. Customers taking CSV format will not be affected.

    26/11/2024

    This issue was resolved on 26 November 2024. To receive updated data:

    • Customers who have only ordered once: Customers will need to re-order to receive the corrected data.

    • Monthly Update Customers: 01 December monthly updates with corrected data will be supplied as normal.

    • Annual Update Customers: 01 January annual updates with corrected data will be supplied as normal.

    Topographic features missing from four feature types

    From 26 September 2024 to 31 October 2024, an issue affected the following four OS NGD feature types, causing features to be missing from the data:

    • OS NGD Building Part Feature Type: ~80 000 features are missing from data schema v2.0 compared to data schema v1.0.

    • OS NGD Land Feature Type: ~38 000 features are missing from data schema v3.0 compared to data schema v2.0.

    • OS NGD Water and OS NGD Structure Feature Types: ~100 features are missing in total across both feature types from data schema v3.0 compared to data schema v2.0.

    For example, where an affected Building feature should be visible, a blank area will instead be seen, creating a ‘gap’:

    31/10/2024

    This issue was resolved on 31 October 2024. Any data ordered or provided after this date will include the fixed data.

    Please note, we advise against using counts from the four aforementioned affected OS NGD feature type datasets when taking historic snapshots of data between 26 September 2024 and 31 October 2024 as the counts may not be accurate due to the missing topographic features.

    Data Issue Name
    Original Description for Data Issue
    Data Issue Resolution Date
    Resolution Message

    Duplicate rows in the Postal Address Related Component

    We are aware of an issue with daily Change‑Only Update (COU) supplies, resulting in a small number of duplicated rows in the Postal Address Related Component.

    This issue only affects customers with orders containing OS NGD Address feature types data schema versions 1.0 or 2.0 who received a daily supply between 11 and 18 February.

    If you believe you are affected by this issue, please .

    04/03/2026

    This issue was resolved on 04 March 2026.

    Small numbers of UPRNs appearing across lifecycle feature types in COUs

    We are aware of an issue affecting the OS NGD Address Theme where a small number of Unique Property Reference Numbers (UPRNs; approximately 500 out of 43 million) are appearing in more than one lifecycle feature type (i.e. present in both the Built Address Feature Type and the Pre‑Build Address Feature Type) within Change‑Only Updates (COUs).

    Data Issue Name
    Original Description for Data Issue
    Resolution Date
    Resolution Message

    Three missing parishes from the Parish Or Community Feature Type

    The Margaret March, Tollard Royal and Marlow Bottom Civil Parish (CP) within the Parish Or Community Feature Type (data schema version 1.0) are missing from the May 2025 release of data.

    This issue is currently being investigated and we are working to fix it for a future release.

    October 2025

    The three missing parishes were restored to the Parish Or Community Feature Type in the October 2025 release of data for the OS Boundaries Collection.

    Data Issue Name
    Original Description for Data Issue
    Resolution Date
    Resolution Message

    Intertidal areas beneath Travelling Cranes and Supported Conveyors not present

    Intertidal areas beneath Travelling Cranes and Supported Conveyors are not currently present and will be added in a future data improvement. This applies to data schema version 3.2 of the Land Feature Type.

    September 2025

    This issue was resolved in September 2025.

    Intertidal areas beneath elevated structures situated over intertidal islands not present

    Intertidal areas beneath elevated structures situated over intertidal islands are not currently present and will be added in a future data improvement. This applies to data schema version 3.2 of the Land Feature Type.

    September 2025

    Data Issue Name
    Original Description for Data Issue
    Data Issue Resolution Date
    Resolution Message

    Uppercase and lowercase variations of two description values in Site Feature Type data schema v1.2

    Two in data schema v1.2 of the contain duplicates with uppercase and lowercase variations.

    25 September 2024

    Data schema v1.0 of Site was launched incorrectly with two description values that did not align with OS casing standards, and on 25 September 2024 the data and related code list were updated to fix this issue.

    The two affected values are:

    • Education Support Site

    • Public Waste Disposal Site

    The OS NGD access services of OS NGD API – Features and OS Select+Build validate against the data schema, meaning both versions of the description values must be retained to facilitate filtering.

    The lowercase values (i.e. Education Support site and Public Waste Disposal site) should be used to filter and retrieve historical features (before 25/09/24), while the uppercase values (i.e. Education Support Site and Public Waste Disposal

    Data Issue Name
    Original Description for Data Issue
    Resolution Date
    Resolution Message

    Field Boundary data quality

    At the time of launch of the Field Boundary Feature Type (March 2024; data schema version 1.0), areas of Great Britain were still to be quality checked and will be improved as part of OS’s continuous quality review programme when updated imagery is available. Most of the known data quality errors are either in Moorland areas or where imagery was captured earlier in the year and vegetated features are ‘leaf-off’. Data issue identification date: 27/03/2024.

    01/03/2026

    This issue was resolved by 01/03/2026 through improvements made to the automated method used to identify field boundary data. More information is available from the .

    Some underground Structure features are missing from the Habitat Coverage cross reference table

    Three underground Structure features with an OS Land Cover Tier B attribute of ‘Coniferous Trees’, ‘Non-Coniferous Trees’, ‘Scattered Coniferous Trees’ or ‘Scattered Non-Coniferous Trees’ are missing from the corresponding Habitat Coverage Reference cross reference table. This issue impacts the Land Feature Type. Data issue identification date: 15/04/2024.

    03/11/2025

    Data Issue Name
    Original Description for Data Issue
    Resolution Date
    Resolution Message

    Street Light features refer to non-existent links

    7 Street Light features refer to a Road Link (data schema versions 2.0, 3.0, 4.0 and 5.0) that does not currently exist. This issue is currently being investigated.

    14/02/2026

    This issue was resolved on 14/02/2026.

    Road Links with unexpected 0 values for pavement width attributes

    187 Road Link features (data schema versions 2.0, 3.0, 4.0 and 5.0) where we would expect their Presence of Pavement Minimum Width M and Presence of Pavement Average Width M attributes to be populated have a value of 0 for these attributes. This issue is currently being investigated.

    Data Issue Name
    Original Description for Data Issue
    Resolution Date
    Resolution Message

    Incorrect 0m width values for Water Links

    There are 190 Water Link features (data schema version 2.0) that have Width Average, Width Minimum and Width Maximum attribute values of 0m. There are an additional 385 Water Link features (data schema version 2.0) that have a Width Minimum attribute value of 0m.

    28/01/2026

    This issue was resolved on 28 January 2026. Customers who take monthly updates will see this fix in the next update on 01 February 2026.

    Unexpectedly null Level of Detail values for Water Links

    7 Water Link features (data schema version 1.0) incorrectly have a null Level of Detail attribute value. All Water Links should have this value populated. This issue is currently being investigated.

    The Data Entity Catalogue Postcode Value Code List values of 'Ward' have not been updated with the latest Government Statistical Service (GSS) ward code in which the GB Postcode Unit Point features (data schema version 1.1) are notionally positioned.

    A fix has been implemented and should be present for the next release of data for the OS GB Postcodes Collection, available from 19 October 2026. This will result in approximately 116 000 changes to Ward references. Issue first reported: 20/08/2026

    19/10/2026

    This issue was resolved on 19 October 2026 following the October 2026 release of data for the OS GB Postcodes Collection. This fix resulted in approximately 116 000 changes to Ward references.

    Historic European Region Feature Type

    This feature type (data schema version 1.0) contains updates made to the boundaries post 01 April 2021 (when the feature type was frozen in the Boundary-Line product). This means that there will be differences between the boundaries accessed via our OS OpenData pages and those accessed via OS NGD.

    Update on 02/06/2026: A fix has been implemented and should be present for the October 2026 release of data for the OS Boundaries Collection. Issue first reported: 08/07/2024

    01/10/2026

    This issue was resolved on 01 October 2026 following the October 2026 release of data for the OS Boundaries Collection.

    Cross Reference Feature attribute values not as expected for Retail Area Aggregated, Retail Area Major and Retail Area Minor Feature Types

    The Cross Reference Feature attribute used by the Related Entity Related Component for Retail Area Aggregated, Retail Area Major and Retail Area Minor features (data schema version 1.0 for all) only has published 'Built Address' values; there are no 'Grid 100m' or 'Grid 1km' values available for this attribute. Issue first reported: 26/03/2026

    01/10/2026

    This issue was resolved on 01 October 2026 following the October 2026 release of data for the OS Functional Areas Collection.

    County Electoral Division GSS codes missing

    Electoral Division features (data schema version 1.0) with a description of ‘Country Electoral Division’ do not have their Government Statistical Service (GSS) codes assigned. Issue first reported: 24/06/2026

    01/10/2026

    This issue was resolved on 01 October 2026 following the October 2026 release of data for the OS Boundaries Collection.

    Regional Authority GSS Codes referencing GSS Codes that do not yet exist.

    Due to the currency of the Named Point Feature Type in the OS NGD Geographical Names Theme being daily, from 14/09/2026 there will be approximately 126 000 features referencing Government Statistical Service (GSS) codes that do not currently exist. Once 'boundaries' found in the OS NGD Administrative and Statistical Units Theme are updated at the start of October 2026, the regional authorities will be updated and will show as expected. Issue first reported: 14/09/2026

    01/10/2026

    This issue was resolved on 01 October 2026 following the October 2026 release of data for the OS Boundaries Collection.

    Missing records in Street to Road Link cross reference table

    There are a small number of Road Links with a Match Status of 'Matched' or 'Matched With Attribute Discrepancy' which do not appear in trn_ntwk_street_rdlinkref as expected.

    08/09/2026

    This issue was resolved on 08 September 2026. Customers who take monthly updates will see this fix in the next update on 01 October 2026.

    Referencing errors in the Road and Path Network

    4 Road Link features (data schema versions 2.0, 3.0, 4.0 and 5.0) reference non-existent Road Node (data schema version 1.0) features.

    2 Path Link features (data schema versions 1.0, 2.0 and 3.0) reference a non-existent Path Node feature (data schema version 1.0).

    These issues are currently being investigated.

    17/08/2026

    OS NGD Buildings Theme resolved data issues

    OS NGD Geographical Names Theme resolved data issues

    OS NGD Land Theme resolved data issues

    OS NGD Land Use Theme resolved data issues

    OS NGD Structures Theme resolved data issues

    OS NGD Transport Theme resolved data issues

    OS NGD Water Theme resolved data issues

    Archived resolved data issues for temporal filtering

    getting started with temporal filtering page
    Current Known Data Issues
    Service Availability Dashboard on the OS Data Hub

    This issue was resolved on 17 August 2026. Customers who take monthly updates will see this fix in the next update on 01 September 2026.

    Interruption to the supply of Daily Updates for OS NGD Building Part (February 2025) and impact on topological data ‘surface’ of OS NGD 'Feature' Collections

    Unlocking Multiple Residence (MR) insight: Better understand complex addresses, such as flats, apartments and shared-entry properties, through enhanced sub-premise information of postal addresses that sit behind a single front door.

    Example image showing how to link between unique identifiers on Royal Mail related components, Royal Mail Address features (PAF or NYB) and local authority records. A background map has been included for context.
    • Stronger links through UPRNs (Unique Property Reference Numbers): Enhanced matching between Royal Mail records and UPRNs makes it easier to connect address data to wider OS and third-party datasets, supporting better integration, analytics and decision-making.

    • Richer address intelligence: New OS-derived attributes (including full address, postcode geography and match indicators) provide additional context to support search, filtering, validation and operational workflows.

    • A future-focused roadmap: October 2026 is the next step in a broader programme of Royal Mail enhancements, with future support planned for Alias and Postcode Information File (PIF) content.

    Administrative and Statistical Units – Regional Authorities

    • Additional features have been added to data schema version 2.0 of the Regional Authority Feature Type that represent operative English combined authorities: English Combined Authority, English Combined County Authority, English Foundation Strategic Authority, English Mayoral Strategic Authority and English Established Mayoral Strategic Authority.

    The fifth OS recommended recipe guide has published on the site:

    • Town and city planning recipe guide: The guide provides a geospatial toolkit to help you identify the level of access to natural areas from existing addresses, both residential and commercial; its step-by-step instructions outline how to select relevant pieces of addressing, administrative and statistical units, buildings, geographical names, land use and water data from the OS NGD and weave them into a recipe.

    The suggested recipe will be useful for town and city planners who want to assess access to natural areas from existing commercial and residential addresses, and provide evidence to help inform compliance with Natural England's Green Infrastructure Framework.

    The fourth OS recommended recipe guide has published on the site:

    • Identifying crossing points and bottlenecks: The guide provides a geospatial toolkit for helping you identify the location of bridges, tunnels, fords and crossing points using the OS NGD; its step-by-step instructions outline how to select relevant pieces of addressing, structures, transport and water data from the OS NGD and weave them into a recipe.

    The suggested recipe will be useful for organisations (particularly emergency services) that need to understand critical infrastructure and mobility restrictions for vehicles and pedestrians.

    A new 'Transport networks in the OS NGD' explainer has been added to the site; this explainer goes through transport networks in the OS NGD and how the data and feature types in the collections fit together. It covers the following topics:

    • Building routable transport networks

    • Road, path, ferry and rail networks

    • Routing information

    • Streets and asset management information

    • Other road network information

    • National street gazetteers, GeoPlace and Improvement Service

    • Transport features

    A new 'Understanding land use in the OS NGD' guide has been added to the site; this guide contains specific advice on how to make the most of OS NGD Land Use data and includes the following topics:

    • How OS represents human activity or the economic function of an area or piece of land

    • How OS Land Use Tier A and Tier B classifications are assigned and maintained

    • How Sites relate spatially to surrounding features

    • How address records are matched and summarised

    • How Site Description values map across to National Land Use Database (NLUD) values

    • How OS Land Use Tier A and Tier B classifications map across to one another

    • How Site Description values map across to OS Land Use Tier A and Tier B classifications

    • Which Sites have populated Status attribute values

    Two more OS recommended recipe guides have been published on the site:

    • Identifying higher-risk buildings recipe guide – The guide contains detailed step-by-step instructions outlining how you can create a recipe in OS Select+Build to identify higher-risk buildings. It provides a geospatial toolkit that will help you use OS NGD data to identify if a building in occupation in Great Britain is classified as higher-risk by the Building Safety Act 2022 and the Higher-Risk Buildings (Descriptions and Supplementary Provisions) Regulations 2023.

    • Safer routes to schools recipe guide – The guide provides a geospatial toolkit for helping you calculate safer routes to schools across Great Britain; its step-by-step instructions outline how to select relevant pieces of addressing, routing and transport network data from the OS NGD and weave them into a recipe in OS Select+Build.

    The first OS recommended recipe guide was published on the site:

    • Greenspace recipe guide – This guide provides a geospatial toolkit to help you understand green spaces across Great Britain; the step-by-step instructions outline how to select relevant pieces of topographic data from the OS NGD and weave them into a greenspace recipe in OS Select+Build.

    The suggested recipe will help support research, management, planning, auditing and policy for greenspace use cases.

    When you order data using OS Select+Build, you create a recipe to define the data you need. Selecting the right data from OS NGD themes can be complex, so we are developing a set of recommended recipe guides to help you get started with common use cases, focussing on areas where many customers have similar requirements.

    These guides are intended as a starting point and you can adapt the suggested recipes at the recipe creation or editing stage so that they fully meet your needs.

    We expect to add further recommended recipe guides over time.

    Highlights of the OS NGD data enhancements released to customers in Spring 2026.

    Administrative and Statistical Units – retail areas

    • A new OS Functional Areas Collection has been added to the OS NGD Administrative and Statistical Units Theme. Functional areas are algorithmically derived notional geographies; they provide nationally consistent data for use in planning, policy and research.

    • Retail areas are the first feature types to be included in the new collection:

      • Retail Area Major features reflect high streets, shopping centres and retail parks.

      • Retail Area Minor features reflect smaller clusters of retail addresses.

      • features provide information on retail areas, from small local centres, through town centres to a single national centre.

    • The three new retail areas feature types define notional geographic extents of retail locations across Great Britain, identifying clusters of buildings with retail addresses.

    Example image showing Retail Area Aggregated, Retail Area Major and Retail Area Minor features in the centre of Southampton. A background map has been included for context.
    Example image showing Retail Area Major features in the centre of Southampton. The different colours for the polygons show what Retail Setting value (High Street, Shopping Centre or Retail Park) is assigned to each Retail Area Major feature. A background map has been included for context.

    Administrative and Statistical Units – postcodes

    • Two new collections have been added to the OS NGD Administrative and Statistical Units Theme: the OS GB Postcodes Collection and OS NI Postcodes Collection. The collections provide complete, analytical and authoritative postcode datasets for Great Britain and Northern Ireland.

    • Postcodes for Great Britain are available via an API for the first time (OS NGD API – Features).

    • Postcode Unit Point Feature Types are available for Great Britain and Northern Ireland. When used together, these feature types include every postcode in the Royal Mail's Postcode Address File (PAF) content with Ordnance Survey’s and Ordnance Survey of Northern Ireland's geospatial attribution for the first time. The identical schemas for these feature types enable compatibility and let you achieve full UK postcode coverage.

    • The has been designed to align with Ordnance Survey's authoritative geospatial data; therefore, a postcode polygon will include the whole building associated with a delivery point. This feature type has full Great Britain coverage.

    Example image showing Postcode Unit Area and Postcode Unit Point features over part of Exeter. A background map is included for context.

    Structures

    • The addition of third-party bridge information to Compound Structure features. Existing bridge data for Great Britain has now been enriched with third-party attribution (i.e. for canal bridges). Rather than creating new bridge geometries, the data ensures bridge names, numbers and the name of the expert third party who provided the information are linked to the Compound Structure features.

    Transport

    • Full data coverage for cycle lanes and bus lanes data across Great Britain was achieved by March 2026. There was partial data coverage across Great Britain for the Bus Lane and Cycle Lane Feature Types between September 2025 (when the two feature types were launched) and March 2026, with iterative increases in coverage released monthly. There's now a consistent and maintained dataset of bus lanes and cycle lanes for the whole of Great Britain.

    Example map showing Cycle Lane features. Background map included for context.

    Example map showing Bus Lane and Road Link features. Background map included for context.

    OS NGD planned enhancements outlined in our roadmap

    • The OS Data Products Roadmap is available to view on Aha! It outlines our focus areas for enhancements and new releases for the OS NGD and our Download products (Premium and OpenData products) over the next two years.

    • Planned improvements to existing OS NGD data are also called out on the OS Data Products Roadmap. A high-level summary of improvements we've recently made to existing OS NGD data can be found on the OS NGD Improvements page.

    • The new data enhancements for the OS NGD are expected to continue to launch twice a year in spring and autumn. Access enhancements related to the OS NGD are not tied to spring and autumn new data enhancement releases and can occur throughout the year.

    • Recently delivered data and access enhancements to the OS NGD are listed below.

    2026 OS NGD enhancements

    Autumn 2026 – OS NGD data enhancements

    Highlights of the OS NGD data enhancements released to customers in Autumn 2026

    Royal Mail Address Feature Types
    Highlights of the OS NGD data enhancements released to customers in Autumn 2026.
    Highlights of the OS NGD data enhancements released to customers in Autumn 2026.

    October 2026 – OS NGD access enhancements

    September 2026 – OS NGD access enhancements

    August 2026 – OS NGD access enhancements

    July 2026 – OS NGD access enhancements

    June 2026 – OS NGD access enhancements

    April 2026 – OS NGD access enhancement

    What are OS recommended recipes?

    Spring 2026 – OS NGD data enhancements

    Highlights of the OS NGD data enhancements released to customers in Spring 2026

    2025 OS NGD enhancements

    Autumn 2025 – OS NGD data enhancements

    Address

    The and now contain a new Royal Mail Address Feature Type, representing a major step forward in address data provision. These feature types combine the full Royal Mail Postcode Address File (PAF) content with Ordnance Survey’s authoritative geospatial attribution for the first time.

    Highlights of the new Royal Mail Address Feature Types:

    • Full PAF content: 100% coverage of Royal Mail’s delivery point addresses, with UDPRN (Unique Delivery Point Reference Number) as the primary key.

    June 2025 – OS NGD access enhancements in OS Select+Build

    You can now edit a recipe in OS Select+Build to add or remove themes / feature types, or change attribute filtering or data schema versions. Please see the and pages for more details.

    March 2025 – OS NGD data enhancements

    Buildings

    • New added to the OS Building Features Collection. Building Access Location features identify access points to key public buildings for vehicles and pedestrians, enhancing urban planning, emergency response, and accessibility.

    • New attribution provided for :

    2024 OS NGD enhancements

    September 2024 – OS NGD data enhancements

    Buildings

    • New number of floors attribution added to features to identify the maximum number of occupiable floors at or above ground level within a residential or office building. Over 23.5 million office or residential buildings in Great Britain now have a number of floors value, and a total of nearly 47 million floors have been added to the OS NGD. Among other uses, the new attribution will provide emergency services with more information when responding to real-time incidents, such as a fire in a high-rise building, and will help support insurers to improve their risk profiling and underwriting.

    Land Use – Enhanced land use attribution, increased coverage for Sites, and more Site Access Location points

    March 2024 – OS NGD data enhancements

    Buildings

    • New attribution provided for :

      • Building Age: The age of the main building in a site, created using Verisk data and OS data​.

    2023 OS NGD enhancements

    September 2023 – OS NGD data enhancements

    Buildings

    • New added to the OS Building Features Collection.

      • Attribution provided on a building's use, how it is connected to other buildings, additional details on addresses contained within a building, and whether a building is considered to be the main one within a site.

    August 2023 – OS NGD data enhancements

    Transport

    • Path network coverage extended to all of Great Britain (it was previously just available for urban areas). The road and path networks have been topologically structured together, which has increased the number of features present in the Paths feature types (i.e. Path, Path Link, Path Node, Connecting Link, and Connecting Node Feature Types).

    March 2023 – OS NGD access enhancements

    APIs

    • Launch of the new vector tiles API: .

    OS Select+Build

    • Option to select which data schema version you want to access for certain address feature types.

    March 2023 – OS NGD data enhancements

    Address

    • New attributes added to existing address feature types and improvements made for addressing floor-level information as part of the release of data schema version 2.0.

    • Improvements made to address data regarding the consistency of address positioning, usage classifications, business names and lifecycle.

    Transport

    Polling District

    A polling district is the subdivision of a parliamentary constituency for the purpose of a UK Parliamentary election. Polling districts are not maintained on a regular basis and have mostly been frozen since 2016. From May 2022, 63 areas will show amended polling districts.

    The earliest date on which you can request a one-off snapshot of a date in the past for data in this feature type is 29 September 2022.

    Any data temporally filtered earlier than the specified earliest date noted above for the data schema version may contain data inconsistencies.

    The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

    Primary identifier for the feature. The OSID is a Globally Unique Identifier (GUID) and requires no centralised authority to ensure uniqueness. Note that the same OSID can occur in more than one feature type when a single feature is represented multiple times in the OS NGD.

    • Data Types: String (GPKG), String (CSV)

    Nullable: false

  • Max Length: 36

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Date when the version was last updated.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The date this version of the feature became the latest version.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The date this version of the feature was superseded by an update or ceased to exist.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The type of change that generated a new version of the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: changetypevalue

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Geometry for the feature.

    • Data Types: Geometry (GPKG), WKT (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    • Geometry Type: MultiPolygon

    The measured area of the geometry in square metres.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 18

    • Scale: 6

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The OS NGD theme to which this feature belongs.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: themevalue

    • Max Length: 40

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    A single descriptive value intended for a quick understanding of what the feature represents.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: pollingdistrictdescriptionvalue

    • Max Length: 50

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0

    Polling district identifier.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 10

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    A single description value for boundary type.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: boundarytypevalue

    • Max Length: 50

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0

    Identifier for the Parent Boundary.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 36

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Further classification indicating the Parent Boundary feature type.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: parentfeaturetypevalue

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Further classification indicating the Parent Boundary.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: parentboundarydescriptionvalue

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Name assigned to identify the Parent Boundary. If the name is defined in multiple languages, then each name shall be provided with an associated language qualifier. If the proper name is only defined in one language, then no language qualifier will be provided.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 254

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The language type associated with name1 for the Parent Boundary. The valid values are defined in the LanguageValue codelist.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: languagevalue

    • Max Length: 3

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Name assigned to identify the Parent Boundary. If the name is defined in multiple languages, then each name shall be provided with an associated language qualifier. If the proper name is only defined in one language, then no language qualifier will be provided.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 254

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The language type associated with name2 for the Parent Boundary. The valid values are defined in the LanguageValue codelist.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: languagevalue

    • Max Length: 3

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Identifier for the Parent Boundary.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 36

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Further classification indicating the Parent Boundary feature type.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: parentfeaturetypevalue

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Further classification indicating the Parent Boundary.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: parentboundarydescriptionvalue

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Name assigned to identify the Parent Boundary. If the name is defined in multiple languages, then each name shall be provided with an associated language qualifier. If the proper name is only defined in one language, then no language qualifier will be provided.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 254

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The language type associated with name1 for the Parent Boundary. The valid values are defined in the LanguageValue codelist.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: languagevalue

    • Max Length: 3

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Name assigned to identify the Parent Boundary. If the name is defined in multiple languages, then each name shall be provided with an associated language qualifier. If the proper name is only defined in one language, then no language qualifier will be provided.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 254

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The language type associated with name2 for the Parent Boundary. The valid values are defined in the LanguageValue codelist.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: languagevalue

    • Max Length: 3

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Identifier for the Parent Boundary.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 36

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Further classification indicating the Parent Boundary feature type.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: parentfeaturetypevalue

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Further classification indicating the Parent Boundary.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: parentboundarydescriptionvalue

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Name assigned to identify the Parent Boundary. If the name is defined in multiple languages, then each name shall be provided with an associated language qualifier. If the proper name is only defined in one language, then no language qualifier will be provided.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 254

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The language type associated with name1 for the Parent Boundary. The valid values are defined in the LanguageValue codelist.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: languagevalue

    • Max Length: 3

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Name assigned to identify the Parent Boundary. If the name is defined in multiple languages, then each name shall be provided with an associated language qualifier. If the proper name is only defined in one language, then no language qualifier will be provided.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 254

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The language type associated with name2 for the Parent Boundary. The valid values are defined in the LanguageValue codelist.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: languagevalue

    • Max Length: 3

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Identifier for the Parent Boundary.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 36

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Further classification indicating the Parent Boundary feature type.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: parentfeaturetypevalue

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Further classification indicating the Parent Boundary.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: parentboundarydescriptionvalue

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Name assigned to identify the Parent Boundary. If the name is defined in multiple languages, then each name shall be provided with an associated language qualifier. If the proper name is only defined in one language, then no language qualifier will be provided.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 254

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The language type associated with name1 for the Parent Boundary. The valid values are defined in the LanguageValue codelist.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: languagevalue

    • Max Length: 3

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Name assigned to identify the Parent Boundary. If the name is defined in multiple languages, then each name shall be provided with an associated language qualifier. If the proper name is only defined in one language, then no language qualifier will be provided.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 254

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The language type associated with name2 for the Parent Boundary. The valid values are defined in the LanguageValue codelist.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: languagevalue

    • Max Length: 3

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The inland area of the feature in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The non-inland area in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    The total area in hectares.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 15

    • Scale: 6

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0

    Temporal filtering

    Feature type attributes

    Loading OS NGD CSV files into databases

    Comma-separated values (CSV) file format is universally supported for easy ingestion into all major database products. Before loading OS NGD data contained in CSV files into a database, it is necessary to create relevant tables. Data definition language (DDL) statements for PostgreSQL, SQL Server and Oracle can be accessed in our OS NGD Resources GitHub repository.

    For instructions on loading CSV files, see the Getting Started with CSV guide.

    osid

    versiondate

    versionavailablefromdate

    versionavailabletodate

    changetype

    geometry

    geometry_area

    theme

    description

    pollingdistrictid

    boundarytype

    boundaryparentreference1_id

    boundaryparentreference1_featuretype

    boundaryparentreference1_classification

    boundaryparentreference1_name1_text

    boundaryparentreference1_name1_language

    boundaryparentreference1_name2_text

    boundaryparentreference1_name2_language

    boundaryparentreference2_id

    boundaryparentreference2_featuretype

    boundaryparentreference2_classification

    boundaryparentreference2_name1_text

    boundaryparentreference2_name1_language

    boundaryparentreference2_name2_text

    boundaryparentreference2_name2_language

    boundaryparentreference3_id

    boundaryparentreference3_featuretype

    boundaryparentreference3_classification

    boundaryparentreference3_name1_text

    boundaryparentreference3_name1_language

    boundaryparentreference3_name2_text

    boundaryparentreference3_name2_language

    boundaryparentreference4_id

    boundaryparentreference4_featuretype

    boundaryparentreference4_classification

    boundaryparentreference4_name1_text

    boundaryparentreference4_name1_language

    boundaryparentreference4_name2_text

    boundaryparentreference4_name2_language

    landareahectares

    tidalareahectares

    totalareahectares

    Site
    ) should be used for records after this date.

    This issue only affects data schema version 1.2 of Site; data schema v2.0 of Site was launched with the casing standards consistently applied.

    27/02/2026

    This issue was resolved by 27 February 2026.

    Incorrect GSS code values for Barnsley and Sheffield

    The GSS codes for Sheffield and Barnsley have only been updated in OS NGD Address GB Collection features that have received change-only updates (COUs) since 01/04/2025. Features in Sheffield or Barnsley that have not received COU since this date will display the previous (incorrect) GSS code.

    24/06/2025

    We are pleased to inform you that the fix for GSS codes affecting the OS NGD Address GB Collection was made available to customers on Tuesday 24/06/2025.

    This issue was resolved in September 2025.

    Site count discrepancies for some Land features

    In a small number of instances, the Containing Site Count attribute presents the wrong value in Land features. This error only impacts 0.7% of Land features, and we expect it to be fixed by early October 2024.

    12/10/2024

    This issue was resolved on 12 October 2024. Any data ordered or provided after this date will include the fixed data.

    This issue was resolved on 03/11/2025.

    Duplicate features in the OS NGD Structures and OS NGD Land Themes, and duplicate features in OS NGD Structures and OS NGD Building Themes

    Following a recent update, not all features which were due to move themes fully migrated from one OS NGD theme to another. There are 3 595 duplicate features in the below themes:

    • 3 584 ‘slipway’ features are in both the OS NGD Structures Theme and the OS NGD Land Theme. These features should only be available in the OS NGD Land Theme.

    • 11 ‘Grandstand’ features are in both the OS NGD Structures Theme and the OS NGD Buildings Theme. These features should only be available in the Building Part Feature Type.

    The duplicated features have the same ID when represented in the more than one feature type.

    02/09/2025

    This issue was resolved on 02 September 2025. Customers who take monthly updates will see this fix in the next update on 01 October 2025.

    Duplicate features in the OS NGD Structures and OS NGD Land Themes, and duplicate features in OS NGD Structures and OS NGD Building Themes

    Following a recent update, not all features which were due to move themes fully migrated from one OS NGD theme to another. There are 3 595 duplicate features in the below themes:

    • 3 584 ‘slipway’ features are in both the OS NGD Structures Theme and the OS NGD Land Theme. These features should only be available in the OS NGD Land Theme.

    • 11 ‘Grandstand’ features are in both the OS NGD Structures Theme and the OS NGD Buildings Theme. These features should only be available in the Building Part Feature Type.

    The duplicated features have the same ID when represented in the more than one feature type.

    02/09/2025

    This issue was resolved on 02 September 2025. Customers who take monthly updates will see this fix in the next update on 01 October 2025.

    12/12/2025

    This issue was resolved on 12/12/2025.

    Road Links with unexpected pavement update dates

    17 Road Link features (data schema versions 2.0, 3.0 and 4.0) with an incorrect Presence of Pavement Update Date attribute date value in the future (2999). The update date should reflect when the attribute was last updated, so it should never be a future date. This issue is currently being investigated.

    05/11/2025

    This issue was resolved on 05 November 2025. Customers who take monthly updates will see this fix in the next update on 01 December 2025.

    Duplicate Street Light features

    There are around 84 000 Street Light features that are duplicated in Milton Keynes, Bedford and surrounding areas. This means that in this area, each street Light geometry is replicated twice; however, each geometry will still have its own unique OSID.

    03/04/2025

    This issue was resolved on 03 April 2025. Customers who take monthly updates will see this fix in the next update on 01 May 2025.

    Incorrect Street Light coverage values on Road Links

    We are aware of an issue that has caused a small number of incorrect values for Street Light coverage attribution on Road Links. Impacted Road Links will have a Presence Of Street Light Coverage attribute value that does not align with the evidence of street light presence in the Street Light Feature Type.

    For example, a Road Link that has Street Lights features along it may have a coverage value of 'Fully Unlit' when it does in fact have Street Light features alongside it.

    This issue affects approximately 0.45% of Road Links.

    03/04/2025

    This issue was resolved on 03 April 2025. Customers who take monthly updates will see this fix in the next update on 01 May 2025.

    Incorrect speed values

    Speed data is supplied quarterly from our third-party supplier. We have identified an issue in which OS have not correctly processed this data. This has resulted in possible incorrect values in the Average and Indicative Speed Feature Type.

    25/07/2024

    This issue was resolved on 25 July 2024. Any data ordered or provided after this date will include the fixed data.

    Welsh speed limit changes

    On 17 September 2023, default 20 mph speed limits were introduced across Wales. We are aware that these changes are not yet reflected in the Average and Indicative Speed Feature Type. Speed limit data is supplied by our third-party supplier quarterly. The most recent supply occurred before the Welsh speed limit changes took place and therefore will not be reflected in the OS NGD until the next supply. We expect the updated Welsh speed limits to be in NGD from December 2023.

    13/12/2023

    This issue was resolved on 13 December 2023. Any data ordered or provided after this date will include updated Welsh speed limit data.

    Incorrect speed values

    In the Average and Indicative Speed Feature Type, the indicative speed value for individual Road Links can be inferred by Ordnance Survey. We are aware that in certain instances some of these indicative speed values are incorrect. We are working to resolve this issue and have an approximate implementation date of the start of July 2023. This issue impacts just over 2% (174 000) of the total Road Links in the Average and Indicative Speed Feature Type.

    02/07/2023

    This issue was resolved on 02 July 2023. Any data ordered or provided after this date will include the fixed data.

    28/01/2026

    This issue was resolved on 28 January 2026. Customers who take monthly updates will see this fix in the next update on 01 February 2026.

    Unexpectedly null Catchment Name and Catchment ID for Water Links

    Approximately 19 000 Water Link features (data schema version 1.0) incorrectly have a null Catchment Name and Catchment ID. Only links which straddle catchment boundaries or sit entirely outside catchments should have null values in these attributes.

    28/10/2025

    This issue was resolved on 28 October 2025. Customers who take monthly updates will see this fix in the next update on 01 November 2025.

    Water Link features with an End Node attribute value of 'MissingXRef'

    3 667 Water Link features (data schema version 1.0) erroneously have an End Node attribute value of 'MissingXRef'. This may cause problems with validation as the value is not a valid OSID.

    28/10/2025

    This issue was resolved on 28 October 2025. Customers who take monthly updates will see this fix in the next update on 01 November 2025.

    Orphaned Water Nodes

    1 007 Water Node features (data schema version 1.0) are not referenced by any extant Water Link.

    28/10/2025

    This issue was resolved on 28 October 2025. Customers who take monthly updates will see this fix in the next update on 01 November 2025.

    Unexpected Water Link names

    Approximately 4 000 Water Link features (data schema version 1.0) are not being named as expected: Name 1 Text / Name 2 Text attribute populated with the name from the longest (by length) named waterway; Name Secondary 1 Text attribute populated with the name of the next longest named waterway, etc.

    28/10/2025

    This issue was resolved on 28 October 2025. Customers who take monthly updates will see this fix in the next update on 01 November 2025.

    contact us for assistance
    description values
    Site Feature Type
    OS NGD Improvements page

    Multiple UDPRN to UPRN matches: Identifying where multiple addresses in PAF can be associated to a single UPRN (Unique Property Reference Number).

  • Enhanced attribution: Additional OS-derived metadata, including geometry, positional accuracy, geometry allocation method, relationships with local authority addresses and standard OS NGD attribution.

  • Buildings

    Enhanced Physical State attribution is now available for Building features. The Physical State attribute classifies buildings as 'Built', 'Under Construction', or 'Derelict' to provide a clear, up-to-date view of their structural condition. Customers can use this attribute to track building construction progress and identify derelict properties; the attribute is also useful to Emergency Services and the planning and insurance sectors as it gives them accurate building lifecycle data.

    Land

    • Intertidal areas obscured by elevated structures, such as piers and jetties, have been added to the Land Feature Type for more complete coverage of the intertidal zone.

    Land Use

    • Enhanced Status attribution is now available for Site, Building Part, Land, Rail, Road Track Or Path, Structure and Water features. The Status attribute reflects the state of a feature in relation to either its physical condition or the activity the feature is intended to support. This value is either inherent from the nature of the topographic feature or can be inherited from the Site the feature lies within.

    • Please note that Status attribute values are only recorded against a subset of over 100 Site types, including Railway Stations, Schools, Sports Grounds, Power Stations and Quarries; the full list of Site types is available in a table on the OS Land Use Features Collection page.

    • National Land Use Database (NLUD) values are now populated for 'Derelict Land'.

    • The now includes a new value of 'Derelict'.

    Transport

    • New Cycle Lane Feature Type added to the OS Transport Network Collection to identify the location of cycle lanes, either segregated by a physical feature or identified by painted or other signage. The new data will support local authorities, regional transport bodies and central government to undertake planning, asset management and road safety analysis, plus understand connectivity and gap analysis for active travel networks.

    • New attribution supplied against the Path Link Feature Type to indicate the presence of cycle lanes.

    • New Bus Lane Feature Type added to the OS Transport Network Collection to identify the location of bus lanes that are segregated by a physical feature or painted section of road only for buses or shared usage. The new data will support local authorities, regional transport bodies and central government to plan street works and conduct connectivity and gap analysis for public transport networks.

    • New attribution supplied against the to indicate the presence of bus lanes and cycle lanes.

    Water

    • Continuous tidelines are now available in the OS Water Features Collection through the addition of two new feature types: Tidal Boundary Continuous High and Tidal Boundary Continuous Low. The latest update delivers automated, continuous mean high water and mean low water tidelines by dissolving existing Tidal Boundary features into seamless lines that are topologically coincident with their source water features. The two new feature types will help customers to conduct environmental management and accurately model coastal change and flooding.

    • New attribution is supplied against Water Link features describing the average width of the watercourse and the width derivation method. Minimum and maximum widths of watercourses are also supplied where a Water Link feature has been captured as a topographic polygon. The new watercourse width attribution will support ecological and flood modelling, infrastructure planning and situational awareness for emergency services.

    Roof Shape: Identifies the predominant geometric shape of a building's roof, aiding in visualisation and architectural analysis.

  • Roof Aspect: Provides information on the orientation of a roof, which is useful for solar energy planning and environmental studies.

  • Green Roof Presence: Indicates whether a building has a green roof, supporting sustainability and urban greening initiatives.

  • Solar Panel Presence: Shows if solar panels are installed on a building's roof, helping in renewable energy assessments and planning.

  • Roof Material: Details the type of predominant material used for a roof, which is important for construction, maintenance, and environmental impact studies.

  • Building Height: A comprehensive set of five attributes detailing the heights of various parts of a building, including both absolute and relative measurements. This enhancement supports urban planning and Emergency Services.

  • These buildings enhancements aim to improve visualisation, urban development planning, emergency response, and sustainability initiatives. More information on the March 2025 buildings enhancements is available from the OS NGD Buildings pages in the 'Using OS NGD Data' section.

  • Geographical Names

    • New Crowd Sourced Name Point Feature Type added to the OS Named Features Collection, which includes names submitted by expert third parties via the Vernacular Names Tool in the OS Data Hub. Where possible, the crowd sourced names are linked to other OS NGD features, allowing the use of both official and colloquial names together.

    Land Use

    • Three new types of site added to Land Use Sites descriptions: Beach, Military Training Area, and Wind Farm. Over 2 600 new sites have been added to the dataset for this enhancement (1 927 beaches, 90 Military Training Areas and 604 Wind Farms). These are sites that may not be spatially coincident with existing topographic areas (i.e. they may not align with topographic features like field boundaries), unlike other types of site. Beaches will include Site Access Locations with attribution that highlights the nearest public Road Node and the direct distance to that node from the access point on the edge of the beach feature. Military Training Areas and Wind Farms will not include Site Access Locations.

    • An Access Purpose attribute has been added to Site Access Location features for key public sites to identify what the Site Access Location is being used for (Primary Public, Public, Private, or Emergency). The new data will enhance and support situational awareness for emergency responses, hazard planning, and policing operations at key public sites; the data will also support travel modelling and make it easier to assess accessibility to services for the public.

    Structures

    • The addition of nine different types of tunnel to the Compound Structure Feature Type. These were added to v2.0 of the schema on 28 March 2025 and v1.0 on 09 April 2025.

    Transport

    • New Street Light Feature Type added to the OS Transport Features Collection to identify the location of pole-mounted street lights and provide a reference to the nearest Road Link or Path Link. This is the first consistent GB-wide dataset of street lights that is updated monthly and maintained to defined quality levels.

    • New attribution supplied against the Road Link and Path Link Feature Types to indicate how well-lit they are. The new data will support the identification of safe routes for active travel use cases.

    New land use attribution will be provided for the OS NGD ‘Features’ Collections for Buildings, Land, Land Use, Structures, Transport and Water. The new attribution maps the OS land use classifications to the National Land Use Database (NLUD) schema and the land use information derived from OS Addressing. The new attribution helps to give more detail about what is contained within a Site – for example, the total number of addresses contained within a single Site and what number of those addresses are defined as commercial, residential, or other.

  • Greater coverage for land use Sites, particularly non-residential sites, with over 1.5 million Sites added to the OS NGD gradually over the last 2 years. This has brought the total number of Sites contained within the OS NGD to 26 million.

  • An additional 180 000 Site Access Location points have been added to the OS NGD. These features show where vehicles and / or pedestrians can access Sites and, among other uses, help the emergency services to identify the most efficient routes for reaching an incident.

  • Structures

    • Additional bridge interaction attribution added to Compound Structure features to identify the type of network (road, path, railway, canal, water or multiple) passing over and / or under bridges. Over 660 000 bridge interactions have been added to the OS NGD.

    Construction Material: The primary construction material of the building, created using Verisk data and OS data​.

  • Basement Presence: An indicator to show whether a basement or a self-contained basement flat are present at the building, created using Verisk data and OS data​.

  • Building Description: A new description attribute to describe the nature of the building, derived from its use and relation to surrounding buildings,​ created using OS data​.

  • More information on the buildings enhancements is available from the OS NGD Buildings pages in the 'Using OS NGD Data' section.

  • Land cover – Enhanced land cover attribution

    • Enhanced land cover attribution to ‘natural’ topographic area features across the OS NGD ‘Features’ Collections for Land, Structures, Transport and Water.

    • Improved consistency and accuracy for specific land features by reducing the minimum capture size criteria in rural and moorland geographies.

    • Mapping OS land cover classification to recognised habitat classification schemes (EUNIS and UK BAP Broad Habitats) in a new cross reference table.

    • Assigning a percentage cover value to topographic areas in a new cross reference table.

    • More information on the land cover enhancements is available from the in the 'Using OS NGD Data' section.

    Structures – Field Boundary

    • New Field Boundary Feature Type added to the OS Structure Features Collection to identify the location, nature and properties of a field boundary in rural and moorland areas.

    • Height and width values provided for vegetated field boundary features.

    • More information on this enhancement is available from the Field Boundary pages in the 'Using OS NGD Data' section.

    Transport

    • New Tram On Road​ Feature Type added to the OS Transport Network Collection to locate where trams are present against the OS road network.

    • Tram track attribution added indicating the presence of tram tracks on a road​. Supplied as new attribution against Road Link features​.

    • More information on these enhancements is available from the OS NGD Transport pages in the 'Using OS NGD Data' section.

    Geographical Names

    • New Named Road Junction Feature Type added to the OS Named Features Collection, which provides enhanced names and the numbers of junctions. Includes both intersects without an official name or number and officially named or numbered junctions.

    Cross references added between the new Building Feature Type and the Building Part, Site, and Built Address Feature Types.

    Transport

    • New rail feature types added to the OS Transport Network Collection, giving information about the topologically connected rail network:

      • Railway Link

      • Railway Link Set

      • Railway Node

    • Available rail network attribution now includes track representation (single / multitrack, siding) and use (freight / passenger / mixed).

    • New added to the OS Transport Network Collection, giving information on the presence of pavements on the Road Network. More information on this enhancement is available from the in the Using OS NGD Data section.

    • New attribution added to the , giving details about pavement presence: left or right side of road, coverage, and minimum and average width. More information on this enhancement is available from the in the 'Using OS NGD Data' section.

    Ability to select a preference for the coordinate reference system you receive your OS NGD data in (see the 'Downloading with OS Select+Build' page and 'Coordinate reference systems' page for more details).

  • New ability to share your created recipes with other organisations so that they can use exactly the same selections as you (see the 'Downloading with OS Select+Build' page for more details).

  • A new Order Summary File will now be provided with your data packages to aid data validation when loading and using OS NGD data.

  • Enhanced search capability now available in both the Recipe Builder and your OS Select+Build Recipe Library, helping you locate feature types and your existing recipes quicker than before.

  • New Average and Indicative Speed Feature Type added to the OS Routing and Asset Management Information (RAMI) Collection, giving full Great Britain coverage for speed data.

  • Speed data is now included in the Public Sector Geospatial Agreement (PSGA), so it is free for PSGA Members for the first time.

  • Increased number of daily time periods now available for average speed data.

  • COUs (change-only updates) available for speed data for the first time.

  • Improved completeness of the Road Width attribute in the Road Link Feature Type, which extends coverage for road width data from just urban areas to urban areas, rural areas and mountain and moorland areas.

  • Water

    • Two new feature types added to the OS Water Features Collection:

      • Waterbody Catchment Feature Type

      • River Basin District Catchment Feature Type

    Retail Area Aggregated
    Postcode Unit Area Feature Type
    OS GB Address Collection
    OS Islands Collection
    Editing OS Select+Build recipes
    Getting started with attribute filtering
    Building Access Location Feature Type
    Building features
    Building
    Buildings
    Building Feature Type
    OS NGD API – Tiles
    Example image showing how to link between unique identifiers on Royal Mail related components, Royal Mail Address features (PAF or NYB) and local authority records. A background map has been included for context. An acronym key is also provided expanding the acronyms for UPRN, UDRPN and UMRRN.
    Images with 8 boxes. Each box contains text outlining one of the highlights of the OS NGD data enhancements released to customers in Spring 2026, for example, Three new Retail Areas Feature Types.
    Example showing Retail Area Aggregated, Retail Area Major and Retail Area Minor features in the centre of Southampton. A background map has been included for context.
    Example showing Retail Area Major features in the centre of Southampton. The different colours for the polygons show what Retail Setting value (High Street, Shopping Centre or Retail Park) is assigned to each Retail Area Major feature. A background map has been included for context.
    Example image showing Postcode Unit Area and Postcode Unit Point features over part of Exeter. A background map is included for context.
    Example map showing Cycle Lane features on roads in an urban area. Background map included for context.
    Example map showing Bus Lane and Road Link features. Background map included for context.

    Royal Mail Address

    The Royal Mail Address Feature Type provides Royal Mail delivery point addresses, a point geometry and information describing the relationship they have with local authority addresses.

    The following table provides details about this feature type’s data schema versions, including the reasons behind the changes and the related launch date when each version went live.

    Version ↓
    Launch Date
    Latest Date
    Change
    Site Description Value Code List
    Road Link Feature Type
    OS NGD Land cover enhancements pages
    Pavement Link Feature Type
    OS NGD Transport pages
    Road Link Feature Type
    OS NGD Transport pages
    Example image showing gaps in the OS NGD Building Part Feature Type data caused by a recent issue.

    1.1

    08 October 2026

    Ongoing

    Minor version increment. Update to schema to make the Description attribute filterable in OS Select+Build.

    1.0

    30 September 2025

    30 September 2026

    Initial launch of the Royal Mail Address Feature Type.

    Please see Data schema versioning for in-depth information about data schema versioning in the OS NGD.

    Temporal filtering allows you to order a one-off snapshot of data from the OS NGD from a current or past date. It is an optional step when you create a new data package in OS Select+Build (the OS NGD download service).

    The earliest and latest dates on which you can request a one-off snapshot of a date in the past for this feature type's data schema versions are indicated in the Data schema version table above. Please note that any data temporally filtered earlier than the specified launch date indicated in the table for the data schema versions may contain data inconsistencies.

    More information about temporal filtering on OS NGD feature types is available from the Getting started with temporal filtering guide.

    Royal Mail related components are provided for Royal Mail Address Feature Type data schema version 2.0 onward; they are not provided against data schema version 1.0 or 1.1 of the feature type.

    Customers taking data schema version 2.0 onward of the Royal Mail Address Feature Type in GeoPackage format will receive the following in their data package:

    • Feature type: Royal Mail Address

    • Related components: Multiple Residence, Delivery Point Alias and Other Alias

    However, the three Royal Mail related components (Multiple Residence, Delivery Point Alias and Other Alias) will only be provided for Royal Mail Address features if the Description attribute is 'Postcode Address File'. Against all other Royal Mail Address features where the Description attribute is 'Not Yet Built', the related components will be provided but will be populated as 'Null'.

    Please see the Address Related Components page for more information about the three Royal Mail related components.

    The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

    Unique Delivery Point Reference Number (UDPRN) assigned by Royal Mail as a persistent identifier.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    Date when the version was last updated.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The date this version of the feature became the latest version.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The date this version of the feature was superseded by an update or ceased to exist.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The type of change that generated a new version of the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: changetypevalue

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The OS NGD theme to which this feature belongs.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: themevalue

    • Max Length: 40

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    A single descriptive value intended for a quick understanding of what the feature represents.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: royalmailaddressdescriptionvalue

    • Max Length: 50

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.1, 2.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    The name of the organisation operating from the address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 60

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    For some organisations, department name is indicated because mail is received by subdivisions of the main organisation at distinct delivery points.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 60

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The sub building name and / or number are identifiers for subdivisions of properties.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 30

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

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

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    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 Building Name or the Sub Building Name fields.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 4

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    In certain places, for example, town centres, there are named thoroughfares within other named thoroughfares, for example, parades of shops on a high street where different parades have their own identity. For example, KINGS PARADE, HIGH STREET and QUEENS PARADE, HIGH STREET.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 80

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    A thoroughfare is a road, track or named access route on which there are Royal Mail delivery points, for example, HIGH STREET.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 80

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    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.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    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.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    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.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 30

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 30

    • OS Select+Build Filterable: No

    The postcode unit that the Address is situated within. A postcode is an abbreviated form of address, made up of combinations of between five and seven alphanumeric characters. These alphanumeric characters are used by Royal Mail to help with the automated sorting of mail. A postcode may cover between 1 and 100 addresses. Postcodes (for example, NW6 4DP) are comprised of two components. The first component is the outward code (or ‘outcode’), which is the first two to four characters of a postcode, constituting the postcode area and the postcode district, for example, NW6. The outward code is the part of the postcode that enables mail to be sent from the accepting office to the correct area for delivery. The second component of a postcode is the inward code (or ‘incode’), which is the last three characters of the postcode, constituting the postcode sector and the postcode unit, for example, 4DP. The inward code is used to sort mail at the local delivery office.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 8

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 8

    • OS Select+Build Filterable: No

    The postcode area is identified by one or two alpha characters at the start of the postcode, the letters being derived from a town, city or district falling within the postcode area. There are, at present, 124 postcode areas in Great Britain, for example, FK for Falkirk, CF for Cardiff and SO for Southampton. For more information about the postcode area, please consult chapter one 'Structure of a PAF address' of the Royal Mail Programmer's Guide.

    • Data Types: String (GeoJSON), String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 2

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0

    The postcode district is identified by one or two alphanumeric characters following the postcode area, for example, FK1 for Falkirk, CF10 for Cardiff and SO16 for Southampton. For more information about the postcode district, please consult chapter one 'Structure of a PAF address' of the Royal Mail Programmer's Guide.

    • Data Types: String (GeoJSON), String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 4

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0

    The postcode sector is a sub-area of a postcode district. It's identified by one numeric character following the postcode district (with a space included), for example, FK1 1 for Falkirk, CF10 1 for Cardiff and SO16 1 for Southampton. For more information about the postcode sector, please consult chapter one 'Structure of a PAF address' of the Royal Mail Programmer's Guide.

    • Data Types: String (GeoJSON), String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 6

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0

    A single numeric digit derived from the associated postcode. The Postcode Information File (PIF) Checksum Digit is derived from the postcode using the Royal Mail postcode checksum algorithm. The Checksum Digit is not part of the postcode itself and should not be represented as part of the postcode value. For more information about PIF attribution, please consult chapter 12 'Postcode Information File' of the Royal Mail Programmer's Guide.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 1

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0

    Details the delivery point address, described as either the relevant building number, or a string containing the most significant 50 characters of the delivery point description (as held as display text within the Postcode Address File – PAF). The Display Text Field will contain only the house number information unless properties do not have a house number, in which case the house name will appear. Where flats occur, the relevant flat information from the PAF will appear. For organisations which appear on the PAF, the organisation will appear on the Postcode Information File (PIF). For more information about PIF attribution, please consult chapter 12 'Postcode Information File' of the Royal Mail Programmer's Guide.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0

    Describes the address as a small or large user as defined by Royal Mail.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: postcodetypevalue

    • Max Length: 10

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    Name of the geographical territory that the Address is located within, where a geographical territory represents either a devolved country or an island nation. This is available only where the Royal Mail Postcode Address File (PAF) Address is matched to a Local Authority Unique Property Reference Number (UPRN).

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: countryvalue

    • Max Length: 25

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0

    Concatenation of the following address components: Organisation, Sub-Building Name and / or Building Name and / or Building Number, Thoroughfare, Locality, Post Town and Postcode.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 1 000

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0

    A two-character code uniquely identifying an individual delivery point within a postcode.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 2

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The Welsh translation of Dependent Thoroughfare.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 80

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The Welsh translation of Thoroughfare.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 80

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The Welsh translation of Double Dependent Locality.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The Welsh translation of Dependent Locality.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The Welsh translation of Post Town.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 30

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 30

    • OS Select+Build Filterable: No

    Post Office Box (PO Box) number or the British Forces Post Office (BFPO) number.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 13

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The date the Royal Mail record last changed.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    Date of the change file that first supplied the Royal Mail record.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    X coordinate defining the position of the object in accordance with the British National Grid (EPSG:27700) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 8

    • Scale: 2

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    Y coordinate defining the position of the object in accordance with the British National Grid (EPSG:27700) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 2

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    Value defining the latitude of the Address location in accordance with the ETRS89 (EPSG:4258) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 7

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    Value defining the longitude of the Address location in accordance with the ETRS89 (EPSG:4258) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 7

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    Geometry for the feature.

    • Data Types: Geometry (GPKG), WKT (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    • Geometry Type: Point

    Local Authority assigned value giving a description of the accuracy of the coordinate position allocated to the Address location, for example, 'Central Internal Position' of a building.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: positionalaccuracyvalue

    • Code List Version: 2.0

    • Max Length: 25

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version: 2.0

    Describes the method by which a geometry was allocated to the Royal Mail record. Where a Royal Mail record is matched to a Local Authority record, the geometry will be assigned from the matched record. Where a Royal Mail record cannot be directly matched, geometry will be assigned by reference to a parent record, a street, or records which share the postcode unit, sector, district or area – in the listed order of preference. Where none of the listed methods are available, the geometry will be allocated to an internal centre point for the Local Authority area or Island in which the Royal Mail address is located.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: geometryallocationmethodvalue

    • Max Length: 25

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 25

    Describes the reason that the Royal Mail record has not been matched to a Local Authority record.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 100

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The date on which the Unmatched Reason value was captured.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The Unique Property Reference Number (UPRN) to which a Unique Delivery Point Reference Number (UDPRN) has been matched.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The feature type of the Unique Property Reference Number (UPRN) to which the Unique Delivery Point Reference Number (UDPRN) has been matched.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: matchedaddressfeaturetypevalue

    • Max Length: 25

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.1, 2.0

    Indicates whether a matched Local Authority Unique Property Reference Number (UPRN) is considered to be the primary match by GeoPlace and / or the relevant Local Authority. This attribute is particularly useful when a Unique Delivery Point Reference Number (UDPRN) is matched to multiple UPRNs as it will provide a one-to-one relationship between the UPRN and UDPRN.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: yesnovalue

    • Max Length: 3

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0

    A description of the relationship assigned between the Unique Delivery Point Reference Number (UDPRN) and the Unique Property Reference Number (UPRN). Where a Postcode Address File (PAF) record relates directly to a Local Authority record, this is set to ‘Direct.’ If a ‘Direct’ match cannot be found, a PAF record may be matched to a Parent, Neighbour or Street record in Local Authority data, in order to estimate a position for the PAF record.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: rmtolamatchtypevalue

    • Max Length: 20

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.1, 2.0

    The date on which the match was made between the Unique Delivery Point Reference Number (UDPRN) and the Unique Property Reference Number (UPRN).

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The method by which the match was made.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: matchmethodvalue

    • Max Length: 10

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    Describes the organisation which made the match between the Royal Mail record and the Local Authority record.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: matchingorganisationvalue

    • Max Length: 25

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    2.0

    08 October 2026

    Ongoing

    Data schema versioning

    🔃 Data schema version table

    Major version increment. New attribution added for Full Address, Country, Primary UPRN Match, Postcode Area, Postcode District, Postcode Sector, PIF (Postcode Information File) Checksum Digit and PIF Display Text.

    The Postcode, Post Town, Welsh Post Town, Geometry Allocation Method and Positional Accuracy attributes are now filterable in OS Select+Build.

    New Multiple Residence, Delivery Point Alias and Other Alias Related Components added.

    Temporal filtering

    🆕 Related components

    🔃 Feature type attributes

    Comma-separated values (CSV) file format is universally supported for easy ingestion into all major database products. Before loading OS NGD data contained in CSV files into a database, it is necessary to create relevant tables. Data definition language (DDL) statements for PostgreSQL, SQL Server and Oracle can be accessed in our .

    For instructions on loading CSV files, see the guide.

    udprn

    versiondate

    versionavailablefromdate

    versionavailabletodate

    changetype

    theme

    description

    organisationname

    departmentname

    subbuildingname

    buildingname

    buildingnumber

    dependentthoroughfare

    thoroughfare

    doubledependentlocality

    dependentlocality

    posttown

    postcode

    🆕 postcodearea

    🆕 postcodedistrict

    There are certain non-geographic districts. In these instances, a district code is allocated to cover all large users in the postcode area. For more information about the postcode, please consult chapter one 'Structure of a PAF address' of the .

    🆕 postcodesector

    🆕 pifchecksumdigit

    All Postcode Address File (PAF) Mainfile addresses have associated Postcode Information File (PIF) attribution, although this attribution may present as null where the daily publication PAF Mainfile address has been created or edited and has not yet appeared in the subsequent monthly publication of PIF.

    All PIF attribution will appear as null upon initial release of v2.0 of the Royal Mail Address Feature Type, with publication in the OS NGD expected to begin in 2027.

    🆕 pifdisplaytext

    All Postcode Address File (PAF) Mainfile addresses have associated Postcode Information File (PIF) attribution, although this attribution may present as null where the daily publication PAF Mainfile address has been created or edited and has not yet appeared in the subsequent monthly publication of PIF.

    All PIF attribution will appear as null upon initial release of v2.0 of the Royal Mail Address Feature Type, with publication in the OS NGD expected to begin in 2027.

    postcodetype

    🆕 country

    🆕 fulladdress

    deliverypointsuffix

    welshdependentthoroughfare

    welshthoroughfare

    welshdoubledependentlocality

    welshdependentlocality

    welshposttown

    poboxnumber

    updatedate

    entrydate

    easting

    northing

    latitude

    longitude

    geometry

    positionalaccuracy

    geometryallocationmethod

    unmatchedreason

    unmatchedreasondate

    uprn

    matchedaddressfeaturetype

    🆕 primaryuprnmatch

    matchtype

    matchdate

    matchmethod

    matchingorganisation

    Royal Mail Address

    The Royal Mail Address Feature Type provides Royal Mail delivery point addresses, a point geometry and information describing the relationship they have with local authority addresses.

    The following table provides details about this feature type’s data schema versions, including the reasons behind the changes and the related launch date when each version went live.

    Version ↓
    Launch Date
    Latest Date
    Change

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Data Schema Version: 1.1

    Data Schema Version: 1.1

    Data Schema Version: 1.1

    Max Length: 25

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • Loading OS NGD CSV files into databases

    Note

    Note

    Note

    royalmailaddressdescriptionvalue
    positionalaccuracyvalue
    geometryallocationmethodvalue
    OS NGD Resources GitHub repository
    Getting Started with CSV
    Royal Mail Programmer's Guide

    1.1

    08 October 2026

    Ongoing

    Minor version increment. Update to schema to make the Description attribute filterable in OS Select+Build.

    1.0

    30 September 2025

    30 September 2026

    Initial launch of the Royal Mail Address Feature Type.

    Please see Data schema versioning for in-depth information about data schema versioning in the OS NGD.

    Temporal filtering allows you to order a one-off snapshot of data from the OS NGD from a current or past date. It is an optional step when you create a new data package in OS Select+Build (the OS NGD download service).

    The earliest and latest dates on which you can request a one-off snapshot of a date in the past for this feature type's data schema versions are indicated in the Data schema version table above. Please note that any data temporally filtered earlier than the specified launch date indicated in the table for the data schema versions may contain data inconsistencies.

    More information about temporal filtering on OS NGD feature types is available from the Getting started with temporal filtering guide.

    Royal Mail related components are provided for Royal Mail Address Feature Type data schema version 2.0 onward; they are not provided against data schema version 1.0 or 1.1 of the feature type.

    Customers taking data schema version 2.0 onward of the Royal Mail Address Feature Type in GeoPackage format will receive the following in their data package:

    • Feature type: Royal Mail Address

    • Related components: Multiple Residence, Delivery Point Alias and Other Alias

    However, the three Royal Mail related components (Multiple Residence, Delivery Point Alias and Other Alias) will only be provided for Royal Mail Address features if the Description attribute is 'Postcode Address File'. Against all other Royal Mail Address features where the Description attribute is 'Not Yet Built', the related components will be provided but will be populated as 'Null'.

    Please see the Address Related Components page for more information about the three Royal Mail related components.

    The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

    Unique Delivery Point Reference Number (UDPRN) assigned by Royal Mail as a persistent identifier.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    Date when the version was last updated.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The date this version of the feature became the latest version.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The date this version of the feature was superseded by an update or ceased to exist.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The type of change that generated a new version of the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: changetypevalue

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The OS NGD theme to which this feature belongs.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: themevalue

    • Max Length: 40

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    A single descriptive value intended for a quick understanding of what the feature represents.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: royalmailaddressdescriptionvalue

    • Max Length: 50

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.1, 2.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    The name of the organisation operating from the address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 60

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    For some organisations, department name is indicated because mail is received by subdivisions of the main organisation at distinct delivery points.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 60

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The sub building name and / or number are identifiers for subdivisions of properties.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 30

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

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

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    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 Building Name or the Sub Building Name fields.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 4

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    In certain places, for example, town centres, there are named thoroughfares within other named thoroughfares, for example, parades of shops on a high street where different parades have their own identity. For example, KINGS PARADE, HIGH STREET and QUEENS PARADE, HIGH STREET.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 80

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    A thoroughfare is a road, track or named access route on which there are Royal Mail delivery points, for example, HIGH STREET.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 80

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    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.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    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.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    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.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 30

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 30

    • OS Select+Build Filterable: No

    The postcode unit that the Address is situated within. A postcode is an abbreviated form of address, made up of combinations of between five and seven alphanumeric characters. These alphanumeric characters are used by Royal Mail to help with the automated sorting of mail. A postcode may cover between 1 and 100 addresses. Postcodes (for example, NW6 4DP) are comprised of two components. The first component is the outward code (or ‘outcode’), which is the first two to four characters of a postcode, constituting the postcode area and the postcode district, for example, NW6. The outward code is the part of the postcode that enables mail to be sent from the accepting office to the correct area for delivery. The second component of a postcode is the inward code (or ‘incode’), which is the last three characters of the postcode, constituting the postcode sector and the postcode unit, for example, 4DP. The inward code is used to sort mail at the local delivery office.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 8

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 8

    • OS Select+Build Filterable: No

    The postcode area is identified by one or two alpha characters at the start of the postcode, the letters being derived from a town, city or district falling within the postcode area. There are, at present, 124 postcode areas in Great Britain, for example, FK for Falkirk, CF for Cardiff and SO for Southampton. For more information about the postcode area, please consult chapter one 'Structure of a PAF address' of the Royal Mail Programmer's Guide.

    • Data Types: String (GeoJSON), String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 2

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0

    The postcode district is identified by one or two alphanumeric characters following the postcode area, for example, FK1 for Falkirk, CF10 for Cardiff and SO16 for Southampton. For more information about the postcode district, please consult chapter one 'Structure of a PAF address' of the Royal Mail Programmer's Guide.

    • Data Types: String (GeoJSON), String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 4

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0

    The postcode sector is a sub-area of a postcode district. It's identified by one numeric character following the postcode district (with a space included), for example, FK1 1 for Falkirk, CF10 1 for Cardiff and SO16 1 for Southampton. For more information about the postcode sector, please consult chapter one 'Structure of a PAF address' of the Royal Mail Programmer's Guide.

    • Data Types: String (GeoJSON), String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 6

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0

    A single numeric digit derived from the associated postcode. The Postcode Information File (PIF) Checksum Digit is derived from the postcode using the Royal Mail postcode checksum algorithm. The Checksum Digit is not part of the postcode itself and should not be represented as part of the postcode value. For more information about PIF attribution, please consult chapter 12 'Postcode Information File' of the Royal Mail Programmer's Guide.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 1

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0

    Details the delivery point address, described as either the relevant building number, or a string containing the most significant 50 characters of the delivery point description (as held as display text within the Postcode Address File – PAF). The Display Text Field will contain only the house number information unless properties do not have a house number, in which case the house name will appear. Where flats occur, the relevant flat information from the PAF will appear. For organisations which appear on the PAF, the organisation will appear on the Postcode Information File (PIF). For more information about PIF attribution, please consult chapter 12 'Postcode Information File' of the Royal Mail Programmer's Guide.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0

    Describes the address as a small or large user as defined by Royal Mail.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: postcodetypevalue

    • Max Length: 10

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    Name of the geographical territory that the Address is located within, where a geographical territory represents either a devolved country or an island nation. This is available only where the Royal Mail Postcode Address File (PAF) Address is matched to a Local Authority Unique Property Reference Number (UPRN).

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: countryvalue

    • Max Length: 25

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0

    Concatenation of the following address components: Organisation, Sub-Building Name and / or Building Name and / or Building Number, Thoroughfare, Locality, Post Town and Postcode.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 1 000

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0

    A two-character code uniquely identifying an individual delivery point within a postcode.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 2

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The Welsh translation of Dependent Thoroughfare.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 80

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The Welsh translation of Thoroughfare.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 80

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The Welsh translation of Double Dependent Locality.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The Welsh translation of Dependent Locality.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The Welsh translation of Post Town.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 30

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 30

    • OS Select+Build Filterable: No

    Post Office Box (PO Box) number or the British Forces Post Office (BFPO) number.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 13

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The date the Royal Mail record last changed.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    Date of the change file that first supplied the Royal Mail record.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    X coordinate defining the position of the object in accordance with the British National Grid (EPSG:27700) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 8

    • Scale: 2

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    Y coordinate defining the position of the object in accordance with the British National Grid (EPSG:27700) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 9

    • Scale: 2

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    Value defining the latitude of the Address location in accordance with the ETRS89 (EPSG:4258) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 7

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    Value defining the longitude of the Address location in accordance with the ETRS89 (EPSG:4258) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 7

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    Geometry for the feature.

    • Data Types: Geometry (GPKG), WKT (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    • Geometry Type: Point

    Local Authority assigned value giving a description of the accuracy of the coordinate position allocated to the Address location, for example, 'Central Internal Position' of a building.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: positionalaccuracyvalue

    • Code List Version: 2.0

    • Max Length: 25

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version: 2.0

    Describes the method by which a geometry was allocated to the Royal Mail record. Where a Royal Mail record is matched to a Local Authority record, the geometry will be assigned from the matched record. Where a Royal Mail record cannot be directly matched, geometry will be assigned by reference to a parent record, a street, or records which share the postcode unit, sector, district or area – in the listed order of preference. Where none of the listed methods are available, the geometry will be allocated to an internal centre point for the Local Authority area or Island in which the Royal Mail address is located.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: geometryallocationmethodvalue

    • Max Length: 25

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 25

    Describes the reason that the Royal Mail record has not been matched to a Local Authority record.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 100

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The date on which the Unmatched Reason value was captured.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The Unique Property Reference Number (UPRN) to which a Unique Delivery Point Reference Number (UDPRN) has been matched.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The feature type of the Unique Property Reference Number (UPRN) to which the Unique Delivery Point Reference Number (UDPRN) has been matched.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: matchedaddressfeaturetypevalue

    • Max Length: 25

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.1, 2.0

    Indicates whether a matched Local Authority Unique Property Reference Number (UPRN) is considered to be the primary match by GeoPlace and / or the relevant Local Authority. This attribute is particularly useful when a Unique Delivery Point Reference Number (UDPRN) is matched to multiple UPRNs as it will provide a one-to-one relationship between the UPRN and UDPRN.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: yesnovalue

    • Max Length: 3

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0

    A description of the relationship assigned between the Unique Delivery Point Reference Number (UDPRN) and the Unique Property Reference Number (UPRN). Where a Postcode Address File (PAF) record relates directly to a Local Authority record, this is set to ‘Direct.’ If a ‘Direct’ match cannot be found, a PAF record may be matched to a Parent, Neighbour or Street record in Local Authority data, in order to estimate a position for the PAF record.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: rmtolamatchtypevalue

    • Max Length: 20

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.1, 2.0

    The date on which the match was made between the Unique Delivery Point Reference Number (UDPRN) and the Unique Property Reference Number (UPRN).

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    The method by which the match was made.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: matchmethodvalue

    • Max Length: 10

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    Describes the organisation which made the match between the Royal Mail record and the Local Authority record.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: matchingorganisationvalue

    • Max Length: 25

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.1, 2.0

    2.0

    08 October 2026

    Ongoing

    Data schema versioning

    🔃 Data schema version table

    Major version increment. New attribution added for Full Address, Country, Primary UPRN Match, Postcode Area, Postcode District, Postcode Sector, PIF (Postcode Information File) Checksum Digit and PIF Display Text.

    The Postcode, Post Town, Welsh Post Town, Geometry Allocation Method and Positional Accuracy attributes are now filterable in OS Select+Build.

    New Multiple Residence, Delivery Point Alias and Other Alias Related Components added.

    Temporal filtering

    🆕 Related components

    🔃 Feature type attributes

    Comma-separated values (CSV) file format is universally supported for easy ingestion into all major database products. Before loading OS NGD data contained in CSV files into a database, it is necessary to create relevant tables. Data definition language (DDL) statements for PostgreSQL, SQL Server and Oracle can be accessed in our .

    For instructions on loading CSV files, see the guide.

    udprn

    versiondate

    versionavailablefromdate

    versionavailabletodate

    changetype

    theme

    description

    organisationname

    departmentname

    subbuildingname

    buildingname

    buildingnumber

    dependentthoroughfare

    thoroughfare

    doubledependentlocality

    dependentlocality

    posttown

    postcode

    🆕 postcodearea

    🆕 postcodedistrict

    There are certain non-geographic districts. In these instances, a district code is allocated to cover all large users in the postcode area. For more information about the postcode, please consult chapter one 'Structure of a PAF address' of the .

    🆕 postcodesector

    🆕 pifchecksumdigit

    All Postcode Address File (PAF) Mainfile addresses have associated Postcode Information File (PIF) attribution, although this attribution may present as null where the daily publication PAF Mainfile address has been created or edited and has not yet appeared in the subsequent monthly publication of PIF.

    All PIF attribution will appear as null upon initial release of v2.0 of the Royal Mail Address Feature Type, with publication in the OS NGD expected to begin in 2027.

    🆕 pifdisplaytext

    All Postcode Address File (PAF) Mainfile addresses have associated Postcode Information File (PIF) attribution, although this attribution may present as null where the daily publication PAF Mainfile address has been created or edited and has not yet appeared in the subsequent monthly publication of PIF.

    All PIF attribution will appear as null upon initial release of v2.0 of the Royal Mail Address Feature Type, with publication in the OS NGD expected to begin in 2027.

    postcodetype

    🆕 country

    🆕 fulladdress

    deliverypointsuffix

    welshdependentthoroughfare

    welshthoroughfare

    welshdoubledependentlocality

    welshdependentlocality

    welshposttown

    poboxnumber

    updatedate

    entrydate

    easting

    northing

    latitude

    longitude

    geometry

    positionalaccuracy

    geometryallocationmethod

    unmatchedreason

    unmatchedreasondate

    uprn

    matchedaddressfeaturetype

    🆕 primaryuprnmatch

    matchtype

    matchdate

    matchmethod

    matchingorganisation

    Non-Addressable Object

    The Non-Addressable Object Feature Type represents local authority and Ordnance Survey captured features that are currently live but are objects that would not be expected to be able to receive mail or deliveries. These objects typically represent structures or sites rather than buildings that somebody could conceivably live, work or engage in leisure activities within. For example, ponds and static water sites, public parks and telephone boxes.

    The following table provides details about this feature type’s data schema versions, including the reasons behind the changes and the related launch date when each version went live.

    Version ↓
    Launch Date
    Latest Date
    Change

    Pre-Build Address

    The Pre-Build Address Feature Type represents local authority addresses that will be able to receive mail, deliveries or services, where the property is either yet to be built but has been granted planning permission, or is under construction. Pre-build addresses can take the format of a development site, a plot number, or a definitive address for property units.

    The following table provides details about this feature type’s data schema versions, including the reasons behind the changes and the related launch date when each version went live.

    Version ↓
    Launch Date
    Latest Date
    Change

    Non-Addressable Object

    The Non-Addressable Object Feature Type represents local authority and Ordnance Survey captured features that are currently live but are objects that would not be expected to be able to receive mail or deliveries. These objects typically represent structures or sites rather than buildings that somebody could conceivably live, work or engage in leisure activities within. For example, ponds and static water sites, public parks and telephone boxes.

    The following table provides details about this feature type’s data schema versions, including the reasons behind the changes and the related launch date when each version went live.

    Version ↓
    Launch Date
    Latest Date
    Change

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Data Schema Version: 1.1

    Data Schema Version: 1.1

    Data Schema Version: 1.1

    Max Length: 25

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1

  • Loading OS NGD CSV files into databases

    Note

    Note

    Note

    royalmailaddressdescriptionvalue
    positionalaccuracyvalue
    geometryallocationmethodvalue
    OS NGD Resources GitHub repository
    Getting Started with CSV
    Royal Mail Programmer's Guide

    Ongoing

    Major version increment implementing the following changes:

    • Extended the max length of the Postcode Source, Full Address, Alternate Language Full Address, Sub Name, Alternate Language Sub Name and Build Status attributes.

    • Modified the associated code lists for the Description, Positional Accuracy and Postcode Source attributes.

    • Added download filters for Primary Classification Description, Secondary Classification Description, and Tertiary Classification Description attributes.

    2.0

    28 March 2023

    Ongoing

    Major version increment adding new attribution for Full Address, Alternate Language Full Address, Lowest Floor Level, Highest Floor Level, Primary Classification Description, Secondary Classification Description, Tertiary Classification Description and Quaternary Classification Description.

    1.0

    02 November 2022

    Ongoing

    Initial launch of the Non-Addressable Object Feature Type.

    Please see Data schema versioning for in-depth information about data schema versioning in the OS NGD.

    Temporal filtering allows you to order a one-off snapshot of data from the OS NGD from a current or past date. It is an optional step when you create a new data package in OS Select+Build (the OS NGD download service).

    The earliest and latest dates on which you can request a one-off snapshot of a date in the past for this feature type's data schema versions are indicated in the Data schema version table above. Please note that any data temporally filtered earlier than the specified launch date indicated in the table for the data schema versions may contain data inconsistencies.

    More information about temporal filtering on OS NGD feature types is available from the Getting started with temporal filtering guide.

    The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

    Unique Property Reference Number (UPRN) assigned by a local custodian or Ordnance Survey as a persistent identifier.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Date when the version was last updated.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The date this version of the feature became the latest version.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The date this version of the feature was superseded by an update or ceased to exist.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The type of change that generated a new version of the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: changetypevalue

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The OS NGD theme to which this feature belongs.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: themevalue

    • Max Length: 40

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    A single descriptive value intended for a quick understanding of what the feature represents.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressdescriptionvalue

    • Code List Version: 2.0

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version: 1.0

    The name of the organisation operating from the address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 100

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    The organisation name is the business name given to an Address 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.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 100

    Text concatenation of 'PO BOX' and the Post Office Box (PO Box) number or the British Forces Post Office (BFPO) number.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 13

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The Sub Name is the secondary description for subdivisions of properties. For example: Sub Name: 'CRYNANT LIBRARY', Name: 'CRYNANT COMMUNITY CENTRE'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 500

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    The name is the English language primary description applied to an address, for example: 'SWANSEA UNIVERSITY BAY CAMPUS' (Welsh: 'CAMPWS Y BAE PRIFYSGOL ABERTAWE'). This attribute will also include numbers when the name contains 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 name will be a blend of distinctive and descriptive naming, for example, RAILWAY TAVERN (PUBLIC HOUSE) or THE COURT ROYAL (HOTEL).

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The number gives a unique numeric identifier for addresses on a given street, for example, '11' (per Local Authority Street Naming and Numbering conventions). This includes numbers that contain a range, decimals or non-numeric characters, for example, 1-11 and 10A.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 13

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Name, number or descriptor that identifies the nearest accessible Street that an Address is located on or close to.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 100

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the area or geographical identifier within a town, settlement, village or hamlet that an address is located within. For example, a locality may be a suburb, housing estate or commercial estate.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the settlement that the Street is located within. Where a settlement can be a City, Town, Village, Hamlet or Parish.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the island upon which an Address is located.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The postcode unit that the Address is situated within. A postcode is an abbreviated form of address, made up of combinations of between five and seven alphanumeric characters. These alphanumeric characters are used by Royal Mail to help with the automated sorting of mail. A postcode may cover between 1 and 100 addresses. Postcodes (for example, NW6 4DP) are comprised of two components. The first component is the outward code (or ‘outcode’), which is the first two to four characters of a postcode, constituting the postcode area and the postcode district, for example, NW6. The outward code is the part of the postcode that enables mail to be sent from the accepting office to the correct area for delivery. The second component of a postcode is the inward code (or ‘incode’), which is the last three characters of the postcode, constituting the postcode sector and the postcode unit, for example, 4DP. The inward code is used to sort mail at the local delivery office. This field will contain the Royal Mail Postcode Address File (PAF) postcode where the Local Authority address has been matched to PAF. Where a match has not been made, the postcode information is sourced from Local Authority assigned data. In cases where the Local Authority do not hold a valid postcode, a spatial nearest neighbour function is used to spatially derive the postcode from the closest Address with a valid postcode.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 8

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Concatenation of the following address components: Organisation (Pre-Build and Built Address Feature Types only), Sub Name and / or Name and / or Number, Street Name, Locality, Town Name, Island Name and Postcode Locator.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 1 000

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 500

    • OS Select+Build Filterable: No

    Name of the geographical territory that the Address is located within, where a geographical territory represents either a devolved country or an island nation.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: countryvalue

    • Max Length: 16

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    The Alternate Language Sub Name is the alternate language secondary description for subdivisions of properties. For example: Alternate Language Sub Name: 'LLYFRGELL Y CREUNANT', Alternate Language Name: 'CANOLFAN CYMUNED CREUNANT'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 500

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    The Alternate Language Name is the alternate language primary description applied to an address, for example: 'CAMPWS Y BAE PRIFYSGOL ABERTAWE' (English: 'SWANSEA UNIVERSITY BAY CAMPUS'). This attribute may also include numbers when the name contains 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 name will be a blend of distinctive and descriptive naming, for example, RAILWAY TAVERN (PUBLIC HOUSE) or THE COURT ROYAL (HOTEL).

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The Alternate Language Number gives a unique numeric identifier for addresses on each street, for example, '11' (per Local Authority Street Naming and Numbering conventions). Numbers that contain a range, decimals or non-numeric characters do not appear in this field but will be found in the Name or the Sub Name attributes.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 13

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Name, number or descriptor that identifies the nearest accessable street that an Address is located on or close to, defined in either Welsh (cym) or Gaelic / Scottish Gaelic (gla).

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 100

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the area or geographical identifier within a town, settlement, village or hamlet that an address is located within, defined in either Welsh (cym) or Gaelic / Scottish Gaelic (gla). For example, a locality may be a suburb, housing estate or commercial estate.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    The name of the settlement that the address is located within, defined in either Welsh (cym) or Gaelic / Scottish Gaelic (gla). A settlement can be a City, Town, Village, Hamlet or Parish.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the island upon which an Address is located.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    ISO 3166-3 Language Code for Welsh or Gaelic / Scottish Gaelic.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: languagevalue

    • Max Length: 3

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Concatenation of the following alternate language address components: Organisation (Pre-Build and Built Address Feature Types only), Alternate Language Sub Name and / or Alternate Language Name and / or Alternate Language Number, Alternate Language Street Name, Alternate Language Locality, Alternate Language Town Name, Alternate Language Island Name and Postcode Locator.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 1 000

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 500

    • OS Select+Build Filterable: No

    Floor level represents either: the access point to the Address, or the floor level or levels that the Address is located on fully occupies or represents occupiable space within the property.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 30

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    In cases where the Floor Level attribute contains a list of floor levels (for example, where a commercial organisation occupies multiple levels within a building), the first value provided will be taken as the lowest floor level. For example, where Floor Level attribute values are given as -1, 0, 1, 2, 3, the Lowest Floor Level is -1. Mezzanine levels may be represented by a partial number, for example, 1.5. If the Floor Level attribute only contains one value, that value will also be used by the Lowest Floor Level attribute.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 3

    • Scale: 1

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0, 3.0

    In cases where the Floor Level attribute contains a list of floor levels (for example, where a commercial organisation occupies multiple levels within a building), the last value provided will be taken as the highest floor level. For example, where Floor Level attribute values are given as -1, 0, 1, 2, 3, the Highest Floor Level is 3. Mezzanine levels may be represented by a partial number, for example, 1.5. If the Floor Level attribute only contains one value, that value will also be used by the Highest Floor Level attribute.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 3

    • Scale: 1

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0, 3.0

    Alphanumeric code used to classify the object using the AddressBase Classification Scheme, which is available to download from the AddressBase Classification Scheme page of the OS Download Products’ Documentation site.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressclassificationcodevalue

    • Max Length: 6

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Description of the classification code as defined in the AddressBase Classification Scheme, which is available to download from the AddressBase Classification Scheme page of the OS Download Products’ Documentation site.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressclassificationdescriptionvalue

    • Max Length: 230

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    A descriptive term used to describe the primary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressprimaryclassificationdescriptionvalue

    • Max Length: 120

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0, 3.0

    A descriptive term used to describe the secondary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Code List Name: addresssecondaryclassificationdescriptionvalue

    • Nullable: true

    • Max Length: 120

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0, 3.0

    A descriptive term or collection of terms used to describe the tertiary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: addresstertiaryclassificationdescriptionvalue

    • Max Length: 120

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 3.0

    A descriptive term used to describe the tertiary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 120

    A descriptive term or collection of terms used to describe the quaternary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: addressquaternaryclassificationdescriptionvalue

    • Max Length: 120

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0, 3.0

    A description of the build status of the Address, for example, 'Built Complete'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: buildstatusvalue

    • Code List Version: 2.0

    • Max Length: 18

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 3.0

    A description of the build status of the land and property unit represented by an Address, for example, 'Built In Use'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version:

    Date when the address entered the lifecycle state given in Build Status.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    Date when the land and property unit entered the lifecycle state given in Build Status.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0

    The lifecycle status of a given Address, for example, 'Provisional' and 'Approved'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressstatusvalue

    • Max Length: 11

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Identifies the source of the postcode assigned to an address. This attribute can be used to identify properties capable of receiving mail as defined by Royal Mail for PAF matched address records, or as defined by Local Authorities for records which are not PAF matched but which are believed to be capable of receiving mail. For example, flats behind a front door with single letter box.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressbasepostalvalue

    • Code List Version: 2.0

    • Max Length: 148

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version: 1.0

    Unique Property Reference Number (UPRN) of the parent record if a parent-child relationship exists.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    In instances where an address sits in a hierarchy (for example, Child UPRN – Parent UPRN – Grandparent UPRN), the Root UPRN will display the Unique Property Reference Number (UPRN) for the top level Addressable Object in the parent-child structure, which in this example is the Grandparent UPRN.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    In instances where an address sits in a hierarchy (for example, Child UPRN – Parent UPRN – Grandparent UPRN), the Hierarchy Level attribute describes the position of the given UPRN within the overall set of relationships. For example, FLAT 1 is the Child UPRN at the lowest level and its Hierarchy Level will be 3; its Parent UPRN is BLOCK H, which will have a Hierarchy Level of 2; BLOCK H has, in turn, a Parent UPRN of EXETER UNIVERSITY, which will have a Hierarchy Level of 1.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The Unique Street Reference Number (USRN), a unique and persistent identifier of a Street which is assigned by the Roads or Highway Authority.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Description of the type of match made between the Unique Property Reference Number (UPRN) and its Unique Street Reference Number (USRN). A value of 1 is matched manually to the most accessible USRN, and a value of 2 is matched spatially to the nearest USRN, which may not be the nearest accessible street.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: usrnmatchindicatorvalue

    • Max Length: 17

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Numeric code identifying the authority responsible for assigning the Unique Property Reference Number (UPRN), creating and maintaining the address record.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the authority responsible for assigning the Unique Property Reference Number (UPRN), creating and maintaining the address record.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    The Office for National Statistics Governmental Statistical Service (GSS) code representing the lower tier local authority.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 9

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    X coordinate defining the position of the object in accordance with the British National Grid (EPSG:27700) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 8

    • Scale: 2

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Y coordinate defining the position of the object in accordance with the British National Grid (EPSG:27700) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 2

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Value defining the latitude of the Address location in accordance with the ETRS89 (EPSG:4258) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 7

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Value defining the longitude of the Address location in accordance with the ETRS89 (EPSG:4258) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 7

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Geometry for the feature.

    • Data Types: Geometry (GPKG), WKT (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    • Geometry Type: Point

    Local Authority assigned value giving a description of the accuracy of the coordinate position allocated to the Address location, for example, 'Central Internal Position' of a building.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: positionalaccuracyvalue

    • Code List Version: 2.0

    • Max Length: 25

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version: 1.0

    The date on which this record was inserted into the Local Authority database.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The date on which the record ceased to exist.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Selected related components are provided for the Non-Addressable Object Feature Type.

    Customers taking data schema version 1.0 or 2.0 of the Non-Addressable Object Feature Type in GeoPackage format will receive the following in their data package:

    • Feature type: Non-Addressable Object

    • Related components: Alternate Address, Postal Address, Other Classification and Related Entity

    Customers taking data schema version 3.0 onward of the Non-Addressable Object Feature Type in GeoPackage format will receive the following in their data package:

    • Feature type: Non-Addressable Object

    • Related components: Alternate Address, Other Classification and Related Entity

    Please see the Address Related Components page for more information about the related components and how to handle them.

    3.0

    Data schema versioning

    Data schema version table

    30 September 2025

    Temporal filtering

    Feature type attributes

    Comma-separated values (CSV) file format is universally supported for easy ingestion into all major database products. Before loading OS NGD data contained in CSV files into a database, it is necessary to create relevant tables. Data definition language (DDL) statements for PostgreSQL, SQL Server and Oracle can be accessed in our .

    For instructions on loading CSV files, see the guide.

    uprn

    versiondate

    versionavailablefromdate

    versionavailabletodate

    changetype

    theme

    description

    organisationname

    poboxnumber

    subname

    name

    number

    streetname

    locality

    townname

    islandname

    Note: This attribute is currently only populated in the OS Islands Address Collection.

    postcode

    fulladdress

    country

    alternatelanguagesubname

    alternatelanguagename

    alternatelanguagenumber

    alternatelanguagestreetname

    alternatelanguagelocality

    alternatelanguagetownname

    alternatelanguageislandname

    Note: This attribute is currently only populated in the OS Islands Address Collection.

    alternatelanguage

    alternatelanguagefulladdress

    floorlevel

    lowestfloorlevel

    This attribute is derived from Floor Level attribute data. Where the Floor Level field is NULL, Lowest Floor Level values will also be NULL.

    highestfloorlevel

    This attribute is derived from Floor Level attribute data. Where the Floor Level field is NULL, Highest Floor Level values will also be NULL.

    classificationcode

    classificationdescription

    primaryclassificationdescription

    secondaryclassificationdescription

    tertiaryclassificationdescription

    quaternaryclassificationdescription

    buildstatus

    buildstatusdate

    addressstatus

    postcodesource

    parentuprn

    rootuprn

    hierarchylevel

    usrn

    usrnmatchindicator

    localcustodiancode

    localcustodiandescription

    lowertierlocalauthoritygsscode

    easting

    northing

    latitude

    longitude

    geometry

    positionalaccuracy

    effectivestartdate

    effectiveenddate

    🆕 Related components

    Ongoing

    Major version increment implementing the following changes:

    • Extended the max length of the Postcode Source, Full Address, Alternate Language Full Address, Sub Name, Alternate Language Sub Name and Build Status attributes.

    • Modified the associated code lists for the Description, Positional Accuracy and Postcode Source attributes.

    • Added download filters for Primary Classification Description, Secondary Classification Description, and Tertiary Classification Description attributes.

    2.0

    28 March 2023

    Ongoing

    Major version increment adding new attribution for Full Address, Alternate Language Full Address, Lowest Floor Level, Highest Floor Level, Primary Classification Description, Secondary Classification Description, Tertiary Classification Description and Quaternary Classification Description.

    1.0

    02 November 2022

    Ongoing

    Initial launch of the Pre-Build Address Feature Type.

    Please see Data schema versioning for in-depth information about data schema versioning in the OS NGD.

    Temporal filtering allows you to order a one-off snapshot of data from the OS NGD from a current or past date. It is an optional step when you create a new data package in OS Select+Build (the OS NGD download service).

    The earliest and latest dates on which you can request a one-off snapshot of a date in the past for this feature type's data schema versions are indicated in the Data schema version table above. Please note that any data temporally filtered earlier than the specified launch date indicated in the table for the data schema versions may contain data inconsistencies.

    More information about temporal filtering on OS NGD feature types is available from the Getting started with temporal filtering guide.

    The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

    Unique Property Reference Number (UPRN) assigned by a local custodian or Ordnance Survey as a persistent identifier.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Date when the version was last updated.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The date this version of the feature became the latest version.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The date this version of the feature was superseded by an update or ceased to exist.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The type of change that generated a new version of the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: changetypevalue

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The OS NGD theme to which this feature belongs.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: themevalue

    • Max Length: 40

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    A single descriptive value intended for a quick understanding of what the feature represents.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressdescriptionvalue

    • Code List Version: 2.0

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version: 1.0

    The name of the organisation operating from the address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 100

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    The organisation name is the business name given to an Address 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.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 100

    Text concatenation of 'PO BOX' and the Post Office Box (PO Box) number or the British Forces Post Office (BFPO) number.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 13

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The Sub Name is the secondary description for subdivisions of properties. For example: Sub Name: 'CRYNANT LIBRARY', Name: 'CRYNANT COMMUNITY CENTRE'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 500

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    The name is the English language primary description applied to an address, for example: 'SWANSEA UNIVERSITY BAY CAMPUS' (Welsh: 'CAMPWS Y BAE PRIFYSGOL ABERTAWE'). This attribute will also include numbers when the name contains 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 name will be a blend of distinctive and descriptive naming, for example, RAILWAY TAVERN (PUBLIC HOUSE) or THE COURT ROYAL (HOTEL).

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The number gives a unique numeric identifier for addresses on a given street, for example, '11' (per Local Authority Street Naming and Numbering conventions). This includes numbers that contain a range, decimals or non-numeric characters, for example, 1-11 and 10A.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 13

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Name, number or descriptor that identifies the nearest accessible Street that an Address is located on or close to.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 100

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the area or geographical identifier within a town, settlement, village or hamlet that an address is located within. For example, a locality may be a suburb, housing estate or commercial estate.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the settlement that the Street is located within. Where a settlement can be a City, Town, Village, Hamlet or Parish.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the island upon which an Address is located.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The postcode unit that the Address is situated within. A postcode is an abbreviated form of address, made up of combinations of between five and seven alphanumeric characters. These alphanumeric characters are used by Royal Mail to help with the automated sorting of mail. A postcode may cover between 1 and 100 addresses. Postcodes (for example, NW6 4DP) are comprised of two components. The first component is the outward code (or ‘outcode’), which is the first two to four characters of a postcode, constituting the postcode area and the postcode district, for example, NW6. The outward code is the part of the postcode that enables mail to be sent from the accepting office to the correct area for delivery. The second component of a postcode is the inward code (or ‘incode’), which is the last three characters of the postcode, constituting the postcode sector and the postcode unit, for example, 4DP. The inward code is used to sort mail at the local delivery office. This field will contain the Royal Mail Postcode Address File (PAF) postcode where the Local Authority address has been matched to PAF. Where a match has not been made, the postcode information is sourced from Local Authority assigned data. In cases where the Local Authority do not hold a valid postcode, a spatial nearest neighbour function is used to spatially derive the postcode from the closest Address with a valid postcode.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 8

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Concatenation of the following address components: Organisation (Pre-Build and Built Address Feature Types only), Sub Name and / or Name and / or Number, Street Name, Locality, Town Name, Island Name and Postcode Locator.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 1 000

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 500

    • OS Select+Build Filterable: No

    Name of the geographical territory that the Address is located within, where a geographical territory represents either a devolved country or an island nation.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: countryvalue

    • Max Length: 16

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    The Alternate Language Sub Name is the alternate language secondary description for subdivisions of properties. For example: Alternate Language Sub Name: 'LLYFRGELL Y CREUNANT', Alternate Language Name: 'CANOLFAN CYMUNED CREUNANT'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 500

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    The Alternate Language Name is the alternate language primary description applied to an address, for example: 'CAMPWS Y BAE PRIFYSGOL ABERTAWE' (English: 'SWANSEA UNIVERSITY BAY CAMPUS'). This attribute may also include numbers when the name contains 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 name will be a blend of distinctive and descriptive naming, for example, RAILWAY TAVERN (PUBLIC HOUSE) or THE COURT ROYAL (HOTEL).

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The Alternate Language Number gives a unique numeric identifier for addresses on each street, for example, '11' (per Local Authority Street Naming and Numbering conventions). Numbers that contain a range, decimals or non-numeric characters do not appear in this field but will be found in the Name or the Sub Name attributes.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 13

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Name, number or descriptor that identifies the nearest accessable street that an Address is located on or close to, defined in either Welsh (cym) or Gaelic / Scottish Gaelic (gla).

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 100

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the area or geographical identifier within a town, settlement, village or hamlet that an address is located within, defined in either Welsh (cym) or Gaelic / Scottish Gaelic (gla). For example, a locality may be a suburb, housing estate or commercial estate.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    The name of the settlement that the address is located within, defined in either Welsh (cym) or Gaelic / Scottish Gaelic (gla). A settlement can be a City, Town, Village, Hamlet or Parish.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the island upon which an Address is located.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    ISO 3166-3 Language Code for Welsh or Gaelic / Scottish Gaelic.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: languagevalue

    • Max Length: 3

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Concatenation of the following alternate language address components: Organisation (Pre-Build and Built Address Feature Types only), Alternate Language Sub Name and / or Alternate Language Name and / or Alternate Language Number, Alternate Language Street Name, Alternate Language Locality, Alternate Language Town Name, Alternate Language Island Name and Postcode Locator.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 1 000

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 500

    • OS Select+Build Filterable: No

    Floor level represents either: the access point to the Address, or the floor level or levels that the Address is located on fully occupies or represents occupiable space within the property.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 30

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    In cases where the Floor Level attribute contains a list of floor levels (for example, where a commercial organisation occupies multiple levels within a building), the first value provided will be taken as the lowest floor level. For example, where Floor Level attribute values are given as -1, 0, 1, 2, 3, the Lowest Floor Level is -1. Mezzanine levels may be represented by a partial number, for example, 1.5. If the Floor Level attribute only contains one value, that value will also be used by the Lowest Floor Level attribute.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 3

    • Scale: 1

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0, 3.0

    In cases where the Floor Level attribute contains a list of floor levels (for example, where a commercial organisation occupies multiple levels within a building), the last value provided will be taken as the highest floor level. For example, where Floor Level attribute values are given as -1, 0, 1, 2, 3, the Highest Floor Level is 3. Mezzanine levels may be represented by a partial number, for example, 1.5. If the Floor Level attribute only contains one value, that value will also be used by the Highest Floor Level attribute.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 3

    • Scale: 1

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0, 3.0

    Alphanumeric code used to classify the object using the AddressBase Classification Scheme, which is available to download from the AddressBase Classification Scheme page of the OS Download Products’ Documentation site.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressclassificationcodevalue

    • Max Length: 6

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Description of the classification code as defined in the AddressBase Classification Scheme, which is available to download from the AddressBase Classification Scheme page of the OS Download Products’ Documentation site.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressclassificationdescriptionvalue

    • Max Length: 230

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    A descriptive term used to describe the primary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressprimaryclassificationdescriptionvalue

    • Max Length: 120

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0, 3.0

    A descriptive term used to describe the secondary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Code List Name: addresssecondaryclassificationdescriptionvalue

    • Nullable: true

    • Max Length: 120

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0, 3.0

    A descriptive term or collection of terms used to describe the tertiary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: addresstertiaryclassificationdescriptionvalue

    • Max Length: 120

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 3.0

    A descriptive term used to describe the tertiary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 120

    A descriptive term or collection of terms used to describe the quaternary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: addressquaternaryclassificationdescriptionvalue

    • Max Length: 120

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0, 3.0

    A description of the build status of the Address, for example, 'Built Complete'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: buildstatusvalue

    • Code List Version: 2.0

    • Max Length: 18

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 3.0

    A description of the build status of the land and property unit represented by an Address, for example, 'Built In Use'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version:

    Date when the address entered the lifecycle state given in Build Status.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    Date when the land and property unit entered the lifecycle state given in Build Status.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0

    The lifecycle status of a given Address, for example, 'Provisional' and 'Approved'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressstatusvalue

    • Max Length: 11

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Identifies the source of the postcode assigned to an address. This attribute can be used to identify properties capable of receiving mail as defined by Royal Mail for PAF matched address records, or as defined by Local Authorities for records which are not PAF matched but which are believed to be capable of receiving mail. For example, flats behind a front door with single letter box.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressbasepostalvalue

    • Code List Version: 2.0

    • Max Length: 148

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version: 1.0

    Unique Property Reference Number (UPRN) of the parent record if a parent-child relationship exists.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    In instances where an address sits in a hierarchy (for example, Child UPRN – Parent UPRN – Grandparent UPRN), the Root UPRN will display the Unique Property Reference Number (UPRN) for the top level Addressable Object in the parent-child structure, which in this example is the Grandparent UPRN.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    In instances where an address sits in a hierarchy (for example, Child UPRN – Parent UPRN – Grandparent UPRN), the Hierarchy Level attribute describes the position of the given UPRN within the overall set of relationships. For example, FLAT 1 is the Child UPRN at the lowest level and its Hierarchy Level will be 3; its Parent UPRN is BLOCK H, which will have a Hierarchy Level of 2; BLOCK H has, in turn, a Parent UPRN of EXETER UNIVERSITY, which will have a Hierarchy Level of 1.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The Unique Street Reference Number (USRN), a unique and persistent identifier of a Street which is assigned by the Roads or Highway Authority.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Description of the type of match made between the Unique Property Reference Number (UPRN) and its Unique Street Reference Number (USRN). A value of 1 is matched manually to the most accessible USRN, and a value of 2 is matched spatially to the nearest USRN, which may not be the nearest accessible street.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: usrnmatchindicatorvalue

    • Max Length: 17

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Numeric code identifying the authority responsible for assigning the Unique Property Reference Number (UPRN), creating and maintaining the address record.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the authority responsible for assigning the Unique Property Reference Number (UPRN), creating and maintaining the address record.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    The Office for National Statistics Governmental Statistical Service (GSS) code representing the lower tier local authority.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 9

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    X coordinate defining the position of the object in accordance with the British National Grid (EPSG:27700) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 8

    • Scale: 2

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Y coordinate defining the position of the object in accordance with the British National Grid (EPSG:27700) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 2

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Value defining the latitude of the Address location in accordance with the ETRS89 (EPSG:4258) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 7

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Value defining the longitude of the Address location in accordance with the ETRS89 (EPSG:4258) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 7

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Geometry for the feature.

    • Data Types: Geometry (GPKG), WKT (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    • Geometry Type: Point

    Local Authority assigned value giving a description of the accuracy of the coordinate position allocated to the Address location, for example, 'Central Internal Position' of a building.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: positionalaccuracyvalue

    • Code List Version: 2.0

    • Max Length: 25

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version: 1.0

    The date on which this record was inserted into the Local Authority database.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The date on which the record ceased to exist.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Selected related components are provided for the Pre-Build Address Feature Type.

    Customers taking data schema version 1.0 or 2.0 of the Pre-Build Address Feature Type in GeoPackage format will receive the following in their data package:

    • Feature type: Pre-Build Address

    • Related components: Alternate Address, Postal Address, Other Classification and Related Entity

    Customers taking data schema version 3.0 onward of the Pre-Build Address Feature Type in GeoPackage format will receive the following in their data package:

    • Feature type: Pre-Build Address

    • Related components: Alternate Address, Other Classification and Related Entity

    Please see the Address Related Components page for more information about the related components and how to handle them.

    3.0

    Data schema versioning

    Data schema version table

    30 September 2025

    Temporal filtering

    Feature type attributes

    Comma-separated values (CSV) file format is universally supported for easy ingestion into all major database products. Before loading OS NGD data contained in CSV files into a database, it is necessary to create relevant tables. Data definition language (DDL) statements for PostgreSQL, SQL Server and Oracle can be accessed in our .

    For instructions on loading CSV files, see the guide.

    uprn

    versiondate

    versionavailablefromdate

    versionavailabletodate

    changetype

    theme

    description

    organisationname

    poboxnumber

    subname

    name

    number

    streetname

    locality

    townname

    islandname

    Note: This attribute is currently only populated in the OS Islands Address Collection.

    postcode

    fulladdress

    country

    alternatelanguagesubname

    alternatelanguagename

    alternatelanguagenumber

    alternatelanguagestreetname

    alternatelanguagelocality

    alternatelanguagetownname

    alternatelanguageislandname

    Note: This attribute is currently only populated in the OS Islands Address Collection.

    alternatelanguage

    alternatelanguagefulladdress

    floorlevel

    lowestfloorlevel

    This attribute is derived from Floor Level attribute data. Where the Floor Level field is NULL, Lowest Floor Level values will also be NULL.

    highestfloorlevel

    This attribute is derived from Floor Level attribute data. Where the Floor Level field is NULL, Highest Floor Level values will also be NULL.

    classificationcode

    classificationdescription

    primaryclassificationdescription

    secondaryclassificationdescription

    tertiaryclassificationdescription

    quaternaryclassificationdescription

    buildstatus

    buildstatusdate

    addressstatus

    postcodesource

    parentuprn

    rootuprn

    hierarchylevel

    usrn

    usrnmatchindicator

    localcustodiancode

    localcustodiandescription

    lowertierlocalauthoritygsscode

    easting

    northing

    latitude

    longitude

    geometry

    positionalaccuracy

    effectivestartdate

    effectiveenddate

    🆕 Related components

    Ongoing

    Major version increment implementing the following changes:

    • Extended the max length of the Postcode Source, Full Address, Alternate Language Full Address, Sub Name, Alternate Language Sub Name and Build Status attributes.

    • Modified the associated code lists for the Description, Positional Accuracy and Postcode Source attributes.

    • Added download filters for Primary Classification Description, Secondary Classification Description, and Tertiary Classification Description attributes.

    • New associated code lists added to the Classification Code, Classification Description, Primary Classification Description, Secondary Classification Description, Tertiary Classification Description and Quaternary Classification Description attributes.

    2.0

    28 March 2023

    Ongoing

    Major version increment adding new attribution for Full Address, Alternate Language Full Address, Lowest Floor Level, Highest Floor Level, Primary Classification Description, Secondary Classification Description, Tertiary Classification Description and Quaternary Classification Description.

    1.0

    02 November 2022

    Ongoing

    Initial launch of the Non-Addressable Object Feature Type.

    Please see Data schema versioning for in-depth information about data schema versioning in the OS NGD.

    Temporal filtering allows you to order a one-off snapshot of data from the OS NGD from a current or past date. It is an optional step when you create a new data package in OS Select+Build (the OS NGD download service).

    The earliest and latest dates on which you can request a one-off snapshot of a date in the past for this feature type's data schema versions are indicated in the Data schema version table above. Please note that any data temporally filtered earlier than the specified launch date indicated in the table for the data schema versions may contain data inconsistencies.

    More information about temporal filtering on OS NGD feature types is available from the Getting started with temporal filtering guide.

    The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

    Unique Property Reference Number (UPRN) assigned by a local custodian or Ordnance Survey as a persistent identifier.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Date when the version was last updated.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The date this version of the feature became the latest version.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The date this version of the feature was superseded by an update or ceased to exist.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The type of change that generated a new version of the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: changetypevalue

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The OS NGD theme to which this feature belongs.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: themevalue

    • Max Length: 40

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    A single descriptive value intended for a quick understanding of what the feature represents.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressdescriptionvalue

    • Code List Version: 2.0

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version: 1.0

    The name of the organisation operating from the address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 100

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    The organisation name is the business name given to an Address 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.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 100

    Text concatenation of 'PO BOX' and the Post Office Box (PO Box) number or the British Forces Post Office (BFPO) number.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 13

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The Sub Name is the secondary description for subdivisions of properties. For example: Sub Name: 'CRYNANT LIBRARY', Name: 'CRYNANT COMMUNITY CENTRE'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 500

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    The name is the English language primary description applied to an address, for example: 'SWANSEA UNIVERSITY BAY CAMPUS' (Welsh: 'CAMPWS Y BAE PRIFYSGOL ABERTAWE'). This attribute will also include numbers when the name contains 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 name will be a blend of distinctive and descriptive naming, for example, RAILWAY TAVERN (PUBLIC HOUSE) or THE COURT ROYAL (HOTEL).

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The number gives a unique numeric identifier for addresses on a given street, for example, '11' (per Local Authority Street Naming and Numbering conventions). This includes numbers that contain a range, decimals or non-numeric characters, for example, 1-11 and 10A.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 13

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Name, number or descriptor that identifies the nearest accessible Street that an Address is located on or close to.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 100

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the area or geographical identifier within a town, settlement, village or hamlet that an address is located within. For example, a locality may be a suburb, housing estate or commercial estate.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the settlement that the Street is located within. Where a settlement can be a City, Town, Village, Hamlet or Parish.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the island upon which an Address is located.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The postcode unit that the Address is situated within. A postcode is an abbreviated form of address, made up of combinations of between five and seven alphanumeric characters. These alphanumeric characters are used by Royal Mail to help with the automated sorting of mail. A postcode may cover between 1 and 100 addresses. Postcodes (for example, NW6 4DP) are comprised of two components. The first component is the outward code (or ‘outcode’), which is the first two to four characters of a postcode, constituting the postcode area and the postcode district, for example, NW6. The outward code is the part of the postcode that enables mail to be sent from the accepting office to the correct area for delivery. The second component of a postcode is the inward code (or ‘incode’), which is the last three characters of the postcode, constituting the postcode sector and the postcode unit, for example, 4DP. The inward code is used to sort mail at the local delivery office. This field will contain the Royal Mail Postcode Address File (PAF) postcode where the Local Authority address has been matched to PAF. Where a match has not been made, the postcode information is sourced from Local Authority assigned data. In cases where the Local Authority do not hold a valid postcode, a spatial nearest neighbour function is used to spatially derive the postcode from the closest Address with a valid postcode.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 8

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Concatenation of the following address components: Organisation (Pre-Build and Built Address Feature Types only), Sub Name and / or Name and / or Number, Street Name, Locality, Town Name, Island Name and Postcode Locator.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 1 000

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 500

    • OS Select+Build Filterable: No

    Name of the geographical territory that the Address is located within, where a geographical territory represents either a devolved country or an island nation.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: countryvalue

    • Max Length: 16

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    The Alternate Language Sub Name is the alternate language secondary description for subdivisions of properties. For example: Alternate Language Sub Name: 'LLYFRGELL Y CREUNANT', Alternate Language Name: 'CANOLFAN CYMUNED CREUNANT'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 500

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    The Alternate Language Name is the alternate language primary description applied to an address, for example: 'CAMPWS Y BAE PRIFYSGOL ABERTAWE' (English: 'SWANSEA UNIVERSITY BAY CAMPUS'). This attribute may also include numbers when the name contains 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 name will be a blend of distinctive and descriptive naming, for example, RAILWAY TAVERN (PUBLIC HOUSE) or THE COURT ROYAL (HOTEL).

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The Alternate Language Number gives a unique numeric identifier for addresses on each street, for example, '11' (per Local Authority Street Naming and Numbering conventions). Numbers that contain a range, decimals or non-numeric characters do not appear in this field but will be found in the Name or the Sub Name attributes.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 13

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Name, number or descriptor that identifies the nearest accessable street that an Address is located on or close to, defined in either Welsh (cym) or Gaelic / Scottish Gaelic (gla).

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 100

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the area or geographical identifier within a town, settlement, village or hamlet that an address is located within, defined in either Welsh (cym) or Gaelic / Scottish Gaelic (gla). For example, a locality may be a suburb, housing estate or commercial estate.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    The name of the settlement that the address is located within, defined in either Welsh (cym) or Gaelic / Scottish Gaelic (gla). A settlement can be a City, Town, Village, Hamlet or Parish.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the island upon which an Address is located.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    ISO 3166-3 Language Code for Welsh or Gaelic / Scottish Gaelic.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: languagevalue

    • Max Length: 3

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Concatenation of the following alternate language address components: Organisation (Pre-Build and Built Address Feature Types only), Alternate Language Sub Name and / or Alternate Language Name and / or Alternate Language Number, Alternate Language Street Name, Alternate Language Locality, Alternate Language Town Name, Alternate Language Island Name and Postcode Locator.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 1 000

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 500

    • OS Select+Build Filterable: No

    Floor level represents either: the access point to the Address, or the floor level or levels that the Address is located on fully occupies or represents occupiable space within the property.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 30

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    In cases where the Floor Level attribute contains a list of floor levels (for example, where a commercial organisation occupies multiple levels within a building), the first value provided will be taken as the lowest floor level. For example, where Floor Level attribute values are given as -1, 0, 1, 2, 3, the Lowest Floor Level is -1. Mezzanine levels may be represented by a partial number, for example, 1.5. If the Floor Level attribute only contains one value, that value will also be used by the Lowest Floor Level attribute.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 3

    • Scale: 1

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0, 3.0

    In cases where the Floor Level attribute contains a list of floor levels (for example, where a commercial organisation occupies multiple levels within a building), the last value provided will be taken as the highest floor level. For example, where Floor Level attribute values are given as -1, 0, 1, 2, 3, the Highest Floor Level is 3. Mezzanine levels may be represented by a partial number, for example, 1.5. If the Floor Level attribute only contains one value, that value will also be used by the Highest Floor Level attribute.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 3

    • Scale: 1

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0, 3.0

    Alphanumeric code used to classify the object using the AddressBase Classification Scheme, which is available to download from the AddressBase Classification Scheme page of the OS Download Products’ Documentation site.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressclassificationcodevalue

    • Max Length: 6

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Description of the classification code as defined in the AddressBase Classification Scheme, which is available to download from the AddressBase Classification Scheme page of the OS Download Products’ Documentation site.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressclassificationdescriptionvalue

    • Max Length: 230

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    A descriptive term used to describe the primary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressprimaryclassificationdescriptionvalue

    • Max Length: 120

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0, 3.0

    A descriptive term used to describe the secondary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Code List Name: addresssecondaryclassificationdescriptionvalue

    • Nullable: true

    • Max Length: 120

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0, 3.0

    A descriptive term or collection of terms used to describe the tertiary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: addresstertiaryclassificationdescriptionvalue

    • Max Length: 120

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 3.0

    A descriptive term used to describe the tertiary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 120

    A descriptive term or collection of terms used to describe the quaternary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: addressquaternaryclassificationdescriptionvalue

    • Max Length: 120

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0, 3.0

    A description of the build status of the Address, for example, 'Built Complete'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: buildstatusvalue

    • Code List Version: 2.0

    • Max Length: 18

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 3.0

    A description of the build status of the land and property unit represented by an Address, for example, 'Built In Use'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version:

    Date when the address entered the lifecycle state given in Build Status.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    Date when the land and property unit entered the lifecycle state given in Build Status.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0

    The lifecycle status of a given Address, for example, 'Provisional' and 'Approved'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressstatusvalue

    • Max Length: 11

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Identifies the source of the postcode assigned to an address. This attribute can be used to identify properties capable of receiving mail as defined by Royal Mail for PAF matched address records, or as defined by Local Authorities for records which are not PAF matched but which are believed to be capable of receiving mail. For example, flats behind a front door with single letter box.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressbasepostalvalue

    • Code List Version: 2.0

    • Max Length: 148

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version: 1.0

    Unique Property Reference Number (UPRN) of the parent record if a parent-child relationship exists.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    In instances where an address sits in a hierarchy (for example, Child UPRN – Parent UPRN – Grandparent UPRN), the Root UPRN will display the Unique Property Reference Number (UPRN) for the top level Addressable Object in the parent-child structure, which in this example is the Grandparent UPRN.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    In instances where an address sits in a hierarchy (for example, Child UPRN – Parent UPRN – Grandparent UPRN), the Hierarchy Level attribute describes the position of the given UPRN within the overall set of relationships. For example, FLAT 1 is the Child UPRN at the lowest level and its Hierarchy Level will be 3; its Parent UPRN is BLOCK H, which will have a Hierarchy Level of 2; BLOCK H has, in turn, a Parent UPRN of EXETER UNIVERSITY, which will have a Hierarchy Level of 1.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The Unique Street Reference Number (USRN), a unique and persistent identifier of a Street which is assigned by the Roads or Highway Authority.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Description of the type of match made between the Unique Property Reference Number (UPRN) and its Unique Street Reference Number (USRN). A value of 1 is matched manually to the most accessible USRN, and a value of 2 is matched spatially to the nearest USRN, which may not be the nearest accessible street.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: usrnmatchindicatorvalue

    • Max Length: 17

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Numeric code identifying the authority responsible for assigning the Unique Property Reference Number (UPRN), creating and maintaining the address record.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the authority responsible for assigning the Unique Property Reference Number (UPRN), creating and maintaining the address record.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    The Office for National Statistics Governmental Statistical Service (GSS) code representing the lower tier local authority.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 9

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    X coordinate defining the position of the object in accordance with the British National Grid (EPSG:27700) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 8

    • Scale: 2

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Y coordinate defining the position of the object in accordance with the British National Grid (EPSG:27700) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 9

    • Scale: 2

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Value defining the latitude of the Address location in accordance with the ETRS89 (EPSG:4258) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 7

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Value defining the longitude of the Address location in accordance with the ETRS89 (EPSG:4258) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 7

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Geometry for the feature.

    • Data Types: Geometry (GPKG), WKT (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    • Geometry Type: Point

    Local Authority assigned value giving a description of the accuracy of the coordinate position allocated to the Address location, for example, 'Central Internal Position' of a building.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: positionalaccuracyvalue

    • Code List Version: 2.0

    • Max Length: 25

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version: 1.0

    The date on which this record was inserted into the Local Authority database.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The date on which the record ceased to exist.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Selected related components are provided for the Non-Addressable Object Feature Type.

    Customers taking data schema version 1.0 or 2.0 of the Non-Addressable Object Feature Type in GeoPackage format will receive the following in their data package:

    • Feature type: Non-Addressable Object

    • Related components: Alternate Address, Postal Address, Other Classification and Related Entity

    Customers taking data schema version 3.0 onward of the Non-Addressable Object Feature Type in GeoPackage format will receive the following in their data package:

    • Feature type: Non-Addressable Object

    • Related components: Alternate Address, Other Classification and Related Entity

    Please see the Address Related Components page for more information about the related components and how to handle them.

    3.0

    Data schema versioning

    Data schema version table

    30 September 2025

    Temporal filtering

    Feature type attributes

    Comma-separated values (CSV) file format is universally supported for easy ingestion into all major database products. Before loading OS NGD data contained in CSV files into a database, it is necessary to create relevant tables. Data definition language (DDL) statements for PostgreSQL, SQL Server and Oracle can be accessed in our .

    For instructions on loading CSV files, see the guide.

    uprn

    versiondate

    versionavailablefromdate

    versionavailabletodate

    changetype

    theme

    description

    organisationname

    poboxnumber

    subname

    name

    number

    streetname

    locality

    townname

    islandname

    Note: This attribute is currently only populated in the OS Islands Address Collection.

    postcode

    fulladdress

    country

    alternatelanguagesubname

    alternatelanguagename

    alternatelanguagenumber

    alternatelanguagestreetname

    alternatelanguagelocality

    alternatelanguagetownname

    alternatelanguageislandname

    Note: This attribute is currently only populated in the OS Islands Address Collection.

    alternatelanguage

    alternatelanguagefulladdress

    floorlevel

    lowestfloorlevel

    This attribute is derived from Floor Level attribute data. Where the Floor Level field is NULL, Lowest Floor Level values will also be NULL.

    highestfloorlevel

    This attribute is derived from Floor Level attribute data. Where the Floor Level field is NULL, Highest Floor Level values will also be NULL.

    classificationcode

    classificationdescription

    primaryclassificationdescription

    secondaryclassificationdescription

    tertiaryclassificationdescription

    quaternaryclassificationdescription

    buildstatus

    buildstatusdate

    addressstatus

    postcodesource

    parentuprn

    rootuprn

    hierarchylevel

    usrn

    usrnmatchindicator

    localcustodiancode

    localcustodiandescription

    lowertierlocalauthoritygsscode

    easting

    northing

    latitude

    longitude

    geometry

    positionalaccuracy

    effectivestartdate

    effectiveenddate

    🆕 Related components

    Historic Address

    The Historic Address Feature Type represents local authority addresses that are no longer in existence. This can occur as a result of demolition or the merging of two built properties to become one new single address, or the splitting of a single property into multiple flats for example.

    The following table provides details about this feature type’s data schema versions, including the reasons behind the changes and the related launch date when each version went live.

    Version ↓
    Launch Date
    Latest Date
    Change

    Historic Address

    The Historic Address Feature Type represents local authority addresses that are no longer in existence. This can occur as a result of demolition or the merging of two built properties to become one new single address, or the splitting of a single property into multiple flats for example.

    The following table provides details about this feature type’s data schema versions, including the reasons behind the changes and the related launch date when each version went live.

    Version ↓
    Launch Date
    Latest Date
    Change

    Max Length: 50

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0

  • OS Select+Build Filterable:
    No
  • Data Schema Version: 1.0, 2.0

  • Data Schema Version: 1.0, 2.0

    Data Schema Version: 2.0

    Data Schema Version: 1.0, 2.0

    Data Schema Version: 2.0

    OS Select+Build Filterable: Yes

  • Data Schema Version: 2.0

  • 1.0
  • Max Length: 12

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0, 2.0

  • Max Length: 75

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0, 2.0

  • Max Length: 25

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0, 2.0

  • New associated code lists added to the Classification Code, Classification Description, Primary Classification Description, Secondary Classification Description, Tertiary Classification Description and Quaternary Classification Description attributes.

    Loading OS NGD CSV files into databases

    addressdescriptionvalue
    addresstertiaryclassificationdescriptionvalue
    buildstatusvalue
    addressbasepostalvalue
    positionalaccuracyvalue
    OS NGD Resources GitHub repository
    Getting Started with CSV

    Max Length: 50

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0

  • OS Select+Build Filterable:
    No
  • Data Schema Version: 1.0, 2.0

  • Data Schema Version: 1.0, 2.0

    Data Schema Version: 2.0

    Data Schema Version: 1.0, 2.0

    Data Schema Version: 2.0

    OS Select+Build Filterable: Yes

  • Data Schema Version: 2.0

  • 1.0
  • Max Length: 12

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0, 2.0

  • Max Length: 75

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0, 2.0

  • Max Length: 25

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0, 2.0

  • New associated code lists added to the Classification Code, Classification Description, Primary Classification Description, Secondary Classification Description, Tertiary Classification Description and Quaternary Classification Description attributes.

    Loading OS NGD CSV files into databases

    addressdescriptionvalue
    addresstertiaryclassificationdescriptionvalue
    buildstatusvalue
    addressbasepostalvalue
    positionalaccuracyvalue
    OS NGD Resources GitHub repository
    Getting Started with CSV

    Max Length: 50

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0

  • OS Select+Build Filterable:
    No
  • Data Schema Version: 1.0, 2.0

  • Data Schema Version: 1.0, 2.0

    Data Schema Version: 2.0

    Data Schema Version: 1.0, 2.0

    Data Schema Version: 2.0

    OS Select+Build Filterable: Yes

  • Data Schema Version: 2.0

  • 1.0
  • Max Length: 12

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0, 2.0

  • Max Length: 75

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0, 2.0

  • Max Length: 25

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0, 2.0

  • Loading OS NGD CSV files into databases

    addressdescriptionvalue
    addresstertiaryclassificationdescriptionvalue
    buildstatusvalue
    addressbasepostalvalue
    positionalaccuracyvalue
    OS NGD Resources GitHub repository
    Getting Started with CSV

    Major version increment implementing the following changes:

    • Extended the max length of the Postcode Source, Full Address, Alternate Language Full Address, Sub Name, Alternate Language Sub Name and Build Status attributes.

    • Modified the associated code lists for the Description, Positional Accuracy and Postcode Source attributes.

    • Added download filters for Primary Classification Description, Secondary Classification Description, and Tertiary Classification Description attributes.

    • New associated code lists added to the Classification Code, Classification Description, Primary Classification Description, Secondary Classification Description, Tertiary Classification Description and Quaternary Classification Description attributes.

    2.0

    28 March 2023

    Ongoing

    Major version increment adding new attribution for Full Address, Alternate Language Full Address, Lowest Floor Level, Highest Floor Level, Primary Classification Description, Secondary Classification Description, Tertiary Classification Description and Quaternary Classification Description.

    1.0

    02 November 2022

    Ongoing

    Initial launch of the Historic Address Feature Type.

    Please see Data schema versioning for in-depth information about data schema versioning in the OS NGD.

    Temporal filtering allows you to order a one-off snapshot of data from the OS NGD from a current or past date. It is an optional step when you create a new data package in OS Select+Build (the OS NGD download service).

    The earliest and latest dates on which you can request a one-off snapshot of a date in the past for this feature type's data schema versions are indicated in the Data schema version table above. Please note that any data temporally filtered earlier than the specified launch date indicated in the table for the data schema versions may contain data inconsistencies.

    More information about temporal filtering on OS NGD feature types is available from the Getting started with temporal filtering guide.

    The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

    Unique Property Reference Number (UPRN) assigned by a local custodian or Ordnance Survey as a persistent identifier.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Date when the version was last updated.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The date this version of the feature became the latest version.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The date this version of the feature was superseded by an update or ceased to exist.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The type of change that generated a new version of the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: changetypevalue

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The OS NGD theme to which this feature belongs.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: themevalue

    • Max Length: 40

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    A single descriptive value intended for a quick understanding of what the feature represents.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressdescriptionvalue

    • Code List Version: 2.0

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version: 1.0

    The name of the organisation operating from the address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 100

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    The organisation name is the business name given to an Address 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.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 100

    Text concatenation of 'PO BOX' and the Post Office Box (PO Box) number or the British Forces Post Office (BFPO) number.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 13

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The Sub Name is the secondary description for subdivisions of properties. For example: Sub Name: 'CRYNANT LIBRARY', Name: 'CRYNANT COMMUNITY CENTRE'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 500

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    The name is the English language primary description applied to an address, for example: 'SWANSEA UNIVERSITY BAY CAMPUS' (Welsh: 'CAMPWS Y BAE PRIFYSGOL ABERTAWE'). This attribute will also include numbers when the name contains 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 name will be a blend of distinctive and descriptive naming, for example, RAILWAY TAVERN (PUBLIC HOUSE) or THE COURT ROYAL (HOTEL).

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The number gives a unique numeric identifier for addresses on a given street, for example, '11' (per Local Authority Street Naming and Numbering conventions). This includes numbers that contain a range, decimals or non-numeric characters, for example, 1-11 and 10A.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 13

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Name, number or descriptor that identifies the nearest accessible Street that an Address is located on or close to.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 100

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the area or geographical identifier within a town, settlement, village or hamlet that an address is located within. For example, a locality may be a suburb, housing estate or commercial estate.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the settlement that the Street is located within. Where a settlement can be a City, Town, Village, Hamlet or Parish.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the island upon which an Address is located.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The postcode unit that the Address is situated within. A postcode is an abbreviated form of address, made up of combinations of between five and seven alphanumeric characters. These alphanumeric characters are used by Royal Mail to help with the automated sorting of mail. A postcode may cover between 1 and 100 addresses. Postcodes (for example, NW6 4DP) are comprised of two components. The first component is the outward code (or ‘outcode’), which is the first two to four characters of a postcode, constituting the postcode area and the postcode district, for example, NW6. The outward code is the part of the postcode that enables mail to be sent from the accepting office to the correct area for delivery. The second component of a postcode is the inward code (or ‘incode’), which is the last three characters of the postcode, constituting the postcode sector and the postcode unit, for example, 4DP. The inward code is used to sort mail at the local delivery office. This field will contain the Royal Mail Postcode Address File (PAF) postcode where the Local Authority address has been matched to PAF. Where a match has not been made, the postcode information is sourced from Local Authority assigned data. In cases where the Local Authority do not hold a valid postcode, a spatial nearest neighbour function is used to spatially derive the postcode from the closest Address with a valid postcode.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 8

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Concatenation of the following address components: Organisation (Pre-Build and Built Address Feature Types only), Sub Name and / or Name and / or Number, Street Name, Locality, Town Name, Island Name and Postcode Locator.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 1 000

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 500

    • OS Select+Build Filterable: No

    Name of the geographical territory that the Address is located within, where a geographical territory represents either a devolved country or an island nation.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: countryvalue

    • Max Length: 16

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    The Alternate Language Sub Name is the alternate language secondary description for subdivisions of properties. For example: Alternate Language Sub Name: 'LLYFRGELL Y CREUNANT', Alternate Language Name: 'CANOLFAN CYMUNED CREUNANT'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 500

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    The Alternate Language Name is the alternate language primary description applied to an address, for example: 'CAMPWS Y BAE PRIFYSGOL ABERTAWE' (English: 'SWANSEA UNIVERSITY BAY CAMPUS'). This attribute may also include numbers when the name contains 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 name will be a blend of distinctive and descriptive naming, for example, RAILWAY TAVERN (PUBLIC HOUSE) or THE COURT ROYAL (HOTEL).

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The Alternate Language Number gives a unique numeric identifier for addresses on each street, for example, '11' (per Local Authority Street Naming and Numbering conventions). Numbers that contain a range, decimals or non-numeric characters do not appear in this field but will be found in the Name or the Sub Name attributes.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 13

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Name, number or descriptor that identifies the nearest accessable street that an Address is located on or close to, defined in either Welsh (cym) or Gaelic / Scottish Gaelic (gla).

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 100

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the area or geographical identifier within a town, settlement, village or hamlet that an address is located within, defined in either Welsh (cym) or Gaelic / Scottish Gaelic (gla). For example, a locality may be a suburb, housing estate or commercial estate.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    The name of the settlement that the address is located within, defined in either Welsh (cym) or Gaelic / Scottish Gaelic (gla). A settlement can be a City, Town, Village, Hamlet or Parish.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the island upon which an Address is located.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    ISO 3166-3 Language Code for Welsh or Gaelic / Scottish Gaelic.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: languagevalue

    • Max Length: 3

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Concatenation of the following alternate language address components: Organisation (Pre-Build and Built Address Feature Types only), Alternate Language Sub Name and / or Alternate Language Name and / or Alternate Language Number, Alternate Language Street Name, Alternate Language Locality, Alternate Language Town Name, Alternate Language Island Name and Postcode Locator.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 1 000

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 500

    • OS Select+Build Filterable: No

    Floor level represents either: the access point to the Address, or the floor level or levels that the Address is located on fully occupies or represents occupiable space within the property.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 30

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    In cases where the Floor Level attribute contains a list of floor levels (for example, where a commercial organisation occupies multiple levels within a building), the first value provided will be taken as the lowest floor level. For example, where Floor Level attribute values are given as -1, 0, 1, 2, 3, the Lowest Floor Level is -1. Mezzanine levels may be represented by a partial number, for example, 1.5. If the Floor Level attribute only contains one value, that value will also be used by the Lowest Floor Level attribute.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 3

    • Scale: 1

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0, 3.0

    In cases where the Floor Level attribute contains a list of floor levels (for example, where a commercial organisation occupies multiple levels within a building), the last value provided will be taken as the highest floor level. For example, where Floor Level attribute values are given as -1, 0, 1, 2, 3, the Highest Floor Level is 3. Mezzanine levels may be represented by a partial number, for example, 1.5. If the Floor Level attribute only contains one value, that value will also be used by the Highest Floor Level attribute.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 3

    • Scale: 1

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0, 3.0

    Alphanumeric code used to classify the object using the AddressBase Classification Scheme, which is available to download from the AddressBase Classification Scheme page of the OS Download Products’ Documentation site.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressclassificationcodevalue

    • Max Length: 6

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Description of the classification code as defined in the AddressBase Classification Scheme, which is available to download from the AddressBase Classification Scheme page of the OS Download Products’ Documentation site.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressclassificationdescriptionvalue

    • Max Length: 230

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    A descriptive term used to describe the primary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressprimaryclassificationdescriptionvalue

    • Max Length: 120

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0, 3.0

    A descriptive term used to describe the secondary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Code List Name: addresssecondaryclassificationdescriptionvalue

    • Nullable: true

    • Max Length: 120

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0, 3.0

    A descriptive term or collection of terms used to describe the tertiary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: addresstertiaryclassificationdescriptionvalue

    • Max Length: 120

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 3.0

    A descriptive term used to describe the tertiary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 120

    A descriptive term or collection of terms used to describe the quaternary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: addressquaternaryclassificationdescriptionvalue

    • Max Length: 120

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0, 3.0

    A description of the build status of the Address, for example, 'Built Complete'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: buildstatusvalue

    • Code List Version: 2.0

    • Max Length: 18

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 3.0

    A description of the build status of the land and property unit represented by an Address, for example, 'Built In Use'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version:

    Date when the address entered the lifecycle state given in Build Status.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    Date when the land and property unit entered the lifecycle state given in Build Status.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0

    The lifecycle status of a given Address, for example, 'Provisional' and 'Approved'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressstatusvalue

    • Max Length: 11

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Identifies the source of the postcode assigned to an address. This attribute can be used to identify properties capable of receiving mail as defined by Royal Mail for PAF matched address records, or as defined by Local Authorities for records which are not PAF matched but which are believed to be capable of receiving mail. For example, flats behind a front door with single letter box.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressbasepostalvalue

    • Code List Version: 2.0

    • Max Length: 148

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version: 1.0

    Unique Property Reference Number (UPRN) of the parent record if a parent-child relationship exists.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    In instances where an address sits in a hierarchy (for example, Child UPRN – Parent UPRN – Grandparent UPRN), the Root UPRN will display the Unique Property Reference Number (UPRN) for the top level Addressable Object in the parent-child structure, which in this example is the Grandparent UPRN.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    In instances where an address sits in a hierarchy (for example, Child UPRN – Parent UPRN – Grandparent UPRN), the Hierarchy Level attribute describes the position of the given UPRN within the overall set of relationships. For example, FLAT 1 is the Child UPRN at the lowest level and its Hierarchy Level will be 3; its Parent UPRN is BLOCK H, which will have a Hierarchy Level of 2; BLOCK H has, in turn, a Parent UPRN of EXETER UNIVERSITY, which will have a Hierarchy Level of 1.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The Unique Street Reference Number (USRN), a unique and persistent identifier of a Street which is assigned by the Roads or Highway Authority.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Description of the type of match made between the Unique Property Reference Number (UPRN) and its Unique Street Reference Number (USRN). A value of 1 is matched manually to the most accessible USRN, and a value of 2 is matched spatially to the nearest USRN, which may not be the nearest accessible street.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: usrnmatchindicatorvalue

    • Max Length: 17

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Numeric code identifying the authority responsible for assigning the Unique Property Reference Number (UPRN), creating and maintaining the address record.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the authority responsible for assigning the Unique Property Reference Number (UPRN), creating and maintaining the address record.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    The Office for National Statistics Governmental Statistical Service (GSS) code representing the lower tier local authority.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 9

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    X coordinate defining the position of the object in accordance with the British National Grid (EPSG:27700) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 8

    • Scale: 2

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Y coordinate defining the position of the object in accordance with the British National Grid (EPSG:27700) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 9

    • Scale: 2

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Value defining the latitude of the Address location in accordance with the ETRS89 (EPSG:4258) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 7

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Value defining the longitude of the Address location in accordance with the ETRS89 (EPSG:4258) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 7

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Geometry for the feature.

    • Data Types: Geometry (GPKG), WKT (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    • Geometry Type: Point

    Local Authority assigned value giving a description of the accuracy of the coordinate position allocated to the Address location, for example, 'Central Internal Position' of a building.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: positionalaccuracyvalue

    • Code List Version: 2.0

    • Max Length: 25

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version: 1.0

    The date on which this record was inserted into the Local Authority database.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The date on which the record ceased to exist.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Selected related components are provided for the Historic Address Feature Type.

    Customers taking data schema version 1.0 or 2.0 of the Historic Address Feature Type in GeoPackage format will receive the following in their data package:

    • Feature type: Historic Address

    • Related components: Alternate Address, Postal Address, Other Classification and Related Entity

    Customers taking data schema version 3.0 onward of the Historic Address Feature Type in GeoPackage format will receive the following in their data package:

    • Feature type: Historic Address

    • Related components: Alternate Address, Other Classification and Related Entity

    Please see the Address Related Components page for more information about the related components and how to handle them.

    3.0

    30 September 2025

    Data schema versioning

    Data schema version table

    Ongoing

    Temporal filtering

    Feature type attributes

    Comma-separated values (CSV) file format is universally supported for easy ingestion into all major database products. Before loading OS NGD data contained in CSV files into a database, it is necessary to create relevant tables. Data definition language (DDL) statements for PostgreSQL, SQL Server and Oracle can be accessed in our .

    For instructions on loading CSV files, see the guide.

    uprn

    versiondate

    versionavailablefromdate

    versionavailabletodate

    changetype

    theme

    description

    organisationname

    poboxnumber

    subname

    name

    number

    streetname

    locality

    townname

    islandname

    Note: This attribute is currently only populated in the OS Islands Address Collection.

    postcode

    fulladdress

    country

    alternatelanguagesubname

    alternatelanguagename

    alternatelanguagenumber

    alternatelanguagestreetname

    alternatelanguagelocality

    alternatelanguagetownname

    alternatelanguageislandname

    Note: This attribute is currently only populated in the OS Islands Address Collection.

    alternatelanguage

    alternatelanguagefulladdress

    floorlevel

    lowestfloorlevel

    This attribute is derived from Floor Level attribute data. Where the Floor Level field is NULL, Lowest Floor Level values will also be NULL.

    highestfloorlevel

    This attribute is derived from Floor Level attribute data. Where the Floor Level field is NULL, Highest Floor Level values will also be NULL.

    classificationcode

    classificationdescription

    primaryclassificationdescription

    secondaryclassificationdescription

    tertiaryclassificationdescription

    quaternaryclassificationdescription

    buildstatus

    buildstatusdate

    addressstatus

    postcodesource

    parentuprn

    rootuprn

    hierarchylevel

    usrn

    usrnmatchindicator

    localcustodiancode

    localcustodiandescription

    lowertierlocalauthoritygsscode

    easting

    northing

    latitude

    longitude

    geometry

    positionalaccuracy

    effectivestartdate

    effectiveenddate

    🆕 Related components

    Major version increment implementing the following changes:

    • Extended the max length of the Postcode Source, Full Address, Alternate Language Full Address, Sub Name, Alternate Language Sub Name and Build Status attributes.

    • Modified the associated code lists for the Description, Positional Accuracy and Postcode Source attributes.

    • Added download filters for Primary Classification Description, Secondary Classification Description, and Tertiary Classification Description attributes.

    2.0

    28 March 2023

    Ongoing

    Major version increment adding new attribution for Full Address, Alternate Language Full Address, Lowest Floor Level, Highest Floor Level, Primary Classification Description, Secondary Classification Description, Tertiary Classification Description and Quaternary Classification Description.

    1.0

    02 November 2022

    Ongoing

    Initial launch of the Historic Address Feature Type.

    Please see Data schema versioning for in-depth information about data schema versioning in the OS NGD.

    Temporal filtering allows you to order a one-off snapshot of data from the OS NGD from a current or past date. It is an optional step when you create a new data package in OS Select+Build (the OS NGD download service).

    The earliest and latest dates on which you can request a one-off snapshot of a date in the past for this feature type's data schema versions are indicated in the Data schema version table above. Please note that any data temporally filtered earlier than the specified launch date indicated in the table for the data schema versions may contain data inconsistencies.

    More information about temporal filtering on OS NGD feature types is available from the Getting started with temporal filtering guide.

    The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

    Unique Property Reference Number (UPRN) assigned by a local custodian or Ordnance Survey as a persistent identifier.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Date when the version was last updated.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The date this version of the feature became the latest version.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The date this version of the feature was superseded by an update or ceased to exist.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The type of change that generated a new version of the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: changetypevalue

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The OS NGD theme to which this feature belongs.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: themevalue

    • Max Length: 40

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    A single descriptive value intended for a quick understanding of what the feature represents.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressdescriptionvalue

    • Code List Version: 2.0

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version: 1.0

    The name of the organisation operating from the address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 100

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    The organisation name is the business name given to an Address 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.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 100

    Text concatenation of 'PO BOX' and the Post Office Box (PO Box) number or the British Forces Post Office (BFPO) number.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 13

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The Sub Name is the secondary description for subdivisions of properties. For example: Sub Name: 'CRYNANT LIBRARY', Name: 'CRYNANT COMMUNITY CENTRE'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 500

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    The name is the English language primary description applied to an address, for example: 'SWANSEA UNIVERSITY BAY CAMPUS' (Welsh: 'CAMPWS Y BAE PRIFYSGOL ABERTAWE'). This attribute will also include numbers when the name contains 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 name will be a blend of distinctive and descriptive naming, for example, RAILWAY TAVERN (PUBLIC HOUSE) or THE COURT ROYAL (HOTEL).

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The number gives a unique numeric identifier for addresses on a given street, for example, '11' (per Local Authority Street Naming and Numbering conventions). This includes numbers that contain a range, decimals or non-numeric characters, for example, 1-11 and 10A.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 13

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Name, number or descriptor that identifies the nearest accessible Street that an Address is located on or close to.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 100

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the area or geographical identifier within a town, settlement, village or hamlet that an address is located within. For example, a locality may be a suburb, housing estate or commercial estate.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the settlement that the Street is located within. Where a settlement can be a City, Town, Village, Hamlet or Parish.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the island upon which an Address is located.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The postcode unit that the Address is situated within. A postcode is an abbreviated form of address, made up of combinations of between five and seven alphanumeric characters. These alphanumeric characters are used by Royal Mail to help with the automated sorting of mail. A postcode may cover between 1 and 100 addresses. Postcodes (for example, NW6 4DP) are comprised of two components. The first component is the outward code (or ‘outcode’), which is the first two to four characters of a postcode, constituting the postcode area and the postcode district, for example, NW6. The outward code is the part of the postcode that enables mail to be sent from the accepting office to the correct area for delivery. The second component of a postcode is the inward code (or ‘incode’), which is the last three characters of the postcode, constituting the postcode sector and the postcode unit, for example, 4DP. The inward code is used to sort mail at the local delivery office. This field will contain the Royal Mail Postcode Address File (PAF) postcode where the Local Authority address has been matched to PAF. Where a match has not been made, the postcode information is sourced from Local Authority assigned data. In cases where the Local Authority do not hold a valid postcode, a spatial nearest neighbour function is used to spatially derive the postcode from the closest Address with a valid postcode.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 8

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Concatenation of the following address components: Organisation (Pre-Build and Built Address Feature Types only), Sub Name and / or Name and / or Number, Street Name, Locality, Town Name, Island Name and Postcode Locator.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 1 000

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 500

    • OS Select+Build Filterable: No

    Name of the geographical territory that the Address is located within, where a geographical territory represents either a devolved country or an island nation.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: countryvalue

    • Max Length: 16

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    The Alternate Language Sub Name is the alternate language secondary description for subdivisions of properties. For example: Alternate Language Sub Name: 'LLYFRGELL Y CREUNANT', Alternate Language Name: 'CANOLFAN CYMUNED CREUNANT'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 500

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    The Alternate Language Name is the alternate language primary description applied to an address, for example: 'CAMPWS Y BAE PRIFYSGOL ABERTAWE' (English: 'SWANSEA UNIVERSITY BAY CAMPUS'). This attribute may also include numbers when the name contains 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 name will be a blend of distinctive and descriptive naming, for example, RAILWAY TAVERN (PUBLIC HOUSE) or THE COURT ROYAL (HOTEL).

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The Alternate Language Number gives a unique numeric identifier for addresses on each street, for example, '11' (per Local Authority Street Naming and Numbering conventions). Numbers that contain a range, decimals or non-numeric characters do not appear in this field but will be found in the Name or the Sub Name attributes.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 13

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Name, number or descriptor that identifies the nearest accessable street that an Address is located on or close to, defined in either Welsh (cym) or Gaelic / Scottish Gaelic (gla).

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 100

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the area or geographical identifier within a town, settlement, village or hamlet that an address is located within, defined in either Welsh (cym) or Gaelic / Scottish Gaelic (gla). For example, a locality may be a suburb, housing estate or commercial estate.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    The name of the settlement that the address is located within, defined in either Welsh (cym) or Gaelic / Scottish Gaelic (gla). A settlement can be a City, Town, Village, Hamlet or Parish.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the island upon which an Address is located.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    ISO 3166-3 Language Code for Welsh or Gaelic / Scottish Gaelic.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: languagevalue

    • Max Length: 3

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Concatenation of the following alternate language address components: Organisation (Pre-Build and Built Address Feature Types only), Alternate Language Sub Name and / or Alternate Language Name and / or Alternate Language Number, Alternate Language Street Name, Alternate Language Locality, Alternate Language Town Name, Alternate Language Island Name and Postcode Locator.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 1 000

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 500

    • OS Select+Build Filterable: No

    Floor level represents either: the access point to the Address, or the floor level or levels that the Address is located on fully occupies or represents occupiable space within the property.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 30

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    In cases where the Floor Level attribute contains a list of floor levels (for example, where a commercial organisation occupies multiple levels within a building), the first value provided will be taken as the lowest floor level. For example, where Floor Level attribute values are given as -1, 0, 1, 2, 3, the Lowest Floor Level is -1. Mezzanine levels may be represented by a partial number, for example, 1.5. If the Floor Level attribute only contains one value, that value will also be used by the Lowest Floor Level attribute.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 3

    • Scale: 1

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0, 3.0

    In cases where the Floor Level attribute contains a list of floor levels (for example, where a commercial organisation occupies multiple levels within a building), the last value provided will be taken as the highest floor level. For example, where Floor Level attribute values are given as -1, 0, 1, 2, 3, the Highest Floor Level is 3. Mezzanine levels may be represented by a partial number, for example, 1.5. If the Floor Level attribute only contains one value, that value will also be used by the Highest Floor Level attribute.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 3

    • Scale: 1

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0, 3.0

    Alphanumeric code used to classify the object using the AddressBase Classification Scheme, which is available to download from the AddressBase Classification Scheme page of the OS Download Products’ Documentation site.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressclassificationcodevalue

    • Max Length: 6

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Description of the classification code as defined in the AddressBase Classification Scheme, which is available to download from the AddressBase Classification Scheme page of the OS Download Products’ Documentation site.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressclassificationdescriptionvalue

    • Max Length: 230

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    A descriptive term used to describe the primary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressprimaryclassificationdescriptionvalue

    • Max Length: 120

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0, 3.0

    A descriptive term used to describe the secondary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Code List Name: addresssecondaryclassificationdescriptionvalue

    • Nullable: true

    • Max Length: 120

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0, 3.0

    A descriptive term or collection of terms used to describe the tertiary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: addresstertiaryclassificationdescriptionvalue

    • Max Length: 120

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 3.0

    A descriptive term used to describe the tertiary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 120

    A descriptive term or collection of terms used to describe the quaternary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: addressquaternaryclassificationdescriptionvalue

    • Max Length: 120

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0, 3.0

    A description of the build status of the Address, for example, 'Built Complete'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: buildstatusvalue

    • Code List Version: 2.0

    • Max Length: 18

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 3.0

    A description of the build status of the land and property unit represented by an Address, for example, 'Built In Use'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version:

    Date when the address entered the lifecycle state given in Build Status.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    Date when the land and property unit entered the lifecycle state given in Build Status.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0

    The lifecycle status of a given Address, for example, 'Provisional' and 'Approved'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressstatusvalue

    • Max Length: 11

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Identifies the source of the postcode assigned to an address. This attribute can be used to identify properties capable of receiving mail as defined by Royal Mail for PAF matched address records, or as defined by Local Authorities for records which are not PAF matched but which are believed to be capable of receiving mail. For example, flats behind a front door with single letter box.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressbasepostalvalue

    • Code List Version: 2.0

    • Max Length: 148

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version: 1.0

    Unique Property Reference Number (UPRN) of the parent record if a parent-child relationship exists.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    In instances where an address sits in a hierarchy (for example, Child UPRN – Parent UPRN – Grandparent UPRN), the Root UPRN will display the Unique Property Reference Number (UPRN) for the top level Addressable Object in the parent-child structure, which in this example is the Grandparent UPRN.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    In instances where an address sits in a hierarchy (for example, Child UPRN – Parent UPRN – Grandparent UPRN), the Hierarchy Level attribute describes the position of the given UPRN within the overall set of relationships. For example, FLAT 1 is the Child UPRN at the lowest level and its Hierarchy Level will be 3; its Parent UPRN is BLOCK H, which will have a Hierarchy Level of 2; BLOCK H has, in turn, a Parent UPRN of EXETER UNIVERSITY, which will have a Hierarchy Level of 1.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The Unique Street Reference Number (USRN), a unique and persistent identifier of a Street which is assigned by the Roads or Highway Authority.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Description of the type of match made between the Unique Property Reference Number (UPRN) and its Unique Street Reference Number (USRN). A value of 1 is matched manually to the most accessible USRN, and a value of 2 is matched spatially to the nearest USRN, which may not be the nearest accessible street.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: usrnmatchindicatorvalue

    • Max Length: 17

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Numeric code identifying the authority responsible for assigning the Unique Property Reference Number (UPRN), creating and maintaining the address record.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the authority responsible for assigning the Unique Property Reference Number (UPRN), creating and maintaining the address record.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    The Office for National Statistics Governmental Statistical Service (GSS) code representing the lower tier local authority.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 9

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    X coordinate defining the position of the object in accordance with the British National Grid (EPSG:27700) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 8

    • Scale: 2

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Y coordinate defining the position of the object in accordance with the British National Grid (EPSG:27700) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 2

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Value defining the latitude of the Address location in accordance with the ETRS89 (EPSG:4258) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 7

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Value defining the longitude of the Address location in accordance with the ETRS89 (EPSG:4258) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 7

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Geometry for the feature.

    • Data Types: Geometry (GPKG), WKT (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    • Geometry Type: Point

    Local Authority assigned value giving a description of the accuracy of the coordinate position allocated to the Address location, for example, 'Central Internal Position' of a building.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: positionalaccuracyvalue

    • Code List Version: 2.0

    • Max Length: 25

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version: 1.0

    The date on which this record was inserted into the Local Authority database.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The date on which the record ceased to exist.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Selected related components are provided for the Historic Address Feature Type.

    Customers taking data schema version 1.0 or 2.0 of the Historic Address Feature Type in GeoPackage format will receive the following in their data package:

    • Feature type: Historic Address

    • Related components: Alternate Address, Postal Address, Other Classification and Related Entity

    Customers taking data schema version 3.0 onward of the Historic Address Feature Type in GeoPackage format will receive the following in their data package:

    • Feature type: Historic Address

    • Related components: Alternate Address, Other Classification and Related Entity

    Please see the Address Related Components page for more information about the related components and how to handle them.

    3.0

    30 September 2025

    Data schema versioning

    Data schema version table

    Ongoing

    Temporal filtering

    Feature type attributes

    Comma-separated values (CSV) file format is universally supported for easy ingestion into all major database products. Before loading OS NGD data contained in CSV files into a database, it is necessary to create relevant tables. Data definition language (DDL) statements for PostgreSQL, SQL Server and Oracle can be accessed in our .

    For instructions on loading CSV files, see the guide.

    uprn

    versiondate

    versionavailablefromdate

    versionavailabletodate

    changetype

    theme

    description

    organisationname

    poboxnumber

    subname

    name

    number

    streetname

    locality

    townname

    islandname

    Note: This attribute is currently only populated in the OS Islands Address Collection.

    postcode

    fulladdress

    country

    alternatelanguagesubname

    alternatelanguagename

    alternatelanguagenumber

    alternatelanguagestreetname

    alternatelanguagelocality

    alternatelanguagetownname

    alternatelanguageislandname

    Note: This attribute is currently only populated in the OS Islands Address Collection.

    alternatelanguage

    alternatelanguagefulladdress

    floorlevel

    lowestfloorlevel

    This attribute is derived from Floor Level attribute data. Where the Floor Level field is NULL, Lowest Floor Level values will also be NULL.

    highestfloorlevel

    This attribute is derived from Floor Level attribute data. Where the Floor Level field is NULL, Highest Floor Level values will also be NULL.

    classificationcode

    classificationdescription

    primaryclassificationdescription

    secondaryclassificationdescription

    tertiaryclassificationdescription

    quaternaryclassificationdescription

    buildstatus

    buildstatusdate

    addressstatus

    postcodesource

    parentuprn

    rootuprn

    hierarchylevel

    usrn

    usrnmatchindicator

    localcustodiancode

    localcustodiandescription

    lowertierlocalauthoritygsscode

    easting

    northing

    latitude

    longitude

    geometry

    positionalaccuracy

    effectivestartdate

    effectiveenddate

    🆕 Related components

    Built Address

    The Built Address Feature Type represents local authority addresses that are currently built and live and can typically receive mail, deliveries, or services. For example, homes, shops, schools and hospitals.

    Data schema versioning

    The following table provides details about this feature type’s data schema versions, including the reasons behind the changes and the related launch date when each version went live.

    Data schema version table

    Version ↓
    Launch Date
    Latest Date
    Change

    3.0

    30 September 2025

    Ongoing

    Please see for in-depth information about data schema versioning in the OS NGD.

    Temporal filtering allows you to order a one-off snapshot of data from the OS NGD from a current or past date. It is an optional step when you create a new data package in OS Select+Build (the OS NGD download service).

    The earliest and latest dates on which you can request a one-off snapshot of a date in the past for this feature type's data schema versions are indicated in the above. Please note that any data temporally filtered earlier than the specified launch date indicated in the table for the data schema versions may contain data inconsistencies.

    More information about temporal filtering on OS NGD feature types is available from the .

    The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

    Unique Property Reference Number (UPRN) assigned by a local custodian or Ordnance Survey as a persistent identifier.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Date when the version was last updated.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The date this version of the feature became the latest version.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The date this version of the feature was superseded by an update or ceased to exist.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The type of change that generated a new version of the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    The OS NGD theme to which this feature belongs.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 40

    A single descriptive value intended for a quick understanding of what the feature represents.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version: 2.0

    The name of the organisation operating from the address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 100

    • OS Select+Build Filterable: No

    Text concatenation of 'PO BOX' and the Post Office Box (PO Box) number or the British Forces Post Office (BFPO) number.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 13

    • OS Select+Build Filterable: No

    The Sub Name is the secondary description for subdivisions of properties. For example: Sub Name: 'CRYNANT LIBRARY', Name: 'CRYNANT COMMUNITY CENTRE'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 500

    • OS Select+Build Filterable: No

    The name is the English language primary description applied to an address, for example: 'SWANSEA UNIVERSITY BAY CAMPUS' (Welsh: 'CAMPWS Y BAE PRIFYSGOL ABERTAWE'). This attribute will also include numbers when the name contains 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 name will be a blend of distinctive and descriptive naming, for example, RAILWAY TAVERN (PUBLIC HOUSE) or THE COURT ROYAL (HOTEL).

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    The number gives a unique numeric identifier for addresses on a given street, for example, '11' (per Local Authority Street Naming and Numbering conventions). This includes numbers that contain a range, decimals or non-numeric characters, for example, 1-11 and 10A.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 13

    • OS Select+Build Filterable: No

    Name, number or descriptor that identifies the nearest accessible Street that an Address is located on or close to.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 100

    • OS Select+Build Filterable: No

    Name of the area or geographical identifier within a town, settlement, village or hamlet that an address is located within. For example, a locality may be a suburb, housing estate or commercial estate.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    Name of the settlement that the Street is located within. Where a settlement can be a City, Town, Village, Hamlet or Parish.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    Name of the island upon which an Address is located.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 50

    • OS Select+Build Filterable: No

    The postcode unit that the Address is situated within. A postcode is an abbreviated form of address, made up of combinations of between five and seven alphanumeric characters. These alphanumeric characters are used by Royal Mail to help with the automated sorting of mail. A postcode may cover between 1 and 100 addresses. Postcodes (for example, NW6 4DP) are comprised of two components. The first component is the outward code (or ‘outcode’), which is the first two to four characters of a postcode, constituting the postcode area and the postcode district, for example, NW6. The outward code is the part of the postcode that enables mail to be sent from the accepting office to the correct area for delivery. The second component of a postcode is the inward code (or ‘incode’), which is the last three characters of the postcode, constituting the postcode sector and the postcode unit, for example, 4DP. The inward code is used to sort mail at the local delivery office. This field will contain the Royal Mail Postcode Address File (PAF) postcode where the Local Authority address has been matched to PAF. Where a match has not been made, the postcode information is sourced from Local Authority assigned data. In cases where the Local Authority do not hold a valid postcode, a spatial nearest neighbour function is used to spatially derive the postcode from the closest Address with a valid postcode.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 8

    • OS Select+Build Filterable: Yes

    Concatenation of the following address components: Organisation (Pre-Build and Built Address Feature Types only), Sub Name and / or Name and / or Number, Street Name, Locality, Town Name, Island Name and Postcode Locator.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 1 000

    • OS Select+Build Filterable: No

    Name of the geographical territory that the Address is located within, where a geographical territory represents either a devolved country or an island nation.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 16

    The Alternate Language Sub Name is the alternate language secondary description for subdivisions of properties. For example: Alternate Language Sub Name: 'LLYFRGELL Y CREUNANT', Alternate Language Name: 'CANOLFAN CYMUNED CREUNANT'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 500

    • OS Select+Build Filterable: No

    The Alternate Language Name is the alternate language primary description applied to an address, for example: 'CAMPWS Y BAE PRIFYSGOL ABERTAWE' (English: 'SWANSEA UNIVERSITY BAY CAMPUS'). This attribute may also include numbers when the name contains 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 name will be a blend of distinctive and descriptive naming, for example, RAILWAY TAVERN (PUBLIC HOUSE) or THE COURT ROYAL (HOTEL).

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    The Alternate Language Number gives a unique numeric identifier for addresses on each street, for example, '11' (per Local Authority Street Naming and Numbering conventions). Numbers that contain a range, decimals or non-numeric characters do not appear in this field but will be found in the Name or the Sub Name attributes.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 13

    • OS Select+Build Filterable: No

    Name, number or descriptor that identifies the nearest accessable street that an Address is located on or close to, defined in either Welsh (cym) or Gaelic / Scottish Gaelic (gla).

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 100

    • OS Select+Build Filterable: No

    Name of the area or geographical identifier within a town, settlement, village or hamlet that an address is located within, defined in either Welsh (cym) or Gaelic / Scottish Gaelic (gla). For example, a locality may be a suburb, housing estate or commercial estate.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    The name of the settlement that the address is located within, defined in either Welsh (cym) or Gaelic / Scottish Gaelic (gla). A settlement can be a City, Town, Village, Hamlet or Parish.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    Name of the island upon which an Address is located.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 50

    • OS Select+Build Filterable: No

    ISO 3166-3 Language Code for Welsh or Gaelic / Scottish Gaelic.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    Concatenation of the following alternate language address components: Organisation (Pre-Build and Built Address Feature Types only), Alternate Language Sub Name and / or Alternate Language Name and / or Alternate Language Number, Alternate Language Street Name, Alternate Language Locality, Alternate Language Town Name, Alternate Language Island Name and Postcode Locator.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 1 000

    • OS Select+Build Filterable: No

    Floor level represents either: the access point to the Address, or the floor level or levels that the Address is located on fully occupies or represents occupiable space within the property.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 30

    • OS Select+Build Filterable: No

    In cases where the Floor Level attribute contains a list of floor levels (for example, where a commercial organisation occupies multiple levels within a building), the first value provided will be taken as the lowest floor level. For example, where Floor Level attribute values are given as -1, 0, 1, 2, 3, the Lowest Floor Level is -1. Mezzanine levels may be represented by a partial number, for example, 1.5. If the Floor Level attribute only contains one value, that value will also be used by the Lowest Floor Level attribute.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 3

    • Scale: 1

    In cases where the Floor Level attribute contains a list of floor levels (for example, where a commercial organisation occupies multiple levels within a building), the last value provided will be taken as the highest floor level. For example, where Floor Level attribute values are given as -1, 0, 1, 2, 3, the Highest Floor Level is 3. Mezzanine levels may be represented by a partial number, for example, 1.5. If the Floor Level attribute only contains one value, that value will also be used by the Highest Floor Level attribute.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 3

    • Scale: 1

    Alphanumeric code used to classify the object using the AddressBase Classification Scheme, which is available to download from the .

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 6

    Description of the classification code as defined in the AddressBase Classification Scheme, which is available to download from the .

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 230

    A descriptive term used to describe the primary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 120

    A descriptive term used to describe the secondary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Code List Name:

    • Nullable: true

    • Max Length: 120

    A descriptive term or collection of terms used to describe the tertiary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 120

    A descriptive term or collection of terms used to describe the quaternary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 120

    A description of the build status of the Address, for example, 'Built Complete'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version: 2.0

    Date when the address entered the lifecycle state given in Build Status.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    The lifecycle status of a given Address, for example, 'Provisional' and 'Approved'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 11

    Identifies the source of the postcode assigned to an address. This attribute can be used to identify properties capable of receiving mail as defined by Royal Mail for PAF matched address records, or as defined by Local Authorities for records which are not PAF matched but which are believed to be capable of receiving mail. For example, flats behind a front door with single letter box.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version: 2.0

    Unique Property Reference Number (UPRN) of the parent record if a parent-child relationship exists.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    In instances where an address sits in a hierarchy (for example, Child UPRN – Parent UPRN – Grandparent UPRN), the Root UPRN will display the Unique Property Reference Number (UPRN) for the top level Addressable Object in the parent-child structure, which in this example is the Grandparent UPRN.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    In instances where an address sits in a hierarchy (for example, Child UPRN – Parent UPRN – Grandparent UPRN), the Hierarchy Level attribute describes the position of the given UPRN within the overall set of relationships. For example, FLAT 1 is the Child UPRN at the lowest level and its Hierarchy Level will be 3; its Parent UPRN is BLOCK H, which will have a Hierarchy Level of 2; BLOCK H has, in turn, a Parent UPRN of EXETER UNIVERSITY, which will have a Hierarchy Level of 1.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The Unique Street Reference Number (USRN), a unique and persistent identifier of a Street which is assigned by the Roads or Highway Authority.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Description of the type of match made between the Unique Property Reference Number (UPRN) and its Unique Street Reference Number (USRN). A value of 1 is matched manually to the most accessible USRN, and a value of 2 is matched spatially to the nearest USRN, which may not be the nearest accessible street.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 17

    Numeric code identifying the authority responsible for assigning the Unique Property Reference Number (UPRN), creating and maintaining the address record.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the authority responsible for assigning the Unique Property Reference Number (UPRN), creating and maintaining the address record.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    The Office for National Statistics Governmental Statistical Service (GSS) code representing the lower tier local authority.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 9

    • OS Select+Build Filterable: Yes

    X coordinate defining the position of the object in accordance with the British National Grid (EPSG:27700) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 8

    • Scale: 2

    Y coordinate defining the position of the object in accordance with the British National Grid (EPSG:27700) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 9

    • Scale: 2

    Value defining the latitude of the Address location in accordance with the ETRS89 (EPSG:4258) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 7

    Value defining the longitude of the Address location in accordance with the ETRS89 (EPSG:4258) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 7

    Geometry for the feature.

    • Data Types: Geometry (GPKG), WKT (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Local Authority assigned value giving a description of the accuracy of the coordinate position allocated to the Address location, for example, 'Central Internal Position' of a building.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version: 2.0

    The date on which this record was inserted into the Local Authority database.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The date on which the record ceased to exist.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Selected related components are provided for the Built Address Feature Type.

    Customers taking data schema version 1.0 or 2.0 of the Built Address Feature Type in GeoPackage format will receive the following in their data package:

    • Feature type: Built Address

    • Related components: Alternate Address, Postal Address, Other Classification and Related Entity

    Customers taking data schema version 3.0 onward of the Built Address Feature Type in GeoPackage format will receive the following in their data package:

    • Feature type: Built Address

    • Related components: Alternate Address, Other Classification and Related Entity

    Please see the for more information about the related components and how to handle them.

    Pre-Build Address

    The Pre-Build Address Feature Type represents local authority addresses that will be able to receive mail, deliveries or services, where the property is either yet to be built but has been granted planning permission, or is under construction. Pre-build addresses can take the format of a development site, a plot number, or a definitive address for property units.

    Data schema versioning

    The following table provides details about this feature type’s data schema versions, including the reasons behind the changes and the related launch date when each version went live.

    Data schema version table

    Version ↓
    Launch Date
    Latest Date
    Change

    3.0

    Please see for in-depth information about data schema versioning in the OS NGD.

    Temporal filtering allows you to order a one-off snapshot of data from the OS NGD from a current or past date. It is an optional step when you create a new data package in OS Select+Build (the OS NGD download service).

    The earliest and latest dates on which you can request a one-off snapshot of a date in the past for this feature type's data schema versions are indicated in the above. Please note that any data temporally filtered earlier than the specified launch date indicated in the table for the data schema versions may contain data inconsistencies.

    More information about temporal filtering on OS NGD feature types is available from the .

    The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

    Unique Property Reference Number (UPRN) assigned by a local custodian or Ordnance Survey as a persistent identifier.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Date when the version was last updated.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The date this version of the feature became the latest version.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The date this version of the feature was superseded by an update or ceased to exist.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The type of change that generated a new version of the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    The OS NGD theme to which this feature belongs.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 40

    A single descriptive value intended for a quick understanding of what the feature represents.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version: 2.0

    The name of the organisation operating from the address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 100

    • OS Select+Build Filterable: No

    Text concatenation of 'PO BOX' and the Post Office Box (PO Box) number or the British Forces Post Office (BFPO) number.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 13

    • OS Select+Build Filterable: No

    The Sub Name is the secondary description for subdivisions of properties. For example: Sub Name: 'CRYNANT LIBRARY', Name: 'CRYNANT COMMUNITY CENTRE'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 500

    • OS Select+Build Filterable: No

    The name is the English language primary description applied to an address, for example: 'SWANSEA UNIVERSITY BAY CAMPUS' (Welsh: 'CAMPWS Y BAE PRIFYSGOL ABERTAWE'). This attribute will also include numbers when the name contains 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 name will be a blend of distinctive and descriptive naming, for example, RAILWAY TAVERN (PUBLIC HOUSE) or THE COURT ROYAL (HOTEL).

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    The number gives a unique numeric identifier for addresses on a given street, for example, '11' (per Local Authority Street Naming and Numbering conventions). This includes numbers that contain a range, decimals or non-numeric characters, for example, 1-11 and 10A.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 13

    • OS Select+Build Filterable: No

    Name, number or descriptor that identifies the nearest accessible Street that an Address is located on or close to.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 100

    • OS Select+Build Filterable: No

    Name of the area or geographical identifier within a town, settlement, village or hamlet that an address is located within. For example, a locality may be a suburb, housing estate or commercial estate.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    Name of the settlement that the Street is located within. Where a settlement can be a City, Town, Village, Hamlet or Parish.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    Name of the island upon which an Address is located.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 50

    • OS Select+Build Filterable: No

    The postcode unit that the Address is situated within. A postcode is an abbreviated form of address, made up of combinations of between five and seven alphanumeric characters. These alphanumeric characters are used by Royal Mail to help with the automated sorting of mail. A postcode may cover between 1 and 100 addresses. Postcodes (for example, NW6 4DP) are comprised of two components. The first component is the outward code (or ‘outcode’), which is the first two to four characters of a postcode, constituting the postcode area and the postcode district, for example, NW6. The outward code is the part of the postcode that enables mail to be sent from the accepting office to the correct area for delivery. The second component of a postcode is the inward code (or ‘incode’), which is the last three characters of the postcode, constituting the postcode sector and the postcode unit, for example, 4DP. The inward code is used to sort mail at the local delivery office. This field will contain the Royal Mail Postcode Address File (PAF) postcode where the Local Authority address has been matched to PAF. Where a match has not been made, the postcode information is sourced from Local Authority assigned data. In cases where the Local Authority do not hold a valid postcode, a spatial nearest neighbour function is used to spatially derive the postcode from the closest Address with a valid postcode.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 8

    • OS Select+Build Filterable: Yes

    Concatenation of the following address components: Organisation (Pre-Build and Built Address Feature Types only), Sub Name and / or Name and / or Number, Street Name, Locality, Town Name, Island Name and Postcode Locator.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 1 000

    • OS Select+Build Filterable: No

    Name of the geographical territory that the Address is located within, where a geographical territory represents either a devolved country or an island nation.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 16

    The Alternate Language Sub Name is the alternate language secondary description for subdivisions of properties. For example: Alternate Language Sub Name: 'LLYFRGELL Y CREUNANT', Alternate Language Name: 'CANOLFAN CYMUNED CREUNANT'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 500

    • OS Select+Build Filterable: No

    The Alternate Language Name is the alternate language primary description applied to an address, for example: 'CAMPWS Y BAE PRIFYSGOL ABERTAWE' (English: 'SWANSEA UNIVERSITY BAY CAMPUS'). This attribute may also include numbers when the name contains 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 name will be a blend of distinctive and descriptive naming, for example, RAILWAY TAVERN (PUBLIC HOUSE) or THE COURT ROYAL (HOTEL).

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    The Alternate Language Number gives a unique numeric identifier for addresses on each street, for example, '11' (per Local Authority Street Naming and Numbering conventions). Numbers that contain a range, decimals or non-numeric characters do not appear in this field but will be found in the Name or the Sub Name attributes.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 13

    • OS Select+Build Filterable: No

    Name, number or descriptor that identifies the nearest accessable street that an Address is located on or close to, defined in either Welsh (cym) or Gaelic / Scottish Gaelic (gla).

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 100

    • OS Select+Build Filterable: No

    Name of the area or geographical identifier within a town, settlement, village or hamlet that an address is located within, defined in either Welsh (cym) or Gaelic / Scottish Gaelic (gla). For example, a locality may be a suburb, housing estate or commercial estate.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    The name of the settlement that the address is located within, defined in either Welsh (cym) or Gaelic / Scottish Gaelic (gla). A settlement can be a City, Town, Village, Hamlet or Parish.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    Name of the island upon which an Address is located.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 50

    • OS Select+Build Filterable: No

    ISO 3166-3 Language Code for Welsh or Gaelic / Scottish Gaelic.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    Concatenation of the following alternate language address components: Organisation (Pre-Build and Built Address Feature Types only), Alternate Language Sub Name and / or Alternate Language Name and / or Alternate Language Number, Alternate Language Street Name, Alternate Language Locality, Alternate Language Town Name, Alternate Language Island Name and Postcode Locator.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 1 000

    • OS Select+Build Filterable: No

    Floor level represents either: the access point to the Address, or the floor level or levels that the Address is located on fully occupies or represents occupiable space within the property.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 30

    • OS Select+Build Filterable: No

    In cases where the Floor Level attribute contains a list of floor levels (for example, where a commercial organisation occupies multiple levels within a building), the first value provided will be taken as the lowest floor level. For example, where Floor Level attribute values are given as -1, 0, 1, 2, 3, the Lowest Floor Level is -1. Mezzanine levels may be represented by a partial number, for example, 1.5. If the Floor Level attribute only contains one value, that value will also be used by the Lowest Floor Level attribute.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 3

    • Scale: 1

    In cases where the Floor Level attribute contains a list of floor levels (for example, where a commercial organisation occupies multiple levels within a building), the last value provided will be taken as the highest floor level. For example, where Floor Level attribute values are given as -1, 0, 1, 2, 3, the Highest Floor Level is 3. Mezzanine levels may be represented by a partial number, for example, 1.5. If the Floor Level attribute only contains one value, that value will also be used by the Highest Floor Level attribute.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 3

    • Scale: 1

    Alphanumeric code used to classify the object using the AddressBase Classification Scheme, which is available to download from the .

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 6

    Description of the classification code as defined in the AddressBase Classification Scheme, which is available to download from the .

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 230

    A descriptive term used to describe the primary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 120

    A descriptive term used to describe the secondary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Code List Name:

    • Nullable: true

    • Max Length: 120

    A descriptive term or collection of terms used to describe the tertiary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 120

    A descriptive term or collection of terms used to describe the quaternary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 120

    A description of the build status of the Address, for example, 'Built Complete'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version: 2.0

    Date when the address entered the lifecycle state given in Build Status.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    The lifecycle status of a given Address, for example, 'Provisional' and 'Approved'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 11

    Identifies the source of the postcode assigned to an address. This attribute can be used to identify properties capable of receiving mail as defined by Royal Mail for PAF matched address records, or as defined by Local Authorities for records which are not PAF matched but which are believed to be capable of receiving mail. For example, flats behind a front door with single letter box.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version: 2.0

    Unique Property Reference Number (UPRN) of the parent record if a parent-child relationship exists.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    In instances where an address sits in a hierarchy (for example, Child UPRN – Parent UPRN – Grandparent UPRN), the Root UPRN will display the Unique Property Reference Number (UPRN) for the top level Addressable Object in the parent-child structure, which in this example is the Grandparent UPRN.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    In instances where an address sits in a hierarchy (for example, Child UPRN – Parent UPRN – Grandparent UPRN), the Hierarchy Level attribute describes the position of the given UPRN within the overall set of relationships. For example, FLAT 1 is the Child UPRN at the lowest level and its Hierarchy Level will be 3; its Parent UPRN is BLOCK H, which will have a Hierarchy Level of 2; BLOCK H has, in turn, a Parent UPRN of EXETER UNIVERSITY, which will have a Hierarchy Level of 1.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The Unique Street Reference Number (USRN), a unique and persistent identifier of a Street which is assigned by the Roads or Highway Authority.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Description of the type of match made between the Unique Property Reference Number (UPRN) and its Unique Street Reference Number (USRN). A value of 1 is matched manually to the most accessible USRN, and a value of 2 is matched spatially to the nearest USRN, which may not be the nearest accessible street.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 17

    Numeric code identifying the authority responsible for assigning the Unique Property Reference Number (UPRN), creating and maintaining the address record.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the authority responsible for assigning the Unique Property Reference Number (UPRN), creating and maintaining the address record.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    The Office for National Statistics Governmental Statistical Service (GSS) code representing the lower tier local authority.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 9

    • OS Select+Build Filterable: Yes

    X coordinate defining the position of the object in accordance with the British National Grid (EPSG:27700) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 8

    • Scale: 2

    Y coordinate defining the position of the object in accordance with the British National Grid (EPSG:27700) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 9

    • Scale: 2

    Value defining the latitude of the Address location in accordance with the ETRS89 (EPSG:4258) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 7

    Value defining the longitude of the Address location in accordance with the ETRS89 (EPSG:4258) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 7

    Geometry for the feature.

    • Data Types: Geometry (GPKG), WKT (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Local Authority assigned value giving a description of the accuracy of the coordinate position allocated to the Address location, for example, 'Central Internal Position' of a building.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version: 2.0

    The date on which this record was inserted into the Local Authority database.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The date on which the record ceased to exist.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Selected related components are provided for the Pre-Build Address Feature Type.

    Customers taking data schema version 1.0 or 2.0 of the Pre-Build Address Feature Type in GeoPackage format will receive the following in their data package:

    • Feature type: Pre-Build Address

    • Related components: Alternate Address, Postal Address, Other Classification and Related Entity

    Customers taking data schema version 3.0 onward of the Pre-Build Address Feature Type in GeoPackage format will receive the following in their data package:

    • Feature type: Pre-Build Address

    • Related components: Alternate Address, Other Classification and Related Entity

    Please see the for more information about the related components and how to handle them.

    OS Select+Build Filterable: No
  • Data Schema Version: 1.0, 2.0, 3.0

  • OS Select+Build Filterable: No
  • Data Schema Version: 1.0, 2.0, 3.0

  • Max Length: 50

  • OS Select+Build Filterable: No

  • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressdescriptionvalue

    • Code List Version: 1.0

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0

    Data Schema Version: 3.0

    The organisation name is the business name given to an Address 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.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 100

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0

    Data Schema Version: 1.0, 2.0, 3.0

    Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0

    Data Schema Version: 1.0, 2.0, 3.0
    Data Schema Version: 1.0, 2.0, 3.0
    Data Schema Version: 1.0, 2.0, 3.0
    Data Schema Version: 1.0, 2.0, 3.0
    Data Schema Version: 1.0, 2.0, 3.0
    Data Schema Version: 1.0, 2.0, 3.0
    Data Schema Version: 1.0, 2.0, 3.0

    Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 500

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0

    OS Select+Build Filterable: Yes
  • Data Schema Version: 1.0, 2.0, 3.0

  • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0

    Data Schema Version: 1.0, 2.0, 3.0
    Data Schema Version: 1.0, 2.0, 3.0
    Data Schema Version: 1.0, 2.0, 3.0
    Data Schema Version: 1.0, 2.0, 3.0
    Data Schema Version: 1.0, 2.0, 3.0
    Data Schema Version: 1.0, 2.0, 3.0
    OS Select+Build Filterable: No
  • Data Schema Version: 1.0, 2.0, 3.0

  • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 500

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0

    Data Schema Version: 1.0, 2.0, 3.0
    OS Select+Build Filterable: No
  • Data Schema Version: 2.0, 3.0

  • OS Select+Build Filterable: No
  • Data Schema Version: 2.0, 3.0

  • OS Select+Build Filterable: Yes
  • Data Schema Version: 1.0, 2.0, 3.0

  • OS Select+Build Filterable: Yes
  • Data Schema Version: 1.0, 2.0, 3.0

  • OS Select+Build Filterable: Yes
  • Data Schema Version: 2.0, 3.0

  • OS Select+Build Filterable: Yes
  • Data Schema Version: 2.0, 3.0

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 3.0

  • A descriptive term used to describe the tertiary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: addresstertiaryclassificationdescriptionvalue

    • Max Length: 120

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0

    OS Select+Build Filterable: No
  • Data Schema Version: 2.0, 3.0

  • Max Length: 18

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 3.0

  • A description of the build status of the land and property unit represented by an Address, for example, 'Built In Use'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: buildstatusvalue

    • Code List Version: 1.0

    • Max Length: 12

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0

    Date when the land and property unit entered the lifecycle state given in Build Status.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0

    OS Select+Build Filterable: No
  • Data Schema Version: 1.0, 2.0, 3.0

  • Max Length: 148

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressbasepostalvalue

    • Code List Version: 1.0

    • Max Length: 75

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0

    OS Select+Build Filterable: No
  • Data Schema Version: 1.0, 2.0, 3.0

  • Data Schema Version: 1.0, 2.0, 3.0
    Data Schema Version: 1.0, 2.0, 3.0
    OS Select+Build Filterable: No
  • Data Schema Version: 1.0, 2.0, 3.0

  • OS Select+Build Filterable: No
  • Data Schema Version: 1.0, 2.0, 3.0

  • OS Select+Build Filterable: No
  • Data Schema Version: 1.0, 2.0, 3.0

  • OS Select+Build Filterable: No
  • Data Schema Version: 1.0, 2.0, 3.0

  • Geometry Type: Point

    Max Length: 25

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: positionalaccuracyvalue

    • Code List Version: 1.0

    • Max Length: 25

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0

    Major version increment implementing the following changes:

    • Extended the max length of the Postcode Source, Full Address, Alternate Language Full Address, Sub Name, Alternate Language Sub Name and Build Status attributes.

    • Modified the associated code lists for the Description, Positional Accuracy and Postcode Source attributes.

    • Added download filters for Primary Classification Description, Secondary Classification Description, and Tertiary Classification Description attributes.

    • New associated code lists added to the Classification Code, Classification Description, Primary Classification Description, Secondary Classification Description, Tertiary Classification Description and Quaternary Classification Description attributes.

    2.0

    28 March 2023

    Ongoing

    Major version increment adding new attribution for Full Address, Alternate Language Full Address, Lowest Floor Level, Highest Floor Level, Primary Classification Description, Secondary Classification Description, Tertiary Classification Description and Quaternary Classification Description.

    1.0

    02 November 2022

    Ongoing

    Initial launch of the Built Address Feature Type.

    Temporal filtering

    Feature type attributes

    Loading OS NGD CSV files into databases

    Comma-separated values (CSV) file format is universally supported for easy ingestion into all major database products. Before loading OS NGD data contained in CSV files into a database, it is necessary to create relevant tables. Data definition language (DDL) statements for PostgreSQL, SQL Server and Oracle can be accessed in our OS NGD Resources GitHub repository.

    For instructions on loading CSV files, see the Getting Started with CSV guide.

    uprn

    versiondate

    versionavailablefromdate

    versionavailabletodate

    changetype

    theme

    description

    organisationname

    poboxnumber

    subname

    name

    number

    streetname

    locality

    townname

    islandname

    Note: This attribute is currently only populated in the OS Islands Address Collection.

    postcode

    fulladdress

    country

    alternatelanguagesubname

    alternatelanguagename

    alternatelanguagenumber

    alternatelanguagestreetname

    alternatelanguagelocality

    alternatelanguagetownname

    alternatelanguageislandname

    Note: This attribute is currently only populated in the OS Islands Address Collection.

    alternatelanguage

    alternatelanguagefulladdress

    floorlevel

    lowestfloorlevel

    This attribute is derived from Floor Level attribute data. Where the Floor Level field is NULL, Lowest Floor Level values will also be NULL.

    highestfloorlevel

    This attribute is derived from Floor Level attribute data. Where the Floor Level field is NULL, Highest Floor Level values will also be NULL.

    classificationcode

    classificationdescription

    primaryclassificationdescription

    secondaryclassificationdescription

    tertiaryclassificationdescription

    quaternaryclassificationdescription

    buildstatus

    buildstatusdate

    addressstatus

    postcodesource

    parentuprn

    rootuprn

    hierarchylevel

    usrn

    usrnmatchindicator

    localcustodiancode

    localcustodiandescription

    lowertierlocalauthoritygsscode

    easting

    northing

    latitude

    longitude

    geometry

    positionalaccuracy

    effectivestartdate

    effectiveenddate

    🆕 Related components

    Data schema versioning
    Data schema version table
    Getting started with temporal filtering guide
    changetypevalue
    themevalue
    addressdescriptionvalue
    countryvalue
    languagevalue
    AddressBase Classification Scheme page of the OS Download Products’ Documentation site
    addressclassificationcodevalue
    AddressBase Classification Scheme page of the OS Download Products’ Documentation site
    addressclassificationdescriptionvalue
    addressprimaryclassificationdescriptionvalue
    addresssecondaryclassificationdescriptionvalue
    addresstertiaryclassificationdescriptionvalue
    addressquaternaryclassificationdescriptionvalue
    buildstatusvalue
    addressstatusvalue
    addressbasepostalvalue
    usrnmatchindicatorvalue
    positionalaccuracyvalue
    Address Related Components page
    OS Select+Build Filterable: No
  • Data Schema Version: 1.0, 2.0, 3.0

  • OS Select+Build Filterable: No
  • Data Schema Version: 1.0, 2.0, 3.0

  • Max Length: 50

  • OS Select+Build Filterable: No

  • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressdescriptionvalue

    • Code List Version: 1.0

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0

    Data Schema Version: 3.0

    The organisation name is the business name given to an Address 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.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 100

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0

    Data Schema Version: 1.0, 2.0, 3.0

    Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0

    Data Schema Version: 1.0, 2.0, 3.0
    Data Schema Version: 1.0, 2.0, 3.0
    Data Schema Version: 1.0, 2.0, 3.0
    Data Schema Version: 1.0, 2.0, 3.0
    Data Schema Version: 1.0, 2.0, 3.0
    Data Schema Version: 1.0, 2.0, 3.0
    Data Schema Version: 1.0, 2.0, 3.0

    Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 500

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0

    OS Select+Build Filterable: Yes
  • Data Schema Version: 1.0, 2.0, 3.0

  • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0

    Data Schema Version: 1.0, 2.0, 3.0
    Data Schema Version: 1.0, 2.0, 3.0
    Data Schema Version: 1.0, 2.0, 3.0
    Data Schema Version: 1.0, 2.0, 3.0
    Data Schema Version: 1.0, 2.0, 3.0
    Data Schema Version: 1.0, 2.0, 3.0
    OS Select+Build Filterable: No
  • Data Schema Version: 1.0, 2.0, 3.0

  • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 500

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0

    Data Schema Version: 1.0, 2.0, 3.0
    OS Select+Build Filterable: No
  • Data Schema Version: 2.0, 3.0

  • OS Select+Build Filterable: No
  • Data Schema Version: 2.0, 3.0

  • OS Select+Build Filterable: Yes
  • Data Schema Version: 1.0, 2.0, 3.0

  • OS Select+Build Filterable: Yes
  • Data Schema Version: 1.0, 2.0, 3.0

  • OS Select+Build Filterable: Yes
  • Data Schema Version: 2.0, 3.0

  • OS Select+Build Filterable: Yes
  • Data Schema Version: 2.0, 3.0

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 3.0

  • A descriptive term used to describe the tertiary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: addresstertiaryclassificationdescriptionvalue

    • Max Length: 120

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0

    OS Select+Build Filterable: No
  • Data Schema Version: 2.0, 3.0

  • Max Length: 18

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 3.0

  • A description of the build status of the land and property unit represented by an Address, for example, 'Built In Use'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: buildstatusvalue

    • Code List Version: 1.0

    • Max Length: 12

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0

    Date when the land and property unit entered the lifecycle state given in Build Status.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0

    OS Select+Build Filterable: No
  • Data Schema Version: 1.0, 2.0, 3.0

  • Max Length: 148

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressbasepostalvalue

    • Code List Version: 1.0

    • Max Length: 75

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0

    OS Select+Build Filterable: No
  • Data Schema Version: 1.0, 2.0, 3.0

  • Data Schema Version: 1.0, 2.0, 3.0
    Data Schema Version: 1.0, 2.0, 3.0
    OS Select+Build Filterable: No
  • Data Schema Version: 1.0, 2.0, 3.0

  • OS Select+Build Filterable: No
  • Data Schema Version: 1.0, 2.0, 3.0

  • OS Select+Build Filterable: No
  • Data Schema Version: 1.0, 2.0, 3.0

  • OS Select+Build Filterable: No
  • Data Schema Version: 1.0, 2.0, 3.0

  • Geometry Type: Point

    Max Length: 25

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: positionalaccuracyvalue

    • Code List Version: 1.0

    • Max Length: 25

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0

    30 September 2025

    Ongoing

    Major version increment implementing the following changes:

    • Extended the max length of the Postcode Source, Full Address, Alternate Language Full Address, Sub Name, Alternate Language Sub Name and Build Status attributes.

    • Modified the associated code lists for the Description, Positional Accuracy and Postcode Source attributes.

    • Added download filters for Primary Classification Description, Secondary Classification Description, and Tertiary Classification Description attributes.

    • New associated code lists added to the Classification Code, Classification Description, Primary Classification Description, Secondary Classification Description, Tertiary Classification Description and Quaternary Classification Description attributes.

    2.0

    28 March 2023

    Ongoing

    Major version increment adding new attribution for Full Address, Alternate Language Full Address, Lowest Floor Level, Highest Floor Level, Primary Classification Description, Secondary Classification Description, Tertiary Classification Description and Quaternary Classification Description.

    1.0

    02 November 2022

    Ongoing

    Initial launch of the Pre-Build Address Feature Type.

    Temporal filtering

    Feature type attributes

    Loading OS NGD CSV files into databases

    Comma-separated values (CSV) file format is universally supported for easy ingestion into all major database products. Before loading OS NGD data contained in CSV files into a database, it is necessary to create relevant tables. Data definition language (DDL) statements for PostgreSQL, SQL Server and Oracle can be accessed in our OS NGD Resources GitHub repository.

    For instructions on loading CSV files, see the Getting Started with CSV guide.

    uprn

    versiondate

    versionavailablefromdate

    versionavailabletodate

    changetype

    theme

    description

    organisationname

    poboxnumber

    subname

    name

    number

    streetname

    locality

    townname

    islandname

    Note: This attribute is currently only populated in the OS Islands Address Collection.

    postcode

    fulladdress

    country

    alternatelanguagesubname

    alternatelanguagename

    alternatelanguagenumber

    alternatelanguagestreetname

    alternatelanguagelocality

    alternatelanguagetownname

    alternatelanguageislandname

    Note: This attribute is currently only populated in the OS Islands Address Collection.

    alternatelanguage

    alternatelanguagefulladdress

    floorlevel

    lowestfloorlevel

    This attribute is derived from Floor Level attribute data. Where the Floor Level field is NULL, Lowest Floor Level values will also be NULL.

    highestfloorlevel

    This attribute is derived from Floor Level attribute data. Where the Floor Level field is NULL, Highest Floor Level values will also be NULL.

    classificationcode

    classificationdescription

    primaryclassificationdescription

    secondaryclassificationdescription

    tertiaryclassificationdescription

    quaternaryclassificationdescription

    buildstatus

    buildstatusdate

    addressstatus

    postcodesource

    parentuprn

    rootuprn

    hierarchylevel

    usrn

    usrnmatchindicator

    localcustodiancode

    localcustodiandescription

    lowertierlocalauthoritygsscode

    easting

    northing

    latitude

    longitude

    geometry

    positionalaccuracy

    effectivestartdate

    effectiveenddate

    🆕 Related components

    Data schema versioning
    Data schema version table
    Getting started with temporal filtering guide
    changetypevalue
    themevalue
    addressdescriptionvalue
    countryvalue
    languagevalue
    AddressBase Classification Scheme page of the OS Download Products’ Documentation site
    addressclassificationcodevalue
    AddressBase Classification Scheme page of the OS Download Products’ Documentation site
    addressclassificationdescriptionvalue
    addressprimaryclassificationdescriptionvalue
    addresssecondaryclassificationdescriptionvalue
    addresstertiaryclassificationdescriptionvalue
    addressquaternaryclassificationdescriptionvalue
    buildstatusvalue
    addressstatusvalue
    addressbasepostalvalue
    usrnmatchindicatorvalue
    positionalaccuracyvalue
    Address Related Components page

    Max Length: 50

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0

  • OS Select+Build Filterable:
    No
  • Data Schema Version: 1.0, 2.0

  • Data Schema Version: 1.0, 2.0

    Data Schema Version: 2.0

    Data Schema Version: 1.0, 2.0

    Data Schema Version: 2.0

    OS Select+Build Filterable: Yes

  • Data Schema Version: 2.0

  • 1.0
  • Max Length: 12

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0, 2.0

  • Max Length: 75

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0, 2.0

  • Max Length: 25

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0, 2.0

  • Loading OS NGD CSV files into databases

    addressdescriptionvalue
    addresstertiaryclassificationdescriptionvalue
    buildstatusvalue
    addressbasepostalvalue
    positionalaccuracyvalue
    OS NGD Resources GitHub repository
    Getting Started with CSV

    Max Length: 50

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0

  • OS Select+Build Filterable:
    No
  • Data Schema Version: 1.0, 2.0

  • Data Schema Version: 1.0, 2.0

    Data Schema Version: 2.0

    Data Schema Version: 1.0, 2.0

    Data Schema Version: 2.0

    OS Select+Build Filterable: Yes

  • Data Schema Version: 2.0

  • 1.0
  • Max Length: 12

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0, 2.0

  • Max Length: 75

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0, 2.0

  • Max Length: 25

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0, 2.0

  • New associated code lists added to the Classification Code, Classification Description, Primary Classification Description, Secondary Classification Description, Tertiary Classification Description and Quaternary Classification Description attributes.

    Loading OS NGD CSV files into databases

    addressdescriptionvalue
    addresstertiaryclassificationdescriptionvalue
    buildstatusvalue
    addressbasepostalvalue
    positionalaccuracyvalue
    OS NGD Resources GitHub repository
    Getting Started with CSV

    Built Address

    The Built Address Feature Type represents local authority addresses that are currently built and live and can typically receive mail, deliveries, or services. For example, homes, shops, schools and hospitals.

    Data schema versioning

    The following table provides details about this feature type’s data schema versions, including the reasons behind the changes and the related launch date when each version went live.

    Data schema version table

    Version ↓
    Launch Date
    Latest Date
    Change

    3.0

    30 September 2025

    Please see for in-depth information about data schema versioning in the OS NGD.

    Temporal filtering allows you to order a one-off snapshot of data from the OS NGD from a current or past date. It is an optional step when you create a new data package in OS Select+Build (the OS NGD download service).

    The earliest and latest dates on which you can request a one-off snapshot of a date in the past for this feature type's data schema versions are indicated in the above. Please note that any data temporally filtered earlier than the specified launch date indicated in the table for the data schema versions may contain data inconsistencies.

    More information about temporal filtering on OS NGD feature types is available from the .

    The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

    Unique Property Reference Number (UPRN) assigned by a local custodian or Ordnance Survey as a persistent identifier.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Date when the version was last updated.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The date this version of the feature became the latest version.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The date this version of the feature was superseded by an update or ceased to exist.

    • Data Types: DateTime (GPKG), DateTime (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The type of change that generated a new version of the feature.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 50

    The OS NGD theme to which this feature belongs.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 40

    A single descriptive value intended for a quick understanding of what the feature represents.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version: 2.0

    The name of the organisation operating from the address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 100

    • OS Select+Build Filterable: No

    Text concatenation of 'PO BOX' and the Post Office Box (PO Box) number or the British Forces Post Office (BFPO) number.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 13

    • OS Select+Build Filterable: No

    The Sub Name is the secondary description for subdivisions of properties. For example: Sub Name: 'CRYNANT LIBRARY', Name: 'CRYNANT COMMUNITY CENTRE'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 500

    • OS Select+Build Filterable: No

    The name is the English language primary description applied to an address, for example: 'SWANSEA UNIVERSITY BAY CAMPUS' (Welsh: 'CAMPWS Y BAE PRIFYSGOL ABERTAWE'). This attribute will also include numbers when the name contains 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 name will be a blend of distinctive and descriptive naming, for example, RAILWAY TAVERN (PUBLIC HOUSE) or THE COURT ROYAL (HOTEL).

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    The number gives a unique numeric identifier for addresses on a given street, for example, '11' (per Local Authority Street Naming and Numbering conventions). This includes numbers that contain a range, decimals or non-numeric characters, for example, 1-11 and 10A.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 13

    • OS Select+Build Filterable: No

    Name, number or descriptor that identifies the nearest accessible Street that an Address is located on or close to.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 100

    • OS Select+Build Filterable: No

    Name of the area or geographical identifier within a town, settlement, village or hamlet that an address is located within. For example, a locality may be a suburb, housing estate or commercial estate.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    Name of the settlement that the Street is located within. Where a settlement can be a City, Town, Village, Hamlet or Parish.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    Name of the island upon which an Address is located.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 50

    • OS Select+Build Filterable: No

    The postcode unit that the Address is situated within. A postcode is an abbreviated form of address, made up of combinations of between five and seven alphanumeric characters. These alphanumeric characters are used by Royal Mail to help with the automated sorting of mail. A postcode may cover between 1 and 100 addresses. Postcodes (for example, NW6 4DP) are comprised of two components. The first component is the outward code (or ‘outcode’), which is the first two to four characters of a postcode, constituting the postcode area and the postcode district, for example, NW6. The outward code is the part of the postcode that enables mail to be sent from the accepting office to the correct area for delivery. The second component of a postcode is the inward code (or ‘incode’), which is the last three characters of the postcode, constituting the postcode sector and the postcode unit, for example, 4DP. The inward code is used to sort mail at the local delivery office. This field will contain the Royal Mail Postcode Address File (PAF) postcode where the Local Authority address has been matched to PAF. Where a match has not been made, the postcode information is sourced from Local Authority assigned data. In cases where the Local Authority do not hold a valid postcode, a spatial nearest neighbour function is used to spatially derive the postcode from the closest Address with a valid postcode.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 8

    • OS Select+Build Filterable: Yes

    Concatenation of the following address components: Organisation (Pre-Build and Built Address Feature Types only), Sub Name and / or Name and / or Number, Street Name, Locality, Town Name, Island Name and Postcode Locator.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 1 000

    • OS Select+Build Filterable: No

    Name of the geographical territory that the Address is located within, where a geographical territory represents either a devolved country or an island nation.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 16

    The Alternate Language Sub Name is the alternate language secondary description for subdivisions of properties. For example: Alternate Language Sub Name: 'LLYFRGELL Y CREUNANT', Alternate Language Name: 'CANOLFAN CYMUNED CREUNANT'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 500

    • OS Select+Build Filterable: No

    The Alternate Language Name is the alternate language primary description applied to an address, for example: 'CAMPWS Y BAE PRIFYSGOL ABERTAWE' (English: 'SWANSEA UNIVERSITY BAY CAMPUS'). This attribute may also include numbers when the name contains 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 name will be a blend of distinctive and descriptive naming, for example, RAILWAY TAVERN (PUBLIC HOUSE) or THE COURT ROYAL (HOTEL).

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    The Alternate Language Number gives a unique numeric identifier for addresses on each street, for example, '11' (per Local Authority Street Naming and Numbering conventions). Numbers that contain a range, decimals or non-numeric characters do not appear in this field but will be found in the Name or the Sub Name attributes.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 13

    • OS Select+Build Filterable: No

    Name, number or descriptor that identifies the nearest accessable street that an Address is located on or close to, defined in either Welsh (cym) or Gaelic / Scottish Gaelic (gla).

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 100

    • OS Select+Build Filterable: No

    Name of the area or geographical identifier within a town, settlement, village or hamlet that an address is located within, defined in either Welsh (cym) or Gaelic / Scottish Gaelic (gla). For example, a locality may be a suburb, housing estate or commercial estate.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    The name of the settlement that the address is located within, defined in either Welsh (cym) or Gaelic / Scottish Gaelic (gla). A settlement can be a City, Town, Village, Hamlet or Parish.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    Name of the island upon which an Address is located.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 50

    • OS Select+Build Filterable: No

    ISO 3166-3 Language Code for Welsh or Gaelic / Scottish Gaelic.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 3

    Concatenation of the following alternate language address components: Organisation (Pre-Build and Built Address Feature Types only), Alternate Language Sub Name and / or Alternate Language Name and / or Alternate Language Number, Alternate Language Street Name, Alternate Language Locality, Alternate Language Town Name, Alternate Language Island Name and Postcode Locator.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 1 000

    • OS Select+Build Filterable: No

    Floor level represents either: the access point to the Address, or the floor level or levels that the Address is located on fully occupies or represents occupiable space within the property.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 30

    • OS Select+Build Filterable: No

    In cases where the Floor Level attribute contains a list of floor levels (for example, where a commercial organisation occupies multiple levels within a building), the first value provided will be taken as the lowest floor level. For example, where Floor Level attribute values are given as -1, 0, 1, 2, 3, the Lowest Floor Level is -1. Mezzanine levels may be represented by a partial number, for example, 1.5. If the Floor Level attribute only contains one value, that value will also be used by the Lowest Floor Level attribute.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 3

    • Scale: 1

    In cases where the Floor Level attribute contains a list of floor levels (for example, where a commercial organisation occupies multiple levels within a building), the last value provided will be taken as the highest floor level. For example, where Floor Level attribute values are given as -1, 0, 1, 2, 3, the Highest Floor Level is 3. Mezzanine levels may be represented by a partial number, for example, 1.5. If the Floor Level attribute only contains one value, that value will also be used by the Highest Floor Level attribute.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: true

    • Precision: 3

    • Scale: 1

    Alphanumeric code used to classify the object using the AddressBase Classification Scheme, which is available to download from the .

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 6

    Description of the classification code as defined in the AddressBase Classification Scheme, which is available to download from the .

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 230

    A descriptive term used to describe the primary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 120

    A descriptive term used to describe the secondary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Code List Name:

    • Nullable: true

    • Max Length: 120

    A descriptive term or collection of terms used to describe the tertiary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 120

    A descriptive term or collection of terms used to describe the quaternary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name:

    • Max Length: 120

    A description of the build status of the Address, for example, 'Built Complete'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version: 2.0

    Date when the address entered the lifecycle state given in Build Status.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 3.0

    The lifecycle status of a given Address, for example, 'Provisional' and 'Approved'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 11

    Identifies the source of the postcode assigned to an address. This attribute can be used to identify properties capable of receiving mail as defined by Royal Mail for PAF matched address records, or as defined by Local Authorities for records which are not PAF matched but which are believed to be capable of receiving mail. For example, flats behind a front door with single letter box.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version: 2.0

    Unique Property Reference Number (UPRN) of the parent record if a parent-child relationship exists.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    In instances where an address sits in a hierarchy (for example, Child UPRN – Parent UPRN – Grandparent UPRN), the Root UPRN will display the Unique Property Reference Number (UPRN) for the top level Addressable Object in the parent-child structure, which in this example is the Grandparent UPRN.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    In instances where an address sits in a hierarchy (for example, Child UPRN – Parent UPRN – Grandparent UPRN), the Hierarchy Level attribute describes the position of the given UPRN within the overall set of relationships. For example, FLAT 1 is the Child UPRN at the lowest level and its Hierarchy Level will be 3; its Parent UPRN is BLOCK H, which will have a Hierarchy Level of 2; BLOCK H has, in turn, a Parent UPRN of EXETER UNIVERSITY, which will have a Hierarchy Level of 1.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The Unique Street Reference Number (USRN), a unique and persistent identifier of a Street which is assigned by the Roads or Highway Authority.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Description of the type of match made between the Unique Property Reference Number (UPRN) and its Unique Street Reference Number (USRN). A value of 1 is matched manually to the most accessible USRN, and a value of 2 is matched spatially to the nearest USRN, which may not be the nearest accessible street.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Max Length: 17

    Numeric code identifying the authority responsible for assigning the Unique Property Reference Number (UPRN), creating and maintaining the address record.

    • Data Types: Integer (GPKG), Integer (CSV)

    • Nullable: false

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0, 3.0

    Name of the authority responsible for assigning the Unique Property Reference Number (UPRN), creating and maintaining the address record.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 35

    • OS Select+Build Filterable: Yes

    The Office for National Statistics Governmental Statistical Service (GSS) code representing the lower tier local authority.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 9

    • OS Select+Build Filterable: Yes

    X coordinate defining the position of the object in accordance with the British National Grid (EPSG:27700) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 8

    • Scale: 2

    Y coordinate defining the position of the object in accordance with the British National Grid (EPSG:27700) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 2

    Value defining the latitude of the Address location in accordance with the ETRS89 (EPSG:4258) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 7

    Value defining the longitude of the Address location in accordance with the ETRS89 (EPSG:4258) coordinate reference system.

    • Data Types: Float (GPKG), Real (CSV)

    • Nullable: false

    • Precision: 9

    • Scale: 7

    Geometry for the feature.

    • Data Types: Geometry (GPKG), WKT (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Local Authority assigned value giving a description of the accuracy of the coordinate position allocated to the Address location, for example, 'Central Internal Position' of a building.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name:

    • Code List Version: 2.0

    The date on which this record was inserted into the Local Authority database.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: false

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    The date on which the record ceased to exist.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0, 3.0

    Selected related components are provided for the Built Address Feature Type.

    Customers taking data schema version 1.0 or 2.0 of the Built Address Feature Type in GeoPackage format will receive the following in their data package:

    • Feature type: Built Address

    • Related components: Alternate Address, Postal Address, Other Classification and Related Entity

    Customers taking data schema version 3.0 onward of the Built Address Feature Type in GeoPackage format will receive the following in their data package:

    • Feature type: Built Address

    • Related components: Alternate Address, Other Classification and Related Entity

    Please see the for more information about the related components and how to handle them.

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0

  • Max Length: 50

  • OS Select+Build Filterable: No

  • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressdescriptionvalue

    • Code List Version: 1.0

    • Max Length: 50

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0

    Data Schema Version: 3.0

    The organisation name is the business name given to an Address 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.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 100

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0

    Data Schema Version: 1.0, 2.0, 3.0

    Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0

    Data Schema Version: 1.0, 2.0, 3.0

    Data Schema Version: 1.0, 2.0, 3.0

    Data Schema Version: 1.0, 2.0, 3.0

    Data Schema Version: 1.0, 2.0, 3.0

    Data Schema Version: 1.0, 2.0, 3.0

    Data Schema Version: 1.0, 2.0, 3.0

    Data Schema Version: 1.0, 2.0, 3.0

    Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Max Length: 500

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0

    OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0, 2.0, 3.0

  • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 110

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0

    Data Schema Version: 1.0, 2.0, 3.0

    Data Schema Version: 1.0, 2.0, 3.0

    Data Schema Version: 1.0, 2.0, 3.0

    Data Schema Version: 1.0, 2.0, 3.0

    Data Schema Version: 1.0, 2.0, 3.0

    Data Schema Version: 1.0, 2.0, 3.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0

  • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Max Length: 500

    • OS Select+Build Filterable: No

    • Data Schema Version: 2.0

    Data Schema Version: 1.0, 2.0, 3.0

    OS Select+Build Filterable: No

  • Data Schema Version: 2.0, 3.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.0, 3.0

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0, 2.0, 3.0

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0, 2.0, 3.0

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 2.0, 3.0

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 2.0, 3.0

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 3.0

  • A descriptive term used to describe the tertiary classification code for this address.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: true

    • Code List Name: addresstertiaryclassificationdescriptionvalue

    • Max Length: 120

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 2.0

    OS Select+Build Filterable: No

  • Data Schema Version: 2.0, 3.0

  • Max Length: 18

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 3.0

  • A description of the build status of the land and property unit represented by an Address, for example, 'Built In Use'.

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: buildstatusvalue

    • Code List Version: 1.0

    • Max Length: 12

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0

    Date when the land and property unit entered the lifecycle state given in Build Status.

    • Data Types: Date (GPKG), Date (CSV)

    • Nullable: true

    • OS Select+Build Filterable: No

    • Data Schema Version: 1.0, 2.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0

  • Max Length: 148

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: addressbasepostalvalue

    • Code List Version: 1.0

    • Max Length: 75

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0

  • Data Schema Version: 1.0, 2.0, 3.0

    Data Schema Version: 1.0, 2.0, 3.0

    OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0

  • Geometry Type: Point

    Max Length: 25

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 3.0

    • Data Types: String (GPKG), String (CSV)

    • Nullable: false

    • Code List Name: positionalaccuracyvalue

    • Code List Version: 1.0

    • Max Length: 25

    • OS Select+Build Filterable: Yes

    • Data Schema Version: 1.0, 2.0

    Ongoing

    Major version increment implementing the following changes:

    • Extended the max length of the Postcode Source, Full Address, Alternate Language Full Address, Sub Name, Alternate Language Sub Name and Build Status attributes.

    • Modified the associated code lists for the Description, Positional Accuracy and Postcode Source attributes.

    • Added download filters for Primary Classification Description, Secondary Classification Description, and Tertiary Classification Description attributes.

    • New associated code lists added to the Classification Code, Classification Description, Primary Classification Description, Secondary Classification Description, Tertiary Classification Description and Quaternary Classification Description attributes.

    2.0

    28 March 2023

    Ongoing

    Major version increment adding new attribution for Full Address, Alternate Language Full Address, Lowest Floor Level, Highest Floor Level, Primary Classification Description, Secondary Classification Description, Tertiary Classification Description and Quaternary Classification Description.

    1.0

    02 November 2022

    Ongoing

    Initial launch of the Built Address Feature Type.

    Temporal filtering

    Feature type attributes

    Loading OS NGD CSV files into databases

    Comma-separated values (CSV) file format is universally supported for easy ingestion into all major database products. Before loading OS NGD data contained in CSV files into a database, it is necessary to create relevant tables. Data definition language (DDL) statements for PostgreSQL, SQL Server and Oracle can be accessed in our OS NGD Resources GitHub repository.

    For instructions on loading CSV files, see the Getting Started with CSV guide.

    uprn

    versiondate

    versionavailablefromdate

    versionavailabletodate

    changetype

    theme

    description

    organisationname

    poboxnumber

    subname

    name

    number

    streetname

    locality

    townname

    islandname

    Note: This attribute is currently only populated in the OS Islands Address Collection.

    postcode

    fulladdress

    country

    alternatelanguagesubname

    alternatelanguagename

    alternatelanguagenumber

    alternatelanguagestreetname

    alternatelanguagelocality

    alternatelanguagetownname

    alternatelanguageislandname

    Note: This attribute is currently only populated in the OS Islands Address Collection.

    alternatelanguage

    alternatelanguagefulladdress

    floorlevel

    lowestfloorlevel

    This attribute is derived from Floor Level attribute data. Where the Floor Level field is NULL, Lowest Floor Level values will also be NULL.

    highestfloorlevel

    This attribute is derived from Floor Level attribute data. Where the Floor Level field is NULL, Highest Floor Level values will also be NULL.

    classificationcode

    classificationdescription

    primaryclassificationdescription

    secondaryclassificationdescription

    tertiaryclassificationdescription

    quaternaryclassificationdescription

    buildstatus

    buildstatusdate

    addressstatus

    postcodesource

    parentuprn

    rootuprn

    hierarchylevel

    usrn

    usrnmatchindicator

    localcustodiancode

    localcustodiandescription

    lowertierlocalauthoritygsscode

    easting

    northing

    latitude

    longitude

    geometry

    positionalaccuracy

    effectivestartdate

    effectiveenddate

    🆕 Related components

    Data schema versioning
    Data schema version table
    Getting started with temporal filtering guide
    changetypevalue
    themevalue
    addressdescriptionvalue
    countryvalue
    languagevalue
    AddressBase Classification Scheme page of the OS Download Products’ Documentation site
    addressclassificationcodevalue
    AddressBase Classification Scheme page of the OS Download Products’ Documentation site
    addressclassificationdescriptionvalue
    addressprimaryclassificationdescriptionvalue
    addresssecondaryclassificationdescriptionvalue
    addresstertiaryclassificationdescriptionvalue
    addressquaternaryclassificationdescriptionvalue
    buildstatusvalue
    addressstatusvalue
    addressbasepostalvalue
    usrnmatchindicatorvalue
    positionalaccuracyvalue
    Address Related Components page

    FAQs

    Frequently asked questions on OS NGD data and the download service of OS Select+Build.

    FAQs covering the OS NGD APIs are available on the .

    General FAQs

    What is the OS NGD?

    The OS National Geographic Database (OS NGD) is a structured database containing authoritative geospatial data for Great Britain. It provides the most current, comprehensive and richly attributed data describing Great Britain ever produced by OS in non-proprietary data formats that are easily integrated into a wide array of customer systems and workflows.

    How do I access the OS NGD?

    There are two access methods for OS NGD data:

    • OS Select+Build (the download service)

    • OS NGD APIs

    Who can access the OS NGD?

    The OS NGD is available to OS Partners and to public sector organisations who are members of the Public Sector Geospatial Agreement (PSGA). OS Select+Build (the download service) and the OS NGD APIs can be accessed via the OS Data Hub on either the Premium Plan or Public Sector Plan.

    Find out more about the PSGA by visiting the OS website, including the benefits of joining, instructions on how to access OS data, success stories, support, registration process information and instructions, and a PSGA Member finder tool to check if your organisation is already a member.

    Data Exploration Licence

    Alternatively, you can try out OS NGD collection data for free for three to six months by applying for a Data Exploration Licence. This licence is available for all collections apart from the OS Islands Address and OS Functional Areas Collections.

    The licence is primarily designed for organisations either considering becoming an OS Partner or who want to trial OS Premium data before working with an existing OS Partner.

    What is the PSGA?

    The Public Sector Geospatial Agreement (PSGA) sets out how Ordnance Survey (OS) provides world-leading location data and expertise to the public sector across Britain. It supports the delivery of critical infrastructure and services, as well as working to help protect our environment. 

    The OS NGD is available to OS Partners and to public sector organisations who are members of the PSGA.

    Find out more about the PSGA by visiting the OS website, including the benefits of joining, instructions on how to access OS data, success stories, support, registration process information and instructions, and a PSGA Member finder tool to check if your organisation is already a member.

    What are the benefits of the OS NGD?

    Please see the OS NGD Key Benefits to Customers page for a full rundown of the benefits.

    What file formats are available for OS NGD data?

    OS NGD data is available in four easy-to-use formats: GeoPackage, CSV (comma-separated values), GeoJSON and vector tiles. The download service of OS Select+Build supports GeoPackage and CSV. OS NGD API – Features supports GeoJSON. OS NGD API – Tiles supports vector tiles.

    For more information about the file formats, please see the File formats and naming page.

    Why are there TOIDs in the OS NGD which are not in OS Premium products?

    Features are now available to customers more quickly in the OS NGD than they are in OS Premium or OS OpenData products. OS NGD features that will also ultimately be supplied in existing products with a TOID will now appear in the OS NGD in advance of their publication in OS Premium or OS OpenData products. At a future refresh of OS Premium or OS OpenData products, these features will appear with the same TOID.

    Is COU data available?

    Monthly and daily COU (Change-Only Update) supplies are available for CSV files; however, they are not available for GeoPackage files. For more information about COUs, please see the COU supplies page and the Data ordering and currency page.

    Why won't my CSV file open in excel / why won't my CSV file load in my GIS?

    Please be aware that CSV (comma-separated values) files are designed to be opened in a database or GI system, and opening them in other software applications could corrupt the data. In particular, Excel has a row limit which might be exceeded by some of our CSV files containing OS NGD data, depending on the order you placed and its size.

    We recommend that you load CSV files containing OS NGD data directly into a database or GI system, rather than trying to open these files in Excel.

    For more information about CSV files, please see the File formats and naming page.

    Does the launch of the OS NGD mean that some existing OS Premium and OS OpenData products will be withdrawn?

    No. The launch of the OS NGD does not instigate withdrawal of any of the existing OS Premium or OS OpenData Download products, including APIs. These products will continue to be managed through their product lifecycle, including withdrawal / becoming End of Life, separately to the OS NGD.

    The OS NGD gives new and enhanced ways for customers to access the most trusted and up-to-date geographic information from OS.

    The OS Product Roadmap is available to view on our website – it has details of upcoming OS NGD releases, new Download product releases (for Premium and OpenData products), and dates for planned product withdrawals as they reach their End of Life stage.

    Why do I have different start dates when applying temporal filters to different feature types?

    Following the launch of the OS NGD in September 2022, we have and will continue to add new feature types as part of our . These could be brand new feature types or enhanced versions of previously existing feature types (with new attribution added for a new version). In both instances, these new / enhanced feature types will have later start dates.

    The earliest date on which you can request a one-off snapshot of a date in the past for data in a feature type in most collections is 29 September 2022, but that date can be later for certain feature types (for example, it's 28 March 2023 for the Waterbody Catchment Feature Type). Each feature type page states the earliest start date available for temporal filtering on that feature type.

    How is OS NGD file naming managed?

    Please refer to the File formats and naming page for information about the OS NGD file naming convention.

    Why am I receiving blank files?

    You could have received blanks files for one of the following reasons:

    • You are collecting data via a COU (Change-Only Update) and there has been no change.

    • You have selected a feature type from one of the following OS NGD collections which has a different update frequency from your selected COU: OS Boundaries Collection (updated biannually), OS Functional Areas Collection (updated biannually), OS GB Postcodes and OS NI Postcodes Collections (both updated monthly), OS Transport Features Collection (updated daily, with the exception of the Street Light Feature Type which is updated monthly), OS Transport Network Collection (updated monthly), OS RAMI Collection (updated monthly) or the OS Water Network Collection (updated quarterly).

    • You have requested data via a temporal filter (i.e. a one-off snapshot of a date in the past) that predates the start date for data from one or more of the collections in your order. The earliest date on which you can request a one-off snapshot of a date in the past for data in a feature type in most collections is 29 September 2022, but that date can be later for certain feature types (for example, it's 28 March 2023 for the Waterbody Catchment Feature Type). Each feature type page states the earliest start date available for temporal filtering on that feature type.

    • You have selected the Annual Full Supply order frequency option for a data package containing one (or more) of the new feature types or new data schema versions of existing feature types released in March and / or September of the current year. If you select an Annual Full Supply frequency for your OS NGD data order in OS Select+Build, we will provide you with the data as it was on 01 January of the current year. This means if a new feature type or a new data schema version of an existing feature type was released after 01 January and you order either of these as part of your Annual Full Supply, you will receive an empty data package for the newly released feature type / new data schema version of an existing feature type. The data for the new feature type / new data schema version of an existing feature type will then be included in your supply on the next 01 January after the release, after which point, data packages containing one of these feature types will no longer contain blank files.

      • For example, the March 2026 OS NGD data enhancements release contained six new feature types (Retail Area Aggregated, Retail Area Major, Retail Area Minor, Postcode Unit Point, Postcode Unit Point, and Postcode Unit Area) and one new data schema version for an existing feature type (Compound Structure v3.0). The data for the new feature types and the new data schema version for the existing feature type will not be part of Annual Full Supply orders until 01 January 2027.

    • You have an existing OS Select+Build recipe that uses the Site Routing Point Feature Type or transacts with that feature type via an OS NGD API. As of 26 April 2023, this feature type no longer contains any features or data. It is in an 'end of life' state where it has stopped receiving updates; therefore, any OS Select+Build recipes that use this feature type or any OS NGD APIs that transact with it will return blank files. You can access historic data for Site Routing Point using the temporal filter option in OS Select+Build by selecting the tick box for a 'one-off snapshot'; historic data is available for this feature type from 03 October 2022 to 25 April 2023. As part of a data enhancement programme in late spring 2023, all Site Routing Points were recreated as and are therefore now accessible via the OS NGD Transport Theme (from the OS Transport Network Collection).

    What is data schema versioning and how does it work in the OS NGD?

    Please see the Data schema versioning page in the OS NGD Fundamentals section for a full explanation of data schema versioning and how it works in the OS NGD.

    Can I download OS NGD documentation for offline use?

    Yes. OS NGD documentation can be saved to a PDF for you to review offline. To create a PDF of a page, click the 'More' button (which looks like a downward arrow) to the right of the 'Copy' button at the top right-hand side of the page, then select the 'Export as PDF' option from the drop-down list.

    How to find the 'Export as PDF' option on this documentation site.

    This tool allows you to download individual pages or groups of pages that make up a complete document. You should limit your documents to a maximum of 100 pages per PDF to prevent issues when saving or opening the file.

    What is the difference between 'Unknown' and 'NULL' attribute values?

    'Unknown' is used in two main circumstances:

    • Where an attribute is expected to be populated but Ordnance Survey does not currently have a value. For example, a feature captured by a remote sensed survey where the land use has not yet been determined.

    • Where an attribute is expected and Ordnance Survey has attempted to obtain a value, but this has not been possible. For example, the ‘use’ of an inactive or derelict site is not clear.

    In summary, 'Unknown' means the attribution value is in scope, but Ordnance Survey does not currently know what that value is.

    'NULL' is used in two main circumstances:

    • The value is not applicable to the attribute in question in this instance – typically, where an attribute value is optional. For example, non-mandatory references to other OS NGD features, such as from Land features to an associated Structure feature, or from a Building feature to a land use Site feature where those referenced features may not exist in the real world.

    • The information is currently out of scope for provision on this attribute for all instances of this feature – usually where there is no viable method of capturing reliable information. For example, is only provided on a range of land use Site features with a specific function. The on land use Site features where provision of a reliable value is not possible is recorded as 'NULL'.

    In summary, 'NULL' means the attribution value either does not exist or is not in the current scope of Ordnance Survey capture.

    Can I try out OS NGD data for free using a Data Exploration Licence?

    Yes, you can try out most OS NGD collection data for free for three to six months by applying for a Data Exploration Licence (DEL). This licence is primarily designed for organisations either considering becoming an OS Partner or who want to trial OS Premium data before working with an existing OS Partner. More information about the licence is available from the OS website.

    The licence is available for all OS NGD collections apart from the OS Islands Address and OS Functional Areas Collections. It will let you use data from the OS GB Address, OS GB Postcodes and OS NI Postcodes Collections data for three months and data from all other collections (apart from the OS Islands Address and OS Functional Areas Collections) for six months.

    OS NGD Collection
    Length of DEL
    How can I verify my data download is correct?

    Feature types downloaded via OS Select+Build will be supplied with an Order Summary File, a JSON manifest that provides metadata for that specific supply. You can use the manifest to validate the data to ensure the currency, record count, schema version, feature name and coordinate reference system (CRS) match your expected order.

    You can find more detail on the contents of the order summary file and how to use it to validate your data order on the Data ordering and currency page in the OS NGD Fundamentals guide.

    API FAQs

    OS Select+Build FAQs

    Which formats can be taken using OS Select+Build and at what frequencies?

    The download service of OS Select+Build supports GeoPackage and CSV file formats (more information on these file formats is available on the File formats and naming page from the OS NGD Fundamentals section).

    For information about data ordering and currency, please see the Data ordering and currency page.

    What are the default coordinate reference systems (CRS) used by the OS NGD collections in OS Select+Build?

    Please see the Coordinate reference systems page in the OS NGD Fundamentals section for full details.

    It is possible to select what CRS you'd like to receive data in for feature types in your data package. There's more information about selecting a CRS on the Getting started with data packages page. If you don't choose a particular CRS for your data package, OS Select+Build will automatically select the default CRSs for the feature types in your data package for you.

    What is a recipe and how do I create one?

    A recipe is a bespoke selection of OS NGD data which is made by a user within OS Select+Build. Recipes allow you to choose the OS NGD data that best fit your requirements.

    Please see the Getting started with recipes page for more information about recipes and step-by-step instructions for creating them.

    How do I edit a recipe?

    Please see the Editing OS Select+Build recipes page for step-by-step instructions on how to edit a recipe.

    How do I delete a recipe?

    Please see the Managing OS Select+Build recipes page for step-by-step instructions on how to delete a recipe.

    How do I know which recipes are associated with which data package?

    Please see the Getting started with data packages page for step-by-step instructions on how to check which recipes are associated with each data package.

    How do I create an OS Select+Build data package?

    Please see the Getting started with data packages page for step-by-step instructions on creating an OS Select+Build data package.

    How do I delete an OS Select+Build data package?

    Please see the Getting started with data packages page for step-by-step instructions on deleting an OS Select+Build data package.

    How does AOI ordering work with OS Islands Address Collection data?

    The OS Islands Address Collection contains data for Northern Ireland, the Isle of Man, and the Channel Islands. When ordering data from this collection, you will be provided with a full supply of the data regardless of whether you select 'All of Britain or Predefined Area', or an 'area of interest' (AOI)​.

    For example, if you order the OS Islands Address Collection and the Building Line Feature Type selected with an AOI, then you will receive the Building Line Feature Type data for your selected AOI and all of the OS Islands Address Collection data​ (i.e. data for Northern Ireland, the Isle of Man, and the Channel Islands, and not just data for your AOI).

    How do I use attribute filtering in OS Select+Build?

    Please see the Getting started with attribute filtering page for step-by-step instructions on how to filter attributes using OS Select+Build.

    How do I identify the correct OS NGD collection for calculating usage?

    The OS NGD collection can be identified within the file name of your .zip file: themeshortcode_collectionshortcode_featuretype.zip.

    For example, bld_fts_buildingpart.zip is the file name which would be created for an order of the Building Part Feature Type within the OS Building Features Collection of the OS NGD Buildings Theme.

    For more information about the file naming convention for OS NGD data, please see the File formats and naming page in the OS NGD Fundamentals section.

    🆕 Unused order notifications FAQs

    What are unused order notifications?

    When any customer downloads an OS NGD data package, either via the OS Data Hub or OS Downloads API, there is a record of this activity. To support you in managing and maintaining your OS NGD data packages, if one is no longer being consumed by users in your organisation, we'll notify admins and the data package creator to let them know that their data package may no longer be required.

    What are the timescales for triggering unused order notifications?

    The timescales for triggering unused order notifications vary depending on the update frequency set for the OS NGD data packages:

    Data Package Update Frequency
    Unused Order Notification Sent After

    Daily

    7 days of no downloads

    What if I want to keep updates going on my data package?

    As long as a data package receives one download between the the time the unused order notification is sent and the stop date, then updates to it will continued uninterrupted.

    The total time until updates are stopped for an unused OS NGD data package varies depending upon the update frequency that's been set for it:

    Data Package Update Frequency
    Unused Order Notification Sent After
    Updates Stopped After
    Total Time Until Updates are Stopped
    What if I need to restart updates on my data package?

    Once updates to an OS NGD data package have been stopped, there is a period of time in which you can restart them and all updates between the stop and restart dates will be fulfilled for your data package:

    Data Package Update Frequency
    Unused Order Notification Sent After
    Updates Stopped After
    Total Time Until Updates are Stopped
    Restart Orders
    What if I need to restart updates to my data package but it is after the restart period?

    Unfortunately, if you miss the window where you can restart updates to your OS NGD data package, you'll need to create a new data package order.

    Please see the Getting started with data packages page for step-by-step instructions on creating a new data package.

    What happens to data packages where updates have been stopped?

    OS NGD data packages will remain available for you to download from the OS Data Hub for 12 months after the date that their updates were stopped.

    Theme-specific FAQs

    🔃 OS NGD Address Theme FAQs

    Can I use OS NGD Address Theme data to update my AddressBase Premium holding?

    We wouldn't recommend trying to use OS NGD Address Theme data to update existing product supplies of AddressBase products. The different data format and attribution mean that there are no direct mappings available back to AddressBase products, and there is a risk of updating your existing holding incorrectly.

    Why are there historic addresses in the Alternate Address data?

    The Alternate Address Related Component provides alternative address labels where they exist for a ‘current’ address, independent of whether these alternate labels are current / live or historic. Where a historic address label is present but there is also a live / approved address label, then the historic version will appear in the Alternate Address data.

    How does lifecycle work in OS NGD Address Theme data?

    As addresses move through different stages of their lifecycle, you will see different update types dependent on your chosen data package. In OS NGD Address Theme data, pre-build, built, and historic addresses are kept in separate feature types. This means that as an address moves from one stage to another (for example, pre-build to built), it will be removed from one feature type and added to the other. This differs to AddressBase Premium, where, when an address changes from one stage to another, the record is updated, i.e. not deleted from one table and inserted into another. This will also mean that, if, for example, a user has a data package that includes pre-build addresses but not built addresses, as an address moves from pre-build to built in its lifecycle, the user will see a deletion to the record that they hold of this address.

    Why are there addresses flagged as 'Non-Postal' that are not in the Non-Addressable Object Feature Type?

    Addresses that cannot receive post are classified as such for various reasons. Therefore, there are a number of different ways of extracting addresses that occupy different classes of 'Non-Postal'. The terms 'Non-Postal' and 'Non-Addressable Objects' used in OS NGD Address Theme data represent categories of addresses which are defined by differing logic.

    Non-Addressable Objects are features which OS deem to always be non-postal. This is our most certain view of addresses that are non-postal, for example, Bandstands, Telephone Boxes, and Nature Reserves. The vast majority of Non-Addressable Objects will also have an 'N' value in the Postcode Source attribute.

    'Non-Postal' in the Description attribute is essentially an amalgamation of all addresses that are defined by Local Authorities to be either 'N: Non-Postal' or 'L: Maybe Postal', and therefore is most relevant for customers who are only interested in using it as a filter to get to the 'Postal' addresses.

    The Postcode Source attribute is the best attribute to use if you are interested in a more nuanced representation of Non-Postal addresses. This splits out 'Not-postal' and 'Maybe Postal' into two different code lists. The vast majority of addresses that have Non-postal in the description field but are not in the Non-Addressable Object Feature Type are likely to be 'Maybe Postal' addresses. This is a Local Authority representation of addresses that may be able to receive post, such as Car Parks.

    What does parent-child relationship mean?

    The parent-child relationship is used to relate multiple addresses to each other. These are most commonly used to relate addresses within a building, for example, a block of flats. A parent Unique Property Reference Number (UPRN) is assigned to the building shell to give an indication that the flats within that building are related to the overarching address, for example, Example Court and the flats within.

    A good example of this is:

    • Parent: 1 High Street (UPRN: 1234)

    • Child: Flat A, 1 High Street (UPRN: 2345)

    • Child: Flat B, 1 High Street (UPRN: 3456)

    However, parent-child relationships also work beyond the level of a single building footprint and can be used to relate addresses in a larger addressable site to each other, for example, University buildings on the same campus site.

    An example of this is:

    • Parent: Exeter University (UPRN 1)

    • Child of UPRN 1: Block C, Exeter University (UPRN 2)

    • Child of UPRN 2: Flat 1, Block C, Exeter University (UPRN 3)

    Please note: Parent records are only inserted where child addresses share part of an address, for example, '1 High Street' in the above example. If two flats occupy the same building but are addressed 12A and 13A, then no parent record would be created.

    What's the source of the improved level information for the Floor Level, Lowest Floor Level and Highest Floor Level attributes?

    These attributes are populated by data captured by local authority address custodians. The data previously had been available within our AddressBase products, but there was a large variation in the textual format. The level information has been standardised into an ordered numeric list (for example, ‘First Floor’ is now ‘1’, and ‘Ground Floor’ is now ‘0’ and remains a string field).

    How is the Full Address attribute populated in OS NGD Address?

    In OS NGD Address Theme data, the Full Address attribute is populated entirely from address data sourced from local authorities. This differs from the logic behind the Full Address attribute used in the AddressBase Core product, which is populated with information from Royal Mail and data from local authorities.

    Royal Mail Address Feature Type FAQs

    🆕 What is the Royal Mail Address Feature Type?

    The Royal Mail Address Feature Type provides full copies of Royal Mail’s datasets. For data schema versions 1.0 and 1.1 of the feature type, this includes Postcode Address File (PAF) only; for data schema version 2.0 of Royal Mail Address, this includes PAF, Not Yet Built (NYB) and Multiple Residence (MR). Additional attribution is supplied with data schema version 2.0 of the feature type, including point geometry, and metadata showing the relationship between Royal Mail delivery points (identified by Unique Delivery Point Reference Numbers – UDPRNs) and local authority addresses (identified by Unique Property Reference Numbers – UPRNs).

    The feature type is available from two OS NGD collections: the OS GB Address and OS Islands Address Collections.

    🆕 Which Royal Mail datasets are included with the Royal Mail Address Feature Type?

    The latest OS NGD release in October 2026 includes Postcode Address File (PAF), Not Yet Built (NYB) and Multiple Residence (MR) in the Royal Mail Address Feature Type (data schema version 2.0).

    Postcode Information File (PIF) and Alias are also road mapped for inclusion in the OS NGD by late 2027 or 2028.

    🆕 How does the Royal Mail Address Feature Type compare with AddressBase Premium?

    AddressBase Premium only represents Postcode Address File (PAF) records in the Delivery Point Address table where a one-to-one Unique Delivery Point Reference Number-Unique Property Reference Number (UDPRN-UPRN) match exists. It does not include many-to-one, parent or street matches. The Royal Mail Address Feature Type represents the full PAF dataset, including records without a local authority match.

    AddressBase Premium also does not include Multiple Residence (MR) or Not Yet Built (NYB) content.

    🆕 Can you access the Royal Mail Address Feature Type through OS Places API?

    Not currently. There are no immediate plans to add Royal Mail Address Feature Type content or attribution to the OS Places API. OS Places API is supplied through a different data feed, so existing OS Places API address locations will not change as a result of this feature type launching.

    🆕 With the release of the Royal Mail Address Feature Type, will earlier data schema versions of other feature types in the OS NGD Address Theme be retired?

    There are currently no plans to remove data schema versions 1.0 or 2.0 of the Built Address, Historic Address, Non-Addressable Object and Pre-Build Address Feature Types from the OS NGD Address Theme. Customers must choose to move to the newest data schema version to access the Royal Mail Address Feature Type. If any data schema version of an addressing feature type is frozen in future, OS expects to give 12 months’ notice to customers.

    🆕 Following the release of the Royal Mail Address Feature Type, have there been changes to code lists or Build Status values?

    Yes. The latest OS NGD Address Theme data enhancements released in Autumn 2025 and 2026 introduce new code lists and updates existing ones, covering areas such as geometry allocation, match methods, classification descriptions and build status. Labels in the Build Status Value Code List are now aligned with updated GeoPlace guidance, for example, 'Built In Use' becomes 'Built Complete', and 'Built Vacant' becomes 'Built Unoccupiable'.

    🆕 Why are the Other Alias and Delivery Point Alias Related Component tables in my Royal Mail Address Feature Type order empty?

    The Royal Mail Address Feature Type (data schema version 2.0 onward) data model includes a number of alias related component tables, including Delivery Point Alias and Other Alias; these tables have been included in the feature type's schema to support future enhancements, but they are not currently populated with data.

    At present, OS does not have a data supply mechanism for the Royal Mail datasets that would provide the information required to populate these two alias related components. As a result, these related component tables are included in the schema but will be returned empty.

    These related components were intentionally included in the data model to provide future compatibility. By incorporating them now, customers will not need to make any schema or application changes should OS introduce support for these datasets in the future. Once a suitable data supply mechanism is available, the relevant alias information can be populated and delivered through the existing Royal Mail Address Feature Type structure, allowing the data to flow seamlessly into customer environments without the need for schema version upgrades or re-engineering.

    🆕 What is the difference between a UPRN and a UDPRN?

    A UPRN is a 12-digit Unique Property Reference Number managed by OS and local authorities. A UDPRN is an 8-digit Unique Delivery Point Reference Number assigned by Royal Mail to a postal delivery point and used in their Postcode Address File (PAF) and Not Yet Built (NYB) products.

    🆕 What UPRN to UDPRN relationships are supported?

    The data model supports one Unique Property Reference Number (UPRN) matching to multiple Unique Delivery Point Reference Numbers (UDPRNs). It does not support multiple UPRNs matching to one UDPRN. The UDPRN is the unique identifier in the Royal Mail Address Feature Type; UPRNs are not unique within this feature type.

    🆕 What UPRN to UMRRN relationships are supported?

    The data model supports one-to-one, direct matching between Unique Property Reference Number (UPRN) and Unique Multiple Residence Reference Numbers (UMRRNs) only.

    🆕 How are PAF records matched to local authority records?

    For Postcode Address File (PAF), records are received daily and an auto-match process is run on all records (including records already matched). For any records that remain unmatched, a manual review process occurs within one to two days. If records can't be matched through the two aforementioned processes, the PAF records will go to local authorities in a monthly feed.

    For Not Yet Built (NYB) and Multiple Residence (MR), records are supplied by Royal Mail monthly and are subject to an auto-match process, and, where a match cannot be found, are then passed through the manual review process.

    🆕 What percentage of PAF records are matched to a local authority address record?

    In the OS GB Address Collection, 99.4% of Postcode Address File (PAF) records are matched to a local authority record: 99.3% directly and 0.4% indirectly through parent, street, postcode unit or postcode sector relationships.

    In the OS Islands Address Collection, around 95% of PAF records are matched.

    🆕 Does PAF replace the local authority address source?

    No. The Royal Mail Address Feature Type makes Postcode Address File (PAF) data easier to access within the OS NGD Address Theme, but it does not prioritise PAF over local authority addresses. Unique Property Reference Number(UPRN)-led local authority address data remains the route to the wider OS address attribution held across the other OS NGD feature types.

    🆕 How quickly are daily PAF updates processed?

    A daily Postcode Address File (PAF) is received each morning and automatically matched against all records. Remaining unmatched records are reviewed manually within one to two days. Records that still cannot be matched are passed to local authorities through a monthly feed.

    🆕 What drives change events?

    Postcode Address File (PAF) records are inserted, updated or deleted through Change-Only Updates (COUs); they do not move between feature types. Updates may be triggered by improved geometry, a changed matched Unique Property Reference Number (UPRN), a lifecycle change in the matched addressable object, or a Royal Mail attribution change, such as postcode or organisation name.

    Examples of change events include:

    • Updated geometry (where the geometry allocation method is updated and consequently improved the location of the delivery point address record)

    • Updated matched addressable object (where the matched UPRN has moved in lifecycle stage and is now contained within a different Addressable Object Feature Type, that is, the Pre-Build Address, Built Address or Historic Address Feature Types)

    • Updated UPRN match (where an appropriate match has been established for a previously unmatched Unique Delivery Point Reference Number – UDPRN)

    • Updated Royal Mail attribution (PAF attribution change, that is, a change to postcode, organisation name or other postal element)

    🆕 Does OS alter Royal Mail-derived attribution?

    No. OS displays Royal Mail-derived Postcode Address File (PAF) fields as supplied. This includes Welsh address fields, which may be populated, duplicated or NULL depending on what Royal Mail provides.

    🆕 What does a Royal Mail Address feature's location or geometry represent?

    The point location represents the allocated position for the Postcode Address File (PAF) record; it does not identify the exact postal delivery medium, such as a letterbox or communal mail room.

    Where a PAF record is matched to a Unique Property Reference Number (UPRN), it inherits the local authority geometry for that address, so the UPRN and Unique Delivery Point Reference Number (UDPRN) share the same position.

    🆕 How is geometry allocated to Royal Mail Address features, including for unmatched records?

    For most Unique Delivery Point Reference Numbers (UDPRNs), geometry is inherited from the directly matched Unique Property Reference Number (UPRN). If no direct match exists, geometry is estimated using the best available geography, such as postcode unit, sector, district or local authority level. Unmatched records are included and represent around 0.2% of Postcode Address File (PAF) records; they can be identified using the Match Type attribution.

    🆕 Are unmatched PAF, NYB and MR records included in the Royal Mail Address Feature Type?

    Yes. The Royal Mail Address Feature Type includes both matched and unmatched Royal Mail records, allowing 100% of Postcode Address File (PAF), Not Yet Built (NYB) and Multiple Residence (MR) delivery point records to be represented in the data.

    🆕 Will OS create new UPRNs for unmatched PAF records?

    No. Local custodians remain the authoritative source for creating and maintaining Unique Property Reference Numbers (UPRNs) under BS7666 standards. OS will not ask local authorities to create new UPRNs simply because a Postcode Address File (PAF) record is unmatched.

    🆕 Why are unmatched reason fields currently NULL?

    OS is working with GeoPlace to populate the Unmatched Reason and Unmatched Reason Date attribution where no suitable Unique Delivery Point Reference Number-Unique Property Reference Number (UDPRN-UPRN) match has been found. The fields remain NULL while the correct meanings and use of the codes are finalised.

    🆕 How should match or address errors be reported?

    Please use the Errors & Omissions tool in the OS Data Hub to report suspected match issues. If the proposed match is accepted, it will soon be reflected in the data. For errors in Postcode Address File(PAF)-derived postal address content, such as a missing building name, please raise the issue with Royal Mail because OS cannot amend, delete or add PAF source data.

    🆕 How does area-of-interest pricing work for the Royal Mail Address Feature Type data schema version 2.0 onward?

    The existing area-of-interest model continues. Customers can license either on a per-point basis or by the number of points within a hectare.

    🆕 Why is the Royal Mail Address Feature Type in the OS GB Address Collection available as a partner distribution option, but this option is not allowed for the Royal Mail Address Feature Type in the OS Address Islands Collection?

    At launch in October 2026, the new licensing options apply to the Royal Mail Address Feature Type in the OS GB Address Collection only. Partners wanting access to the Royal Mail Address Feature Type in the OS Islands Address Collection must license the full collection.

    🆕 Why can a UDPRN entry date go backwards when moving from NYB to PAF?

    The Entry Date attribute on Royal Mail Address features shows when the Unique Delivery Point Reference Number (UDPRN) was first received by OS in a specific Royal Mail product, such as Not Yet Built (NYB) or Postcode Address File (PAF). When a record moves between Royal Mail products, the entry date may appear to regress. This reflects Royal Mail lifecycle handling and is not a data fault. For lifecycle tracking, please use the local authority addressable feature types in the OS NGD (that is, the Pre-Build Address, Built Address, Non-Addressable Object and Historic Address Feature Types).

    🆕 Why are AddressKey and OrganisationKey missing from the Royal Mail Address Feature Type?

    OS does not receive AddressKey or OrganisationKey in the Postcode Address File (PAF) and Not Yet Built (NYB) files supplied by Royal Mail, so they cannot be included in the OS NGD. Royal Mail has also superseded these keys with the Unique Delivery Point Reference Number (UDPRN), which is the preferred identifier for future-resilient and efficient processing.

    🆕 How are Welsh translation attributes (for example, Welsh Dependent Thoroughfare and Welsh Post Town) in the Royal Mail Address Feature Type received / generated?

    For any Royal Mail-derived fields and attributes in the Royal Mail Address Feature Type, OS does not transform, alter or uplift any of the source information. We simply display exactly what is provided in the Postcode Address File (PAF).

    For Welsh addresses, this means that there may be some instances where there isn’t a Welsh alternative address, and, in which case, the attribution will either be NULL or duplicated. Examples of what Royal Mail does these scenarios can be found on page 48 of the Royal Mail Programmer's Guide.

    🔃 OS NGD Administrative and Statistical Units Theme FAQs

    🔃 Boundaries data FAQs

    Can I easily identify wards linked to a specific unitary authority?

    Yes. This can be done non-spatially by interrogating the new Boundary Parent Reference attributes.

    What's the difference between a boundary and a functional area?

    Features in the OS Boundaries Collection have specified geometries, often detailed in law; OS documents these geometries, but is not responsible for saying where the boundary goes. In contrast, functional areas are algorithmically derived notional geometries – which means OS will place them based on the information we know about each area, such as the address, site and topographic data we hold in the rest of the OS NGD.

    🆕 Why didn't you add the new Regional Authority features to data schema versions 1.0 and 1.1 of the Regional Authority Feature Type?

    Data schema versions 1.0 and 1.1 of the Regional Authority Feature Type have a geometry type of 'Polygon', which requires the Regional Authority features to be made of a single part. Some of the new Regional Authority features included in the OS NGD from data schema version 2.0 onward (for example, English Combined Authority) have polygons made of multiple parts (for example, if the area includes islands), so they need to be in a feature type with a geometry type of 'MultiPolygon'. A geometry type change to a feature type requires a major data schema version uplift, so we have therefore uplifted the Regional Authority Feature Type to data schema version 2.0 (released in October 2026). We have limited data schema versions 1.0 and 1.1 of the feature type to include only the Greater London Authority.

    The Regional Authority Description Value Code List details the types of regional authorities currently captured in the OS NGD from data schema version 2.0 onward of the Regional Authority Feature Type.

    We recommend all existing and new OS NGD customers to use data schema version 2.0 onward of the Regional Authority Feature Type to receive any future regional authorities that may become operative.

    More information on data schema versioning in the OS NGD is available from the of the OS NGD Fundamentals.

    🆕 Why these regional authorities?

    In line with plans for English devolution, we have created new Regional Authority features for existing, operative combined authorities from data schema version 2.0 onward of this feature type. The Regional Authority Description Value Code List details the types of regional authorities currently captured in the OS NGD from data schema version 2.0 onward of the Regional Authority Feature Type. We intend to add more Regional Authority features as and when more authorities become operative in the future, along with regional authorities located outside of England.

    Postcodes data FAQs

    Why isn’t the polygon for my Postcode Unit Area feature the shape I expect?

    Postcode Unit Area features are created with input from a variety of data sources, the most important of which is the coordinates of addresses with that postcode. After the coordinates have been determined, an algorithm fills in the gaps between them until all of the landmass of Great Britain is part of at least one Postcode Unit Area feature. Sometimes, particularly in areas of low address density, this creates very irregular shapes.

    For Postcode Unit Area features, why do the counts on the postcode parts attributes not equal the figure in the Total attribute?

    Sometimes a delivery point has a postcode but we don’t have enough other information about it to place it in a particular part. However, we include these delivery points in the total to ensure all records in Royal Mail's Postcode Address File (PAF) are accounted for. For example, if a postcode has three parts which have five delivery points each plus a delivery point which cannot be placed in any of those parts, the attribution on each feature will be:

    Attribute Name
    Count
    Why are there postcode parts for Postcode Unit Area features which do not have any delivery points in them?

    Postcode Unit Area features are created to cover the whole landmass of Great Britain. In places where the landmass fragments (particularly along the coast), a postcode part is created for each piece of land, and that polygon is attributed to the postcode of the nearest delivery point.

    Why do the postcode parts overlap?

    The Postcode Unit Area Feature Type was designed for multiple features to have exactly the same polygon, called coincident geometries. This replaces the visible squares called vertical streets in the Code-Point with Polygons product.

    The way we achieve this is we derive the theoretical shape of a postcode based on the features which have been assigned to that postcode. If any of the postcode shapes overlap, we split them into parts such that only 100% overlaps occur. This means:

    • A postcode can be made of one or more parts

    • A Feature ID is assigned to each postcode part

    • Metadata is provided for how many parts make up a postcode

    • Each part is assigned a Geometry ID

    • Where parts share identical geometries (the 100% overlaps, called coincident – for example, where multiple postcodes are in the same building), they are assigned the same Geometry ID

    • Metadata is provided for how many parts share a coincident geometry

    • Neighbouring polygons can have the same postcode

    • Not all parts of a postcode must be neighbours

    More information on this is available on the .

    How do I find multiple postcodes in the same building? Why can’t I see vertical streets?

    The easiest way to find a postcode in the same place is to look for Postcode Part Count Coincidental Geometry attribute values of over 0 for your Postcode Unit Area features.

    The Postcode Unit Area Feature Type was designed to include all postcodes which can have a polygon, for those polygons to align to real-world features, and to provide complete surface coverage of Great Britain. Where multiple postcodes are in the same building, they will share a geometry which covers the whole of that building; we call these ‘coincidental geometries’. This is different to the Code-Point with Polygons product, which has visible squares where the vertical streets are to be linked to in a separate table to view the postcodes, which was a pain point for many customers.

    More information on this is available on the More than Maps site.

    Why isn’t this Building feature within a Postcode Unit Area feature?

    Postcode polygons (Postcode Unit Area features) have been designed to align to the Building features visually and are accurate to 1:1 scale; however, they don't use the same vertices as the Building features, so tiny slivers of a building could be in the neighbouring postcode polygon. As a result, analysis using ‘wholly within’ tests will get inaccurate results. Note, for many use cases, Address points are more suitable than Building features.

    Why are some Postcode Unit Point features not in buildings?

    Most Postcode Unit Point features will be at the same coordinate as a suitable address with that postcode. That address does not have to be located in a building, either because the address is in place ahead of a Building feature being created or because it is for a feature other than a building (such as a caravan). Additionally, we give a point for all postcodes in Royal Mail’s Postcode Address File (PAF). When there are no suitable addresses with a postcode, that Postcode Unit Point feature is given an approximate location based on other addresses in the postcode sector. Sometimes that approximate coordinate is outside of a building and could even be in water, especially in coastal areas.

    Why is the Postcode Unit Point feature at a different coordinate than the Code-Point point for the same postcode?

    OS NGD postcodes (Postcode Unit Point features) and Code-Point postcodes are created in different ways. Most of the time, the different methodologies produce the same result. Both results are equally valid as postcode points are notional geographies, meaning unlike our other data, they are not defined in law or surveyed to be in an exact position. In both datasets, the point is intended to be used as an easy-to-process approximation of the postcode's theoretical position.

    More information on this is available on the More than Maps site.

    Retail areas data FAQs

    Why is a Retail Area Minor feature not automatically part of a Retail Area Aggregated feature?

    Retail Area Aggregated features are derived from areas that contain at least one Retail Area Major feature and any neighbouring addresses with a classification that is indicative of retail use. As a result, Retail Area Aggregated features might be a single parade of shops or a large section of a city. Not all Retail Area Minor features are located close enough to a Retail Area Major feature to become part of a Retail Area Aggregated feature.

    For example, in the image below of Aylesbury, the northeasternmost Retail Area Minor feature doesn't appear in a Retail Area Aggregated feature as it's not located close enough to a Retail Area Major feature. The other five Retail Area Minor features over the centre of the town do form part of Retail Area Aggregated features as they are all located close enough to Retail Area Major features to automatically become part of Retail Area Aggregated features.

    Example showing Retail Area Aggregated, Retail Area Major and Retail Area Minor features in the centre of Aylesbury. A background map has been included for context.
    Why is this address not in a retail area?
    • Our retail area features are created based on a combination of count and proximity thresholds. If the retail addresses are not close enough together, they will not meet our capture requirements. We are keen to optimise the thresholds used by the algorithm, so please contact us or your OS Account Manager to report any instances of this problem as an area for us to learn from.

    • Currently, we require an address to have an Address Classification Code Value which starts ‘CR’ (i.e. Retail) to be classified as a retail address. Particularly large warehouse-type stores are classified as ‘Industrial’ (i.e. as 'CI' in the Address Classification Code Value Code List), so will not be included as a retail address in a potential retail area feature. If an address has a different classification code value and you believe it should have a Retail (‘CR’) classification code value, please report this via our Errors & Omissions Tool on the . If a change is made, this will be incorporated into the next release of retail areas data.

    Why is there not a retail area where I expect to see one?

    Our retail areas are based on several factors, including address classification, density and proximity thresholds. If an area doesn't meet these criteria, then a retail area feature won't be produced for it. We know this means that certain areas customers expect to see marked as retail area features are not always present in the data, but we are keen to optimise the thresholds used by the algorithm. If you would like to be part of our user engagement about what makes a retail area, please get in touch.

    Will more feature types be added to the OS Functional Areas Collection in future? Why is the collection not called the OS Retail Areas Collection?

    We plan to release more feature types in future for other kinds of functional areas, including office areas, leisure areas and more. If you would like to be part of our user engagement about which kinds of functional areas would be of most interest and what should be included in each, please get in touch.

    Why do retail area features overlap?

    Overlapping features are expected in functional areas (both overlaps of different feature types and of features in a single feature type). This is because a single building might have characteristics that relate to more than one area. For example, a building on a street corner could have retail addresses related to two streets both containing numerous retail address; therefore, that building on a corner would be included in two Retail Area Major features. As the name suggests, Retail Area Aggregated features are an aggregation of Major Retail Area features and sometimes Retail Area Minor features, so will always overlap other features.

    In Retail Area Major features, why does an address with a Unique Street Reference Number (USRN) not always have the USRN as the dividing feature?

    If the address falls within a Site (for example, a shopping centre), the Site is used as the dividing feature instead of the USRN (in such cases, the Dividing Feature USRN attribute value would be NULL and the Dividing Feature Site ID attribute value would be populated).

    Example image showing a dividing feature for West Quay Shopping Centre in Southampton. A background map has been included for context.
    Why have you provided counts of addresses with classifications other than 'Retail'?

    The proportion of addresses with different types of classifications can help you to understand the characteristics of an area. It enables use cases where you can look at the changes in an area over time or between different areas which started with similar characteristics. For example, if one area received funding for an initiative and another did not, you can use these characteristics as a counterfactual to see the impact the initiative made.

    Why can non-retail buildings be included in retail areas?

    Our functional areas are deliberately generalised polygons to allow for how different people perceive the same area. This is achieved by adding a buffer to the specific retail locations. Sometimes buildings which don't have a classification of 'Retail' are encapsulated by that buffer (for example, a detached residential house between two shops being included).

    Why have you included point coordinates on polygon features for retail areas?

    We have chosen to include weighted centroids for the retail area features to enable a number of use cases where a point is easier to handle. Using a position weighted on the retail addresses makes this a better representation for examples like routing where it increases the accuracy of estimations.

    Example image showing the location of an address weighted centroid generated from the Easting/Northing or Latitude/Longitude attribution for a Retail Area Major in Bristol. Attribution for the Retail Area Major feature is displayed. A background map has been included for context.
    Why is the weighted centroid for my retail area feature outside the polygon for the feature?

    We have chosen to include weighted centroids for the retail area features to enable a number of use cases where a point is easier to handle. Using a position weighted on the retail addresses makes this a better representation for examples like routing where it increases the accuracy of estimations.

    Example image showing the location of an address weighted centroid generated from the Easting/Northing or Latitude/Longitude attribution for a Retail Area Major in Bristol. Attribution for the Retail Area Major feature is displayed. A background map has been included for context.

    However, weighted centroids don't always fall inside the polygon (for example, in donut-shaped or crescent-shaped polygons). Where this happens, the information that the polygon inherits from the weighted centroid point is not always valid for the polygon. For example, in Chippenham, the weighted centroid falls on a river and so is classed as non-urban, despite the polygon being fully urban. This impacts subsequent calculations, such as which Retail Area Aggregated feature is defined as the town centre.

    The root cause of a weighted centroid not being in a polygon affects all three retail area feature types; currently, under 2.1% of all features in the three retail area feature types are impacted by this issue.

    Are temporary retail locations included in retail area features?

    As a rule, no, as we don't have information about temporary retail locations. However, sometimes temporary retail locations happen to be included in retail area features because they are located in an area which also has permanent retail locations. For example, a market held on a high street would automatically be in a Retail Area Major feature by virtue of the neighbouring shops. However, an ice cream van in a cliff top car park is unlikely to be in a retail area feature.

    How do I use the Related Entity Related Component table with OS NGD Address Theme data?

    Cross-reference identifiers in the Related Entity Related Component table for retail area features are stored as a string. This means you need to change the character type and potentially filter by feature type when trying to join the Unique Property Reference Number (UPRN) to other datasets (for example, the Built Address Feature Type) where they are stored as integers.

    Example image showing the relationship between a Retail Area Minor feature and the Related Entities table. A background map has been included for context.
    For Retail Area Major features, why can the Addresscount Residential count be low when the Residential Density count is high?

    The Residential Density attribute measures the overall density of residential addresses within a wider built-up area, and is used to set the thresholds for classifying a Retail Area Major feature; whereas the Addresscount Residential attribute value is specifically inside that feature. It is therefore expected that there will be some low / zero Residential Density attribute counts in some Retail Area Major features, especially those which represent sites such as shopping centres or railway stations.

    OS NGD Buildings Theme FAQs

    How are Building features derived?

    Building features are derived by using the Building Part Feature Type and merging connected Building Parts that are within the same Land Use Site and have a contiguous border greater than 0.5m.

    If a Building Part Feature Type does not belong to a Site, then it will retain the same geometry in the Building Feature Type.

    If there are multiple Sites, the smaller Site has hierarchy over the larger site (i.e. Building Parts only merge within the smaller Site, and if they share a border with a Building Part outside of the smallest Site, then the Building Parts features will not merge).

    Is height data available on building features ?

    Yes. Height data is available on Building features and Building Part features.

    How have Building address counts been derived ?

    The various address count attributes that have been derived from the Built Address Feature Type in the OS GB Address Collection where the Build Status attribute value is classified as ‘Built In Use’. Residential, commercial and other address counts have been derived where the primary code in the address classification is equal to ‘R’, ‘C’, or anything not ‘R’ or ‘C’ respectively.

    What is a ‘Main Building’ and how has the data been derived ?

    The main building aims to easily identify the building a casual visitor to a site would identify as the most useful building to represent the entire site. For example, the house on a residential site would be identified as the main building rather than the shed in the garden, or the ticket office of a train station rather than the waiting room on the other side of the platform.

    How is ‘Building Use’ derived ?

    Building use is derived from an in-house algorithm that uses either OS NGD Address data or OS Land Use Sites data to determine what the building is being used for. In most cases, the attribute value has been derived from address data classification.

    What’s the difference between the ‘Building Use’ and ‘OS Land Use Tier A’ value ?

    There are two main differences; a difference in what each attribute is trying to convey and a difference in their derivation.

    • Building Use attempts to convey what the Building is specifically being used for, whilst OS Land Use Tier A attempts to convey what activity the site that the Building is situated within is being used for. For example, Nurses' accommodation on a hospital site will have the Building Use value of ‘Residential Accommodation’ but the OS Land Use Tier A value of ‘Medical Or Health Care’.

    • Building Use is mainly derived from address data, whilst OS Land Use Tier A data is derived from Ordnance Survey sites data.

    What is the difference in the derivation process between Roof Shape and Roof Material?

    The derivation of Roof Shape involves using automated methods and height models to delineate roof faces, while Roof Material is derived from imagery processed by a supervised ML model and an Automated Feature Extraction algorithm.

    What is the difference between Building Access Locations and Land Use Site Access Locations?

    Building Access Locations identify specific entry and exit points for individual buildings, while Land Use Site Access Locations represent access points for broader areas (Sites), identified for a specific purpose, connecting them to the Road Network.

    OS NGD Geographical Names Theme FAQs

    Why are settlement extents depicted differently by the Named Area Feature Type within the OS Named Features Collection and feature types in the OS Boundaries Collection?

    The OS Boundaries Collection provides a definitive dataset of administrative and electoral boundaries; whereas, the depiction of settlement boundaries in the Named Area Feature Type of the OS Named Features Collection is an OS geographic depiction of the extent of settlements and should not be mistaken for administrative or electoral uses.

    Why is the OS NGD Geographical Names Theme not OpenData like OS Open Names?

    More features and attributes are provided in the OS NGD Geographical Names Theme than in OS Open Names. The theme also includes a new feature type (Named Area) which shows geometry never before published by OS. The rich attribution provided by the theme's data lends itself to helping users perform gazetteer searches as well as high-level visualisation and spatial analysis of named features and places.

    Crowd Sourced Name Point features' FAQs

    Why are there no Crowd Sourced Name Point features in my area?

    Coverage of Crowd Source Name Point features is dependent on submissions from expert third parties via the Vernacular Names Tool.

    The Vernacular Names Tool is a resource developed by Ordnance Survey to assist Emergency Services by incorporating user-submitted colloquial names for geographic features across Great Britain.

    Why are the names of the Crowd Sourced Name Point features not in a standardised format?

    The names are published as they are submitted by expert third parties. OS doesn't make changes to the names and doesn't enforce standardisation at this time because casing and punctuation can be important elements in some names. Spelling mistakes are also expected as these can be common variants tried in searches.

    Can I submit a new name (i.e. a new Crowd Sourced Name Point feature)?

    Crowd sourced names can be submitted via the Vernacular Names Tool on the OS Data Hub. You'll need to be member of an approved organisation to submit a name.

    The Vernacular Names Tool is a resource developed by Ordnance Survey to assist Emergency Services by incorporating user-submitted colloquial names for geographic features across Great Britain.

    Can I suggest a change to a Crowd Sourced Name Point feature's name, coordinate or classification, or suggest a match to it?

    Please report these via the Errors & Omissions Tool on the OS Data Hub.

    Why has my name not been published?

    Names usually appear in the Crowd Sourced Name Point features dataset within two months of being submitted, but they can be viewed in the Vernacular Names Tool on the OS Data Hub before then.

    The Vernacular Names Tool is a resource developed by Ordnance Survey to assist Emergency Services by incorporating user-submitted colloquial names for geographic features across Great Britain.

    Names will not be published if they have been flagged as containing personally identifiable information or potentially offensive language. They will also not be published if the name is identical to an existing OS feature or is of an unsuitable classification (for example, a defibrillator as their locations are not currently captured).

    Why is the same name in the Crowd Sourced Names Point features dataset multiple times?

    OS is not looking for duplicates within Crowd Sourced Names Point features, so if the same name is submitted multiple times, all entries will be published.

    OS NGD Land and Land Use Themes' FAQs

    How does OS NGD Land Theme data differ from OS NGD Land Use Theme data?

    OS NGD Land Theme data contains land cover attribution that describes the physical and biological surface of the land. OS NGD Land Use Theme data contains land use attribution that describes the human or economic activity taking place on areas of land (i.e. how areas of land are being used / their purpose).

    How does the OS NGD Land Theme differ from the OS MasterMap Topography Layer, Sites Layer, and Greenspace Layer products?

    The OS NGD Land Theme contains some land information data which can also be seen in the OS MasterMap Topography Layer, Sites Layer, and Greenspace Layer products. The data in the theme is similar as that provided by the aforementioned OS products, but it has been structured to be more analytical and consistent across the six OS NGD features collections, allowing you to easily select the specific features you require and delivering greater value to users.

    (The six OS NGD features collections, which also include data from the three aforementioned OS products, are the OS Building Features, OS Land Features, OS Land Use Features, OS Structure Features, OS Transport Features, and OS Water Features Collections.)

    What are the NGD land cover enhancements?

    Please refer to the OS NGD Land cover enhancements section for further information.

    Why are Wind Farm site polygons the shape they are?

    Wind farms are a complex site to model as they are often constructed across large areas of open land with much of the ground around individual turbines being used for other activities, such as animal grazing or a solar farm. Some Wind Farm sites, in contrast, may be wholly contained within another existing site, such as a factory. Additionally, access roads may extend a significant distance from the turbines, or each turbine may have individual access. Consequently, what is recognised as a Wind Farm extent is heavily dependent on the surrounding geography, the nature of the wind farm, and the user’s perspective.

    OS has chosen not to include the entire extent of the land parcels below turbines as the definition of a Wind Farm extent because this can sometimes translate to many thousands of hectares in mountain and moorland areas and therefore misrepresent the real-world site. Other sources of land extent data such as land registration and planning area data were considered, but did not provide consistent high-quality coverage across Great Britain.

    Instead, a nominal 300m buffer was applied to the individual wind turbines associated with wind farm schemes referenced in the Renewable Energy Planning Database to indicate the general area of land used as a Wind Farm. Land Use Sites extents are not meant to represent specific concepts like land ownership, which is made clearer by this nominal geometry design choice.

    OS NGD Structures Theme FAQs

    How does OS Structure Features Collection data differ from structure features data available in the OS MasterMap Topography Layer product?

    In comparison to OS MasterMap Topography Layer data, OS Structure Features Collection data has been enriched with additional attribution, including the following:

    • Geometry change metadata

    • A Description attribute to provide a one-word or simple phrase description of a feature

    • Detailed land use classification

    • Detailed land cover classification

    • Capture specification to give details about the geography of the area a feature resides in (that is, urban, rural, or moorland)

    • Embedded height attribution for chimneys, roofed tanks, and glasshouses, enabling users to create simple height models of these structures. Field Boundary features also have a height value.

    In addition, other feature types are available in the OS Structure Features Collection: the Compound Structure Feature Type and the Field Boundary Feature Type.

    What is a compound structure?

    The Compound Structure Feature Type is a polygon feature which encompasses one or more components and represents a manmade construction that has been built for a specific purpose. Examples include a bridge, a dam, and an aqueduct. A compound structure essentially combines multiple polygons into a single polygon, making it easier for you to analyse and query data when you want to analyse a structure as a single part rather than its constituent parts.

    Why don't all structures have names?

    Name attribution, where known, is provided for structure features to help you identify what a structure is called. This attribute is optional as not all structures have a name and, in some instances, OS may not yet have captured a structure's name in the data.

    What structures will have height attributes allocated?

    Embedded height attribution is available for chimneys, roofed tanks, and glasshouses, enabling users to create simple height models of these structures. Field Boundary features also have a height value.

    Where can I learn more about Field Boundary features?

    Please refer to the Field Boundary section for further information.

    Why are some London Underground stations missing from Tube or Metro Tunnel features in Compound Structures?

    OS's capture focus is on tunnels that reach the surface, meaning that the Metropolitan and District Lines of the London Underground are captured, whereas other London Underground lines are generally not captured.

    Why are there temporal differences in data currency for bridge interactions?

    Bridges in the OS Structure Features Collection are updated daily, whereas networks in the OS Transport Network Collection and the OS Water Network Collection are updated monthly and quarterly, respectively. This can lead to temporal differences in data currency for bridge interactions.

    Which third-party bridge information is available?

    OS only adds third-party bridge information as attribution to bridge features if it has been provided by an authoritative third party. Initially, this information has been provided by organisations for canal bridges, but OS looks to add information for other types of bridge, like rail, in the future.

    OS NGD Transport Theme FAQs

    Can I use OS NGD Transport Theme data for routing?

    Yes. Data in the OS Routing and Asset Management Information (RAMI) Collection can be fed into routing software. The routing information provides details about potential routing hazards (for example, dangerous bends and low bridges) and vehicle restrictions (for example, one-way streets and road widths).

    How has the Rail Network been generalised?

    The generalisation of Rail Networks should ensure full connectivity between relevant Rail Nodes. Rail track generalisation can be typically three or four Rail Links represented as one link, for example, multiple siding tracks. However, this may not always be the case, for example, tracks that pass either side of a station platform are normally included to ensure connectivity at a station.

    How will tracks be distinguished from paths?

    Paths and tracks will both be represented in the OS Transport Network Collection. The Description attribute provides a one-word or simple phrase description of a feature, and you'll be able to use this attribute to easily distinguish between paths and tracks.

    What routing and asset management information is included in the OS RAMI Collection?

    The OS Routing and Asset Management Information (RAMI) Collection provides in-depth routing and asset management information for roads across Great Britain. Rights and restrictions define properties that restrict, regulate or prohibit the use of the network by traffic which may affect the allowable route for users. Advisory information provides additional information that may either affect a driver’s preferred choice of route or highlight potential hazards, such as the presence of a toll or a level crossing. Asset management information provides additional information describing the network to support its long-term operation and maintenance.

    Bus lane data FAQs

    What is the coverage of bus lanes?

    There is full data coverage across Great Britain for bus lanes data.

    What is the update frequency of bus lane data?

    The Bus Lane Feature Type is updated into the OS NGD monthly. Bus lane attribution on the Road Link Feature Type is also updated monthly.

    How have bus lanes been captured?

    Bus lanes are sourced from OS aerial imagery, for built-up areas only. Where features are not visible from aerial imagery (for example, where they're obscured by tree cover), these will not be included. You can record any omissions on the OS Data Hub Error Reporting Tool for OS to investigate. Please see the known limitations page on Using OS NGD Data for more information.

    Are Guided Busways, Bus Gates and High Occupancy Vehicle Lanes included in the Bus Lane dataset?

    Bus lanes are defined as a section of road that is segregated by a physical feature or painted section of road that indicates primary usage for buses. Guided Busways and Bus Gates have been captured in the dataset as they meet these criteria. However High Occupancy Vehicle (HOV) Lanes have not been captured because although buses can sometimes use these lanes, this is not their primary use. OS views HOV Lanes as being distinct from Bus Lanes and Bus Gates which have the primary use for buses, sometimes with exemptions for cyclists, motorcyclists and taxis.

    Cycle lane data FAQs

    What is the coverage of cycle lanes?

    There is full data coverage across Great Britain for cycle lanes data.

    What is the update frequency of cycle lane data?

    The Cycle Lane Feature Type is updated into the OS NGD monthly. Cycle lane attribution on the Road Link and Path Link Feature Types is also updated monthly.

    How have cycle lanes been captured?

    Cycle lanes are sourced from OS aerial imagery, where they exist alongside publicly accessible Road Links and Path Links. Where features are not visible from aerial imagery (for example, where there is no visible evidence of a cycle lane or where it's obscured by tree cover), these will not be included unless they have been identified through other intelligence sources. In particular, the completeness of Unsegregated Shared Use Cycle Lanes will be lower as these features are typically indicated by blue signage at street level and don’t have a clear designation that can be seen from aerial imagery. Please see the Known limitations page on Using OS NGD Data for more information. You can record any omissions on the OS Data Hub Error Reporting Tool for OS to investigate.

    Are cycle routes included in the Cycle Lane Feature Type?

    The Cycle Lane Feature Type represents designated cycling infrastructure, not cycle routes. Features are only captured where a section of road or path is designated for cyclists, either segregated by a physical feature, identified by painted or other signage, or identified by a different colour of tarmac or surface type. Please note that routes that are part of the National Cycle Network are not captured as Cycle Lane features unless designated infrastructure is present that meets these criteria.

    Pavement data FAQs

    Why are the Pavement Links depicted in the centre of the road?

    The pavement data in the OS NGD uses the Road Link geometry in order to give the features a geographic location; therefore, pavements will be depicted using the road centre line.

    Why within the Pavement Link Feature Type do I only see a centre line but the road has a pavement on both sides?

    When there is a pavement on both sides of the road, we create two features both with the same geometry; therefore, if viewed in a GIS, these will appear on top of each other, but each individual feature will have specific attribution relative to its own side of the road.

    Why are there gaps in the depictions of pavements within the Pavement Link Feature Type?

    Often, the answer is there is no pavement adjacent to the Road Network. Some gaps appear, typically at junctions, where the end of Road Links have no adjacent pavement.

    Why do pavements ‘stop’ at bridge intersections within the Pavement Link Feature Type?

    Currently OS does not capture large-scale depictions of features such as pavements when they are obscured by structures from above.

    How do I interpret which side of the road is left and which is right?

    The left and right side of the road is determined by the direction of digitisation of the Road Link. In Direction of digitisation is from start node to end node, and Against Direction is from end node to start node.

    Why do I have two Pavement Links for the same section of road?

    When there is a pavement on both sides of the road, we create two features both with the same geometry; therefore, if viewed in a GIS, these will appear on top of each other, but each individual feature will have specific attribution relative to its own side of the road.

    Speed data FAQs

    What is the source of indicative speed limit and average speed data?

    Indicative speed limit data is sourced from road signage and surveying. Average speed data is calculated based on historic speed information, which is based upon in-vehicle telematics devices; in this context, 'historic' means that the average speed data was collected over a six-month period for the selected road link.

    What is the update frequency for average speed data and indicative speed data?

    Speed data is published monthly into the OS NGD. Indicative Speed data is updated by our third-party supplier four times a year, and Average Speed data is updated twice a year. In-between these updates, OS 'infills' speeds with inferred values to account for any changes in the network monthly.

    Why is average speed provided in kilometres per hour (kph) rather than miles per hour (mph)?

    Average speed is provided in kph to support travel time analysis software in the market which predominantly uses kph as the unit of speed.

    Street light data FAQs

    How has Street Light data been sourced?

    Street Lights have been captured from OS aerial imagery.

    What is the coverage and completeness of Street Light data?

    Street Light data is GB coverage. Features have been captured where they exist alongside publicly accessible Road Links and Path Links. Street Lights will not be included where they exist along restricted access roads. Where features are not visible from aerial imagery (for example, where obscured by tree cover or not visible due to urban shading), these will not be included.

    Does attribute data for Street Lights include timings for when they are on or off?

    No, the Street Light dataset does not contain information on the times when they are on / off.

    How has the Street Light coverage attribution been created?

    An algorithm is used to give an indication of how well-lit a link is; this algorithm is based on an inferred light radius and does not account for information such as the height of a lamp post, the type of bulb, or the presence of any light-blocking obstructions or buildings.

    What is the update frequency for Street Lights?

    Street Light data is updated into the OS NGD monthly. This includes both the Street Light Feature Type, and Road Link and Path Link attribution.

    Are there any known limitations for Street Light data?

    Yes. There are two known limitations:

    • Street Light Completeness: Street Lights have been captured from aerial imagery and therefore there are some limitations to completeness. Where features are not visible from aerial imagery (for example, where obscured by tree cover or not visible due to urban shading), these will not be included.

    • Overlighting and Underlighting: Street Light coverage attribution on Road Links and Path Links is indicative only, and there may be some instances of overlighting and underlighting. An algorithm is used to give an indication of how well-lit a link is; this algorithm is based on an inferred light radius and does not account for information such as the height of a lamp post, the type of bulb, or the presence of any light-blocking obstructions or buildings.

    🔃 OS NGD Water Theme FAQs

    Why are more water courses depicted in the Water Link Feature Type than in the Water Link Sets Feature Type?

    Water link sets are only created where there are a number of water links that share the same name. Within the Water Link Feature Type, there are numerous water links which are unnamed; these unnamed water links therefore will not appear in the Water Link Set Feature Type as they cannot be joined accurately.

    How is the In Country attribute determined for Waterbody Catchment features that straddle the border between two countries?

    Country attribution for catchments that straddle the Wales-England or Scotland-England border is as provided in the third-party data from the authoritative bodies and is aligned with the Geometry Source attribute (i.e. the source organisation that provided the data: Environment Agency for England, Natural Resources Wales for Wales, and Scottish Environment Protection Agency for Scotland).

    Why are coastal catchments missing from Waterbody Catchment features?

    Coastal catchments for this feature type are not supplied in the third-party data from the authoritative bodies.

    Why do River Basin District Catchment features include geometries for islands located far away from the mainland, including outside the extent of the British National Grid?

    The data for this feature type is as provided by the third-party data from the authoritative bodies.

    What are the recommended scenarios for using Tidal Boundary features versus continuous tidelines, and how should I choose between them?

    Tidal Boundary features should be used when segmented representations of mean high water and mean low water tidelines with richer metadata are required for detailed analysis or site-specific mapping purposes.

    Continuous tidelines (i.e. Tidal Boundary Continuous High and Tidal Boundary Continuous Low features) are recommended for applications that benefit from seamless, aggregated water boundaries with better intuitive visual experience, such as macro analysis or when updating boundary features to align with coastlines.

    How are the watercourse widths calculated?

    In Water Link Feature Type data schema version 2.0 onward, there are three possible methods for determining width values:

    • Calculated From Polygon – For Water Links which represent a body of water captured as a topographic area feature, calculations of average, minimum and maximum widths are based on the topographic area feature geometry. For some short links at junctions, the average width will be Modelled From Network instead. A small number of Water Links may fall outside of the capability of the Calculated From Polygon algorithm; in these cases, a Default Value for Geographic Region algorithm will be applied to determine width values instead.

    • Modelled From Network – For Water Links which represent a water feature captured as a topographic line feature, average width is a modelled width based on a known calculated downstream width and the number of upstream sources in the network. Where a calculated downstream width isn’t available, then a Default Value For Geographic Region algorithm will be applied instead. A small number of short Water Links at junctions which represent a body of water captured as a topographic area feature will also be Modelled from Network. A small number of Water Links may fall outside of the capability of the Modelled From Network algorithm; in these cases, a Default Value for Geographic Region algorithm will be applied to determine width values instead.

    • Default Value For Geographic Region – For Water Links captured as a topographic line feature (where no width has been processed), average width is a default width based on the capture specification. For Water Links which represent a body of water captured as a topographic area feature, there may be small number of features that fall outside the capability of the Calculated From Polygon algorithm and Modelled From Network algorithm to create; in these instances, a Default Value For Geographic Region algorithm will be applied to determine width values instead.

    The indicates which method has been used to populate the , and attributes.

    🆕 Are there any known limitations for Water Link Feature Type data?

    Yes. A small number of Water Link features (data schema version 2.0) have unexpectedly high Width Maximum attribute values due to known limitations in the width calculation algorithm. The issue most commonly occurs where narrower river channels connect to larger water bodies, causing the derived maximum width to reflect a wider connected section rather than the local channel itself.

    FAQs page of our OS APIs Documentation site

    Change Log

    This page lists changes made to OS NGD documentation. Changes will be made for a variety of reasons, including reflecting any alterations made to the OS NGD data itself as we enhance and improve the offering, plus simple improvements to the documentation to aid understanding.

    You may also be interested in the following two pages:

    • – This page gives you a high-level summary of new data and access enhancements recently launched for the OS NGD. It also gives a link to the , which outlines our focus areas for enhancements and new releases for the OS NGD and our Download products (Premium and OpenData products) over the next two years.

    • – A high-level summary of data improvements implemented throughout the year for the OS NGD.

    The table below gives a summary of the changes made to OS NGD documentation and the date upon which those changes took effect:

    Version
    Date
    Notes

    For example, the October 2026 OS NGD data enhancements release contained five new data schema versions for existing feature types: Regional Authority v2.0, Royal Mail Address v1.1 and v2.0 (OS GB Address Collection), and Royal Mail Address v1.1 and v2.0 (OS Islands Address Collection). The new data schema versions for the existing feature types will not be part of Annual Full Supply orders until 01 January 2027.

    OS Land Use Features

    6 months

    OS NI Postcodes

    3 months

    OS RAMI

    6 months

    OS Structure Features

    6 months

    OS Transport Features

    6 months

    OS Transport Network

    6 months

    OS Water Features

    6 months

    OS Water Network

    6 months

    OS GB Address

    3 months

    OS Boundaries

    6 months

    OS Building Features

    6 months

    OS Functional Areas

    N/A

    OS GB Postcodes

    3 months

    OS Islands Address

    N/A

    OS Named Features

    6 months

    OS Land Features

    Monthly

    60 days of no downloads

    Annual

    395 days of no downloads

    Daily

    7 days of no downloads

    +7 days

    14 days

    Monthly

    60 days of no downloads

    +60 days

    120 days

    Annual

    395 days of no downloads

    +30 days

    425 days

    Daily

    7 days of no downloads

    +7 days

    14 days

    +14 days

    Monthly

    60 days of no downloads

    +60 days

    120 days

    +90 days

    Annual

    395 days of no downloads

    +30 days

    425 days

    +120 days

    postcodepartcount_total

    3

    postcodepartdeliverypointcount_total

    5

    postcodedeliverypointcount_total

    16

    postcodedeliverypointcount_matched

    15

    postcodedeliverypointcount_unmatched

    1

    data enhancements
    Road Nodes
    Status
    Status
    Data schema versioning page
    More than Maps site
    OS Data Hub
    Width Derivation Method attribute
    Width Average
    Width Minimum
    Width Maximum
    Screenshot of the dropdown options available for copying content from a page in GitBook.
    Example showing Retail Area Aggregated, Retail Area Major and Retail Area Minor features in the centre of Aylesbury. A background map has been included for context.
    Example image showing a dividing feature for West Quay Shopping Centre in Southampton. A background map has been included for context.
    Example image showing the location of an address weighted centroid generated from the Easting/Northing or Latitude/Longitude attribution for a Retail Area Major in Bristol. Attribution for the Retail Area Major feature is displayed. A background map has been included for context.
    Example showing the location of an address weighted centroid generated from the Easting/Northing or Latitude/Longitude attribution for a Retail Area Major in Bristol. Attribution for the Retail Area Major feature is displayed in a pop up box. A background map has been included for context.
    Example image showing the relationship between a Retail Area Minor feature and the Related Entities table. A background map has been included for context.
    Example map showing the nominal 300m buffer around individual Wind Turbines. This particular Wind Farm site (Wear Point Wind Farm) has four turbines.

    6 months

    9.2

    04/09/2026

    New OS recommended recipe guide added to the site: .

    9.1

    01/09/2026

    New pages added ahead of the October 2026 OS NGD data enhancements release:

    • Three new address related component pages added: , and .

    Existing pages amended ahead of the October 2026 OS NGD data enhancements release:

    • Major data schema version increment from 1.0 to 2.0 for two existing feature types: (OS GB Address Collection) and (OS Islands Address Collection). This is due to new attributes and three new related components being added to these feature types, plus some filters being altered on existing attributes – please see the data schema version table on the feature type pages for full details of changes. (These feature types also had a minor data schema version increment from 1.0 to 1.1 to make the Description attribute filterable in OS Select+Build.)

    9.0

    12/08/2026

    The 'OS NGD Future Data Enhancements' page was deleted. Information about future data enhancements is now covered in a note at the top of the ; that note explains that the is now available to view on Aha! The roadmap outlines our focus areas for enhancements and new releases for the OS NGD and our Download products (Premium and OpenData products) over the next two years.

    8.9

    07/08/2026

    New added to the site; this explainer goes through transport networks in the OS NGD and how the data and feature types in the collections fit together. It covers the following topics:

    • Building routable transport networks

    • Road network

    • Routing information

    • Streets and asset management information

    8.8

    03/07/2026

    New added to the site; the guide contains specific advice on how to make the most of OS NGD Land Use data and includes the following topics:

    • How OS represents human activity or the economic function of an area or piece of land

    • How OS Land Use Tier A and Tier B classifications are assigned and maintained

    • How Sites relate spatially to surrounding features

    • How address records are matched and summarised

    8.7

    26/06/2026

    New section on the 'Use of geographic coordinate reference systems in the OS NGD' added to the .

    8.6

    04/06/2026

    Two new OS recommended recipe guides added to the site:

    8.5

    02/06/2026

    The feature counts sections for the OS Routing And Asset Management Information (RAMI) and OS Transport Network Collections were removed from the following pages:

    • (in the OS NGD Fundamentals)

    • (in the Data Structure section)

    • (in the Data Structure section)

    • (in the Data Structure section)

    8.4

    13/05/2026

    updated with new FAQs added about unused order notifications.

    8.3

    11/05/2026

    Minor data schema version increments from 1.0 to 1.1, 2.0 to 2.1 and 3.2 to 3.3 to the in the OS Land Features Collection to account for the updates made to the (now on v2.0) to indicate two deprecated values no longer in the data (Heath and Boulders Or Rock And Heath Or Rough Grassland Or Marsh).

    8.2

    06/05/2026

    Coverage map added to the to show the density of green spaces across Great Britain provided by the recipe.

    8.1

    01/05/2026

    Minor data schema version increment from 1.0 to 1.1 to the in the OS Boundaries Collection to make the Boundary Parent Reference ID, Boundary Parent Reference Feature Type, Boundary Parent Reference Classification and Boundary Parent Reference Name 1 Text attributes nullable, in line with boundary changes in Wales.

    8.0

    29/04/2026

    2025 announcements moved into their own tabbed area of the 'Recent announcements' sub-section on the . 2025 What's New? items moved into their own '2025 OS NGD enhancements' sub-section of the .

    7.9

    27/04/2026

    Minor data schema version increment from 1.0 to 1.1 to the in the OS Building Features Collection to reflect the update to the Access Obstruction attribute’s max length from 20 to 30. Clarified documentation to specify the handling of multiple obstruction values by adding a note under the . Added two sentences to the end of the description of the to specify the handling of multiple obstruction values.

    7.8

    24/04/2026

    New tutorial video added to three existing pages in the Downloading with OS Select+Build section of the site:

    The video covers how to create a recipe using OS Select+Build, add filters to a recipe, and create a data package to receive your OS NGD data.

    7.7

    22/04/2026

    Documentation supporting the OS NGD APIs transferred to the OS APIs documentation site to sit alongside documentation for our other OS APIs. Both OS NGD APIs can now be found under Accessing OS APIs:

    FAQs covering the OS NGD APIs have been transferred to the newly created API FAQs page:

    7.6

    21/04/2026

    Minor data schema version increments from 1.0 to 1.1 to the Postcode Unit Point Feature Types in the and Collections to reflect a schema update to the coordinate reference system and storage coordinate reference system URLs.

    7.5

    17/04/2026

    New pages added to the site:

    Navigation on two existing pages updated to mention the new OS recommended recipe guides:

    7.4

    16/04/2026

    The following value was removed from the as it's not part of the product specification and was erroneously included in the code list:

    • Outside Land Boundary: A term used to identify a feature that occurs beyond the captured land extent.

    7.3

    26/03/2026

    Existing pages amended with information about the March 2026 OS NGD data enhancements release:

    • Updates made to the following pages: , , OS NGD Fundamentals – , OS NGD Fundamentals – , OS NGD Fundamentals – , OS NGD Fundamentals – , OS NGD Fundamentals – , Future OS NGD Data Enhancements (page since superseded by a 'OS NGD planned enhancements outlined in our roadmap' note on the page in August 2026), , , , , and .

    • Minor updates made to the and Collections pages.

    7.2

    24/03/2026

    New section added to the explaining the Order Summary File supplied with OS Select+Build downloads and how to use it to validate your supplies.

    7.1

    12/03/2026

    Minor data schema version increments from 1.1 to 1.2, 2.0 to 2.1, 3.0 to 3.1, and 4.0 to 4.1 for the to account for an update to the definitions for the Building Use Address Count Total, Building Use Address Count Residential, Building Use Address Count Commercial and Building Use Address Count Other attributes to change 'built in use' to 'built complete' to align with the updated label in v2.0 of the .

    7.0

    03/03/2026

    Minor data schema version increment from 3.1 to 3.2 for the to account for the update made to the OS Land Cover Tier A attribute to make it filterable in OS Select+Build.

    6.9

    19/02/2026

    New pages added ahead of the March 2026 OS NGD data enhancements release:

    • 3 new collection pages added to the OS NGD Administrative and Statistical Units Theme: , , and

    • 6 new feature type pages added: , , , , and

    • 12 new code list pages added: , , , , , , , , ,

    6.8

    31/10/2025

    New page added for the October 2025 OS NGD data enhancement release:

    • One new code list added:

    Existing pages amended with information about the October 2025 OS NGD data enhancement:

    • Major data schema version released for one existing feature type:

    6.7

    28/10/2025

    Minor data schema version increment from 1.0 to 1.1 for the to add Tidal Outlet to the Water Node Description Value Code List and increase the Description attribute's max length from 8 to 12. Version 2.0 released for the to account for the addition of the new Tidal Outlet label.

    6.6

    15/10/2025

    Feature counts

    • October 2025 feature counts for the OS Routing and Asset Management Information (RAMI) and OS Transport Network Collections were added to the of the OS NGD Fundamentals. Going forward, feature counts for the OS RAMI and OS Transport Network Collections will be updated monthly on this page. Feature counts will not be provided for any other OS NGD collections.

    Improvements made to 10 code lists

    • Missing definitions (previously recorded as "No definition available") for values added to 10 code lists: , , , , , , , , and

    6.5

    02/10/2025

    Code list name corrections

    • The following 14 code list names have been corrected on this documentation site to remove 'os' so that they match the correct code list names already used in the schema:

      • (formerly Building Part OS Land Cover Tier A Value), (formerly Building Part OS Land Cover Tier B Value), (formerly Land OS Land Cover Tier A Value), (formerly Land OS Land Cover Tier B Value), (formerly Rail OS Land Cover Tier A Value), (formerly Rail OS Land Cover Tier B Value), (formerly Road Track Or Path OS Land Cover Tier A Value), (formerly Road Track Or Path OS Land Cover Tier B Value), (formerly Structure OS Land Cover Tier A Value), (formerly Structure OS Land Cover Tier B Value), (formerly Water OS Land Cover Tier A Value), (formerly Water OS Land Cover Tier B Value), (formerly OS Land Use Tier A Value) and (formerly OS Land Use Tier B Value)

    6.4

    30/09/2025

    Warning note added to the page about ensuring COU supplies are processed in the correct productVersion date order.

    6.3

    30/09/2025

    New pages added for the September 2025 OS NGD data enhancements release:

    • Pages added for the two new and Feature Types (data schema version 1.0 for both).

    • 12 new code lists added: , , , , , , , , , , , and

    Existing pages amended with information about the September 2025 OS NGD data enhancements:

    6.2

    29/09/2025

    Existing pages amended with information about the September 2025 OS NGD data enhancements:

    • Three minor data schema versions released for existing feature types: (v3.2) and (v1.3 and v2.4)

    • One existing code list updated:

    • Updates made to the following six OS NGD collection pages: , , , , and .

    6.1

    25/09/2025

    New pages added for the September 2025 OS NGD data enhancements release:

    • Pages added for the new , , and Feature Types (data schema version 1.0 for all).

    • Five new code lists added: , , , and

    • New and pages added to the to reflect the addition of the new Bus Lane and Cycle Lane Feature Types to the OS Transport Network Collection and the addition of new Bus Lane and Cycle Lane attribution in the Path Link Feature Type (v3.0 onward) and Road Link Feature Type (v5.0 onward).

    6.0

    05/09/2025

    User experience improvements made to enhance navigation through the and sections:

    • Updated OS NGD definition on the homepage and the page.

    • Added navigation links to relevant additional information: , , , , and .

    5.9

    29/08/2025

    page restructured to improve usability and customer experience:

    • Three new sub-pages created: , , and .

    • Additional navigation links added to and to highlight key workflows.

    5.8

    28/07/2025

    Minor data schema version increment (v1.1) added to 6 feature types in the OS Boundaries Collection, 1 feature type in the OS Land Use Features Collection and 9 feature types in the OS Transport Networks Collection to remove the query and download filters from the Description attribute for the feature types as this attribute supports only a single value:

    • OS Boundaries Collection: , , , , , and

    • OS Land Use Features Collection:

    • OS Transport Networks Collection: , ,

    5.7

    17/07/2025

    Minor data schema version increments (v2.2 and v1.1) added to the to account for:

    • Updates made to max length from 15 to 20 and max length from 25 to 20.

    • A new value (Under Construction) being added to the and .

    5.6

    26/06/2025

    • Two new questions added to the in the OS Select+Build section for 'How do I edit a recipe?' and 'How do I delete a recipe?'

    • page updated with an entry for June 2025 on Editing recipes in OS Select+Build.

    • updated with an entry for June 2025 on Editing recipes in OS Select+Build.

    • Updates made to the :

    5.5

    13/06/2025

    Data schema versioning and temporal filtering sub-sections added to the four addressing related component pages: , , , and .

    5.4

    06/06/2025

    Data schema versioning and temporal filtering sub-sections improved on feature type pages for those feature types with more than one data schema version: , , and for the OS GB Address Collection; , , and for the OS Islands Address Collection; ; ; ; ; ; ; ; ; ; ; , and .

    5.3

    07/05/2025–23/05/2025

    Restructuring work carried out on the navigation menu on the left-hand-side of the site to improve navigation and the customer experience:

    • New section created for OS NGD NEWS, with four pages moved to this section (, , and Future OS NGD Data Enhancements (page since superseded by a 'OS NGD planned enhancements outlined in our roadmap' note on the page in August 2026).

    • New section created for DATA AND SERVICE STATUS, with three pages moved to this section (, and ).

    • ACCESSING OS NGD section renamed as GETTING STARTED and various pages moved into this section (, , , , , and

    5.2

    09/05/2025

    New page added to the site: . The page highlights recent improvements OS has made to the data that are not connected to the biannual big data releases in spring and autumn.

    5.1

    27/03/2025

    New pages added for the March 2025 OS NGD data enhancements release:

    • Pages added for the new , , and Feature Types.

    • Eighteen new code lists added: Roof Material Value, Roof Shape Value, Roof Confidence Indicator Value, Physical State Value, Access Mode Value, Access Purpose Value, Access Obstruction Value, Access Level Value, Building Access Location Description Value, Network Node Feature Type Value, Street Light Description Value, Link Reference Confidence Value, Transport Feature Type Value, Illumination Value, Crowd Sourced Name Description Value, Crowd Sourced Name Match Type Value, Matched Feature Type NGD Value and Matched Theme NGD Value

    Existing pages amended with information about the March 2025 OS NGD data enhancements:

    5.0

    25/03/2025

    OS Premium Download Products section deleted from the OS NGD Documentation site. Documentation for the (OS MRN) and (OS ESG) products was moved to the .

    4.9

    13/03/2025

    Updates made to the page to reflect the release of new sample data connected to the March 2025 OS NGD data enhancements for the following collections: OS Building Features, OS Land Use Features, OS Named Features, OS Structure Features, OS Transport Features, and OS Transport Network Collections.

    4.8

    11/03/2025

    Publication of new page: .

    4.7

    06/02/2025

    Former 'Known Data Issues' page split into two pages: and .

    4.6

    26/09/2024

    New pages added for the September 2024 OS NGD data enhancements release:

    • Six new code lists added: Address Classification Source Value, Classification Correlation Value, Matched UPRN Value, Network Over Under Bridge Value, Status Value, and Yes No Value

    Existing pages amended with information about the September 2024 OS NGD data enhancements:

    • Updates made to the Building Part, Land, Rail, Road Link, Road Track Or Path, Site, Structure, and Water Feature Type pages to reflect new attribution for land use, as supplied with data schema version 3.0 for all feature types bar Building Part and Site, which are supplied with data schema version 2.0.

    4.5

    27/03/2024

    New pages added for the March 2024 OS NGD data enhancements release:

    • Pages added for the new Field Boundary, Named Road Junction, and Tram On Road Feature Types, together with pages for their associated new code lists.

    • New sections added to the USING NGD DATA section for OS NGD Land cover enhancements, OS NGD Structures and OS NGD Transport.

    Existing pages amended with information about the March 2024 OS NGD data enhancements:

    • Updates made to the Land, Rail, Road Link, Road Track Or Path, Structure, and Water Feature Type pages to reflect new attribution for land cover, as supplied with data schema version 2.0 for all feature types bar Road Link, which is supplied with data schema version 3.0.

    4.4

    28/09/2023

    New pages added for the September 2023 OS NGD data enhancements release:

    • Pages added for the new Building, Railway Link, Railway Link Set, Railway Node, and Pavement Link Feature Types, together with their associated new code lists.

    Existing pages amended with information about the September 2023 OS NGD data enhancements:

    • Updates made to the Road Link Feature Type page to reflect the new attribution for pavement presence, as supplied with data schema version 2.0.

    • New section added to the USING NGD DATA section for OS NGD Buildings.

    4.3

    10/08/2023

    Changes introduced to reflect expansion of coverage from urban paths only to GB-wide coverage.

    4.2

    21/06/2023

    New page added to the GETTING STARTED section: 'OS NGD Talks, Webinars, Tutorial Videos and Case Studies'.

    4.1

    19/06/2023

    Temporal filtering sub-section wording updated on the feature type pages of eight feature types in the OS NGD Addressing Theme in the DATA STRUCTURE section. The earliest and latest dates on which you can request a one-off snapshot of a date in the past for the data schema versions available for these feature types are now documented. Example images added to all OS NGD collection pages (in the DATA STRUCTURE section) to show what the different feature types in the collections look like in the data. A background map has been included in each image to provide context. Example images added to the 'Average And Indicative Speed', 'Highway Dedication' and 'Restriction' Feature Types pages (of the OS RAMI Collection) to show what the different feature types look like in the data. A background map has been included in each image to provide context.

    4.0

    15/06/2023

    Definition expanded for the Average And Indicative Speed Feature Type (of the OS RAMI Collection). Road Link Direction attribute (OS RAMI Collection, attribute for the Restriction Feature Type) definition updated from ‘The direction in which the restriction applies in direction of digitisation of the Road Link feature.’ to ‘The direction in which the restriction applies in relation to the direction of digitisation of a Road Link feature'. Directionality attribute (OS Transport Network Collection, attribute for the Road Link Feature Type) definition updated from ‘Indication of the direction of traffic flow.’ to ‘Indication of the direction of traffic flow in relation to the direction of digitisation of a Road Link feature'. Three missing definition values entered in the Link Direction value code list and final sentence of code list definition expanded.

    3.9

    12/06/2023

    New warning note added to the 'Site Routing Point Feature Type' page under the feature type description at the top of the page. Information note added to the 'Road Node Feature Type' page under the feature type description at the top of the page. Fifth reason added for one of the General FAQs on the FAQs page ('Why am I receiving blank files?' FAQ), relating to the Site Routing Point Feature Type being an 'end of life' feature type as of late spring 2023.

    3.8

    07/06/2023

    New announcement added to 'Product Announcement' page: 'June 2023: 5 days of system downtime for feature types'.

    3.7

    25/05/2023

    New images added to the 'Homepage', 'What's New?', 'Terminology and access', and 'OS NGD Future Data Enhancements' (page since superseded by a 'OS NGD planned enhancements outlined in our roadmap' note on the What's New? page in August 2026) pages.

    3.6

    03/05/2023

    One YouTube video added to the 'Accessing OS NGD APIs' page; the video gives instructions on how to add OS NGD API – Tiles to a new project on the OS Data Hub and generate an API key. One YouTube video added to the 'Getting Started with Attribute Filtering' page and the 'Getting Started with Temporal Filtering' page; the video gives instructions on how to get started with both attribute filtering and temporal filtering in OS Select+Build.

    3.5

    21/04/2023

    'Known Data Issues' page: New section and table added for 'OS NGD Transport Theme known data issues' to document an 'Incorrect speed values' issue.

    3.4

    06/04/2023

    New page added to 'DATA STRUCTURE' section: 'Product Announcements'. New section ('How do I check if filters are used in an existing recipe?') added to the 'Getting Started with Attribute Filtering' sub-page in the 'Accessing OS NGD' section.

    3.3

    05/04/2023

    New sub-page added to the 'Downloading with OS Select+Build' page in the 'Accessing OS NGD' section: 'Getting Started with Temporal Filtering'.

    3.2

    03/04/2023

    More information added about default coordinate reference systems available for the OS RAMI, OS Water Network and OS Transport Network Collections on their retrospective collection pages in the Data Structure section and in the 'Coordinate reference systems' page in the OS NGD Fundamentals section.

    3.1

    30/03/2023

    Recipe sharing information added to the 'What's New?' page and the 'Downloading with OS Select+Build' page.

    3

    29/03/2023

    New pages published: 'Data schema versioning' and 'What's New?' (both within the Getting Started section); 'Versioning information' (within OS NGD Address in the Data Structure section). Existing pages amended with information about the March 2023 OS NGD data enhancements: 'OS NGD Key Benefits to Customers'; 'OS NGD Fundamentals'; 'Downloading with OS Select+Build'; 'Accessing OS NGD APIs'; 'Using Code Examples'; theme pages for Address, Transport and Water; all 13 collection pages; 'Known Data Issues'; 'Data Catalogue'; 'FAQs'; 'Future OS NGD Data Enhancements' (page since superseded by a 'OS NGD planned enhancements outlined in our roadmap' note on the What's New? page in August 2026). Coming soon banner removed from all relevant addressing feature type pages and from the Average And Indicative Speed, Waterbody Catchment, and River Basin District Catchment Feature Type pages.

    2.9

    23/03/2023

    Diagrams added to the 'Water Link' and 'Water Link Set' Feature Type pages (within the DATA STRUCTURE section) to show how these features look in OS NGD data.

    2.8

    10/03/2023

    New pages published for the Average And Indicative Speed Feature Type (within the OS RAMI Collection of the OS NGD Transport Theme), Capture Method Value Code List, and Average And Indicative Speed Description Value Code List. New pages published for the Waterbody Catchment Feature Type and River Basin District Catchment Feature Type (both within the OS Water Features Collection of the OS NGD Water Theme), Waterbody Category Value Code List, Waterbody Catchment Description Value Code List, and River Basin District Catchment Description Value Code List. Existing pages updated to include data schema version 2 information and new attributes for the Built Address, Historic Address, Non-Addressable Object and Pre-Build Address Feature Types in both the OS GB Address and OS Islands Address Collections (within the OS NGD Address Theme). The Related Entity Related Component page was also updated to include data schema version 2 information and new attributes.

    2.7

    08/03/2023

    'Known Data Issues' page: Section and table removed for 'OS NGD Transport Theme known data issues' as these have been resolved. 'Daily COU updates temporarily paused' row removed from 'OS NGD Address Theme known data issues' table as this issue has been resolved. Page title change from 'Accessing OS NGD API – Features' to 'Accessing OS NGD APIs' in the DATA STRUCTURE section.

    2.6

    06/03/2023

    Temporal filtering information added to the top of all 81 feature type pages (detailing the earliest date on which you can request a one-off snapshot of a date in the past for data in each feature type). Temporal filtering information generalised on all 13 collection pages, pointing users to individual feature type pages to get dates instead.

    2.5

    03/03/2023

    Content published on the 'Getting Started with Attribute Filtering' page.

    2.4

    22/02/2023

    Order of pages amended in the 'OS NGD Fundamentals' section and new placeholder page on 'Data schema versioning' added to this section. New placeholder page on 'What's New' added to 'GETTING STARTED' section. New placeholder page 'Versioning information' added to 'DATA STRUCTURE' section for the Addressing Theme. Geometry type corrected from Polygon to MultiPolygon for the Geometry attribute of all feature types in the OS Boundaries Collection (apart from the Boundary High Water Mark, GLA Assembly Constituency and Regional Authority Feature Types).

    2.3

    20/02/2023

    'Known Data Issues' page: New section and table added for the OS NGD Transport Theme known data issues. New row added to the OS NGD Address Theme known data issues table ('Daily COU updates temporarily paused').

    2.2

    30/11/2022

    Missing definitions added to the 'Structure Land Cover Tier A Value' and 'Structure Land Cover Tier B Value' Code Lists.

    2.1

    25/11/2022

    New section added to the 'Known Data Issues' page for the OS NGD Administrative and Statistical Units Theme.

    2

    17/11/2022

    'Known Data Issues' page added to the Data Structure section. Updates made to the 'Coordinate Reference Systems' page: table added outlining the default coordinate reference system used by each OS NGD collection; note deleted; OS Select+Build list of coordinate reference systems altered by removing World Geodetic System (WGS84: EPSG: 4326) and inserting European Terrestrial Reference System (ETRS89: EPSG: 4258). New OS Select+Build FAQ added to the 'FAQs' page ('How do I identify the correct OS NGD collection for calculating usage?').

    1.9

    16/11/2022

    Updates made to the 'Sample Data Information' page to mention that sample data is now available for the OS GB Address Collection. Sample data is available for 12 of the 13 OS NGD collections. Note added to say that sample data won't be released for the OS Islands Address Collection. Wording updated for two of the General FAQs on the 'FAQs' page ('Why am I receiving blank files?' FAQ and the 'Why do I have different start dates when applying temporal filters to different feature types?' FAQ).

    1.8

    08/11/2022

    New General FAQ added to the 'FAQs' page ('What are the default coordinate reference systems used by the OS NGD collections?'). New sections added to the 13 OS NGD collection pages on earliest temporal filtering date and default coordinate reference systems.

    1.7

    04/11/2022

    New note added to the 'Data ordering and currency' page about geographic filtering supply options. Note added to the 'Related Components' page. New note added to the 'COU supplies' page about features moving between OS NGD themes and between OS NGD feature types. Introductory sentence added above the CSV structure table on the 'File formats and naming' page. Definition added for the 'Made Surface' label in the 'Rail Description Value' Code List. The maintenanceauthority_authorityname attribute's definition was corrected from 'The authority responsible for the street naming and numbering or maintenance' to 'The authority responsible for maintenance.'

    1.6

    03/11/2022

    Formatting changes on the 'FAQs' page to include expandable blocks. Minor changes to two labels in the 'Land Description Value' Code List: 'Heath Or Rough Grassland And Scattered Boulders or Scattered Rock' was changed to 'Heath Or Rough Grassland And Scattered Rock'; and 'Heath Or Rough Grassland And Scattered Boulders or Scattered Rock And Scrub' was changed to 'Heath Or Rough Grassland And Scattered Rock And Scrub'.

    1.5

    01/11/2022

    Note (saying that ''the Address Theme will be launched later this year'') removed from the top of the OS NGD Address Theme, OS GB Address Collection and OS Islands Address Collection pages as the OS NGD Address Theme went live to customers in OS Select+Build on 31/10/2022. Correction made to the feature type description on the Connecting Link Feature Type page to say that a Connecting Link does not represent a feature in the real world.

    1.4

    28/10/2022

    Updates made to the 'OS NGD Sample Data Information' page to mention that sample data is now available for the OS Boundaries Collection. Sample data is available for 11 of the 13 OS NGD collections.

    1.3

    21/10/2022

    Updates made to the 'OS NGD Sample Data Information' page to mention that sample data is now available for the OS Water Network, OS Transport Network, OS Named Features, and OS Routing and Asset Management Information (RAMI) Collections. Sample data is available for 10 of the 13 OS NGD collections.

    1.2

    14/10/2022

    Amendments made to the instructions for loading CSV files into an Oracle database in the 'Loading CSV files' page.

    1.1

    11/10/2022

    'Data Entity Catalogue' Code List updated to remove OS NGD Landform label and insert OS NGD Rail label. 'OS Land Use Tier B Value' Code List updated to include previously unavailable definitions for all bar five labels. 'Accessibility' page added to the EXTRA LINKS section. Additional instructions added to the 'Downloading with OS Select+Build' page on downloading data packages. Two YouTube videos added to the 'Downloading with OS Select+Build' page; the videos give instructions on how to create a new recipe using OS Select+Build, and how to create and download a data package using OS Select+Build. One YouTube video added to the 'Accessing OS NGD APIs' page; the video gives instructions on how to add OS NGD API – Features to a new project on the OS Data Hub and generate an API key.

    1

    29/09/2022

    OS NGD official launch to customers.

    0.3

    25/08/2022 to 29/09/2022

    Amendments to multiple pages and publication of new pages in preparation for OS NGD launch.

    0.2

    24/08/2022

    Amendments to multiple pages in preparation for the first set of OS NGD sample data being released.

    0.1

    12/05/2022

    Pre-release of OS NGD documentation on the OS NGD Documentation Platform.

    9.5

    23/10/2026

    New OS recommended recipe guide added to the site: Town and city planning recipe guide.

    9.4

    08/10/2026

    Existing pages amended with information about the October 2026 OS NGD data enhancement release for data schema versions 1.1 and 2.0 of the Royal Mail Address Feature Types in the OS GB Address and OS Islands Address Collections:

    • Updates made to the following pages: What's New?, OS NGD Fundamentals – Data ordering and currency, OS NGD Fundamentals – Data schema versioning, OS NGD News, OS NGD Sample Data and FAQs.

    • Minor updates made to the OS GB Address Collection and OS Islands Address Collection pages.

    • Warning notes (saying that data isn’t live yet through the live access service of OS Select+Build) removed from the following pages:

      • OS NGD Fundamentals – page

      • page

      • (OS GB Address Collection) page

      • (OS Islands Address Collection) page

      • and pages

      • page

      • , and Related Components pages

    • New 'Related components' section added to 10 of the 12 addressing feature type pages to inform customers that these feature type use related components:

      • , , , and in the OS GB Address Collection

      • , , , and in the OS Islands Address Collection

    9.3

    01/10/2026

    Existing pages amended with information about the October 2026 OS NGD data enhancement release for data schema version 2.0 of the Regional Authority Feature Type in the OS Boundaries Collection:

    • Updates made to the following pages: What's New?, OS NGD News and FAQs.

    • Warning notes (saying that data isn’t live yet through the live access services of OS Select+Build and OS NGD API – Tiles) have been removed from the following pages:

      • Regional Authority Feature Type page

    What's New?
    OS Data Products Roadmap
    OS NGD Improvements

    Minor updates made to the definitions of the following existing code lists to account for new attributes in the Royal Mail Address Feature Type using the code lists: Country Value and Postcode Type Value.

  • Updates made to the following pages: OS NGD Fundamentals – Unique identifiers (new Unique Multiple Residence Reference Number identifier added), OS NGD Address Theme (extensive changes to the unique identifiers and data structure sections), and Address Related Components (extensive updates with the addition of three new Royal Mail related components, plus a page name change from Related Components to Address Related Components).

  • Regional Authority Feature Type definition updated:

    • From: With the introduction of the regional government for London (referred to as the Greater London Authority or GLA by OS NGD documentation), the proportional representation voting area for this new administration is the GLA Assembly Constituency. The existing London borough structure also has a relationship with the new GLA, and each London borough is divided for voting purposes into London borough wards.

    • To: Regional authorities, also known as strategic or combined authorities, are regional bodies formed by local authorities to manage devolved powers (for example, coordinating regional transport, economic growth and strategic planning policies).

  • Major data schema version increment from 1.1 to 2.0 for one existing feature type: Regional Authority. This is due to adding five new values to the related code list (Regional Authority Description Value) and changing the geometry type for the Geometry attribute from Polygon to MultiPolygon.

  • Major version increment from 1.0 to 2.0 for one existing code list: Regional Authority Description Value. This is due to adding five new values to the code list and updating the definition of the original value in the code list.

  • ⚠️ Please note that the pages mentioned above have been amended on / added to this documentation site to give customers an advanced preview of the upcoming data for the October 2026 OS NGD data enhancements release. Data schema versions 1.1 and 2.0 for the Royal Mail Address Feature Types, the three new Royal Mail related components, and data schema version 2.0 for the Regional Authority Feature Type are currently not available through OS Select+Build (the bespoke download service). The information held on the new and updated pages is as accurate as possible but is subject to change before the OS NGD data enhancements release at the start of October 2026.

    Other road network information

  • National street gazetteers, GeoPlace and Improvement Service

  • Path network

  • Ferry network

  • Rail network

  • Transport features

  • How Site Description values map across to National Land Use Database (NLUD) values

  • How OS Land Use Tier A and Tier B classifications map across to one another

  • How Site Description values map across to OS Land Use Tier A and Tier B classifications

  • Which Sites have populated Status attribute values

  • There wasn't a need to list the monthly feature counts for these two collections separately as this information is provided by Order Summary Files.

    Order Summary File: Feature types downloaded via OS Select+Build are supplied with an Order Summary File, a small JSON manifest that provides key metadata about the supplied file; you can use this file to validate the data to ensure the currency, record counts (feature counts), schema version, feature name and coordinate reference system (CRS) match your expected order.

    (What's next? section added to the bottom of the page)
  • What's New? (entry about the new recipe added to the top of the page)

  • Minor updates and clarifications made to the following pages in the Using NGD Data section: Bus Lane Feature Type, Road Link attribution, Known limitations, Cycle Lane Feature Type, Road Link and Path Link attribution, and Known limitations.
  • Warning note about incomplete data coverage removed from the top of the Bus Lane Feature Type and Cycle Lane Feature Type pages.

  • Warning notes (saying that data isn’t live yet through the live access services of OS Select+Build and the OS NGD APIs) removed from the following pages:

    • OS NGD Administrative and Statistical Units Theme page

    • OS Functional Areas, OS GB Postcodes and OS NI Postcodes Collections pages

    • Compound Structure, Retail Area Aggregated, Retail Area Major, Retail Area Minor, Postcode Unit Area, Postcode Unit Point and Postcode Unit Point Feature Type pages

    • , , , , , , , , , , , and Code List pages

  • ,
    , and

    Existing pages amended ahead of the March 2026 OS NGD data enhancements release:

    • Major data schema version increment from 2.0 to 3.0 for one existing feature type: Compound Structure (v3.0)

    • Updates made to the OS NGD Administrative and Statistical Units Theme page to include information about the three new collections that will be added to the theme at the end of March 2026.

    • Major version increment from 1.0 to 2.0 for one existing code list: Relationship Type Value.

    • Updates made to the following pages: OS NGD Fundamentals – Unique identifiers and Coordinate reference systems.

    Updates made to the OS Water Network Collection page.
  • Updates made to the following pages: What's New?, OS NGD Fundamentals – Data schema versioning, OS NGD Fundamentals – Data ordering and currency, Future OS NGD Data Enhancements (page since superseded by a 'OS NGD planned enhancements outlined in our roadmap' note on the What's New? page in August 2026), OS NGD News (Recent Announcements section), Current Known Data Issues and FAQs.

  • The aforementioned code list names were corrected to remove 'os' from them where they are mentioned on the following seven feature type pages: Building Part, Land, Rail, Road Track Or Path, Site, Structure and Water.

    Eight major data schema versions released for existing feature types: Built Address (v3.0), Built Address (v3.0), Historic Address (v3.0), Historic Address (v3.0), Non-Addressable Object (v3.0), Non-Addressable Object (v3.0), Pre-Build Address (v3.0) and Pre-Build Address (v3.0)
  • Updates made to the Built Address, Historic Address, Non-Addressable Object and Pre-Build Address Feature Type pages in the OS GB Address Collection and the Built Address, Historic Address, Non-Addressable Object and Pre-Build Address Feature Type pages in the OS Islands Address Collection to reflect changes in the max length of certain attributes, modifications to associated code lists for a few attributes, and the addition of download filters and new associated code lists for certain attributes, as supplied with data schema version 3.0 of these feature types.

  • Three major data schema versions released for existing addressing related components: Alternate Address (v3.0), Other Classification (v3.0) and Related Entity (v3.0).

  • Warning note added to the Postal Address Related Component page.

  • Five existing code lists updated: AddressBase Postal Value, Address Description Value, Build Status Value, Data Entity Catalogue and Positional Accuracy Value

  • Updates made to the OS NGD Address Theme page.

  • Updates made to two collection pages: OS GB Address and OS Islands Address.

  • Updates and improvements made to the Related Components information page.

  • Versioning information page for OS NGD Address Theme deleted as this information is available from the data schema version section and table at the top of each individual feature type page (for example, Built Address).

  • Updates made to the following pages: What's New?, OS NGD Fundamentals – Data schema versioning, OS NGD Fundamentals – Unique identifiers, and Future OS NGD Data Enhancements (page since superseded by a 'OS NGD planned enhancements outlined in our roadmap' note on the What's New? page in August 2026).

  • Updates made to the following pages: What's New?, Current Known Data Issues and Future OS NGD Data Enhancements (page since superseded by a 'OS NGD planned enhancements outlined in our roadmap' note on the What's New? page in August 2026).

    Existing pages amended with information about the September 2025 OS NGD data enhancements:
    • Two major data schema versions released for existing feature types: Path Link (v3.0) and Road Link (v5.0).

      • Updates made to the Path Link Feature Type page to reflect the addition of new Presence of Cycle Lane attribution and the removal of Cycle Facility attribution, as supplied with data schema version 3.0 onward.

      • Updates made to the Road Link Feature Type page to reflect the addition of new Presence of Bus Lane and Presence of Cycle Lane attribution and the removal of Cycle Lane Facility attribution, as supplied with data schema version 5.0 onward.

    • Four existing code lists updated: , , and

    • Updates made to the following two OS NGD theme pages: and .

    • Updates made to the following three OS NGD collection pages: , and .

    • Updates made to the (in the ‘USING OS NGD DATA’ section) to reflect the enhancements made to the Physical State attribute for the Building Feature Type.

    • Updates made to the following pages: , , OS NGD Fundamentals – , Future OS NGD Data Enhancements (page since superseded by a 'OS NGD planned enhancements outlined in our roadmap' note on the page in August 2026), , , , and .

    ,
    ,
    ,
    ,
    ,
    , and

    Instructions updated throughout the page to reflect recent navigation changes to the top and secondary navigation menus in the OS Data Hub.

  • New sub-section added for 'How do I edit a recipe?'

  • New sub-section added for 'How do I delete a data package?'

  • Updates made to the 'Things to remember' boxes at the bottom of the page.

  • .
  • GETTING STARTED section renamed as INTRODUCTION TO OS NGD and various pages moved into this section (OS NGD Explained, OS NGD Key Benefits to Customers, OS NGD Sample Data and OS NGD Data Viewer.

  • New page added to the site: OS NGD Explained.

  • OS NGD Core Principles renamed as OS NGD Fundamentals.

  • Product Announcements page content moved to the bottom of the new OS NGD News landing page as a sub-section called Recent Announcements.

  • Landing pages (Introduction to OS NGD, Getting Started Information, OS NGD News, Data and Service Status Information and Data Structure Information) added for all sections. These pages use navigation cards to show what content is available in the section. What's Next? sections with navigation cards and links added to all new landing pages to improve the customer experience.

  • Homepage content updated. New navigation cards added to the bottom of the page to show what's available on the site.

  • Four major data schema versions released for existing feature types: Building (v4.0), Path Link (v2.0), Road Link (v4.0), Site Access Location (v2.0):

    • Updates made to the Building Feature Type page to reflect the new attribution for Roof Shape, Roof Aspect, Roof Material, Solar Panel Presence, Green Roof Presence and Building Height, as supplied with data schema version 4.0.

    • Updates made to the Path Link Feature Type page to reflect the addition of new Street Light attribution, as supplied with data schema version 2.0.

    • Updates made to the Road Link Feature Type page to reflect the addition of new Street Light attribution, as supplied with data schema version 4.0.

    • Updates made to the page to reflect new Access Purpose attribution, as supplied with data schema version 2.0.

  • Seven minor data schema versions released for existing feature types: Building Part (v2.1), Land (v3.1), Rail (v3.1), Road Track Or Path (v3.1), Site (v2.2), Structure (v3.1) and Water (v3.1).

  • Four code lists updated: Built Structure Height Confidence Value, Site Description Value, Site Access Location Description Value and Compound Structure Description Value.

  • Updates made to the OS NGD Buildings pages (in the ‘USING NGD DATA’ section) to reflect the release of the new Building Access Location Feature Type (v1.0) and the addition of new attribution in the Building Feature Type (v4.0) for Roof Shape, Roof Aspect, Roof Material, Solar Panel Presence, Green Roof Presence and Building Height.

  • Updates made to the OS NGD Transport pages (in the ‘USING NGD DATA’ section) to reflect the addition of the new Street Light Feature Type to the OS Transport Features Collection and the addition of new Street Light attribution in the Path Link Feature Type (v2.0) and Road Link Feature Type (v4.0) of the OS Transport Network Collection.

  • Updates made to the following three OS NGD theme pages: Buildings, Geographical Names, and Transport.

  • Updates made to the following five OS NGD collection pages: OS Building Features, OS Land Use Features, OS Named Features, OS Transport Features, and OS Transport Network.

  • Updates made to the following pages: What's New?, Current Known Data Issues, OS NGD Fundamentals – Data schema versioning, OS NGD Fundamentals – Data ordering and currency, Future OS NGD Data Enhancements (page since superseded by a 'OS NGD planned enhancements outlined in our roadmap' note on the What's New? page in August 2026), OS NGD Webinars, Tutorials and Case Studies, OS NGD API – Features – What data is available? and FAQs.

  • Updates made to the Compound Structure Feature Type page to reflect new attribution for bridge interactions, as supplied with data schema version 2.0.
  • Updates made to the Building Feature Type page to reflect new Number of Floors attribution, as supplied with data schema version 3.0.

  • Three code lists updated: Building Part Description Value, Compound Structure Description Value and Relationship Type Value.

  • Updates made to the OS NGD Buildings pages (in the USING NGD DATA section) to reflect new Number of Floors attribution in data schema version 3.0 of the Building Feature Type.

  • Updates to the 'What's New?', 'Known data issues', 'Product announcements', 'OS NGD Fundamentals', 'Future OS NGD Data Enhancements'(page since superseded by a 'OS NGD planned enhancements outlined in our roadmap' note on the What's New? page in August 2026), and 'Sample data' pages.

  • Updates made to the following collection pages: OS Structure Features, OS Land Features, OS Land Use Features, OS Building Features, OS Transport Features and OS Water Features Collections.

  • Updates to the 'What's New?', 'Product announcements', 'Future OS NGD Data Enhancements' (page since superseded by a 'OS NGD planned enhancements outlined in our roadmap' note on the What's New? page in August 2026), and 'Sample data' pages.

  • Updates to the 'What's New?', 'Product announcements', 'Future OS NGD Data Enhancements' (page since superseded by a 'OS NGD planned enhancements outlined in our roadmap' note on the What's New? page in August 2026), and 'Sample data' pages.

  • Updates made to the OS Building Features and OS Transport Network Collections pages.

  • Unique identifiers
    OS NGD Address Theme
    Royal Mail Address Feature Type
    Royal Mail Address Feature Type
    Country Value Code List
    Postcode Type Value Code List
    Address Related Components
    Multiple Residence
    Delivery Point Alias
    Other Alias
    Built Address
    Historic Address
    Non-Addressable Object
    Pre-Build Address
    Royal Mail Address
    Built Address
    Historic Address
    Non-Addressable Object
    Pre-Build Address
    Royal Mail Address
    Regional Authority Description Value Code List page
    Identifying crossing points and bottlenecks
    Multiple Residence
    Delivery Point Alias
    Other Alias
    Royal Mail Address
    Royal Mail Address
    What's New page
    OS Data Products Roadmap
    Transport networks in the OS NGD explainer
    'Understanding land use in the OS NGD' guide
    Coordinate reference systems page in the OS NGD Fundamentals
    Identifying higher-risk buildings recipe guide
    Safer routes to schools recipe guide
    Data ordering and currency
    OS NGD Transport Theme
    OS RAMI Collection
    OS Transport Network Collection
    FAQs page
    Land Feature Type
    Land Description Value Code List
    greenspace recipe guide page
    Devolved Parliament Constituency Feature Type
    OS NGD News page
    What's New? page
    Building Access Location Feature Type
    Access Obstruction attribute
    Access Obstruction Value Code List
    Managing OS OS Select+Build recipes
    Getting started with attribute filtering
    Getting started with data packages
    OS NGD API – Features
    OS NGD API – Tiles
    OS API FAQs
    OS GB Postcodes
    OS NI Postcodes
    Getting started with OS recommended recipes
    Greenspace recipe guide
    Downloading with OS Select+Build
    Country Value Code List
    What's New?
    Current Known Data Issues
    Coordinate reference systems
    Data ordering and currency
    Data schema versioning
    File formats and naming
    Unique identifiers
    What's New?
    OS NGD API – Features – What data is available?
    OS NGD API – Features
    OS NGD News
    OS NGD Improvements
    FAQs
    OS Structure Features
    OS Transport Network
    Data ordering and currency page
    Building Feature Type
    Build Status Value Code List
    Road Track Or Path Feature Type
    OS Functional Areas
    OS GB Postcodes
    OS NI Postcodes
    Retail Area Aggregated
    Retail Area Major
    Retail Area Minor
    Postcode Unit Area
    Postcode Unit Point
    Postcode Unit Point
    Data Entity Catalogue Compound Structure Value
    Data Entity Catalogue Postcode Value
    Data Entity Catalogue Retail Area Value
    Density Value
    Input Address Accuracy Value
    Postcode Unit Area Description Value
    Postcode Unit Point Description Value
    Retail Area Aggregated Description Value
    Retail Area Major Description Value
    Retail Area Minor Description Value
    Water Link Width Derivation Method Value
    Water Link (v2.0)
    Water Node Feature Type
    Water Node Description Value Code List
    Data ordering and currency page
    Boundary High Water Mark Description Value
    Country Description Value
    Electoral Division Description Value
    GLA Assembly Constituency Description Value
    Historic County Description Value
    Historic European Region Description Value
    Parish Or Community Description Value
    Polling District Description Value
    Region Description Value
    Ward Description Value
    Building Part Land Cover Tier A Value
    Building Part Land Cover Tier B Value
    Land Cover Tier A Value
    Land Cover Tier B Value
    Rail Land Cover Tier A Value
    Rail Land Cover Tier B Value
    Road Track Or Path Land Cover Tier A Value
    Road Track Or Path Land Cover Tier B Value
    Structure Land Cover Tier A Value
    Structure Land Cover Tier B Value
    Water Land Cover Tier A Value
    Water Land Cover Tier B Value
    Land Use Tier A Value
    Land Use Tier B Value
    Processing COUs
    Royal Mail Address
    Royal Mail Address
    Address Classification Code Value
    Address Classification Description Value
    Address Primary Classification Description Value
    Address Quaternary Classification Description Value
    Address Secondary Classification Description Value
    Address Tertiary Classification Description Value
    Geometry Allocation Method Value
    Matched Address Feature Type Value
    Matching Organisation Value
    Match Method Value
    RM To LA Match Type Value
    Royal Mail Address Description Value
    Land
    Site
    Site Description Value
    OS Building Features
    OS Land Features
    OS Land Use Features
    OS Structure Features
    OS Transport Features
    OS Water Features
    Bus Lane
    Cycle Lane
    Tidal Boundary Continuous High
    Tidal Boundary Continuous Low
    Bus Lane Description Value
    Cycle Lane Description Value
    Side Of Link Value
    Tidal Boundary Continuous High Description Value
    Tidal Boundary Continuous Low Description Value
    Bus lanes
    Cycle lanes
    OS NGD Transport sub-section (in the ‘USING NGD DATA’ section)
    Introduction to OS NGD
    Getting Started
    OS NGD Documentation
    OS NGD Explained
    OS NGD Explained
    OS NGD Key Benefits to Customers
    OS NGD Sample Data
    Getting Started Information
    OS NGD Fundamentals
    Accessing OS NGD APIs
    Downloading with OS Select+Build
    Managing OS Select+Build recipes
    Editing OS Select+Build recipes
    Sharing OS Select+Build Recipes
    Getting started with recipes
    Getting started with data packages
    Boundary High Water Mark
    Country
    GLA Assembly Constituency
    Historic County
    Historic European Region
    Regional Authority
    Site Access Location
    Connecting Link
    Connecting Node
    Ferry Link
    Building Part Feature Type
    OS Land Cover Tier A attribute's
    OS Land Cover Tier B attribute's
    Building Part Land Cover Tier A Value Code List
    Building Part Land Cover Tier B Value Code List
    FAQs page
    What's New?
    OS NGD News landing page's Recent announcements section
    Downloading with OS Select+Build page
    Alternate Address
    Postal Address
    Other Classification
    Related Entity
    Built Address
    Historic Address
    Non-Addressable Object
    Pre-Build Address
    Built Address
    Historic Address
    Non-Addressable Object
    Pre-Build Address
    Building
    Building Part
    Land
    Site
    Site Access Location
    Compound Structure
    Structure
    Rail
    Road Track Or Path
    Path Link
    Road Link
    Water
    What's New?
    Change Log
    OS NGD Improvements
    What's New?
    Live Service Disruption and Planned Maintenance
    Current Known Data Issues
    Resolved Data Issues
    OS NGD Fundamentals
    Downloading with OS Select+Build
    Accessing OS NGD APIs
    Styling OS NGD Data
    OS NGD Webinars, Tutorials and Case Studies
    OS NGD Improvements
    Building Access Location
    Crowd Sourced Name Point
    Street Light
    OS Multi-modal Routing Network
    OS Emergency Services Gazetteer
    OS Download Products' Documentation site
    OS NGD Sample Data Information
    Live Service Disruption and Planned Maintenance
    Current Known Data Issues
    Resolved Data Issues
    Getting started with recipes
    Retail Hierarchy Value
    Retail Setting Value
    Ferry Node
    Ferry Terminal
    Path
    Path Node
    Road
    Railway Link Set
    FAQs
    Data Entity Catalogue Compound Structure Value
    Data Entity Catalogue Postcode Value
    Data Entity Catalogue Retail Area Value
    Density Value
    Input Address Accuracy Value
    Postcode Unit Area Description Value
    Postcode Unit Point Description Value
    Relationship Type Value
    Retail Area Aggregated Description Value
    Retail Area Major Description Value
    Retail Area Minor Description Value
    Retail Hierarchy Value
    Retail Setting Value
    Building Description Value
    Link Direction Value
    Link Reference Confidence Value
    Transport Feature Type Value
    Transport
    Water
    OS Building Features
    OS Transport Network
    OS Water Features
    OS NGD Building pages
    What's New?
    Current Known Data Issues
    Data ordering and currency
    What's New?
    OS NGD API – Features – What data is available?
    OS NGD API – Tiles – What data is available?
    OS NGD News
    OS NGD Improvements
    FAQs
    Site Access Location Feature Type