This PR adds targets to track and read in the outputs from the MODFLOW_extraction workflow; combine the river/catchment attributes into a single data frame in p2_static_inputs_nhm_combined; and writes the combined data to a feather file called '2_process/out/nhm_attributes.feather'.
The data contains one row for each seg_id_nat and one column for each attribute:
@janetrbarclay, the code here generates the same .feather file that you've been working from (on caldera). So as long as that format works within your workflow and plays nicely with river-dl, I don't think this PR needs further review.
I'm going to go ahead and merge this PR since Janet has already successfully used the output feather file in the river-dl workflow (in other words, we know that the data format matches what river-dl is expecting).
This PR adds targets to track and read in the outputs from the MODFLOW_extraction workflow; combine the river/catchment attributes into a single data frame in
p2_static_inputs_nhm_combined
; and writes the combined data to a feather file called'2_process/out/nhm_attributes.feather'
.The data contains one row for each
seg_id_nat
and one column for each attribute:@janetrbarclay, the code here generates the same .feather file that you've been working from (on caldera). So as long as that format works within your workflow and plays nicely with river-dl, I don't think this PR needs further review.
closes #21