Originator: U.S. Geological Survey
Publication_Date: unpublished material
Title: SB-424 trackline data
Geospatial_Data_Presentation_Form: vector digital data
Source_Citation_Abbreviation: SEG-Y SB-424 data
Source_Currentness_Reference: ground condition
Chirp seismic data were collected using an EdgeTech 3100 portable sub-bottom profiling system and an SB-424 towfish (4-24 kHz), which was towed from a port side davit on the R/V Rafael with the transducer approximately 2 m below the water line, and 8.5 meters astern of the DGPS antenna mounted atop the port side of the cabin. Chesapeake Technology SonarWiz (version 6.05.0011) seismic acquisition software was used to control the 3100 topside unit, digitally log trace data in the SEG-Y Rev. 1 format (IEEE floating point), and record GPS navigation coordinates to the SEG-Y trace headers (in arc seconds of Latitude and Longitude, multiplied by a scalar of 360000). Data were acquired using a 250 milliseconds (ms) shot rate, a 5-ms pulse length, and a 4 to 24 kHz frequency sweep at 30 to 50 percent power. Traces were recorded with a 23-microsecond sample interval over lengths of approximately 100 ms.
PROCESS STEP 1:
SIOSEIS (version 2015.3.1), Shearwater Reveal (version 4.1-01-31-2018), and Seismic Unix (version 4.2) were used to process SEG-Y data, create navigation files, and plot images. The processing flow and scripts used to produce navigation files including trackline shapefiles are summarized below and in the following processing steps.
1) SIOSEIS was used to read the raw SEG-Y files, extract the envelope-detected trace, renumber shots starting from one, and write out new SEG-Y files.
2) Reveal was use to run the following flows:
A) read_segy.flow - SegyTapeRead read the traces. HeaderMath and UTMLatLong were used to convert the source lat/lon positions from seconds of arc to decimal degrees, project them to UTM Zone 16N WGS 84 meters, and write each to new header words (NRP_LAT, NRP_LON, NRP_X, and NRP_Y). DBWrite wrote the UTM positions for the first channel of each FFID to an internal Reveal database table. Finally, Output wrote the traces to a new file "*.sht-raw.seis" in the internal OpenCPS format.
B) layback_shift.flow - Input read the "*.seis" file and sorted the traces to FFID/CHANNEL. The custom Python module ShotlineLayback (developed by Nathan Miller of USGS-WHCMSC) was used to define the measured horizontal offset between the DGPS antenna and the SB-424 transducer (-8.5 m). The algorithm interpolated a sail line from the source shot positions (NRP_X and NRP_Y), then computed layback positions for the SB-424 shots by translating them back along the sail by the measured offset. ApplyStatic was used to shift the traces down by 2.7 ms to account for the approximate 2 m tow depth of the SB-424 (the sound speed of 1500 m/s. Output wrote the shifted traces to a new SEG-Y files in which the trace header words SRC_X, SRC_Y represent the calculated layback coordinates, and REC_X, REC_Y maintain the original DGPS coordinates.
3) The SIOSEIS script read424 was used to read layback and static corrected SEG-Y files, write a Seismic Unix file, and extract SEG-Y trace header information, including shot number, pre-layback and layback longitude and latitude, year, Julian day, and time of day (UTC). Header information from each SEG-Y file was saved to text files after an AWK (no version) filter was used to maintain the first and last shots, shots at multiples of 100, 500, and shots with unique navigation coordinates. Geographic coordinates (WGS 84) were converted to UTM zone 16 N coordinates (WGS 84) using Proj (version 4.9.3). End shots and shots at multiples of 100 may not have unique navigation coordinates. Separate text files containing the first and last shots and even 500 shot intervals were also saved. A 500 shot interval was chosen because it corresponds to the annotation interval provided along the top of the seismic-reflection profile images. Read424 called a Python script 424inlbtoSQL18043.py, written by Wayne Baldwin (USGS-WHCMSC), which imported the CSV files to a Spatialite (version 4.3.0) enabled SQLite (version 3) database, creating two tables containing point geometries for the unique and 500 shot interval navigation. The script also created line geometries from the unique navigation (sorted by LineName and Shot) and wrote them to an additional database table. The tracklines are based on all the shot navigation.
These process steps and all subsequent process steps were conducted by the same person - David Foster.
Contact_Organization: U.S. Geological Survey
Contact_Person: David S. Foster
Address_Type: mailing and physical address
Contact_Voice_Telephone: (508) 548-8700 x2271
Contact_Facsimile_Telephone: (508) 457-2310
Address: 384 Woods Hole Rd.
City: Woods Hole
PROCESS STEP 2:
The SB-424 trackline features were added (Add Data) into ArcMap (version 10.3.1) from the SQLite database, then exported (Right click on database feature class >Data> Export Data) to the new Esri polyline shapefile 2018-043-FA_Edgetech424_Tracklines.shp