Core+ PropertyResilience – Output specification

Here we document some of the outputs you will find in your Core+ PropertyResilience reports.

Reports are generated at the level of individual parcels and will contain information about all the buildings in the parcel. In addition to the fields specified in this document, we also include some of the original informational fields found in the source cadastral and buildings layers so the output can easily be cross-referenced with other data sources.

The following fields are computed for every building, and are available in the XLSX, CSV, GeoPackage, and JSON outputs, and most of these (but not all) are also shown in the PDF reports.  Reports contain information from events with several different return periods, and the values in the table below are supplied for each of these events where applicable (indicated with a T[x]- prefix for an x-year event).

ClassDescriptionField names [units]
RainThe rain depth used for the region the building is in for the relevant return period. If you set the rain slider in the Flash Flood Map to this amount, you will see the flooding extents used for the report for the property.T[x]-rain [m]:  The rain depth for the region containing the building.
Wetted perimeter

Consider the terrain adjacent to the building, parts of this terrain may be flooded resulting in standing water up against the sides of the building. We compute the length of the perimeter that has standing water (the wetted perimeter). Additionally we provide the surface area of the perimeter that is covered by standing water, e.g. if a 10 m long building has 10 cm of water standing up against it, 10 m * 10 cm = 1 m² of the building's sides is affected by standing water, making up the wetted area.

shape_len [m]: total length of the building perimeter.
T[x]-wetted-perimeter [m]: the wetted perimeter of the building.
T[x]-wetted-perimeter-10cm [m]: the wetted perimeter of a building considering only sections where the depth is at least 10 cm.
T[x]-wetted-area [m²]: the area of the sides of the building that is wet.

Maximum  water depthWe find the maximum depth of the water adjacent to the building and provide the coordinates for this location as well.

T[x]-max-depth [m]: The maximum depth adjacent to the building.
T[x]-x [m], T[x]-y [m]: Easting and northing of the location of max-depth in the country's default coordinate system.

Watershed area

There can also be large flow paths with large upstream areas close to the building, they can be problematic as well and are therefore included in the report. 

T[x]-max-upstream [m²]: The largest flow path within 3 meters.
Note: The value stored here is the maximum of the value found at the current return period and the ones found from shorter return periods.
Risk scoreAs described in the introduction, we compute an overall risk score for each parcel, as well as an individual risk score for each building.

risk-score [number]: The numeric risk score.
risk-name [string]: The human-readable name of the risk score.

Buildings also include all fields from the parcel they're in, including sc_parcel_id, which can be used to match buildings with corresponding parcels.

Note: the JSON output is carefully structured to make the output easier to understand and to reduce redundancy. This hierarchy is ignored above. The structure of the document is described in the API documentation, but it can also be readily understood from downloading an example.

Building and property fields from source layers

For convenience, we include some of the original fields from the national cadastral and building layers used in PropertyResilience. For instance, this includes the original identifiers of the parcels and buildings.  In the spreadsheet and GeoPackage formats, you will find these properties mixed in with the properties mentioned on this page. For the JSON output, these properties are separated. Therefore, if a field in a PropertyResilience report is not in the table above, is it likely one of those fields and we refer to the relevant national dataset for more information. If you are in doubt you are always welcome to contact support.