[1 pt] PR: New Flood Impact Assessment Tool

[erkaufman]

New tool that can assess the impact of a flood on road and/or building vector files. Closes #1226.

Additions

tools/analyze_flood_impact.py : added a tool that assesses the impact of a flood on roads and buildings by calculating how many roads and structures the test flood extent intersects, comparing the test impacted roads and structures to a benchmark, and calculating CSI.

Testing

Tested on HUC 07140102 at vllm7 ahps site with MoDOT roads shapefile and US Structures FEMA building footprints.
Ran for inundation rasters produced from a few different flows (major-stage flow and highest observed flow at vllm7 ahps site).

Deployment Plan (For developer use)

How does the changes affect the product?

• Code only?
• If applicable, has a deployment plan be created with the deployment person/team?
• Require new or adjusted data inputs? Does it have start, end and duration code (in UTC)?
• If new or updated data sets, has the FIM code been updated and tested with the new/adjusted data (subset is fine, but must be a subset of the new data)?
• Require new pre-clip set?
• Has new or updated python packages?

Issuer Checklist (For developer use)

You may update this checklist before and/or after creating the PR. If you're unsure about any of them, please ask, we're here to help! These items are what we are going to look for before merging your code.

• Informative and human-readable title, using the format: [_pt] PR: <description>
• Links are provided if this PR resolves an issue, or depends on another other PR
• If submitting a PR to the dev branch (the default branch), you have a descriptive Feature Branch name using the format: dev-<description-of-change> (e.g. dev-revise-levee-masking)
• Changes are limited to a single goal (no scope creep)
• The feature branch you're submitting as a PR is up to date (merged) with the latest dev branch
• pre-commit hooks were run locally
• Any change in functionality is tested
• New functions are documented (with a description, list of inputs, and expected output)
• Placeholder code is flagged / future todos are captured in comments
• CHANGELOG updated with template version number, e.g. 4.x.x.x
• Add yourself as an assignee in the PR as well as the FIM Technical Lead

Merge Checklist (For Technical Lead use only)

• Update CHANGELOG with latest version number and merge date
• Update the Citation.cff file to reflect the latest version number in the CHANGELOG
• If applicable, update README with major alterations

[RileyMcDermott-NOAA]

I tested the code tools/analyze_flood_impact.py on HUC 12090301 using the 100yr AEP flow as the benchmark map and the 50yr AEP flow as the test extent, clipped to the area around the town of Bastrop, TX. The process took 51 seconds to run on dev1. It identifed 459 structures and 81 roads impacted in the benchmark inundation and 244 impacted structures and 56 impacted roads in the test inundation for a CSI of 0.692. The output geopackage file contains the benchmark and test vector inundation, imapcted roads, and impacted structures layers.

I also was able to sucessfully test the code at the county level, (about 1/3 the HUC size in this case) and the process took 59.34 minutes.

I updated the comments within tools/analyze_flood_impact.py to help direct future users to datasources for road and building files and explain input parameter requirements in more detail to help with datapreprocessing.