Multibeam echo sounder, Reson T-20P tracklines collected in Little Egg Inlet and offshore the southern end of Long Beach Island, NJ, during USGS Field Activity 2018-001-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 echo sounder, Reson T-20P tracklines collected in Little Egg Inlet and offshore the southern end of Long Beach Island, NJ, during USGS Field Activity 2018-001-FA (Esri polyline shapefile, GCS WGS 84)
Abstract:
The natural resiliency of the New Jersey barrier island system, and the efficacy of management efforts to reduce vulnerability, depends on the ability of the system to recover and maintain equilibrium in response to storms and persistent coastal change. This resiliency is largely dependent on the availability of sand in the beach system. In an effort to better understand the system's sand budget and processes in which this system evolves, high-resolution geophysical mapping of the sea floor in Little Egg Inlet and along the southern end of Long Beach Island near Beach Haven, New Jersey was conducted from May 31 to June 10, 2018, followed by a sea floor sampling survey conducted from October 22 to 23, 2018, as part of a collaborative effort between the U.S. Geological Survey and Stockton University. Multibeam echo sounder bathymetry and backscatter data were collected along 741 kilometers of tracklines (approximately 200 square kilometers) of the coastal sea floor to regionally define its depth and morphology, as well as the type and distribution of sea-floor sediments. Six hundred ninety-two kilometers of seismic-reflection profile data were also collected to define the thickness and structure of sediment deposits in the inlet and offshore. These new data will help inform future management decisions that affect the natural and recreational resources of the area around and offshore of Little Egg Inlet. These mapping surveys provide high-quality data needed to build scientific knowledge of the evolution and behavior of the New Jersey barrier island system.
Supplemental_Information:
Additional information on the field activities associated with this project are available at https://cmgds.marine.usgs.gov/fan_info.php?fan=2018-001-FA and https://cmgds.marine.usgs.gov/fan_info.php?fan=2018-049-FA.
  1. How might this data set be cited?
    U.S. Geological Survey, 20210422, Multibeam echo sounder, Reson T-20P tracklines collected in Little Egg Inlet and offshore the southern end of Long Beach Island, NJ, during USGS Field Activity 2018-001-FA (Esri polyline shapefile, GCS WGS 84): data release DOI:10.5066/P9C3J33K, 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., Barnhardt, Walter A., Worley, Charles R., Nichols, Alex R., Baldwin, Wayne E., and Evert, Steve, 2021, High-resolution geophysical and geological data collected in Little Egg Inlet and offshore the southern end of Long Beach Island, NJ, during USGS Field Activities 2018-001-FA and 2018-049-FA: data release DOI:10.5066/P9C3J33K, U.S. Geological Survey, Reston, VA.

    Online Links:

    Other_Citation_Details:
    Suggested citation: Ackerman, S.D., Barnhardt, W.A., Worley, C.R., Nichols, A.R., Baldwin, W.E., and Evert, S., 2021, High-resolution geophysical and geological data collected in Little Egg Inlet and offshore the southern end of Long Beach Island, NJ, during USGS Field Activities 2018-001-FA and 2018-049-FA: U.S. Geological Survey data release, https://doi.org/10.5066/P9C3J33K.
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -74.472894
    East_Bounding_Coordinate: -74.195914
    North_Bounding_Coordinate: 39.567002
    South_Bounding_Coordinate: 39.37764
  3. What does it look like?
    https://www.sciencebase.gov/catalog/file/get/5f5f952e82ce3550e3bff21c/?name=2018-001-FA_T20P_Tracklines_browse.jpg (JPEG)
    Thumbnail image of multibeam echo sounder tracklines collected off southern Long Beach Island, New Jersey.
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 31-May-2018
    Ending_Date: 10-Jun-2018
    Currentness_Reference:
    data were collected on the following dates: 20180531-20180610 (Julian day 151-161); bathymetry data from 20180531 (Julian day 151) were processed for performing the patch test to calibrate the multibeam sonar; these data were not incorporated into the final bathymetry dataset; but the tracklines are in this shapefile. No surveying was done on 20180603 (Julian day 154).
  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 (388)
    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?
    2018-001-FA_T20P_Tracklines
    T20P multibeam echo sounder tracklines collected off southern Long Beach Island, New Jersey during USGS Field Activity 2018-001-FA. (Source: U.S. Geological Survey)
    LineName
    Reson SeaBat User Interface s7k filename for the T20-P MBES trackline in the format: UTC start date and time (YYYYMMDD_HHMMSS format, i.e. '20180605_114157'). The file names for the primary/main and secondary T20-P units are prepended with 'M_' or 'S_', respectively. (Source: U.S. Geological Survey) Character set
    YrJD_strt
    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
    JD_UTC_strt
    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
    YrJD_end
    Year and Julian day (YYYY-JD) at the end 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
    JD_UTC_end
    Julian day and UTC time at the end 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
    SurveyID
    Woods Hole Coastal and Marine Science Center (WHCMSC) field activity identifier (e.g. "2018-001-FA" where 2018 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 12N, WGS 84) calculated in the SQLite database. (Source: U.S. Geological Survey)
    Range of values
    Minimum:0.01
    Maximum:9.80
    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)
    • U.S. Geological Survey
  2. Who also contributed to the data set?
  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 trackline navigation for approximately 741 kilometers of multibeam echo sounder bathymetry and backscatter data collected by the U.S. Geological Survey during cruise 2018-001-FA collected off southern Long Beach Island, New Jersey. 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 s7k 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. The pair of mills cross transmit and receive arrays were mounted side-by-side within a bracket that oriented them at opposing 30-degree angles (relative to horizontal). The bracket was pole-mounted on the starboard side of the R/V Petrel so that the sonar arrays were oriented athwart ships (primary and secondary arrays facing outward and down to port and starboard, respectively) and located approximately 1.235 m below the waterline when deployed. Vessel navigation and attitude data were acquired using an Applanix POS MV Wavemaster (model 220, V5) 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 starboard side of vessel, and the wetpod MRU mounted atop the sonar bracket just aft of the pole. An AML Micro X SV mounted on the sonar bracket monitored sound speed near the sonars during acquisition, and an ODIM MVP30 moving vessel profiler (MVP), mounted on the stern, was used to collect water column sound speed profiles at 1 to 2 hour intervals while underway (See shapefile 2018-001-FA_MVP_data.shp available from the larger work citation). The Reson SeaBat User Interface (version 5.0.0.6) was used to control the sonars, which were operated in intermediate mode at full power (220 db), with frequency-modulated pulses between 200 to 300 kHz. The range of the 1024 across track beams formed by the sonars were adjusted manually depending on water depth, and resulted in combined swath widths of 60 to 200 meters or typically 3 to 6 times the water depth. Data were monitored and recorded using the Reson SeaBat User Interface (UI) (version 5.0.0.6) and Hypack/Hysweep (version 2017, 17.1.3.0). 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" and "S" suffix to denote the port (primary) "M" and "S" starboard (or secondary) sonar heads. HYSWEEP also was used to log the navigation, attitude, and bathymetry data for both sonars to a single HSX format file. The Reson SeaBat User Interface s7k data were used to produce the final processed backscatter mosaic and bathymetry grid.
  2. How were the data generated, processed, and modified?
    Date: Sep-2018 (process 1 of 5)
    PROCESSING STEP 1: CARIS HIPS DATA PROCESSING. Multibeam bathymetry processing within CARIS HIPS (version 10.4.1) during the survey consisted of the following flow:
    1) Vessel configuration files were created in CARIS for the port ("M"=main, or primary) and starboard ("S"=secondary) sonars (Petrel_dual_T20P_s7k_M.hvf, and Petrel_dual_T20P_s7k_S.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 10.4.1) was created with projection information set to Universal Transverse Mercator (UTM) Zone 18N, WGS 84. Separate HIPS projects were created for the Port (M), and Starboard (S) line files using the two vessel configuration files in #1 above.
    3) Each Reson s7k file (M and S) were imported to the new CARIS projects (M and S respectively) 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) Navigation was reviewed and edited as needed using the Navigation Editor tool.
    6) Sound velocity correction was applied using the CARIS algorithm, a master SVP file containing all the sound velocity profiles collected during the survey and specifying the nearest in distance method, delayed heave source, and use surface sound speed.
    7) Data were merged selecting no tide and the delayed heave source.
    8) 4-m resolution Swath Angle Weighted (SWATH) surfaces were created to incorporate all the files (M and S) 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.
    10) Survey lines adjusted for refraction anomalies were remerged, and the respective SWATH surfaces were recomputed to reflect the changes. Processing during the survey was primarily focused on QA/QC during acquisition. Editing processes did require trial and error and were at times iterative. This process step was completed over the course of several months beginning with work done during the survey in June 2018; the date on this process step indicated below is the last day described processing was done. 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: Jul-2019 (process 2 of 5)
    PROCESSING STEP 2: APPLY POST PROCESSED SBET FILES AND EDIT SOUNDINGS.
    Post-survey processing within CARIS HIPS (version 10.4.1) consisted of the following flow: 1) Post-processed navigation, vessel attitude, and GPS height data from POSPac SBET files were used to update HIPS survey lines using the import auxiliary data function.
    2) Navigation source was set to Applanix SBET, and navigation was reviewed and edited as needed using the Navigation Editor tool.
    Date: Jan-2020 (process 3 of 5)
    PROCESSING STEP 3: EXTRACT NAVIGATION. Use Caris printfNav and Python to extract and reformat the navigation fixes stored in the Caris HIPS database and add them to a geospatial SQLite (version 3.27.1) database: 1) Extract navigation for each line in Caris HDCS directory using the Caris program printfNav for all the lines. (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 TXT navigation files for each survey line in the Caris project.
    2) A Python script (CARIS_bathynav2sql_2018-001-FA.py) runs on the navigation TXT files, creating a new line in the SQLite database (which is created if it does not already exist) for each record, with new fields survey ID, vessel name, and system name. The script creates both point and polyline navigation for each survey line.
    Date: Jan-2020 (process 4 of 5)
    PROCESSING STEP 4: CREATE ESRI SHAPEFILE CONTAINING THE POLYLINE DATA: The T20P polyline features was exported from the SQLite database as in ESRI Shapefile format using Spatialite-tools (version 4.3.0_3) using the terminal command: 
    > spatialite_tool -e -shp 2018-001-FA_T20P_Tracklines -d /Data/2018_001_FA_NJ/proc/SQLdb/2018-001-FA-SQLdb.sqlite -t BathyTrack_ln -g geom_bathyt -c CP1252 -s 4326 --type LINESTRING
    Date: Apr-2020 (process 5 of 5)
    PROCESING STEP 5: RENAME SHAPEFILE ATTRIBUTE TABLE FIELDS:
    The trackline shapefile was loaded into an QGIS (version 3.10) project. The following attribute table field names were updated using the Layer Properties dialog: 'Year_JD_i0' was changed to 'YrJD_strt', 'JD_UTC_in0' was changed to 'JD_UTC_strt', 'Year_JD_e0' was changed to 'YrJD_end', and 'JD_UTC_end' was kept as is. The remaining field headers were unchanged. The QGIS tool Refactor was used to set the precision for the trackline length field.
  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?
    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 starboard side of vessel. DGPS 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. DGPS positions are horizontally accurate to 0.5 - 2 meters, but accuracy can increase 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?
    The only multibeam-sonar data collected on 20180531 (May 31, Julian day 151) was the sonar patch test, used to calibrate any attitude offsets for the bathymetry data; these data were processed and used for the patch test but not incorporated into the final bathymetry dataset since the same area was re-occupied on subsequent survey days. However, the patch test tracklines are included in this shapefile. Also, no data were collected on 20180603 (June 3; Julian day 154) due to rough sea-state.
  5. How consistent are the relationships among the observations, including topology?
    Multibeam echo sounder (MBES) data were collected during day-trip survey operations, usually 8-10 hours per day. 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.
    Note that the M_ and S_ survey lines are collected simultaneously because of the dual-headed sonar system. The sonar files are often coincident, although occasionally becomes unsynchronized which does not affect the quality of the data, just the timing of survey file changes and line naming. Therefore, the total length of survey lines reported in this dataset will be approximately double the actual distance traveled by the survey vessel during data collection.

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)
    U.S. Geological Survey - ScienceBase
    U.S. Geological Survey
    Denver Federal Center, Building 810, Mail Stop 302
    Denver, CO
    United States

    1-888-275-8747 (voice)
    sciencebase@usgs.gov
  2. What's the catalog number I need to order this data set? Multibeam echo sounder, Reson T-20P tracklines, collected off southern Long Beach Island, New Jersey during USGS Field Activity 2018-001-FA: includes the shapefile 2018-001-FA_T20P_Tracklines.shp, the browse graphic 2018-001-FA_T20P_Tracklines_browse.jpg, and the Federal Geographic Data Committee (FGDC) Content Standards for Digital Geospatial Metadata (CSDGM) metadata file 2018-001-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 capable of utilizing web mapping or feature services.

Who wrote the metadata?

Dates:
Last modified: 22-Apr-2021
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)
sackerman@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_P9C3J33K/2018-001-FA_T20P_Tracklines_meta.faq.html>
Generated by mp version 2.9.50 on Tue Sep 21 18:19:01 2021