-
Notifications
You must be signed in to change notification settings - Fork 33
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] Preprocess MS and FR stream networks #206
Conversation
After this is merged, it seems like the changelog should show 3.0.1.0. @nickchadwick-noaa thoughts? CORRECTED -- I recommended 3.0.2.0 before, by accident. |
I agree @BradfordBates-NOAA , 3.0.1.0 seems reasonable since it's a larger update. |
…nto dev-nhd-ftypes
…ws.py; will address in future feature branch
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed code modifications/additions and examined new outputs. I did not run the new code, but the newly created vector files appear as expected. I also created a slide deck summarizing my review. Approving for merge.
Friendly reminder to update CHANGELOG to read 3.0.1.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Re-approved after updating CHANGELOG.md
A new method to moves the contents of snap_and_clip_to_nhd.py to aggregate_vector_inputs.py as preprocessing step.
addresses issues #58, #12, #118, #73, and partial resolution of #4.
Major Changes
In the current FIM 3.0.0.2 workflow, NHDPlus HR is subset and traversed on an individual HUC scale. This creates a problem in HUCs with incoming streams due to incomplete knowledge of the upstream network. This feature branch attempts to resolve this issue by preprocessing the FR and MS network for the entire NWM domain in aggregate_vector_inputs.py. In addition, the new workflow aims to resolve several recurring issues:
Added Files
Additional Minor Changes
Testing
Aggregate CSI score comparison without headwater adjustment
Aggregate CSI score comparison with headwater adjustment
FR CSI scores are very similar to the current development branch before adjusting headwater streams. This is expected as there are currently no intersection operations for this extent. However, this new method should provide a better FIM network overall beyond just the 49 BLE sites used for evaluation. Adjusting the FR headwaters shows a slight overall improvement in CSI scores.
It has been noted in a previous PR that BLE observation data is not ideal for comparing MS outputs. Although there is a slight regression in aggregate CSI scores, a qualitative look at the data shows that the results are comparable. Another key improvement to the MS network is the handling of incoming streams. In FIM 3.0.0.2, any NHDPlus HR stream segment that crosses the HUC boundary is assumed to be a MS headwater stream. This resulted in unwanted encroaching tributaries being included in the MS stream network. The new feature branch resolves this issue by preprocessing the network and filtering out unwanted tributaries.