2022-312-FA_trkln: Digital Chirp Subbottom Profile Trackline Data Collected During USGS Field Activity Number 2022-312-FA Near Panama City, Florida, November 2022

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

Frequently anticipated questions:

What does this data set describe?

Title:
2022-312-FA_trkln: Digital Chirp Subbottom Profile Trackline Data Collected During USGS Field Activity Number 2022-312-FA Near Panama City, Florida, November 2022
Abstract:
From June 20-30, 2022, the U.S. Geological Survey (USGS) conducted geophysical surveys to investigate the geologic controls on barrier island evolution and sediment transport near Panama City, Florida (FL). Geophysical data were collected as part of the Coastal Sediment Availability and Flux and Defense Advanced Research Protection Agency (DARPA) Reefense projects. This shapefile represents a line dataset of field activity number (FAN) 2022-312-FA chirp tracklines.
Supplemental_Information:
Additional survey and data details are available from the USGS Coastal and Marine Geoscience Data System (CMGDS) at, https://cmgds.marine.usgs.gov/fan_info.php?fan=2022-312-FA and in the Field Activity Collection System (FACS) and geophysical logs, which are included in the download file, 2022-312-FA_logs.zip (Forde and others, 2023).
  1. How might this data set be cited?
    Forde, Arnell S., 20231101, 2022-312-FA_trkln: Digital Chirp Subbottom Profile Trackline Data Collected During USGS Field Activity Number 2022-312-FA Near Panama City, Florida, November 2022:.

    This is part of the following larger work.

    Forde, Arnell S., Wei, Emily A., and Stalk, Chelsea A., 20231101, Archive of Chirp Subbottom Profile Data Collected in June 2022 Near Panama City, Florida: U.S. Geological Survey data release doi:10.5066/P9YTB22D, 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: -85.708144
    East_Bounding_Coordinate: -85.469306
    North_Bounding_Coordinate: 30.149756
    South_Bounding_Coordinate: 30.0229876
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 20-Jun-2022
    Ending_Date: 30-Jun-2022
    Currentness_Reference:
    ground condition
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: Vector Digital Dataset (Polyline)
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
      This is a Vector data set. It contains the following vector data types (SDTS terminology):
      • String (224)
    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.0197883202. Longitudes are given to the nearest 0.0227434348. 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?
    2022-312-FA_trkln.shp Attribute Table
    Table containing attribute information associated with the dataset. (Source: U.S. Geological Survey)
    FID
    Internal feature number. (Source: Esri) Sequential unique whole numbers that are automatically generated.
    Shape
    Feature geometry. (Source: Esri) Coordinates defining the features.
    Line
    Trackline name (Source: U.S. Geological Survey) Line numbers were assigned by the EdgeTech 3400 chirp topside unit during data acquisition and are composed of the FAN, DOY, and trackline number. The naming convention used for each subbottom line is as follows: x_env, where 'x' is an alphanumeric number indicating a specific trackline (for example, 2022_312_FA_171_001) and 'env' denotes that the seismic traces were output as an envelope. Four track lines were manually assigned and do not follow this convention. For these files, the DOY information is excluded from the line number (for example, 2022_312_FA_001b_env). 26 test and “tie” lines (perpendicular tracklines crossing two parallel lines) also deviate from the previously described naming convention and have names such as, 2022_312_FA_172_014testDv5_env and 2022_312_FA_171_004tie_env.
    Image
    Graphics Interchange Format (GIF) image name (Source: U.S. Geological Survey) This attribute field provides the name of the subbottom profile image (.gif) that is associated with each trackline as a hyperlinked GIF; a folder containing all these .gif files, named "images", is included in 2022-312-FA_gis.zip.
    Entity_and_Attribute_Overview:
    Navigation files are available as ASCII delimited text files in CSV format. The final navigation files are provided in 2022-312-FA_nav.zip (Forde and others, 2023) and represent the reprojected survey shotpoint navigation, 1,000-shot-interval locations, and start of line files. The entity and attribute information provided here describes the tabular data associated with the shapefile, 2022-312-FA_trkln.shp. Please review the detailed descriptions that are provided (the individual attribute descriptions) for information on the values that appear as fields/table entries of the dataset.
    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?
    Data collection and processing were performed by Chelsea Stalk, Emily Wei, and Arnell Forde of the USGS St. Petersburg Coastal and Marine Science Center.
  3. To whom should users address questions about the data?
    Arnell S. Forde
    U.S. Geological Survey
    Geologist
    600 4th Street South
    St. Petersburg, FL
    USA

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

Why was the data set created?

To aid in the registering of digital chirp seismic reflection data collected during USGS FAN 2022-312-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: 05-Oct-2022 (process 1 of 2)
    Navigation files were extracted from the SEG-Y trace headers using Seismic Unix release 44 software, processed with PROJ.5.1.0 software to generate Universal Transverse Mercator (UTM) Zone 16 North (N) coordinates from latitude and longitude coordinates (World Geodetic System of 1984, WGS84), and then saved as ASCII text files in comma-separated values (CSV) format. Person who carried out this activity:
    Arnell S. Forde
    U.S. Geological Survey
    Geologist
    600 4th Street South
    St. Petersburg, FL
    USA

    727-502-8000 (voice)
    aforde@usgs.gov
    Date: 01-Aug-2023 (process 2 of 2)
    The reformatted text files were imported into Esri ArcMap 10.8 software to produce a geographic representation of the subbottom profile tracklines collected within the survey area. The 'PointsToLine' script (located in the ArcToolbox) was used to create a shapefile in which individual chirp shotpoints were connected to form tracklines. Person who carried out this activity:
    Arnell S. Forde
    U.S. Geological Survey
    Geologist
    600 4th Street South
    St. Petersburg, FL
    USA

    727-502-8000 (voice)
    aforde@usgs.gov
  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?
  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), which is accurate to within 0.5-2 meters (m). Positions from the POS MV IANS were recorded and written to the seismic trace headers every 0.20 seconds, with unique navigation fixes every 1 second. The approximately 3-meter offset between the chirp and vessel's IANS reference point has not been accounted for in the comma-delimited American Standard Code for Information Interchange (ASCII) navigation files and trackline map.
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
    A total of 234 seismic lines were collected during this field activity. Ten lines were excluded from Forde and others (2023), due to equipment or acquisition issues resulting in partial or unusable data files.
  5. How consistent are the relationships among the observations, including topology?
    This dataset is 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
Use_Constraints 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
  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?
    • Availability in digital form:
      Data format: 2022-312-FA_gis.zip (Forde and others, 2023) contains the survey navigation data represented geospatially using a Google Earth Keyhole Markup Language Zipped (KMZ), Esri map document (MXD), shapefiles, and a folder of processed subbottom profile images (accessible via hyperlinks included in the MXD). This metadata record describes the trackline locations provided in 2022-312-FA_trkln.shp, which is one of three Esri shapefiles included in the geographic information system (GIS) data ZIP file. in format Shapefile, MXD, KMZ, GIF Size: 127.9
      Network links: https://coastal.er.usgs.gov/data-release/doi-P9YTB22D/data/2022-312-FA_gis.zip
    • Cost to order the data: None

  5. What hardware or software do I need in order to use the data set?
    This shapefile was created for use with Esri ArcGIS 10.8 software. It may also be viewed with QGIS (https://www.qgis.org/en/site/, 2023), GeoMapApp 3.6.15 (https://www.geomapapp.org, 2023), or other GIS software capable of importing the data.

Who wrote the metadata?

Dates:
Last modified: 30-Oct-2023
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/2022-312-FA_trkln.shp.faq.html>
Generated by mp version 2.9.51 on Thu Nov 2 09:21:21 2023