2019-333-FA_sol: Digital Chirp Subbottom Profile Start of Line Data Collected During USGS Field Activity Number 2019-333-FA Offshore of the Rockaway Peninsula, New York, September–October 2019

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

Frequently anticipated questions:

What does this data set describe?

Title:
2019-333-FA_sol: Digital Chirp Subbottom Profile Start of Line Data Collected During USGS Field Activity Number 2019-333-FA Offshore of the Rockaway Peninsula, New York, September–October 2019
Abstract:
From September 27 through October 5, 2019, the U.S. Geological Survey (USGS) conducted geophysical surveys to investigate the geologic controls on barrier island evolution and sediment transport offshore of the Rockaway Peninsula, New York. This shapefile represents a point dataset of field activity number (FAN) 2019-333-FA chirp subbottom profile start of trackline locations.
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=2019-333-FA and in the Field Activity Collection System (FACS) and geophysical logs, which are included in the download file, 2019-333-FA_logs.zip (Forde and others, 2021).
  1. How might this data set be cited?
    Forde, Arnell S., 20210525, 2019-333-FA_sol: Digital Chirp Subbottom Profile Start of Line Data Collected During USGS Field Activity Number 2019-333-FA Offshore of the Rockaway Peninsula, New York, September–October 2019:.

    This is part of the following larger work.

    Forde, Arnell S., Wei, Emily A., DeWitt, Nancy T., and Miselis, Jennifer L., 20210525, Archive of Chirp Subbottom Profile Data Collected in 2019 From Rockaway Peninsula, New York: U.S. Geological Survey data release doi:10.5066/P9ZO8QKJ, 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.9392
    East_Bounding_Coordinate: -73.7604
    North_Bounding_Coordinate: 40.5899
    South_Bounding_Coordinate: 40.5296
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 27-Sep-2019
    Ending_Date: 05-Oct-2019
    Currentness_Reference:
    ground condition
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: Vector Digital Dataset (Point)
  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):
      • Entity point (73)
    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.0197459685. Longitudes are given to the nearest 0.0258684611. 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?
    2019-333-FA_sol.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.
    UTMX
    UTM-X easting coordinate (Source: Universal Transverse Mercator (WGS 1984, Zone 18))
    Range of values
    Minimum:589831.239
    Maximum:604913.062
    UTMY
    UTM-Y northing coordinate (Source: Universal Transverse Mercator (WGS 1984, Zone 18))
    Range of values
    Minimum:4487092.777
    Maximum:4493964.334
    Line
    Trackline name (Source: U.S. Geological Survey) The naming convention used for each subbottom line is as follows: exy_bp_mod, where 'e' means the seismic traces were output as an envelope, 'x' is an 8-digit number indicating a specific trackline (for example, 0002_1609), 'y' is a letter (such as, a or b) representing a new line if recording was prematurely terminated or reran for quality or acquisition problems, and '_bp_mod' denotes that the seismic data were bandpass filtered and modified to use post-processed GPS coordinates for navigation. Line numbers were automatically assigned by the chirp topside unit during data acquisition and are composed of a 4-digit Hypack trackline number and a 4-digit timestamp corresponding to the line's start time. There are four transit lines (etransit_to_13_bp_mod, etransit_to_beach_bp_mod, eTransitlogJD278_bp_mod, and e20190902155831_bp_mod) whose file names were manually entered and therefore do not follow the aforementioned convention.
    Shot
    Shotpoint number (Source: U.S. Geological Survey)
    Range of values
    Minimum:1
    Maximum:1
    Lon
    Longitude (Source: World Geodetic System 1984 Geographic Coordinate System)
    Range of values
    Minimum:-73.939211
    Maximum:-73.760378
    Lat
    Latitude (Source: World Geodetic System 1984 Geographic Coordinate System)
    Range of values
    Minimum:40.529583
    Maximum:40.589908
    YEAR
    Year of data acquisition (Source: U.S. Geological Survey)
    Range of values
    Minimum:2019
    Maximum:2019
    DOY_HR_MIN
    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.
    Entity_and_Attribute_Overview:
    Navigation files are available as ASCII delimited text files in CSV format. The final navigation files are provided in 2019-333-FA_nav.zip (Forde and others, 2021) 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, 2019-333-FA_sol.shp. The entity and attribute information provided here describes the tabular data associated with the dataset. 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 Nancy DeWitt, Jennifer Miselis, 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 subbottom profile data collected during USGS FAN 2019-333-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: 04-Feb-2021 (process 1 of 2)
    Navigation files were extracted from the seismic trace headers using Seismic Unix release 44 software, processed with PROJ.5.1.0 software to generate Universal Transverse Mercator (UTM) 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. A custom script was created to produce unique navigation fixes for each line and for all instances where the shot was equal to 1, that data point was output into a new text file. All the shotpoints described in the previous step were concatenated in the CSV file, 2019-333-FA_sol.csv, which represents the start of each trackline collected during the survey. 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: 04-Feb-2021 (process 2 of 2)
    The reformatted, text files were imported into Esri ArcMap 10.6 software to produce a geographic representation of the shotpoint data collected within the survey area. ArcMap was used to create a point shapefile containing start of line locations for all chirp 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?
    The validity or accuracy of marine subbottom profiles is highly qualitative and depends on equipment and operating condition variables.
  2. How accurate are the geographic locations?
    Both subbottom and bathymetry data were collected aboard a towed seismic sled, which was outfitted with a Spectra Precision SP90M GPS receiver (to collect position information) and a single-beam echosounder. Differential positioning was obtained through post-processing the base station (established on USGS benchmark RIIS) data to the rover located on the sled. As the subbottom profile data were acquired, the position of the vessel was continuously determined by an Ashtech Proflex 500 unit with a global navigation satellite system antenna. Positions from the Proflex were recorded and written to the seismic trace headers every second (s). During subbottom processing, vessel coordinates previously saved to the seismic headers were replaced with post-processed GPS. The approximately 14-m offset between the chirp and GPS antenna has been accounted for in the 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 74 seismic lines were collected during this field activity. e0021_1955 was a partial line containing no usable data, so it was excluded from this data release.
  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: 2019-333-FA_gis.zip contains the survey navigation data represented geospatially using a Google Earth KMZ, Esri map document, shapefiles, and a folder of processed subbottom profile images (accessible via hyperlinks included in the MXD). This metadata record describes the start of line locations provided in, 2019-333-FA_sol.shp, which is one of the three Esri shapefiles included in the geographic information system (GIS) data ZIP file. in format Shapefile, MXD, KMZ, GIF Size: 46.5
      Network links: https://coastal.er.usgs.gov/data-release/doi-P9ZO8QKJ/data/2019-333-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.6 software. It may also be viewed with Esri public domain software Explorer for ArcGIS, GeoMapApp 3.6.10 (http://www.geomapapp.org, 2021), or other GIS software capable of importing the data.

Who wrote the metadata?

Dates:
Last modified: 28-Apr-2021
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/2019-333-FA_sol.shp.faq.html>
Generated by mp version 2.9.50 on Tue Sep 21 18:18:31 2021