Archive of Chirp Subbottom Profile, Imagery, and Geospatial Data Collected in May 2023 from Oahu, Hawaii

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

Frequently anticipated questions:


What does this data set describe?

Title:
Archive of Chirp Subbottom Profile, Imagery, and Geospatial Data Collected in May 2023 from Oahu, Hawaii
Abstract:
As part of the Coastal Sediment Availability and Flux and Defense Advanced Research Protection Agency (DARPA) Reefense projects, scientists from the U.S. Geological Survey (USGS) St. Petersburg Coastal and Marine Science Center (SPCMSC) conducted a nearshore geophysical survey to map the shoreface and inner shelf, as well as characterizing stratigraphy near Oahu, Hawaii (HI) May 7-13, 2023. The purpose of this study was to conduct a geologic assessment (including bathymetric mapping) near Fort Hase Beach, Oahu, in support of efforts to construct an artificial coral reef offshore of Marine Corps Base Hawaii (MCBH). This publication serves as an archive of high-resolution chirp subbottom trace data, survey trackline map, navigation files, geographic information system (GIS) data, and formal Federal Geographic Data Committee (FGDC) Content Standard for Digital Geospatial Metadata (CSDGM). Processed subbottom profile images are also provided. The archived trace data are in standard Society of Exploration Geophysicists (SEG) SEG-Y revision 1 format (Norris and others, 2002). In addition to this data release, the SEG-Y files can be downloaded from the USGS Coastal and Marine Geoscience Data System (CMGDS) at, https://cmgds.marine.usgs.gov.
Supplemental_Information:
Chirp systems use a signal of continuously varying frequency; the system used during this survey produces high-resolution, shallow-penetration (typically less than 75-milliseconds [ms]) profile images of sub-seafloor stratigraphy. The towfish contains a transducer that transmits and receives acoustic energy and is typically towed 1–2 meters (m) below the sea's surface. As transmitted acoustic energy intersects density boundaries, such as the seafloor or sub-surface sediment layers, energy is reflected toward the transducer, received, and recorded by a PC-based seismic acquisition system. This process is repeated at regular intervals (for example, 0.125 seconds [s]) and returned energy is recorded for a specific duration (for example, 50 ms). In this way, a two-dimensional (2D) image of the shallow geologic structure beneath the towfish is produced.
  1. How might this data set be cited?
    Forde, Arnell S., 20240129, Archive of Chirp Subbottom Profile, Imagery, and Geospatial Data Collected in May 2023 from Oahu, Hawaii:.

    This is part of the following larger work.

    Forde, Arnell S., Wei, Emily A., and Stalk, Chelsea A., 20240129, Archive of Chirp Subbottom Profile Data Collected in 2023 From Oahu, Hawaii: U.S. Geological Survey data release doi:10.5066/P9I2T4ZE, U.S. Geological Survey - St. Petersburg Coastal and Marine Science Center, St. Petersburg, Florida.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -157.795000
    East_Bounding_Coordinate: -157.724867
    North_Bounding_Coordinate: 21.446094
    South_Bounding_Coordinate: 21.409567
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 07-May-2023
    Ending_Date: 13-May-2023
    Currentness_Reference:
    ground condition
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: SEG-Y, tabular, vector, and raster digital data
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
      This is a Point 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.0198168345. Longitudes are given to the nearest 0.0211353562. 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.257223563.
  7. How does the data set describe geographic features?
    2023-310-FA_nav.csv (35071 data records), 2023-310-FA_1000sht.csv (136 data records), 2023-310-FA_sol.csv (81 data records).
    These files, which are located in 2023-310-FA_nav.zip (Forde and others, 2023), represent the May 2023 subbottom navigation data. The attributes described below are for the survey's shotpoint navigation file, 2023-310-FA_nav.csv., which contains all the unique shot navigation fixes including the minimum and maximum range of values. 2023-310-FA_1000sht.csv represents the 1000th shot interval and has the same attribute definitions as the shot navigation but different ranges of values not represented here. Not all lines have a record, since some of the data are less than 1000 shots. 2023-310-FA_sol represents the navigation fix for the start of each seismic line and also with the same attribute definition as the survey navigation – but different ranges of values not represented here. For detailed information specific to the ArcGIS data, please see the associated shapefile metadata. (Source: U.S. Geological Survey)
    UTMX
    UTM-X coordinate (Zone 4N) (Source: Universal Transverse Mercator Coordinate System)
    Range of values
    Minimum:624877.207
    Maximum:632135.187
    Units:meters
    UTMY
    UTM-Y coordinate (Zone 4N) (Source: Universal Transverse Mercator Coordinate System)
    Range of values
    Minimum:2368011.318
    Maximum:2372055.082
    Units:meters
    Line
    Trackline name (Source: U.S. Geological Survey) Line numbers were assigned by the EdgeTech 424 chirp topside unit during data acquisition and are composed of an alphanumeric identifier and trackline number. The naming convention used for each subbottom line is as follows: xy_line#, where 'x' represents a partial FAN, 'y' denotes the survey area, which is either Marine Corps Base Hawaii (MCBH) or Marine Corps Base Hawaii Coconut Island (MCBH_CI), and 'line#' is the trackline number (for example, 2023_310_MCBH_CI_line01 and 2023_310_MCBH_line01). If recording was prematurely terminated or reran, due to quality or acquisition issues, characters (specifically "a" or "b") or sequentially increasing numbers (such as .001, .002, etc.), were manually appended to the trackline name.
    Shot
    Shotpoint number (Source: U.S. Geological Survey)
    Range of values
    Minimum:1
    Maximum:5997
    Lon
    Longitude (decimal degrees) (Source: World Geodetic System 1984 Geographic Coordinate System)
    Range of values
    Minimum:-157.795000
    Maximum:-157.724867
    Units:decimal degrees
    Lat
    Latitude (decimal degrees) (Source: World Geodetic System 1984 Geographic Coordinate System)
    Range of values
    Minimum:21.409567
    Maximum:21.446094
    Units:decimal degrees
    YEAR
    Year of data acquisition (Source: U.S. Geological Survey)
    Range of values
    Minimum:2023
    Maximum:2023
    DOY:HR:MIN:SEC
    Day of year:hour:minute:second (Source: U.S. Geological Survey) Day of year, hour, minute and second of data acquisition, in Coordinated Universal Time (UTC).
    Entity_and_Attribute_Overview:
    Navigation file: Navigation files are available as ASCII delimited text files in comma-separated values file format. The final navigation files are provided in 2023-310-FA_nav.zip (Forde and others, 2023) and represent the reprojected survey shotpoint navigation, 1,000-shot-interval locations, and start of line files.
    Entity_and_Attribute_Overview:
    Binary data file: Seismic trace data are available as binary files in SEG-Y format (81 files). These files have a .sgy extension and range in size from 1.4 to 57 megabytes. These data are included in the download file, 2023-310-FA_segy.zip (Forde and others, 2023), and can also be found by going to the USGS CMGDS at, https://cmgds.marine.usgs.gov. The SEG-Y rev. 1 format (Norris and others, 2002) data presented here consists of the following: a 3,600-byte reel identification header, with the first 3,200 bytes consisting of an ASCII header block followed by a 400-byte binary header block, both of which include information specific to line and reel number; a trace data block that follows the reel identification header, with the first 240 bytes of each trace block consisting of the binary trace identification header; and seismic data samples that follow the trace identification header.
    Entity_and_Attribute_Overview:
    Graphic image file: Printable versions of the processed subbottom profiles are available as GIF images (81 files) and are included in the download file, 2023-310-FA_seisimag.zip (Forde and others, 2023).
    Entity_and_Attribute_Overview:
    GIS file: The GIS data associated with this survey are provided in Forde and others (2023) as a compressed zip file, 2023-310-FA_gis.zip, which is composed of an Esri map document, shapefiles, individual shapefile metadata, a Google Earth Keyhole Markup Language Zipped (KMZ) file, a folder of processed subbottom profile images, and a readme file.
    Entity_and_Attribute_Detail_Citation:
    The entity and attribute information were generated by the individual and/or agency identified as the originator of the dataset. Please review the rest of the metadata record for additional details and information.

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Arnell S. Forde
  2. Who also contributed to the data set?
    Funding and (or) support for this study were provided by DARPA and the USGS Coastal and Marine Hazards and Resources Program. The authors thank Captain Joe Reich of Alyce C Sportfishing for his assistance in data collection and piloting the contracted Research Vessel (R/V) Alyce C. The authors would also like to thank Jessica Jimenez-Buscat, Lance Bookless, Jason Bowlen, Mark Edmonson, and Meagan Ostrem at Marine Corps Base Hawaii for their help coordinating base access and survey logistics. Finally, the authors wish to thank Ben Jones, Joshua Levy, Zhenhua Huang, and Robert Toonen at the University of Hawaii for help with survey planning, logistics, and coordination efforts. This document was improved by scientific/editorial and metadata reviews from VeeAnn Cross and Breanna Williams of the Woods Hole and St. Petersburg Coastal and Marine Science Centers, respectively.
  3. To whom should users address questions about the data?
    Arnell S. Forde
    U.S. Geological Survey
    Geologist
    600 4th Street South
    Saint Petersburg, FL
    USA

    (727) 502-8000 (voice)
    aforde@usgs.gov

Why was the data set created?

The purpose of this data release is to archive digital chirp subbottom profile data and associated files collected during USGS Field Activity Number 2023-310-FA. Additional survey and data details are available from the USGS CMGDS at, https://cmgds.marine.usgs.gov/fan_info.php?fan=2023-310-FA.

How was the data set created?

  1. From what previous works were the data drawn?
  2. How were the data generated, processed, and modified?
    Date: 13-May-2023 (process 1 of 4)
    Chirp acquisition - Subbottom data were acquired from one survey platform, an Edgetech 424 Portable Subbottom Profiler, which was towed on the port side of the 26-foot research vessel, the R/V Alyce C. 84 lines, equivalent to a total of 110.16 line-kilometers, were surveyed. The seismic source utilized during 2023-310-FA consisted of an EdgeTech 424 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 at 5 hertz (Hz), which equates to 0.20 pings per second. The frequency sweep was 4-20 kilohertz (kHz), pulse lengths ranged between 5 ms and 10 ms, and recording length was approximately 53.2 ms. Based on survey speeds of 3.5-4.5 knots, the shot spacing was roughly 0.450 m. During acquisition, positions from the POS MV IANS were recorded and written to the seismic trace headers in arcseconds every 0.2 s. The binary portion of the seismic data provided in this publication (Forde and others, 2023) is stored in SEG-Y rev. 1, 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 ASCII format instead of Extended Binary Coded Decimal Interchange Code (EBCDIC) format. The SEG-Y formatted envelope 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 in .gif format) are chirp subbottom profile images that were processed using SU software. Survey Field Activity Collection System (FACS) logs, geophysical logs, and acquisition geometry figure are also provided as supplemental information in the download file, 2023-310-FA_logs.zip (Forde and others, 2023). Person who carried out this activity:
    Emily A. Wei
    U.S. Geological Survey
    Research Geologist
    600 4th Street South
    St. Petersburg, FL

    (727) 502-8000 (voice)
    ewei@usgs.gov
    Date: 07-Aug-2023 (process 2 of 4)
    Chirp processing and image creation - The EdgeTech 424 chirp system recorded the subbottom data in JSF and SEG-Y rev. 1 formats. Enveloped SEG-Y trace data were processed with custom scripts and SU Release 44 (Cohen and Stockwell, 2010) software to produce gained Graphics Interchange Format (GIF) images of the subbottom profiles included in Forde and others (2023). A representative chirp data processing sequence consisted of (1) removing raw [vessel] navigation data for each shot and converting the SEG-Y file to SU format, (2) applying automatic gain control, (3) trimming the trace data TWT to 30 ms (no observable features, aside from multiples, were encountered below that point in the profiles), (4) generating a PostScript image of the traces, and (5) converting the PostScript image to a GIF image. The subbottom profile images have tic marks every 200 shots, with labels, larger tic marks, and dashed grid lines every 1000 shots. Not all lines have 1000 shots or more, see the logical consistency report for additional details. Person who carried out this activity:
    Arnell S. Forde
    U.S. Geological Survey
    Geologist
    600 4th Street South
    St. Petersburg, FL

    (727) 502-8000 (voice)
    aforde@usgs.gov
    Data sources used in this process:
    • *.sgy
    Data sources produced in this process:
    • *.gif
    Date: 07-Aug-2023 (process 3 of 4)
    Navigation acquisition and processing - A Norbit Winghead MBES system with an integrated Applanix Pos MV Wavemaster II V5 IANS with two AeroAntenna Technology (AT16575-540Ts-TNCF-000-RG-45_NM-R) GNSS antennas (positioned forward-aft near the aft-starboard of the vessel) and an associated IMU were used for positioning onboard the R/V Alyce C. Real-time positions from the Applanix system were recorded and written to the seismic trace headers via a RS232 cable running from the Norbit topside unit to the topside unit of the chirp system every 0.20 seconds, with unique navigation fixes being recorded every second. During subbottom processing, location data were extracted from the SEG-Y headers of the processed chirp profiles, using bespoke scripts and 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 4 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) 2023-310-FA_nav.csv contains unique shotpoint positions (along each line) for the entire survey – roughly every 5 shots, (2) 2023-310-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) 2023-310-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). Person who carried out this activity:
    Arnell S. Forde
    U.S. Geological Survey
    Geologist
    600 4th Street South
    St. Petersburg, FL

    (727) 502-8000 (voice)
    aforde@usgs.gov
    Data sources used in this process:
    • *.txt
    Data sources produced in this process:
    • 2023-310-FA_nav.csv
    • 2023-310-FA_1000sht.csv
    • 2023-310-FA_sol.csv
    Date: 10-Oct-2023 (process 4 of 4)
    Trackline map creation - 2023-310-FA_location.mxd and associated shapefiles (.shp) were created with Esri ArcMap 10.8.2 software. The survey navigation file, 2023-310-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 2023-310-FA_trkln.shp. The 1,000-shot-interval and start-of-line files, 2023-310-FA_1000sht.csv and 2023-310-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 Forde and others (2023) are unprojected (geographic coordinates, WGS84). For detailed information about the GIS files provided in this data release, please refer to the individual metadata records (*_metadata.txt and *.shp.xml) accompanying each shapefile and the readme file included in 2023-310-FA_gis.zip (Forde and others, 2023). Person who carried out this activity:
    Arnell S. Forde
    U.S. Geological Survey
    Geologist
    600 4th Street South
    St. Petersburg, FL

    (727) 502-8000 (voice)
    aforde@usgs.gov
    Data sources used in this process:
    • 2023-310-FA_nav.csv
    • 2023-310-FA_1000sht.csv
    • 2023-310-FA_sol.csv
    Data sources produced in this process:
    • 2023-310-FA_trkln.shp
    • 2023-310-FA_shots.shp
    • 2023-310-FA_sol.shp
    • 2023-310-FA.kmz
  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: Society of Exploration Geophysicists, SEG Technical Standards Committee Release 1.0, May 2002.

    Online Links:

    Cohen, J.K., and Stockwell, J.W., Jr., 2010, Seismic Un*x Release No. 44: An open source software package for seismic research and processing: Center for Wave Phenomena, Colorado School of Mines, Golden, Colorado.

    Online Links:


How reliable are the data; what problems remain in the data set?

  1. How well have the observations been checked?
    The validity or accuracy of marine subbottom profiles is highly qualitative and dependent on equipment and operating condition variables.
  2. How accurate are the geographic locations?
    As the subbottom profile data were acquired, the position of the vessel was continuously determined by an Applanix POS MV Wavemaster II inertial aided navigation system (IANS) integrated into the Norbit Winghead MBES, which is accurate to within 0.5-2 meters (m). To ensure consistent spacing between survey lines acquired aboard the R/V Alyce C, pre-determined trackline locations were imported into HYPACK 2021 navigation software and followed during seismic data collection. During acquisition, positions from the POS MV IANS were recorded and written to the seismic trace headers in arcseconds every 0.2 s and were subsequently converted to decimal degrees latitude and longitude coordinates (World Geodetic System of 1984, WGS84, realization G1150). The approximate 3-m offset between the chirp shot position and the vessel's IANS reference point of the Applanix system, the Inertial Measurement Unit (IMU), were not accounted for during acquisition, nor have the American Standard Code for Information Interchange (ASCII) navigation files and trackline map been corrected to reflect the offset.
  3. How accurate are the heights or depths?
    These data are not to be used for bathymetry or navigation. Two-way travel times (TWT) shown on the printable profile images are relative to the chirp towfish position (below the sea surface), not to the sea surface.
  4. Where are the gaps in the data? What is missing?
    A total of 84 seismic lines were collected during this field activity. Three lines were excluded from this data release (Forde and others 2023), due to equipment or acquisition issues, resulting in unusable data. More detail on acquisition conditions is available from the Excel spreadsheet 2023-310-FA_MBES_CHIRP_OPS_LOG.xlsx contained in 2023-310-FA_logs.zip (Forde and others, 2023). Please note, this log includes information about all data acquired during this field activity and is not limited to the data included in this seismic data release.
  5. How consistent are the relationships among the observations, including topology?
    These datasets are from one field activity with consistent instrument calibrations. No seismic reflection data were collected on DOY 128 (May 8, 2023) or 129 (May 9, 2023). Subbottom profiles that have less than 1000 shots recorded to their trace headers will not have a corresponding 1000-shot-interval shot file in 2023-310-FA_1000sht.csv, which is included in 2023-310-FA_nav.zip (Forde and others, 2023).

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?
Access_Constraints None. These data are held in the public domain.
Use_Constraints Public domain data from the U.S. Government are freely redistributable with proper metadata and source attribution. The U.S. Geological Survey requests to be acknowledged as originator of the data in future products or derivative research.
  1. Who distributes the data set? (Distributor 1 of 1)
    Arnell S. Forde
    U.S. Geological Survey
    Geologist
    600 4th Street South
    St. Petersburg, FL
    USA

    (727) 502-8000 (voice)
    aforde@usgs.gov
    Contact_Instructions:
    The SEG-Y files included in Forde and others (2023) are also downloadable from the Coastal and Marine Geoscience Data System at, https://cmgds.marine.usgs.gov.
  2. What's the catalog number I need to order this data set?
  3. What legal disclaimers am I supposed to read?
    This publication was prepared by an agency of the United States Government. Although these data were processed successfully on a computer system at the U.S. Geological Survey, no warranty expressed or implied is made regarding the display or utility of the data on any other system, nor shall the act of distribution imply any such warranty. The U.S. Geological Survey shall not be held liable for improper or incorrect use of the data described and (or) contained herein. Reference herein to any specific commercial product, process, or service by trade name, trademark, manufacturer, or otherwise does not constitute or imply its endorsement, recommendation, or favoring by the United States Government or any agency thereof.
  4. How can I download or order the data?
  5. What hardware or software do I need in order to use the data set?
    Use of SEG-Y data requires specialized seismic processing software, such as public domain software Seismic Unix (https://github.com/JohnWStockwellJr/SeisUnix).

Who wrote the metadata?

Dates:
Last modified: 29-Jan-2024
Metadata author:
Arnell S. Forde
U.S. Geological Survey
Geologist
600 4th Street South
St. Petersburg, FL
USA

(727) 502-8000 (voice)
aforde@usgs.gov
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)

This page is <https://cmgds.marine.usgs.gov/catalog/spcmsc/2023-310-FA_metadata.faq.html>
Generated by mp version 2.9.51 on Mon Jan 29 13:19:16 2024