ExperimentalWe used data and feedback to make a user-friendly site. We’d love your feedback.
Back to data.ca.gov.

Interagency Ecological Program Zooplankton Study

The Zooplankton Study was implemented in 1972 to assess food resources available to fish in the upper San Francisco Estuary (SFE). Mandated by the State Water Resources Control Board's Water Right Decision D-1641, the study is conducted jointly by the California Department of Fish and Wildlife and the California Department of Water Resources under the guidance and management of the Interagency Ecological Program. For over five decades, this study has monitored the zooplankton community in the region, tracking abundance trends and distributional patterns, detecting and monitoring introduced species, and documenting changes in community composition. The Zooplankton Study uses three gear types to sample macro-, meso-, and micro-zooplankton across the upper SFE on a monthly basis. ## About This Federated Record This CNRA Open Data Platform record is based on metadata federated from the Environmental Data Initiative (EDI) Data Portal. Its purpose is to improve the discoverability of the data package through the CNRA Open Data Platform. The EDI Data Portal is the repository of record for this data package. Metadata, resource links, and supporting information displayed here may not reflect the latest updates available in EDI. Resources shown here—including Full Metadata, Provenance, and Data Quality Report—are provided to help users understand and evaluate the data package and the supporting information available from EDI. For the current data package, citation, DOI, data files, metadata, provenance, data quality documentation, revision history, and other supporting information, refer to the EDI data package landing page: https://portal.edirepository.org/nis/metadataviewer?packageid=edi.522.14&key=vqSpNwnbe91Bi8trB5RY25CoPD4 Access requirements, permissions, and authorization policies for resources hosted by EDI are established and managed independently of the CNRA Open Data Platform.

Data files

No files available

Supporting files

Data title and descriptionAccess dataFile detailsLast updated

1972-2024_CBMatrix_EDI

Catch-per-unit-effort for each zooplankton taxon. Note: CPUE is set up in a “cross-tabbed” structure, with ZooCode as column name, and CPUE as value. This allows one row per tow sample, with catch values for every organism.

CSV (EXTERNAL DOWNLOAD)
09/25/26

1972-2024_Mysid_Length_Data_EDI

Mysid length frequency

CSV (EXTERNAL DOWNLOAD)
09/25/26

1972-2024_MysidMatrix_EDI

Catch per unit effort of mysids. Note: CPUE is set up in a “cross-tabbed” structure, with ZooCode as column name, and CPUE as value. This allows one row per tow sample, with catch values for every organism.

CSV (EXTERNAL DOWNLOAD)
09/25/26

1972-2024_PumpMatrix_EDI

Catch per unit effort for pump sample taxa. Note: CPUE is set up in a “cross-tabbed” structure, with ZooCode as column name, and CPUE as value. This allows one row per tow sample, with catch values for every organism.

CSV (EXTERNAL DOWNLOAD)
09/25/26

StationLookup

Station locations, description and lat long when available

CSV (EXTERNAL DOWNLOAD)
09/25/26

ZooCode_lookup

Codes for zooplankton taxa

CSV (EXTERNAL DOWNLOAD)
09/25/26

EZ_Station_Locations_lookup

locations of EZ and EZ-SJR stations 1994-2024, location description and lat long if available

CSV (EXTERNAL DOWNLOAD)
09/25/26

amphipod_notes.pdf

Amphipod data previously uploaded to EDI contains errors, which will be corrected for a future upload. Amphipod data are not included in June 2025 upload. Description of QA/QC methods for amphipod data in macro_matrix.csv

PDF
09/25/26

Provenance Metadata

This method step describes provenance-based metadata as specified in the LTER EML Best Practices. This provenance metadata does not contain entity specific information.

HTML
09/25/26

Full Metadata

A link to the original metadata web page on the EDI Portal

HTML
09/25/26

Dataset Quality Report

A link to the EDI Quality Metadata Page

HTML
09/25/26

API endpoint

Dataset Name

Use the query web API to retrieve data with a set of basic parameters. Copy the API endpoint you need to start.

Usage documentation