This log of operations includes: flashboard installation and removal dates, when tidal operations were started and stopped, and notes any technical issues. This current document is an Excel file that contains the data as a Table. The Table can be sorted or filtered, and can be read by scripting languages such as Python or R. The date and time are stored together in the DATETIME field. The GATE 1, GATE 2, and GATE 3 fields state whether each gate is operating in Tidal Mode, set to Open, or set to Closed. The ACTION field states what operational change has occurred. The timestamped records go back to May 5, 2018. If prior dates are needed, refer to the Historical (Archived) Suisun Marsh Salinity Control Gates Log PDF, which contains records going back to November 1, 1998. This document replaces the Archived version because the Archived version did not contain a timestamp for every record. For the records that did have a timestamp, the timestamps were placed in the REMARKS field. This issue, along with the document being a PDF file, created a problem for reading the data into time-series analysis software.

Monthly salinity reports for the Suisun Marsh from October through May of each year.

Monthly salinity reports for the Suisun Marsh from October through May of each year.

The Suisun Marsh Salinity Control Gates (SMSCG) have the potential to increase low-salinity-zone habitat for endangered Delta Smelt (Hypomesus transpacificus, California Endangered Species Act listed as Endangered, Federal Endangered Species Act listed as Threatened), and to allow them to more frequently occupy Suisun Marsh, especially Montezuma Slough, one of their most important rearing habitats. Operation of the SMSCG in summer and fall to improve Delta Smelt habitat are called for in the Biological Opinion and Incidental Take permit for the Central Valley Project and State Water Project. To support the adaptive management of the action, the California Department of Water Resources monitored the change in water quality, phytoplankton, zooplankton, fishes, and clams resulting from the action in 2018. This data package includes data collected by the Interagency Ecological Program’s (IEP) long-term monitoring programs supplemented with targeted sample collection where existing surveys lack spatial or temporal coverage. This package also includes modeling the change in Delta Smelt habitat based on area of open water with appropriate temperature, salinity, and turbidity. Monitoring during no-action years (2019 and 2020) will be used as a baseline for comparison during action years. This data package will be updated annually during both action years and non-action years.

This digital dataset contains the surface water operational data used for the Salinas Valley Operational Model (SVOM) including the time series data and the operational rules. While much of the input data is shared between the Salinas Valley Operational Model (SVOM) and the Salinas Valley Integrated Hydrologic Model (SVIHM), the SVOM has additional input data specific to the purpose and function of the model. The SVOM is a hypothetical baseline model developed to examine the benefit of different reservoir operations to the availability of water resources for the San Antonio and Nacimiento Reservoirs. The San Antonio and Nacimiento reservoirs are used for regional water supply and management of Salinas River flows to support conservation, fish passage, and support downstream diversions for the Salinas Valley Watershed Model (SVWM). By using the SVOM, Monterey County can evaluate reservoir management projects and practices to help make decisions that optimize the use of available groundwater resources and develop habitat conservation plans to sustain threatened salmon populations. To improve flood protection and increase storage capacity, Monterey County is considering a 11,000-foot gravity-flow interlake tunnel connecting the Nacimiento and San Antonio reservoirs. The tunnel would allow the excess water from winter storm events to be captured and transferred into the San Antonio Reservoir, increasing storage capacity by 18%. The interlake tunnel would also require the spillway elevation to be raised as the San Antonio Reservoir dam to accommodate the additional water. The SVOM will be used to evaluate the feasibility and benefits of different tunnel and operation configurations in support of environmental and engineering design needs. While this data release includes some of the files necessary to set up the interlake tunnel scenario, the SVOM does not include the implementation or analysis for the interlake tunnel. The reservoir releases are dynamically simulated based on the defined operational rules, instead of a time series of historical releases like in SVIHM, using the surface water operations framework from MODFLOW-OHWM (Hanson and others, 2014; Boyce and others, 2020). The operation rules are based on current reservoir operation rules and legal constraints, allowing for the reservoir’s release into the stream network to be simulated internally to account for changes in reservoir storage and reservoir releases for conservation, demands, and flood management. Each rule is a set of logic statements that determine if reservoir releases are triggered. The time series data and supporting datasets included are required to carry out the logic in each of the rules.

These datasets provide information on soil properties, plant species cover, and soil surface elevation in a tidal wetland and a managed impounded wetland in northern Suisun Marsh, California, USA.

,

Annual report submitted by the DWR's Delta Modeling Section

Measurements of Selenium collected at Folsom South Canal At Florin Rd. Currently collected twice a year, previously collected quarterly. Access further information for this data set by contacting Bureau of Reclamation, California-Great Basin Region, Environmental Affairs Division (CGB-157). See ResultAttributes for STAFF_GAUGE, SMPL_DEPTH, SMPL_CATEGORY_NAME, METHOD_CODE, RESULT_RL, RESULT_RL-UNIT_STD_NAME, RESULT_MDL, RESULT_MDL-UNIT_STD_NAME, USBR_QA_SUBTYPE_NAME, USBR_QULFR_DESCRIPTION. STAFF_GAUGE is the water height in decimal feet measured by gauge (e.g., 15.2). SMPL_DEPTH is the vertical depth at which sample is collected (e.g., 0 - 15 cm). For water samples: depth below water/air interface. For sediment and soil samples: depth below water/solid or air/solid interface. SMPL_CATEGORY_NAME is the category type of sample (e.g., Composite). METHOD_CODE is the name of method used to obtain result (e.g., EPA 200.8). RESULT_RL is the result reporting limit (accounting for dilution) (e.g., 0.02). RESULT_RL-UNIT_STD_NAME is the unit associated with RESULT_RL (e.g., mg/L). RESULT_MDL is the result method detection limit (e.g., 0.007). RESULT_MDL-UNIT_STD_NAME is the unit associated with RESULT_MDL (e.g., mg/L). USBR_QA_SUBTYPE_NAME is the quality control type of the sample (e.g., USBR_BLANK_SPIKE). USBR_QULFR_DESCRIPTION is the quality assurance description (if any) (e.g., Result may have a high bias.).

Measurements of Selenium collected at Folsom South Canal At Grantline Rd. Currently collected twice a year, previously collected quarterly. Access further information for this data set by contacting Bureau of Reclamation, California-Great Basin Region, Environmental Affairs Division (CGB-157). See ResultAttributes for STAFF_GAUGE, SMPL_DEPTH, SMPL_CATEGORY_NAME, METHOD_CODE, RESULT_RL, RESULT_RL-UNIT_STD_NAME, RESULT_MDL, RESULT_MDL-UNIT_STD_NAME, USBR_QA_SUBTYPE_NAME, USBR_QULFR_DESCRIPTION. STAFF_GAUGE is the water height in decimal feet measured by gauge (e.g., 15.2). SMPL_DEPTH is the vertical depth at which sample is collected (e.g., 0 - 15 cm). For water samples: depth below water/air interface. For sediment and soil samples: depth below water/solid or air/solid interface. SMPL_CATEGORY_NAME is the category type of sample (e.g., Composite). METHOD_CODE is the name of method used to obtain result (e.g., EPA 200.8). RESULT_RL is the result reporting limit (accounting for dilution) (e.g., 0.02). RESULT_RL-UNIT_STD_NAME is the unit associated with RESULT_RL (e.g., mg/L). RESULT_MDL is the result method detection limit (e.g., 0.007). RESULT_MDL-UNIT_STD_NAME is the unit associated with RESULT_MDL (e.g., mg/L). USBR_QA_SUBTYPE_NAME is the quality control type of the sample (e.g., USBR_BLANK_SPIKE). USBR_QULFR_DESCRIPTION is the quality assurance description (if any) (e.g., Result may have a high bias.).