Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
The following Core Principle pages provide an overview of the OS National Geographic Database (NGD). They cover the core elements of its design, including the format of data you can access, the coordinate reference systems used, and how Change-Only Updates (COUs) will be provided, amongst other topics.
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.
The key benefits of the OS National Geographic Database (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.
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 a brand new 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 been enriched with 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.
The launch of the OS NGD 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. 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 National Geographic Database (NGD) contains authoritative data that describes the geography of Great Britain. It delivers improved data structures, increased currency of data supply and enhanced metadata. OS NGD data can be accessed through the OS Data Hub via the download service, OS Select+Build, and two APIs: OS NGD API – Features and OS NGD API – Tiles.
OS Select+Build and the OS NGD APIs are available to Public Sector Geospatial Agreement (PSGA) Members and OS Partners. To get access to the OS NGD you must first log into the OS Data Hub. The OS NGD will be accessible via both the Premium Plan and Public Sector Plan on the OS Data Hub.
OS NGD data has been categorised to make it easier for you to discover the data you need:
The data is structured into nine themes of related items: Address, Administrative and Statistical Units, Buildings, Geographical Names, Land, Land Use, Structures, Transport, and Water.
Each theme is made up of one or more collections, which in turn have feature types.
Feature types are the most granular level, with objects grouped by geometry or classification.
This platform is where you will find documentation to help you get started using OS NGD data via OS Select+Build and the OS NGD APIs. Using the navigation panel on the left-hand-side of the screen, you can select and view pages of interest, including OS NGD core principles, getting started information and guides for using OS Select+Build and the APIs, key benefits to customers, FAQs, and detailed information about the data structure and code lists.
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.
It is plug and play with most databases.
The ability to quickly load large datasets using COPY method rather than INSERT.
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.
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.
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.
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 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 NGD 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:
Attribute type | Quotes (Y/N) | If NULL | Example |
---|---|---|---|
Theme | Theme short code | Collection | Collection short code |
---|---|---|---|
Integer
N
"
123
Real
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
Buildings
bld
Building Features
fts
Water
wtr
Water Features
fts
Water Network
ntwk
Land
lnd
Land Features
fts
Structures
str
Structure Features
fts
Transport
trn
Transport Features
fts
Transport Network
ntwk
RAMI
rami
Administrative and Statistical Units
asu
Boundaries
bdy
Address
add
GB Address
gb
Islands Address
isl
Geographical Names
gnm
Named Features
fts
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.
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.
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.
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.
The OS NGD will primarily use a new identifier called the OSID (OS Identifier) to uniquely identify features. The OSID will be used persistently and will allow the unique identification of records in the OS NGD. It should be noted that the OSID will not be unique across the OS NGD, but rather 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 Features Theme.
Other unique identifiers are also present in the OS NGD. These include the UPRN (Unique Property Reference Number) and USRN (Unique Street Reference Number). These will remain the unique identifiers in our data to represent Address and Local Authority Street records respectively.
The TOID (Topographic Identifier) 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. 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.
1: There must be a value.
2: There must be two values.
n: There may be one or more values.
0: Population is optional.
These values may be used in combination.
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 'Data schema versioning' page.
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 or the new 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.
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 NGD Water Features (topographic data) and OS NGD 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 data you receive will be provided at a feature type level.
The OS NGD is available via the OS Data Hub on either the Premium Plan or Public Sector Plan. 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.
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.
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).
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 version 1.0 and 2.0:
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.
As new enhancements are made to a given feature type in the OS NGD which require the schema to be uplifted (for example, data schema version 2.0 being created), the new data schema version will become available via the OS NGD access services (i.e. OS Select+Build and the OS NGD APIs). This new data schema version will become known as the 'latest', with the previous data schema version becoming known as being in 'maintenance'.
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.
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. You can choose from data schema versions which are in the 'latest' or 'maintenance' states.
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.
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.
In the worked example below, we demonstrate how a feature type has new 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 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 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 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 therefore moves into 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.
The following video from the Geospatial Commission Public Sector Contracts Annual Conference in October 2022 gives a high-level introduction to the OS NGD, including what data is available, how to access the data, the support available, the benefits, and the roadmap for product enhancements:
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:
Find out how customers across numerous sectors are using and benefiting from OS NGD data:
Discover how North Yorkshire Fire & Rescue Service used OS Select+Build to reduce data analysis timeframes.
Discover how to determine pavement widths in OS NGD data.
Find out more about how the new speed datasets make it easier to analyse travel times, enhance routing analytics and provide accurate insight for safety and infrastructure policy decisions.
Sample data is available for the following OS NGD collections:
Sample data for the collections is available in GeoPackage and CSV (comma-separated values) formats.
One zip file of sample data is provided per OS NGD collection. Within each of these zip files, the individual feature types for each collection are separated into their own folder.
The sample data for each OS NGD collection covers three 10km by 10km areas in Great Britain: Exeter (England), Newport (Wales), and Inverness (Scotland). The exception to this is the OS NGD Boundaries Collection sample data which provides national coverage for Great Britain.
Please note that sample data is not available for the OS NGD Islands Address Collection.
Sample data always use the latest data schema version available for each collection.
Please note that as we are publishing three 10km x 10km sample data areas for most of the OS NGD collections, a small number of feature types are not represented within these areas and therefore their record counts will be zero:
Landform Point (Land Features Collection)
Maintenance Point (RAMI Collection)
Railway Link Set (Transport Network Collection)
If you are a (Public Sector Geospatial Agreement) PSGA Member and you'd like to know more about how to get the most out of OS NGD data, head to the and take a look at our OS NGD Lightning Talks. The talks are presented by OS Technical Consultants who introduce the OS NGD data themes and show you what can be achieved using OS NGD data and how. New Lightening Talks are added to the PSGA Members area periodically.
The OS NGD Lightning Talks will soon be available to OS Partners on the .
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 the PSGA Members area and Partner Portal periodically.
OS National Geographic Database (NGD) sample data is available to download from the .
OS NGD collection | Available formats | Sample data coverage |
---|
GB Address | GeoPackage, CSV | Three 10km x 10km areas |
Boundaries | GeoPackage, CSV | National coverage for Great Britain |
GeoPackage, CSV | Three 10km x 10km areas |
GeoPackage, CSV | Three 10km x 10km areas |
Land Use Features | GeoPackage, CSV | Three 10km x 10km areas |
GeoPackage, CSV | Three 10km x 10km areas |
Routing and Asset Management Information (RAMI) | GeoPackage, CSV | Three 10km x 10km areas |
GeoPackage, CSV | Three 10km x 10km areas |
GeoPackage, CSV | Three 10km x 10km areas |
GeoPackage, CSV | Three 10km x 10km areas |
GeoPackage, CSV | Three 10km x 10km areas |
Water Network | GeoPackage, CSV | Three 10km x 10km areas |
As we release new enhancements into the OS NGD, we will update this page to provide you with a high-level summary of what's launched.
Buildings
Building Age. The age of the main building in a site, created using Verisk data and OS data.
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.
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.
Structures – Field Boundary
New Field Boundary feature type added to Structures Feature 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.
Transport
Tram track attribution indicating the presence of tram tracks on a road. Supplied as new attribution against Road Link features.
New 'Tram on Road' feature type to locate where trams are present against the OS Road network.
Geographical Names
New feature type ‘Named Road Junction’ which provides enhanced names and numbers of junctions. Includes both officially named or numbered junctions and intersects without an official name or number.
Buildings
New Building Feature Type added to Building Features Collection.
Attribution provided on the building's use, how it is connected to other buildings, additional details on addresses contained within the building, and whether a building is considered the main one within a site.
Cross references between the new Building feature type and the Building Part, Site, and Built Address feature types.
Transport
New rail feature types added to the Transport Network Collection, giving information about topologically connected rail network:
Available rail network attribution includes track representation (single / multitrack, siding), and use (freight / passenger / mixed).
New Pavement Link Feature Type added to the Transport Network Collection, giving information on presence of pavements on Road Network.
New attribution added to Road Link Feature Type, giving details about the pavement presence: left or right side of road, coverage, and minimum and average width.
Transport
For the first time we are extending the coverage of our Path network to all of Great Britain and topologically structuring our road and path networks together. This means there will be many more features present in our Path feature types (Path, Path Link, Path Node, Connecting Link, and Connecting Node), and you will now get Path data for all areas of Great Britain (not just urban areas which was our previous offering).
Launch of the new vector tiles API: OS NGD API – Tiles.
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 (see the Addressing 'Versioning information' page for more information).
Improvements made to address data regarding the consistency of address positioning, usage classifications, business names and lifecycle.
Transport
New Average and Indicative Speed Feature Type added to the OS NGD 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 Water Features Collection:
Option to select which data schema version you want to access for certain address feature types (see the Addressing 'Versioning information' page and the 'Data schema versioning' page for more information).
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.
The OS NGD delivery roadmap (as of May 2023) can be seen in the image below. It details what was delivered in the September 2022 and March 2023 data releases, and what is planned for delivery in the upcoming September 2023 and March 2024 data releases.
In the future, we plan to deliver over 60 data enhancements to the OS NGD. As we design and develop these data enhancements, more details will be added to the 'Future OS NGD Data Enhancements' page.
Building Features
Land Features
Named Features
Structure Features
Transport Features
Transport Network
Water Features
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.
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 140 TB, 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 (ESPG: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.
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.
Accessing GeoPackage data via ArcGIS Pro
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.
These instructions were created using ArcGIS Pro version 2.5, but versions from 1.1 onwards will support GeoPackage.
Start ArcGIS Pro, then 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.
In the ribbon at the top of the project, select Map > Add Data.
A dialog box will appear. 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.
The layers can be selected either individually or together. Once the relevant layers have been selected, click OK. The selected layers will then be added into ArcGIS Pro.
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.
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.
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
Accessing GeoPackage data via CadCorp
CadCorp SIS (version SIS 9 or later)
A GeoPackage dataset
These instructions were created using CadCorp SIS 9 Desktop Express; however all versions of CadCorp SIS 9 or later support GeoPackage.
Start CadCorp SIS.
In the upper ribbon, select Add Overlay.
A dialog box will appear. Select Files > File.
From here, another dialog box appears where you can map to where the GeoPackage has been stored locally.
Once the correct GeoPackage has been located, click Finish.
The data should now appear on the map.
OS Select+Build is our download service that gives you access to OS National Geographic Database (NGD) data. You can use it to choose and download the OS NGD data you need (by theme, collection and feature type) and select how you want to receive your data.
For the first time, you can select and build only the data you require rather than taking off-the shelf OS products. For example, if you're only interested in buildings information, then you just select the OS NGD Buildings Theme and the content you require within that theme. There's no need to take a whole product and spend time filtering out the data you need from it.
You can also take data from different OS NGD collections. For example, you could select the Building Line and Building Part Feature Types (which are both in the Building Features Collection of the Buildings Theme) and the Structure Line Feature Type (which is in the Structure Features Collection of the Structures Theme).
The screenshot below 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.
There are two different file formats options available when you download OS NGD data from OS Select+Build: GeoPackage and CSV. Various supply options are available.
OS Select+Build is available via the OS Data Hub.
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 NGD 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.
Before you create a data package to receive your OS NGD data, you'll need to create a recipe.
To create a new recipe:
Log into your OS Data Hub account.
Select Download from the main menu.
Choose OS Select+Build from the secondary navigation menu.
Click the Create a new recipe button.
Add the following details to your recipe under Create your recipe in the secondary navigation menu:
Give your recipe a name.
Add a description for your recipe.
Select your OS NGD data by choosing the themes, collections and feature types you want to include in your recipe.
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.
Add filters to the feature types, if needed.
Click the Create recipe button.
Your new recipe will now instantly be available in your OS Select+Build Recipe Library.
Please note:
We recommend defining a naming convention for your organisation before creating OS NGD recipes and / or data packages.
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 by default. See the 'Data schema versioning' page for more information.
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.
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:
Log into your OS Data Hub account.
Select Download from the main menu.
Choose OS Select+Build 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:
Log into your OS Data Hub account.
Select Download from the main menu.
Choose OS Select+Build from the secondary navigation menu.
In your OS NGD Select+Build Recipe Library, scroll or search for the recipe you would like to find out more about.
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.
To see what OS NGD themes, collections and feature types are in a recipe, follow the steps above to find a recipe in your OS Select+Build Recipe Library, then:
Click on the name of the recipe you would like to find out more about.
You are now within the Recipe details screen, where you can view detailed 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
A recipe can be shared with another organisation to enable collaboration.
To share a recipe:
Log into your OS Data Hub account.
Select Download from the main menu.
Choose OS Select+Build from the secondary navigation menu.
In your organisation's OS Select+Build Recipe Library, scroll or search for the recipe you want to share.
Click on the name of the recipe to view the recipe details.
In this view, you will be able to see the Share recipe button; please note that you can only share recipes created by your organisation.
Click the Share recipe button.
The share recipe dialog will appear.
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.
Add a message for the organisation receiving the recipe to provide them with context around why you are sharing the recipe with them.
Click Send.
To accept a shared recipe:
Log into your OS Data Hub 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.
Click the bell button.
You will then 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.
Click View recipe details.
The recipe details will be displayed for you to review. If you are happy with 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.
To reject a shared recipe:
Log into your OS Data Hub 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.
Click the bell button.
You will then 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.
Click View recipe details.
The recipe details will be displayed for you to review. 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.
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:
Log into your OS Data Hub account.
Select Download from the main menu.
Choose OS Select+Build from the secondary navigation menu.
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.
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.
Select the desired coordinate reference system.
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.
Click the Create data package button.
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.
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.
Please note that the Annual Full Supply order frequency option will not be available for the the three new feature types released in March 2023 (River Basin District Catchment, Waterbody Catchment, and Average and Indicative Speed Feature Types) or the data schema version 2.0 addressing feature types until 01 January 2023. If you select this order frequency for a data package containing one (or more) of the three new feature types or the data schema version 2.0 addressing feature types before 01 January 2023, then you will receive blank files.
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:
Log into your OS Data Hub account.
Select Download from the main menu.
Choose Data packages from the secondary navigation menu.
You will be then taken to your Data packages list.
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.
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:
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.
This is also known as a manifest file, a computing file which contains metadata. We provide an Order Summary file for each feature type in your data package. The following file naming convention will be applied to each Order Summary file you receive:
collection_featuretype_orderSummary.jso
For example, the file name for the Building Part Feature Type Order Summary file would look like this:
bld_fts_buildingpart_orderSummary.jso
The example below shows the information a Order Summary file contains:
You can:
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.
You can't:
Delete a recipe.
Edit a recipe once it's been created.
Download the contents of an OS NGD data package using the grouped file function.
Future OS Select+Build enhancements being considered:
The ability to edit a recipe.
The option to delete a recipe.
Accessing GeoPackage data via MapInfo Professional
MapInfo Professional (version 15.2 or later)
A GeoPackage dataset
These instructions were completed using MapInfo Professional version 2019; however, any version from 15.2 onwards can be used.
Start MapInfo Professional.
Select Open > Table in the top ribbon.
A dialog box will appear where you can search for the appropriate GeoPackage. Once located, select the GeoPackage and click Open.
Another dialog box will appear. Here, it is possible to select which layers to import into MapInfo Professional from the GeoPackage.
Once the layers have been selected, click OK.
The data should now be available in your workspace.
Using GDAL to load a GeoPackage into a database
GDAL is a translator library for raster and vector geospatial data formats that is released under an X/MIT style Open Source License by the Open Source Geospatial Foundation. 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 PostgreSQL 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 PostgreSQL database with PostGIS extension enabled
GDAL version 1.11.0 or above (with access to a command line interface to use it)
A GeoPackage dataset
You can interrogate a GeoPackage dataset using the ogrinfo program which lists information about it. At a basic level it will return the layers contained within it:
ogrinfo
<PATH_TO_GEOPACKAGE>
Using the ‘Summary Only’ (-so
) and ‘List all features of all layers’ (-al
) arguments you can view summary information about all the layers within the GeoPackage, including projection, schema, feature count and extents:
ogrinfo
<PATH_TO_GEOPACKAGE>
-so -al
The GeoPackage can be loaded into a PostgreSQL database using the ogr2ogr program, the 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=
<PORTNUMBER>
active_schema=
<TARGETSCHEMA>
"
<PATHTOGEOPACKAGE>
<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.
Will create two tables in the example_schema
schema:
Different loading options (including renaming tables, reprojecting the data, etc.) can be found on the PostgreSQL / PostGIS — GDAL documentation page.
Accessing GeoPackage data via QGIS
QGIS (version 2.10.1 or later)
A GeoPackage dataset
These instructions were created using QGIS version 3.22. Other versions of QGIS can be used, from version 2.10.1 onwards.
Open a new or existing QGIS project.
On the top ribbon of the workspace, add a layer by selecting Layer > Add Layer > Add Vector Layer.
The Data Source Manager - Vector dialog box will appear. Here, it is possible to select the GeoPackage that will be loaded using the three dots button located next to the Vector Dataset(s) box. Click the three dots button.
Navigate to the GeoPackage. Double-click the file or select it, then click Add.
A separate dialog box will appear. Here, the layers of the GeoPackage can be selected and added to a map. It is possible to add selected layers, numerous layers or all layers.
Once the relevant layers have been selected, click OK.
The GeoPackage layers should now be viewable in the layers list on the left-hand side of the workspace.
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 OS NGD Resources GitHub repository.
These instructions are based on PostgreSQL version 14, but should work for all supported versions. The instructions assume that you have set-up your database with the PostGIS 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 COPY command:
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.
These instructions are based on Microsoft SQL Server 2019, but should work for all supported versions.
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:
It is not possible to BULK INSERT
the geometries directly in their Well-Known Text (WKT) format.
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.
The following pages provide an overview of the OS National Geographic Database (NGD) APIs and how you can access them. They cover the core elements of its design, including data available, a technical specification, and how to get started, amongst other topics.
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.
The APIs are self-documenting and allow you to easily discover what OS NGD data is available before using it. You can explore the various data collections for free to decide what best suits your needs. The data is ready to use in numerous applications (desktop, web, and mobile), enabling you to power your applications with rich, consistent and current information about the real world.
The OS NGD APIs are available via the OS Data Hub.
Temporal filtering allows you to order a one-off snapshot of data from the OS National Geographic Database (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 'Downloading with OS Select+Build' page.
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.
Please note, 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.
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.
To create a new OS NGD data package and apply a temporal filter to it:
Log into your OS Data Hub account.
Select Download from the main menu.
Choose OS Select+Build from the secondary navigation menu.
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.
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.
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:
Select the supply date needed for the snapshot:
Click the Create data package button.
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.
Before you can access the OS NGD APIs, you will need to add one of them to a new or an existing project in the OS Data Hub and generate an API key.
To do this:
Log into your OS Data Hub account.
Select API Dashboard from the main menu (you must be signed into the OS Data Hub to view the contents of this tab).
Select APIs from the secondary navigation menu.
Select the Add to API project button of the API you want to add.
If you already have a project, you may want to add OS NGD API – Features or OS NGD API – Tiles into that existing project. Alternatively, if you want to add one of the NGD APIs to a new project, you should select Add to NEW PROJECT from the drop-down menu. If creating a new project, enter the project name.
The next screen will contain the project API key and the API endpoint address (API URL).
You can return to this screen by clicking My projects from the secondary navigation menu at any point in the future if you need to copy your API key or the API endpoint address, or if you need to regenerate your API key.
You can freely explore OS NGD data without having an API key.
To find an API endpoint address:
Log into your OS Data Hub account.
Select API Dashboard from the main menu (you must be signed into the OS Data Hub to view the contents of this tab).
Select My projects from the secondary navigation menu.
Select the project you're interested in.
Your API endpoint address will be displayed in the project information under the OS NGD API that has been added to the project.
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 National Geographic Database (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 Downloading with OS Select+Build page has step-by-step instructions on how to create a new recipe.)
Attribute filtering is an optional step for those with advanced OS data knowledge.
You cannot apply attribute filters to feature types in existing recipes held in your OS Select+Build Recipe Library; they can only be added to new recipes during the recipe creation stage.
The following sub-sections give step-by-step instructions on how to add attribute filters to a new recipe and provide worked examples of creating both simple and nested filters.
To add attribute filters to a new recipe:
Log into your OS Data Hub account.
Select Download from the main menu.
Choose OS Select+Build from the secondary navigation menu.
Click the Create a new recipe button, adding the relevant details to your recipe (see the Downloading with OS Select+Build page for more information on creating recipes).
The Advanced Filter Options panel will slide into view from the right, where you can begin to build your filter(s):
For a simple filter, select +Add rule.
For a more complex nested filter, select +Add group.
Once you have added all of your relevant filters, click Apply Filter.
Click the Create recipe button.
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 Building Features Collection. Our aim is to build a filter to select buildings where education is recorded as the land use.
To do this:
Log into your OS Data Hub account.
Select Download from the main menu.
Choose OS Select+Build from the secondary navigation menu.
Click the Create a new recipe button.
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.
The Advanced Filter Options panel will slide into view from the right, where you can begin to build your filter(s).
We are going to build a filter where the OS Land Use Tier A attribute is set to Education.
In the Advanced Filter Options panel, click + Add rule, 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.
Click Apply filter.
Click the Create recipe button.
Your filter will return buildings where education (Education) is recorded as the land use (OS Land Use Tier A attribute).
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 15 metres 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.
To do this:
Follow the steps outlined above for creating a simple filter for Building Part until you reach the Advanced Filter Options panel step.
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.
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.
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.
Click Apply filter.
Click the Create recipe button.
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).
To check what filters have been applied to feature types in an existing recipe:
Log into your OS Data Hub account.
Select Download from the main menu.
Choose OS Select+Build from the secondary navigation menu.
In your OS NGD Select+Build Recipe Library, scroll or search for the recipe you would like to find out more about.
Click on the name of the recipe you would like to find out more about.
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.
Click the filter icon next to the feature type(s) you want to add a filter to in the theme selection tree.
Click on the filter icon to the right of Building Part.
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. Click into each endpoint to learn more.
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:
Operator Type | Supported Operators |
---|---|
Comparison
EQUAL TO [ = ]
, LESS THAN [ < ]
, LESS THAN OR EQUAL TO [ <= ]
, GREATER THAN [ > ]
, GREATER THAN OR EQUAL TO [ >= ]
, ISNULL
, LIKE
, IN
, BETWEEN
Logical
AND
, OR
, NOT [ <> ]
Array
AEQUALS
, ACONTAINS
, ACONTAINEDBY
, AOVERLAPS
Spatial
INTERSECTS
The following table documents the OS NGD datasets available through the OS NGD API – Features showing the themes, collections and lists the available feature types.
OS NGD themes and collections have been created to group similar geographic entities and data types, making it quicker and easier to identify the data you need. The OGC API - Features standard also references feature collections, and in the context of OS NGD datasets, this is equivalent to feature types.
The following naming convention has been applied to the feature collections: theme-collection-featuretype-version. Short codes have been used for both the theme and collection to keep the feature collection names manageable and not overly long. An example of the short codes used is below:
bld-fts-buildingline-1
Click on the theme to find out more information about the dataset.
Find out more about the hierarchy of OS NGD data here.
A collection in OS NGD API - Features references OS NGD Feature Type grouping. Feature types have their own data model and specifications which are not commonly shared with other feature types.
GET
a list of all OS NGD Collections by using the below endpoint:
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.
You can:
Request specific features using location, attribute, and / or time queries.
Interrogate highly detailed feature information.
Freely discover what OS NGD data collections are available.
Explore the OS NGD data schemas and queryables.
Request data in GeoJSON format.
Visualise Ordnance Survey data and apply your own styling.
You can't:
Create a scalable map of Great Britain across zoom levels.
Request more than 100 features in a single transaction.
Access data from:
OS NGD Address theme,
OS NGD Administrative and Statistical Units Theme,
Waterbody Catchment and River Basin District Catchment Feature Types (of the Water Features Collection in the OS NGD Water Theme).
Theme | Collection | Feature Type(s) |
---|---|---|
Building Features
Building, Building Line, Building Part
Named Features
Named Area, Named Point
Land Features
Land, Land Point, Landform, Landform Line, Landform Point
Land Use Features
Site, Site Access Location, Site Routing Point
Structure Features
Compound Structure, Structure, Structure Line, Structure Point
Transport Features
Cartographic Rail Detail, Rail, Road Line, Road Track or Path
Transport Network
Connecting Link, Connecting Node, Ferry Link, Ferry Node, Ferry Terminal, Path, Path Link, Path Node, Pavement Link, Railway Link, Railway Link Set, Railway Node, Road, Road Junction, Road Link, Road Node, Street
RAMI
Average and Indicative Speed, Highway Dedication, Maintenance Area, Maintenance Line, Maintenance Point, Reinstatement Area, Reinstatement Line, Reinstatement Point, Restriction, Routing Hazard, Routing Structure, Special Designation Area, Special Designation Line, Special Designation Point
Water Features
Inter Tidal Line, Tidal Boundary, Water, Water Point
Water Network
Water Link, Water Link Set, Water Node
Increased data update frequency
You can access NGD themes of data which are updated up to daily.
Rich attribution
Access OS NGD data that has been enriched with attribution to ensure that it's straightforward to navigate and query.
New, easier ways to access data
OS NGD API – Features give you direct, online access to the OS NGD & schemas using the latest OGC API – Features standard .
Choose exactly what data you take
Access the OS NGD Feature Type you need rather than pre-selected OS products and filter only what is important to you.
Accessing OS NGD data with OS NGD API - Features via QGIS
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).
QGIS (version 3.12.0 or later)
Open a blank document in QGIS. Uncheck the "Render" box for now.
Navigate to Layer → Add Layer → Add WFS Layer...
The following window will be displayed:
If you have connected to a WFS / OGC API - Features before, you will have the options available in the drop down immediately under the layers tab. If you've connected to OS NGD API – Features before, select the layer in the drop-down menu and click Connect.
If you have NOT called WFS / OGC API - Features before, click the New button below the drop-down menu.
The window that pops up requires the API information you obtained in the OS Data Hub.
Provide the service details of the API as follows:
Provide a name for the API. It is good practice to name your connections in a way that makes them instantly recognisable.
Input the OS NGD API – Features URL in the URL box.
Your API Key that has been generated in the OS Data Hub and would have been automatically added to the URL.
Click the Detect button to identify the version.
As best practice we recommend that you limit your max number of features and page size to 100 to ensure a smooth service. Larger values may result in a very slow response.
You will not be required to put styling, zoom or coordinate information in the URL. This will be added at a later stage by the GIS application.
Leave all the other options blank and click OK.
It is worth noting that you will NOT require a User name or Password to use the service as all authentication is done through your OS NGD API – Features key.
Once you've completed the initial connection, the details you have supplied will be saved by your QGIS application and it can be used with any of your new or existing geospatial projects.
The next step is to select the Server connection in the drop-down list and click Connect.
You will be presented with a list of features. Click on the ones you want to apply. To select more than one feature, use the Ctrl key when choosing.
Depending on what you're attempting to do, you could either choose all layers or individual layers with features of specific interest. This can then be combined with back-drop mapping for visualisation, interrogation and analytical purposes.
It is best practice to load only the feature/s which you are interested in. In order to engage the bounding box, ensure you tick the option to Only request features overlapping the view extent. In other words, only selected features within the viewing window will load, not everything. Your viewing window in your GIS application sets your bbox.
Select the appropriate layer/s and click Add. This could take several minutes depending on which features you choose to apply.
Your data will be presented at a GB-wide scale (1:4,400,000 scale).
Please be aware that each feature, regardless of its layer, will count towards the request restriction and so the more types of features you call, the longer it will take to load into the GIS.
You can now tick the feature layer checkbox in the layers panel as well as the Render checkbox and use the data as intended. QGIS will automatically stop calling features should you need to zoom out and reposition your bounding box area of interest.
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.
Accessing OS NGD API - Features via Leaflet
Leaflet is an open-source JavaScript library for displaying interactive maps on the web or mobile. A simple and lightweight library that will enable you to display and visualise location data and build dynamic applications.
OS Maps API and OS NGD API - Features added to an API project in the OS Data Hub with an API Key.
A text editor like Visual Studio Code or Notepad to edit and save your HTML and JavaScript files
Create a new HTML file with a text editor (e.g. Notepad, Visual Studio Code)
Add the basic HTML structure to your file with a placeholder <div>
for the map.
To enable access to OS APIs an API key is required. Inside the <script>
tag, add a variable called apiKey
, replacing 'INSERT_API_KEY_HERE'
with the API key from your project.
Add a variable called collectionID
, replacing 'INSERT_COLLECTIONID_HERE'
with the collection ID for the desired NGD Feature Type and version (e.g. bld-fts-buildingpart-1).
Define the configuration options for the map, defining minZoom
, maxZoom
, center
, zoom
, maxBounds
, attributionControl
.
minZoom
and maxZoom
: Sets the minimum and maximum zoom level for the map. Users will not be able to go beyond these levels.
center
: Sets the initial center point of the map.
zoom
: Sets the initial zoom level of the map.
maxBounds
: Defines the maximum bounds and restricts panning the map.
style
: Defines the style of the map, configured via a URL pointing at the style specified.
attributionControl
: When set to 'false', it hides the attribution control which displays map credits.
Initialize the map with the id
of the <div>
element and the configuration option defined in mapOptions
.
Using the 'L.tileLayer
' method, specify the basemap layer for OS Maps API, which includes your API Key to load the tiles to your map.
Create a function called fetchFeatures
that fetches the API based on the current map extent (bounding box) by generating a bbox string.
Construct the API request URL to fetch OS NGD data from the OS NGD API - Features. The URL includes the collectionId
, bbox
and apiKey
.
Once the features have been returned in JSON, update the source data of the map's layers to display the features.
Inside the map.on('moveend',...)
event handler fetches and updates the features based on the map's current extent.
Features within the viewport extent will load initially (first 100 features) and continue to load as you pan and zoom across the map.
Congratulations! You've successfully created a map using Leaflet and added an NGD layer using the OS NGD API - Features in a few steps. Continue to explore Ordnance Survey's code examples to learn more about advanced features and functionality such as adding markers, pop-ups, and additional layers.
The following pages provide an overview of how to get started using the OS NGD API - Features. They cover the core elements to get started in the most common GIS software and web mapping libraries.
These pages should be used in conjunction with the more detailed pages within the Data Structure section and Technical Specification.
Accessing OS NGD data with OS NGD API - Features via Cadcorp SIS
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 Ordnance Survey Data Hub through dedicated wizards.
The instructions that follow demonstrate how to connect to the OS NGD API – Features using Cadcorp SIS Desktop version 9.1.1668.
Cadcorp SIS (version SIS 9 or later)
In Cadcorp SIS Desktop, open an existing map or create a new one.
In the Home tab, click Add Overlay.
In the Overlay Types dialog, select Ordnance Survey (GB) → OS (GB) Data Hub, and then click Next.
In the OS (GB) Data Hub dialog:
Select OS National Geographic Database (NGD) API – Features
Enter a valid API key.
Select Premium/Public Sector Plan, if you have this plan.
Select Save in the UI settings database (encrypted).
Click Next.
In the OS Data Hub NGD API – Features dialog:
Well-known ‘recipe’: Select a pre-defined recipe, if available.
Data Themes: Select your data themes in the left panel.
Features: The feature types available within the selected themes display in the right panel. Use the editing tools to delete feature types or to change the order in which they display in your SIS Workspace Definition (SWD).
Select either:
Local cache: To store the data temporarily on your machine. When you save the SWD and reopen it, the data will be fetched for a second time.
One-off import: To import the data. These imports have a larger file size, but the data is not queried for a second time when the file is reopened.
Set Filtering options: These settings are used in conjunction and define how much data is required for display. It is recommended that you always set a spatial filter and feature limit.
Spatial: The ‘Intersect with current view extent’ option limits the download to only selected features within the current window extent. You can also load features within a specific area of interest by using the polygon feature to draw your area of interest on the map BEFORE opening the Add Overlay dialog.
Maximum number of features: Limits the number of feature values downloaded to the number set. Note: This limit is applied per feature within any filtered spatial area.
Click Finish.
The selected themes and feature types display in the SWD.
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.
You can:
Use it as a basemap in GIS, web or mobile applications.
View the whole of Great Britain in unrivalled detail.
Seamlessly pan, zoom, pitch and tilt the map.
Overlay your own data on the basemap to give geographic context to your data.
Trace over OS NGD (Premium Data) detailed geometries.
Customise the map style and content to create the map you need.
Access maps in different projections: British National Grid and Web Mercator.
You can't:
Retrieve all the detailed attribution from OS NGD data.
Access data from the:
OS NGD Address Theme,
Routing and Asset Management Information (RAMI) Collection (of the OS NGD Transport Theme).
Accessing OS NGD data with OS NGD API - Features via OpenLayers
OpenLayers is easy to use and can be integrated with a variety of other web development frameworks.
OS Maps API and OS NGD API - Features added to an API project in the OS Data Hub with an API Key.
A text editor like Visual Studio Code or Notepad to edit and save your HTML and JavaScript files
Create a new HTML file with a text editor (e.g. Notepad, Visual Studio Code)
Add the basic HTML structure to your file with a placeholder <div>
for the map.
To enable access to OS APIs an API key is required. Inside the <script>
tag, add a variable called apiKey
, replacing 'INSERT_API_KEY_HERE'
with the API key from your project.
Add a variable called collectionId
, replacing 'INSERT_COLLECTIONID_HERE'
with the collection ID for the desired NGD Feature Type and version (e.g. bld-fts-buildingpart-1).
Create a source for the basemap layer using the OS Maps API and initialize the ol.map
class with the applicable map properties - target
, layers
and view
. Add the following code inside the JavaScript block:
The above code creates the main map instance using the OpenLayers library where you can specify various properties:
target
: Defines where the map should be displayed, in this instance it is set to the id
of the <div>
element.
layers
: An array containing the layers to be added to the map.
view
: Defines the initial view of the main, containing various settings such as projection, extent (the geographic bounds of the map), minimum and maximum zoom levels, centre of the map and the initial zoom level.
Define and initialize the source using the ol.source.Vector
class to make a request to OS NGD API Features. By utilising the ol.loadingstrategy.bbox
this means that data from the OS NGD API - Features will be loaded based on the visible map extent.
Create a separate layer to overlay OS NGD data onto the map, you will need to add the ngdFeatures
layers to the ol.map
object to render both layers on the map.
Features within the viewport extent will load initially (first 100 features) and continue to load as you pan across the map.
Accessing OS NGD API - Features via MapLibre GL JS
OS Maps API and OS NGD API - Features added to an API project in the OS Data Hub with an API Key.
A text editor like Visual Studio Code or Notepad to edit and save your HTML and JavaScript files
Create a new HTML file with a text editor (e.g. Notepad, Visual Studio Code)
Add the basic HTML structure to your file with a placeholder <div>
for the map.
To enable access to OS APIs an API key is required. Inside the <script>
tag, add a variable called apiKey
, replacing 'INSERT_API_KEY_HERE'
with the API key from your project.
Add a variable called collectionId
, replacing 'INSERT_COLLECTIONID_HERE'
with the collection ID for the desired NGD Feature Type and version (e.g. bld-fts-buildingpart-1).
To add the OS Maps API, you will need to define the map style using MapLibre GL JS's format. This specifies the source of map tiles, which will be retrieved from OS Maps API in the 'Light' raster tiles style.
Initialize the map object using the maplibregl.Map
class to configure the basemap layer and define its properties - container
, minZoom
, maxZoom
, maxBounds
, style
, center
and zoom
.
Add navigation controls to the map, excluding the compass button and disabling map rotation.
The above code creates the main map instance using the MapLibre GL JS library where you can specify various properties:
container
: Defines where the map should be displayed, in this instance it is set to the id
of the <div>
element.
minZoom
and maxZoom
: Sets the minimum and maximum zoom level for the map. Users will not be able to go beyond these levels.
maxBounds
: Defines the maximum bounds and restricts panning the map.
style
: Defines the style of the map, configured via a URL pointing at the style specified.
center
: Sets the initial center point of the map.
zoom
: Sets the initial zoom level of the map.
Create an empty GeoJSON placeholder to hold the feature objects called by the OS NGD API - Features.
Create a function called fetchFeatures
that fetches the API based on the current map extent (bounding box) by generating a bbox string.
Construct the API request URL to fetch OS NGD data from the OS NGD API - Features. The URL includes the collectionId
, bbox
and apiKey
.
Once the features have been returned in JSON, update the source data of the map's layers to display the features.
Event listeners are triggered when the map loads and finishes moving (panning or zooming) to load and update features based on the map's updated extent. Inside the map.on('load',...)
event handler, we add styles for various types of features, including polygons, linestrings and points so that any collectionId
specified will render.
Inside the map.on('moveend',...)
event handler fetches and updates the features based on the map's current extent.
Features within the viewport extent will load initially (first 100 features) and continue to load as you pan and zoom across the map.
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.
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.
Congratulations! You've successfully created a map using OpenLayers and added an OS NGD layer using the OS NGD API - Features in a few steps. Continue to explore Ordnance Survey's to learn more about advanced features and functionality such as adding markers, pop-ups, and additional layers.
is a free and powerful JavaScript library for displaying interactive maps on the web. It's based on Mapbox GL JS and provides a wide range pf features for creating maps with custom styles, markers and interactivity.
Congratulations! You've successfully created a map using MapLibre GL JS and added an OS NGD layer using the OS NGD API - Features in a few steps. Continue to explore Ordnance Survey's to learn more about advanced features and functionality such as adding markers, pop-ups, and additional layers.
Increased data update frequency
OS NGD API - Tiles is updated weekly ensuring you have access to the latest data as quickly as possible.
Beautifully styled basemap, ready to customise
Customise your maps to perfectly meet your needs. You have a choice between using Ordnance Survey styles or creating your own.
Interactive and flexible web maps
Control every aspect of your map with the flexibility to create dynamic interaction with the map and individual features.
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 GIS software and web mapping libraries.
These pages should be used in conjunction with the more detailed pages within the Data Structure section and Technical Specification.
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. Click into each endpoint to learn more.
The following sub-sections provide step-by-step instructions on how to access OS NGD API - Tiles in various GIS software packages.
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.
Accessing OS NGD API - Tiles via QGIS
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).
QGIS (version 3.22.0 or later)
Open a blank document in QGIS. Uncheck the "Render" box for now.
Navigate to Layer → Add Layer → Add Vector Tilers Layer...
The following window will be displayed:
Click the New button below the drop-down menu and select New Generic Connection
The window that pops up requires the API information you obtained in the OS Data Hub.
Provide the service details of the API as follows:
Provide a name for the API. It is good practice to name your connections in a way that makes them instantly recognisable.
In the URL box, input the OS NGD API - Tiles URL to retrieve tiles for your preferred collection.
Your API Key, which has been generated in the OS Data Hub.
Set the Min and Max Zoom Levels based on your preferred projection.
Web Mercator (EPSG: 3857): Min Zoom = 6, Max Zoom = 19
British National Grid (BNG: EPSG: 27700): Min Zoom = 0, Max Zoom = 15
In the Style URL box, input the OS NGD API - Tiles style URL to style the tiles based on the default style for the specified collection.
Leave all other options blank and click OK.
To retrieve tiles and style them appropriately, you will need two URLs. The URLs have slight variations based on the collection ID and projection. Here are some example URLs to retrieve the basemap (ngd-base) in Web Mercator (EPSG: 3857):
https://api.os.uk/maps/vector/ngd/ota/v1/collections/ngd-base/styles/3857?key={INSERT_YOUR_API_KEY}
Please note: You will need to replace the /{tileMatrix}/{tileRow}/{tileCol} used in the default 'retrieve tile' URL with /{z}/{y}/{x} to be able to connect to the OS NGD API - Tiles.
Click Add and Close in the Data Source Manager and you'll see the map displayed in the QGIS screen
To learn more about the available collections in OS NGD API - Tiles, you can view what data is available .
Accessing OS NGD API - Tiles via Leaflet
Leaflet is an open-source JavaScript library for displaying interactive maps on the web or mobile. A simple and lightweight library that will enable you to display and visualise location data and build dynamic applications.
OS NGD API - Tiles added to an API project in the OS Data Hub with an API Key.
A text editor like Visual Studio Code or Notepad to edit and save your HTML and JavaScript files
Create a new HTML file with a text editor (e.g. Notepad, Visual Studio Code).
Add the basic HTML structure to your file with a placeholder <div>
for the map.
To enable access to OS APIs an API key is required. Inside the <script>
tag, add a variable called apiKey
, replacing 'INSERT_API_KEY_HERE'
with the API key from your project.
Inside the <script>
tag, add another variable called collectionId
with the collection ID for the OS NGD API - Tiles base map - ngd-base
We need to intercept and customise the style request, adding a tiles property to provide a correctly formatted URL and authentication through the apiKey is enabled to ensure the correct tiles are requested.
Add the following code inside the Javascript block:
Initialize the map object using the L.Map
class to configure the vector tile layer and the mapOptions
variable to define its properties - minZoom
, maxZoom
, maxBounds
, center
and zoom
.
The above code creates the main map instance using the Leaflet library where you can specify various properties:
minZoom
and maxZoom
: Sets the minimum and maximum zoom level for the map. Users will not be able to go beyond these levels.
maxBounds
: Defines the maximum bounds and restricts panning the map.
center
: Sets the initial center point of the map.
zoom
: Sets the initial zoom level of the map.
Congratulations! You've successfully created a vector map using Leaflet using the OS NGD API - Tiles in a few steps. Continue to explore Ordnance Survey's code examples to learn more about advanced features and functionality such as adding markers, pop-ups, and additional layers.
These pages contain specific advice on how to make the most of the OS NGD Buildings data.
Technical articles covering a variety of topics to provide more in-depth examinations of using OS NGD data via OS Select+Build and the OS NGD APIs.
Use our custom stylesheets to easily visualise your chosen OS Select+Build dataset(s). Pick from one of two styles – contextual or analytical – available in QGIS, ArcMap, and SLD format.
Accessing OS NGD API - Tiles via OpenLayers
OpenLayers is easy to use and can be integrated with a variety of other web development frameworks.
OS NGD API - Tiles added to an API project in the OS Data Hub with an API Key.
A text editor like Visual Studio Code or Notepad to edit and save your HTML and JavaScript files
Create a new HTML file with a text editor (e.g. Notepad, Visual Studio Code)
Add the basic HTML structure to your file with a placeholder <div>
for the map.
To enable access to OS APIs an API key is required. Inside the <script>
tag, add a variable called apiKey
, replacing 'INSERT_API_KEY_HERE'
with the API key from your project.
Inside the <script>
tag, add another variable called collectionId
with the collection ID for the OS NGD API - Tiles base map - ngd-base
To correctly render the vector tiles within OpenLayers, you will need to fetch
the defined EPSG:3857 Tile Matrix Set and style definitions from the OS NGD API - Tiles service. The two endpoints provide information about the structure of the vector tiles and how the styles are to be applied.
A promise.all
is used to process the data to ensure that both requests are completed before proceeding.
Based on the fetched Tile Matrix Set data, a tile grid is defined using the ol.tilegrid.TileGrid class. The tile grid provides information about the resolution, origin and tile sizes to handle the vector tiles correctly.
Add the following code inside the Javascript block:
Define the a new vector tiles layer and source that will be used to fetch vector tiles from the OS NGD API - Tiles. The ol.layer.VectorTile
uses a ol.source.OGCVectorTile
source to retreive tiles from the API.
After creating the vector layer, you will need to use a style function to ensure that the Ordnance Survey style are applied to each tile. Using the olms.applyStyle
function to retrieve the style sheets available for the base map.
Initialize the map object using the ol.map
class to configure the vector tile layer and define its properties - target
, layers
and view
The above code creates the main map instance using the OpenLayers library where you can specify various properties:
target
: Defines where the map should be displayed, in this instance it is set to the ID
of the <div>
element.
layers
: An array containing the layers to be added to the map.
view
: Defines the initial view of the main, containing various settings such as projection, extent (the geographic bounds of the map), minimum and maximum zoom levels, centre of the map and the initial zoom level.
Accessing OS NGD API - Tiles via MapLibre GL JS
OS NGD API - Tiles added to an API project in the OS Data Hub with an API Key.
A text editor like Visual Studio Code or Notepad to edit and save your HTML and JavaScript files
Create a new HTML file with a text editor (e.g. Notepad, Visual Studio Code).
Add the basic HTML structure to your file with a placeholder <div>
for the map.
To enable access to OS APIs an API key is required. Inside the <script>
tag, add a variable called apiKey
, replacing 'INSERT_API_KEY_HERE'
with the API key from your project.
Inside the <script>
tag, add another variable called collectionId
with the collection ID for the OS NGD API - Tiles base map - ngd-base
We need to intercept and customise the style request, adding a tiles
property to provide a correctly formatted URL and authentication through the apiKey
is enabled to ensure the correct tiles are requested.
Add the following code inside the Javascript block:
Initialize the map object using the maplibregl.Map
class to configure the vector tile layer and define its properties - container
, minZoom
, maxZoom
, maxBounds
, style
, center
and zoom
.
Add navigation controls to the map, excluding the compass button and disabling map rotation.
The above code creates the main map instance using the MapLibre GL JS library where you can specify various properties:
container
: Defines where the map should be displayed, in this instance it is set to the ID
of the <div>
element.
minZoom
and maxZoom
: Sets the minimum and maximum zoom level for the map. Users will not be able to go beyond these levels.
maxBounds
: Defines the maximum bounds and restricts panning the map.
style
: Defines the style of the map, configured via a URL pointing at the default style for the 'collectionId
' defined.
center
: Sets the initial center point of the map.
zoom
: Sets the initial zoom level of the map.
General FAQs and answers for OS APIs are available on the and , for example, 'What's a Project?', 'What throttling is applied to the APIs?'
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.
Congratulations! You've successfully created a vector map using OpenLayers using the OS NGD API - Tiles in a few steps. Continue to explore Ordnance Survey's to learn more about advanced features and functionality such as adding markers, pop-ups, and additional layers.
is a free and powerful JavaScript library for displaying interactive maps on the web. It's based on Mapbox GL JS and provides a wide range pf features for creating maps with custom styles, markers and interactivity.
Congratulations! You've successfully created a vector map using MapLibre GL JS using the OS NGD API - Tiles in a few steps. Continue to explore Ordnance Survey's to learn more about advanced features and functionality such as adding markers, pop-ups, and additional layers.
There are some agreed and known challenges with capturing and publishing data for Building Age, Construction Material and Basement Presence.
There is no single, definitive measurement or information available for any of these attributes at a national scale.
There are limited and sometimes conflicting sources of information from which to derive values.
The real world can be very difficult to represent in data. For example, new builds can be made to look like older buildings.
Note
This content supplements the content on the OS NGD Building feature page.
A new building geometry which represents a single building footprint. This geometry consists of adjoining building parts which have been determined to be part of the same building. When contained in a Land Use Site, adjoining building parts are represented by a single feature.
Separate, non-adjoining building parts within a Land Use Site are also represented as NGD Building features.
For the initial capture of Basement Presence attributes, OS has used data captured and supplied by Verisk. This data will be maintained by data updates from Verisk and supplemented by OS Surveyed data.
Values for this attribute are: Present, Not present, Unknown, Null. As only buildings that contain at least one address are within scope, Null is used for buildings that are out of scope like garages or sheds.
Sourced from OS Address attribution.
Values for this attribute are: Present, Not present, Unknown, Null. As only buildings that contain at least one address are within scope, Null is used for buildings that are out of scope like garages or sheds.
For the initial capture of Building Age Period, OS has used data captured and supplied by Verisk. This data will be maintained by data updates from Verisk and supplemented by OS Surveyed data.
The Building Age Period ranges vary for earlier periods and move to consistent decadal ranges from 1980 onwards. Earlier than 1919, it difficult to identify commercial buildings so there is a catch-all range of pre-1919 as well as more defined ranges going back to 1837 covering only residential buildings.
The Building Age Period can be Unknown where OS does not know the building age and Null if the building is out of scope, that is, does not have at least one address (for example, domestic outbuildings like sheds and separate garages).
For the initial capture of Building Age year, OS has used data captured and supplied by Verisk. This data will be maintained by data updates from Verisk and supplemented by OS Surveyed data.
If a Building Part has an address and a Building Age, and is part of a larger Building feature with other Building Parts that do not have an address, the resulting Building feature will inherit the Building Age Period of the single addressed part of the Building. This can create anomalies in the data. Where a Building has multiple Building Ages from different Building Parts, the oldest date is used.
The Building Age Year can be Unknown where OS does not know the building age and Null if the building is out of scope, that is, does not have at least one address (for example, domestic outbuildings like sheds and separate garages).
For the initial capture of Construction Material, OS has used data captured and supplied by Verisk and OS. OS data identifies Static Caravans and Mobile Homes. This data will be maintained by data updates from Verisk and supplemented by OS Surveyed data.
The primary material can be the internal or structural material, or the externally visible material and the Constructionmaterial_thirdpartyprovenance attribute can help determine this. Typically, data sourced from EPC will show the internal or structural value.
Where multiple Building Parts make up a single Building, the Construction Material will be derived from the Building Part with the largest area.
The Construction Material can be Unknown where OS does not know the material and Null if the building is out of scope, that is, does not have at least one address (for example, domestic outbuildings like sheds and separate garages).
Created using OS Address and OS Land Use Sites data.
The following information defines the third party provenance attribute values and how they are created.
Verisk data is sourced from multiple third party data sources and / or created using algorithms. The Verisk data provenance can be identified using the following attributes:
This additional attribution will help users determine the value and suitability of this data to meet specific use cases.
This is not a named third party provenance value, however, the process used to create Building Age Period, Construction Material and Basement Presence data is partly dependent on the process used to create Verisk UKBuildings data.
Much of the data supplied by Verisk is based on initial capture and classification of building characteristics from vertical and oblique aerial imagery. Trained observers outlined defined areas, encompassing buildings with similar age, use and physical characteristics, using a detailed residential and non-residential classification. This classification provides the basis for many of the age values and with age being a key determinant of Basement Presence and Construction Materials, this is a key foundation of this data.
Within the Verisk UKBuildings data, Construction Material was observed for non-residential buildings (in urban areas) and was modelled based on Verisk premise age and type for residential buildings. So, for example, all low Victorian Terrace buildings would have brick walls and slate roof materials. Modern detached houses would have brick walls and tile roof.
Address Analysis is an umbrella term describing construction dates derived from investigation of historic address data and modern Postal Address data (post 1996).
Changes in modern Postal Addresses data used to infer when buildings were built. For example, if an address first appears in 2008, it could be assumed that the building relating to that address was built in that year.
Historic address data from Historic Maps and Census data, can indicate that a specific building existed when the data was collected (assuming the building hasn’t been demolished and rebuilt with the same name). For example, if a building called “The Old Mill” is present on a historic map from 1895 and present in modern address data, it can be assumed that the building Construction Date is earlier than 1895.
Age bands given in EPC relate to changes in building regulations impacting heating and energy efficiency and are therefore do not necessarily align to the Building Age Period attribute values.
A building may have more than one EPC or may be given more than one age in a single EPC which can sometimes lead to inconsistencies. For example, it is common to find buildings in a single housing estate that may not be assigned the same single Building Age.
EPC is the primary source of data for this attribute and is extracted from the Walls Description field. This is often the internal walls which can lead to a difference in what values are represented across the data. This will be a mix of internal/structural and external construction material.
The Floor Level characteristic of Domestic EPCs, provides confirmation that an address is at basement level, for single storey flats or maisonettes.
Open data sources that can contain multiple references to age which can lead to challenges deciding which age to extract.
The sale prices of properties in England and Wales submitted to HMLR for registration.
Verisk have used advanced analytics and data modelling to derive building information where no definitive or observed data can be identified.
Some building characteristics used in this process include -
Known age characteristics of nearby buildings.
Building size, shape, orientation, and distance from road. For example: modern buildings are smaller and parallel to roads.
Address and Postcode characteristics.
Local area statistics, such as Census.
Age and other characteristics of the building - Uses the concept of architypes to describe standard characteristics of properties of similar age and residential type. Such architypes provide default construction characteristics if other information is not available.
Known characteristics of nearby buildings. For example, buildings along a terrace are likely to have the same construction material.
Local area statistics (ONS).
Age and other characteristics of the building - Basements are most commonly found in older buildings, and modern high-rise buildings.
Known characteristics of nearby buildings. For example, if a building along a terrace or road has a basement it is possible that other buildings on the same terrace or road will also have a basement.
Building size, shape, orientation, distance from road and slope.
Local area statistics (ONS).
HM Land Registry
Analysis of Local Authority planning and building control data to identify buildings with a basement.
Basements were also identified from planning applications.
Valuation Office Agency (Fair Rent Register)
Non-Domestic EPC (England and Wales & Scotland)
Cabinet Office (ePIMS)
Data derived from Verisk UKBuildings data and this manual observation process.
Two open data Valuation Office datasets (Fair Rent Register and 2018 Non-domestic rating data) were used to identify buildings with basements.
These pages contain specific advice on how to make the most of the OS NGD Field Boundary data.
A new building geometry which represents a single building footprint. This geometry consists of adjoining building parts which have been determined to be part of the same building. When contained in a Land Use Site, adjoining building parts are represented by a single feature.
Version one of NGD Building features was published in the September 2023 release of OS NGD. Version two was published in the OS NGD March 2024 release.
The OS NGD Building feature type will be enhanced with additional attribution over time.
Note
Indicates if a basement is present in the building. Basement presence is recorded for buildings with at least one address. It may be recorded for some non-addressable buildings, but the majority of these will have basement presence recorded as NULL.
Indicates if the basement contains a self-contained flat.
The period (that is, a range of years) in which the building was constructed. Construction period is recorded for addressable buildings. It may be recorded for some non-addressable buildings, but the majority of these will have construction period recorded as NULL.
The year in which the building was constructed. This is recorded for buildings constructed post-1999 and where available.
The primary material from which the building is constructed. Construction material is recorded for buildings with at least one address. It may be recorded for some non-addressable buildings, but the majority of these will have construction material recorded as NULL.
A single descriptive value intended for a quick understanding of what the feature represents.
The provenance of the Building Age, Construction Material and Basement Presence provided by the third party data provider, for example the name of an organisation and or the specific dataset provided by that organisation or the data process used to create the data.
This content supplements the attribute definitions on the page.
Theme | Buildings |
Collection | Building |
Feature Type | Building |
Version | 2.0 |
Coverage | Great Britain All Buildings in scope |
Geometry | Not applicable (Building attribution) |
Attribution | Basement presence Presence of self-contained basement flat Third party provenance |
Data Sources | Verisk and Ordnance Survey |
Data Updates | Updates from Verisk assessed within 10 days and subject to validation will be updated into the NGD within three months. Updates from OS are subject to the standard revision policy. When available, updates are processed up to daily |
Supply Type | Full supply and Change Only Update (COU) |
Supply Format | GeoPackage, CSV (OS NGD Select+Build), GeoJSON (OS NGD API – Features, OS NGD API - Tiles) |
Theme | Buildings |
Collection | Building |
Feature Type | Building |
Version | 2.0 |
Coverage | Great Britain Buildings with at least one address |
Geometry | Not applicable (NGD Building attribution) |
Attribution | Period of construction Year of construction, where available Third party provenance |
Data Sources | Verisk and Ordnance Survey |
Data Updates | Updates from Verisk assessed within 10 days and subject to validation will be updated into the NGD within three months. Updates from OS are subject to the standard revision policy. When available, updates are processed up to daily |
Supply Type | Full supply and Change Only Update (COU) |
Supply Format | GeoPackage, CSV (OS NGD Select+Build), GeoJSON (OS NGD API – Features, OS NGD API - Tiles) |
Theme | Buildings |
Collection | Building |
Feature Type | Building |
Version | 2.0 |
Coverage | Great Britain Buildings with at least one address |
Geometry | Not applicable (NGD Building attribution) |
Attribution | Construction material Third party provenance |
Data Sources | Verisk and Ordnance Survey |
Data Updates | Updates from Verisk assessed within 10 days and subject to validation will be updated into the NGD within three months. Updates from OS are subject to the standard revision policy. When available, updates are processed up to daily |
Supply Type | Full supply and Change Only Update (COU) |
Supply Format | GeoPackage, CSV (OS NGD Select+Build), GeoJSON (OS NGD API – Features, OS NGD API - Tiles) |
Theme | Buildings |
Collection | Building |
Feature Type | Building |
Version | 2.0 |
Coverage | Great Britain Buildings with at least one address |
Geometry | Not applicable (Building attribution) |
Attribution | Building description |
Data Sources | Ordnance Survey |
Data Updates | Updates from Verisk assessed within 10 days and subject to validation will be updated into the NGD within three months. Updates from OS are subject to the standard revision policy. When available, updates are processed up to daily |
Supply Type | Full supply and Change Only Update (COU) |
Supply Format | GeoPackage, CSV (OS NGD Select+Build), GeoJSON (OS NGD API – Features, OS NGD API - Tiles) |
A Field Boundary is a line which identifies the nature of the physical barrier feature and its characteristics when adjacent to, or contained within, specific types of land cover. Field Boundary features are predominately classified in Rural and Moorland areas of Great Britain. Vegetated Field Boundary features are given height and width values to give an indication of size. Both man-made, for example ‘Wall’, and vegetated Field Boundary features, for example ‘Hedge’, are regarded as structures and therefore exist in the OS NGD Structures theme.
Field Boundary features are coincident with and reference all, or part of, an underlying OS NGD Structure Built Obstruction Line. They represent physical barriers between adjoining areas of land. There are five distinct categories to describe Field Boundary features: Tree Canopy, Wooded Strip, Hedge, Wall and Other. An 'Unknown' description is applied when the feature hasn’t yet been classified.
Field Boundary features are predominately classified across Rural and Moorland areas in Great Britain where they are adjacent to, or contained within, topographic areas of Agricultural Land, Trees, Rough Grassland or Heath OR when adjacent to land in the Rural Payment Agency’s (RPA) Rural Land Register (RLR) where they are in urban areas in England.
Features adjacent to land in the RPA’s RLR are buffered by 2 metres.
See fieldboundarydescriptionvalue for Field Boundary feature definitions.
Note:
Water-based boundaries, for example Ditches and Drains, are features within the OS NGD Water theme and are therefore not categorised as Field Boundary features.
Field Boundary data is created by an automated process. The inputs to the process are OS NGD Structure Built Obstruction Lines, OS aerial imagery (25cm), Digital Surface Model (DSM) and Digital Terrain Model (DTM).
After new imagery is available and the topographic area updates in 10km-by-10km area are complete, the automated process is run to classify features and calculate height and width values.
Field Boundary features are coincident with and reference the underlying parent OS NGD Structures ‘Built Obstruction’ Line. Field Boundary features follow the existing geometry of the Built Obstruction line.
Field Boundary features may be subdivisions of the Built Obstruction line where different classifications can be identified from OS aerial imagery. Where the line is not recognised as a vegetated or wall feature, the Field Boundary feature is classified as ‘Other’, for example fences, or newly planted hedges where features are too small to be identified from 25cm aerial imagery. Where the classification of Field Boundary features has not yet taken place by the automated process, these are classified as ‘Unknown’.
Where more than one classification is present, the classification hierarchy is used to decide which classification should be applied, that is, Tree Canopy (highest) to Unknown (lowest). Any classified section of Field Boundary feature less than 4.0 metres is ignored and subsumed into the surrounding classified sections based on the hierarchy.
Vegetated field boundary features are given minimum, maximum and average (mean) height and width values. Values are rounded up to the nearest 0.5 metres and provide an indication of the height or width rather than an absolute value.
Consideration is given to the natural movement of these features and seasonal variances, therefore during the calculation process, the Hedge width calculation includes a tolerance of 2.0 metres, and the width calculation of Tree Canopy and Wooded Strip includes a tolerance of 3.0 metres.
The minimum, maximum and average values are calculated using the 10th and 90th percentile values, sampled along the length of the Field Boundary feature at regular intervals. The calculated average mean value represents the most appropriate average height or width for each section of vegetated Field Boundary. Wall, Unknown and Other features are not given a height or width value.
The imagery_evidencedate attribute is the date on which the latest imagery capture was gathered and used to identify the Field Boundary feature. Where a feature has not yet been classified, it is ‘Unknown’ and the imagery_evidencedate will be null.
The 'isWoodlandBoundary' attribute is a Boolean flag to identify whether a field boundary is adjacent to a land cover area classified as woodland. ‘Woodland’ is defined as a land cover polygon with a classification of Coniferous Trees and/or Non-Coniferous Trees.
Vegetated Field Boundary features adjacent to an area of woodland in the OS NGD Land Theme, which include a classification of Coniferous Trees, Non-Coniferous Trees, Scattered Coniferous Trees or Scattered Non-Coniferous Trees, will have the 'isWoodlandBoundary' attribute populated with ‘True’ and height and width values will be null.
OS carries out a flying programme each year, capturing each area of Great Britain at least once every 3 years. The aerial imagery derived from this capture programme can be impacted by seasonal variances, that is, the time of year when the area was flown over, or even the time of day. Earlier in the year vegetated features may be captured with leaf-off, and long shadows are created which may impact the quality of the feature’s classification and width measurements.
Additionally, the automated process uses aerial imagery as a top-down view to classify Field Boundary features so some features may have their true nature obscured by overhanging trees. For example, fences running through woodland can be obscured by trees and therefore classified as Tree Canopy.
Limitations exist with existing OS NGD Structure lines, which is output in Field Boundary data:
Where the OS NGD Structure Line data is an ‘Edge or Limit’ of vegetation change rather than ‘Built Obstruction’ the Field Boundary is not classified.
Where features are close together and parallel e.g. a Ditch and a Hedge, the capture specification for NGD features will generalise and select one of the features, in this example the Ditch rather than the Built Obstruction Line is captured. This generalisation results in no Field Boundary features being classified and can commonly occur in low-lying areas. Additionally where Built Obstruction Lines are closely aligned, only one of these is picked up by the automated process and classified as a Field Boundary feature.
Moorland areas have a positional accuracy (RMSE) of 4.09m. The automated process has a search buffer of 2m to find potential vegetated Field Boundary features and 3m buffer for ‘Wall’ features. A search buffer any higher than this will result in many false positive classifications with the surrounding area, therefore some features in Moorland areas maybe inaccurately positioned.
Field Boundary features are classified through areas of woodland. This can occur when Built Obstruction Lines exist across areas of woodland and were classified when still visible from aerial imagery. Due to progressive changes in the natural environment, the trees have grown over time and obscured the underlying Built Obstruction Line. Classification from imagery will always classify the Field Boundary feature as 'Tree Canopy’ even if in the real world this is a fence.
There are known areas of Great Britain where the data quality maybe lower. See Known Data Issues for additional information.
A Road Track or Path feature type is found within the OS NGD Transport Theme, under the Transport Features Collection.
This feature type provides a polygon representation for transport-related features, which includes pavements. To identify the features which represent pavements you can filter on the Description
attribute for a value of Pavement
. This will result in you obtaining a polygon representation of the pavements for your areas of interest.
Pavement polygons have been captured as part of Ordnance Survey’s topographic data capture and are ‘surveyed’ features. These features are not segmented per road/street but are contiguous until broken by a real-world feature such as a road.
These features (unlike those described in following sections) do not contain specific attribution on pavement width, total presence, or sides of specific roads and streets.
An accurate depiction of the location and extent of pavements, primarily suited for visualisation use cases.
Allocation of pavement widths for entire pavement polygons (noting these polygons are not clipped to roads).
This polygon dataset has not been designed as and is not a routable network.
The pavements are not split into polygons only for roads they correspond to.
A linked dataset to the road link or pavement link data. There is no relationship between these polygons and the other two related feature types: Road Link and Pavement Link.
These pages contain general tips on using OS NGD Transport data and specific advice on how to make the most of the data provided by individual feature types.
Within the OS NGD Transport Theme, in the Transport Network Collection, there is a Road Link feature type which represents a line geometry for Great Britain’s road system.
This feature type provides a routable network, when used in conjunction with the Road Nodes feature type. Specific pavement attribution is provided against a road link (Version 2 schema) as described below.
Total metres of pavement present (includes both sides of the road).
Total coverage of pavement as a percentage (includes both sides of the road), e.g. if there is 50% coverage on the left-hand side, and 50% coverage on the right-hand side without any overlap then a 100% value will be assigned.
Total metres of pavements on the left side of the road.
Percentage coverage of pavement on the left side of the road.
Total metres of pavement on the right side of the road.
Percentage coverage of pavement on the left side of the road.
When allocating a pavement as left- or right-hand side of a road the direction of ‘digitisation’ of the Road Link feature is used, as determined by the startnode
and endnode
attribution of the road link.
Minimum Width of the pavement along the road link (includes both sides of the road)
Average Width of the pavement along the road link (includes both sides of the road)
To assign pavement information to Road Links we have used an algorithm which uses the pavement polygons which have been captured as part of Ordnance Survey’s topographic data capture and the road link data. Therefore the pavement attribution has not been surveyed as identified in its metadata attributes.
A buffer based on the average width of the Road Link is used to identify if a pavement exists along a Road Link. Generally, a pavement is associated with a road if it is immediately beside the road edge or at a short distance, without a physical barrier. Where the pavement is further away from the road edge or a physical barrier exists, the feature will be captured as a Path, as it will not meet the definition of a pavement.
When allocating a pavement as left- or right-hand side of a road the direction of ‘digitisation’ of the Road Link feature is used, as determined by the startnode
and endnode
attribution of the road link.
To ensure this feature type remains a fully routable network, some generalisation has taken place when assigning the pavement attribution. For example, to account for small gaps in pavement coverage at road junctions – meaning the pavement presence will still be set at 100% in these scenarios. This does not mean we have generalised or altered the road network data itself, just the way we assign pavement presence attribution.
Routing applications, which could use the specific pavement attribution to build logic to consider where roads are walkable. For example, a routing engine could decide that if there is 90% pavement coverage then this can be used for walking in their models.
High level understanding of whether a pedestrian can walk down a road.
Identify road links where there are significant pinch points in pavements.
Support analysis to identify how many roads in a given area have pavement coverage, and to identify those with lower overall pavement coverage to aid decision making.
Support asset management by allowing analysis into how many metres of pavement exist in an area of interest.
Provide understanding of whether adequate pavements exist to link new housing developments to key hubs in the local area.
Visualisation use cases to depict exactly where a pavement is located.
Understanding exactly where a pavement starts and ends along a road – the Pavement Link feature type will help with this use case.
Pavement definition - A raised, paved or man-made surface for pedestrian use at the side of a road.
Understanding the location of pavements can help provide insight into the accessibility of an area for pedestrians, as well as giving useful information for maintaining and monitoring these features as assets.
Within the OS NGD there are several feature types which will allow you to view and analyse pavement data, each with their own designs and intended use cases. These pavement representations are all found within the OS NGD Transport Theme and are listed below:
A polygon representation in the Road Track or Path feature type.
Specific pavement attribution provided on the Road Link feature type describing the presence and dimensions of pavements associated with the specific Road Link.
A dedicated Pavement Link feature type to help you understand where individual pavements start and end, and the pavement widths for each side of the road.
The following sections give more detailed information about the above three representations and how they can be used, to allow you to decide which of them is best suited for your use case.
A Field Boundary is a line feature representing the field boundary features adjacent to, or contained within, areas of agricultural land, trees, rough grassland or heath. It also includes features adjacent to land in the RPA’s Rural Land Register that are situated within urban areas in England. Field Boundary features replicate all, or part of, the underlying OS NGD Structure (Built Obstruction) Line and are classified as Tree Canopy, Wooded Strip, Hedge, Wall, Other or Unknown (in hierarchy order).
Theme
Structures
Collection
Structure Features
Feature Types
Field Boundary
Coverage
Great Britain, in Rural and Moorland areas. Features adjacent to, or contained within, areas of Agricultural Land, Trees, Rough Grassland and Heath OR when adjacent to land in the Rural Payment Agency’s (RPA) Rural Land Register (RLR) where they are in urban areas in England.
Geometry
Lines that represent physical barriers (Built Obstruction).
Data Sources
Automated classification using OS aerial imagery, digital surface models (DSM), digital terrain models (DTM), and ‘Built Obstruction’ Structure Lines from OS NGD.
Data Updates
3-year cyclical revision from OS aerial imagery (25cm). When the topographic area updates in 10km-by-10km area are complete, the automated process is run to classify and calculate height and width values. When available, updates are processed up to daily into OS NGD.
Supply Type
Full supply and Change Only Update (COU).
Supply Formats
GeoPackage or CSV download from OS NGD Select+Build.
GeoJSON from OS NGD API – Features and OS NGD API – Tiles.
Licensing Terms
Available to customers under PSGA licensing terms. Commercial terms are available for OS Partners based on the number of hectares.
The Pavement Link feature type can be found in the OS NGD Transport Theme, in the Transport Network Collection.
This feature type provides a geometry to depict pavement presence which is derived from the Road Link feature type geometry and as a result will be coincident with the Road Link features.
A Pavement Link feature is provided when a pavement is present and an individual feature will be created to represent each side of the road. As a result, when a pavement is present on both sides of a road, two Pavement Link features will be provided with the same geometry, whilst the attribution on the feature will specify which side of the road the given feature is associated with.
The Pavement Link feature represents the start and end points of the section of pavement. If comparing this geometry to the Road Link feature then you would expect to find ‘gaps’ in the Pavement Link features where pavements are not fully connected or do not exist.
All Pavement Link features have a linked identifier to the Road Link feature they are associated with (the roadlinkid
attribute).
The Pavement Link feature type aims to give a granular depiction of where a pavement exists along a road link.
To create the Pavement Link feature type we have used an algorithm which uses the pavement polygons which have been captured as part of Ordnance Survey’s topographic data capture and the road link data.
A buffer based on the average width of the Road Link is used to identify if a pavement exists along a Road Link. Generally, a pavement is associated with a road if it is immediately beside the road edge or at a short distance, without a physical barrier. Where the pavement is further away from the road edge or a physical barrier exists, the feature will be captured as a Path, as it will not meet the definition of a pavement.
When allocating a pavement as left- or right-hand side we use the direction of ‘digitisation’ of the associated Road Link feature, (as determined by the startnode
and endnode
attribution of the road link), with a separate Pavement Link feature being provided for each side of the road, which in some instances can result in overlapping geometries.
Understanding where (extent and side of the road) a pavement exists along any given road link. This provides additional information above and beyond that on the road link for identifying start and end points of a pavement. This is particularly useful when undertaking street works to identify whether a pavement might be impacted in any way by the planned street works.
Identifying more accurately where pinch points exist along a stretch of pavement, using the more detailed pavement link geometry to identify their location.
Pavement Link features are a discontinuous set of geometries and therefore not a routable network. Pavement Link features provide a more accurate representation of start and end points of pavements, which are not contiguous or topologically structured meaning the data is not intended for routing use cases.
A pavement centre line. If you would like a more accurate visual depiction of pavements the data in the Road Track or Path feature type provides a better solution.
Tram definition: A rail track dedicated to the movement of passenger tram rolling stock within big towns and cities.
Understanding where tram tracks are present on the road network can provide useful information for maintaining both road and tram assets, understanding risk for road users sharing the same space as trams, and supporting transport network management.
Within the OS NGD there are several feature types which will allow you to view and analyse tram track information, each with their own design and intended use cases.
These are all found within the OS NGD Transport Theme and are listed below:
Tram presence attribution provided on the Road Link feature type.
A dedicated Tram On Road feature type to help you understand the extent of tram track presence on the road network.
A Network representation in the Railway Link feature type.
The following sub-pages give more detailed information about the above three representations and how they can be used, to allow you to decide which best suits your use case.
Within the OS NGD Transport Theme, in the Transport Network Collection, the Road Link feature type represents a line geometry for Great Britain’s road system.
This feature type provides a routable network, when used in conjunction with the Road Node feature type. Specific tram attribution is provided against a road link (schema version 3.0) as described below.
Attribution indicating the presence of trams
The extent of tram track present on the road link, either full or partial
The direction the tram track applies, in relation to the direction of digitisation of the road link
To determine tram presence information on roads, we have used an algorithm which assesses Railway Links, road surface polygons (part of OS NGD Transport Features: Road, Track and Path topographic data) and Road Links.
The algorithm takes Railway Links with the description value ‘Tram’ and applies a buffer to identify which road polygons intersect and are therefore closely associated with these Tram links. All Road Links within the intersected polygons are then candidates for inclusion in the dataset. Further logic within the algorithm determines which Road Links are attributed with tram presence. The entire Road Link receives the attribution of ‘partial’ or ‘full’ presence.
Note that certain types of tram link are not considered by the algorithm, including "preserved", "static museum" and "funicular". These types of tram link are not required for transportation and navigation use cases, as they mainly serve a leisure purpose.
Identify all road links that have a tram track on them.
Support asset management uses cases by identifying whether a Road Link has a tram track on it which will impact street works and reinstatement jobs.
Support transport network management by identifying which Road Links will be impacted during tram track maintenance or incidents on the tram network, and what this would mean for wider traffic flows, road closures and diversions.
Visualisation use cases to depict the exact extent of the tram tracks.
Routing along the tram network – the Railway Link feature type will help with this use case.
The Tram On Road feature type can be found in the OS NGD Transport Theme, in the Transport Network Collection.
This feature type provides a stand-alone geometry to depict where tram tracks are on the road network. This geometry is derived from the Road Link feature type and as a result will be coincident with the Road Link features.
A Tram On Road feature is provided where a tram track is present on the road network. The feature represents the section of the Road Link where there is a tram track closely associated with it. When comparing this geometry to the Road Link feature type you would expect to find ‘gaps’ in Trams on Road features where tram tracks do not coincide with the entire Road Link.
All Tram On Road features have a linked identifier (roadlinkid attribute) to the Road Link feature they are associated with.
The Tram on Road feature type aims to give a granular depiction of the where tram tracks exist on a road link.
To create the Tram on Road feature type we have used an algorithm which assesses Railway Links, road surface polygons (part of OS NGD Transport Features: Road, Track and Path topographic data) and Road Links.
The algorithm takes Railway Links with description value ‘Tram’ and applies a buffer to identify which road polygons intersect and are therefore closely associated with these Tram links. All Road Links within the intersected polygons are then candidates for inclusion in the dataset. Further logic within the algorithm determines which Road Links are attributed with tram presence. A Tram on Road feature is created to indicate exactly where the tram interacts closely with the Road Link, with its geometry derived from the Road Link.
Note that certain types of tram link are not considered by the algorithm, including "preserved", "static museum" and "funicular". These types of tram link are not required for transportation and navigation use cases, as they mainly serve a leisure purpose.
Understanding where (the extents of) tram tracks are on the road network
Visualisation of the physical extents of where tram tracks are on roads
Routing along the tram network. Tram on Road consists of a discontinuous set of geometries, which is not a routable network. Instead, the Railway Link feature type will help with this use case.
A tram track centre line. Tram on Road uses Road Link geometry. The Railway Link feature type provides geometry for the generalised rail network, including tram tracks.
Within the OS NGD transport Theme, in the Transport Network Collection, the Railway Link feature type represents geometry of Great Britain’s Rail network.
This feature type provides a routable network when used in conjunction with the Railway Node feature type. The Rail network includes tram tracks as well as train tracks. Trams can be identified by the description attribute, which describes the nature of the railway the feature is representing (for example, description = Tram).
The Railway Link feature type provides a generalised geometry for the rail network of Great Britain. The generalisation of the rail network ensures full connectivity between relevant rail nodes. Rail track generalisation can be typically 3 or 4 sets of rail tracks 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.
Routing along the rail network, including trams
Visualising track centreline geometry. Railways Links provide the generalised geometry of rail and tram tracks
Identifying which road links have tram track on them
Natural topographic area features are mapped to:
EUNIS habitat type hierarchical view (marine version 2022 & terrestrial version 2021) using Level 1 and Level 2 classification; and
UK BAP Broad Habitats classification 2008
A simple algorithm automatically maps the OS Land Cover Tier B attribute of natural topographic area features to EUNIS and UK BAP classification scheme values using a lookup table prior to product publication. These are output into the Habitat Coverage Reference table.
Mapping the OS land cover classification to EUNIS Level 1 is mandatory. For EUNIS Level 2 and UK BAP it is not always possible to achieve a direct mapping as habitat classifications can be species-based, making it difficult to derive from a land cover classification. In such instances, there will be no entry for these records in the Habitat Coverage Reference table.
Coastal features also receive a habitat mapping. Coastal features are defined as being within the intertidal zone +200 metre buffer above the Mean High Water (Springs) Line.
The land cover enhancements align the OS land cover classifications to European Nature Information System (EUNIS) and UK Biodiversity Action Plan (BAP) Broad Habitats classification scheme values and provide a percentage of each land cover classification. These enhancements apply to ‘natural’ topographic area features which exist across several OS NGD themes.
The feature’s OS Land Cover Tier B attribute is mapped to EUNIS and UK BAP Broad Habitats classification scheme values where the topographic area feature is ‘natural’ i.e. the OS Land Cover Tier A attribute is one of ‘Excavated or Deposited’, ‘Open Vegetation’, ‘Mineral’, ‘Multiple’, ‘Trees’, ‘Under Construction’ or ‘Water’.
A percentage cover value is also assigned to the OS Land Cover Tier B attribute for those features above the Mean High Water (Springs) line. ‘Water’ features are not given a percentage cover value.
The land cover enhancements are supplied in a new cross-reference table. See the Habitat Coverage Reference table relating to the Land feature type .
The image below provides examples of these natural land cover features in OS NGD.
OS NGD Theme | Feature Type |
---|---|
OS NGD Land
Land
OS NGD Structures
Structure
OS NGD Transport
Rail
OS NGD Transport
Road Track or Path
OS NGD Water
Water
Natural topographic area features above Mean High Water (Springs) are assigned a percentage value for each OS land cover classification. Water features are currently excluded from scope as it’s not always possible to confidently discern a percentage value of any additional land cover classes in the water feature using aerial imagery.
Percentage cover values are calculated against the OS Land Cover Tier B attribute by an automated machine learning process using:
Automated interpretation of OS RGBI (25cm) aerial imagery to classify the type of land cover.
Automated comparison against the existing OS land cover classification derived from existing capture methods.
Automated calculation of percentage values for each OS Land Cover Tier B classification. Note: there can be up to five classifications within a single topographic area feature.
OS Land Cover Tier B percentage values are assigned to EUNIS and UK BAP Broad Habitats classifications, where a direct mapping exists.
The percentage values are output into the Habitat Coverage Reference cross-reference table.
Single class topographic area feature containing ‘Non-Coniferous Trees’.
Cross reference table is supplied as it’s ‘Open Vegetation’.
OS Land Cover Tier B classification is mapped to EUNIS Level 1 and Level 2 (where possible).
OS Land Cover Tier B classification is mapped to UK BAP.
OS Land Cover Tier B classification is assigned a percentage cover of 100% by default.
The percentage cover value is assigned to EUNIS and UK BAP.
Multi-class topographic area feature containing ‘Rough Grassland’, ‘Scrub’, ‘Scattered Non-Coniferous Trees’.
Cross reference table is supplied as it’s ‘Open Vegetation’ and ‘Trees’.
Each OS Land Cover Tier B classification is mapped to EUNIS Level 1 and Level 2 (where possible).
Each OS Land Cover Tier B classification is mapped to UK BAP.
Each OS Land Cover Tier B classification is assigned a percentage cover value.
The percentage cover values are assigned to EUNIS and UK BAP.
OS Land Cover Tier B percentage values total 100% for an individual topographic area feature.
Defined OS Land Cover Tier B classifications are assigned a minimum value of 10%
Percentage values are only calculated against the OS Land Cover Tier B value and then applied to EUNIS and UK BAP, where possible.
It's not always possible to map directly between OS Land Cover Tier B classification & EUNIS Level 2 or UK BAP so in these instances, no percentage cover value is supplied in the table.
Where it has not been possible to match the machine learning classification to the existing OS land cover classification, an 'Other' classification is added to the table to allow percentage values to total 100%. This can occur where features on the ground are obscured by overhanging trees. See Known Limitations for further information.
An 'Other' classification can have a minimum value of 5%.
Percentage values are rounded up in increments of 5%.
Percentage values can be null where a real-world change has occurred causing the topographic area feature to be updated. The percentage values for this topographic area feature will be recalculated when the automated process is next run against the updated aerial imagery.
Only topographic area features above Mean High Water (Springs) Line are assigned a percentage cover value. ‘Water’ topographic area features are also excluded from scope.
Manual land cover classification is subjective and in the natural environment, features change over time, for example scrub becomes trees. OS carries out a flying programme each year, capturing each area of Great Britain at least once every 3 years. The aerial imagery derived from this capture programme can be impacted by seasonal variances, i.e. the time of year when the area was flown over, or even the time of day. Earlier in the year vegetated features may be captured with leaf-off, long shadows may impact the feature’s classification, or during a dry summer an area of marsh may look like rough grassland.
Additionally, the automated machine learning classification to derive the percentage cover value uses aerial imagery as a top-down view so some features on the ground may have their true nature obscured by overhanging trees.
The automated classification of some feature types is of lower confidence and therefore the percentage cover value for these features may be of lower quality, i.e. ‘Saltmarsh’, ‘Heath’, ‘Rough Grassland’.
The Habitat Coverage Reference table provides the new attribution for habitat mapping and percentage coverage by linking to the OSID. There is a 1-to-many relationship which should be considered when joining the cross-reference table to features in GIS software packages.
The naming of the Habitat Coverage Reference file depends on which topographic area feature it applies to i.e.:
OS NGD Land feature type = land_habcovref
OS NGD Rail feature type = rail_habcovref
OS NGD Road Track or Path feature type = roadtrackorpath_habcovref
OS NGD Structure feature type = structure_habcovref
OS NGD Water feature type = water_habcovref
The Habitat Coverage Reference table is included with the GeoPackage file and available separately if data is requested in CSV format.
The fix for the known data issue relating to the description of Parish and Community 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 17th May until 27th May 2024.
This will result in larger daily change only update files. On 1 June 2024 the OS NGD Address monthly change only update file will be larger than a full supply file as all features will have a delete and an update record.
The March 2024 enhancement release for the OS NGD is now live. To find out more information about what these enhancements include please see our 'Whats new' page.
The September 2023 enhancement release for the OS NGD is now live. To find out more information about what these enhancements include please see our 'Whats new' page.
During August, and therefore before the September monthly supplies, we will be expanding our coverage of Paths and Tracks to the whole of Great Britain.
Previously, Paths and Tracks were provided only for urban areas.
This means that if you take a full supply of Path Link, Path Node and/or Path, Connecting Link or Connecting Node during August, this supply will have significantly grown in the total number of features compared to what you may have recently received, due to this expansion of coverage.
Equally, if you currently receive a monthly COU for any of the previously mentioned feature types, your Change Only Update will be significantly larger in September.
In our addressing products, we provide information detailing which local authority an address is within. As of 01 April 2023, several local authorities have reorganised to form new authorities. This means that the local authority code for all addresses within the affected authorities will change from the old authority to the new one, resulting in larger than normal Change-Only Updates (COUs) for feature types in the GB Address Collection.
The Government Statistical Services (GSS) codes for the local authority areas will be updated in May 2023, again resulting in larger than normal Change-Only Updates (COUs) for feature types in the GB Address Collection.
The following table lists the changes to the local authorities:
Existing local authority | Existing local custodian code | Existing GSS code | New local authority | New local custodian code | New GSS code |
---|---|---|---|---|---|
Allerdale
905
E07000026
Cumberland
940
E06000063
Carlisle
915
E07000028
Cumberland
940
E06000063
Copeland
920
E07000029
Cumberland
940
E06000063
Barrow-in-Furness
910
E07000027
Westmorland and Furness
935
E06000064
Eden
925
E07000030
Westmorland and Furness
935
E06000064
South Lakeland
930
E07000031
Westmorland and Furness
935
E06000064
Scarborough
2730
E07000168
North Yorkshire
2745
E06000065
Ryedale
2725
E07000167
North Yorkshire
2745
E06000065
Selby
2735
E07000169
North Yorkshire
2745
E06000065
Hambleton
2710
E07000164
North Yorkshire
2745
E06000065
Richmondshire
2720
E07000166
North Yorkshire
2745
E06000065
Harrogate
2715
E07000165
North Yorkshire
2745
E06000065
Craven
2705
E10000023
North Yorkshire
2745
E06000065
Mendip
3305
E07000187
Somerset
3300
E06000066
Sedgemoor
3310
E07000188
Somerset
3300
E06000066
Somerset West and Taunton
3330
E07000246
Somerset
3300
E06000066
South Somerset
3325
E07000189
Somerset
3300
E06000066
[1] No percentage value for Water features.
[2] Other features are included in scope where they have a natural land cover i.e. areas under construction are included because they are generally sand or bare earth until construction is complete. ‘Constructed’ or ‘Made’ features are out of scope.
[3] Only features above the Mean High Water (Springs) line have a percentage value.
This page lists known data issues in relation to the OS National Geographic Database (NGD) themes, collections and feature types. The OS NGD is in its infancy and, as such, will be largely developed and iterated upon in its early life.
As and when we resolve a known data issue, we will remove it from this page.
Data issue name | Data issue description |
---|---|
Data issue name | Data issue description |
---|---|
Data issue name | Data issue description |
---|---|
Data issue name | Data issue description |
---|---|
Data issue name | Data issue description |
---|---|
Data issue name | Data issue description |
---|---|
Theme
Land, Structures, Transport, Water [1]
Collection
Feature collections
Feature Types
Land, Rail, Road Track or Path, Structure, Water [1]
Coverage
Great Britain (‘Excavated or Deposited’, ‘Open Vegetation’, ‘Mineral’, ‘Multiple’, ‘Trees’, ‘Under Construction’ or ‘Water’ [1] topographic area features) [2] [3]
Geometry
Polygons
Data Sources
Classification of topographic area features is from existing ground and remote survey methods. Automated classification from OS aerial imagery (25cm) to determine percentage cover value.
Data Updates
3-year cyclical revision from OS aerial imagery. Updates are processed up to daily into OS NGD.
Supply Type
Full supply and Change Only Update (COU).
Supply Formats
GeoPackage or CSV download from OS NGD Select+Build.
GeoJSON from OS NGD API – Features.
Very small number of features not being given the correct 'End of Life' change type
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 'XXX Features', for example, 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.
Isle of Man addresses
A total of 32 address records are currently present in the OS NGD GB Address Collection which should not be contained within this collection as they are actually Isle of Man records. These records are correctly present in the OS NGD Islands Address Collection.
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'.
Your Change-Only Update (COU) processing will still work correctly, and your data holdings will be complete, but the address will have been incorrectly marked as 'New'.
Parish and Community / Ward GSS Codes
The Parish and Community GSS Codes for every feature type have been correctly assigned but incorrectly described as Ward GSS Codes and vice versa. When using these codes which reside in the Related Entities component if you are wanting a GSS Ward code you will need to use the records currently described as Parish and Community GSS codes and vice versa.
Historic European Region Feature Type
This feature type 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.
Some underground Structure features are
missing from the Habitat Coverage
Reference table
3 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.
Duplicate/overlapping Field Boundary
features exist
Approx. 20k Field Boundary features are overlapping and 23 of these have duplicate geometries, resulting in more than one version of the same feature in the dataset. This is currently being investigated.
Field Boundary data quality
At the time of launch (March 2024), areas of Great Britain were still to be quality checked and will be improved as part of OS’ 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’. The downloadable file below contains the status of each 10km2 area relating to the quality of the Field Boundary feature classification.
Welsh speed limit changes
On the 17th September 2023, default 20mph 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 3rd 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 in December 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. This issue impacts just over 2% (174 000) of the total Road Links in the Average and Indicative Speed Feature Type. This issue was resolved on 02 July 2023. Any data ordered or provided after this date will include the fixed data.
Invalid geometries in Waterbody Catchment and River Basin District Catchment features
Some catchment polygons appear to 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.
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.
Non-unique Waterbody Catchment IDs
Two instances occur where the Waterbody Catchment ID is not unique: GB109056040082 and GB104027063230. This is as per the third-party data from the authoritative bodies.
Certain Waterbody Catchment features do not nest exactly within a River Basin District Catchment.
A total of 14 instances occur where Waterbody Catchments do not nest exactly within their associated River Basin District Catchment. This is as per the third-party data from the authoritative bodies.
The OS Data Catalogue is where GEMINI metadata records can be found for all of the OS NGD data themes and for OS Select+Build, OS NGD API – Features and OS NGD API – Tiles.
In the future, we plan to deliver over 30 data enhancements to the OS NGD. As we design and develop these data enhancements, more details will be added to this page.
Recently delivered enhancements to the OS NGD are listed on the What's New? page
New attribution for buildings to provide additional information on the number of floors, building height and building status (built or under construction).
Attribution on building roofs (including roof shape, aspect, construction material, and presence of solar panels and green roofs)
Access locations for key public buildings
Even more land use sites for commercial, industrial, community, amenity, infrastructure, residential, and construction sites
Improved land use attribution in the Land Feature Type
Access purpose information for major public sites
Extending inter tidal areas to include obscured polygons beneath elevated structures
New attribution to indicate whether vacant or derelict land
Improved river width attribution
New feature types for continuous tidelines to complement the existing Tidal Boundary Feature Type
New attribution for cycle lanes, streetlights and bus lanes
Enhanced names and places data, such as vernacular names, tunnels, and bridge interactions.
Ongoing improvements to address data regarding the consistency of address positioning, usage classifications, address lifecycle and business names
Improved alignment of administrative and electoral boundaries with topographic features, where appropriate
Addition of feature types for postcode points and enhanced postcode areas
Improved 'reason for change' metadata to make it easier for customers to identify change that is relevant to their use cases