-
Notifications
You must be signed in to change notification settings - Fork 30
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
Erroneous Inundation Found In RFC FIM #1057
Comments
I noticed that there doesn't appear to be an underlying NWM flowline showing up in the area of inundation to the east of the Merrimack River. Does appear that the inundation is coming from branch 0, so I guess the question is why is there not a NWM flowline here and where is it being crosswalked? So... after digging deeper it appears there is an orphaned NWM flowline north of interstate 93 draining into Steven's Pond. That NWM headwater point seems to be allowing the DEM derived flowline to create a flowpath to the southwest where it joins up with the Merrimack River. That means there is a DEM derived flowline that doesn't have an overlapping NWM flowline so the crosswalk is mapping flows in that DEM derived reach to the mainstem Merrimack. Tagging @mluck on this issue since he's been exploring crosswalk issues recently. |
Nice analysis, @RyanSpies-NOAA. Some follow-on information:
|
Verifying with 10-year recurrence flows that #1205 resolves this issue since DEM-derived reaches whose midpoints aren't within 100 meters of a NWM stream (colored lines) are eliminated from inundation (top: v4.5.2.3, bottom: #1205) @derekgiardino |
HUC8: 01070006
NWM ID: 6745646
Merrimack River
RFC FIM 2023-12-18 15Z Adopted from CONN3 RFC Forecast
Noticing an erroneous overestimation from Branch 0 extending out into the town of Mancester. Doesn't seem to follow a gap in 3DEP but is finding a way out of bank and then filling a large area away from the Merrimack River.
The text was updated successfully, but these errors were encountered: