Data Fields¶
When wildcat runs an assessment, it stores a variety of data fields (often called properties) in the output segments.geojson
and basins.geojson
files. Users may read these fields directly from the output files, or use the export command to extract specific variables of interest. Users can also use the export command to rename data fields from their default names. The remainder of this page describes these data fields and various export options.
Assessment Properties¶
When wildcat runs an assessment, it saves a variety of data fields in the output segments.geojson
and basins.geojson
files. First are a set of variables characterizing the stream segment watersheds:
Watershed Variable |
Description |
Units |
---|---|---|
|
A unique, constant ID for each segment in the network. Set during network delineation. |
N/A |
|
Total catchment area |
Square kilometers (km²) |
|
The proportion of catchment area that is outside the fire perimeter |
From 0 to 1 |
|
The proportion of burned catchment area. |
From 0 to 1 |
|
The average slope gradient along the stream segment. |
Gradient |
|
The average confinement angle along the stream segment |
Degrees |
|
The total developed catchment area |
Square kilometers (km²) |
Next are a series of boolean (0/False or 1/True) variables used to implement network filtering:
Filter Check |
Description |
---|---|
|
True if the segment intersects an included area mask. |
|
True if the segment’s catchment exceeds the maximum size |
|
True if the segment passes either of the perimeter or physical filtering criteria |
|
True if the segment passes the fire perimeter criterion |
|
True if the segment intersects the fire perimeter |
|
True if the segment’s catchment is considered outside the fire perimeter |
|
True if the segment passes the physical criterion |
|
True if a sufficient proportion of the catchment area is burned |
|
True if the segment has a sufficiently steep slope gradient |
|
True if the segment has a sufficiently low confinement angle |
|
True if the segment’s catchment is sufficiently undeveloped. |
|
True if a segment should be retained to preserve flow continuity. |
And then a series of variables used as inputs to the hazard assessment models:
Model Input |
Description |
---|---|
|
Terrain variable for the M1 model. The proportion of catchment area with both (1) moderate-or-high burn severity, and (2) slope angle ≥ 23 degrees |
|
Fire variable for the M1 model. Mean catchment dNBR divided by 1000. |
|
Soil variable for the M1 model. Mean catchment KF-factor. |
|
Catchment area burned at moderate or high severity in square kilometers. Used to implement the volume model. |
|
Vertical relief in meters. Used to implement the volume model. |
The number of hazard model results will depend on the number of values used for each hazard modeling parameter. To accommodate this, wildcat assigns result names using a prefixed indexing scheme. When you export hazard model results, wildcat will replace these indices with simplified parameter values. To generate these name, probabilities
and volume_CI
values are first multiplied by 100. Then, all parameter values are rounded to the nearest integer and subsitituted for the relevant index. The following table summarizes these names:
Assessment Name |
Exported Name |
Description |
---|---|---|
|
|
Combined hazard classifications for the ith I15 value |
|
|
Debris-flow likelihoods for the ith I15 value |
|
|
Potential sediment volumes for the ith I15 value |
|
|
Lower bound of the jth confidence interval for potential sediment volumes for the ith I15 value |
|
|
Upper bound of the jth confidence interval for potential sediment volumes for the ith I15 value |
|
|
Rainfall accumulations for the dth rainfall duration and the pth probability level |
|
|
Rainfall intensities for the dth rainfall duration and the pth probability level |
Wildcat follows Python conventions and uses 0-indexing to indicate parameter values. So the first value of a parameter will have an index of 0, the second value will have an index of 1, and so on.
Tip
You can learn more about how wildcat estimates hazards in the assess command overview.
Example Result Names¶
This section provides an example of how model result property names are generated. Consider an assessment run with the following configuration:
I15_mm_hr = [16, 20, 24]
volume_CI = [0.9, 0.95]
durations = [15, 30, 60]
probabilities = [0.5, 0.75]
In this case, the output assessment files will include the following properties:
Show Properties
Assessment Name |
Exported Name |
Description |
---|---|---|
|
|
Combined hazard classification for a peak 15-minute rainfall intensity of 16 mm/hour |
|
|
Combined hazard classification for a peak 15-minute rainfall intensity of 20 mm/hour |
|
|
Combined hazard classification for a peak 15-minute rainfall intensity of 24 mm/hour |
|
|
Debris-flow likelihoods for a peak 15-minute rainfall intensity of 16 mm/hour |
|
|
Debris-flow likelihoods for a peak 15-minute rainfall intensity of 20 mm/hour |
|
|
Debris-flow likelihoods for a peak 15-minute rainfall intensity of 24 mm/hour |
|
|
Potential sediment volumes for a peak 15-minute rainfall intensity of 16 mm/hour |
|
|
Potential sediment volumes for a peak 15-minute rainfall intensity of 20 mm/hour |
|
|
Potential sediment volumes for a peak 15-minute rainfall intensity of 24 mm/hour |
|
|
Upper and lower bounds of the 90% confidence interval for potential sediment volumes for a peak 15-minute rainfall intensity of 16 mm/hour |
|
|
Upper and lower bounds of the 95% confidence interval for potential sediment volumes for a peak 15-minute rainfall intensity of 16 mm/hour |
|
|
Upper and lower bounds of the 90% confidence interval for potential sediment volumes for a peak 15-minute rainfall intensity of 20 mm/hour |
|
|
Upper and lower bounds of the 95% confidence interval for potential sediment volumes for a peak 15-minute rainfall intensity of 20 mm/hour |
|
|
Upper and lower bounds of the 90% confidence interval for potential sediment volumes for a peak 15-minute rainfall intensity of 24 mm/hour |
|
|
Upper and lower bounds of the 95% confidence interval for potential sediment volumes for a peak 15-minute rainfall intensity of 24 mm/hour |
|
|
Rainfall accumulations and intensities for a 15-minute rainfall duration at a 50% probability level |
|
|
Rainfall accumulations and intensities for a 15-minute rainfall duration at a 75% probability level |
|
|
Rainfall accumulations and intensities for a 30-minute rainfall duration at a 50% probability level |
|
|
Rainfall accumulations and intensities for a 30-minute rainfall duration at a 75% probability level |
|
|
Rainfall accumulations and intensities for a 60-minute rainfall duration at a 50% probability level |
|
|
Rainfall accumulations and intensities for a 60-minute rainfall duration at a 75% probability level |
Exporting Properties¶
By default, wildcat will export model results, model inputs, and watershed variables. However, you can use the properties
, exclude_properties
, and include_properties
settings to select specific properties for export. To select properties, you may use any combination of property names, result prefixes, and/or property groups.
Property names are the most basic and allow you to select a property by providing its name. If selecting a specific hazard model result, you should use the indexed variant of its name. For example:
properties = ["Area_km2", "H_0", "IsConfined", "R_1_2"]
A result prefix is the fixed text at the beginning of a model result field. You can use a result prefix to select all fields corresponding to particular hazard model result. For example:
# Export all volume estimates and confidence intervals
properties = ["V", "Vmin", "Vmax"]
Property groups allow you to select a group of related properties. Wildcat supports the following groups:
Name |
Description |
---|---|
|
|
|
All filter checks |
|
|
|
All model results |
|
All watershed variables, model inputs, and model results |
|
All model inputs and results |
|
All filter checks and watershed variables |
|
All available properties |
For example:
# Export model results and watershed variables
properties = ["results", "watershed"]
Renaming Properties¶
Wildcat’s default property names are designed to work for a variety of export file formats. In particular, the default names are all less than 10 characters, which is a requirement for Shapefile exports. However, some users may want to use different names for exported properties – either because they are exporting to less restrictive file formats, or because they simply prefer a different naming convention. You can apply custom names to exported variables using the rename
config setting.
Important
If you rename properties, wildcat will not check that the new names are valid for the export format. You are responsible for validating property names for different export formats.
The rename
setting should be a Python dict
specifying any renaming options. The keys of the dict should be strings corresponding to any combination of full property names, result prefixes, and/or hazard modeling parameters. Full property names are the most basic. The value for the name should be a string indicating the name for the property in the exported file. If renaming a specific hazard modeling result, then you should use the indexed variant of the name. For example:
rename = {
"Segment_ID": "SID",
"Area_km2": "Total catchment area (km2)",
"H_0": "Combined-Hazard-16mmh",
"R_1_1": "RainAcc_30min_75%",
}
The rename
setting can also include result prefixes. In this case, the value for the prefix should be a string indicating a new name for the prefix. The new name will replace all instances of the prefix in the exported files. For example, if you ran an assessment with the following settings:
I15_mm_hr = [16, 20, 24]
properties = ["H", "P"]
rename = {
"H": "Hazard",
}
then the combined hazard results in the exported file would be named: Hazard_16mmh
, Hazard_20mmh
, and Hazard_24mmh
. Note that the parameter indices are still converted to values, although you can disable this using the clean_names
setting.
Finally, rename
can include hazard modeling parameter names. The value for a parameter should be a list with one element per parameter. Each element should be a string indicating the name for the associated parameter value in exported names. For example, if you ran an assessment with the following settings:
durations = [15, 30, 60]
probabilities = [0.5, 0.75]
rename = {
"durations": ["_15min", "_30min", "_60min"],
"probabilities": ["P50", "P75"],
}
then the rainfall accumulation results in the exported file would be named: R_15min_P50
, R_15min_P75
, R_30min_P50
, R_30min_P75
, R_60min_P50
, and R_60min_P75
. Note that we included an underscore in the renamed durations because the default export names do not include an underscore between the R
prefix and the rainfall duration value.
Note
Full property names have the highest priority. If you rename a result prefix or parameter, but also rename a specific result, then the name for the result will override the prefix and parameter options. For example, if you ran an assessment with the following config settings:
I15_mm_hr = [16, 20, 24]
rename = {
"H": "hazard",
"I15_mm_hr": ["16_mm_hr", "20_mm_hr", "24_mm_hr"],
"H_0": "My hazard legend",
}
then the combined hazard results in the exported file would be named: My hazard legend
, hazard_20_mm_hr
, and hazard_24_mm_hr
.