Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BLTN7 partner FIM (depth grids) are incorrect #1316

Open
3 tasks
RyanSpies-NOAA opened this issue Oct 11, 2024 · 0 comments
Open
3 tasks

BLTN7 partner FIM (depth grids) are incorrect #1316

RyanSpies-NOAA opened this issue Oct 11, 2024 · 0 comments
Assignees

Comments

@RyanSpies-NOAA
Copy link
Collaborator

Issue was initially flagged when evaluating very poor alpha test performance metrics at this site. It appears the original HEC-RAS depth grids are incorrect for this location. There is almost no discernable difference in the inundation extent between the minimum stage (<action) and maximum stage (>major). This can be seen in the HEC-RAS depth grid outputs as well as on the published partner FIM maps on NWPS.

BLTN7: Swannanoa River at Biltmore
https://water.noaa.gov/gauges/bltn7

However, when looking at the HEC-RAS derived polygon flood extents, we can see a more realistic pattern in the inundation with action stage largely contained to the channel and then incremental expansion as we increase stage up to the major flood stage.

Here is action stage (1985ft NAVD88) differences:
From HEC-RAS depth raster -->
Image

Aligns with extent shown on NWPS gauge site (exceeds FEMA FIRM 1%):
Image

From HEC-RAS polygon extent -->
Image

Suggested actions:

  • Report issue to NWPS
  • Add BLTN7 to the alpha test "exclusion" list
  • Reprocess the benchmark library using the polygon extents instead of the depth rasters (this would require some dev)
@RyanSpies-NOAA RyanSpies-NOAA self-assigned this Oct 11, 2024
@RyanSpies-NOAA RyanSpies-NOAA changed the title BLTN7 benchmark (depth grids) are incorrect BLTN7 partner FIM (depth grids) are incorrect Oct 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant