> 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/getting-started/downloading-with-os-select+build/getting-started-with-os-recommended-recipes/identifying-crossing-points-and-bottlenecks-recipe-guide.md). # Identifying crossing points and bottlenecks recipe guide A guide with detailed step-by-step instructions outlining how you can create a recipe in OS Select+Build to identify the location of bridges, tunnels, fords and crossing points. ## What is the identifying crossing points and bottlenecks recipe? The guide below provides a geospatial toolkit for helping you identify the location of bridges, tunnels, fords and crossing points using the OS NGD; its step-by-step instructions outline how to select relevant pieces of addressing, structures, transport and water data from the OS NGD and weave them into a recipe. {% hint style="info" %} ## Definitions For this recipe guide: * We define a **crossing point** as a feature where a pedestrian or vehicle passes over or under another feature. * We define a **bottleneck** as a feature that could restrict or channel the movement of pedestrians or vehicles. {% endhint %} ### Use cases The recipe will be useful for organisations (particularly emergency services) that need to understand critical infrastructure and mobility restrictions for vehicles and pedestrians. Use cases for the recipe include: * Understanding mobility constraints for pedestrians and vehicles in communities * Planning road closures * Managing evacuations * Predicting the movement patterns of crowds * Identifying choke points for exceptional loads / large vehicles * Identifying if services can access different communities * Incident response planning and situational awareness * Mapping critical infrastructure * Modelling transport routes ### Feature types required In this recipe, we'll be identifying the exact location of the four types of features using point and topographic features, so we'll be excluding generic network data representations. The following four feature types are included in the identifying crossing points and bottlenecks recipe: | Theme | Collection | Feature Type | | ----------------- | --------------------- | ----------------------------------------------------------------------------------------------- | | OS NGD Address | OS GB Address | [Non Addressable Object](/osngd/data-structure/address/gb-address/non-addressable-object.md) | | OS NGD Structures | OS Structure Features | [Compound Structure](/osngd/data-structure/structures/structure-features/compound-structure.md) | | OS NGD Transport | OS Transport Features | [Road Track Or Path](/osngd/data-structure/transport/transport-features/road-track-or-path.md) | | OS NGD Water | OS Water Features | [Water Point](/osngd/data-structure/water/water-features/water-point.md) | {% hint style="info" %} ## Note about adapting or skipping filtering * You can adapt the suggested identifying crossing points and bottlenecks recipe at the recipe creation or editing stage so that it fully meets your needs. The filters chosen for this recipe (see steps 8 to 11 below) are a suggestion and you can amend them depending on your requirements. * Applying filters in OS Select+Build to the four feature types at the recipe creation (or recipe editing) stage lets you target the right types of bridges, tunnels and crossings. Filtering will also reduce the number of features being downloaded as you'll just be downloading a subset of the features available for each feature type selected. * If preferred, you can skip the filtering steps (8 to 11 below) at the recipe creation stage, download all features for the four feature types, then subsequently filter the data later in your chosen geographic information system (GIS) or relational database management system (RDBMS). {% endhint %} ### Types of bridges, tunnels and crossings included Types of bridges included and links to the code lists that define them:
Type of BridgeLink to the Code List(s) Containing the Definition(s) for the Infrastructure Feature(s)
BridgeBridge is defined in the Compound Structure Description Value Code List
Transporter BridgeTransporter Bridge is defined in the Compound Structure Description Value Code List
FootbridgeFootbridge is defined in Compound Structure Description Value Code List
Footbridge / WalkwayFootbridge / Walkway is defined in Address Classification Description Value Code List
Clapper BridgeClapper Bridge is defined in the Compound Structure Description Value Code List
Lift BridgeLift Bridge is defined in the Compound Structure Description Value Code List
Swing BridgeSwing Bridge is defined in the Compound Structure Description Value Code List
Types of tunnels included and links to the code lists that define them:
Type of TunnelsLink to the Code List(s) Containing the Definition(s) for the Infrastructure Feature
Rail TunnelRail Tunnel is defined in the Compound Structure Description Value Code List
Tube Or Metro TunnelTube Or Metro Tunnel is defined in the Compound Structure Description Value Code List
Pedestrian Tunnel Or SubwayPedestrian Tunnel Or Subway is defined in the Compound Structure Description Value Code List
UnderpassUnderpass is defined in the Compound Structure Description Value Code List
Canal TunnelCanal Tunnel is defined in the Compound Structure Description Value Code List
Types of crossings included and links to the code lists that define them:
Type of CrossingLink to the Code List(s) Containing the Definition(s) for the Infrastructure Feature
Level CrossingLevel Crossing is defined in the Address Classification Description Value Code List and Road Track Or Path Description Value Code List
Railway Pedestrian CrossingRailway Pedestrian Crossing is defined in the Address Classification Description Value Code List
Pedestrian CrossingPedestrian Crossing is defined in the Road Track Or Path Description Value Code List
FordFord is defined in the Water Point Description Value Code List and Road Track Or Path Description Value Code List
## Creating the recipe To create the identifying crossing points and bottlenecks recipe in OS Select+Build: {% stepper %} {% step %} ### Log into your [OS Data Hub](https://osdatahub.os.uk/) account Click *Log in* on the OS Data Hub menu bar to log into your account.
A screenshot of the OS Data Hub home page showing the sign up and log in buttons in the top right hand corner

Screenshot showing the OS Data Hub homepage.

{% endstep %} {% step %} ### Navigate to the OS Data Hub workspace Select *Data* from the menu bar to view your workspace. {% endstep %} {% step %} ### Navigate to the OS Select+Build Recipe Library Choose *Downloads* > *OS Select+Build Recipe Library* from the left-hand-side secondary navigation menu.
Screenshot of the OS Select+Build Recipe Library screen in the OS Data Hub.

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

{% endstep %} {% step %} ### Choose Create a new recipe Click the *Create a new recipe* button at the top right-hand-side of the screen. {% endstep %} {% step %} ### Give the recipe a name and description * Give your recipe a descriptive name in the *Recipe name* dialog box on the left-hand-side of the screen. * Add a detailed description for your recipe (this is optional, but it's useful if other team members will be accessing the recipe). {% endstep %} {% step %} ### Select the feature types Select your OS NGD data by choosing the themes, collections and feature types you want to include in your recipe. You'll need to select the following four feature types from the *Themes* panel on the left-hand-side of the screen: * Non Addressable Object (found within *Address* > *GB Address* > *Non Addressable Object*) * Compound Structure (found within *Structures* > *Structure Features* > *Compound Structure*) * Road Track Or Path (found within *Transport* > *Transport Features* > *Road Track Or Path*) * Water Point (found within *Water* > *Water Features* > *Water Point*) {% hint style="info" %} **Note:** Only these four individual feature types are needed for this recipe – do not select all feature types from the OS GB Address, OS Structure Features, OS Transport Features and OS Water Features Collections. {% endhint %}
Screenshot showing the tree view in the secondary navigation menu that opens when you create a recipe in OS Select+Build in the OS Data Hub. Three of the four feature types needed for the identifying crossing points and bottlenecks recipe are shown to have been selected in this screenshot: Compound Structure, Road Track Or Path, and Water Point; Non Addressable Object has also been selected, but isn't visible in the screenshot.

Screenshot showing the tree view in the secondary navigation menu that opens when you create a recipe in OS Select+Build in the OS Data Hub. Three of the four feature types needed for the identifying crossing points and bottlenecks recipe are shown to have been selected in this screenshot: Compound Structure, Road Track Or Path, and Water Point; Non Addressable Object has also been selected, but isn't visible in the screenshot.

{% endstep %} {% step %} ### (Optional) Choose a data schema version Selecting a data schema version for a feature type is an optional step; if you don't choose a particular data schema version for a feature type, OS Select+Build will always select the latest available data schema version for you for each feature type by default. We recommend using the pre-selected latest data schema version for feature types unless you have a specific need to use an earlier one. (See the [Data schema versioning page](/osngd/getting-started/os-ngd-fundamentals/data-schema-versioning.md) for more information on data schema versioning in the OS NGD.) If you wish to choose which schema version (where applicable) you'd like to receive the data in for a feature type, click on the feature type name within the tree view in the secondary navigation menu, then choose a data schema version from the *Choose Data Schema* drop-down box in the right-hand side panel.
Screenshot showing the tree view in the secondary navigation menu that opens when you create a recipe in OS Select+Build in the OS Data Hub. The Compound Structure Feature Type has been selected in this screenshot and the Choose Schema Version drop-down menu is visible in the right-hand-side panel, which lets you select the data schema version you want to use for the feature type.

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

{% endstep %} {% step %} ### Add a filter to the Non Addressable Object Feature Type {% hint style="info" %} ## Why are filters needed in this recipe? OS Select+Build provides the option to apply filters on certain attributes when creating a recipe so that only the features and attribution that are needed are included in the data. * A filter is required on the Non Addressable Object Feature Type on the Classification Description attribute so that only level crossing and railway pedestrian crossing addresses appear in the data. * A filter is required on the Compound Structure Feature Type on the Description attribute so that 12 specified infrastructure types (for example, road tunnels, footbridges and swing bridges) appear in the data. * A filter is required on the Road Track Or Path Feature Type on the Description attribute so that only fords, level crossings and pedestrian crossings appear in the data. * A filter is required on the Water Point Feature Type on the Description attribute so that only fords and tidal fords appear in the data. Filters need to be set one at a time for the feature types that need to use them. {% endhint %} To add a filter to the Non Addressable Object Feature Type: * Click on the *filter icon* Filter icon in OS Select+Build to the right of Non Addressable Object in the theme selection tree (make sure you select Non Addressable Object from the GB Address drop-down, not from the Islands Address drop-down).
Screenshot of the theme selection tree in OS Select+Build with the filter icon highlighted beside Non Addressable Object.

Screenshot of the theme selection tree in OS Select+Build with the filter icon highlighted beside Non Addressable Object.

*The Advanced Filter Options panel will then slide into view from the right-hand side of the screen and you can begin to build your filter.* In the Advanced Filter Options panel: * Click *the + Add rule* button twice, which will give you two rules. * In the first rule, select *classificationDescription* from the first drop-down, leave the operator in the second drop-down as: = (the equal sign), then select *Level Crossing* from the third drop-down. * In the second rule, select *classificationDescription* from the first drop-down, leave the operator in the second drop-down as: = (the equal sign), then select *Railway Pedestrian Crossing* from the third drop-down. * Before continuing, select whether you would like the rules within the group to have an And or an Or condition. In this case, you should select *Or* from the And / Or selector.
Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build. The two rules filter options selected for the Non Addressable Object Feature Type are shown in this screenshot.

Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build. The two rules filter options selected for the Non Addressable Object Feature Type are shown in this screenshot.

* Click the *Apply filter* button. * Close the Advanced Filter Options panel. {% endstep %} {% step %} ### Add a filter to the Compound Structure Feature Type To add a filter to the Compound Structure Feature Type: * Click on the *filter icon* Filter icon in OS Select+Build to the right of Compound Structure in the theme selection tree.

Screenshot of the theme selection tree in OS Select+Build with the filter icon highlighted beside Compound Structure.

*The Advanced Filter Options panel will then slide into view from the right-hand side of the screen and you can begin to build your filter.* In the Advanced Filter Options panel: * Click *the + Add rule* button 12 times, which will give you 12 rules. * In the first rule, select *Description* from the first drop-down, leave the operator in the second drop-down as: = (the equal sign), then select *Bridge* from the third drop-down. * In the second rule, select *Description* from the first drop-down, leave the operator in the second drop-down as: = (the equal sign), then select *Transporter Bridge* from the third drop-down. * Repeat this process for rules 3 to 12; for each rule, select *Description* from the first drop-down, leave the operator in the second drop-down as: = (the equal sign), then select the following options from the third drop-down (until the Advanced Filter Options panel looks like the example screenshot below): * Rail Tunnel * Road Tunnel * Tube Or Metro Tunnel * Footbridge * Pedestrian Tunnel Or Subway * Underpass * Clapper Bridge * Lift Bridge * Swing Bridge * Canal Tunnel *(You may also notice there is another attribute called Status, which is an* *indicator of whether the feature is currently performing its original function; for this recipe, we want all infrastructure, but we can filter on the Status attribute in our GIS or RDBMS after download.)* * Before continuing, select whether you would like the rules within the group to have an And or an Or condition. In this case, you should select *Or* from the And / Or selector.
Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build. The 12 rules filter options selected for the Compound Structure Feature Type are shown in this screenshot.

Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build. The 12 rules filter options selected for the Compound Structure Feature Type are shown in this screenshot.

* Click the *Apply filter* button. * Close the Advanced Filter Options panel. {% endstep %} {% step %} ### Add a filter to the Road Track Or Path Feature Type To add a filter to the Road Track Or Path Feature Type: * Click on the *filter icon* Filter icon in OS Select+Build to the right of Road Track Or Path in the theme selection tree.
Screenshot of the theme selection tree in OS Select+Build with the filter icon highlighted beside Road Track Or Path.

Screenshot of the theme selection tree in OS Select+Build with the filter icon highlighted beside Road Track Or Path.

*The Advanced Filter Options panel will then slide into view from the right-hand side of the screen and you can begin to build your filter.* In the Advanced Filter Options panel: * Click *the + Add rule* button three times, which will give you three rules. * In the first rule, select *Description* from the first drop-down, leave the operator in the second drop-down as: = (the equal sign), then select *Ford* from the third drop-down. * In the second rule, select *Description* from the first drop-down, leave the operator in the second drop-down as: = (the equal sign), then select *Level Crossing* from the third drop-down. * In the third rule, select *Description* from the first drop-down, leave the operator in the second drop-down as: = (the equal sign), then select *Pedestrian Crossing* from the third drop-down. * Before continuing, select whether you would like the rules within the group to have an And or an Or condition. In this case, you should select *Or* from the And / Or selector.
Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build. The three rules filter options selected for the Road Track Or Path Feature Type are shown in this screenshot.

Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build. The three rules filter options selected for the Road Track Or Path Feature Type are shown in this screenshot.

* Click the *Apply filter* button. * Close the Advanced Filter Options panel. {% endstep %} {% step %} ### Add a filter to the Water Point Feature Type To add a filter to the Water Point Feature Type: * Click on the *filter icon* Filter icon in OS Select+Build to the right of Water Point in the theme selection tree.
Screenshot of the theme selection tree in OS Select+Build with the filter icon highlighted beside Water Point.

Screenshot of the theme selection tree in OS Select+Build with the filter icon highlighted beside Water Point.

*The Advanced Filter Options panel will then slide into view from the right-hand side of the screen and you can begin to build your filter.* In the Advanced Filter Options panel: * Click *the + Add rule* button twice, which will give you two rules. * In the first rule, select *Description* from the first drop-down, leave the operator in the second drop-down as: = (the equal sign), then select *Ford* from the third drop-down. * In the second rule, select *Description* from the first drop-down, leave the operator in the second drop-down as: = (the equal sign), then select *Tidal Ford* from the third drop-down. * Before continuing, select whether you would like the rules within the group to have an And or an Or condition. In this case, you should select *Or* from the And / Or selector.
Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build. The two rules filter options selected for the Water Point Feature Type are shown in this screenshot.

Screenshot of creating a filter in the Advanced Filter Options panel in OS Select+Build. The two rules filter options selected for the Water Point Feature Type are shown in this screenshot.

* Click the *Apply filter* button. * Close the Advanced Filter Options panel. {% endstep %} {% step %} ### Finish creating the recipe Once you have applied filters to the four feature types, click the *Create recipe* button to complete the recipe creation process. Your new recipe will now instantly be available in your OS Select+Build Recipe Library. You can view a summary of the completed identifying crossing points and bottlenecks recipe, including the required feature types and filters, if you click *Data* > *Downloads* > *OS Select+Build Recipe Library* > \**your recipe's name*\* > *View all filters*. The recipe summary should look like the screenshot below:
Screenshot of the OS Select+Build Recipe details screen showing a summary of the identifying crossing points and bottlenecks recipe, including selected feature types and their data schema versions, plus all filters applied.

Screenshot of the OS Select+Build Recipe details screen showing a summary of the identifying crossing points and bottlenecks recipe, including selected feature types and their data schema versions, plus all filters applied.

{% endstep %} {% endstepper %} *** ## What's next? ### Further guidance on creating, editing and deleting recipes More information on creating, editing and deleting recipes in OS Select+Build and on adding attribute filters to recipes can be found in the following guides:

πŸ“– Getting started with recipes guides

Getting started with recipes

🎯 Getting started with attribute filtering guide

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

πŸ“š Getting started with data packages guide

Getting started with data packages
### Create a map to identify crossing points and bottlenecks from your recipe Once you've created your recipe and added a data package to it to receive the data, you can import the data into your chosen GIS (geographic information system) to analyse it or create maps. The following guide gives an example of how to create a map in QGIS, standardise the geometry of the datasets and, if required, standardise the data into one layer using common attributes:

πŸ—ΊοΈ Guide for using QGIS to standardise data for identifying crossing points and bottlenecks in OS NGD data

https://docs.os.uk/more-than-maps/using-topographic-features/standardising-data-for-crossing-points-and-bottlenecks-in-qgis
--- # 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/getting-started/downloading-with-os-select+build/getting-started-with-os-recommended-recipes/identifying-crossing-points-and-bottlenecks-recipe-guide.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.