Multibeam sonar tracklines collected in Cape Cod Bay, Massachusetts with a Reson T-20P during USGS Field Activity 2019-002-FA (Esri polyline shapefile, GCS WGS 84)

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

Frequently anticipated questions:

What does this data set describe?

Title:
Multibeam sonar tracklines collected in Cape Cod Bay, Massachusetts with a Reson T-20P during USGS Field Activity 2019-002-FA (Esri polyline shapefile, GCS WGS 84)
Abstract:
Accurate data and maps of sea floor geology are important first steps toward protecting fish habitat, delineating marine resources, and assessing environmental changes due to natural or human impacts. To address these concerns the U.S. Geological Survey, in cooperation with the Massachusetts Office of Coastal Zone Management (CZM), comprehensively mapped the Cape Cod Bay sea floor to characterize the surface and shallow subsurface geologic framework. Geophysical data collected include swath bathymetry, backscatter, and seismic reflection profile data. Ground-truth data, including sediment samples, underwater video, and bottom photographs were also collected. This effort is part of a long-term collaboration between the USGS and the Commonwealth of Massachusetts to map the State’s waters, support research on the Quaternary evolution of coastal Massachusetts, the influence of sea-level change and sediment supply on coastal evolution, and efforts to understand the type, distribution, and quality of subtidal marine habitats. This collaboration produces high-resolution geologic maps and Geographic Information System (GIS) data that serve the needs of research, management and the public. Data collected as part of this mapping cooperative continue to be released in a series of USGS Open-File Reports and Data Releases (https://www.usgs.gov/centers/whcmsc/science/geologic-mapping-massachusetts-seafloor). This data release provides the geophysical and geologic sampling data collected in Cape Cod Bay during USGS Field Activities 2019-002-FA and 2019-034-FA in 2019.
Supplemental_Information:
Support for 2019-002-FA was provided to the USGS from the Massachusetts Office of Coastal Zone Management. Additional information on the field activities associated with this project are available at https://cmgds.marine.usgs.gov/fan_info.php?fan=2019-002-FA and https://cmgds.marine.usgs.gov/fan_info.php?fan=2019-034-FA.
  1. How might this data set be cited?
    Ackerman, Seth D., 20220718, Multibeam sonar tracklines collected in Cape Cod Bay, Massachusetts with a Reson T-20P during USGS Field Activity 2019-002-FA (Esri polyline shapefile, GCS WGS 84): data release DOI:10.5066/P99DR4PN, U.S. Geological Survey, Coastal and Marine Hazards and Resources Program, Woods Hole Coastal and Marine Science Center, Woods Hole, Massachusetts.

    Online Links:

    This is part of the following larger work.

    Ackerman, Seth D., Foster, David S., Andrews, Brian D., Danforth, William W., Baldwin, Wayne E., Huntley, Emily C., Worley, Charles R., and Brothers, Laura L., 2022, High-resolution geophysical and geological data collected in Cape Cod Bay, Massachusetts during USGS Field Activities 2019-002-FA and 2019-034-FA: data release DOI:10.5066/P99DR4PN, U.S. Geological Survey, Reston, VA.

    Online Links:

    Other_Citation_Details:
    Suggested citation: Ackerman, S.D., Foster, D.S., Andrews, B.D., Danforth, W.W., Baldwin, W.E., Huntley, E.C., Worley, C.R., and Brothers, L.L., 2022, High-resolution geophysical and geological data collected in Cape Cod Bay, Massachusetts during USGS Field Activities 2019-002-FA and 2019-034-FA: U.S. Geological Survey data release, https://doi.org/10.5066/P99DR4PN.
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -70.51046787
    East_Bounding_Coordinate: -70.10421171
    North_Bounding_Coordinate: 42.03046465
    South_Bounding_Coordinate: 41.74782158
  3. What does it look like?
    https://cmgds.marine.usgs.gov/data-releases/media/2021/10.5066-P99DR4PN/11617ca507e24b7a98dd27b01709e16a/2019-002-FA_T20P_Tracklines_browse.jpg (JPEG)
    Thumbnail image of multibeam echo sounder tracklines collected in Cape Cod Bay, Massachusetts.
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 01-Aug-2019
    Ending_Date: 29-Aug-2019
    Currentness_Reference:
    data were collected on the following dates: 20190801-20190829 (Julian day 213-241).
  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 (1097)
    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.000005. Longitudes are given to the nearest 0.000005. 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?
    2019-002-FA_T20P_Tracklines.shp
    Shapefile of T20P multibeam echo sounder tracklines collected in Cape Cod Bay, Massachusetts during USGS Field Activity 2019-002-FA. (Source: U.S. Geological Survey)
    LineName
    Hysweep HSX filename for the T20-P MBES trackline in the format: UTC Julian date and time (DDD_NNNN_HHMM format, i.e. '221_0000_1703', where DDD is the Julian date, NNNN is an optional planning number (typically 0000) and HHMM is hour minute in UTC time). (Source: U.S. Geological Survey) Character set
    Year_JD
    Year and Julian day 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
    StartTime
    Calendar date and UTC time at the start of the survey line in the format: YYYY-MM-DD HH:MM:SS.SSS, example "2019-08-01 23:19:13.284". (Source: U.S. Geological Survey) Character set
    EndTime
    Calendar date and UTC time at the end of the survey line in the format: YYYY-MM-DD HH:MM:SS.SSS, example "2019-08-02 00:09:11.476". (Source: U.S. Geological Survey) Character set
    TotalTime
    Total survey time for a particular trackline. For lines longer than 60 minutes in duration, the format is HH:MM:SS.SSS, i.e. "01:04:23.333"; lines shorter than 60 minutes are in the format MM:SS.SSS, i.e. "49:58.192" (Source: U.S. Geological Survey) Character set
    SurveyID
    Woods Hole Coastal and Marine Science Center (WHCMSC) field activity identifier (e.g. "2019-002-FA" where 2019 is the survey year, 002 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 T20P trackline in kilometers (UTM Zone 19N, WGS 84) calculated in QGIS. (Source: U.S. Geological Survey)
    Range of values
    Minimum:0.01
    Maximum:28.23
    Units:kilometers
    Resolution:0.01

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Seth D. Ackerman
  2. Who also contributed to the data set?
    The authors acknowledge our fellow participants of the Cape Cod Bay field activities 2019-002-FA (Walter Barnhardt, Luke Bennett, Eric Moore, Alex Nichols, Jake Fredericks, and Dan Kennedy) and 2019-034-FA (Dann Blackwood, Eric Moore, and Alex Nichols); the crew of the M/V Warren Jr and the R/V Tioga; and our sea floor mapping group onshore support team during these surveys (Jane Denny, PJ Bernard, Barry Irwin, and Emile Bergeron).
  3. To whom should users address questions about the data?
    Seth Ackerman
    U.S. Geological Survey
    Geologist
    384 Woods Hole Rd.
    Woods Hole, MA
    USA

    508-548-8700 x2315 (voice)
    508-457-2310 (FAX)
    sackerman@usgs.gov

Why was the data set created?

This dataset contains a polyline shapefile representing the trackline navigation for approximately 4912 kilometers of multibeam echo sounder bathymetry and backscatter data collected by the U.S. Geological Survey during survey 2019-002-FA in Cape Cod Bay, Massachusetts. This information can help spatially correlate the bathymetry and backscatter data with other geophysical data.

How was the data set created?

  1. From what previous works were the data drawn?
    Reson T20P multibeam echo sounder raw bathymetry and backscatter (source 1 of 1)
    U.S. Geological Survey, Unpublished Material, raw MBES data in HSX format.

    Type_of_Source_Media: disc
    Source_Contribution:
    Multibeam echo sounder (MBES) bathymetry and backscatter data were collected using dual-head Reson T20-P sonars aboard the M/V Warren Jr. The system was pole-mounted on the port side of the vessel with the transducers located approximately 4.13 m below the waterline when deployed. Vessel navigation and attitude data were acquired using an Applanix POS MV Wavemaster (model 220, V5). An AML Micro X SV mounted on the sonar bracket monitored sound speed near the sonars during acquisition, and an AML MVP30 moving vessel profiler (MVP) or an AML Minos X sound velocity profiler (SVP) was deployed from the stern of the vessel to collect water column sound speed profiles at 1 to 4 hour intervals while underway (See shapefile 2019-002-FA_MVPSVP_data.shp available from the larger work citation). The Reson SeaBat User Interface (version 5.0.0.6) was used to control the sonars, as well as to monitor and record the sonar data. Hypack/Hysweep (version 2019, 19.X.X.X) was also used for record and monitor the sonar data. The SeaBat User Interface logged the navigation, attitude, bathymetry, time-series backscatter, and water column data to s7k format files for each sonar. The line files were created by the Reson UI using the following naming convention: YYYYMMDD_HHMMSS_M/S. The line files were appended with a "M" or "S" suffix to denote the port (primary) and starboard (or secondary) sonar heads, respectively. Hypack Hysweep 2019 also was used to log the navigation, attitude, and bathymetry data for both sonars to a single HSX format file. Hypack Hysweep filenames have the format 'YYYYMMDD_HHMMSS_LLL_HHMM', which prepends the Reson filename (YYYYMMDD_HHMMSS) to the Hypack Hysweep filename (LLL_HHMM), where LLL indicates the three digit planned line number and HHMM is the UTC time. The Hysweep HSX data were used to produce the final processed bathymetry grid. The Reson SeaBat User Interface s7k data were used to produce the final processed backscatter mosaic. This dataset was created from the Hysweep HSX data in CARIS HIPS (version 11.3).
  2. How were the data generated, processed, and modified?
    Date: May-2020 (process 1 of 3)
    PROCESSING STEP 1: CARIS HIPS DATA PROCESSING. Multibeam bathymetry processing within CARIS HIPS (version 11.3) post-survey consisted of the following flow:
    1) A vessel configuration file was created in CARIS for the HSX sonar files (WarrenJrHSX_4-24-2020.hvf) which included relevant, linear and angular installation offsets for each T20-P unit as well as vendor specified uncertainty values for each of the survey sensors.
    2) A CARIS HIPS project (version 11.3) was created with projection information set to Universal Transverse Mercator (UTM) Zone 19N, WGS84 using the vessel configuration file from step 1.
    3) Each HSX file was imported to the new CARIS project using the Import/Conversion Wizard.
    4) Delayed heave data from raw POS MV files were used to update HIPS survey lines using the import auxiliary data function.
    5) Post-processed navigation, vessel attitude, and GPS height data from POSPac SBET files, and post-processed RMS attitude error data from POSPac smrmsg files were used to update HIPS survey lines using the import auxiliary data function.
    6) Navigation source was set to Applanix SBET, and navigation was reviewed and edited as needed using the Navigation Editor tool.
    7) Georeference Bathymetry was done to apply the sound velocity corrections from the final SVP file (2019-002-FA_SVP_MASTER_v2.svp) containing all the sound velocity profiles collected during the survey, specifying the nearest in time method, delayed heave source, and use surface sound speed.
    8) 5-m resolution Swath Angle Weighted (SWATH) surfaces were created to incorporate all the files as they were processed, and the SWATH surfaces were reviewed for inconsistencies and anomalies.
    9) The swath and subset editors were used to remove spurious points through manual editing and filter application, and the refraction editor was used to adjust sound speed values in areas where sound velocity data did not adequately correct depth profiles, which were obviously influenced by local anomalies in speed of sound through the water column.
    The steps described above were performed by Brian Andrews and Bill Danforth. The contact person for this and all subsequent processing steps below is Seth Ackerman. Person who carried out this activity:
    Seth Ackerman
    U.S. Geological Survey
    Geologist
    384 Woods Hole Rd.
    Woods Hole, MA
    USA

    508-548-8700 x2315 (voice)
    508-457-2310 (FAX)
    sackerman@usgs.gov
    Date: Dec-2020 (process 2 of 3)
    PROCESSING STEP 2: EXPORT TRACKLINE NAVIGATION. All of the tracklines were selected in CARIS HIPS (version 11.3), then exported as a shapefile (File, Export, Selection, Shapefile...) using the coordinate reference system WGS 84 (EPSG:4326).
    Date: 17-May-2021 (process 3 of 3)
    PROCESING STEP 3: SHAPEFILE ATTRIBUTE TABLE FIELD ORGANIZATION:
    The trackline shapefile was loaded into an QGIS (version 3.14) project. Several fields representing CARIS HIPS processing parameters were removed. The remaining fields were renamed and reorganized using the QGIS attribute table editor into the final structure described in the Entity and Attribute information below. The QGIS tool 'Add Geometry Attributes' was used to calculate trackline length and 'Refactor' was used to set the precision for the trackline length field.
  3. What similar or related data should the user be aware of?
    Pendleton, E.A., Baldwin, W.E., Barnhardt., W.A., Ackerman, S.D., Foster, D.S., Andrews, B.D., and Schwab, W.C., 2013, Shallow Geology, Sea-floor Texture, and Physiographic Zones of the Inner Continental Shelf from Nahant to Northern Cape Cod Bay, Massachusetts: Open-File Report 2012-1157, U.S. Geological Survey, Coastal and Marine Geology Program, Woods Hole Coastal and Marine Science Center, Woods Hole, MA.

    Online Links:

    Andrews, B.D., Ackerman, S.D., Baldwin, W.E., and Barnhardt, W.A., 2010, Geophysical and Sampling Data from the Inner Continental Shelf: Northern Cape Cod Bay, Massachusetts: Open-File Report 2010-1006, U.S. Geological Survey, Coastal and Marine Geology Program, Woods Hole Coastal and Marine Science Center, Woods Hole, MA.

    Online Links:

    Ackerman, Seth D., Foster, David S., Danforth, William W., and Huntley, Emily C., 2019, High-resolution geophysical and sampling data collected off Town Neck Beach in Sandwich, Massachusetts, 2016: data release DOI:10.5066/P9HZHXXV, U.S. Geological Survey, Reston, VA.

    Online Links:

    Other_Citation_Details:
    Suggested citation: Ackerman S.D., Foster D.S., Danforth W.W., and Huntley, E.C., 2019, High-resolution geophysical and sampling data collected off Town Neck Beach in Sandwich, Massachusetts, 2016: U.S. Geological Survey data release, https://doi.org/10.5066/P9HZHXXV.

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 Systems (GNSS) with acceleration data from a Motion Reference Unit (MRU) and GPS azimuthal heading. The POS MV was configured with two AeroAntenna Technologies GPS antennas located at either end of a 2-m baseline, which was oriented fore and aft and mounted atop the MBES pole, approximately midships on the port side of vessel. DGPS positions are horizontally accurate to 0.5 - 2 meters, but accuracy improves to less than 10 cm after post-processing with Applanix POSPac (version 8.1).
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
    Data were collected on the following dates: 20190801-20190829 (Julian day 213-241); bathymetry data from 20190801 (Julian day 213) and 20190827 (Julian day 239) includes data processed for performing the patch test to calibrate the multibeam sonar but these data were not incorporated into the final bathymetry dataset or the backscatter mosaic. Data collected during some turns and along lines that extend beyond the area of a continuous geophysical survey data were also excluded from the final bathymetry dataset and backscatter mosaic. However, the patch test tracklines and tracklines that extend beyond the survey area are all included in this shapefile.
  5. How consistent are the relationships among the observations, including topology?
    Multibeam echo sounder (MBES) data were collected during 24-hour survey operations in August 2019. Acquisition may have been suspended briefly during file changes or for longer periods during turns and system calibration, malfunction, or troubleshooting system issues. Any gaps between the polyline features in this shapefile reflect those time periods where data were not recorded.
    This trackline shapefile was generated from the bathymetry data processed in Computer Aided Resource Information System (CARIS) Hydrographic Information Processing System (HIPS; version 11.3) using the Hysweep HSX raw sonar files. Note that backscatter imagery (processed in QPS FMGT version 7.8.9) was created using the Reson UI s7k raw files (M_ and S_ survey lines) that were collected simultaneously with the Hysweep HSX files. This polyline shapefile only represents the HSX tracklines which are generally the same extent as the s7k tracks. The s7k (M_ and S_) sonar files are mostly coincident with each other, although they can become unsynchronized. The small timing offset only affects the timing of survey file changes and the resulting line names, not the quality of the data.

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 dataset.
  1. Who distributes the data set? (Distributor 1 of 1)
    Seth Ackerman
    U.S. Geological Survey
    Geologist
    384 Woods Hole Rd.
    Woods Hole, MA
    USA

    508-548-8700 x2315 (voice)
    508-457-2310 (FAX)
    sackerman@usgs.gov
  2. What's the catalog number I need to order this data set? Multibeam echo sounder, Reson T-20P tracklines, collected in Cape Cod Bay, Massachusetts during USGS Field Activity 2019-002-FA: includes the shapefile 2019-002-FA_T20P_Tracklines.shp, the browse graphic 2019-002-FA_T20P_Tracklines_browse.jpg, and the Federal Geographic Data Committee (FGDC) Content Standards for Digital Geospatial Metadata (CSDGM) metadata file 2019-002-FA_T20P_Tracklines_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. Although these data and associated metadata have been reviewed for accuracy and completeness and approved for release by the U.S. Geological Survey (USGS), and have been processed successfully on a computer system at the USGS, no warranty expressed or implied is made regarding the display or utility of the data for other purposes, nor on all computer systems, nor shall the act of distribution constitute any such warranty. The USGS or the U.S. Government shall not be held liable for improper or incorrect use of the data described and/or contained herein. Any use of trade, firm, or product 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, or GIS software.

Who wrote the metadata?

Dates:
Last modified: 23-Apr-2024
Metadata author:
Seth Ackerman
U.S. Geological Survey
Geologist
384 Woods Hole Rd.
Woods Hole, MA
USA

508-548-8700 x2315 (voice)
508-457-2310 (FAX)
whsc_data_contact@usgs.gov
Contact_Instructions:
The metadata contact email address is a generic address in the event the person is no longer with USGS. (updated on 20240423)
Metadata standard:
Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)
This page is <https://cmgds.marine.usgs.gov/catalog/whcmsc/DRB_data_release/DRB_P99DR4PN/2019-002-FA_T20P_Tracklines_meta.faq.html>
Generated by mp version 2.9.51 on Thu Jun 27 10:43:57 2024