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

What is the OS NGD?

How do I access the OS NGD?

Who can use the OS NGD?

Discover OS NGD

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

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

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.

What's the OS NGD?

What's available on this site?

Accessing OS NGD data with OS NGD API – Tiles via GIS software

The following sub-sections provide step-by-step instructions on how to access OS NGD data via OS NGD API – Tiles in various GIS software packages:

• Cadcorp SIS

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 for more information.

Upon OS NGD launch, 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.

Requirements

• CadCorp SIS (version SIS 9 or later)

• A GeoPackage dataset

Requirements

• MapInfo Professional (version 15.2 or later)

• A GeoPackage dataset

Requirements

• QGIS (version 2.10.1 or later)

• A GeoPackage dataset

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

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.

The following pages provide an overview of the OS NGD APIs and how you can access them. They cover the core elements of the design (including data available), technical specifications, and how to get started, amongst other topics.

The following pages provide an overview of how to get started using OS NGD API – Features. They provide step-by-step instructions to get started in the most common and .

Accessing OS NGD data with OS NGD API – Features via GIS software

The following sub-sections provide step-by-step instructions on how to access OS NGD data via OS NGD API – Features in various GIS software packages:

ArcGIS Online is a web-based platform geographic information system (GIS). ArcGIS Online services are managed by Esri and accessed by a client running on a wide range of options.

The instructions that follow demonstrate how to connect to OS NGD API – Features using ESRI ArcGIS Online.

What you need

• Access to the ESRI ArcGIS Online service.

Accessing OS NGD data with OS NGD API – Features via web mapping libraries

The following sub-sections provide step-by-step instructions on how to access OS NGD data via OS NGD API – Features in various web mapping libraries:

OS NGD API – Tiles Technical Specification provides an overview of the endpoints available, as well as the parameters that can be used with each endpoint. The Technical Specification is intended to be used by customers who want to integrate with the API. The service offers the following endpoints:

The following pages provide an overview of how to get started using the OS NGD API – Tiles. They cover the core elements to get started in the most common and .

Primary unique identifier for the OS NGD

The OS NGD primarily uses a new identifier called the OSID (OS Identifier) to uniquely identify features. The OSID is used persistently and allows the unique identification of records in the OS NGD. It should be noted that the OSID is not unique across the OS NGD but rather is only unique at a feature type level. The reason for this is, when possible, the same OSID will be used on multiple features when they represent the same geographical feature. For example, a point feature in the OS NGD Geographical Names Theme which represents a water body will have the same OSID as the more detailed water body representation in the OS NGD Water Theme.

Other unique identifiers

UPRN, USRN and UDPRN

Other unique identifiers are also present in the OS NGD, including the UPRN (Unique Property Reference Number), USRN (Unique Street Reference Number) and UDPRN (Unique Delivery Point Reference Number); these remain the unique identifiers in our data to represent Local Authority Address, Local Authority Street and Royal Mail delivery point address records, respectively. (A UDPRN is a unique and persistent identifier that Royal Mail assigns to identify a specific delivery point, for example, a mailbox or business unit.)

TOID

The Topographic Identifier (TOID) is also present in the OS NGD, but in most instances, this is an optional attribute and therefore should not be relied upon to complete data linking or for implementing COUs (Change-Only Updates). The reason for this identifier being optional is the improved currency on which the OS NGD will be 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.

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 .

Requirements

• ArcMap (version 10.2.2 or later)

• A GeoPackage dataset

Instructions

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

What is OS NGD API – Features?

With OS NGD API – Features, you can filter by attribute, location and / or time to create your own customised data selections. Based on the latest OGC API – Features standard, this API can help accelerate your time-to-value by making it easier to build awesome things with our trusted geospatial data. You can use it to reduce your data management overheads, automate your workflows, and innovate at pace.

Things to remember for OS NGD API – Features

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:

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 .

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

Accessing OS NGD data with OS NGD API – Tiles via web mapping libraries

The following sub-sections provide step-by-step instructions on how to access OS NGD data via OS NGD API – Tiles in various web mapping libraries:

• Leaflet

What is GeoPackage?

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

Requirements

• ArcGIS Pro (version 1.1 or later)

• A GeoPackage dataset

The Cadcorp Spatial Information System® (Cadcorp SIS®) is an integrated family of geospatial products comprising desktop, web, and developer applications.

Cadcorp SIS Desktop connects directly to the OS Data Hub through dedicated wizards.

What you need

• Cadcorp SIS (version SIS 9 or later).

What is OS NGD API – Tiles?

OS NGD API – Tiles offers you a vector tile service powered by the OS NGD. It provides a detailed and customisable basemap that's based on the latest to help you create stunning and interactive web maps. It can be used with most web mapping libraries, including OpenLayers, MapLibre GL JS and Leaflet. The major benefit of vector tiles is that they are optimised for use across the internet and are therefore great for building interactive web maps that allow users to zoom, pan, rotate, tilt and more.

You have a choice between using Ordnance Survey styles or creating your own. You can customise the content and style to create a professional-looking map that perfectly meets your needs, matches your branding, and pleases your customers.

OS NGD API – Tiles is available in two projections: British National Grid for Great Britain (GB) data and Web Mercator, a global coordinate system.

The Cadcorp Spatial Information System® (Cadcorp SIS®) is an integrated family of geospatial products comprising desktop, web, and developer applications.

Cadcorp SIS Desktop connects directly to the OS Data Hub through dedicated wizards.

What you need

• Cadcorp SIS (version SIS 9.1 or later).

OS NGD delivery roadmap up to Spring 2026

The OS NGD delivery roadmap can be seen in the following image; the roadmap details what was delivered in the Autumn 2025 data enhancements releases and what is planned for delivery in the upcoming Spring 2026 data enhancements release:

Recently delivered enhancements to the OS NGD are listed on the .

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 edit the content of an existing recipe (i.e. add or remove themes / feature types, or change attribute filtering or data schema versions) and you can edit the name or description of an existing recipe.

The following sub-sections on this page cover:

How do I edit the name of my recipe?

To edit a recipe's name:

How do I edit the description of my recipe?

To edit a recipe's description:

How do I edit a recipe?

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:

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:

How do I accept a recipe shared with me?

To accept a shared recipe:

How do I reject a recipe shared with me?

To reject a recipe shared with you:

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

Feature retention options

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

1. Latest feature view

2. Full feature archive

Latest feature view

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.

Change type

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.

Version dates

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

Full feature archive

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

API Reference

OS NGD API – Features technical specification provides an overview of the endpoints available, as well as the parameters that can be used with each endpoint. The technical specification is intended to be used by customers who want to integrate with the API. The service offers the following endpoints:

Use of CQL operators

The OS NGD API – Features supports a generic filter grammar called Common Query Language (CQL) for specifying enhanced filter criteria to return a subset of features. CQL is written using a familiar text-based syntax, making it more readable and better-suited for creating complex filters.

The following table documents the supported operators:

ESRI ArcGIS Pro is a desktop geographic information system (GIS) application that allows users to maintain, visualise and analyse spatial data.

The instructions that follow demonstrate how to connect to OS NGD API – Features using ESRI ArcGIS Pro.

What you'll need

• ESRI ArcGIS Pro (version 3.4.0 or later).

• A preloaded base map, for example, or .

• OS NGD API – Features added to an API project in the OS Data Hub with an API Key. See for more information.

Instructions

QGIS is an open GIS (Geospatial Information System) desktop application that allows you to display, interrogate, visualise and create geospatial information including from geo-centric APIs (for example, a WFS).

The instructions that follow demonstrate how to connect to OS NGD API – Features using QGIS.

What you need

• QGIS (version 3.12.0 or later).

• A preloaded basemap, for example, or .

• OS NGD API – Features added to an API project in the OS Data Hub with an API Key. See for more information.

Instructions

This ‘how-to’ guide will show you how to create your own style for OS NGD API – Tiles which you can then use in web maps and GIS software.

To do this, we recommend using the open source visual editor, Maputnik.

What's next?

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 ) and select how you want to download your data as a data package. OS Select+Build is available via the .

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.

Requirements

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 .

This example will provide an introduction on how to use OS NGD API – Features to extract and plot OS NGD data! We’ll be using , a library that builds on Pandas to help manage and analyse spatial data.

What you'll need

• OS NGD API – Features added to an API project in the OS Data Hub with an API Key. See for more information.

QGIS is an open GIS (Geospatial Information System) desktop application that allows you to display, interrogate, visualise and create geospatial information including from geo-centric APIs (for example, a Vector Tiles Service).

The instructions that follow demonstrate how to connect to OS NGD API – Tiles using QGIS.

What you'll need

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:

How has data schema versioning been implemented?

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.

• 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 list versioning

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

Worked example

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.

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

Annual Full Supply orders and data schema versioning

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 2025 OS NGD data enhancements release contained 3 new feature types (Building Access Location, Crowd Sourced Name Point, and Street Light), and 11 new data schema versions (Building v4.0, Building Part v2.1, Land v3.1, Path Link v2.0, Rail v3.1, Road Link v4.0, Road Track Or Path v3.1, Site v2.2, Site Access Location v2.0, Structure v3.1, and Water v3.1). The data for the new feature types and the new data schema versions will not be part of Annual Full Supply orders until 01 January 2026.

For example, the Autumn 2025 OS NGD data enhancements releases contained 6 new feature types (Royal Mail Address, Royal Mail Address, Bus Lane, Cycle Lane, Tidal Boundary Continuous High and Tidal Boundary Continuous Low), and 14 new data schema versions for existing feature types (Built Address v3.0, Built Address v3.0, Historic Address v3.0, Historic Address v3.0, Land v3.2, Non-Addressable Object v3.0, Non-Addressable Object v3.0, Path Link v3.0, Pre-Build Address v3.0, Pre-Build Address v3.0, Road Link v5.0, Site v1.3 and 2.4, and Water Link v2.0) and 3 new data schema versions for existing addressing related components (Alternate Address v3.0, Other Classification v3.0 and Related Entity v3.0). The data for the new feature types and the new data schema versions will not be part of Annual Full Supply orders until 01 January 2026.

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.

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:

The OS NGD 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 NGD 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), with the ability to use PAF’s Unique Delivery Point Reference Number (UDPRN) alongside the Unique Property Reference Number (UPRN).

• Create mail shots using the Royal Mail address.

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

Key elements

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

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

Coverage

Great Britain.

Default coordinate reference system

British National Grid (EPSG: 27700).

Temporal filtering

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.

Supply formats

GeoPackage or CSV (comma-separated values).

Supply mechanism

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.

Using our data

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

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:

is a free and open-source JavaScript library for displaying interactive maps on the web. It is a powerful tool that can be used to create a wide variety of map-based applications, from simple web maps to complex GIS applications.

OpenLayers is easy to use and can be integrated with a variety of other web development frameworks.

What you'll need

What is a tile matrix set?

A tile matrix set is a standardised way to divide the coverage of the service into a regularly spaced grid system made up of tiles (512x512 pixels).

By defining the tile matrix set for each coordinate reference system, we can ensure interoperability across different software, achieve accurate positioning with consistent behaviour, and improve performance.

🖥️ Webinars

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.

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

• Local Authority addresses

Overview of the OS NGD data structure

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: