Seismic Reflection, EdgeTech SB-424 chirp profile images collected within Lake Powell, UT-AZ during USGS field activity 2017-049-FA (PNG images).

PROCESS STEP 1: SIOSEIS (version 2015.3.1), OpenCPS (version 3.3.0), 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) OpenCPS 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 12N 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 OpenCPS 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 "*.sht-raw.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 (-2.8 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 1.35 ms to account for the approximate 1 m tow depth of the SB-424 (the sound speed of 1480 m/s, a typical value observed from SVP profiles during the survey, was used to convert the depth in meters to 2-way travel time in ms). 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 12 N coordinates (WGS 84) using Proj (version 4.6.0). 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 424toSQL17049.py, written by Wayne Baldwin, which imported the CSV files to a Spatialite (version 4.3.0) enabled SQLite (version 3.21.0) database, creating two tables containing point geometries for the unique and 500 shot interval navigation.
4) The Seismic Unix script Plot424 creates 12-inch-high variable density plots of the seismic profiles, which are converted to PNG format using ImageMagick (version 6.9.5-4). Images show two-way travel time (seconds) along the y-axis (left margin) and shots along profile (labeled at 500 shot intervals) on the x-axis (along top of profile).

Added keywords section with USGS persistent identifier as theme keyword.