Core+ PropertyResilience – Introduction

Core+ PropertyResilience generates flood resilience reports by extracting relevant flood risk parameters from Scalgo's national analyses at the level of cadastral parcels.  Reports can be generated either as an end-user friendly PDF document per parcel, or batched, for anything from a handful of parcels to nationwide portfolios.  Batch reports are delivered in spreadsheet, GIS, or other formats ready for further processing.  Each form of report contains relevant flood-related metrics both on a per-building level, as well as an aggregated resilience score per building and per parcel.

Report background

To generate a PropertyResilience report for a parcel, we start by extracting data at the building level using the Scalgo Live Flash Flood Map with infiltration and drainage, around the buildings on the parcel.  We use the standard rain events available for the country to determine the amounts of rain to consider for each building, for a number of common to rare rainfall scenarios - this data forms the basis of the resilience score. PropertyResilience works out of the box without any further configuration.

There are two ways to retrieve a report: using a simple user interface inside Scalgo Live, or through an API that can be used to invoke the service in third-party software. This is used for generating reports in bulk.  The same report formats are available independent of whether you use the Scalgo Live UI or the API.

The simplest way to get a report is via the Scalgo Live UI:

1. Enable the cadastral layer relevant for your country, consult the table below to find the right layer, or click the link to go directly to Scalgo Live.
2. Enable the Point Query tool from the toolbar and click on a parcel.
3. Under Point Info in the right sidebar, click the PropertyResilience report button.
4. Select the desired format and generate the report.

Note: If the button does not appear, please make sure your user account has access to Core+ PropertyResilience, and you've enabled the right cadastral parcel layer, e.g. by opening Scalgo Live through the links in the Quick Start table.

Quick start links

Use the links in the table below to open Scalgo Live with the right cadastral map activated for generating reports.

For generating reports in bulk or integrating with your company's workflow, use the PropertyResilience API.

Documentation

Technical documentation (openapi.json) and a human-readable description of how the API works (index.html) are available for developers.

Note: To access these links, you need to have a Scalgo Live account and access to Core+ PropertyResilience.

Sample code

A Python sample application (apiclient.py) is provided to help developers get started quickly.

If you have any technical questions, you are very welcome to contact Scalgo Live support.

Parcel identification

To get the result for a parcel you need its official ID, or you can query via a point that is located inside the parcel.  If you do not have official parcel IDs, but only addresses, we recommend using a geocoding service that uses national authoritative data sources. This ensures alignment with the authoritative cadastral maps used in Scalgo Live.

Please see the API documentation above for more information about the exact query formats available in each country.

PropertyResilience can generate reports in the formats listed below.  Please consult the output specification documentation for a detailed description of what kind of information and field names we provide in these formats.

PDF report

A report summarizing the findings in three sections with increasing detail: a single-page overview of building resilience scores; a per-building overview with score, building characteristics (type, area, etc.), and a location graphic; and per-building, per-event details showing the metrics underlying the resilience score for the building.

Spreadsheet (.xlsx or .csv)

A spreadsheet document with a sheet for parcels and a sheet with individual buildings, either in Microsoft Excel format or as a pair of CSV files.

The sheets contain informational fields from the authoritative parcel and building datasets, resilience scores for parcels and buildings, as well as per-event detailed numbers from different risk sources used to determine the resilience scores.

GeoPackage (.gpkg)

A GeoPackage with two polygonal layers: buildings and parcels. This format is similar to the spreadsheet format, and includes the same data fields, but you also get the geometries of the building footprints and parcels. As such, it can be used for visualization as well as for further processing in GIS.

JSON

This format includes the same data as the spreadsheets, but in a much more structured way, suited for automated processing. For example, you can process the output in your own scripts and implement your own business logic.

A PropertyResilience report, regardless of its format, contains a risk score. Each parcel has an overall risk score, and each building in the parcel gets its own risk score as well.  The risk score gives a quick understanding of the risk of a particular parcel or building. Scalgo Live uses the following color-coded risk levels:

The risk levels are based on the Scalgo Live Flash Flood Map with infiltration and drainage.  The level is computed taking into account the return periods of the various rain events and the hydrological properties of the Flash Flood Map.

The key usage metric for Core+ PropertyResilience is parcels queried. If you are an organization administrator, you can see your organization's usage within the current billing period, and the previous, through the account dashboard in the "Billing Statistics" section. Here are some key things to keep in mind with this statistic:

• It does not matter how many buildings are on the individual parcels, only the number of parcels is counted.
• The number of API queries you use to query the parcels is not important. Five queries of one parcel is counted the same as a single batch query of five parcels.
• If there are no buildings on the parcel, the query fails. This does not count as a queried parcel.
• If a parcel cannot be found for the given query parameter, the query fails. This does not count as a queried parcel.

If you have any questions regarding this, feel free to contact support.