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

[5pt] Test out larger agreedem buffer on flatter floodplains #1422

Open
CarsonPruitt-NOAA opened this issue Feb 7, 2025 · 3 comments
Open
Assignees
Labels

Comments

@CarsonPruitt-NOAA
Copy link
Collaborator

One of the underlying issues that contributes to the catchment boundary glass wall occurs when a floodplain is very flat. Oftentimes HAND will attribute floodplain pixels to stream pixels several km downstream because of small variations in the DEM or natural levees near the streambank. In the illustration below, the flow direction at green X is likely being routed along the green arrow, causing its relative elevation to be too high. If it were routed to the stream along the more direct white arrow, the relative elevation would be much more realistic. (HUC 11070203)

Image

This task is just to test the hypothesis to see if the agree buffer distance has any effect on mitigating the catchment boundary glass wall. Eventually, we may want to adjust the buffer by stream order or floodplain width.

@CarsonPruitt-NOAA
Copy link
Collaborator Author

export agree_DEM_buffer=70

@CarsonPruitt-NOAA
Copy link
Collaborator Author

Another smaller example in HUC 06010108

Image

@RyanSpies-NOAA
Copy link
Collaborator

Here is the experimental depth output I generated for 11070203 (near Strong City and Cottonwood Falls) using the NWM 25yr recurrence flow datafile:
Image

This image displays the GMS branch "volume m3" for each inundated catchment polygon. Note there are significant fluctuations in the volume extracted from the SRCs between these "hot dog" catchments:
Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants