Nearshore bathymetry of the Columbia River littoral cell, Washington and Oregon, 2023

Frequently anticipated questions:

• What does this data set describe?
  1. How might this data set be cited?
  2. What geographic area does the data set cover?
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
  5. What is the general form of this data set?
  6. How does the data set represent geographic features?
  7. How does the data set describe geographic features?
• Who produced the data set?
  1. Who are the originators of the data set?
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
• Why was the data set created?
• How was the data set created?
  1. From what previous works were the data drawn?
  2. How were the data generated, processed, and modified?
  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?
  2. How accurate are the geographic locations?
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
  5. How consistent are the relationships among the data, including topology?
• How can someone get a copy of the data set?
  1. Are there legal restrictions on access or use of the data?
  2. Who distributes the data?
  3. What's the catalog number I need to order this data set?
  4. What legal disclaimers am I supposed to read?
  5. How can I download or order the data?
• Who wrote the metadata?

What does this data set describe?

1. How might this data set be cited?
   Stevens, Andrew W., Wood, Jeffrey M., Ruggiero, Peter R., and Gelfenbaum, Guy R., 20240126, Nearshore bathymetry of the Columbia River littoral cell, Washington and Oregon, 2023: data release DOI:10.5066/P9W15JX8, U.S. Geological Survey, Pacific Coastal and Marine Science Center, Santa Cruz, California.

   Online Links:

   • https://doi.org/10.5066/P9W15JX8
   • https://www.sciencebase.gov/catalog/item/65668187d34e17319deceb6c

   This is part of the following larger work.
   Stevens, Andrew W., Weiner, Heather M., Wood, Jeffrey M., Ruggiero, Peter R., Kaminsky, George M., and Gelfenbaum, Guy R., 2019, Beach topography and nearshore bathymetry of the Columbia River littoral cell, Washington and Oregon (ver. 4.0, January 2024): data release DOI:10.5066/P9W15JX8, U.S. Geological Survey, Santa Cruz, CA.

   Online Links:

   • https://doi.org/10.5066/P9W15JX8

2. What geographic area does the data set cover?

   West_Bounding_Coordinate: -124.2167094
   East_Bounding_Coordinate: -123.9517786
   North_Bounding_Coordinate: 47.1035713
   South_Bounding_Coordinate: 46.1106468
   

3. What does it look like?
4. Does the data set describe conditions during a particular time period?

   Beginning_Date: 25-Aug-2023

   Ending_Date: 29-Aug-2023

   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 (3042532)
   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)

   area

   Designation of sub-area within the Columbia River littoral cell survey area (Source: producer defined)

   Value	Definition
   Clatsop	Clatsop sub-area
   Long Beach	Long Beach sub-area
   Grayland	Grayland sub-area
   North Beach	North Beach sub-area
   Clatsop Spit	Clatsop Spit sub-area
   West Sand Island	West Sand Island sub-area

   line_number

   Numeric code identifying the number of the survey line. Data that were not collected along a survey line are labeled "None". (Source: Producer defined)

   Range of values
   Minimum:	001
   Maximum:	224

   datetime_utc

   The date and time of data collection in Coordinated Universal Time (UTC). (Source: Producer Defined)

   Range of values
   Minimum:	2023-Aug-25 16:30:51.868
   Maximum:	2023-Aug-29 22:19:23.865
   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:	-124.2167094
   Maximum:	-123.9517786
   Units:	Decimal degrees

   latitude

   Latitude coordinate of data point relative to the North American Datum of 1983 (Source: Producer defined)

   Range of values
   Minimum:	46.1106468
   Maximum:	47.1035713
   Units:	Decimal degrees

   easting_m

   East 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:	217898.44
   Maximum:	233276.58
   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:	92312.59
   Maximum:	203307.58
   Units:	meters

   distance_m

   Distance from reference point along planned survey line. NaN=not a number, because the data were not collected along a pre-defined survey line. (Source: Producer defined)

   Range of values
   Minimum:	-3305.72
   Maximum:	197.96
   Units:	meters

   offline_m

   Horizontal distance from planned survey line. Depending on the orientation of the target line and position of the reference point, the offline distance can be positive or negative in any direction. NaN=not a number, because the data were not collected along a pre-defined survey line. (Source: Producer defined)

   Range of values
   Minimum:	-36.71
   Maximum:	39.99
   Units:	meters

   ellipsoid_ht_m

   Height in meters of data point with reference to the reference ellipsoid (Source: Producer defined)

   Range of values
   Minimum:	-40.99
   Maximum:	-22.94
   Units:	meters

   ortho_ht_m

   Height in meters of data point with reference to the North American Vertical Datum of 1988. (Source: Producer defined)

   Range of values
   Minimum:	-16.84
   Maximum:	0.93
   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
   • Jeffrey M. Wood
   • Peter R. Ruggiero
   • Guy R. Gelfenbaum
2. Who also contributed to the data set?
3. To whom should users address questions about the data?
   PCMSC Science Data Coordinator

   U.S. Geological Survey, Pacific Coastal and Marine Science Center

   2885 Mission Street

   Santa Cruz, CA
   

   831-427-4747 (voice)

   pcmsc_data@usgs.gov

Why was the data set created?

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-2023 (process 1 of 3)

   Bathymetry data were collected between August 25 and August 29, 2023, using four single-beam sonar systems and global navigation satellite systems (GNSS) receivers mounted on personal watercraft (PWC). The sonar systems consisted of either an Odom Echotrac CV-100 or CEE Hydrosystems Ceescope single-beam echosounder and 200 kHz transducer with a 9-degree beam angle. Raw acoustic backscatter returns were digitized by the echosounder with a vertical resolution of 1.25 cm. Depths from the echosounders were computed using sound velocity profiles measured using a YSI CastAway CTD during the survey. Positioning of the survey vessels was determined at 5 to 10 Hz using survey-grade GNSS receivers. Output from the GNSS receivers and sonar systems were combined in real time on the PWC by a computer running HYPACK hydrographic survey software. Navigation information was displayed on a video monitor, allowing PWC operators to navigate along survey lines at speeds of 2 to 3 m/s.

   Date: 23-Sep-2023 (process 2 of 3)

   Survey-grade positions of the PWCs were achieved with a single-base station and differential post-processing. Positioning data from the GNSS receivers were post-processed using Waypoint Grafnav to apply differential corrections from a GNSS base station with known horizontal and vertical coordinates relative to the North American Datum of 1983. Orthometric elevations relative to the NAVD88 vertical datum were computed using National Geodetic Survey Geoid12a offsets. Bathymetric data were merged with post-processed positioning data and spurious soundings were removed using a custom Graphical User Interface (GUI) programmed with the computer program MATLAB. The final point data from the PWCs are projected in cartesian coordinates using the Washington State Plane South, meters coordinate system.

   Date: 28-Nov-2023 (process 3 of 3)

   All available bathymetry 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?
   Daniels, Richard C., Ruggiero, Peter, and Weber, Leonard E., 1999, Washington Coastal Geodetic Control Network: Report and Station Index: Washington State Department of Ecology Publication #99-103, Olympia, WA.

   International Hydrographic Organization (IHO), 2008, IHO standards for hydrographic surveys (5th ed.): International Hydrographic Bureau Special Publication 44, 28p., Monaco.

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?
   Survey-grade positions of the personal watercraft (PWCs) were achieved with global navigation satellite system (GNSS) receivers and a single GNSS base station placed on a benchmark with published horizontal coordinates relative to the North American Datum of 1983 (Daniels and others, 1999). The horizontal positions of the geodetic reference network meet first-order specifications established by the National Geodetic Survey with a horizontal accuracy of 2 cm or better. Positioning data from the PWCs were post-processed using Waypoint Grafnav software to apply differential corrections from the GNSS base station. Manufacturer reported accuracy for the differentially corrected horizontal positions for the GNSS rover trajectories is 0.8 cm + 0.5 ppm. Baselines from the GNSS base station varied between 300 m and 12 km with a mean of 3.5 km, suggesting the average horizontal accuracy of survey vessel positions to be about 1 cm. Combining the uncertainty in the benchmark and watercraft yields a total uncertainty of 3 cm. Uncertainty in the horizontal positions associated with pitch and roll of the survey vessels is unknown.
3. How accurate are the heights or depths?
   Uncertainty in the final elevations is derived from the combination of uncertainty in the GNSS positioning and bathymetric sounding measurements. The vertical positions of the geodetic reference network meet 2 cm local ellipsoid height specifications established by the National Geodetic Survey (Daniels and others, 1999). Manufacturer reported accuracy for the differentially corrected vertical positions for the GNSS rover trajectories is 1.5 cm + 1 ppm relative to the benchmark elevation. Baselines from the GNSS base station varied between 300 m and 12 km with a mean of 3.2 km, suggesting the average vertical accuracy of survey vessel positions to be about 1.8 cm. The manufacturer of the single-beam echosounder used in this study reports a vertical accuracy of 1 cm. Additional uncertainty in the final computed elevations data is related to unmeasured variability in the speed of sound used to compute depths from bathymetric soundings and, thus, is depth-dependent. Based on analysis of available speed of sound measurements, we estimate uncertainties in the final depth soundings to be no greater than 1 percent of the water depth. The total vertical uncertainty is calculated using the constant- and depth-dependent factors summed in quadrature (International Hydrographic Organization, 2008). The vertical uncertainty in final elevations varied between 3 cm and 19 cm with a mean vertical uncertainty of 10 cm. Uncertainty in the vertical positions associated with pitch and roll of the survey vessels 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?

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 (crlc23_bathy.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?
   • Availability in digital form:

     Data format:	comma-delimited text file in format comma-delimited text (version Matlab 9.8.0.1396136) text Size: 324.65
     Network links:	https://www.sciencebase.gov/catalog/file/get/65668187d34e17319deceb6c?name=crlc23_bathy.csv https://www.sciencebase.gov/catalog/item/65668187d34e17319deceb6c https://www.sciencebase.gov/catalog/item/6566803ad34e17319deceb64 https://doi.org/10.5066/P9W15JX8

   • Cost to order the data: None

Who wrote the metadata?

Dates:

Last modified: 26-Jan-2024

Metadata author:

PCMSC Science Data Coordinator

U.S. Geological Survey, Pacific Coastal and Marine Science Center

2885 Mission St.

Santa Cruz, CA

831-427-4747 (voice)

pcmsc_data@usgs.gov

Metadata standard:

Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)