Urban flood risk mitigation - run of retention m3 seems to be right but do not show appropirate Data

[Tp09]

Hello,

The model is running successfully and the data make sense but when I compare the runoff-retetntion-volume-m3-output to other outputs I can see that they have other values.

2020-10-05 19:44:40,327 utils.prepare_workspace(111) INFO Writing log messages to C:/Users/thols/OneDrive/Desktop/process\InVEST-UrbanFloodRiskMitigation-log-2020-10-05–19_44_40.txt
2020-10-05 19:44:40,330 model._logged_target(1629) Level 100 Starting model with parameters:
Arguments for InVEST natcap.invest.urban_flood_risk_mitigation 3.8.7:
aoi_watersheds_path C:/Users/thols/OneDrive/Desktop/Data_Input/watershed.shp
built_infrastructure_vector_path
curve_number_table_path C:/Users/thols/OneDrive/Desktop/Data_Input/abcneu.csv
infrastructure_damage_loss_table_path
lulc_path C:/Users/thols/OneDrive/Desktop/new/landuse.tif
n_workers -1
rainfall_depth 27
results_suffix
soils_hydrological_group_raster_path C:/Users/thols/OneDrive/Desktop/new/hsgsoil.tif
workspace_dir C:/Users/thols/OneDrive/Desktop/process

2020-10-05 19:44:40,404 validation._wrapped_validate_func(839) DEBUG Using ARG_SPEC for validation
2020-10-05 19:44:40,412 validation._wrapped_validate_func(843) INFO Starting whole-model validation with ARGS_SPEC
2020-10-05 19:44:40,544 validation._wrapped_validate_func(889) DEBUG Validation warnings: []
2020-10-05 19:44:45,743 geoprocessing.logger_callback(3239) INFO Warp 63.0% complete C:/Users/thols/OneDrive/Desktop/process\temp_working_dir_not_for_humans\aligned_lulc.tif
2020-10-05 19:44:47,539 geoprocessing.logger_callback(3239) INFO Warp 100.0% complete C:/Users/thols/OneDrive/Desktop/process\temp_working_dir_not_for_humans\aligned_lulc.tif
2020-10-05 19:44:47,883 geoprocessing.align_and_resize_raster_stack(752) INFO 1 of 2 aligned: aligned_lulc.tif
2020-10-05 19:44:52,971 geoprocessing.logger_callback(3239) INFO Warp 62.0% complete C:/Users/thols/OneDrive/Desktop/process\temp_working_dir_not_for_humans\aligned_soils_hydrological_group.tif
2020-10-05 19:44:55,773 geoprocessing.logger_callback(3239) INFO Warp 100.0% complete C:/Users/thols/OneDrive/Desktop/process\temp_working_dir_not_for_humans\aligned_soils_hydrological_group.tif
2020-10-05 19:44:56,065 geoprocessing.align_and_resize_raster_stack(752) INFO 2 of 2 aligned: aligned_soils_hydrological_group.tif
2020-10-05 19:44:56,066 geoprocessing.align_and_resize_raster_stack(754) INFO aligned all 2 rasters.
2020-10-05 19:44:56,158 geoprocessing.raster_calculator(375) INFO starting stats_worker
2020-10-05 19:44:56,163 geoprocessing.raster_calculator(381) INFO started stats_worker <Thread(Thread-2, started daemon 16124)>
2020-10-05 19:45:01,168 geoprocessing.(451) INFO 82.7% complete
2020-10-05 19:45:02,064 geoprocessing.raster_calculator(454) INFO 100.0%% complete
2020-10-05 19:45:02,065 geoprocessing.raster_calculator(457) INFO signaling stats worker to terminate
2020-10-05 19:45:02,066 geoprocessing.raster_calculator(459) INFO Waiting for raster stats worker result.
2020-10-05 19:45:02,066 threading.run(870) DEBUG payload is None, terminating
2020-10-05 19:45:02,823 geoprocessing.raster_calculator(375) INFO starting stats_worker
2020-10-05 19:45:02,825 geoprocessing.raster_calculator(381) INFO started stats_worker <Thread(Thread-3, started daemon 9000)>
2020-10-05 19:45:05,162 geoprocessing.raster_calculator(454) INFO 100.0%% complete
2020-10-05 19:45:05,163 geoprocessing.raster_calculator(457) INFO signaling stats worker to terminate
2020-10-05 19:45:05,163 geoprocessing.raster_calculator(459) INFO Waiting for raster stats worker result.
2020-10-05 19:45:05,164 threading.run(870) DEBUG payload is None, terminating
2020-10-05 19:45:05,791 geoprocessing.raster_calculator(375) INFO starting stats_worker
2020-10-05 19:45:05,794 geoprocessing.raster_calculator(381) INFO started stats_worker <Thread(Thread-4, started daemon 7312)>
2020-10-05 19:45:08,620 geoprocessing.raster_calculator(454) INFO 100.0%% complete
2020-10-05 19:45:08,621 geoprocessing.raster_calculator(457) INFO signaling stats worker to terminate
2020-10-05 19:45:08,622 geoprocessing.raster_calculator(459) INFO Waiting for raster stats worker result.
2020-10-05 19:45:08,623 threading.run(870) DEBUG payload is None, terminating
2020-10-05 19:45:09,088 geoprocessing.raster_calculator(375) INFO starting stats_worker
2020-10-05 19:45:09,090 geoprocessing.raster_calculator(381) INFO started stats_worker <Thread(Thread-5, started daemon 8992)>
2020-10-05 19:45:11,621 geoprocessing.raster_calculator(454) INFO 100.0%% complete
2020-10-05 19:45:11,622 geoprocessing.raster_calculator(457) INFO signaling stats worker to terminate
2020-10-05 19:45:11,623 threading.run(870) DEBUG payload is None, terminating
2020-10-05 19:45:11,623 geoprocessing.raster_calculator(459) INFO Waiting for raster stats worker result.
2020-10-05 19:45:12,227 geoprocessing.raster_calculator(375) INFO starting stats_worker
2020-10-05 19:45:12,229 geoprocessing.raster_calculator(381) INFO started stats_worker <Thread(Thread-6, started daemon 16548)>
2020-10-05 19:45:14,817 geoprocessing.raster_calculator(454) INFO 100.0%% complete
2020-10-05 19:45:14,818 geoprocessing.raster_calculator(457) INFO signaling stats worker to terminate
2020-10-05 19:45:14,819 threading.run(870) DEBUG payload is None, terminating
2020-10-05 19:45:14,819 geoprocessing.raster_calculator(459) INFO Waiting for raster stats worker result.
2020-10-05 19:45:15,267 geoprocessing.raster_calculator(375) INFO starting stats_worker
2020-10-05 19:45:15,269 geoprocessing.raster_calculator(381) INFO started stats_worker <Thread(Thread-7, started daemon 1268)>
2020-10-05 19:45:17,050 geoprocessing.raster_calculator(454) INFO 100.0%% complete
2020-10-05 19:45:17,051 geoprocessing.raster_calculator(457) INFO signaling stats worker to terminate
2020-10-05 19:45:17,051 threading.run(870) DEBUG payload is None, terminating
2020-10-05 19:45:17,051 geoprocessing.raster_calculator(459) INFO Waiting for raster stats worker result.
2020-10-05 19:45:17,606 geoprocessing.reproject_vector(1640) INFO starting reprojection
2020-10-05 19:45:17,614 utils._log_gdal_errors(68) WARNING [errno 1] A geometry of type MULTIPOLYGON is inserted into layer watershed of geometry type POLYGON, which is not normally allowed by the GeoPackage specification, but the driver will however do it. To create a conformant GeoPackage, if using ogr2ogr, the -nlt option can be used to override the layer geometry type. This warning will no longer be emitted for this combination of layer and feature geometry type.
2020-10-05 19:45:17,622 geoprocessing.reproject_vector(1683) INFO reprojection 100.0% complete on reprojected_aoi.gpkg
2020-10-05 19:45:17,723 geoprocessing.zonal_statistics(1129) DEBUG <osgeo.gdal.Dataset; proxy of <Swig Object of type ‘GDALDatasetShadow *’ at 0x1B044548> >
2020-10-05 19:45:21,622 geoprocessing.align_and_resize_raster_stack(752) INFO 1 of 1 aligned: clipped_rastertbgomqo2.tif
2020-10-05 19:45:21,624 geoprocessing.align_and_resize_raster_stack(754) INFO aligned all 1 rasters.
2020-10-05 19:45:21,626 geoprocessing.zonal_statistics(1189) INFO build a lookup of aggregate field value to FID
2020-10-05 19:45:21,627 geoprocessing.zonal_statistics(1196) INFO creating disjoint polygon set
2020-10-05 19:45:21,633 geoprocessing.calculate_disjoint_polygon_set(2082) INFO build shapely polygon list
2020-10-05 19:45:21,640 geoprocessing.calculate_disjoint_polygon_set(2096) INFO build shapely rtree index
2020-10-05 19:45:21,648 geoprocessing.calculate_disjoint_polygon_set(2111) INFO poly feature lookup 100.0% complete on reprojected_aoi.gpkg
2020-10-05 19:45:21,649 geoprocessing.calculate_disjoint_polygon_set(2113) INFO build poly intersection lookup
2020-10-05 19:45:21,655 geoprocessing.calculate_disjoint_polygon_set(2137) INFO poly intersection feature lookup 100.0% complete on reprojected_aoi.gpkg
2020-10-05 19:45:21,655 geoprocessing.calculate_disjoint_polygon_set(2171) INFO maximal subset build 100.0% complete on reprojected_aoi.gpkg
2020-10-05 19:45:21,696 geoprocessing.zonal_statistics(1219) INFO processing 3 disjoint polygon sets
2020-10-05 19:45:21,699 geoprocessing.zonal_statistics(1253) INFO disjoint polygon set 1 of 3 100.0% processed on reprojected_aoi.gpkg
2020-10-05 19:45:22,067 geoprocessing.zonal_statistics(1261) INFO rasterizing disjoint polygon set 1 of 3 reprojected_aoi.gpkg
2020-10-05 19:45:24,332 geoprocessing.zonal_statistics(1279) INFO summarizing rasterized disjoint polygon set 1 of 3 reprojected_aoi.gpkg
2020-10-05 19:45:25,596 geoprocessing.zonal_statistics(1253) INFO disjoint polygon set 2 of 3 100.0% processed on reprojected_aoi.gpkg
2020-10-05 19:45:25,875 geoprocessing.zonal_statistics(1261) INFO rasterizing disjoint polygon set 2 of 3 reprojected_aoi.gpkg
2020-10-05 19:45:27,952 geoprocessing.zonal_statistics(1279) INFO summarizing rasterized disjoint polygon set 2 of 3 reprojected_aoi.gpkg
2020-10-05 19:45:28,901 geoprocessing.(1225) INFO zonal stats approximately 100.0% complete on reprojected_aoi.gpkg
2020-10-05 19:45:28,904 geoprocessing.zonal_statistics(1253) INFO disjoint polygon set 3 of 3 100.0% processed on reprojected_aoi.gpkg
2020-10-05 19:45:29,128 geoprocessing.zonal_statistics(1261) INFO rasterizing disjoint polygon set 3 of 3 reprojected_aoi.gpkg
2020-10-05 19:45:31,077 geoprocessing.zonal_statistics(1279) INFO summarizing rasterized disjoint polygon set 3 of 3 reprojected_aoi.gpkg
2020-10-05 19:45:32,143 geoprocessing.zonal_statistics(1322) DEBUG unset_fids: 0 of 4
2020-10-05 19:45:32,151 geoprocessing.zonal_statistics(1325) DEBUG gt [ 3.6209706e+05 1.0000000e+00 0.0000000e+00 5.6245770e+06
0.0000000e+00 -1.0000000e+00] for (‘C:/Users/thols/OneDrive/Desktop/process\intermediate_files\Q_m3.tif’, 1)
2020-10-05 19:45:32,152 geoprocessing.zonal_statistics(1399) DEBUG remaining unset_fids: 0 of 4
2020-10-05 19:45:32,152 geoprocessing.zonal_statistics(1407) INFO all done processing polygon sets for reprojected_aoi.gpkg
2020-10-05 19:45:32,240 geoprocessing.zonal_statistics(1129) DEBUG <osgeo.gdal.Dataset; proxy of <Swig Object of type ‘GDALDatasetShadow *’ at 0x1B0448F0> >
2020-10-05 19:45:35,141 geoprocessing.align_and_resize_raster_stack(752) INFO 1 of 1 aligned: clipped_rasterlutkrgrj.tif
2020-10-05 19:45:35,141 geoprocessing.align_and_resize_raster_stack(754) INFO aligned all 1 rasters.
2020-10-05 19:45:35,144 geoprocessing.zonal_statistics(1189) INFO build a lookup of aggregate field value to FID
2020-10-05 19:45:35,145 geoprocessing.zonal_statistics(1196) INFO creating disjoint polygon set
2020-10-05 19:45:35,152 geoprocessing.calculate_disjoint_polygon_set(2082) INFO build shapely polygon list
2020-10-05 19:45:35,155 geoprocessing.calculate_disjoint_polygon_set(2096) INFO build shapely rtree index
2020-10-05 19:45:35,157 geoprocessing.calculate_disjoint_polygon_set(2111) INFO poly feature lookup 100.0% complete on reprojected_aoi.gpkg
2020-10-05 19:45:35,157 geoprocessing.calculate_disjoint_polygon_set(2113) INFO build poly intersection lookup
2020-10-05 19:45:35,163 geoprocessing.calculate_disjoint_polygon_set(2137) INFO poly intersection feature lookup 100.0% complete on reprojected_aoi.gpkg
2020-10-05 19:45:35,163 geoprocessing.calculate_disjoint_polygon_set(2171) INFO maximal subset build 100.0% complete on reprojected_aoi.gpkg
2020-10-05 19:45:35,205 geoprocessing.zonal_statistics(1219) INFO processing 3 disjoint polygon sets
2020-10-05 19:45:35,207 geoprocessing.zonal_statistics(1253) INFO disjoint polygon set 1 of 3 100.0% processed on reprojected_aoi.gpkg
2020-10-05 19:45:35,527 geoprocessing.zonal_statistics(1261) INFO rasterizing disjoint polygon set 1 of 3 reprojected_aoi.gpkg
2020-10-05 19:45:37,580 geoprocessing.zonal_statistics(1279) INFO summarizing rasterized disjoint polygon set 1 of 3 reprojected_aoi.gpkg
2020-10-05 19:45:38,637 geoprocessing.zonal_statistics(1253) INFO disjoint polygon set 2 of 3 100.0% processed on reprojected_aoi.gpkg
2020-10-05 19:45:38,901 geoprocessing.zonal_statistics(1261) INFO rasterizing disjoint polygon set 2 of 3 reprojected_aoi.gpkg
2020-10-05 19:45:41,039 geoprocessing.zonal_statistics(1279) INFO summarizing rasterized disjoint polygon set 2 of 3 reprojected_aoi.gpkg
2020-10-05 19:45:41,872 geoprocessing.(1225) INFO zonal stats approximately 100.0% complete on reprojected_aoi.gpkg
2020-10-05 19:45:41,873 geoprocessing.zonal_statistics(1253) INFO disjoint polygon set 3 of 3 100.0% processed on reprojected_aoi.gpkg
2020-10-05 19:45:42,109 geoprocessing.zonal_statistics(1261) INFO rasterizing disjoint polygon set 3 of 3 reprojected_aoi.gpkg
2020-10-05 19:45:44,605 geoprocessing.zonal_statistics(1279) INFO summarizing rasterized disjoint polygon set 3 of 3 reprojected_aoi.gpkg
2020-10-05 19:45:46,003 geoprocessing.zonal_statistics(1322) DEBUG unset_fids: 0 of 4
2020-10-05 19:45:46,016 geoprocessing.zonal_statistics(1325) DEBUG gt [ 3.6209706e+05 1.0000000e+00 0.0000000e+00 5.6245770e+06
0.0000000e+00 -1.0000000e+00] for (‘C:/Users/thols/OneDrive/Desktop/process\Runoff_retention.tif’, 1)
2020-10-05 19:45:46,017 geoprocessing.zonal_statistics(1399) DEBUG remaining unset_fids: 0 of 4
2020-10-05 19:45:46,017 geoprocessing.zonal_statistics(1407) INFO all done processing polygon sets for reprojected_aoi.gpkg
2020-10-05 19:45:46,131 geoprocessing.zonal_statistics(1129) DEBUG <osgeo.gdal.Dataset; proxy of <Swig Object of type ‘GDALDatasetShadow *’ at 0x1B044D58> >
2020-10-05 19:45:49,454 geoprocessing.align_and_resize_raster_stack(752) INFO 1 of 1 aligned: clipped_raster0i5vqzri.tif
2020-10-05 19:45:49,455 geoprocessing.align_and_resize_raster_stack(754) INFO aligned all 1 rasters.
2020-10-05 19:45:49,460 geoprocessing.zonal_statistics(1189) INFO build a lookup of aggregate field value to FID
2020-10-05 19:45:49,462 geoprocessing.zonal_statistics(1196) INFO creating disjoint polygon set
2020-10-05 19:45:49,472 geoprocessing.calculate_disjoint_polygon_set(2082) INFO build shapely polygon list
2020-10-05 19:45:49,476 geoprocessing.calculate_disjoint_polygon_set(2096) INFO build shapely rtree index
2020-10-05 19:45:49,479 geoprocessing.calculate_disjoint_polygon_set(2111) INFO poly feature lookup 100.0% complete on reprojected_aoi.gpkg
2020-10-05 19:45:49,480 geoprocessing.calculate_disjoint_polygon_set(2113) INFO build poly intersection lookup
2020-10-05 19:45:49,487 geoprocessing.calculate_disjoint_polygon_set(2137) INFO poly intersection feature lookup 100.0% complete on reprojected_aoi.gpkg
2020-10-05 19:45:49,487 geoprocessing.calculate_disjoint_polygon_set(2171) INFO maximal subset build 100.0% complete on reprojected_aoi.gpkg
2020-10-05 19:45:49,547 geoprocessing.zonal_statistics(1219) INFO processing 3 disjoint polygon sets
2020-10-05 19:45:49,550 geoprocessing.zonal_statistics(1253) INFO disjoint polygon set 1 of 3 100.0% processed on reprojected_aoi.gpkg
2020-10-05 19:45:49,860 geoprocessing.zonal_statistics(1261) INFO rasterizing disjoint polygon set 1 of 3 reprojected_aoi.gpkg
2020-10-05 19:45:52,010 geoprocessing.zonal_statistics(1279) INFO summarizing rasterized disjoint polygon set 1 of 3 reprojected_aoi.gpkg
2020-10-05 19:45:53,240 geoprocessing.zonal_statistics(1253) INFO disjoint polygon set 2 of 3 100.0% processed on reprojected_aoi.gpkg
2020-10-05 19:45:53,495 geoprocessing.zonal_statistics(1261) INFO rasterizing disjoint polygon set 2 of 3 reprojected_aoi.gpkg
2020-10-05 19:45:55,554 geoprocessing.zonal_statistics(1279) INFO summarizing rasterized disjoint polygon set 2 of 3 reprojected_aoi.gpkg
2020-10-05 19:45:56,394 geoprocessing.(1225) INFO zonal stats approximately 100.0% complete on reprojected_aoi.gpkg
2020-10-05 19:45:56,396 geoprocessing.zonal_statistics(1253) INFO disjoint polygon set 3 of 3 100.0% processed on reprojected_aoi.gpkg
2020-10-05 19:45:56,631 geoprocessing.zonal_statistics(1261) INFO rasterizing disjoint polygon set 3 of 3 reprojected_aoi.gpkg
2020-10-05 19:45:59,020 geoprocessing.zonal_statistics(1279) INFO summarizing rasterized disjoint polygon set 3 of 3 reprojected_aoi.gpkg
2020-10-05 19:46:00,044 geoprocessing.zonal_statistics(1322) DEBUG unset_fids: 0 of 4
2020-10-05 19:46:00,050 geoprocessing.zonal_statistics(1325) DEBUG gt [ 3.6209706e+05 1.0000000e+00 0.0000000e+00 5.6245770e+06
0.0000000e+00 -1.0000000e+00] for (‘C:/Users/thols/OneDrive/Desktop/process\Runoff_retention_m3.tif’, 1)
2020-10-05 19:46:00,051 geoprocessing.zonal_statistics(1399) DEBUG remaining unset_fids: 0 of 4
2020-10-05 19:46:00,051 geoprocessing.zonal_statistics(1407) INFO all done processing polygon sets for reprojected_aoi.gpkg
2020-10-05 19:46:00,459 urban_flood_risk_mitigation._write_summary_vector(472) DEBUG creating layer flood_risk_service
2020-10-05 19:46:00,509 model._logged_target(1638) INFO Execution finished
2020-10-05 19:46:00,511 utils.prepare_workspace(117) INFO Elapsed time: 1m 20.180000000000007s

[Tp09]

Here is a picture. My resulting values are between 0.002 and 0.027. The colours do make sense but I do not understand why I have these low values. I am running InVEST 3.8.9.

[esoth]

Hi @Tp09,

Do the relative runoff retention values (Runoff_retention.tif) also seem low?

You could try calculating the runoff retention volume 𝑅_𝑚3𝑖 for one pixel by hand using equations 1 - 4 in the user’s guide: https://storage.googleapis.com/releases.naturalcapitalproject.org/invest-userguide/latest/urban_flood_mitigation.html#runoff-production-and-runoff-attenuation-index
Please let us know if that lines up with the raster values you’re seeing!

[Tp09]

Dear @esoth, thanks for replying.

PS: Run off retention m3: Besides they do not range a lot. It’s from 0,0027 to 0,027.

The run off retention values are in a normal range (compared to other outputs)

I will try your advices and give you feedback.

Kind regards

[Tp09]

Hello @esoth,

precipitation is 27 mm

study area is: 17.595.635 m² / pixel size 1 m²

10-3 is 0,001

when I try to calculate one Pixel --> 0.9684765 (value from runoff_retention)

0.9684765 * 27 * 0.001 * 1 -----------------> 0.02614887.

When I want to calculate runoff_retention_m³ for the whole area, is the formula --> runoff_retention * 27 * 0.001 * 1 ?

[Tp09]

Finally, I know whats going on.

I got these values because of the low Pixel size. I resampled the test data for the model to pixel size 1m instead of 30m. Now they also have these low Values.

What is your opinion about these values? Are they usable? Regards Tp09

[Tp09]

Dear @esoth,

Why is there a warning message regarding the multipolygon?

My watershed consist of 4 subwatersheds. It has also correct attributes in the table?

[dcdenu4]

Hi @Tp09,

I just noticed that you are using InVEST 3.8.7. We made a bugfix that might be very relevant in InVEST 3.8.9. Could you try downloading the latest version of invest [ InVEST Download Page ] and let us know if you still see these low unexpected values?

Cheers,

Doug

[Tp09]

Hello @dcdenu4 ,

I have downloaded the latest Version.

It is the same. My output got the same low values as in the previous version.

I only get higher values when i change the pixel size.

Kind regards Tp09

[dcdenu4]

Hey @Tp09,

Thanks for trying that. Would you be willing to share your input data so we could better check to see if it’s a bug with the model? You could zip up your inputs and share them here, or a cloud sharing service like google drive, dropbox, etc… My email is ddenu @ stanford . edu if you’d feel more comfortable sharing that way.

Doug

[Tp09]

Hey @dcdenu4,

Can you confirm to me that you downloaded it? Then I will delet it.

Kind regards Tim

[dcdenu4]

@Tp09,

I Downloaded it.

[Tp09]

Thank you very much

[dcdenu4]

Hey @Tp09,

Thanks for sharing your data. I think everything looks in working order and if I’ve wrapped my mind around the problem I’m pretty confident in those low volume values. The reason those values are so low is because, as you pointed out, the pixel size of 1m x 1m.

If we drop 27mm of rain on a 1 x 1 pixel and the retention ratio is 0.62, we would expect a little more than half of that to be retained volume. 27mm to meters is 0.027m, and since the pixel size is 1m x 1m, that will be our retention volume for that pixel. That’s a 0.027 cubic meter retention on a pixel (which is 1m x 1m).

The sample data has higher values because it’s looking at 27mm per meter for a 30m x 30m area. So 0.027m x 900sqm = 24.3m_3. That’s a 24.3 cubic meter retention on a pixel (which is 30m x 30m).

So the confusion might be, the 27mm of storm depth is “dropped on the landscape” per meter and NOT per pixel. The model is designed to convert that to an output of volume per pixel.

Does that make sense? Sorry if that attempted explanation was confusing. So yes, I’m not an expert in the science development of the model, but the values seem reasonable.

Doug

[Tp09]

Hey @dcdenu4,

thank you a lot for sharing your time with me. Your Explanation was really helpful and in my eyes we share the same opinion. I think I will change the Pixel Size a bit

So I have one more (my last) question: What does the values in the Damage.csv file mean?

There is 0 (type) and 1 (Damage) --> How can I understand them? I think I know what type is but what about 1 (Damage) what does Value 1 mean?

[dcdenu4]

Hi @Tp09,

No problem at all.

The damage is referring to cost in dollars per square meter of infrastructure damage. So in the example sample data if type 0 is residential infrastructure, then damage would be $100 per square meter of potential damage from flooding on that type of infrastructure. So in the output shapefile the aff.bld field will show potential damage to built infrastructure in $, per watershed.

Cheers,

Doug

[Tp09]

Hello @dcdenu4,

get it. Thank you so much for everything. Nice support at all. stay safe.