All work done in env-data branch
Create a script to pull updated environmental gage data for each tributary (utilize logic from jpe-datasets)
Check that queries return data
Updates existing data with new data from query (make sure to use old data if new query fails)
Cache data as an environmental_gage.rds table.
Environmental gage should have date, stream, site, site_group, environmental parameter (flow, temp), value, unit, gage agency, gage number, and statistic)
Talk through the best way to document gages used for each trib (I feel like maybe a link to the map with a description of our criteria for choosing is the best way?)
For Yuba and Feather in the pull script, lets save these datasets with the interpolation in the package (see the Rmd for where they are saved in GCP) AND pull in data from the gages but filter to year(date) > 2024. That way we do not need to apply all the regression interpolation within the package. The data with interpolation will represent the "historical dataset" and then we will rely on the gages moving forward.
All work done in
env-data
branch Create a script to pull updated environmental gage data for each tributary (utilize logic from jpe-datasets) Check that queries return data Updates existing data with new data from query (make sure to use old data if new query fails) Cache data as an environmental_gage.rds table. Environmental gage should have date, stream, site, site_group, environmental parameter (flow, temp), value, unit, gage agency, gage number, and statistic)