> For the complete documentation index, see [llms.txt](https://docs.os.uk/osngd/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.os.uk/osngd/~/changes/1810/getting-started/os-ngd-fundamentals/os-ngd-data-ordering-and-currency.md).
# Data ordering and currency
To get access to the OS NGD you must first log into the [OS Data Hub](https://osdatahub.os.uk/). The OS NGD is accessible via both the [Premium Plan and Public Sector Plan on the OS Data Hub](https://osdatahub.os.uk/plans).
## Geographic filtering
There are three options within OS Select+Build (the OS NGD download service) in relation to the geographic extent of your order. These are:
* **Great Britain**: Receive all data for the whole of Great Britain.
* **Customer Specified Area**: Draw an area of interest (AOI) and only receive the data which intersects this area.
* **Pre-defined Area**: Select a pre-defined area, and only receive the data which intersects this area.
{% hint style="info" %}
## Exceptions
* The only exception to the above is the OS NGD Address Islands Collection; this collection contains data for Northern Ireland, the Isle of Man, and the Channel Islands, and it will be provided as a full supply of data independent of any geographic filtering applied to your OS NGD recipe.
* COU Supplies are not available for AOIs. Monthly Full Supplies are available for AOIs.
{% endhint %}
## Order update options
When accessing the OS NGD, the following order update options will be available:
* One Off Full Supply
* Regular Full Supply
* Change-Only Update (COU; after an initial Full Supply)
* No Update
The following frequencies will be available dependent on the type of order you place:
* **Daily Supply**: This will provide you with the latest updates OS have loaded and verified for publication since the previous day as a COU file.
* **Monthly Supply:** Either a Full Supply or COU Supply of all the changes which have occurred in the previous month.
* **Annual Supply**: A Full Supply of the data to show how the data looked at the end of each year.
Further details about the options available to you can be found further down on this page.
{% hint style="info" %}
## Please note
* Monthly orders provide data for the 1st of the month. For example, if you ordered a Monthly order on 17 September 2024, you would receive the data as it was on 01 September 2024.
* If you select an Annual Full Supply frequency for your OS NGD data order in OS Select+Build, we will provide you with the data as it was on 01 January of the current year. This means if a new feature type or a new data schema version of an existing feature type was released after 01 January and you order either of these as part of your Annual Full Supply, you will receive an **empty data package** for the newly released feature type / new data schema version of an existing feature type. The data for the new feature type / new data schema version of an existing feature type will then be included in your supply on the next 01 January after the release.
* For example, the March 2025 OS NGD data enhancements release contained 3 new feature types (Building Access Location, Crowd Sourced Name Point, and Street Light), and 11 new data schema versions (Building v4.0, Building Part v2.1, Land v3.1, Path Link v2.0, Rail v3.1, Road Link v4.0, Road Track Or Path v3.1, Site v2.2, Site Access Location v2.0, Structure v3.1, and Water v3.1). As per the bullet above, the data will not be part of Annual Full Supply orders until 01 January 2026.
* For example, the Autumn 2025 OS NGD data enhancements releases contained 6 new feature types (Royal Mail Address, Royal Mail Address, Bus Lane, Cycle Lane, Tidal Boundary Continuous High and Tidal Boundary Continuous Low), and 14 new data schema versions for existing feature types (Built Address v3.0, Built Address v3.0, Historic Address v3.0, Historic Address v3.0, Land v3.2, Non-Addressable Object v3.0, Non-Addressable Object v3.0, Path Link v3.0, Pre-Build Address v3.0, Pre-Build Address v3.0, Road Link v5.0, Site v1.3 and 2.4, and Water Link v2.0) and 3 new data schema versions for existing addressing related components (Alternate Address v3.0, Other Classification v3.0 and Related Entity v3.0). As per the bullet above, the data will not be part of Annual Full Supply orders until 01 January 2026.
{% endhint %}
### Update files
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.
### File supply
If you use OS Select+Build to access the OS NGD, then a separate download file will be provided for each feature type you order. For example, if your selected theme has two feature types you will be supplied with two separate files (CSV or GeoPackage) as part of your order.
### Ordering combinations
The following tables summarise the different options available to you dependent on what you specify when ordering your data through OS Select+Build.
For the purposes of the tables below, the following definitions are being used:
* Unfiltered means a Great Britain supply with no further attribute filters applied.
* Filtered means an order for data which either has a geographic filter applied or an attribute filter applied.
#### GPKG files
| Initial Supply | Update Options |
|---|
| Daily (filtered / unfiltered) | N/A |
| Monthly (filtered / unfiltered) | Monthly Full Supply |
| Annual (filtered / unfiltered) | Annual Full Resupply with data from 01 January |
{% hint style="info" %}
Please note that COU supplies are only available for CSV files; they are not available for GeoPackage files.
{% endhint %}
#### CSV files
| Initial Supply | Update Options |
|---|
| Daily (filtered) | N/A |
| Daily (unfiltered) | Daily COU |
| Monthly (filtered) | Monthly Full Supply |
| Monthly (unfiltered) | Monthly COU or Monthly Full Supply |
| Annual (filtered / unfiltered) | Annual Full Resupply with data from 01 January |
{% hint style="info" %}
You can use the [OS Downloads API](https://osdatahub.os.uk/docs/downloads/overview) to manage your daily / monthly COU supply of OS NGD data.
{% endhint %}
### Order summary file
Feature types downloaded via OS Select+Build will be supplied with an Order Summary File, a small JSON manifest that provides key metadata about the supplied file. You can use this file to validate the data to ensure the currency, record count, schema version, feature name and coordinate reference system (CRS) match your expected order.
The following file naming convention will be applied to each Order Summary file you receive:
* collection\_featuretype\_orderSummary.json
For example, the file name for the Building Part Feature Type Order Summary file would look like this:
* bld\_fts\_buildingline\_orderSummary.json
The example below shows the information an Order Summary file contains:
```json
{
"featureName": "bld-fts-buildingline",
"crs": "http://www.opengis.net/def/crs/EPSG/0/27700",
"schemaVersion": "1.0",
"validFromDate": null,
"validToDate": "2023-03-01",
"recordCount": 202653
}
```
The following table provides a brief description of each field:
| Field | Description | Use |
| ------------- | -------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| featureName | The feature type delivered in this order. | Validate the downloaded feature against your recipe. |
| crs | The coordinate reference system used for your supply. | Validate the coordinate reference system against the CRS selected for your recipe. |
| schemaVersion | The OS NGD data schema version provided for the feature. | Coordinate data schema updates with changes to your data. |
| validFromDate | The start date of coverage for this supply. | Validate the currency of your data to ensure the earliest date aligns with the expected supply window for your order frequency. |
| validToDate | The end date of coverage for this supply. | Validate the currency of your data to ensure the latest date aligns with the expected supply window for your order frequency. |
| recordCount | The total number of records delivered in the file. | Check that delivered entries match the number of records expected for your download. |
## Currency of OS NGD data
### OS Select+Build and OS NGD API – Features
Whether accessing OS NGD data through OS Select+Build or OS NGD API – Features, the following currency of the data will apply:
| Theme | Collection | Update Frequency |
| ----------------------------------------------------------------------------------------------------- | ------------------------------- | ------------------------------------------------------------------------- |
| OS NGD Address
(\*N.B. Not available in OS NGD API – Features)
| Both OS NGD Address collections | Daily |
| OS NGD Administrative and Statistical Units
(\*N.B. Not available in OS NGD API – Features)
| OS NGD Boundaries | Biannual |
| OS NGD Buildings | OS NGD Buildings Features | Daily |
| OS NGD Geographical Names | OS NGD Named Features | Daily |
| OS NGD Land | OS NGD Land Features | Daily |
| OS NGD Land Use | OS NGD Land Use Features | Daily |
| OS NGD Structures | OS NGD Structure Features | Daily |
| OS NGD Transport | OS NGD Transport Features | Daily (apart from the Street Light Feature Type which is updated monthly) |
| | OS NGD Transport Network | Monthly |
| | OS NGD RAMI | Monthly |
| OS NGD Water | OS NGD Water Features | Daily |
| | OS NGD Water Network | Quarterly |
{% hint style="info" %}
\*Please see the ['What data is available' (for OS NGD API – Features)](/osngd/~/changes/1810/getting-started/access-the-os-ngd-api/os-ngd-api-features/what-data-is-available.md) page for more information on what features are available in this API.
{% endhint %}
For collections that are not updated daily, the table below provides the date of the last update; it also shows the version of the OS MasterMap product to which the OS NGD data corresponds, if applicable:
| Collection | Last Updated | Corresponding OS MasterMap Product |
|---|
| OS NGD Boundaries | 16 October 2025 | Boundary-Line – October 2025 publication |
| OS NGD Transport Features – Street Light Feature Type only | 06 March 2026 | N/A |
| OS NGD Transport Network | 06 March 2026 | OS MasterMap Highways Network – March 2026 publication |
| OS NGD RAMI | 06 March 2026 | OS MasterMap Highways Network – March 2026 publication |
| OS NGD Water Network | 28 January 2026 | OS MasterMap Water Network – January 2026 publication |
### OS NGD API – Tiles
When accessing OS NGD data through OS NGD API – Tiles, the data currency is weekly for the basemap and variable for the four data overlays – please see the ['What data is available' (for OS NGD API – Tiles) page](/osngd/~/changes/1810/getting-started/access-the-os-ngd-api/os-ngd-api-tiles/what-data-is-available.md) for more information on update frequency, available feature types and available attribution for this API.
{% hint style="warning" %}
Please note:
* The OS NGD Address Theme is only available via OS Select+Build and is not available via OS NGD API – Features or OS NGD API – Tiles.
* The OS NGD Administrative and Statistical Units Theme is only available via OS Select+Build and OS NGD API – Tiles and is not available via OS NGD API – Features.
* Feature types in the Routing and Asset Management Information (RAMI) Collection (of the OS NGD Transport Theme) are only available via OS Select+Build and OS NGD API – Features and are not available via OS NGD API – Tiles.
* The Tidal Boundary Continuous High, Tidal Boundary Continuous Low, River Basin District Catchment and Waterbody Catchment Feature Types (of the Water Features Collection in the OS NGD Water Theme) are not available via OS NGD API – Features but they are available via OS Select+Build and OS NGD API – Tiles.
{% endhint %}
## Feature counts for the OS NGD Transport Theme
Feature counts are detailed below for the [Routing and Asset Management (RAMI)](/osngd/~/changes/1810/data-structure/transport/rami.md) and [Transport Network](/osngd/~/changes/1810/data-structure/transport/transport-network.md) Collections of the [OS NGD Transport Theme](/osngd/~/changes/1810/data-structure/transport.md). These feature counts will be updated monthly to reflect data currency for these collections.
RAMI Collection feature counts for March 2026 (click the arrow to view the table)
| Feature Type | Full Supply Feature Count |
| ---------------------------- | ------------------------- |
| Average And Indicative Speed | 8 570 178 |
| Highway Dedication | 4 041 972 |
| Maintenance Area | 1 419 |
| Maintenance Line | 1 467 435 |
| Maintenance Point | 65 840 |
| Reinstatement Area | 2 016 |
| Reinstatement Line | 1 610 609 |
| Reinstatement Point | 132 959 |
| Restriction | 1 101 215 |
| Routing Hazard | 43 651 |
| Routing Structure | 1 404 192 |
| Special Designation Area | 21 949 |
| Special Designation Line | 525 642 |
| Special Designation Point | 283 456 |
Transport Network Collection feature counts for March 2026 (click the arrow to view the table)
| Feature Type | Full Supply Feature Count |
| ---------------- | ------------------------- |
| Bus Lane | 25 633 |
| Connecting Link | 2 015 598 |
| Connecting Node | 1 869 425 |
| Cycle Lane | 424 576 |
| Ferry Link | 223 |
| Ferry Node | 340 |
| Ferry Terminal | 340 |
| Path | 25 414 |
| Path Link | 3 385 955 |
| Path Node | 3 994 615 |
| Pavement Link | 9 363 867 |
| Railway Link | 155 733 |
| Railway Link Set | 154 |
| Railway Node | 152 409 |
| Road | 858 598 |
| Road Junction | 6 884 |
| Road Link | 8 570 177 |
| Road Node | 7 595 842 |
| Street | 1 570 604 |
| Tram On Road | 3 246 |
{% hint style="info" %}
Please note, feature counts are currently **only provided for two OS NGD collections**: the Routing and Asset Management (RAMI) and Transport Network Collections of the OS NGD Transport Theme.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.os.uk/osngd/~/changes/1810/getting-started/os-ngd-fundamentals/os-ngd-data-ordering-and-currency.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.