> For the complete documentation index, see [llms.txt](https://docs.os.uk/more-than-maps/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/more-than-maps/using-buildings/identifying-higher-risk-buildings-in-arcgis-pro.md).
# Identifying Higher-Risk Buildings in ArcGIS Pro
This describes a step-by-step guide using ArcGIS Pro how you can identify if a building in occupation is classified as Higher-Risk by the Building Safety Act 2022 and the Higher-Risk Buildings (Descriptions and Supplementary Provisions) Regulations 2023 using OS NGD data.
This article follows on from [Identifying higher-risk buildings recipe guide on the OS Docs platform](https://docs.os.uk/osngd/getting-started/downloading-with-os-select+build/getting-started-with-os-recommended-recipes/identifying-higher-risk-buildings-recipe-guide) that will guide you through accessing the data needed for the article below.
Create a new ArcGIS Pro Project and add your preferred backdrop mapping. In this example, OS Maps API Light is being used.
Add the 2 feature types you have downloaded from OS Data Hub to a map and order them in table of contents so that `main.add_gb_builtaddress` sits above `main.bld_fts_building`.
Change the symbology as desired.
Select the `Analysis` option from the top ribbon and then click `Tools`. This will open the geoprocessing pane, usually docked on the right-hand side of screen. Either type `Spatial Join` into the *Find Tools* search or select toolboxes and locate the `Spatial Join` tool in the `Analysis Tools` toolbox. Open the tool.
* Set the target features as the `main.bld_fts_building` layer and join features as the `main.add_gb_builtaddress` layer.
* Select an output feature class location and suitable file name.
* Ensure join operation is set to `join one to one`.
* Un tick `Keep All Target Features`.
* Ensure `Match Option` is set to ‘Intersect’.
* Expand the `Field Map` options and select all the attributes drawn from the `main.add_gb_builtaddress` feature type and remove them. They will start from the attribute UPRN.
* Run the tool.
Viewing the new layer you will see that a reduced number of building features have been returned however there is an additional step required to ensure all the criteria have been met. Open the layers attribute table and sort the newly created `Join_Count` attribute in ascending order.
One of the criteria for a Higher-Risk Building is that there are 2 or more residential addresses. From reviewing the `Join_Count` attribute, we can see that there are several buildings with only a single join. This is complicated by the fact that serviced apartments / aparthotels often don’t have individual addresses but do fall within the criteria for Higher-Risk Buildings. We will use an attribute query in the Select By Attributes dialogue box to identify non-commercial buildings where is only a single address.
```sql
(Join_Count < 2 And buildinguse_oslandusetiera <> 'Temporary Or
Holiday Accommodation') Or (Join_Count < 2 And
buildinguse_oslandusetiera IS NULL)
```
Now select the `Edit` option from the top ribbon and `Delete` the selected rows. Save your edits. You now have a feature class that contains all buildings that are considered Higher-Risk.
---
# 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/more-than-maps/using-buildings/identifying-higher-risk-buildings-in-arcgis-pro.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.