Oceanographic time-series monitoring data of a shallow-water placement of dredged sediment in south San Francisco Bay, California, 2023-2025

Metadata also available as - [Outline] - [Parseable text] - [XML]

Frequently anticipated questions:

What does this data set describe?

Title:
Oceanographic time-series monitoring data of a shallow-water placement of dredged sediment in south San Francisco Bay, California, 2023-2025
Abstract:
Oceanographic and meteorological time-series monitoring data were collected by the U.S. Geological Survey (USGS) Pacific Coastal and Marine Science Center from 2023 to 2025, to monitor a pilot shallow-water placement of dredged sediment project led by the US Army Corps of Engineers San Francisco District. Data were collected at nine stations located in the shallows offshore of Whales Tail Marsh in south San Francisco Bay, CA. Stations were positioned around the placement site of the dredged material. Data were collected prior to, during, and after the sediment was placed. Stations consisted of platforms deployed along 2 transects: one along-shore and one cross-shore. Stations in the cross-shore transect included: XM, located approximately 25 meters from the bay edge on Whales Tail marsh; X4 located slightly offshore of the marsh; X3 just offshore (west) of X4; X2 (same location as XG and XL) east/marsh side of the placement area; X1 western side of the placement area; and X0 just east of the navigational channel. A wave-met buoy MW was close to and slightly east of X0. Along-shore transect platforms included AN and AS, north and south of the placement area, respectively. Data types include pressure, velocity, turbidity, suspended particle size distribution, conductivity, temperature, wave statistics, and wind speed and direction, barometric pressure and air temperature. Data files are grouped by deployment (A-E) then by station name (OR) instrument type, except for data recorded at station X0 and MW, which have their own folders. At several stations there were periods of low water when sensors were no longer submerged, resulting in spurious data. In addition, most instruments experienced some degree of biofouling. Users are advised to assess data quality carefully, and to check the metadata for instrument information, as platform deployment times and data-processing methods varied.
Supplemental_Information:
Additional information about the field activities from which these data were derived is available online at: https://cmgds.marine.usgs.gov/fan_info.php?fan=2023-655-FA Any use of trade, product, or firm names is for descriptive purposes only and does not imply endorsement by the U.S. Government. Image maps showing locations of sampling sites are located with the Supplemental files accompanying this dataset. Tables of filenames and contents as well as calibration data for optical instruments are also included.
  1. How might this data set be cited?
    McGill, Samantha C., Allen, Rachel M., Thede, Joanne C., Stevens, Andrew W., Dartnell, Peter, and Lacy, Jessica R., 20250820, Oceanographic time-series monitoring data of a shallow-water placement of dredged sediment in south San Francisco Bay, California, 2023-2025: data release DOI:10.5066/P14D723N, U.S. Geological Survey, Pacific Coastal and Marine Science Center Santa Cruz, California.

    Online Links:

    This is part of the following larger work.

    McGill, Samantha C., Lacy, Jessica R., Stevens, Andrew W., Allen, Rachel M., Dartnell, Peter, Thede, Joanne C., Tan, Angela C., and Hatcher, Gerald A., 2025, Oceanographic and hydrographic monitoring data of a shallow-water placement of dredged sediment in south San Francisco Bay, California, 2023-2025: data release DOI:10.5066/P14D723N, U.S. Geological Survey, Pacific Coastal and Marine Science Center, Santa Cruz, California.

    Online Links:

    Other_Citation_Details:
    Suggested Citation: McGill, S.C., Lacy, J.R., Stevens, A.W., Allen, R.M., Dartnell, P., Thede, J.C., Tan, A.C., and Hatcher, G.A., 2025, Hydrodynamic, bathymetric, and sediment transport data spanning dredge material placement in south San Francisco Bay, California, 2023-2025: U.S. Geological Survey data release, https://doi.org/10.5066/P14D723N.
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -122.22200
    East_Bounding_Coordinate: -122.14503
    North_Bounding_Coordinate: 37.60645
    South_Bounding_Coordinate: 37.57390
  3. What does it look like?
    DMP23_timeseries_summary_figure.png (PNG)
    A figure displaying the different instruments and data types collected over the duration of the project. Station MW is plotted separately below the main plot, since it had a deployment time range that extended beyond the other instruments.
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 14-Aug-2023
    Ending_Date: 10-Feb-2025
    Currentness_Reference:
    Ground condition at time data were collected.
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: NetCDF files
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
      Indirect_Spatial_Reference:
      Data were collected continuously at survey locations. Refer to self-contained netCDF files for more location information.
    2. What coordinate system is used to represent geographic features?
      Horizontal positions are specified in geographic coordinates, that is, latitude and longitude. Latitudes are given to the nearest 1.0E-5. Longitudes are given to the nearest 1.0E-5. Latitude and longitude values are specified in Decimal degrees. The horizontal datum used is World Geodetic System 1984 (WGS84).
      The ellipsoid used is WGS84.
      The semi-major axis of the ellipsoid used is 6378137.0.
      The flattening of the ellipsoid used is 1/298.257223563.
  7. How does the data set describe geographic features?
    Entity_and_Attribute_Overview:
    NetCDF files are self-contained and attribute information may be found in the header of the file itself.
    Entity_and_Attribute_Detail_Citation:
    The entity and attribute information were generated by the individual and/or agency identified as the originator of the data set. Please review the rest of the metadata record for additional details and information.

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Samantha C. McGill
    • Rachel M. Allen
    • Joanne C. Thede
    • Andrew W. Stevens
    • Peter Dartnell
    • Jessica R. Lacy
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
    U.S. Geological Survey, Pacific Coastal and Marine Science Center
    Attn: PCMSC Science Data Coordinator
    2885 Mission Street
    Santa Cruz, CA
    US

    831-427-4747 (voice)
    pcmsc_data@usgs.gov

Why was the data set created?

These data were collected as part of a collaborative study with USGS Western Ecological Research Center monitoring the pilot project conducted by U.S. Army Corps of Engineers San Francisco District. The study investigated the transport, impacts, and evolution of strategically placed dredged material in a shallow subtidal region adjacent to a marsh. Goals of this study were to assess the potential use of shallow-water placement for marsh management and restoration while gaining insight into local sediment transport adjacent to marshes in the shallows of south San Francisco Bay. These data are intended for researchers, students, policy makers, and the general public.

How was the data set created?

  1. From what previous works were the data drawn?
    atmospheric pressure (source 1 of 2)
    National Oceanic and Atmospheric Administration (NOAA), 2025, Redwood City, CA - Station ID: 9414523: National Oceanic and Atmospheric Administration (NOAA), online.

    Online Links:

    Type_of_Source_Media: online database
    Source_Contribution: data used for local atmospheric pressure corrections
    atmospheric pressure (source 2 of 2)
    National Oceanic and Atmospheric Administration (NOAA), 2025, Alameda, CA - Station ID: 9414750: National Oceanic and Atmospheric Administration (NOAA), online.

    Online Links:

    Type_of_Source_Media: online database
    Source_Contribution: data used for local atmospheric pressure corrections
  2. How were the data generated, processed, and modified?
    Date: 22-Sep-2023 (process 1 of 18)
    Deployment A: A total of seven platforms (AN, AS, X1, X2, XL, X3, and X4) were deployed between August 14th and 15th, 2023. Platforms AN and X1 were “grate” style platforms, both were equipped with an upward looking Nortek Aquadopp acoustic doppler profiler with a Seapoint turbidity meter mounted onto a weighted grate placed directly on the bottom surface. AN also included an RBR logger measuring pressure and temperature. X3 consisted of a Seapoint turbidity meter logged by an RBR Virtuoso single-channel data logger, as well as an RBR logger measuring pressure mounted onto was a weight-stand (single weight plate with a vertical pole). Three tripods (AS, X4, and X2) consisted of included a Nortek single point ADV (acoustic doppler velocimeter) each with a Seapoint turbidity meter. AS also had an RBR CTD (conductivity, temperature, and depth), while X2 had an addition Nortek single point acoustic doppler velocimeter with a Seapoint turbidity meter and a Seapoint turbidity meter logged by an RBR Virtuoso single-channel data logger. XL, which was located at station X2, had a Sequoia Scientific Laser in-situ scattering and transmissometry (LISST 200x) particle size analyzer, an RBR Virtuoso single-channel data logger with Seapoint turbidity meter, and a Sequoia Scientific submersible acoustic backscatter sensor (LISST-ABS) logged by a Nortek Vector. The Vector's only function was to log the LISST ABS data. All turbidity meters were equipped with a Zebra-Tech hydro-wiper to prevent biofouling. XL was recovered on September 5, 2023, all other platforms were recovered on September 22, 2023.
    Date: 11-Oct-2023 (process 2 of 18)
    An RDI Acoustic doppler current profiler mounted on a low-profile tripod was deployed at station X0, in the navigational channel, west of the placement area. This platform was recovered on October 11, 2023.
    Date: 04-Jan-2024 (process 3 of 18)
    Deployment B: On November 2, 2023, all six stations described during Deployment A were re-occupied with the with the same instrumented platform setup. These stations included: AN, AS, X1, X2, X3, and X4. Platform XL (located at station X2) was deployed and recovered twice during deployment B and was turned at shorter intervals (approximately two-week) because of the instrumentation’s high susceptibly biofouling. The platform at X1 was runover by a vessel, sustaining some damage on December 30, data were successfully recovered from instruments on the platform, however data following the collision were removed. Platforms were recovered on January 4, 2024.
    Date: 13-Aug-2024 (process 4 of 18)
    On November 2, 2023, an instrumented buoy which measure meteorological and wave parameters was deployed at a new station, MW. This platform consisted of a Nexsens CB-250 buoy equipped with an Airmar WX200 sensor to measure wind speed, buoy position and orientation, air temperature and relative barometric pressure. Directions recorded by the Nexsens buoy’s wind sensor were corrected to true north using a three-axis orientation sensor to account for motion of the buoy. Meteorological variables were averaged over a two-minute sampling interval and recorded using a Nexsens X2 data logger at 10 min intervals. The ultrasonic anemometer was located about 1.2 m above the sea surface. The buoy was recovered on August 13, 2024.
    Date: 21-Jan-2025 (process 5 of 18)
    A single marsh-top station (XM) was deployed roughly 25 m back from the Bay edge. XM consisted of a Seapoint turbidity meter logged by an RBR Virtuoso single-channel data logger, as well as an RBR logger measuring pressure attached to rebar above the marsh surface. The Seapoint turbidity meters were equipped with Zebra-Tech hydro-wipers to prevent biofouling. This platform was swapped out every 60-90 days, for a total of 4 deployments (B-E) which were always concurrent with the start/end of the other time-series platform deployment and recovery dates. The pressure sensor failed during deployment B, so only turbidity data are available during that time.
    Date: 06-Mar-2024 (process 6 of 18)
    Deployment C: On January 4, 2024, stations AN, AS, X1, X2, and X3 were deployed using the same types of instrumentation as prior deployments. Station X1 was deployed with the same instrumentation as before but also included an additional RBR logger measuring pressure and temperature; X3 included an additional RBR CTD. Station X4 and X1 were deployed on January 9, 2024. XL (deployed at station X2) was recovered after two weeks and deployed again on February 8, 2025, and included an EofE ECHOLOGGER EA400 profiling altimeter. Platforms were recovered on March 6, 2024.
    Date: 01-May-2024 (process 7 of 18)
    Deployment D: Four platforms were deployed on March 6, 2024. Station X1 consisted of a “grate” style platform again, equipped with an upward looking Nortek Aquadopp acoustic doppler profiler with a Seapoint turbidity meter mounted onto a weighted grate placed directly on the bottom surface. X2 consisted of a tripod equipped with two Nortek single point acoustic doppler velocimeter each with a Seapoint turbidity meter, an RBR CTD, and a Seapoint turbidity meter logged by an RBR Virtuoso single-channel data logger. The CTD at X2 failed, no conductivity/salinity data were published. Station X3 again consisted of a Seapoint turbidity meter logged by an RBR Virtuoso single-channel data logger, an RBR CTD, as well as an RBR logger measuring pressure mounted onto was a weight-stand (single weight plate with a vertical pole). Station X4 consisted of a Nortek single point acoustic doppler velocimeter each with a Seapoint turbidity meter mounted onto a tripod. All turbidity meters were equipped with a Zebra-Tech hydro-wiper to prevent biofouling. All platforms were recovered on May 1, 2024.
    Date: 13-Aug-2024 (process 8 of 18)
    Deployment E: During June 18, 2024, five platforms were deployed. X1 consisted of a “grate” style platform again, equipped with an upward looking Nortek Aquadopp acoustic doppler profiler with a Seapoint turbidity meter, and an RBR logger measuring pressure and temperature, all mounted onto a weighted grate placed directly on the bottom surface. A new grate style platform XG was also equipped with an upward looking Nortek Aquadopp acoustic doppler profiler with a Seapoint turbidity meter and deployed at station X2. The CTD at X2 failed, no conductivity/salinity data were published. Station X2 also included a tripod equipped with two Nortek single point acoustic doppler velocimeter each with a Seapoint turbidity meter, an RBR CTD, and a Seapoint turbidity meter logged by an RBR Virtuoso single-channel data logger. Station X3 again consisted of a Seapoint turbidity meter logged by an RBR Virtuoso single-channel data logger, an RBR CTD, as well as an RBR logger measuring pressure mounted onto was a weight-stand (single weight plate with a vertical pole). Station X4 again consisted of a Nortek single point acoustic doppler velocimeter each with a Seapoint turbidity meter mounted onto a tripod. All turbidity meters were equipped with a Zebra-Tech hydro-wiper to prevent biofouling. Platforms were recovered on August 13, 2024.
    Date: 10-Feb-2025 (process 9 of 18)
    On October 25, 2024, an instrumented buoy which measure meteorological and wave parameters was deployed again at station MW. This platform consisted of a Nexsens CB-250 buoy equipped with an Airmar WX200 sensor to measure wind speed, buoy position and orientation, air temperature and relative barometric pressure. The ultrasonic anemometer was located about 1.2 m above the sea surface. The buoy was recovered on February 10, 2025.
    Date: 11-Apr-2025 (process 10 of 18)
    The raw data files from each sensor were processed and converted to netCDF using stglib python libraries, a package of code to process data consistent with procedures of the USGS Coastal/Marine Hazards and Resources Program. In stglib, attributes conforming to Climate and Forecast (CF) Conventions version 1.6 were added. All times are in Coordinated Universal Time (UTC).
    Date: 11-Apr-2025 (process 11 of 18)
    Data were accumulated into netCDF files. During post-processing, data collected before deployment and after recovery were removed. Data quality assurance and quality control (QAQC) was performed by inspecting all variables and replacing spurious values with the fill value. Bad data points identified by 1) the deployment and recovery times, 2) data flagged as erroneous by the manufacturer, 3) amplitude or correlation values outside of predetermined quality thresholds for the velocimeter were removed. Further details on which portions of data were flagged and replaced are available in the metadata in each netCDF file and information about the individual QAQC trimming functions are available in the stglib documentation (https://doi.org/10.5066/P13IQYFW) in the "Instrument configuration file" section. The files include data of intermittent poor quality due to various reasons which may include but are not limited to biofouling, movement of platform, and exposure during low tides. Despite removal of bad data, some are still present in the files and therefore judgment should be applied when using them, as with all other data files. Use of all data requires careful assessment of data quality.
    Date: 11-Apr-2025 (process 12 of 18)
    All pressure data were given a new variable P_1ac, that contains atmospherically corrected pressure data. For this correction, the residual difference between the in-air reading of the pressure sensor and the NOAA station was removed and is noted in the netCDF file as atmospheric_pressure_correction_offset_applied. The atmospheric pressure data used for the correction were collected from NOAA station 9414523, Redwood City, CA. Gaps in the Redwood City record, which occurred during a few but not all deployment periods, were filled by interpolation data from NOAA station 9414750, Alameda, CA. Data sources used in this process:
    • atmospheric pressure
    Date: 11-Apr-2025 (process 13 of 18)
    For each turbidity sensor, a linear least-squares regression with intercept of zero was made between the turbidity values (in NTU or volts) and sample suspended sediment concentration (SSC) values (in milligrams per liter) from in situ measurements coincident to water sample collection. These constants are available as a support file in this data release DMP_Turbidity_to_SSC_calibration_constants.csv. Users should also note the gain setting used when applying a calibration coefficient to the turbidity data, all turbidity to SSC calibration constants were based on 5x gain setting.
    Date: 09-May-2025 (process 14 of 18)
    Comparison of pressure data from the RDI ADCP at XO with the known water depth identified a scaling error later confirmed by the manufacturer. ADCP pressure data was compared with pressure data from the Nortek Aquadopp at the nearest site X1. A comparison of the mean-removed pressure from the 2 instruments resulted in a scaling factor of 1.9511 with a statistical correlation of 1.00. This scaling factor was applied to the ADCP pressure data prior to the atmospheric pressure correction.
    Date: 11-Jul-2025 (process 15 of 18)
    Surface waves were sampled using a Seaview SVS-603HR wave sensor on the buoy. The sensor was configured to measure wave time-series at 4 Hz intervals during 8.5-minute bursts. Directional data were corrected to true north using the magnetic compass within the sensor and adjusted by +13 deg to account for magnetic declination at the site. Algorithms in the sensor computed bulk wave statistics and spectral information in real time were recorded to a micro-SD card in the wave sensor.
    Date: 13-Aug-2025 (process 16 of 18)
    Wave statistics were calculated from the bursts of velocity and pressure measured by the ADV and from the bursts of pressure measured by the RBR bursting pressure logger. Calculations were completed using routines available on https://doi.org/10.5066/P13IQYFW. Additional information on frequency cutoffs used for the calculations can be found in the metadata of the nc data file.
    Date: 13-Aug-2025 (process 17 of 18)
    Files were named with a convention that uses a 13- to 17-digit alpha-numeric code. The first three characters for this dataset are all “DMP” indicating the experiment name (Dredge Material Placement); the fourth and fifth positions represent the calendar year in which the project commenced (23, 2023); the sixth character is a letters representing the orientation of the transect the station was in (A, along-shore transect; X, cross-shore transect); the seventh character is either a letter or a number representing the station's location (N, north; S, south; M, marsh; 0-4; where 0 is the western most station and 4 is the eastern most station); the eight character is a letter corresponding to the deployment (A through I, where A is the first deployment); the ninth and tenth characters represent the instrument position on the platform, where 01 is the top-most. The eleventh, twelfth, and sometimes thirteenth characters are abbreviations for the instrument type (vec, Norteks acoustic doppler velocimeter; aq, Nortek aquadopp acoustic doppler current profiler; pt, RBRs bursting pressure sensor with temperature; pr, RBRs pressure sensor; ctd, RBRs conductivity, temperature, and depth logger; tu, RBRs Virtuoso turbidity logger; ls, Sequoia LISST 200x; alt, EofE EchoLogger EA400 profiling altimeter; wh, RDI acoustic doppler current profiler). There are an additional 1 to 4 characters with a hyphen used to convey information about the data contained in the file. Filenames containing (-a) were used for instruments with singular observations, the (b-a) indicate that the file contain burst statistics/burst averaged data, while filenames with (b) indicate burst observations for bursting instruments, the (s-a) indicates the file contains wave statistics. The only exception to file naming is for station MW (the wave-met buoy), whose first five characters follow the same naming convention as other files, but 6th and 7th characters are 'MW' representing the stations name, the eighth character is a number specifying the deployment number, the ninth and tenth characters are numbers that represent the instrument position on the platform, where 01 is the top-most. The eleventh through thirteenth characters indicate the type of data (wvs, wave statistics or met, meteorological data); Information on the files available for each station and the data each file contains is listed in the DMP_time_series_file_table.csv.
    Date: 13-Aug-2025 (process 18 of 18)
    The netCDF files were compressed and combined in zipped folders for each deployment (A-E, 5 total), within the zipped deployment folders are subfolders for each station. The wave-meteorological buoy data are zipped separately by deployment (2 total), the ADCP are zipped separately as well. Details on the including data type and file name for each deployment and platform can be found in the support file: DMP23_time_series_file_table.csv.
  3. What similar or related data should the user be aware of?
    Nowacki, D.J., Suttles, S.E., Bales, R.D., and De Meo, O.A., 2024, stglib: Oceanographic Time Series Data Processing Library.

    Online Links:

    Other_Citation_Details:
    Nowacki, D.J., Suttles, S.E., Bales, R.D., De Meo, O.A., 2024, stglib: Oceanographic Time Series Data Processing Library, U.S. Geological Survey software release, doi:10.5066/P13IQYFW.

How reliable are the data; what problems remain in the data set?

  1. How well have the observations been checked?
    No formal attribute accuracy tests were conducted. Data were collected in a complex and changing physical environment. Sites are intermittently inundated and affected by tidal and atmospheric variation. Instruments at the same site are submerged or partially submerged at varying times. Ambient air temperature, as well as water temperature, may affect measurements. Biological fouling may have impacted data quality. Data are raw unless noted in the netCDF file metadata, as the removal of bad data is highly interpretative and may result in a loss of information, preventing further analysis and understanding. Individual instrument accuracy can be found on each manufacturer’s website.
  2. How accurate are the geographic locations?
    Horizontal location data were collected ship navigational system, except for XM, which was collected via global navigation satellite system (GNSS) receivers operating in real time kinematic mode with differential corrections from a single GNSS base station placed on a benchmark with established coordinates relative to the North American Datum of 1983 (2011 realization). The estimated uncertainty in horizontal positions at the 95 percent confidence interval was 0.033 m. All other horizontal positions were derived from ship navigation systems, which included: Garmin GPSMAP 7610 and a Garmin GPS19x antenna, Garmin GPSmap XSV chartplotter and a Garmin GPS19x antenna, and Garmin Echomap UHD2 64sv w/ inbuilt GPS antenna; all were WAAS-capable, and had location to within 3 m.
  3. How accurate are the heights or depths?
    There are two sources of uncertainty associated with vertical positioning of the instruments: 1) the measuring tools used during instrument mounting, 2) the amount of settling that occurs during deployment. No corrections were made to the data to account for these errors. Users may refer to the pre-deployment sensor heights provided in the datafiles in addition to the nominal heights of the sensors which are also found in the data files to verify changes in sensor elevation. The heights provided do not account for any sinking that may have occurred during the deployment.
  4. Where are the gaps in the data? What is missing?
    Dataset is considered complete for the information presented, as described in the abstract. Data outside of the deployment and recovery times have been removed. Users are advised to read the metadata in each netCDF file carefully for additional details affecting individual instruments and sensors.
  5. How consistent are the relationships among the observations, including topology?
    No formal logical accuracy tests were conducted. Data fall within expected ranges, however due to the intermittent and gradual inundation of tidal and marsh sites, some measurements will be in air while others are in water (including at the same site). Data spikes that reflect the changing conditions have been retained as the assessment of data quality and accuracy may be useful in interpretation and analysis.

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?
Access_Constraints No access constraints
Use_Constraints USGS-authored or produced data and information are in the public domain from the U.S. Government and are freely redistributable with proper metadata and source attribution. Please recognize and acknowledge the U.S. Geological Survey as the originators of the dataset and in products derived from these data. This information is not intended for navigation purposes.
  1. Who distributes the data set? (Distributor 1 of 1)
    U.S. Geological Survey - CMGDS
    2885 Mission Street
    Santa Cruz, CA

    831-427-4747 (voice)
    pcmsc_data@usgs.gov
  2. What's the catalog number I need to order this data set? Downloadable data in netCDF format and compressed into zipped archives. The netCDF files were compressed and combined in zipped folders for each deployment (A-E, 5 total), within the zipped deployment folders are subfolders for each station. The wave-meteorological buoy data are zipped separately by deployment (2 total), the ADCP data are zipped separately as well. Instrument type suffixes follow the nomenclature defined above for filenames including a two- or three-character code for the instrument type (vec, Nortek acoustic doppler velocimeter; aqd, Nortek aquadopp acoustic doppler current profiler; pt, RBRs bursting pressure sensor with temperature; pr, RBRs pressure sensor; ctd, RBRs conductivity, temperature, and depth logger; tu, RBRs Virtuoso turbidity logger; ls, Sequoia LISST 200x; alt, EofE EchoLogger EA400 profiling altimeter; wh, RDI acoustic doppler current profiler). The suffixes for the station MW files are: "wvs", wave statistics; "met", meteorological data. Information on the files available for each station and the data each file contains is listed in the DMP_time_series_file_table.csv.
  3. What legal disclaimers am I supposed to read?
    Unless otherwise stated, all data, metadata and related materials are considered to satisfy the quality standards relative to the purpose for which the data were collected. Although these data and associated metadata have been reviewed for accuracy and completeness and approved for release by the U.S. Geological Survey (USGS), no warranty expressed or implied is made regarding the display or utility of the data on any other system or for general or scientific purposes, nor shall the act of distribution constitute any such warranty.
  4. How can I download or order the data?
    • Availability in digital form:
      Data format: Downloadable zip file of time-series data in netCDF format following CF 1.8 or CF-1.10 Metadata Conventions. File download sizes range from 17.6 to 200 MB. in format NetCDF (version netCDF-4, CF-1.8, CF-1.10) Data are in netCDF formats. Size: 6035.1
      Network links: https://doi.org/10.5066/P14D723N
    • Cost to order the data: None.

  5. What hardware or software do I need in order to use the data set?
    The downloadable data file has been compressed with the "zip" command and can be unzipped with Winzip or other archive utilities. To utilize these data, the user must have software capable of uncompressing the WinZip file and importing and viewing a netCDF file.

Who wrote the metadata?

Dates:
Last modified: 20-Aug-2025
Metadata author:
PCMSC Science Data Coordinator
U.S. Geological Survey, Pacific Coastal and Marine Science Center
2885 Mission Street
Santa Cruz, CA
United States

831-427-7520 (voice)
pcmsc_data@usgs.gov
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)
This page is <https://cmgds.marine.usgs.gov/catalog/pcmsc/DataReleases/CMGDS_DR_tool/DR_P14D723N/DMP23_timeseries_metadata.faq.html>
Generated by mp version 2.9.51 on Tue Sep 2 13:32:13 2025