Sonobuoy Seismic and Navigation Data Collected Using Sercel GI Guns and Ultra Electronics Seismic Sonobuoys During the Mid-Atlantic Resource Imaging Experiment (MATRIX), USGS Field Activity 2018-002-FA

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

Frequently anticipated questions:

What does this data set describe?

Title:
Sonobuoy Seismic and Navigation Data Collected Using Sercel GI Guns and Ultra Electronics Seismic Sonobuoys During the Mid-Atlantic Resource Imaging Experiment (MATRIX), USGS Field Activity 2018-002-FA
Abstract:
In summer 2018, the U.S. Geological Survey partnered with the U.S Department of Energy and the Bureau of Ocean Energy Management to conduct the Mid-Atlantic Resources Imaging Experiment (MATRIX) as part of the U.S. Geological Survey Gas Hydrates Project. The field program objectives were to acquire high-resolution 2-dimensional multichannel seismic-reflection and split-beam echo sounder data along the U.S Atlantic margin between North Carolina and New Jersey to determine the distribution of methane gas hydrates in below-sea floor sediments and investigate potential connections between gas hydrate dynamics and sea floor methane seepage. MATRIX field work was carried out between August 8 and August 28, 2018 on the research vessel Hugh R. Sharp and resulted in acquisition of more than 2,000 track-line kilometers of multichannel seismic-reflection and colocated split-beam echo sounder data, along with wide-angle seismic reflection and refraction data from 63 expendable sonobuoy deployments.
Supplemental_Information:
This research was supported by USGS Coastal and Marine Hazards and Resources Program, USGS-DOE interagency agreement DE-FE0023495, and USGS-BOEM interagency agreement M17PG00041. Additional information on the field activity is available from https://www.usgs.gov/centers/whcmsc/science/mid-atlantic-resource-imaging-experiment-matrix?qt-science_center_objects=0#qt-science_center_objects and https://cmgds.marine.usgs.gov/fan_info.php?fan=2018-002-FA.
  1. How might this data set be cited?
    Baldwin, Wayne, Foster, David, Bergeron, Emile, Ferro, Peter Dal, McKee, Jennifer, Moore, Eric, Nichols, Alex, O'Brien, Thomas, Powers, Dan, Miller, Nathaniel, and Ruppel, Carolyn, 20210428, Sonobuoy Seismic and Navigation Data Collected Using Sercel GI Guns and Ultra Electronics Seismic Sonobuoys During the Mid-Atlantic Resource Imaging Experiment (MATRIX), USGS Field Activity 2018-002-FA: data release DOI:10.5066/P97LBUSP, U.S. Geological Survey, Coastal and Marine Hazards and Resources Program, Woods Hole Coastal and Marine Science Center, Woods Hole, Massachusetts.

    Online Links:

    Other_Citation_Details:
    Suggested citation: Baldwin, W.E., Foster, D.S., Bergeron, E.M., Dal Ferro, P., McKee, J.A., Moore, E.M., Nichols, A.R., O'Brien, T.F., Powers, D., Miller, N.C., and Ruppel, C.D., 2021, Sonobuoy seismic and navigation data collected using Sercel GI guns and Ultra Electronics expendable sonobuoys during the Mid-Atlantic Resource Imaging Experiment (MATRIX), USGS Field Activity 2018-002-FA: U.S. Geological Survey data release, https://doi.org/10.5066/P97LBUSP.
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -74.255774
    East_Bounding_Coordinate: -70.967755
    North_Bounding_Coordinate: 38.624090
    South_Bounding_Coordinate: 36.546064
  3. What does it look like?
    https://www.sciencebase.gov/catalog/file/get/5fecb0c1d34ea5387defd613/?name=2018-002-FA_SBBrowseImage.jpg (JPEG)
    Sonobuoy browse image.
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 10-Aug-2018
    Ending_Date: 27-Aug-2018
    Currentness_Reference:
    ground condition
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: tabular, vector, binary, and raster digital data
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
    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 WGS 1984.
      The ellipsoid used is WGS 84.
      The semi-major axis of the ellipsoid used is 6378137.0.
      The flattening of the ellipsoid used is 1/298.257224.
  7. How does the data set describe geographic features?
    2018-002-FA_SB_depnav.shp
    Sonobuoy deployment location point shapefile for survey 2018-002-FA (63 point features). (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.
    SBDepLon
    Longitude coordinate of sonobuoy deployment in decimal degrees, WGS 84, negative value indicates Western hemisphere. (Source: U.S. Geological Survey)
    Range of values
    Minimum:-74.136881
    Maximum:-70.967949
    Units:degrees
    Resolution:1E-06
    SBDepLat
    Latitude coordinate of sonobuoy deployment in decimal degrees, WGS 84. (Source: U.S. Geological Survey)
    Range of values
    Minimum:36.577548
    Maximum:38.62409
    Units:degrees
    Resolution:1E-06
    SBName
    Name of the sonobuoy deployment during which seismic data were attempted to be collected in the format: FieldActivity#-DeploymentNumber (i.e.'2018-002-FA_SB01'). (Source: U.S. Geological Survey) Character set
    SB_Image
    PNG image name of seismic profile corresponding to sonobuoy deployment. If no image is available for the survey line, the value is set to "no image available". (Source: U.S. Geological Survey) Character set
    Year
    Year the data were collected YYYY. (Source: U.S. Geological Survey) Character set
    JD_UTC
    Julian day and UTC time of the MCS shot in the sonobuoy record 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
    WHCMSC field activity identifier (e.g. "2018-002-FA" where 2018 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
    Device used to collect seismic data. (Source: U.S. Geological Survey) Character set
    2018-002-FA_SB_shtnav.shp
    Sonobuoy MCS shot point navigation shapefile for survey 2018-002-FA (23311 point features). (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.
    SBDepLon
    Longitude coordinate of sonobuoy deployment in decimal degrees, WGS 84, negative value indicates Western hemisphere. (Source: U.S. Geological Survey)
    Range of values
    Minimum:-74.136881
    Maximum:-70.967949
    Units:degrees
    Resolution:1E-06
    SBDepLat
    Latitude coordinate of sonobuoy deployment in decimal degrees, WGS 84. (Source: U.S. Geological Survey)
    Range of values
    Minimum:36.577548
    Maximum:38.42298
    Units:degrees
    Resolution:1E-06
    ShtLon
    Longitude coordinate of MCS shot in decimal degrees, WGS 84, negative value indicates Western hemisphere. Used to generate the point feature geometry. (Source: U.S. Geological Survey)
    Range of values
    Minimum:-74.255774
    Maximum:-70.967755
    Units:degrees
    Resolution:1E-06
    ShtLat
    Latitude coordinate of MCS shot in decimal degrees, WGS 84. Used to generate the point feature geometry. (Source: U.S. Geological Survey)
    Range of values
    Minimum:36.546064
    Maximum:38.422745
    Units:degrees
    Resolution:1E-06
    SBName
    Name of the sonobuoy deployment during which seismic data were collected in the format: FieldActivity#-DeploymentNumber (i.e.'2018-002-FA_SB01'). (Source: U.S. Geological Survey) Character set
    LineName
    Name of the MCS seismic-reflection profile collected concurrently with the sonobuoy deployment in the format: FieldActivity#-FileNumber (i.e.'2018-002-FA_MX01'). (Source: U.S. Geological Survey) Character set
    FFID
    MCS Line shot number. (Source: U.S. Geological Survey)
    Range of values
    Minimum:132
    Maximum:9117
    Units:shot
    Resolution:1
    Offset
    Nominal offset distance in meters (Geographic, WGS 84) between static sonobuoy deployment position and successive MCS shot positions. Negative numbers indicate sonobuoy position forward of airgun sources along the trackline. (Source: U.S. Geological Survey)
    Range of values
    Minimum:-46
    Maximum:20259
    Units:shot
    Resolution:1
    Year
    Year the data were collected YYYY. (Source: U.S. Geological Survey) Character set
    JD_UTC
    Julian day and UTC time of the MCS shot in the sonobuoy record in the format: JD:HH:MM:SS.SSSSSS; 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
    WHCMSC field activity identifier (e.g. "2018-002-FA" where 2018 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
    Device used to collect seismic data. (Source: U.S. Geological Survey) Character set
    2018-002-FA_SB_shtnav.csv
    Sonobuoy MCS shot point navigation ASCII CSV file for survey 2018-002-FA (23311 point features). Attribute information is identical to '2018-002-FA_SB_shtnav.shp' except for the omission of the 'FID' and 'Shape' columns. The first row of the file represents the column headers. (Source: U.S. Geological Survey)
    2018-002-FA_SB_shtTracklines.shp
    Sonobuoy shot trackline shapefile for survey 2018-002-FA (46 polyline features). (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.
    SBName
    Name of the sonobuoy deployment during which seismic data were collected in the format: FieldActivity#-DeploymentNumber (i.e.'2018-002-FA_SB01'). (Source: U.S. Geological Survey) Character set
    SB_Image
    PNG image name of seismic profile corresponding to sonobuoy deployment. (Source: U.S. Geological Survey) Character set
    LineName
    Name of the MCS seismic-reflection profile collected concurrently with the sonobuoy deployment in the format: FieldActivity#-FileNumber (i.e.'2018-002-FA_MX01'). (Source: U.S. Geological Survey) Character set
    FFID_init
    MCS Line shot number at the start of the sonobuoy recording. (Source: U.S. Geological Survey)
    Range of values
    Minimum:132
    Maximum:8680
    Units:shot
    Resolution:1
    FFID_end
    MCS Line shot number at the end of the sonobuoy recording. (Source: U.S. Geological Survey)
    Range of values
    Minimum:561
    Maximum:9117
    Units:shot
    Resolution:1
    Year
    Year the data were collected (YYYY). (Source: U.S. Geological Survey) Character set
    JDUTC_init
    Julian day and UTC time of the first MCS shot in the sonobuoy record in the format: JD:HH:MM:SS.SSSSSS; 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_end
    Julian day and UTC time of the last MCS shot in the sonobuoy record in the format: JD:HH:MM:SS.SSSSSS; 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
    WHCMSC field activity identifier (e.g. "2018-002-FA" where 2018 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
    Device used to collect seismic data. (Source: U.S. Geological Survey) Character set
    Length_km
    Length of sonobuoy profile line in kilometers (Geographic WGS 84) calculated in the SQLite database. (Source: U.S. Geological Survey)
    Range of values
    Minimum:5.07
    Maximum:20.29
    Units:kilometers
    Resolution:0.01
    2018-002-FA_SB_Images
    Portable network graphic images of sonobuoy profiles for survey 2018-002-FA (46 PNG images). (Source: U.S. Geological Survey)
    2018-002-FA_SB_SegyData
    Binary SEG-Y format files of sonobuoy profiles for survey 2018-002-FA (46 SEG-Y files). (Source: U.S. Geological Survey)
    Entity_and_Attribute_Overview:
    The 46 PNG sonobuoy profile images can be hyperlinked to their corresponding trackline or deployment locations in ArcGIS using the shapefiles '2018-002-FA_SB_shtTracklines.shp' or '2018-002-FA_SB_depnav.shp', respectively. The images illustrate nominal offset distance between the sonobuoy deployment location and the recorded MCS shot location along the profile on the x-axis (annotation at 1000-meter intervals) and two-way travel time (seconds) on the y-axis.
    The 46 binary SEG-Y files (Norris and Faichney, 2002) provided for each sonobuoy deployment that recorded MCS shots contain minimally processed shot gathers with nominal source-receiver offsets and navigation in the trace headers. A SEG-Y file consists of 1) a 3200-byte textural file header containing general information (see examples following processing steps); 2) a 400-byte binary record with information such as sample rate and record length specific to the data set; and 3) multiple records, one seismic reflection trace per record. Each trace record is preceded by a 240-byte "trace header" containing information such as trace number and acquisition day and time specific to each trace. The trace data are represented as a time series of unitless 16-bit integer or 32-bit real numbers proportional to the pressure recorded at each hydrophone. The SEG-Y file is useful only if you have access to specialized software designed to process and display seismic reflection data.
    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)
    • Wayne Baldwin
    • David Foster
    • Emile Bergeron
    • Peter Dal Ferro
    • Jennifer McKee
    • Eric Moore
    • Alex Nichols
    • Thomas O'Brien
    • Dan Powers
    • Nathaniel Miller
    • Carolyn Ruppel
  2. Who also contributed to the data set?
    Colby Pedrie and E. Lee Ellett of Scripps Institution of Oceanography provided access to critical seismic equipment and expertise. Jess Stark and Ray Hatton of Stark Industries assisted with compressor logistics. Timothy Elfers and Patrick Hart of the USGS - Pacific Coastal and Marine Science Center contributed to project scoping, compressor contracting, and machining. The marine office of the University of Delaware, along with the crew of the R/V Hugh R. Sharp, accommodated numerous requests and changes to ensure the success of the program. Protected species visual observers were provided by RPS, Inc.
  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 sonobuoy deployment and multichannel seismic shot navigation, processed sonobuoy profile images, and processed sonobuoy SEG-Y trace data collected during 63 expendable seismic sonobuoy deployments by the U.S. Geological Survey during the Mid-Atlantic Resource Imaging Experiment (MATRIX; field activity 2018-002-FA). The data were acquired along portions of the U.S. Atlantic margin between North Carolina and New Jersey to support mapping of sedimentary and structural features of the sea floor and subsurface and evaluation of geologic hazards and the distribution of methane gas hydrates in below-seafloor sediments.

How was the data set created?

  1. From what previous works were the data drawn?
    MCS and sonobuoy data (source 1 of 1)
    U.S. Geological Survey, Unpublished Material, Raw MCS and sonobuoy data.

    Type_of_Source_Media: disc
    Source_Contribution:
    Multichannel seismic-reflection data were shot using up to four Sercel 105/105 cubic inch generator-injector (GI) airguns powered by four portable Stark Industries diesel compressors. The sources were configured in two strings of two guns that were towed 47.8 m astern of the NRP off the port and starboard quarters of the R/V Hugh R. Sharp. The airgun strings were controlled and synchronized by two Teledyne Marine Hotshot units. The sources were typically triggered on distance (25 - 35 m intervals) using the USGS developed RaspberryPi and Python based TriggerPi controller, but also occasionally on time (equating to similar shot distances) using the Geometrics CNT-1 software. Shot times were recorded with microsecond precision using the Hotshot blast phone monitoring to return a shot-instant trigger that was transmitted to an FEI-Zyfer Inc. GPStarplus Model 565 GPS clock for precise day and time tagging (DDD:HH:MM:SS.SSSSSS), and ultimately logged to HYPACK (version 2018, 18.1.11.0) raw files via serial connection. Shots were recorded using Ultra Electronics Maritime Systems Inc. expendable seismic sonobuoys (models AN/SSQ-53D(3) and AN/SSQ-53G), which were deployed from either the port or starboard 01 deck (dependent upon current direction and streamer feather), approximately amidships, either using a pneumatic launch tube or by hand. Sonobuoys were programmed to deploy the hydrophone to a depth of 61 m and transmit data over a user selected VHF channel. VHF signals from up to three simultaneously transmitting sonobuoys were received via a Laird PLC-1666 Yagi antenna mounted on the flying bridge. The analog signals were split to three Winradio G39WSB USB sonobuoy receivers and passed to a Reftek RT160 data logger, which digitized the data at 24-Bits and a 1-millisecond sample rate, and continuously logged the three separate channels to IRIS (Incorporated Research Institutions of Seismology) miniSEED formatted files (https://ds.iris.edu/ds/nodes/dmc/data/formats/miniseed/). A split from the NRP GPS antenna was fed to the RT160 GPS receiver to provide common day and time information to the miniSEED sonobuoy records. Geometrics CNT-1 seismic acquisition software (version 5.361) running on a Windows PC was used to control the multichannel system, digitally log traces in the Geometrics SEG-D format, and record shot NRP GPS navigation coordinates to the SEG-D external headers.
  2. How were the data generated, processed, and modified?
    Date: Jun-2020 (process 1 of 6)
    PROCESS STEP 1:
    Shearwater Reveal (version 4.1) seismic processing software was used to execute the following processing flows to produce MCS layback shot navigation.
    1. Import SEG-D sequences: SegDRead read raw Geometrics SEG-D shot sequence files, extracted navigation fixes from the external headers, and wrote them to new header words. HeaderMath converted the source lat/lon positions from seconds of arc to decimal degrees (NRP_LAT, NRP_LON). UTMLatLong projected the geographic navigation to UTM Zone 18N WGS 84 meters (NRP_X, and NRP_Y). Output wrote the trace sequence to Reveal formatted ".seis" files.
    2. Layback geometry assignment: Input read sequence files sorted by FFID/CHANNEL. The Python module ShotlineLayback (developed by Nathan Miller of USGS-WHCMSC) defined the source and streamer geometry based on measured horizontal offsets from the NRP to the center of the sources (cos) and the centers of the first and last 6.25 m spaced channel groups, and when necessary, the first and last 12.5 m spaced channel groups on the active streamer section. The following table lists the linear offsets from the NRP to center of source (COS) and index channels (IC) used to define layback geometry by line.
    NRP to COS offset,NRP to IC offset(IC#) - Linelist -47.8,-174.6(1)/-922.69(120)/-932.38(121)/-1320.81(152) - Line MX01 -47.8,-176.6(1)/-924.69(120)/-934.38(121)/-1322.81(152) - Lines MX02 and MX03 -47.8,-176.6(1)/-874.38(112) - Lines MX04 - MX10 -47.8,-176.6(1)/-975(128)/-984.69(129)/-1373.12(160) - Lines MX11 - MX17 -47.8,-176.6(1)/-975(128)/-984.69(129)/-1272.56(152) - Lines MX18 and MX19
    The module interpolated a sail line from the shot NRP positions (NRP_X and NRP_Y), then computed layback positions for the source and channel groups (values were interpolated for all channels in between the defined index channels) for each FFID by translating them back along the sail line by their respective offsets. Layback midpoint positions along the sail line were also computed for each shot/receiver pair. HeaderMath computed and populated a new header word for trace offset using OFFSET = ABS(NRP2CHAN) - ABS(NRP2COS). Output wrote the trace sequence with defined geometry to new files.
    4. Geometry modification for tailbuoy navigation: Tailbuoy GPS navigation acquired during lines MX01 to MX07 and MX11 to MX19 were used to adjust the source and streamer geometry to incorporate trigonometrically estimated streamer feather into the CMP binning process. Input read the layback geometry files. Text files containing tailbuoy positions and UTC times extracted from HYPACK raw files were used as inputs for DBmerge, which matched times in the trace headers to times in the tailbuoy navigation file (through interpolation) and inserted tailbuoy positions into the trace headers (TB_LON and TB_LAT). UTMLatLong projected the geographic tailbuoy positions to WGS84 UTM Zone 18N meters (TB_X and TB_Y). HeaderMath estimated the streamer feather azimuth relative to the NRP using CABLE_AZ_RAD = atan2(NRP_Y - TB_Y, NRP_X - TB_X), then calculated new layback and feather adjusted source and receiver positions using SRC_X = NRP_X + NRP2COS * cos(CABLE_AZ_RAD), SRC_Y = NRP_Y + NRP2COS * sin(CABLE_AZ_RAD), REC_X = NRP_X + NRP2CHAN * cos(CABLE_AZ_RAD), REC_Y = NRP_Y + NRP2CHAN * sin(CABLE_AZ_RAD). DBWrite wrote the feather adjusted source positions (in UTM 18N WGS84 meters and geographic decimal degrees), FFID number, year, day number, and UTC times for the shots in each line to ASCII CSV files.
    These process steps and all subsequent process steps were conducted by the same person - Wayne Baldwin. Person who carried out this activity:
    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
    Date: Oct-2020 (process 2 of 6)
    PROCESS STEP 2:
    The following processing flow was executed within a python notebook (FA2018002_SonobuoyMiniseed.ipynb) on raw sonobuoy traces and navigation by deployment.
    1. Obspy (version 1.2.2) was used to read all raw miniSEED files contributing to a deployment into a merged three trace stream. Interactive plotting was used to identify the trace containing data for the deployment and determine the date and times of the hydrophone deployment and the first and last recorded shots. A position for the hydrophone deployment was manually retrieved from the Hemisphere GPS message in the HYPACK raw file corresponding to the determined time. During this process a row for each sonobuoy deployment containing columns for its coordinates, name, year, UTC day and time, image name, SurveyID, VehicleID, and DeviceID were entered into the ASCII CSV file '2018-002-FA_SB_depnav.csv'.
    2. Python was used to parse HYPACK raw files for the FEI clock shot-instant messages within the first and last shot temporal limits and append them into a Pandas (version 0.25.1) dataframe containing columns for year, Julian day, hour, minute, second, microsecond, and Pandas datetime object. Similarly, the CSV version of the final MCS shot navigation ('2018-002-FA_MCS_shtnav.csv', available online at https://doi.org/10.5066/P91WP1RZ) was parsed to produce a dataframe with the same temporal limits containing columns for deployment longitude and latitude (static coordinates determined manually in previous operation), shot longitude and latitude, FFID, offset, year, Julian day, hour, minute, second, and Pandas datetime object. Offset is the distance in meters between the static deployment position and each shot position as calculated by pyproj (version 1.9.6) on the WGS84 ellipsoid. The offsets are nominal estimates and do not account for post-deployment drift of the sonobuoy.
    3. The dataframes produced in the previous operation were merged, using the Pandas merge "asof" module with the datetime object as the join key, to produce a dataframe retaining the deployment longitude and latitude, shot longitude and latitude, FFID, and offset columns from the MCS shot navigation input and the year, Julian day, hour, minute, second, microsecond, and Pandas datetime object columns from the FEI clock shot-instant input. Generally, the "nearest" direction argument was specified during the "asof" merge to simply match the rows of each dataframe containing the closest datetime objects. However, problems with the network time protocol sever software on the Geometrics acquisition computer during deployments SB1 - SB10 resulted in MCS SEG-D header times up to 7 seconds behind the FEI clock shot-instant times. In these instances, the "backwards" direction argument was specified during the "asof" merge in order to match rows so that those with earlier datetime objects in the MCS shot navigation dataframe were matched with those containing later datetime objects in the FEI clock shot-instant dataframe. New columns containing the sonobuoy name, associated MCS line name, SurveyID, VehicleID, and DeviceID were added to the resultant merged shot time dataframe and it was exported to an ASCII CSV file. Upon completing this processing step for all deployments, the shot time ASCII CSV files were concatenated into a single file, '2018-002-FA_SB_shtnav.csv', and a header line was inserted.
    4. The merged shot time dataframe was used along with the Obspy trace slice module to cut the continuously recorded sonobuoy record into an Obspy stream containing individual traces for each recorded shot. Iterating over the dataframe rows, Obspy was used to slice 15 second traces from the input record starting at each shot instant, create and populate a list of user defined SEG-Y header words (trace sequence number, ffid, trace id, trace within ffid, coordinate scalar, source x and y coordinates (shot positions in arcseconds), group x and y coordinates (static deployment position in arcseconds), offset (nominal distance between source and sonobuoy), coordinate units (2 = arcseconds), year, day, hour, minute, second, and time basis code (4 = UTC)), and write the resultant trace stream to a SEG-Y Rev. 1 formatted file (32-Bit IBM floating point).
    Date: Dec-2020 (process 3 of 6)
    PROCESS STEP 3:
    Shearwater Reveal was used to execute the following processing flow for sonobuoy records.
    1. Import read the SEG-Y traces, Detrend determined and removed any mean amplitude trend from the traces, Despike reduced large amplitude noise spikes, BandpassFilter applied a high pass filter to retain frequencies greater than 8 Hz, and Output wrote the processed traces to a new SEG-Y Rev. 1 formatted file (32-Bit IBM floating point). Each output SEG-Y file contains a textural file header similar to the example from sonobuoy SB01 included below.
    Example sonobuoy file SEG-Y Textural Header:
    C 1 U.S. GEOLOGICAL SURVEY COASTAL AND MARINE HAZARDS AND RESOURCES PROGRAM
    C 2 SURVEY_ID: 2018-002-FA AREA: US ATLANTIC MARGIN VESSEL: R/V HUGH R. SHARP
    C 3 YEAR: 2018 SONOBUOY NAME: SB01 MCS LINE NAME: MX01
    C 4
    C 5 ACQUISITION: UP TO 4 x 105 CU IN AIR GUNS, 30 METER SHOT INTERVAL,
    C 6 ULTRA ELECTRONICS AN/SSQ-53D(3) SONOBUOY, 1 MS RECORDING SAMPLE INTERVAL,
    C 7 CONTINUOUSLY RECORDED TO IRIS MINISEED FORMAT. SOURCE CHANGES THROUGHOUT
    C 8 WHILE TROUBLESHOOTING.
    C 9
    C10
    C11 PROCESSING: IMPORT AND CONCATENATE RAW MINISEED RECORDS, COMBINE
    C12 MCS SHOT NAVIGATION (SEE HTTPS://DOI.ORG/10.5066/P91WP1RZ) WITH
    C13 MICROSECOND RESOLUTION SHOT INSTANT TIMING FOR TEMPORAL RANGE OF INPUT
    C14 RECORD, SLICE 15 SECOND TRACES FROM THE INPUT AT EACH SHOT INSTANT,
    C15 COMPUTE NOMINAL OFFSET BETWEEN SHOT AND SONOBUOY DEPLOYMENT POSITIONS (IN
    C16 METERS), CONCATENATE TRACES TO OUTPUT SEG-Y FILE WITH HEADER INFORMATION,
    C17 DESPIKE TO REDUCE LARGE AMPLITUDE NOISE BURSTS, AND HIGH PASS FILTER
    C18 (> 8 Hz).
    C19
    C20
    C21 OUTPUT: 32-BIT IBM FLOATING POINT SEG-Y
    C22 RECORD LENGTH: 15 SEC
    C23
    C24 MCS SHOT (SRC) AND SONOBUOY DEPLOYMENT (GRP) COORDINATES ARE STORED IN
    C25 GEOGRAPHIC ARCSECONDS (SCALED BY 100). DIVIDE BY 360000 FOR DECIMAL
    C26 DEGREES. OFFSET BETWEEN SRC AND REC IN METERS IS NOMINAL
    C27
    C28 SRC-X AND SRC-Y IN BYTES 73-76 AND 77-80
    C29 GRP-X AND GRP-Y IN BYTES 81-84 AND 85-88
    C30 COORDINATE SCALAR IN BYTES 71-72
    C31 OFFSET IN BYTES 37-40
    C32
    C33
    C34
    C35
    C36 FOR ADDITIONAL INFORMATION CONCERNING THIS DATASET REFER TO THE ASSOCIATED
    C37 USGS SCIENCEBASE DATA RELEASE ONLINE AT:
    C38 HTTPS://DOI.ORG/10.5066/P97LBUSP
    C39
    C40
    Date: Dec-2020 (process 4 of 6)
    PROCESS STEP 4:
    The following flow was executed within a python notebook (FA2018002_SonobuoySQLdb.ipynb) to import sonobuoy deployment and shot data into a SpatiaLite (version 4.3.0) enabled SQLite (version 3.3.0) database.
    1. Pandas 'read_csv' imported data from the files '2018-002-FA_SB_depnav.csv' and '2018-002-FA_SB_shtnav.csv' into new dataframes containing the deployment and shot information, respectively. Pandas 'to_sql' created and populated SQL database tables from each dataframe.
    2. SQLite operations created ('AddGeometryColumn') and populated ('Update') point geometry columns in each of the new tables from the deployment and shot coordinates, respectively. Additionally, a new database table was created ('Create Table' and 'AddGeometryColumn') with a line string geometry column to contain tracklines generated ('Insert') from the shot point geometries for each deployment. The trackline database table was updated to include columns for the sonobuoy deployment name, image name, associated MCS line name, initial FFID, end FFID, Year, initial day and time, end day and time, SurveyID, VehicleID, DeviceID, and the line length in kilometers (calculated on the WGS84 ellipsoid).
    Date: Dec-2020 (process 5 of 6)
    PROCESS STEP 5:
    The sonobuoy deployment and shot points and shot trackline features were added (Add Data) into ArcGIS Pro (version 2.3.3) from the SQLite database, then exported (using the Feature Class to Feature Class geoprocessing tool) to the new Esri point and polyline shapefiles '2018-002-FA_SB_depnav.shp', '2018-002-FA_SB_shtnav.shp', and '2018-002-FA_SB_shtTracklines.shp', respectively.
    Date: Dec-2020 (process 6 of 6)
    PROCESS STEP 6:
    The Seismic Unix (version 4.3) script 'plot_sb' was used to read the processed SEG-Y files, balance the traces ('sugain' quantile clip and scale), and create variable density greyscale Postscript plots (using the Seismic Unix 'psimage' module) showing two-way travel time (seconds) along the y-axis (left margin) and along profile nominal offset (labeled at 1000 meter intervals) on the x-axis (along top of profile). The Postscript images were then converted to 200 dpi PNG formatted images using ImageMagick convert (version 6.9.10-78).
  3. What similar or related data should the user be aware of?
    Norris, M.W., and Faichney, A.K., 2002, SEG-Y rev. 1 Data Exchange Format - SEG Technical Standards Committee: Society of Exploration Geophysicists, Tulsa, OK.

    Online Links:

    Baldwin, Wayne, Foster, David, Bergeron, Emile, Ferro, Peter Dal, McKee, Jennifer, Moore, Eric, Nichols, Alex, O'Brien, Thomas, Powers, Dan, Miller, Nathaniel, and Ruppel, Carolyn, 2020, Multichannel Seismic-Reflection and Navigation Data Collected Using Sercel GI Guns and Geometrics GeoEel Digital Streamers During the Mid-Atlantic Resource Imaging Experiment (MATRIX), USGS Field Activity 2018-002-FA: data release DOI:10.5066/P91WP1RZ, U.S. Geological Survey, Coastal and Marine Hazards and Resources Program, Woods Hole Coastal and Marine Science Center, Woods Hole, Massachusetts.

    Online Links:

    Other_Citation_Details:
    Suggested citation: Baldwin, W.E., Foster, D.S., Bergeron, E.M., Dal Ferro, P., McKee, J.A., Moore, E.M., Nichols, A.R., O'Brien, T.F., Powers, D., Miller, N.C., and Ruppel, C.D., 2021, Multichannel seismic-reflection and navigation data collected using Sercel GI guns and Geometrics GeoEel digital streamers during the Mid-Atlantic Resource Imaging Experiment (MATRIX), USGS field activity 2018-002-FA: U.S. Geological Survey data release, https://doi.org/10.5066/P91WP1RZ
    Baldwin, Wayne E., Bergeron, Emile M., Foster, David S., Moore, Eric M., Nichols, Alex R., O'Brien, Tom F., Miller, Nathaniel C., and Ruppel, Carolyn D., 2021, Split-beam Echo Sounder and Navigation Data Collected Using a Simrad EK80 Wide Band Transceiver and ES38-10 Transducer During the Mid-Atlantic Resource Imaging Experiment (MATRIX), USGS Field Activity 2018-002-FA: data release DOI:10.5066/P948VJ4X, U.S. Geological Survey, Coastal and Marine Hazards and Resources Program, Woods Hole Coastal and Marine Science Center, Woods Hole, Massachusetts.

    Online Links:

    Other_Citation_Details:
    Suggested citation: Baldwin, W.E., Bergeron, E.M., Foster, D.S., Moore, E.M., Nichols, A.R., O'Brien, T.F., Miller, N.C., and Ruppel, C.D., 2021, Split-beam echo sounder and navigation data collected using a Simrad EK80 wide band transceiver and ES38-10 transducer during the Mid-Atlantic Resource Imaging Experiment (MATRIX), USGS field activity 2018-002-FA: U.S. Geological Survey data release, https://doi.org/10.5066/P948VJ4X.

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?
    Sonobuoy deployments and multichannel seismic-reflection shots were navigated using a Wide Area Augmentation System (WAAS) enabled Hemisphere R131 Differential GPS (DGPS) receiver, with the navigational reference point (NRP) antenna mounted on the 01 deck rail, approximately along the vessel centerline and 16.15 m from the stern of the R/V Hugh R. Sharp. The seismic sources were towed 47.8 m astern of the NRP off the port and starboard quarters. The Geometrics CNT-1 seismic acquisition software (version 5.361) logged shot times and navigation coordinates to SEG-D external headers. The tailbuoy trailing the streamer was also navigated using an Adafruit Ultimate GPS FeatherWing (WASS/DGPS) with data transmitted to the ship via a Feather M0 RFM95 LoRa Radio and logged using HYPACK (version 2018, 18.1.11.0). Processing descriptions provided below outline the procedures for calculating layback distances between the NRP and acoustic sources and the protocol used to account for towing feather angle. Offsets between the NRP and sonobuoy water entry positions were not accounted for. Although horizontal accuracy of WAAS enabled DGPS is estimated to be within 2-3 m, we assume the accuracy of the shot positions to be +/- 20 m due to layback offset between the NRP and sources and movement of the sources astern of the ship.
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
    Sonobuoys were deployed at variable intervals (generally between 5 and 17 km apart) along MATRIX MCS survey lines 2018-002-FA_MX01, 2018-002-FA_MX07, 2018-002-FA_MX09, 2018-002-FA_MX12, 2018-002-FA_MX13, 2018-002-FA_MX16, and 2018-002-FA_MX18 (see https://doi.org/10.5066/P91WP1RZ). The file '2018-002-FA_SB_shtnav.shp' contains navigation coordinates for all MCS shots recorded during the sonobuoy deployments. Hiatus in source operation and variability in source level (number of guns firing in the array) occurred periodically throughout the survey due to complications arising from source instrumentation issues (including triggering and airgun and compressor troubleshooting, maintenance, or repair), impacts from locally deployed fishing gear, mitigation of marine mammal encounters (power-downs, shut-downs, and ramp-ups), periods of inclement weather and sea state, and vessel equipment problems. The "Notes" column of the MATRIX MCS Line Note Log '2018-002-FA_StreamerConfig_InfoLogs.pdf'(available online at https://doi.org/10.5066/P91WP1RZ) outlines significant issues encountered during each line and the "MATRIX Number of Guns Log" documents changes in the source array throughout the survey.
  5. How consistent are the relationships among the observations, including topology?
    Quality control was conducted during processing to ensure consistency of SEG-Y data files with corresponding navigation ASCII CSV and shapefiles, and sonobuoy profile images. Seismic shots were recorded during 46 of the 63 sonobuoy deployments and SEG-Y data files and PNG profile images only exist for the 46 successful deployments. Failed deployments are identified in '2018-002-FA_SB_depnav.shp' by a "no image available" entry in the "SB_Image" column. All failed deployments were caused by the hydrophone being cut off during interaction with the seismic streamer. Amplitude clipping is present in most traces recorded for all deployments due to preamp gain settings during acquisition. Julian day dates, UTC times, multi-channel seismic (MCS) FFID numbers, and MCS shot navigation are consistent between corresponding sonobuoy records in '2018-002-FA_SB_Segy.zip' (SEG-Y headers do not preserve microsecond shot time resolution), '2018-002-FA_SB_shtnav.shp', and '2018-002-FA_SB_shtnav.csv'. Similarly, Julian day dates, UTC times, and sonobuoy deployment navigation are consistent between '2018-002-FA_SBsegy.zip', '2018-002-FA_SB_shtnav.shp', '2018-002-FA_SB_shtnav.csv', and '2018-002-FA_SB_depnav.shp'. The attribute fields 'SBName' and 'SB_Image' for each point feature in '2018-002-FA_SB_depnav.shp' and line feature in '2018-002-FA_SB_shtTracklines.shp' correspond to the SEG-Y data files in '2018-002-FA_SB_Segy.zip' and the PNG profile images in '2018-002-FA_SB_Images.zip', respectively.

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
    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 sonobuoy seismic and navigation data collected using Sercel GI guns and Ultra Electronics seismic sonobuoys during the Mid-Atlantic Resource Imaging Experiment (MATRIX), USGS field activity 2018-002-FA: includes '2018-002-FA_SB_depnav.shp' containing sonobuoy deployment locations, '2018-002-FA_SB_shtnav.shp' and '2018-002-FA_SB_shtnav.csv' containing point locations of MCS shots recorded by sonobuoys, '2018-002-FA_SB_shtTracklines.shp' containing trackline features created from recorded shots, the zip archive '2018-002-FA_SB_Images.zip' containing 46 sonobuoy profile PNG images, the zip archive '2018-002-FA_SB_SegyData' containing the processed sonobuoy traces in binary SEG-Y with source-receiver geometry and navigation in the headers, the browse graphic '2018-002-FA_SB_BrowseImage.jpg', and the Federal Geographic Data Committee (FGDC) Content Standards for Digital Geospatial Metadata (CSDGM) metadata file 2018-002-FA_SB_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 shapefiles, CSV files, PNG images, and/or SEG-Y seismic trace files.

Who wrote the metadata?

Dates:
Last modified: 19-Mar-2024
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)
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 20240319)
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_P97LBUSP/2018-002-FA_SB_meta.faq.html>
Generated by mp version 2.9.51 on Wed Jun 26 15:25:05 2024