-
Notifications
You must be signed in to change notification settings - Fork 5
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
Filter sites streamorder meas #56
Filter sites streamorder meas #56
Conversation
missed changing this `p4_nwis_meas_sw_data_rds` target in #56 . This target which now is derived from `p2_nwis_meas_sw_data` and not `p1_nwis_meas_sw_data` since we process this latter target and added stream_order_category col.
Discovered that there is a merge conflict because main no longer has Resolved by merging #60 first to main (commit msleckman@9b78a4b) The conflict is no longer present in this PR, nor in #58 since the commit histories are now in sync. |
…der_meas adding old files to enable merge of #56
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.
This ran for me but I'd like you to address the comments below before merging. The most important is to have tidy, well-defined, targets. It would be better to create a site-level target that includes the streamorder variable and other site-level info, rather than adding directly to the long form data. This will make the pipeline more modular, and the site-level target will be useful in subsequent targets.
The comments about the buffer accuracy are important, but can be ignored for now.
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.
Ah, ok I see my suggestion of creating a site-level target is partially addressed in #58
Address minor comments and go ahead and merge, those comments can be addressed on next PR
Co-authored-by: Cee Nell <[email protected]>
pipeline runs with latest changes following review. Merging. |
This is a small PR addressing issue #51
Note - I defined this as filtering in the title and issue, but in reality this is just creation of the stream order col for the nwis disc records dataset. No filtering is done until we visualize this data on maps.
Previously, the Stream Order 3 categorization was only done on the dv sw target
p1_nwis_dv_sw_data
.This PR repeats this process for the field measurements (meas) sw dataset. -
p1_nwis_meas_sw_data
.I therefore created a function -
add_stream_order()
which takes the dplyr code chunk that was previously directly in the target chunk forp2_nwis_dv_sw_data
, and placed it in a function insites_along_waterbody.R
In sum:
functions added:
add_stream_order()
targets added:
p2_nwis_dv_sw_data
Findings:
Number of unique field measurement sites per lake, split by stream order:
Summary table of sites:
Discrete sw measurements coverage over time (ignoring SO category):
streamflow (cf/s)
gage height (ft) - note gaps
code for scatterplots