1 of 19

Downloading with OS Select+Build

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

What is OS Select+Build?

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

File formats available with OS Select+Build

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

What's different about OS Select+Build?

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

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

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

Learn more about recipes in the Getting started with recipes guide.

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

Using OS Select+Build

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

Getting started with recipes

What is a recipe?

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

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

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

Using OS Select+Build recipes

Things to remember

You can:

Delete a recipe
Edit an existing recipe (i.e. add or remove themes / feature types, or change attribute filtering or data schema versions)
Edit the name or description of a recipe
Create multiple data packages from a single recipe
Delete a data package
Search through your organisation's recipes in the OS Select+Build Recipe Library using the recipe name, description, or content (i.e. themes, collections, or feature types)
Search through your organisation's data packages in the Data packages list screen using the data package name, data package number, or product name
Collect your data package(s) via the OS Data Hub or the OS Downloads API
Share a recipe with another organisation that has access to OS Select+Build

You can't:

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

Managing OS Select+Build recipes

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

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

The following sub-sections on this page cover:

How do I create a new recipe?

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

Log into your OS Data Hub account

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

Navigate to the OS Data Hub workspace

Select Data from the menu bar to view your workspace.

Navigate to the OS Select+Build Recipe Library

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

Choose Create a new recipe

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

Add details to the recipe

Give your recipe a descriptive name.
Add a detailed description for your recipe.
Select your OS NGD data by choosing the themes, collections and feature types you want to include in your recipe.
(Optional) Add filters to the feature types, if needed; more information about this is available on the Getting started with attribute filtering page.

(Optional) Choose a data schema version

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.

Finish creating the recipe

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.
Adding filters to feature types is an optional step for those with advanced OS data knowledge; see the Getting started with attribute filtering page for more information on applying filters and step-by-step instructions.
Selecting a data schema version for a feature type is an optional step; if you don't choose a particular data schema version for a feature type, OS Select+Build will always select the latest available data schema version for you for each feature type by default. See the Data schema versioning page for more information.

What's next?

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

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

To find your OS Select+Build Recipe Library:

Log into your OS Data Hub account

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

Navigate to the OS Data Hub workspace

Select Data from the menu bar to view your workspace.

Navigate to the OS Select+Build Recipe Library

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

How do I check what's in a recipe?

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

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

Navigate to the OS Data Hub workspace

Select Data from the menu bar to view your workspace.

Navigate to the OS Select+Build Recipe Library

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

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

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

The recipe's name
The recipe's author
The date the recipe was created
A description of the recipe, if one has been added
OS NGD theme tags to show which themes are included in the recipe

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

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

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

The recipe's name
A description of the recipe, if one has been added
An option to view all of the filters applied to feature types in the recipe (if applicable)
The date the recipe was created
The recipe's author
An option to show the data schema version of each feature type in the recipe
A recipe tree detailing the OS NGD themes, collections, and feature types included in the recipe

How do I delete a recipe?

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

To delete a recipe:

Log into your OS Data Hub account

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

Navigate to the OS Data Hub workspace

Select Data from the menu bar to view your workspace.

Navigate to the OS Select+Build Recipe Library

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

Find the recipe you want to delete

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

Open the detailed recipe view

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

Delete the recipe

Click on the name of the recipe to view the recipe details.
- If there are no data packages associated with the recipe, you will be asked to confirm the deletion of the recipe.
- Where there are data packages associated, you will see the following warning:
Click the Delete recipe button.

A shared recipe cannot be deleted.

Editing OS Select+Build recipes

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

You can edit the content of an existing recipe (i.e. add or remove themes / feature types, or change attribute filtering or data schema versions) and you can edit the name or description of an existing recipe.

The following sub-sections on this page cover:

How do I edit the name of my recipe?

To edit a recipe's name:

Log into your OS Data Hub account

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

Navigate to the OS Data Hub workspace

Select Data from the menu bar to view your workspace.

Navigate to the OS Select+Build Recipe Library

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

Select the recipe you want to edit

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

View recipe details

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

Click the edit icon next to the recipe name

Click on the pencil icon next to the recipe name.

Change the name of the recipe

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

Save changes to the recipe

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

How do I edit the description of my recipe?

To edit a recipe's description:

Log into your OS Data Hub account

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

Navigate to the OS Data Hub workspace

Select Data from the menu bar to view your workspace.

Navigate to the OS Select+Build Recipe Library

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

Select the recipe you want to edit

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

View recipe details

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

Click the edit icon next to the recipe name

Click on the pencil icon next to the recipe name.

Change the description of the recipe

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

Save changes to the recipe

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

How do I edit a recipe?

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

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

Log into your OS Data Hub account

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

Navigate to the OS Data Hub workspace

Select Data from the menu bar to view your workspace.

Navigate to the OS Select+Build Recipe Library

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

Select the recipe you want to edit from the list

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

Edit recipe data

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

Save changes to your recipe

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

Recipes with data packages linked to them that receive COUs

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

To create a copy of a recipe:

Log into your OS Data Hub account.
Select Data from the main menu.
Choose Downloads > OS Select+Build Recipe Library from the secondary navigation menu.
From your list of recipes, click on the name of the recipe you wish to edit, then click on the Recipe actions dropdown and select Edit recipe.
When the 'Recipe cannot be edited' warning pop up appears, click the Copy recipe button.

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

The copied recipe will appear in your OS Select+Build Recipe Library and you can now edit it following the 'How do I edit a recipe?' steps outlined above.

Sharing OS Select+Build recipes

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

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

The following sub-sections on this page cover:

To share a recipe:

Log into your account

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

Navigate to the OS Data Hub workspace

Select Data from the menu bar to view your workspace.

Navigate to the OS Select+Build Recipe Library

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

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

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

Click the Recipe actions dropdown.
Click the Share recipe button.

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

Choose the correct organisation from the recipe dialog

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 descriptive message about the recipe

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

How do I accept a recipe shared with me?

To accept a shared recipe:

Log into your account

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

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

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

View details of the received recipe

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

Accept the shared recipe

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

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

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

How do I reject a recipe shared with me?

To reject a recipe shared with you:

Log into your account

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

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

View details of the received recipe

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

Decline the shared recipe

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

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

Getting started with attribute filtering

Step-by-step instructions on how to add attribute filters to recipes in your OS Select+Build Recipe Library.

Introducing attribute filtering

Attribute filtering is a new concept which we have introduced as part of OS Select+Build. The filters can help you to narrow down the exact data you need from the OS NGD. If required, you can add attribute filters to individual feature types when you create a new bespoke recipe of OS NGD data using OS Select+Build. The managing OS Select+Build recipes page has step-by-step instructions on how to create a new recipe. You can also add, edit or remove attribute filters to / in / from feature types in an existing recipe of OS NGD data.

Attribute filtering is an optional step for those with advanced OS data knowledge.

You can:

Add attribute filters to feature types in a new recipe
Add, edit or remove attribute filters to / in / from feature types in an existing recipe

The following sub-sections cover:

How do I add attribute filters to a new recipe?

To add attribute filters to a new recipe:

Log into your OS Data Hub account

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

Navigate to the OS Data Hub workspace

Select Data from the menu bar to view your workspace.

Navigate to the OS Select+Build Recipe Library

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

Create a recipe

Click the Create a new recipe button, adding the relevant details to your recipe.

See the Managing OS Select+Build recipes page for more information on creating recipes.

Add filters to feature types in your recipe

Click the filter icon next to the feature type(s) you want to add a filter to in the theme selection tree.

The Advanced Filter Options panel will then slide into view from the right and you can begin to build your filter(s):

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

Finish creating the recipe

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

How do I add attribute filters to an existing recipe?

To add attribute filters to an existing recipe:

Log into your OS Data Hub account

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

Navigate to the OS Data Hub workspace

Select Data from the menu bar to view your workspace.

Navigate to the OS Select+Build Recipe Library

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

Find the recipe you want to edit

In your OS NGD Select+Build Recipe Library, scroll or search for the recipe you would like to edit. Once you've found the recipe, click on its name; you'll be taken to the Recipe details screen.

Edit the recipe

In the Recipe details screen, click on the Recipe actions dropdown and select Edit recipe.

You'll now be able to add filters (see Step 6) or remove filters (see Step 7) from feature types in the recipe.

Add a filter to a feature type

Click the filter icon next to the feature type you want to add a filter to in the selection tree for the recipe.

The Advanced Filter Options panel will then slide into view from the right and you can begin to build your filter(s):

For a simple filter, select +Add rule.
For a more complex nested filter, select +Add group.
Once you have added all of your relevant filters, click Apply Filter.

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

Remove a filter from a feature type

Click the Edit filter iconnext to the feature type you want to remove a filter from in the selection tree for the recipe.
When the Advanced Filter Options panel slides into view from the right, select Clear all filters.

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

Worked example of creating a simple filter

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.

Log into your OS Data Hub account

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

Navigate to the OS Data Hub workspace

Select Data from the menu bar to view your workspace.

Navigate to the OS Select+Build Recipe Library

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

Create a new recipe

Click the Create a new recipe button.

See the Managing OS Select+Build recipes page for more information on creating recipes.

Add details to the recipe

Give your recipe a descriptive name.
Add a detailed description for your recipe
Select your OS NGD data by choosing the themes, collections and feature types you want to include in your recipe. For this worked example:
- Click on the arrow to the right of Buildings within the theme selection tree to see the collections available within the theme, then click on the arrow to the right of Buildings Features to see the feature types available within that collection.
- Click on the check box next to Building Part to select that feature type.

Add a filter to the Building Part Feature Type where the OS Land Use Tier A attribute is set to Education

Click on the filter icon to the right of Building Part.

The Advanced Filter Options panel will slide into view from the right, where you can begin to build your filter(s):

In the Advanced Filter Options panel, click + Add rule, then select OSLandUseTierA from the first drop-down.

Leave the operator in the second drop-down as: = (i.e. the equal sign), then select Education from the third drop-down.

Click the Apply filter button.

Finish creating the recipe

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

Your filter will return buildings where education (Education) is recorded as the land use (OS Land Use Tier A attribute).

Worked example of creating a nested filter

What if, in addition to the simple filter above (returning results for buildings with a land use of education), we want those results to show only buildings over 15metres in height? What if you also wanted to add an additional filter to show buildings with a land use of rail? To achieve this, you could create a nested filter using the + Add group option.

Follow the steps outlined above for creating a simple filter for Building Part until you reach the Advanced Filter Options panel step (Step 6).

Add a simple filter to the Building Part Feature Type

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.

Add a nested filter to the Building Part Feature Type

Click + Add rule to add a second rule below the OSLandUseTierA rule.
In the second rule, select relativeHeightMaximum from the first drop-down, set the operator in the second drop-down as > (i.e. the more than sign), and type 15 in the input box.
Before continuing, select whether you would like the rules within the group to have an And or an Or condition. In this case, you should select And from the And / Or selector.

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.

Finish creating the recipe

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

Your filter will return results for buildings (Building Part) that have either an education (Education) land use if that building is over 15 metres high or a railway land use (Transport:Rail).

How do I check if filters are used in an existing recipe?

To check what filters have been applied to feature types in an existing recipe:

Log into your OS Data Hub account

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

Navigate to the OS Data Hub workspace

Select Data from the menu bar to view your workspace.

Navigate to the OS Select+Build Recipe Library

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

Find the recipe you want to check for filter presence on

In your OS NGD Select+Build Recipe Library, scroll or search for the recipe you would like to edit. Once you've found the recipe, click on its name; you'll be taken to the Recipe details screen.

Check for filter presence

You are now within the Recipe details screen, where you can view detailed information about the recipe, including the recipe's name, the date it was created, etc. If filters have been applied to the recipe, a filter icon(i.e. a black funnel symbol) will appear under the recipe name alongside text stating: 'Filters have been applied to this recipe'.

Click View all filters to view all of the filters that have been applied to feature types in the recipe.

In the example recipe below, you can see that there is a filter icon(i.e. the black funnel symbol) against the Building Part Feature Type; therefore, this feature type has filters applied to it.

Getting started with data packages

Step-by-step instructions on how to create new data packages, find and download existing ones, and delete data packages.

Adding a data package to your OS Select+Build recipe allows you to select the area, format, and update frequency to receive for your data.

The following sub-sections on this page cover:

How do I create a new data package?

Once you've created a recipe, you'll then need to create a data package against it to receive your OS NGD data.

To create a new OS NGD data package:

Log into your OS Data Hub account

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

Navigate to the OS Data Hub workspace

Select Data from the menu bar to view your workspace.

Navigate to the OS Select+Build Recipe Library

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

Find the recipe you plan to add a data package against

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 details to the data package

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.

Finish creating the data package

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.

Please note:

When you order data through OS Select+Build, the data package/s you receive will be provided at a feature type level. Each feature type you order will be available to download as a .zip file. Currently, grouped files are not available for OS NGD data packages.
Single or multiple data packages can be created from a single defined recipe. Creating multiple data packages from a single recipe is useful if you want to select a different file format or area of interest for a recipe.
The Annual Full Supply order frequency option will not be available for a data package containing one (or more) of the new feature types or new data schema versions of existing feature types released in March and / or September of the current year. If you select an Annual Full Supply frequency for your OS NGD data order in OS Select+Build, we will provide you with the data as it was on 01 January of the current year. This means if a new feature type or a new data schema version of an existing feature type was released after 01 January and you order either of these as part of your Annual Full Supply, you will receive an empty data package for the newly released feature type / new data schema version of an existing feature type. The data for the new feature type / new data schema version of an existing feature type will then be included in your supply on the next 01 January after the release, after which point, data packages containing one of these feature types will no longer contain blank files.

How do I find and download an existing data package?

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

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

Navigate to the OS Data Hub workspace

Select Data from the menu bar to view your workspace.

Navigate to Data packages

Choose Downloads > Data packages from the secondary navigation menu. You will then be taken to your data package list.

Find the data package you're looking for

Scroll through the list to find a particular data package or use the search bar to search by data package name, data package number, or product name.

Data packages linked to an OS NGD recipe

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.

Download the desired data package

Once you have found the data package you want from the list, click the Download button in the Status column.
You are now within the Data package summary screen, where you can view and download files. Under 'Individual file downloads' in the bottom left-hand side of your screen, you will see a .zip file for every feature type in your data package order. Click on a file to download it.

What is the Order Summary file?

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 an Order Summary file contains:

{
 "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
}

How do I delete a data package?

To delete an existing OS NGD data package:

Log into your OS Data Hub account

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

Navigate to the OS Data Hub workspace

Select Data from the menu bar to view your workspace.

Navigate to Data packages

Choose Downloads > Data packages from the secondary navigation menu. You will then be taken to your data package list.

Find the data package you are looking for

Scroll through the list to find a particular data package or use the search bar to search by data package name, data package number, or product name.

Data packages linked to an OS NGD recipe

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.

Delete the package from the data packages summary screen

Click the Package options dropdown in the top right-hand side of your screen.
Click Delete package.

A warning pop up will appear.

Click the Delete package button in the pop up.

Getting started with temporal filtering

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

Introducing temporal filtering

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

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

Things to note

You cannot apply a temporal filter to an existing data package held in your Data packages list; a temporal filter can only be added to new data packages during the data package creation stage.
The earliest date you can request for the majority of feature types in the OS NGD via a temporal filter is 29 September 2022.
As new feature types are added to the OS NGD, their temporal filter range will begin on the date they are added (for example, 28 March 2023 for the Waterbody Catchment Feature Type). Each feature type page states the earliest start date available for temporal filtering on that feature type.
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.

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

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

Log into your OS Data Hub account

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

Navigate to the OS Data Hub workspace

Select Data from the menu bar to view your workspace.

Navigate to the OS Select+Build Recipe Library

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

Find the recipe you want to create a data package against

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 details to the data package

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:

Finish creating your data package

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.

Getting started with GeoPackage

What is GeoPackage?

GeoPackage (.gpkg) is an open, non-proprietary, platform-independent, and standard data format for geographic information systems (GIS), as (OGC). It is designed to be a lightweight format that can contain large amounts of varied and complex data in a single, easy to distribute and ready to use file. GeoPackage is natively supported by numerous software applications.

Key features and benefits of GeoPackage

GeoPackage offers users the following key features and benefits:

The single file is easy to transfer and offers the end-user a rich experience.
Attribute names are not limited in length, making the format user-friendly.
The file size limit is very large at 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.

Accessing GeoPackage data via GIS software

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.

Converting / Loading a GeoPackage to other data formats

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 .

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

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

ArcGIS Pro

Accessing GeoPackage data via ArcGIS Pro

Requirements

ArcGIS Pro (version 1.1 or later)
A GeoPackage dataset

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

Instructions

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

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.

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

A dialog box will appear.

Adding a GeoPackage into ArcGIS Pro

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.

Select all of the relevant layers and 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.

ArcMap

Accessing GeoPackage data via ArcMap

Requirements

ArcMap (version 10.2.2 or later)
A GeoPackage dataset

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

Instructions

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

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

Navigate to the appropriate folder containing the GeoPackage to be uploaded

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

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

Select the layers you want to upload into ArcMap.

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

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

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

Cadcorp SIS

Accessing GeoPackage data via CadCorp

Requirements

CadCorp SIS (version SIS 9 or later)
A GeoPackage dataset

Instructions

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

In the upper ribbon, select Add Overlay.

In the Add Overlay dialog box select Files > File

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

Navigate to the GeoPackage file

Once the correct GeoPackage has been located, click Finish.

The data should now appear on the map.

MapInfo Professional

Accessing GeoPackage data via MapInfo Professional

Requirements

MapInfo Professional (version 15.2 or later)
A GeoPackage dataset

Instructions

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

Select Open > Table in the top ribbon.

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

Locate the GeoPackage in the file explorer and click Open.

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

Select which layers to import into MapInfo Progessional from the GeoPackage

Once the layers have been selected, click OK.

The data should now be available in your workspace.

QGIS

Accessing GeoPackage data via QGIS

Requirements

QGIS (version 2.10.1 or later)
A GeoPackage dataset

Instructions

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

Open a new or existing QGIS project.

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

The Data Source Manager - Vector dialog box will appear.

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

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

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

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

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

FME

Reading GeoPackage data via FME

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

Requirements

FME Desktop
An FME license
A GeoPackage dataset

Instructions

In the FME top ribbon, click the Add Reader button

A dialog box will appear.

The Coordinate System should also be set appropriately.

Click Parameters in the Add Reader dialog box

Another dialog box will appear to specify OGC GeoPackage Parameters.

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

Select the layers to be added into the workbench

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

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

GDAL

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.

Requirements

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

Instructions

Use the ogrinfo program to list information about the GeoPackage

ogrinfo <PATH_TO_GEOPACKAGE>

Example:

ogrinfo wtr_ntwk_waterlinkset.gpkg

ogrinfo output

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

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

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

ogrinfo<PATH_TO_GEOPACKAGE>-so -al

Example:

ogrinfo wtr_ntwk_waterlinkset.gpkg -so -al

ogrinfo detailed output

INFO: Open of `C:\wtr_ntwk_waterlinkset.gpkg'
      using driver `GPKG' successful.
Layer name: wtr_ntwk_waterlinkset
Geometry: Unknown (any)
Feature Count: 116
Extent: (209562.134000, 79229.510000) - (341688.834000, 853194.875000)
Layer SRS WKT:
PROJCRS["OSGB 1936 / British National Grid",
[...]

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

Load the GeoPackage into a PostgreSQL database using the ogr2ogr program

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

ogr2ogr -f PostgreSQL "PG:user=<USERNAME>password=<PASSWORD> dbname=<DATABASENAME>host=<HOST>port=<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.

ogr2ogr -f PostgreSQL "PG:user=example_user password=example_password dbname=postgres host=localhost port=5432 active_schema=example_schema" wtr_ntwk_waterlinkset.gpkg

This will create twp tables in the example_schema schema:

schemaname     | tablename
---------------+---------------------------------
example_schema | wtr_ntwk_waterlinkset
example_schema | wtr_ntwk_waterlinkset_wtrlinkref

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

Getting started with CSV

What is a CSV file?

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

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

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

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

Key features of OS NGD CSV format

CSV offers users the following key features:

Change-Only Update (COU) files are only supplied in CSV format (they are not supplied in GeoPackage format)
Geometry provided as Well-Known Text (WKT)
Header rows included in the file
There will be one record per line in each file
Fields will be separated by commas
Where string fields contain commas, they will be delimited by double quotes
Double quotes inside strings will be escaped by doubling
Records will be terminated by Carriage Returns and Line Feeds
CSV files will be Unicode encoded in UTF-8

Loading CSV files

Loading OS NGD CSV files into databases

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

Prior to loading the data into a database, it is necessary to create the relevant tables in the database. We have supplied the DDL statements that can be accessed in our 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:

COPY destination_schema.destination_table 
    FROM 'source_path_to_csv_file\source_name_of_csv_file.csv'
    DELIMITER ','
    CSV HEADER
    ENCODING 'UTF8';

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:

BULK INSERT destination_schema.destination_table
FROM 'source_path_to_csv_file\source_name_of_csv_file.csv'
WITH (
    FORMAT = 'CSV',
    FIRSTROW = 2
);

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

Post process example

-- Add new geometry column
ALTER TABLE destination_schema.destination_table
ADD new_geometry_column_name geometry;

-- Set new geometry column using existing WKT column
UPDATE destination_schema.destination_table
SET [new_geometry_column_name] =  geometry::STGeomFromText(destination_table.geometry, /* EPSG_CODE_OF_GEOM */); 

-- Optional drop original WKT column
ALTER TABLE destination_schema.destination_table
DROP COLUMN geometry;

Computed column example

ALTER TABLE destination_schema.destination_table
ADD new_computed_column_name AS
    geometry::STGeomFromText(destination_table.geometry, /* EPSG_CODE_OF_GEOM */) persisted;

It is not possible to 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.

Processing COUs

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

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

Database software
Data loading method or software
Feature retention and lifecycle requirements

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

Feature retention options

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

Latest feature view
Full feature archive

Latest feature view

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

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

Change type

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

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

changetypevalue

Action

New

Insert as a new feature

Moved From A Different Feature Type

Insert as a new feature

End Of Life

Delete existing feature based on unique identifier

Moved To A Different Feature Type

Delete existing feature based on unique identifier

Modified Attributes

Update the record (see section below)

Modified Geometry

Update the record (see section below)

Modified Geometry And Attributes

Update the record (see section below)

Version dates

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

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

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

Full feature archive

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

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

Getting started with attribute filtering

Step-by-step instructions on how to add attribute filters to recipes in your OS Select+Build Recipe Library.

Introducing attribute filtering

Attribute filtering is an optional step for those with advanced OS data knowledge.

You can:

Add attribute filters to feature types in a new recipe
Add, edit or remove attribute filters to / in / from feature types in an existing recipe

The following sub-sections cover:

How do I add attribute filters to a new recipe?

To add attribute filters to a new recipe:

Log into your OS Data Hub account

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

Navigate to the OS Data Hub workspace

Select Data from the menu bar to view your workspace.

Navigate to the OS Select+Build Recipe Library

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

Create a recipe

Click the Create a new recipe button, adding the relevant details to your recipe.

See the Managing OS Select+Build recipes page for more information on creating recipes.

Add filters to feature types in your recipe

Click the filter icon next to the feature type(s) you want to add a filter to in the theme selection tree.

The Advanced Filter Options panel will then slide into view from the right and you can begin to build your filter(s):

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

Finish creating the recipe

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

How do I add attribute filters to an existing recipe?

To add attribute filters to an existing recipe:

Log into your OS Data Hub account

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

Navigate to the OS Data Hub workspace

Select Data from the menu bar to view your workspace.

Navigate to the OS Select+Build Recipe Library

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

Find the recipe you want to edit

In your OS NGD Select+Build Recipe Library, scroll or search for the recipe you would like to edit. Once you've found the recipe, click on its name; you'll be taken to the Recipe details screen.

Edit the recipe

In the Recipe details screen, click on the Recipe actions dropdown and select Edit recipe.

You'll now be able to add filters (see Step 6) or remove filters (see Step 7) from feature types in the recipe.

Add a filter to a feature type

Click the filter icon next to the feature type you want to add a filter to in the selection tree for the recipe.

The Advanced Filter Options panel will then slide into view from the right and you can begin to build your filter(s):

For a simple filter, select +Add rule.
For a more complex nested filter, select +Add group.
Once you have added all of your relevant filters, click Apply Filter.

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

Remove a filter from a feature type

Click the Edit filter iconnext to the feature type you want to remove a filter from in the selection tree for the recipe.
When the Advanced Filter Options panel slides into view from the right, select Clear all filters.

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

Worked example of creating a simple filter

Log into your OS Data Hub account

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

Navigate to the OS Data Hub workspace

Select Data from the menu bar to view your workspace.

Navigate to the OS Select+Build Recipe Library

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

Create a new recipe

Click the Create a new recipe button.

See the Managing OS Select+Build recipes page for more information on creating recipes.

Add details to the recipe

Give your recipe a descriptive name.
Add a detailed description for your recipe
Select your OS NGD data by choosing the themes, collections and feature types you want to include in your recipe. For this worked example:
- Click on the arrow to the right of Buildings within the theme selection tree to see the collections available within the theme, then click on the arrow to the right of Buildings Features to see the feature types available within that collection.
- Click on the check box next to Building Part to select that feature type.

Add a filter to the Building Part Feature Type where the OS Land Use Tier A attribute is set to Education

Click on the filter icon to the right of Building Part.

The Advanced Filter Options panel will slide into view from the right, where you can begin to build your filter(s):

In the Advanced Filter Options panel, click + Add rule, then select OSLandUseTierA from the first drop-down.

Leave the operator in the second drop-down as: = (i.e. the equal sign), then select Education from the third drop-down.

Click the Apply filter button.

Finish creating the recipe

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

Your filter will return buildings where education (Education) is recorded as the land use (OS Land Use Tier A attribute).

Worked example of creating a nested filter

Follow the steps outlined above for creating a simple filter for Building Part until you reach the Advanced Filter Options panel step (Step 6).

Add a simple filter to the Building Part Feature Type

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.

Add a nested filter to the Building Part Feature Type

Click + Add rule to add a second rule below the OSLandUseTierA rule.
In the second rule, select relativeHeightMaximum from the first drop-down, set the operator in the second drop-down as > (i.e. the more than sign), and type 15 in the input box.
Before continuing, select whether you would like the rules within the group to have an And or an Or condition. In this case, you should select And from the And / Or selector.

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.

Finish creating the recipe

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

Your filter will return results for buildings (Building Part) that have either an education (Education) land use if that building is over 15 metres high or a railway land use (Transport:Rail).

How do I check if filters are used in an existing recipe?

To check what filters have been applied to feature types in an existing recipe:

Log into your OS Data Hub account

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

Navigate to the OS Data Hub workspace

Select Data from the menu bar to view your workspace.

Navigate to the OS Select+Build Recipe Library

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

Find the recipe you want to check for filter presence on

In your OS NGD Select+Build Recipe Library, scroll or search for the recipe you would like to edit. Once you've found the recipe, click on its name; you'll be taken to the Recipe details screen.

Check for filter presence

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.

Downloading with OS Select+Build

What is OS Select+Build?

File formats available with OS Select+Build

What's different about OS Select+Build?

Using OS Select+Build

Getting started with recipes

What is a recipe?

Using OS Select+Build recipes

Things to remember

Managing OS Select+Build recipes

How do I create a new recipe?

Log into your OS Data Hub account

Navigate to the OS Data Hub workspace

Navigate to the OS Select+Build Recipe Library

Choose Create a new recipe

Add details to the recipe

(Optional) Choose a data schema version

Finish creating the recipe

Please note

What's next?

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

Log into your OS Data Hub account

Navigate to the OS Data Hub workspace

Navigate to the OS Select+Build Recipe Library

How do I check what's in a recipe?

Log into your OS Data Hub account

Navigate to the OS Data Hub workspace

Navigate to the OS Select+Build Recipe Library

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

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

How do I delete a recipe?

Log into your OS Data Hub account

Navigate to the OS Data Hub workspace

Navigate to the OS Select+Build Recipe Library

Find the recipe you want to delete

Open the detailed recipe view

Open the recipe actions dropdown

Delete the recipe

Editing OS Select+Build recipes

How do I edit the name of my recipe?

Log into your OS Data Hub account

Navigate to the OS Data Hub workspace

Navigate to the OS Select+Build Recipe Library

Select the recipe you want to edit

View recipe details

Click the edit icon next to the recipe name

Change the name of the recipe

Save changes to the recipe

How do I edit the description of my recipe?

Log into your OS Data Hub account

Navigate to the OS Data Hub workspace

Navigate to the OS Select+Build Recipe Library

Select the recipe you want to edit

View recipe details

Click the edit icon next to the recipe name

Change the description of the recipe

Save changes to the recipe

How do I edit a recipe?

Log into your OS Data Hub account

Navigate to the OS Data Hub workspace

Navigate to the OS Select+Build Recipe Library

Select the recipe you want to edit from the list

Edit recipe data

Save changes to your recipe

Recipes with data packages linked to them that receive COUs

Sharing OS Select+Build recipes

How do I share a recipe?

Log into your account

Navigate to the OS Data Hub workspace

Navigate to the OS Select+Build Recipe Library

Find the recipe you want to share

Select share recipe with your organisation from the recipe actions dropdown

Choose the correct organisation from the recipe dialog

Add a descriptive message about the recipe

How do I accept a recipe shared with me?

Log into your account

Open the notification menu

View details of the received recipe

Accept the shared recipe

How do I reject a recipe shared with me?