Coos Estuary, southern Oregon
Here you will find observational data we have collected or helped collect, as well as grid, forcing, and setup files to run our numerical simulations of the estuary. Please contact us if you use these data or the modeling resources, or have suggestions. Enjoy.
CTD Data [File, 2 MB]: A MATLAB file of all the along-estuary conductivity/temperature/depth (CTD) profiles we collected from 2012-2014, which are mostly described in Sutherland and O'Neill 2016. See the README for information on variables and more details.
ADCP Data [File1 File2]: A MATLAB file of water velocities, time, and depth from a Sontek 150 kHz ADCP. The ADCP was bottom mounted, upward looking, and deployed by the South Slough west of the main channel near the BLM docks. See the README for information on variables and more details.
Bathymetry: Many organizations have collected bathymetry data in and around the estuary. These include the USACE channel surveys, USACE Coastal Lidar, and NOAA. For our own work, we partnered with Peter Ruggiero at OSU to collect high-resolution transects to fill in gaps. The raw data are available here in a zip file [19 MB]. See the cruise report [8 MB, Word doc] for details. Additional data were collected in Spring 2017 and will be added when available.
Please contact us if you use these data or have comments/questions.
FVCOM Numerical Model
We use the open source Finite Volume Coastal Ocean Model code as our platform for modeling the hydrodynamics of the Coos estuary. Below we have put many of the items needed to successfully setup and run a version of the Coos estuary model using FVCOM v3.
Grid/Mesh [FILE}: This is the unstructured grid file for our model domain, created using SMS software and a coastline.
Bathymetry [FILE]: This bathymetry product was built from numerous data sources, starting with the NOAA DEM and adding higher res data on top. It is then smoothed for model purposes.
Discharge [FILE README file]: Discharge comes mainly from gages maintained by the Coos Watershed Association. The main river source is the Coos River, although numerous small sources of freshwater enter the estuary.
Tides: We use modeled tides to force the Coos estuary simulations, based on the TPXO/Poseidon inverse tidal model. Specifically, we use 13 constituents (e.g., M2, S2, N2, K2, K1, O1, P1) along the model domain boundary. These tides are checked with sea levels measured at the Charleston, OR, tide gage.
FVCOM parameter file [FILE]: An example run file from one of our recent simulations, showing the values for common parameters used and input/output flags.
Notes on setting up FVCOM [File1 File2]: A few files that contain notes created by our group on our progress, challenges, and tips on setting up FVCOM. File1 is mostly from Dave Sutherland on getting FVCOM running on a local server and initial hiccups. File2 will be on getting FVCOM running on a remote cluster, with additional challenges and hiccups discussed.
The links and resources below will allow you to explore more partners and stakeholders interested in the dynamics of the Coos estuary. Some of them also contain data resources.
Oregon DEQ LASAR Database (water quality data)
NANOOS observations (NVS Viewer)
UW Coastal Ocean modeling group (boundary conditions)
Partnership for Coastal Watersheds (local stakeholders)
Coquille Tribe (water quality monitoring)
Confederated Tribes of the Coos, Lower Umpqua, and Siuslaw (CTCLUSI, water quality monitoring)
Funding for this work has come from Oregon Sea Grant, the National Estuarine Research Reserve Science Collaborative, and the University of Oregon.