the remaining TODOs/clarifications on feather snorkel data are:
[ ] what is the difference between unit and units_covered ? units_coveredis only collected past 2007 and is pretty inconsistent relative to unit. Do we need both or can we just stick with unit?
[ ] substratecolumn: whereas the lookup table has codes for substrate that range from 1:6, values in the post-2004 database contain multiple values (i.e. 12, 234, etc.) and include one 0
[ ] instream_covercolumn: whereas the lookup table has codes for this that range from A:F, values in the post-2004 database contain multiple values (i.e. BCDE, DE, etc.). Can we confirm that for substrateand instream_coverthese are recording the occurrence of multiple codes at once?
[ ] Should we map section_nameto the reach numbers from our JPE work (1:39 or the ones for the snorkel survey (1:21?)
[ ] it looks like unit_typeand hydrologyare referring to the same thing. Confirm that this is true, and we can rename column
[ ] confirm meaning of following fields: bank_distance, visibility, est_size
[ ] survey_typefields contain either "unit" or "'comp", confirm meaning of this field, same with section_type, fields contain either "permanent" or "random"
file path to csv associated: juvenile-rearing-monitoring/seine-and-snorkel-data/feather-river/data/combined_feather_snorkel_data.csv"
associated branch: 200-add-feather-snorkel-early
the remaining TODOs/clarifications on feather snorkel data are:
units_covered?units_coveredis only collected past 2007 and is pretty inconsistent relative to unit. Do we need both or can we just stick with unit?substratecolumn: whereas the lookup table has codes for substrate that range from 1:6, values in the post-2004 database contain multiple values (i.e. 12, 234, etc.) and include one 0instream_covercolumn: whereas the lookup table has codes for this that range from A:F, values in the post-2004 database contain multiple values (i.e. BCDE, DE, etc.). Can we confirm that forsubstrateandinstream_coverthese are recording the occurrence of multiple codes at once?section_nameto the reach numbers from our JPE work (1:39 or the ones for the snorkel survey (1:21?)unit_typeandhydrologyare referring to the same thing. Confirm that this is true, and we can rename columnbank_distance,visibility,est_sizesurvey_typefields contain either "unit" or "'comp", confirm meaning of this field, same withsection_type, fields contain either "permanent" or "random"file path to csv associated:
juvenile-rearing-monitoring/seine-and-snorkel-data/feather-river/data/combined_feather_snorkel_data.csv"associated branch:200-add-feather-snorkel-early