Archive of Chirp Subbottom Profile, Imagery, and Geospatial Data Collected in June 2022 Near Panama City, Florida

Chirp Acquisition - Subbottom data were acquired from one survey platform, an Edgetech 3400 Portable Subbottom Profiler, which was towed by the 26-foot research vessel, the R/V Sallenger. 234 lines, equivalent to a total of 415.71 line-kilometers, were surveyed. The seismic source utilized during 2022-312-FA consisted of an EdgeTech 3400 towfish running DISCOVER version 4.09 acquisition software and towed on the port side of the vessel, approximately 3 m across-track from the IANS reference point. The data were acquired in J-STAR standard format (JSF) and SEG-Y formats at 5 hertz (Hz), which equates to a 0.20 s sample interval, using a frequency sweep of 3-8 kilohertz (kHz) and 3-16 kHz, pulse length of 20 ms, and recording length was approximately 47.34 ms. Based on survey speeds of 3.5-4.5 knots, the shot spacing was approximately 0.450 m. The binary portion of the seismic data provided in this publication (Forde and others, 2023) is stored in SEG-Y rev. 0, IBM 32-bit float [big-endian byte order] format, which is a standard digital format that can be read and manipulated by most seismic processing software packages; the first 3,200 bytes of the file header are in American Standard Code for Information Interchange (ASCII) format instead of Extended Binary Coded Decimal Interchange Code (EBCDIC) format. The SEG-Y formatted trace files have a .sgy extension and may be downloaded and processed with commercial or public domain software such as Seismic Unix (SU) (Cohen and Stockwell, 2010). The printable profiles provided are chirp subbottom profile images that were processed using SU software. Survey Field Activity Collection System (FACS) logs, geophysical logs, and acquisition geometry are also provided as supplemental information in the download file, 2022-312-FA_logs.zip (Forde and others, 2023).

Chirp processing - The EdgeTech 3400 dual frequency system recorded the subbottom data in JSF and SEG-Y rev. 1 formats. SEGY data were saved (with alternating pings supplied by each transducer) as separate files for the 3-8 kHz and 3-16 kHz frequencies. 3-8 kHz data have “A” appended to the end of the file name, for example, 2022_312_FA_001bA.sgy. The raw JSF and SEG-Y data are not provided in this data release (Forde and others, 2023) but are available on request. Using the jsf2segy software package (https://github.com/Geosvy/jsf2segy), JSF files were converted to analytic and envelope SEG-Y traces. The envelope SEG-Y files are comprised of the combined frequency data. This step was performed to make the data more accessible for users and reduce the quantity and total size of files being provided in this publication. The envelope SEG-Y data were processed with Seismic Unix (Release 44) software to produce gained Graphics Interchange Format (GIF) images of the subbottom profiles included in this data release. A representative chirp data processing sequence consisted of (1) creating the envelope seismic data file from the analytic data (envelope converted files included in this publication have "_env" appended to the line name), (2) removing raw [vessel] navigation data for each shot and converting the SEG-Y file to SU format, (3) applying automatic gain control, (4) trimming the trace data TWT to 30 ms (no observable features, aside from multiples, were encountered below that point in the profiles), (5) generating a PostScript image of the traces, and (6) converting the PostScript image to a GIF image.

Navigation acquisition and processing - An Applanix Pos MV Wavemaster II V5 IANS with two GA830 GNSS antennas (positioned amidships) and an associated IMU was used for positioning onboard the R/V Sallenger. Real-time positions from the Applanix system were recorded and written to the seismic trace headers via a RS232 cable running from the Applanix receiver to the topside unit of the chirp system every 0.20 seconds with unique coordinate fixes being recorded every second. During subbottom processing, location data were extracted from the SEG-Y headers of the processed chirp profiles, using Seismic Unix (Cohen and Stockwell, 2010) software and output as ASCII text files; PROJ.5.1.0 (https://proj.org/) software was used to project WGS84 latitude and longitude coordinates to Universal Transverse Mercator (UTM) northings and eastings (WGS84, Zone 16 North [N], meters). Navigation files for each subbottom line, saved by line number, were concatenated into comma-delimited text files so they could be represented geospatially using Esri ArcGIS software. The final output files are as follows: (1) 2022-312-FA_nav.csv contains unique shotpoint positions (along each line) for the entire survey, (2) 2022-312-FA_1000sht.csv includes the 1,000-shot-interval locations that were generated to correlate shot locations on the trackline map with evenly spaced 1,000-shot index markers along the top of the printable profile images, and (3) 2022-312-FA_sol.csv has the start-of-line locations for each trackline. The concatenated, comma-delimited text files were later imported into ArcMap and saved as either a point or polyline file (in Esri's shapefile format) for use in the map document (.mxd) included in this archive (Forde and others, 2023).

Trackline map creation - 2022-312-FA_location.mxd and associated shapefiles (.shp) were created with Esri ArcMap 10.8.2 software. The survey navigation file, 2022-312-FA_nav.csv, was imported into ArcMap and processed using the ArcScript "Points to Line" to create a polyline shapefile of the cruise tracklines called 2022-312-FA_trkln.shp. The 1,000-shot-interval and start-of-line files, 2022-312-FA_1000sht.csv and 2022-312-FA_sol.csv, were imported into ArcMap and saved as point shapefiles. A non-proprietary version of the location map was created by utilizing the ArcToolbox "Map to KML" tool, which converted each layer included in the map document (.mxd) to keyhole markup language (.kml) format prior to them being compressed (zipped) and saved as a .kmz file. The ArcGIS and Google Earth geospatial files provided in this publication are unprojected (geographic coordinates, WGS84). For detailed information about the GIS files provided in Forde and others (2023), please refer to the individual metadata records (*_metadata.txt and *.shp.xml) accompanying each shapefile and the readme file included in 2022-312-FA_gis.zip (Forde and others, 2023).