Single-beam bathymetric data near Kipnuk, Alaska, collected June 21, 2022

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

Frequently anticipated questions:


What does this data set describe?

Title:
Single-beam bathymetric data near Kipnuk, Alaska, collected June 21, 2022
Abstract:
Single-beam bathymetric data near Kipnuk, Alaska, collected June 21, 2022, Raw Data File 2023-9, provides bathymetric data collected near Kipnuk, Alaska on June 21, 2022. The purpose of this survey is to provide bath-ymetric data for the assessment of coastal hazards and riverine erosion studies. These data were collected using an M2Ocean Hydroball integrated bathymetric sensor and processed using CIDCO DepthStar software. DGGS collected coincident Global Navigation Satellite System (GNSS) base station and water level time series data using Trimble survey equipment and a Stilltek iGage radar sensor, respectively, to correct horizontal and vertical positions. This data product does not meet the International Hydrographic Organization (IHO) bath-ymetric coverage standard (IHO, 2022), is not intended for use in determining navigability, and is released as a Raw Data File with an open end-user license. The data are available from the DGGS website: http://doi.org/10.14509/31007.
Supplemental_Information:
bathymetry:    Bathymetric sounding data delivered in comma delimited (CSV) format with column headers and accompanied by a data dictionary detailing the header names, definitions, and applicable units.
  1. How might this data set be cited?
    Horen, K.C., Buzard, R.M., Overbeck, J.R., Poisson, A.C., and Siemsen, Z.J., 2023, Single-beam bathymetric data near Kipnuk, Alaska, collected June 21, 2022: Raw Data File RDF 2023-9, Alaska Division of Geological & Geophysical Surveys, Fairbanks, Alaska, United States.

    Online Links:

    Other_Citation_Details: 7 p.
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -164.092687
    East_Bounding_Coordinate: -164.039382
    North_Bounding_Coordinate: 59.966572
    South_Bounding_Coordinate: 59.936228
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: 19-Jun-2022
    Currentness_Reference:
    ground condition
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: csv
  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?
      Grid_Coordinate_System_Name: Universal Transverse Mercator
      Universal_Transverse_Mercator:
      UTM_Zone_Number: 3
      Transverse_Mercator:
      Scale_Factor_at_Central_Meridian: 0.999600
      Longitude_of_Central_Meridian: -165
      Latitude_of_Projection_Origin: 0
      False_Easting: 500000.000000
      False_Northing: 0
      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest .00000001
      Ordinates (y-coordinates) are specified to the nearest .00000001
      Planar coordinates are specified in Meters
      The horizontal datum used is NAD83 (2011).
      The ellipsoid used is GRS 80.
      The semi-major axis of the ellipsoid used is 6378137.
      The flattening of the ellipsoid used is 1/298.257222101.
      Vertical_Coordinate_System_Definition:
      Depth_System_Definition:
      Depth_Datum_Name: NAVD88, GEOID12B
      Depth_Resolution: 0.002
      Depth_Distance_Units: meters
      Depth_Encoding_Method: Attribute values
  7. How does the data set describe geographic features?
    rdf2023-11-bathymetric-data.csv, rdf2023-11-bathymetric-data-dictionary.csv
    Bathymetric sounding data delivered in comma delimited (CSV) format with column headers and accompanied by a data dictionary detailing the header names, definitions, and applicable units. (Source: DGGS)

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
  2. Who also contributed to the data set?
    We thank the Native Village and City of Kipnuk for supporting the creation of these data products, made possible with the National Fish and Wildlife Foundation's National Coastal Resilience Funding through our partners at the Alaska Native Tribal Health Consortium. The views and conclusions contained in this document are those of the authors and should not be interpreted as representing the opinions or policies of the Alaska Division of Geological & Geophysical Surveys, the U.S. Government, the National Fish and Wild-life Foundation, or the National Fish and Wildlife Foundation's funding sources. Mention of trade names or commercial products does not constitute endorsement by the Alaska Division of Geological & Geophysical Surveys, the U.S. Government, the National Fish and Wildlife Foundation, or the National Fish and Wildlife Foundation's funding sources.
  3. To whom should users address questions about the data?
    Alaska Division of Geological & Geophysical Surveys
    Metadata Manager
    3354 College Road
    Fairbanks, AK
    USA

    (907)451-5020 (voice)
    (907)451-5050 (FAX)
    dggspubs@alaska.gov
    Hours_of_Service: 8 am to 4:30 pm, Monday through Friday, except State holidays
    Contact_Instructions:
    Please view our website (https://www.dggs.alaska.gov) for the latest information on available data. Please contact us using the e-mail address provided above when possible.

Why was the data set created?

This work provides bathymetric data for the assessment of coastal hazards and riverine erosion studies.

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: 17-Aug-2022 (process 1 of 3)
    Field collection - DGGS used an M2Ocean Hydroball bathymetric sensor, composed of an Imagenex 852 single-beam echosounder (SBES), a Tallysman TW3972 GNSS antenna, and a Honeywell HMR3000 inclinometer to col-lect field data. On August 17, 2022, DGGS temporarily installed a Trimble R10 receiver sampling at 5 Hz as a GNSS base station over known benchmark 946 6084 D with a published solution available from https://www.ngs.noaa.gov/OPUS/getDatasheet.jsp?PID=BBHK19&ts=21202103238. Base station data were used to correct the HydroBall sensor positions. To provide water level corrections, DGGS collected derived water level time series data from a temporarily installed Solinst model 3001 Levelogger Edge LT M10/F30 pressure and temperature sensor fully submerged approximately 20 m offshore, and at the Kipnuk Airport Automated Surface/Weather Observing System (ASOS/AWOS) station PAKI located approximately 28 km to the southeast.
    Date: 17-Aug-2022 (process 2 of 3)
    Survey setails - The bathymetric survey was performed on August 17 from 3:30 PM to 6:30 PM AKDT. The weather throughout the survey was mostly cloudy, with light wind and wave heights under 0.3 m. The Hydroball was attached to a catamaran configuration and towed behind a small boat equipped with an outboard motor at speeds below 4 knots. The Imagenex 852 SBES was configured with a maximum range of 20 m, gain of 5 dB, and pulse length of 120 microseconds. Due to time and vessel constraints, the bathymetric survey was per-formed using a survey pattern inconsistent with the requirements outlined in the IHO standards (IHO, 2022). Approximately 10.0 km of riverine bathymetry were surveyed.
    Date: 2022 (process 3 of 3)
    Data processing - Data were processed using methods described in the accompanying report.
  3. What similar or related data should the user be aware of?
    Buzard, R.M., Overbeck, J.R., Chriest, Jonathan, Endres, K.L., and Plumb, E.W., 2021, Coastal flood impact assessments for Alaska communities: Report of Investigation RI 2021-1, Alaska Division of Geological & Geophysical Surveys, Fairbanks, Alaska, United States.

    Online Links:

    Other_Citation_Details: 16 p
    Buzard, R.M., Turner, M.M., Miller, K.Y., Antrobus, D.C., and Overbeck, J.R., 2021, Erosion exposure assessment of infrastructure in Alaska coastal communities: Report of Investigation RI 2021-3, Alaska Division of Geological & Geophysical Surveys, Fairbanks, Alaska, United States.

    Online Links:

    Other_Citation_Details: 29 p
    Overbeck, J.R., Buzard, R.M., Turner, M.M., Miller, K.Y., and Glenn, R.J., 2020, Shoreline change at Alaska coastal communities: Report of Investigation RI 2020-10, Alaska Division of Geological & Geophysical Surveys, Fairbanks, Alaska, United States.

    Online Links:

    Other_Citation_Details: 29 p., 47 sheets

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

  1. How well have the observations been checked?
    The use of the IHO minimum bathymetric standards (IHO, 2022) would be inappropriate for assessment of these data, which do not meet the IHO prescribed systematic survey pattern criteria. To avoid misinterpretation, DGGS has developed order of accuracy criteria for the qualification of bathymetric survey data separate from but based on the IHO standards. The reported accuracy of these data is intended to express quality only and should not be considered sufficient for safe navigation. We describe methods in the accompanying report
  2. How accurate are the geographic locations?
    We quantified the horizontal accuracy using methods described in the accompanying report.
  3. How accurate are the heights or depths?
    We quantified the vertical accuracy using methods described in the accompanying report.
  4. Where are the gaps in the data? What is missing?
    This data releaase is complete. DGGS filtered out low-quality, non-differential (single) GNSS position data using standard categorization (single, float, fixed). All 0.0 m depth soundings, excessive noise, and vertical anomalies were removed through visual inspection. DGGS used time series data for both depth and attitude (pitch and yaw) to manually re-move anomalous soundings and any sounding reporting an attitude deviation larger than twenty degrees. No significant erroneous areas requiring repair were identified during this quality control process. Base station data were processed using the OPUS static processing service, which derives GNSS coordi-nates from the average of three independent, single-baseline solutions, each computed by double-differenced carrier-phase measurements from three nearby National Continuously Operating Reference Stations (CORS). OPUS provides the range of the three individual single baselines, known as the peak-to-peak error. These ranges include any errors from the CORS used during processing. OPUS ortho height ranges are estimated using the same calculations applied to horizontal error report-ing, typically resulting in a much larger potential error compared to the peak-to-peak error of the ellipsoid height. For more accurate ortho height error reporting, DGGS used NOAA's Vertical Datum Transformation software for final elevation conversions from NAD83 (2011) ellipsoidal heights to NAVD88 (GEOID12B) ortho heights. This software employs accurate, multi-parameter mathematical equations and location-specific grid models to perform vertical transformations and report the total root-mean-square error.
  5. How consistent are the relationships among the observations, including topology?
    DGGS filtered out low-quality, non-differential (single) GNSS position data using standard categorization (single, float, fixed). All 0.0 m depth soundings, excessive noise, and vertical anomalies were removed through visual inspection. DGGS used time series data for both depth and attitude (pitch and yaw) to manually re-move anomalous soundings and any sounding reporting an attitude deviation larger than twenty degrees. No significant erroneous areas requiring repair were identified during this quality control process. Base station data were processed using the OPUS static processing service, which derives GNSS coordi-nates from the average of three independent, single-baseline solutions, each computed by double-differenced carrier-phase measurements from three nearby National Continuously Operating Reference Stations (CORS). OPUS provides the range of the three individual single baselines, known as the peak-to-peak error. These ranges include any errors from the CORS used during processing. OPUS ortho height ranges are estimated using the same calculations applied to horizontal error report-ing, typically resulting in a much larger potential error compared to the peak-to-peak error of the ellipsoid height. For more accurate ortho height error reporting, DGGS used NOAA's Vertical Datum Transformation software for final elevation conversions from NAD83 (2011) ellipsoidal heights to NAVD88 (GEOID12B) ortho heights. This software employs accurate, multi-parameter mathematical equations and location-specific grid models to perform vertical transformations and report the total root-mean-square error.

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?
Access_Constraints:
This report, map, and/or dataset is available directly from the State of Alaska, Department of Natural Resources, Division of Geological & Geophysical Surveys (see contact information below).
Use_Constraints:
Any hard copies or published datasets utilizing these datasets shall clearly indicate their source. If the user has modified the data in any way, the user is obligated to describe the types of modifications the user has made. The user specifically agrees not to misrepresent these datasets, nor to imply that changes made by the user were approved by the State of Alaska, Department of Natural Resources, Division of Geological & Geophysical Surveys. The State of Alaska makes no express or implied warranties (including warranties for merchantability and fitness) with respect to the character, functions, or capabilities of the electronic data or products or their appropriateness for any user's purposes. In no event will the State of Alaska be liable for any incidental, indirect, special, consequential, or other damages suffered by the user or any other person or entity whether from the use of the electronic services or products or any failure thereof or otherwise. In no event will the State of Alaska's liability to the Requestor or anyone else exceed the fee paid for the electronic service or product.
  1. Who distributes the data set? (Distributor 1 of 1)
    Alaska Division of Geological & Geophysical Surveys
    Metadata Manager
    3354 College Road
    Fairbanks, AK
    USA

    (907)451-5020 (voice)
    (907)451-5050 (FAX)
    dggspubs@alaska.gov
    Hours_of_Service: 8 am to 4:30 pm, Monday through Friday, except State holidays
    Contact_Instructions:
    Please view our website (https://www.dggs.alaska.gov) for the latest information on available data. Please contact us using the e-mail address provided above when possible.
  2. What's the catalog number I need to order this data set? RDF 2023-9
  3. What legal disclaimers am I supposed to read?
    The State of Alaska makes no expressed or implied warranties (including warranties for merchantability and fitness) with respect to the character, functions, or capabilities of the electronic data or products or their appropriateness for any user's purposes. In no event will the State of Alaska be liable for any incidental, indirect, special, consequential, or other damages suffered by the user or any other person or entity whether from the use of the electronic services or products or any failure thereof or otherwise. In no event will the State of Alaska's liability to the Requestor or anyone else exceed the fee paid for the electronic service or product.
  4. How can I download or order the data?

Who wrote the metadata?

Dates:
Last modified: 14-Aug-2023
Metadata author:
Alaska Division of Geological & Geophysical Surveys
Attn: Simone Montayne
Metadata Manager
3354 College Road
Fairbanks, AK
USA

(907)451-5020 (voice)
(907)451-5050 (FAX)
dggspubs@alaska.gov
Hours_of_Service: 8 am to 4:30 pm, Monday through Friday, except State holidays
Metadata standard:
FGDC Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)
Metadata extensions used:

Generated by mp version 2.9.50 on Mon Aug 14 14:37:52 2023