Multibeam echo sounder - navigation tracklines for Reson 7160 data collected during USGS field activities 2017-001-FA and 2017-002-FA.

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

Frequently anticipated questions:

What does this data set describe?

Title:
Multibeam echo sounder - navigation tracklines for Reson 7160 data collected during USGS field activities 2017-001-FA and 2017-002-FA.
Abstract:
In spring and summer 2017, the U.S. Geological Survey’s Gas Hydrates Project conducted two cruises aboard the research vessel Hugh R. Sharp to explore the geology, chemistry, ecology, physics, and oceanography of sea-floor methane seeps and water column gas plumes on the northern U.S. Atlantic margin between the Baltimore and Keller Canyons. Split-beam and multibeam echo sounders and a chirp subbottom profiler were deployed during the cruises to map water column backscatter, sea-floor bathymetry and backscatter, and subsurface stratigraphy associated with known and undiscovered sea-floor methane seeps. The first cruise, known as the Interagency Mission for Methane Research on Seafloor Seeps and designated as field activity 2017-001-FA, was conducted from May 4 to May 11, 2017, and acquired geophysical data to support remotely operated vehicle exploration of seep sites using the Global Explorer, which is operated by Oceaneering International, Inc. Geophysical operations during cruise 2017-002-FA from August 25 to September 6, 2017, were also focused on mapping water column methane plumes, sea-floor seep sites, and subseafloor strata, but primarily supported conductivity, temperature, and depth instrument deployment, surface-water methane-concentration mapping, and water-sampling operations as part of a collaborative study with the University of Rochester of the effect of methane seepage on ocean water biogeochemistry. The National Oceanic and Atmospheric Administration’s Office of Ocean Exploration and Research partially sponsored cruise 2017-001-FA, and the U.S. Department of Energy partially sponsored both cruises.
Supplemental_Information:
Support for 2017-001-FA was provided to the USGS by NOAA and DOE through interagency agreements 16-01118 and DE-FE0023495, respectively. Support for 2017-002-FA was provided to the USGS and the University of Rochester by DOE through interagency agreement DE-FE0026195 and grant DE-FE0028980, respectively. Additional information on the field activity is available from https://cmgds.marine.usgs.gov/fan_info.php?fan=2017-001-FA and https://cmgds.marine.usgs.gov/fan_info.php?fan=2017-002-FA. Additional information specific to the Interagency Mission for Methane Research on Seafloor Seeps is available at https://www.usgs.gov/centers/whcmsc/science/immerss-interagency-mission-methane-research-seafloor-seeps?qt-science_center_objects=0#qt-science_center_objects and https://archive.usgs.gov/archive/sites/soundwaves.usgs.gov/2017/05/outreach.html.
  1. How might this data set be cited?
    U.S. Geological Survey, 20200409, Multibeam echo sounder - navigation tracklines for Reson 7160 data collected during USGS field activities 2017-001-FA and 2017-002-FA.: data release DOI:10.5066/P9Y1MSTN, U.S. Geological Survey, Coastal and Marine Geology Program, Woods Hole Coastal and Marine Science Center, Woods Hole, Massachusetts.

    Online Links:

    This is part of the following larger work.

    Baldwin, Wayne E., Moore, Eric M., Worley, Charles R., Nichols, Alex R., and Ruppel, Carolyn D., 2020, Marine Geophysical Data Collected to Support Methane Seep Research Along the U.S. Atlantic Continental Shelf Break and Upper Continental Slope Between the Baltimore and Keller Canyons During U.S. Geological Survey Field Activities 2017-001-FA and 2017-002-FA.: data release DOI:10.5066/P9Y1MSTN, U.S. Geological Survey, Reston, VA.

    Online Links:

    Other_Citation_Details:
    Suggested citation: Baldwin, W.E., Moore, E.M., Worley, C.R., Nichols, A.R., and Ruppel, C.D., 2020, Marine Geophysical Data Collected to Support Methane Seep Research Along the U.S. Atlantic Continental Shelf Break and Upper Continental Slope Between the Baltimore and Keller Canyons During U.S. Geological Survey Field Activities 2017-001-FA and 2017-002-FA: U.S. Geological Survey data release, https://doi.org/10.5066/P9Y1MSTN.
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -74.860827
    East_Bounding_Coordinate: -74.022091
    North_Bounding_Coordinate: 37.848654
    South_Bounding_Coordinate: 35.510819
  3. What does it look like?
    https://www.sciencebase.gov/catalog/file/get/5e1e3815e4b0ecf25c610e23/?name=2017-001-FA_2017-002-FA_7160Tracklines_browse.jpg (JPG)
    Multibeam echo sounder tracklines around Keller Canyon.
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 09-May-2017
    Ending_Date: 06-Sep-2017
    Currentness_Reference:
    ground condition
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: vector digital data
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
      This is a Vector data set. It contains the following vector data types (SDTS terminology):
      • string (1108)
    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.000001. Longitudes are given to the nearest 0.000001. Latitude and longitude values are specified in Decimal degrees. The horizontal datum used is D_WGS_1984.
      The ellipsoid used is WGS_1984.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257224.
  7. How does the data set describe geographic features?
    2017-001-FA_2017-002-FA_7160Tracklines
    Reson 7160 multibeam echo sounder tracklines for USGS field activities 2017-001-FA and 2017-002-FA along the U.S. Atlantic continental shelf break and upper slope between Accomac and Keller Canyons. (Source: U.S. Geological Survey)
    FID
    Internal feature number. (Source: Esri) Sequential unique whole numbers that are automatically generated.
    Shape
    Feature geometry. (Source: Esri) Coordinates defining the features.
    LineName
    Reson SeaBat User Interface s7k or HYPACK HYSWEEP HSX/7K pair filename for the 7160 MBES trackline. See logical consistency report for naming format description. (Source: U.S. Geological Survey) Character set
    YJD_init
    Year and Julian date at the start of the survey line in the format: YYYY-JD; where Julian day is the integer number (although recorded here in text string format) representing the interval of time in days since January 1 of the year of collection. (Source: U.S. Geological Survey) Character set
    JDUTC_init
    Julian day and UTC time at the start of the survey line in the format: JD:HH:MM:SS; Julian day is the integer number (although recorded here in text string format) representing the interval of time in days since January 1 of the year of collection. (Source: U.S. Geological Survey) Character set
    YJD_end
    Year and Julian date (YYYY-JD) at the end of the survey line. (Source: U.S. Geological Survey) Character set
    JDUTC_end
    Julian day and UTC time (JD:HH:MM:SS) at the end of the survey line. (Source: U.S. Geological Survey) Character set
    SurveyID
    WHCMSC field activity identifier (e.g. "2017-001-FA" where 2017 is the survey year, 001 is survey number of that year, and FA is Field Activity). (Source: U.S. Geological Survey) Character set
    VehicleID
    Survey vessel name. (Source: U.S. Geological Survey) Character set
    DeviceID
    Sonar device used to collect MBES data. (Source: U.S. Geological Survey) Character set
    Length_km
    Length of swath data line in kilometers (UTM Zone 18N, WGS 84) calculated in the SQLite database. (Source: U.S. Geological Survey)
    Range of values
    Minimum:0.008
    Maximum:16.971
    Units:kilometers
    Resolution:0.001

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • U.S. Geological Survey
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
    U.S. Geological Survey
    Attn: Wayne E. Baldwin
    Geologist
    384 Woods Hole Road
    Woods Hole, Massachusetts
    US

    508-548-8700 x2226 (voice)
    508-457-2310 (FAX)
    wbaldwin@usgs.gov

Why was the data set created?

This dataset contains trackline navigation for approximately 412 km of Reson 7160 multibeam echo sounder bathymetry and backscatter data collected by the U.S. Geological Survey during USGS field activities 2017-001-FA and 2017-002-FA along the U.S. Atlantic continental shelf break and upper slope between Accomac and Keller Canyons. This information can help spatially correlate the bathymetry and backscatter data with other geophysical and sample data.

How was the data set created?

  1. From what previous works were the data drawn?
    Reson 7160 multibeam echo sounder data (source 1 of 1)
    U.S. Geological Survey, Unpublished Material, raw multibeam echo sounder data.

    Type_of_Source_Media: disc
    Source_Contribution:
    Multibeam echo sounder seafloor bathymetry and backscatter and water column backscatter data were collected using a Reson 7160 (44 kHz center frequency, 512 beams, 1.5 x 2 degree across- and along-track beam widths, respectively). The Mills Cross transmit and receive transducer arrays were pole-mounted on the port side of the R/V Hugh R Sharp just aft of the Bosun's locker with the transducers positioned approximately 2.8 m below the waterline when deployed. Vessel navigation and attitude data were acquired with an Applanix POS MV Wavemaster (model 220, v5) configured with two Trimble GPS antennas located at either end of a 2-m baseline oriented fore and aft and mounted atop the MBES pole, and the wet pod IMU mounted atop the sonar bracket just aft of the pole. An AML Micro X SV mounted on the sonar bracket monitored sound speed in water near the sonar during acquisition, and water column sound speed profiles were collected using Sippican T4 and T5 Expendable Bathythermograph probes and Seabird Electronics 911plus CTD casts at various points during both cruises (see shapefile '2017-001-FA_2017-002-FA_SVPdata.shp' available from the larger work citation). The Reson SeaBat User Interface (version 4.0.0.10) was used to control the sonar, which was operated primarily in FM mode at various power levels throughout the cruises. The range of the 512 across-track beams formed by the sonars were adjusted manually depending on water depth. Data were monitored and recorded using the Reson SeaBat User Interface (version 4.0.0.10) and HYPACK HYSWEEP (version 2017, 17.1.3.0). The SeaBat User Interface logged navigation, attitude, bathymetry, time-series backscatter, and water column data to s7k format files. HYPACK HYSWEEP logged navigation, attitude, and bathymetry data to HSX format files, and navigation, attitude, and time series backscatter data to 7K format files. Patch test calibrations were performed during each field activity to determine possible misalignments between the MBES and POS MV reference frames or systematic timing latencies.
  2. How were the data generated, processed, and modified?
    Date: 2017 (process 1 of 4)
    Shipboard multibeam processing within Computer Aided Resource Information System (Caris) Hydrographic Information Processing System (HIPS; version 9) consisted of the following flow:
    1) Caris HIPS projects were created to process 7160 data. Projection information was set to Universal Transverse Mercator (UTM) Zone 18N, WGS 84.
    2) Vessel configuration files were created in the Caris projects for the R/V Hugh R. Sharp, which included relevant linear and angular installation offsets for the 7160 installation as well as vendor specified uncertainty values for each of the survey sensors.
    3) Raw files were imported to the Caris projects using the Import/Conversion Wizard.
    4) Delayed heave and navigation data (navigation only loaded for HSX data used from JD238 of 2017-002-FA) from raw POS MV files were used to update HIPS survey lines using the import auxiliary data function.
    5) Navigation was reviewed and edited as needed using the Navigation Editor tool.
    This process step and all subsequent process steps were conducted by Eric Moore and Wayne Baldwin, though Baldwin is listed as the contact. Person who carried out this activity:
    U.S. Geological Survey
    Attn: Wayne Baldwin
    Geologist
    384 Woods Hole Rd.
    Woods Hole, MA

    508-548-8700 x2226 (voice)
    508-457-2310 (FAX)
    wbaldwin@usgs.gov
    Date: Jun-2018 (process 2 of 4)
    Extract and reformat the navigation fixes stored in the Caris HIPS database and add them to a geospatial SQLite (version 3.21.0) database:
    1) Navigation for each line in Caris HDCS directory was extracted using the Caris program printfNav. (Extracted navigation file is tab-delimited in format YYYY-JD HH:MM:SS:FFF DD.LAT DD.LONG SSSSS_VVVVV_YYYY-JD_LLLL AR where YYYY=year, JD=Julian Day, HH=hour, MM=minute, SS=seconds, FFF=fractions of a second, DD.LAT=latitude in decimal degrees, DD.LONG=longitude in decimal degrees, SSSSS=survey name, VVVVV=vessel name, LLLL=linename, AR=accepted or rejected navigation fix). This step creates the directory of TXT navigation files for each survey line in the Caris project.
    2) A Python script (pySQLBathNav) parsed each printfNav output file, to remove rejected navigation records, and add accepted records as point geometries to a geospatial SQLite database (which was created if it did not already exist). Additional fields for survey ID, vessel name, and system name were added during parsing. Polyline geometries were created from the point geometries for each survey line, using UTC time as the sort order field, and fields for JD
    Date: Nov-2019 (process 3 of 4)
    Create Esri shapefile containing the polyline data:
    The polyline features for each field activity were added (Add Data) into ArcMap (version 10.7.1) from the SQLite database, then exported (Right click on database feature class > Data > Export Data) to the new Esri polyline shapefiles 2017-001-FA_7160Tracklines.shp and 2017-002-FA_7160Tracklines.shp. The ArcGIS process 'Merge' was used to combine both trackline datasets into the single shapefile 2017-001-FA_2017-002-FA_7160Tracklines.shp
    Date: 06-Aug-2020 (process 4 of 4)
    Added keywords section with USGS persistent identifier as theme keyword. 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
  3. What similar or related data should the user be aware of?
    Demopoulos, A., McClain-Counts, J., Bourque, J., Prouty, N., Smith, B., Brooke, S., Ross, S., and Ruppel, C., 2019, Examination of Bathymodiolus childressi nutritional sources, isotopic niches, and food-web linkages at two seeps in the US Atlantic margin using stable isotope analysis and mixing models.: Deep Sea Research Part I 148, pp.53-66, Elsevier, Amsterdam, Netherlands.

    Online Links:

    Leonte, M., Ruppel, C. D., Ruiz‐Angulo, A., and Kessler, J. D., 2020, Surface methane concentrations along the Mid‐Atlantic Bight driven by aerobic subsurface production rather than seafloor gas seeps.: Journal of Geophysical Research: Oceans vol. 125, American Geophysical Union Publications, Washington, DC.

    Online Links:

    Ruppel, C., Demopoulos, A., and Prouty, N., 2018, Exploring US Mid-Atlantic Margin Methane Seeps: IMMeRSS, May 2017.: Supplement to Oceanography 31(1), p.93, The Oceanography Society, Rockville, MD.

    Online Links:

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?
    Navigation data were acquired using the WGS 84 coordinate system with an Applanix POS MV Wavemaster (model 220, v5), which blends Global Navigation Satellite System (GNSS) and acceleration data from an Inertial Motion Unit (IMU) and GPS azimuthal heading. The POS MV was configured with two Trimble GPS antennas located at either end of a 2-m baseline, which was oriented fore and aft and mounted atop the MBES pole just aft of the bosun's locker on the port side of vessel. GPS positions were obtained from the primary antenna located on the forward end of the baseline, and the positional offsets between the antenna and the navigational reference point (the POS MV IMU) were accounted for in the Applanix POSView (version 8.60) acquisition software. Positions from the POS MV are assumed to be horizontally accurate to 3 meters.
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
    This shapefile includes trackline navigation for all multibeam echo sounder data collected during field activities 2017-001-FA and 2017-002-FA, except for those collected during troubleshooting of MBES system navigation and telemetry problems conducted on May 4 (JD124) 13:10 - 13:25 UTC, May 7 (JD127) 05:21 - 05:39, and May 8 (JD128) 03:37 - 08:57. While the line navigation for all the data are included in this shapefile, the final bathymetry grids or backscatter mosaics may not include all data from all lines.
  5. How consistent are the relationships among the observations, including topology?
    Multibeam echo sounder (MBES) data were primarily collected overnight (between approximately 24:00 and 10:00 UTC) during field activities 2017-001-FA and 2017-002-FA. Raw MBES data were recorded in both the Reson SeaBat User Interface (s7k format) and HYPACK HYSWEEP (HSX and 7K pair file formats) acquisition software. Reson s7k files contain seafloor bathymetry and backscatter and uncompressed water column backscatter data, while HYPACK HYSWEEP HSX and 7K paired files contain seafloor bathymetry and backscatter, respectively. The additional volume of water column data saved to the s7k raw files resulted in a greater number than the HSX/7K pair files; one HSX/7K pair encompasses the same coverage as one or more s7k files. Reson s7k files were primarily used for bathymetry and backscatter processing, but problems with navigation and telemetry during acquisition made the use of several HSX files necessary because the problems did not affect HYPACK HYSWEEP acquisition. The column "LineName" in the attribute table of '2017-001-FA_2017-002-FA_7160Tracklines.shp' indicates the file type used for processing; Reson s7k filenames have the Reson SeaBat User Interface default format 'YYYYMMDD_HHMMSS' indicating UTC start date and time; HYPACK HYSWEEP filenames have the format 'YYYYMMDD_HHMMSS_LLL_HHMM', which prepends the Reson filename (for the first equivalent file encompassed by the corresponding HYPACK HYSWEEP file) to the HYPACK HYSWEEP filename, which indicates the three digit planned line number and the UTC time. Navigation for each of the file formats is identical (though files may differ in start or end times by several seconds) and polylines included in '2017-001-FA_2017-002-FA_7160Tracklines.shp' are indicative of all data used for processing.

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:
Public domain data from the U.S. Government are freely distributable with proper metadata and source attribution. Please recognize the U.S. Geological Survey as the originator of the data set.
  1. Who distributes the data set? (Distributor 1 of 1)
    U.S. Geological Survey - ScienceBase
    Federal Center
    Denver, CO

    1-888-275-8747 (voice)
  2. What's the catalog number I need to order this data set? USGS data release of Reson 7160 MBES trackline data collected along the U.S. Atlantic continental shelf break and upper slope between Accomac and Keller Canyons during USGS field activities 2017-001-FA and 2017-002-FA: includes '2017-001-FA_2017-002-FA_7160Tracklines.shp' containing the trackline features, the browse graphic '2017-001-FA_2017-002-FA_7160Tracklines_browse.jpg', and the Federal Geographic Data Committee (FGDC) Content Standards for Digital Geospatial Metadata (CSDGM) metadata file '2017-001-FA_2017-002-FA_7160Tracklines_meta.xml'.
  3. What legal disclaimers am I supposed to read?
    Neither the U.S. Government, the Department of the Interior, nor the USGS, nor any of their employees, contractors, or subcontractors, make any warranty, express or implied, nor assume any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or process disclosed, nor represent that its use would not infringe on privately owned rights. The act of distribution shall not constitute any such warranty, and no responsibility is assumed by the USGS in the use of these data or related materials. Any use of trade, product, or firm names is for descriptive purposes only and does not imply endorsement by the U.S. Government.
  4. How can I download or order the data?
  5. What hardware or software do I need in order to use the data set?
    To utilize these data, the user must have software capable of reading shapefile format.

Who wrote the metadata?

Dates:
Last modified: 06-Aug-2020
Metadata author:
U.S. Geological Survey
Attn: Wayne E. Baldwin
Geologist
384 Woods Hole Rd.
Woods Hole, MA

(508) 548-8700 x2226 (voice)
(508) 457-2310 (FAX)
wbaldwin@usgs.gov
Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)
This page is <https://cmgds.marine.usgs.gov/catalog/whcmsc/SB_data_release/DR_P9Y1MSTN/2017-001-FA_2017-002-FA_7160Tracklines_meta.faq.html>
Generated by mp version 2.9.50 on Tue Sep 21 18:20:12 2021