Topography data from the Elwha River delta, Washington, August 2019

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

Frequently anticipated questions:

What does this data set describe?

Title:
Topography data from the Elwha River delta, Washington, August 2019
Abstract:
This part of the data release presents topography data from the Elwha River delta collected in August 2019. Topography data were collected on foot with global navigation satellite system (GNSS) receivers mounted on backpacks.
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=2019-633-FA
Any use of trade, product, or firm names is for descriptive purposes only and does not imply endorsement by the U.S. Government.
  1. How might this data set be cited?
    Stevens, Andrew W., Gelfenbaum, Guy R., Warrick, Jonathan A., Miller, Ian M., and Weiner, Heather M., 20241112, Topography data from the Elwha River delta, Washington, August 2019: data release DOI:10.5066/P9CR1ABQ, U.S. Geological Survey, Pacific Coastal and Marine Science Center, Santa Cruz, California.

    Online Links:

    This is part of the following larger work.

    Stevens, Andrew W., Gelfenbaum, Guy R., Warrick, Jonathan A., Miller, Ian M., and Weiner, Heather M., 2024, Bathymetry, topography, and sediment grain-size data from the Elwha River delta, Washington, August 2019: data release DOI:10.5066/P9CR1ABQ, U.S. Geological Survey, Pacific Coastal and Marine Science Center, Santa Cruz, CA.

    Online Links:

    Other_Citation_Details:
    Stevens, A.W., Gelfenbaum, G.R., Warrick, J.A., Miller, I.M., and Weiner, H.M., 2024, Bathymetry, topography, and sediment grain-size data from the Elwha River delta, Washington, August 2019: U.S. Geological Survey data release, https://doi.org/10.5066/P9CR1ABQ.
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -123.5880331
    East_Bounding_Coordinate: -123.4720764
    North_Bounding_Coordinate: 48.1518607
    South_Bounding_Coordinate: 48.1316920
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 26-Aug-2019
    Ending_Date: 29-Aug-2019
    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. It contains the following vector data types (SDTS terminology):
      • Point (217481)
    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 0.0000001. Longitudes are given to the nearest 0.0000001. Latitude and longitude values are specified in Decimal degrees. The horizontal datum used is North American Datum of 1983.
      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.01
      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)
    datetime_utc
    The date and time of data collection in Coordinated Universal Time (UTC). (Source: Producer defined)
    Range of values
    Minimum:2019-Aug-26 17:32:44.000
    Maximum:2019-Aug-29 17:13:34.000
    Units:date and time in yyyy-mmm-dd HH:MM:SS.FFF format
    longitude
    Longitude coordinate of data point relative to the North American Datum of 1983 (Source: Producer defined)
    Range of values
    Minimum:-123.5880331
    Maximum:-123.4720764
    Units:Decimal degrees
    latitude
    Latitude coordinate of data point relative to the North American Datum of 1983 (Source: Producer defined)
    Range of values
    Minimum:48.1316920
    Maximum:48.1518607
    Units:Decimal degrees
    easting_m
    East coordinate of data point relative to the North American Datum of 1983, projected in the Washington State Plane North, meters, coordinate system (Source: Producer defined)
    Range of values
    Minimum:295025.34
    Maximum:303642.86
    Units:meters
    northing_m
    North coordinate of data point relative to the North American Datum of 1983,projected in the Washington State Plane South, meters, coordinate system (Source: Producer defined)
    Range of values
    Minimum:129274.07
    Maximum:131657.35
    Units:meters
    ortho_ht_m
    Height in meters relative to the NAVD88 vertical datum, computed assuming a static geoid value of -20.11 m which is based on the NGS Geoid09 offset at the location of the GNSS base station (Source: Producer defined)
    Range of values
    Minimum:-1.77
    Maximum:5.56
    Units:meters
    Entity_and_Attribute_Overview: The first line of the csv file is a header line.
    Entity_and_Attribute_Detail_Citation: U.S. Geological Survey

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 R. 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

    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: 29-Aug-2019 (process 1 of 3)
    Topographic data were collected between August 26 and August 29, 2019, on foot with GNSS equipment mounted on backpacks operating primarily in real-time kinematic (RTK) mode. GNSS backpacks were equipped with a dual-frequency GNSS receivers and handheld data collectors. Differential corrections were transmitted at 1-Hz intervals by a VHF radio to the backpack GNSS receivers from a GNSS 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. Prior to data collection, vertical distances between the GNSS antenna and the ground were measured using a tape measure for each topographic surveyor. Hand-held data collectors were used to log raw data and display navigational information allowing surveyors to navigate along predefined survey lines spaced at 25- to 50-m intervals along the delta. Profiles were surveyed from the landward edge of the primary dune over the beach foreshore, to wading depth on the same series of transects as the nearshore bathymetry platforms. Additional topography data between transects were collected to better characterize morphologic variability within the study area.
    Date: 15-Mar-2020 (process 2 of 3)
    Raw topography data were reviewed in Trimble Business Center (TBC) to ensure measured antenna offsets were applied properly in the field. Differential post-processing was performed on points collected in autonomous mode where VHF communication with the base station failed. Orthometric elevations relative to the NAVD88 vertical datum were computed assuming a static geoid value of -20.11 m which is based on the NGS Geoid09 offset at the location of the GNSS base stations. The final point data are projected in cartesian coordinates using the Washington State Plane North, meters coordinate system.
    Date: 08-Dec-2023 (process 3 of 3)
    All available topographic data from the survey were compiled into a comma-delimited text file for distribution
  3. What similar or related data should the user be aware of?

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 and topographic surveys. 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 GNSS receiver, a fixed-height tripod, and antenna. The static observations were recorded internally in the receiver and the raw observations were processed using the National Geodetic Survey (NGS) 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 GNSS backpacks were determined using differential corrections from the base station receivers. Manufacturer reported accuracy for the differentially corrected horizontal positions for the rover receivers used in the survey is 0.8 cm + 0.5 ppm. Baselines from the GNSS base station were typically less than 5 km, suggesting a horizontal accuracy of backpack 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 therefore approximately 3 cm. Uncertainty in the horizontal positions associated with variable posture during data collection of the surveyors is unknown.
  3. How accurate are the heights or depths?
    The vertical uncertainty of topographic measurements is estimated by combining the uncertainty in the base station coordinate and remote GNSS positions collected in kinematic mode. Uncertainties in the elevation of the base station were provided by NGS OPUS and ranged between 0.02 m and 0.04 m, with an average vertical uncertainty of 0.03 m. Manufacturer reported vertical accuracy in the rover positions is 1.5 cm + 1 ppm for differential corrected kinematic data for the rover receivers used in the surveys. Baseline lengths were typically less than 5 km, suggesting the vertical accuracy of backpack positions to be 2 cm relative to the base station coordinates. Combining the uncertainty in the elevation of the base station coordinates and rover positions yields a total uncertainty in the backpack GNSS positions of approximately 5 cm. Uncertainty in the vertical positions associated with variable posture of the surveyors during data collection 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?
    No formal logical accuracy tests were conducted.

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 originator(s) 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 - 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? Topography data are available as a comma-delimited text file (ew19_topo.csv), along with associated FGDC-compliant 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: 12-Nov-2024
Metadata author:
U.S. Geological Survey, Pacific Coastal and Marine Science Center
Attn: PCMSC Science Data Coordinator
2885 Mission Street
Santa Cruz, CA

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_P9CR1ABQ/ew19_topo_metadata.faq.html>
Generated by mp version 2.9.51 on Fri Nov 15 15:39:06 2024