FR-CRM Monitoring TAC
AGENDA & MINUTES
5/30/03
Attending: Fraser Sime, Kevin Pond, Clay Clifton, Ken Cawley, Dennis Heiman, Cris
Bailey, Jim Wilcox, Leslie Mink
1. Review
’99 and ’01 watershed monitoring data and data mgmt. TAC really likes the
Goodrich SCI site, and wants to re-approach Beatty Co. for access there.
-
Review Final Report Tables we went ove the list of
question Leslie had for averyone. See
list for more info.
-
DWR assistance - Database Management Kris is about 70%
finished with re-formatting data into a databse format, Bedload samples
lab started analyzing samples on 5/30/03.
Check at end of June to get data.
- Focus of final report (to be on
summarizing data, not analysis, not statistics??) - yes
2. What
data, and if, to collect in 2003 & how to format
-
Move Butt and Red Clover sites? Collect WQ, temperature,
and bugs at Red Clover, move work with FS to get their data for the Chase SCI
site. (Notson Bridge deposition is
affected by the bridge too muc, so we won’t use this site). Drum bridge site is so bouldery that it is
not a good site to show indications of what upstream watershed conditions are
like. HOWEVER, it will be good to
continue that water quality info because the Chase site just looks at Red
Clover Valley, the Drum bridge site shows really how all of Red Clover affects
Indian Cr., in terms of water quality.
For Butt, Cr, Leslie needs to get more info from Ken Roby – where are
their 2 sites, and is it good to keep our site to add to all of the data, or
would it be best to move it to one of their sites?
-
Review of what parameters to collect at non-alluvial
channels for this year, continue to collect all the data, we’re still early
enough, and setting baseline variability, that its good to get more data on all
of these sites. At some future time,
like after a few more data collection efforts, we may decide to scale back the
geomorphic data collection at non-alluvial sites?
-
Eshock each site? yes
(clarification on DWR help) DWR
can help with electroshocking equipment, and one person. CRM would have to supply the other crew
members. (Probably good for this higher flow year) yes (need a
permit) How often? Yes, collect this year, but not every other year.
-
Macroinvertebrates Dennis will get about five metrcis to
summarize the copious analysis data into.
-
Farenheit for all temp data? Yes. FS uses F and everyone understands it. Leslie will ask Tim Sagraves to re-program
Contiunous recording stations to F for WY04.
-
WQ collection DWR collect? Fraser to check if Jerry
Bole’s shop has time, if not, Leslie will get collection protocols from Dennis’
contract lab and DWR, and collect the samples, and send them to the RWQCB
contract lab., we collect?, DWR analyze?
3. Project
monitoring: group reviewed this list and had no comment
- hobo temps into Spanish Cr
- pre-project @ Poplar (fish, habitat
typing, bugs)
- continue well reading at Last Chance,
Stone Dairy, Hosselkus, Clarks
- veg monitoring at Last Chance
(pre-project), Clarks (Hobotemps, too) & Hosselkus (continue)
- continue w/ flows at Big Flat w/ Sagraves
- DWR doing post-project wildlife at Clarks
-
September flight photos
-
Assistance with Last Chance project monitoring
(clarification on DWR help) again, DWR can help with one person and an
e-shocker if we need it.
4. Weather Stations and back up systems Kevin will purchase some back up rain buckets
for the weather stations. Will try and
get Tville station in befreo 6/30, but not looking good. DWR lands and right-of-way dept snafu.
5. New
Sulphur Station & citizen monitoring station should go in this fall, and
citizen monitoring coord. to go under
contract soon.
-
good
indicators? Others? Add D50
from pebble count (only collectged in
’01).
-
Keep
same indicators at all sites, or just do water quality at some sites (NFFR abv
Almanor?, others?) for this year, keep same at all sites, after we get lots
of maybe 3-4 more years of baseline data, we could scale back.
-
SCI
parameters measured but not summarized here are:
max BF depth, used for ER calc keep out of
summery
wood (pretty much zero everywhere), no, add this
back in., not to SCI level, though, just tally up number of pieces that are
hydraulically or structurally affecting the channel.
FP width (I think its just used to calc entrench
ratio??), right, keep out of summary
bank depth (I just used %=0) this is redundant, in fact, % shore depth =
zero is redu7ndant – delete from table.
-
helpful
(and/or valid?) to add columns for # parameters improve >10%, and degrading
>10? ???
-
are
there a thresholds of change? From Roby – not really, you have to set your
own confidence level, and look at it from that standpoint.
-
Can
any conclusions be drawn from this data or is it valid to do that at this
time? (Richard suggests we’re still
collecting baseline) still baseline, summarize, but no conclusions
-
Some
parameters are easy to interpret degrade vs. improve, others aren’t. ER?
BF width
Avg BF depth (can’t these just be summarized in
W/D?) some need to be looked at in conjunction with others. Keep BF depth and width, because that tells
the reader what size channel it is.
Keep ER – its not the best, but its standard. Include in report a discussion
of the meanings of the parameters.
-
Entrenchment
is Fpwidth/Bfwidth. Would it be more
useful for us to have a Top of Terrace area / BF area?? Don’t use area, it
doesn’t tell you as much as ER.
I need to write a rationale for sampling NFFR abv
Almanor, Indian abv Spanish, and Jamison.
People explain, and I forget.
They don’t seem very alluvial to me. Never mind
Group by year or station? Both? both
Are these summaries good? Others? Delete mean
daily water temp. reword 7-day avg
column “number of times that the 7-day average exceeds 19C. Include a discussion in report of
significance of 66F and 75F. (fish biology)
Organize by location or type of data station?
Organize by subwatershed?
Put in context of watershed “snapshot”?
Put in
context of watershed happenings,and organize by location, but don’t need a
nested analysis.