Chirp sub-bottom data collected in the Great Salt Lake, Utah, during USGS field activity 2021-615-FA

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

Frequently anticipated questions:

What does this data set describe?

Title:
Chirp sub-bottom data collected in the Great Salt Lake, Utah, during USGS field activity 2021-615-FA
Abstract:
This data release contains 57 high-resolution chirp sub-bottom profiles collected in the southern Great Salt Lake, Utah. Data were collected by the U.S. Geological Survey (USGS) in June of 2021 during USGS field activity 2021-615-FA.
Supplemental_Information:
Additional information about the field activity or activities from which these data were derived is available online at:
https://cmgds.marine.usgs.gov/fan_info.php?fan=2021-615-FA
Any use of trade, product, or firm names is for descriptive purposes only and does not imply endorsement by the U.S. Government.
  1. How might this data set be cited?
    Balster-Gee, Alicia F., Brothers, Daniel S., DuRoss, Christopher B., Kluesner, Jared W., Powers, Daniel C., Currie, Jackson E., Ferro, Peter Dal, and Jobe, Jessica A., 20250904, Chirp sub-bottom data collected in the Great Salt Lake, Utah, during USGS field activity 2021-615-FA: data release DOI:10.5066/P13FCNPJ, U.S. Geological Survey, Pacific Coastal and Marine Science Center, Santa Cruz, California.

    Online Links:

    Other_Citation_Details:
    Suggested Citation: Balster-Gee, A.F., Brothers, D.S., DuRoss, C.B., Kluesner, J.W., Powers, D.C., Currie, J.E., Dal Ferro, P., Jobe, J.A., 2025, Chirp sub-bottom data collected in the Great Salt Lake, Utah during USGS field activity 2021-615-FA: U.S. Geological Survey data release, https://doi.org/10.5066/P13FCNPJ.
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -112.482800239
    East_Bounding_Coordinate: -112.183759519
    North_Bounding_Coordinate: 41.120925762
    South_Bounding_Coordinate: 40.747385234
  3. What does it look like?
    2021-615-FA.GreatSaltLake.chirp.preview.png (PNG)
    Map of chirp sub-bottom tracklines in the southern Great Salt Lake.
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 19-Jun-2021
    Ending_Date: 02-Jul-2021
    Currentness_Reference:
    Ground condition at the time data were collected.
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: seismic-reflection data in SEG-Y format
  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. It contains the following vector data types (SDTS terminology):
      • Point (57)
    2. What coordinate system is used to represent geographic features?
      Grid_Coordinate_System_Name: Universal Transverse Mercator
      Universal_Transverse_Mercator:
      UTM_Zone_Number: 12
      Transverse_Mercator:
      Scale_Factor_at_Central_Meridian: 0.9996
      Longitude_of_Central_Meridian: -111.0
      Latitude_of_Projection_Origin: 0.0
      False_Easting: 500000.0
      False_Northing: 0.0
      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 0.0001
      Ordinates (y-coordinates) are specified to the nearest 0.0001
      Planar coordinates are specified in Meter
      The horizontal datum used is D_WGS_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?
    Entity_and_Attribute_Overview: Seismic Shots with Time Stamp in standard SEG-Y file format
    Entity_and_Attribute_Detail_Citation:
    Society of Exploration Geophysicists (SEG) Technical Standards, available for download at http://seg.org/Publications/SEG-Technical-Standards

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Alicia F. Balster-Gee
    • Daniel S. Brothers
    • Christopher B. DuRoss
    • Jared W. Kluesner
    • Daniel C. Powers
    • Jackson E. Currie
    • Peter Dal Ferro
    • Jessica A. Jobe
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
    U.S. Geological Survey, Pacific Coastal and Marine Science Center
    Attn: PCMSC Science Data Coordinator
    2885 Mission Street
    Santa Cruz, CA

    831-427-4747 (voice)
    pcmsc_data@usgs.gov

Why was the data set created?

This high-resolution sub-bottom dataset was acquired in the Great Salt Lake, Utah, to investigate paleoseismic evidence associated with the Great Salt Lake Fault. The dataset aims to image subsurface sedimentary structures and stratigraphy to identify and characterize past earthquake events, contributing to a better understanding of the fault’s seismic history, recurrence intervals, and associated geohazards in the region.

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: 16-Jul-2025 (process 1 of 1)
    Raw SEG-Y format seismic shots were imported into Shearwater Reveal 5 (seismic software), and navigational data was converted to UTM zone 12N and stored in header bytes 81 and 85 with a -1000 scalar (scalar recoded in header byte 71). Further processing included transforming to envelope, applying water column and bottom mute, and performing swell correction using the peak trace amplitude time-averaged over the swell period (typically between 21 and 55 traces). Sometimes, two passes of swell correction were required when there were mixed swell periods. SEG-Y files were named ###.swell.segy, where ### is the line number. SEG-Y files were zipped into the file 2021-615-FA.GreatSaltLake.chirp.data.zip.
  3. What similar or related data should the user be aware of?

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

  1. How well have the observations been checked?
    Quality control of attribute accuracy was conducted during field data collection and processing workflows. Some seismic profiles have gaps in them due to system crashes. Minor swell correction artifacts exist at line starts and ends as well as in areas where lake floor amplitudes are low.
  2. How accurate are the geographic locations?
    An Applanix POS-MV (Position and Orientation System for Marine Vessels) Elite was used to position the source vessel during data collection. The Applanix POS-MV Elite has a stated positional accuracy of 0.5-2 meters (https://www.applanix.com/downloads/products/specs/posmv/POS-MV-ELITE.pdf). Accuracies of final products may be lower due to total propagated uncertainties of the mapping systems, which include the position and motion compensation system and navigation error.
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
    The dataset is considered complete for the information presented, as described in the abstract. Users are advised to read the rest of the metadata record carefully for additional details.
  5. How consistent are the relationships among the observations, including topology?
    Quality control was conducted during acquisition and processing to ensure consistency of SEG-Y header navigation and seismic-reflection data that matches bathymetry along the tracklines.

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?
Access_Constraints No access constraints
Use_Constraints USGS-authored or produced data and information are in the public domain from the U.S. Government and are freely redistributable with proper metadata and source attribution. These data are marked with a Creative Common CC0 1.0 Universal License. Please recognize and acknowledge the U.S. Geological Survey as the originator of the dataset and in products derived from these data. This information is not intended for navigation purposes.
  1. Who distributes the data set? (Distributor 1 of 1)
    U.S. Geological Survey - CMGDS
    2885 Mission Street
    Santa Cruz, CA

    831-427-4747 (voice)
    pcmsc_data@usgs.gov
  2. What's the catalog number I need to order this data set? These data are available in SEG-Y format (###.swell.segy where ### is the line number) and are contained in a single zip file (2021-615-FA.GreatSaltLake.chirp.data.zip) accompanied by CSDGM FGDC-compliant metadata.
  3. What legal disclaimers am I supposed to read?
    Unless otherwise stated, all data, metadata, and related materials are considered to satisfy the quality standards relative to the purpose for which the data were collected. Although these data and associated metadata have been reviewed for accuracy and completeness and approved for release by the U.S. Geological Survey (USGS), no warranty expressed or implied is made regarding the display or utility of the data on any other system or for general or scientific purposes, nor shall the act of distribution constitute any such warranty.
  4. How can I download or order the data?
    • Availability in digital form:
      Data format: Zip file contains the processed seismic data per navigation line. in format SEG-Y (version SEG-Y rev 1) Size: 8400
      Network links: https://doi.org/10.5066/P13FCNPJ
    • Cost to order the data: None.

  5. What hardware or software do I need in order to use the data set?
    Use of SEG-Y data requires specialized software, such as ProMax and Seisworks by Landmark Geophysical; FOCUS and SeisX by Paradigm Geophysical; SPW by Parallel Geoscience; VISTA by Seismic Image Software; SeiSee by Dalmorneftegeophysica (DMNG), amongst others.

Who wrote the metadata?

Dates:
Last modified: 04-Sep-2025
Metadata author:
U.S. Geological Survey, Pacific Coastal and Marine Science Center
Attn: PCMSC Science Data Coordinator
2885 Mission Street
Santa Cruz, CA

831-427-4747 (voice)
pcmsc_data@usgs.gov
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)
This page is <https://cmgds.marine.usgs.gov/catalog/pcmsc/DataReleases/CMGDS_DR_tool/DR_P13FCNPJ/2021-615-FA.chirp.metadata.faq.html>
Generated by mp version 2.9.51 on Tue Sep 9 17:04:02 2025