Nearshore bathymetry data from the Elwha River delta, Washington, July 2016, collected from kayak

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

Frequently anticipated questions:

What does this data set describe?

Title:
Nearshore bathymetry data from the Elwha River delta, Washington, July 2016, collected from kayak
Abstract:
This part of the data release presents bathymetry data from the Elwha River delta collected in July 2016 using a kayak. The kayak was equipped with a single-beam echosounder and a survey-grade global navigation satellite system (GNSS) receiver.
Supplemental_Information:
Additional information about the field activities from which these data were derived are available online at: http://cmgds.marine.usgs.gov/fan_info.php?fan=2016-653-FA
  1. How might this data set be cited?
    Stevens, Andrew W., Gelfenbaum, Guy, Warrick, Jonathan A., Miller, Ian M., and Weiner, Heather M., 2016, Nearshore bathymetry data from the Elwha River delta, Washington, July 2016, collected from kayak: data release DOI:10.5066/F7GQ6VXX, U.S. Geological Survey, Santa Cruz, CA.

    Online Links:

    This is part of the following larger work.

    Stevens, Andrew W., Gelfenbaum, Guy, Warrick, Jonathan A., Miller, Ian M., and Weiner, Heather M., 2016, Bathymetry, topography, and sediment grain-size data from the Elwha River delta, Washington, July 2016: data release DOI:10.5066/F7GQ6VXX, U.S. Geological Survey, Santa Cruz, CA.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -123.569342
    East_Bounding_Coordinate: -123.562184
    North_Bounding_Coordinate: 48.149713
    South_Bounding_Coordinate: 48.144250
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 19-Jul-2016
    Ending_Date: 19-Jul-2016
    Currentness_Reference:
    ground condition at time data were collected
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: comma-delimited text
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
      This is a Point data set.
    2. What coordinate system is used to represent geographic features?
      The map projection used is Lambert Conformal Conic.
      Projection parameters:
      Standard_Parallel: 47.5
      Standard_Parallel: 48.73333333333333
      Longitude_of_Central_Meridian: -120.8333333333333
      Latitude_of_Projection_Origin: 47.0
      False_Easting: 500000.0
      False_Northing: 0.0
      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 0.001
      Ordinates (y-coordinates) are specified to the nearest 0.001
      Planar coordinates are specified in METERS
      The horizontal datum used is NAD83 (CORS96).
      The ellipsoid used is GRS_1980.
      The semi-major axis of the ellipsoid used is 6378137.0.
      The flattening of the ellipsoid used is 1/298.257222101.
      Vertical_Coordinate_System_Definition:
      Altitude_System_Definition:
      Altitude_Datum_Name: North American Vertical Datum of 1988
      Altitude_Resolution: 0.001
      Altitude_Distance_Units: meters
      Altitude_Encoding_Method:
      Explicit elevation coordinate included with horizontal coordinates
  7. How does the data set describe geographic features?
    Attribute Table
    Table containing attribute information associated with the dataset (Source: Producer defined)
    Survey_Date
    The date corresponding to the start of the multi-day survey in mm/dd/yyyy format (Source: Producer Defined)
    Range of values
    Minimum:07/17/2016
    Maximum:07/17/2016
    Units:date in mm/dd/yyyy format
    Longitude
    Longitude coordinate of data point relative to the North American Datum of 1983 (CORS96 realization) (Source: Producer defined)
    Range of values
    Minimum:-123.569342
    Maximum:-123.562184
    Units:Decimal degrees
    Latitude
    Latitude coordinate of data point relative to the North American Datum of 1983 (CORS96 realization) (Source: Producer defined)
    Range of values
    Minimum:48.144250
    Maximum:48.149713
    Units:Decimal degrees
    X
    East coordinate of data point relative to the North American Datum of 1983 (CORS96 realization), projected in the Washington State Plane, North, meters, coordinate system (Source: Producer defined)
    Range of values
    Minimum:296464.330
    Maximum:296984.350
    Units:meters
    Y
    North coordinate of data point relative to the North American Datum of 1983 (CORS96 realization), projected in the Washington State Plane, North, meters, coordinate system (Source: Producer defined)
    Range of values
    Minimum:130821.410
    Maximum:131441.240
    Units:meters
    Ellip_Ht_m
    Height in meters of data point with reference to the reference ellipsoid (Source: Producer defined)
    Range of values
    Minimum:-20.920
    Maximum:-18.610
    Units:meters
    Ortho_Ht_m
    Height in meters of data point with reference to the North American Vertical Datum of 1988 at the base station (-20.11 m above ellipsoid height). (Source: Producer defined)
    Range of values
    Minimum:-0.810
    Maximum:1.500
    Units:meters

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Andrew W. Stevens
    • Guy Gelfenbaum
    • Jonathan A. Warrick
    • Ian M. Miller
    • Heather M. Weiner
  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?

Data were obtained to assess the coastal geomorphic response following the removal of two dams on the Elwha River. These data are intended for science researchers, students, policy makers, and the general public. These data can be used with geographic information systems or other software to identify topographic and shallow-water bathymetric features.

How was the data set created?

  1. From what previous works were the data drawn?
  2. How were the data generated, processed, and modified?
    Date: 19-Jul-2016 (process 1 of 6)
    Bathymetry data were collected on July 19, 2016 in the river channel and portions of the estuary using a kayak equipped with a SonarMite single-beam echosounder and 200 kHz transducer with a 4 degree beam angle. Depths from the kayak sonar were computed assuming a sound velocity if 1,460 m/s. Positioning of the kayak was determined at 1-Hz using a Trimble R7 GNSS receiver and Trimble Zephyr Model 2 antenna operating in real-time kinematic (RTK) mode. Differential corrections were transmitted by a VHF radio to the GNSS receiver on the kayak at 1-Hz from a base station placed on a benchmark with known horizontal and vertical coordinates relative to the North American Datum of 1983 (CORS96 realization) and North American Vertical Datum of 1988. Bathymetric soundings and positioning data were recorded on a Trimble TSC2 data collector.
    Date: 22-Jul-2016 (process 2 of 6)
    Raw data were reviewed and quality control was applied using Trimble Business Center software. Elevations relative to the NAVD88 vertical datum were computed using a static offset of -20.11 m based on the National Geodetic Survey Geoid09 offset computed at the base station locations. The final data are projected in Cartesian coordinates using the Washington State Plane North, meters coordinate system.
    Date: 18-Nov-2016 (process 3 of 6)
    All available bathymetry data from the survey were compiled into a comma-delimited text file for distribution.
    Date: 02-Oct-2025 (process 4 of 6)
    Data and metadata files were moved to a different location on ScienceBase, resulting in a change of ID number in the Online_Linkage and Network_Resources URLs of the metadata. In addition, edits were made as needed to bring the metadata up to current PCMSC standards including standardizing doi# links, correcting typos, adding disclaimers, and refining keywords. Point of Contact and Metadata Contact information sections were changed to static PCMSC contact information. No data were changed. Users are advised to compare the metadata date of this file to any similar file to ensure they are using the most recent version. Person who carried out this activity:
    Susan A Cochran
    U.S. Geological Survey, Pacific Coastal and Marine Science Center
    2885 Mission St.
    Santa Cruz, CA
    United States

    831-460-7545 (voice)
    scochran@usgs.gov
    Date: 19-Oct-2020 (process 5 of 6)
    Edited metadata to add keywords section with USGS persistent identifier as theme keyword. No data were changed. Person who carried out this activity:
    U.S. Geological Survey
    Attn: VeeAnn A. Cross
    Marine Geologist
    384 Woods Hole Road
    Woods Hole, MA

    508-548-8700 x2251 (voice)
    508-457-2310 (FAX)
    vatnipp@usgs.gov
    Date: 14-Oct-2021 (process 6 of 6)
    Performed minor edits to the metadata to correct typos. No data were changed Person who carried out this activity:
    U.S. Geological Survey
    Attn: Susan A. Cochran
    Geologist
    2885 Mission Street
    Santa Cruz, CA

    831-460-7545 (voice)
    scochran@usgs.gov
  3. What similar or related data should the user be aware of?
    International Hydrographic Organization (IHO), 2008, IHO standards for hydrographic surveys (5th ed.): International Hydrographic Bureau Special Publication 44, 28p., Monaco.

    Online Links:

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
  2. How accurate are the geographic locations?
    A series of benchmarks with known coordinates were established adjacent to the study area to provide geodetic control for the bathymetric survey. The positions of the benchmarks were derived from a minimum of two static GNSS occupations. The equipment for the static occupations consisted of a dual frequency Trimble R7 GNSS receiver, a fixed-height tripod, and Trimble Geodetic Model 2 antenna. The static observations were recorded internally in the receiver and the raw observations were processed using the National Geodetic Survey Online Positioning User Service (OPUS, https://www.ngs.noaa.gov/OPUS/). Estimated uncertainties in the horizontal position of the individual GNSS occupations were provided by OPUS and ranged between 0.006 m and 0.06 m with an average horizontal uncertainty of 0.02 m. The processed positions from each occupation were averaged to obtain the final reported position of the benchmark. All final positions of the survey vessel were determined using differential corrections from the base station receivers. Manufacturer reported accuracy for the differentially corrected horizontal positions for the Trimble R7 rover trajectories is 0.8 cm + 0.5 ppm. Baselines from the GNSS base station were typically less than 5 km, suggesting a horizontal accuracy of survey-vessel positions to be 0.825 cm relative to the base station. The combined horizontal uncertainty from the base station coordinate solutions and rover trajectories is between 1.5 cm and 7 cm with a mean horizontal uncertainty of 3 cm. Uncertainty in the horizontal positions associated with pitch and roll of the survey vessel is unknown.
  3. How accurate are the heights or depths?
    Uncertainty in the final elevations are derived from the combination of uncertainty in the GNSS positioning and bathymetric sounding measurements. Manufacturer reported accuracy for the differentially corrected vertical positions for the Trimble R7 rover trajectories is 1.5 cm + 1 ppm. Baselines from the GNSS base station were typically less than 5 km, suggesting the vertical accuracy of survey vessel positions to be 2 cm relative to the base station coordinate. Combining the uncertainty in the elevation of the base station coordinates and rover positions yields a total uncertainty in the GNSS-derived survey-vessel positions of approximately 5 cm. Additional uncertainty in the final computed elevations data is related to variability in the speed of sound used to compute depths from bathymetric soundings and, thus, are depth-dependent. The speed of sound in the river was not measured and we estimate the uncertainty in the final elevations to be 2 percent of water depth. The total vertical uncertainty is calculated using Equation 1: sigmat=sqrt(a^2+(b×d)^2 ), where sigmat is the total vertical uncertainty, a is the uncertainty of the GNSS vertical position, b is the depth-dependent uncertainty factor (0.02), and d is water depth. Maximum water depths surveyed by the kayak are approximately 3 m yielding a maximum total vertical uncertainty of 8 cm. Uncertainty in the vertical positions associated with pitch and roll of the kayak is unknown.
  4. Where are the gaps in the data? What is missing?
    Dataset is considered complete for the information presented, as described in the abstract. Users are advised to read the rest of the metadata record carefully for additional details.
  5. How consistent are the relationships among the observations, including topology?
    All data falls within expected ranges.

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?
Access_Constraints: none
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 originator(s) of the dataset and in products derived from these data. This information is not intended for navigational purposes.
  1. Who distributes the data set? (Distributor 1 of 1)
    U.S. Geological Survey - Science Base
    U.S. Geological Survey
    Denver Federal Center, Building 810, Mail Stop 302
    Denver, CO
    USA

    1-888-275-8747 (voice)
    sciencebase@usgs.gov
  2. What's the catalog number I need to order this data set? Bathymetry data are available as a comma-delimited text file (ew16_july_kayak.txt), along with associated metadata.
  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?

Who wrote the metadata?

Dates:
Last modified: 19-Oct-2020
Metadata author:
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
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)
This page is <https://cmgds.marine.usgs.gov/catalog/pcmsc/DataReleases/ScienceBase/DR_F7GQ6VXX/ew16_july_kayak.faq.html>
Generated by mp version 2.9.50 on Fri Oct 15 19:10:26 2021