Archive of Chirp Subbottom Profile Data Collected in June 2018 From Fire Island, New York

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

Frequently anticipated questions:


What does this data set describe?

Title:
Archive of Chirp Subbottom Profile Data Collected in June 2018 From Fire Island, New York
Abstract:
Researchers from the U.S. Geological Survey (USGS) conducted a long-term, coastal morphologic-change study at Fire Island, New York, prior to and after Hurricane Sandy impacted the area in October 2012. The Fire Island Coastal System Change project (https://coastal.er.usgs.gov/fire-island/) objectives include understanding the morphologic evolution of the barrier island system on a variety of time scales (months to centuries) and resolving storm-related impacts, post-storm beach response, and recovery. From June 2-16, 2018, scientists from the USGS St. Petersburg Coastal and Marine Science Center conducted geophysical surveys on Fire Island to characterize and quantify spatial variability in the subaerial geology with the goal of subsequently integrating onshore geology with other surf zone and nearshore datasets. This publication serves as an archive of high-resolution subbottom profile images, survey trackline map, navigation files, geographic information system (GIS) data, and formal Federal Geographic Data Committee (FGDC) metadata. Additionally, in April 2016, geophysical and sediment sampling data were collected as part of the Fire Island project. The ground penetrating radar and vibracore datasets are available from Forde and others, 2018; Buster and others, 2018; and Bernier and others, 2018.
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) vertical image of the shallow geologic structure beneath the towfish is produced. The seismic source utilized during 2018-322-FA consisted of an EdgeTech SB-512i towfish running Discover version 4.09 acquisition software, towed by the research vessel (R/V) Sallenger, approximately 20 m behind the global positioning system (GPS) reference point. The data were acquired using a frequency sweep between 0.5 and 12 kilohertz (kHz), a 43 kHz sample frequency, and recording length was approximately 66.5 ms. Based on survey speeds of 3.5-4.5 knots, the shot spacing was approximately 0.450 m. The printable profiles provided are chirp subbottom profile images that were processed using Seismic Unix (SU) software. Survey Field Activity Collection System (FACS) and geophysical logs are also provided as supplemental information in the download file, 2018-322-FA_logs.zip.
  1. How might this data set be cited?
    Forde, Arnell S., DeWitt, Nancy T., Fredericks, Jake J., and Miselis, Jennifer L., 20190226, Archive of Chirp Subbottom Profile Data Collected in June 2018 From Fire Island, New York: U.S. Geological Survey Data Release doi:10.5066/P9Q8TVHH, 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: -73.323953
    East_Bounding_Coordinate: -72.858925
    North_Bounding_Coordinate: 40.729458
    South_Bounding_Coordinate: 40.607681
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 02-Jun-2018
    Ending_Date: 16-Jun-2018
    Currentness_Reference:
    ground condition
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: multimedia presentation
  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.0197884765. Longitudes are given to the nearest 0.0227336944. Latitude and longitude values are specified in Decimal Degrees. The horizontal datum used is World Geodetic System of 1984.
      The ellipsoid used is WGS 1984.
      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?
    2018-322-FA.txt, s2018-322-FA.txt, 2018-322-FA_s.txt
    Survey shotpoint navigation files in ASCII text format. (Source: SEG Y headers, https://seg.org/Publications/tech-stand.)
    UTMX
    UTM-X coordinate (Zone 18) (Source: Universal Transverse Mercator Coordinate System)
    Range of values
    Minimum:641742.084
    Maximum:680861.002
    Units:meters
    UTMY
    UTM-Y coordinate (Zone 18) (Source: Universal Transverse Mercator Coordinate System)
    Range of values
    Minimum:4496740.789
    Maximum:4510905.548
    Units:meters
    Line
    Trackline number (Source: U.S. Geological Survey) The naming convention used for each subbottom line is as follows: x_env_bp, where 'x' is a 1- or 2-digit number representing a specific trackline and '_env_bp' means that the seismic data were bandpass filtered then output as envelope data files. If recording was prematurely terminated, reran for quality or acquisition problems, or exceeded the file size limit/maximum shotpoint number (as determined by the acquisition software, Discover v. 4.09) the filename was appended with sequentially increasing numbers such as .001, .002, etc.
    Shot
    Shotpoint number (Source: U.S. Geological Survey)
    Range of values
    Minimum:1
    Maximum:27566
    Lon
    Longitude (decimal degrees) (Source: World Geodetic System of 1984 Geographic Coordinate System)
    Range of values
    Minimum:-73.323953
    Maximum:-72.858925
    Units:decimal degrees
    Lat
    Latitude (decimal degrees) (Source: World Geodetic System of 1984 Geographic Coordinate System)
    Range of values
    Minimum:40.607681
    Maximum:40.729458
    Units:decimal degrees
    YEAR
    Year (Source: U.S. Geological Survey)
    Range of values
    Minimum:2018
    Maximum:2018
    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
    Entity_and_Attribute_Overview:
    Graphic image file: Printable versions of the processed subbottom profiles are available as GIF images and are included in the download file, 2018-322-FA_seisimag.zip.
    Entity_and_Attribute_Overview:
    Navigation file: Navigation files are available as ASCII text files. Provided are raw shotpoint navigation files, reprojected survey shotpoint navigation, 1,000-shot-interval locations, and start of line files. The final navigation files are provided in 2018-322-FA_nav.zip.
    Entity_and_Attribute_Overview:
    GIS file: The GIS data associated with this survey are provided as a compressed zip file, 2018-322-FA_arc.zip, which is composed of an Esri map document, shapefiles, a folder containing the processed profile images, shapefile metadata for each GIS file and a readme document. The shapefiles provided may also be viewed using other versions of Esri desktop software including their free software Explorer for ArcGIS, which is available at http://www.esri.com/software/arcgis/explorer/index.html.
    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
    • Nancy T. DeWitt
    • Jake J. Fredericks
    • Jennifer L. Miselis
  2. Who also contributed to the data set?
    Funding and (or) support for this study was provided by the USGS Coastal and Marine Geology Program. The authors thank Andy Farmer of Cherokee Nation Technologies and Anastasios Stathakopoulos of the USGS for their assistance in data collection and piloting the R/V Sallenger. This document was improved by scientific and metadata reviews from Stephen Bosse and Chelsea Stalk of Cherokee Nation Technologies.
  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?

To archive all digital chirp subbottom profile data and associated files collected during Field Activity Number 2018-322-FA. Additional survey and data details are available from the Coastal and Marine Geoscience Data System (CMGDS) at, https://cmgds.marine.usgs.gov/fan_info.php?fan=2018-322-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-Nov-2018 (process 1 of 4)
    Chirp acquisition and processing - USGS scientists created a purpose-built, towed sled system to mount the 512i chirp profiler (just below the water's surface) and enable launching and recovery from the beach. The seismic sled was also configured to help ensure the quality of data collected in exceedingly shallow water depths, such as those observed near the shoreline and surf zone. The SEG Y data were processed with SU (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) applying a 3000-4000-10,000-12,000 bandpass filter to the analytic data to remove noise from the raw data, prior to creating the envelope seismic data file; corrected files included in this publication have "_env_bp" appended to the line name (2) removing navigation data for each shot and converting the SEG Y file to SU format, (3) applying automatic gain control, (4) generating a PostScript image of the traces, and (4) converting the PostScript image to a GIF image. 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:
    • SEG Y
    Data sources produced in this process:
    • SEG Y.gif
    Date: 13-Nov-2018 (process 2 of 4)
    Navigation processing: Location data were extracted from the SEG Y headers using Seismic Unix software and output as ASCII text files; PROJ.5.1.0 (https://proj4.org/) software was used to project WGS84 latitude and longitude coordinates to Universal Transverse Mercator (UTM) northings and eastings (WGS84, Zone 18, meters). Raw navigation files for each seismic line, saved by line number, were concatenated into comma-delimited text files for use with Esri ArcGIS software. The final output files are as follows: (1) 2018-322-FA.txt contains unique shotpoint positions (along each line) for the entire survey, (2) s2018-322-FA.txt 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) 2018-322-FA_s has the start-of-line locations for each trackline. The concatenated, comma-delimited text files were later imported into ArcGIS 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. 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:
    • *_env_bp.txt
    Data sources produced in this process:
    • 2018-322-FA.txt
    • s2018-322-FA.txt
    • 2018-322-FA_s.txt
    Date: 2017 (process 3 of 4)
    Trackline map creation: 2018-322-FA_location.mxd was created with Esri ArcGIS 10.3.1 software. The survey navigation file, 2018-322-FA.txt, was imported into ArcMap 10.3.1 and processed using the ArcScript "Points to Lines" to create a line shapefile of the cruise tracklines called 2018-322-FA_trkln. The 1,000-shot-interval file and the start-of-line file were imported into ArcMap and saved as point shapefiles 2018-322-FA_shots and 2018-322-FA_sol, respectively. A non-proprietary version of the survey tracklines was created using the "Layer to KML" tool within ArcToolbox and output in keyhole markup language (kml) format. The ArcGIS files included in this release are unprojected (geographic coordinates, WGS84). Please refer to the individual shapefile metadata and readme file, included in 2018-322-FA_arc.zip, for detailed information about the geospatial files provided in this data release. 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:
    • 2018-322-FA.txt
    • s2018-322-FA.txt
    • 2018-322-FA_s.txt
    Data sources produced in this process:
    • 2018-322-FA_trkln.shp
    • 2018-322-FA_shots.shp
    • 2018-322-FA_sol.shp
    • 2018-322-FA.kml
    Date: 13-Oct-2020 (process 4 of 4)
    Added keywords section with USGS persistent identifier as theme keyword. Person who carried out this activity:
    U.S. Geological Survey
    Attn: VeeAnn A. Cross
    Marine Geologist
    384 Woods Hole Road
    Woods Hole, MA

    508-548-8700 x2251 (voice)
    508-457-2310 (FAX)
    vatnipp@usgs.gov
  3. What similar or related data should the user be aware of?
    Cohen, J.K., and Stockwell, J.W., Jr., CWP/SU, 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:

    Forde, Arnell S., Bernier, Julie C., and Miselis, Jennifer L., 20180210, Archive of Ground Penetrating Radar and Differential Global Positioning System Data Collected in April 2016 from Fire Island, New York: U.S. Geological Survey Data Release doi:10.5066/F7P84B1P, U.S. Geological Survey - St. Petersburg Coastal and Marine Science Center, St. Petersburg, Florida.

    Online Links:

    Forde, Arnell S., Bernier, Julie C., and Miselis, Jennifer L., 20180210, Ground Penetrating Radar and Differential Global Positioning System Data Collected in April 2016 from Fire Island, New York: U.S. Geological Survey Data Series 1078, U.S. Geological Survey, St. Petersburg, FL.

    Online Links:

    Buster, Noreen A., Bernier, Julie C., Brenner, Owen T., Kelso, Kyle W., Tuten, Thomas M., and Miselis, Jennifer L., 2018, Sediment Data from Vibracores Collected in 2016 from Fire Island, New York: U.S. Geological Survey Data Series DS 1100, U.S. Geological Survey, St. Petersburg, FL.

    Online Links:

    Bernier, Julie C., Buster, Noreen A., Brenner, Owen T., Kelso, Kyle W., Tuten, Thomas M., and Miselis, Jennifer L., 2018, Archive of Sediment Data from Vibracores Collected in 2016 from Fire Island, New York.

    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. Survey lines collected on the first survey day, day of year (DOY) 153, used a frequency sweep of 0.5-6 KHz; however, 0.7-12 KHz was used for all other survey days (DOY 157-160). During the initial chirp data processing, visual inspection of the images rendered from the seismic data (excluding DOY 153 subbottom profiles) showed the presence of an anomaly at approximately 10 ms (two-way travel time [TWT]) on each profile. The preceding issue was resolved during post-processing, the data were re-checked for quality assurance/quality control compliance, and the corrected profile images were included in the data release.
  2. How accurate are the geographic locations?
    An Ashtech Proflex 800 GPS receiver was used to collect position information. The manufacturer's stated accuracy for positioning when utilizing a differential global positioning system (DGPS) is 0.5–2 m. To ensure consistent spacing between survey lines (for example, 5 m in the nearshore and 10 m for offshore lines), pre-determined trackline locations were imported into HYPACK 2018 navigation software and followed during seismic data collection. Positions from the DGPS were recorded and written to seismic trace headers in latitude and longitude coordinates (World Geodetic System of 1984, WGS84, realization G1762) every 1 second (s). The approximate 20-m offset between the chirp shot and ship's GPS reference point was not accounted for during acquisition, nor have the 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. TWT times shown on the printable profile images are relative to the chirp towfish position, not to the sea surface.
  4. Where are the gaps in the data? What is missing?
    A total of 115 seismic lines were collected during this survey.
  5. How consistent are the relationships among the observations, including topology?
    These datasets are from one field activity with consistent instrument calibrations.

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 this data release are also downloadable from the Coastal and Marine Geoscience Data System 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.

Who wrote the metadata?

Dates:
Last modified: 13-Oct-2020
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/2018-322-FA_metadata.faq.html>
Generated by mp version 2.9.50 on Tue Sep 21 18:18:31 2021