Chirp seismic reflection - shotpoints, tracklines, profile images, and SEG-Y traces for EdgeTech SB-512i chirp data collected during USGS field activity 2019-002-FA (point and polyline shapefiles, CSV text, PNG Images, and SEGY data, GCS WGS 84)

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

Frequently anticipated questions:

What does this data set describe?

Title:
Chirp seismic reflection - shotpoints, tracklines, profile images, and SEG-Y traces for EdgeTech SB-512i chirp data collected during USGS field activity 2019-002-FA (point and polyline shapefiles, CSV text, PNG Images, and SEGY data, GCS WGS 84)
Abstract:
Accurate data and maps of sea floor geology are important first steps toward protecting fish habitat, delineating marine resources, and assessing environmental changes due to natural or human impacts. To address these concerns the U.S. Geological Survey, in cooperation with the Massachusetts Office of Coastal Zone Management (CZM), comprehensively mapped the Cape Cod Bay sea floor to characterize the surface and shallow subsurface geologic framework. Geophysical data collected include swath bathymetry, backscatter, and seismic reflection profile data. Ground-truth data, including sediment samples, underwater video, and bottom photographs were also collected. This effort is part of a long-term collaboration between the USGS and the Commonwealth of Massachusetts to map the State’s waters, support research on the Quaternary evolution of coastal Massachusetts, the influence of sea-level change and sediment supply on coastal evolution, and efforts to understand the type, distribution, and quality of subtidal marine habitats. This collaboration produces high-resolution geologic maps and Geographic Information System (GIS) data that serve the needs of research, management and the public. Data collected as part of this mapping cooperative continue to be released in a series of USGS Open-File Reports and Data Releases (https://www.usgs.gov/centers/whcmsc/science/geologic-mapping-massachusetts-seafloor). This data release provides the geophysical and geologic sampling data collected in Cape Cod Bay during USGS Field Activities 2019-002-FA and 2019-034-FA in 2019.
Supplemental_Information:
Support for 2019-002-FA was provided to the USGS from the Massachusetts Office of Coastal Zone Management. Additional information on the field activities associated with this project are available at https://cmgds.marine.usgs.gov/fan_info.php?fan=2019-002-FA and https://cmgds.marine.usgs.gov/fan_info.php?fan=2019-034-FA.
  1. How might this data set be cited?
    Foster, David S., 20220718, Chirp seismic reflection - shotpoints, tracklines, profile images, and SEG-Y traces for EdgeTech SB-512i chirp data collected during USGS field activity 2019-002-FA (point and polyline shapefiles, CSV text, PNG Images, and SEGY data, GCS WGS 84): data release DOI:10.5066/P99DR4PN, U.S. Geological Survey, Coastal and Marine Hazards and Resources Program, Woods Hole Coastal and Marine Science Center, Woods Hole, Massachusetts.

    Online Links:

    This is part of the following larger work.

    Ackerman, Seth D., Foster, David S., Andrews, Brian D., Danforth, William W., Baldwin, Wayne E., Huntley, Emily C., Worley, Charles R., and Brothers, Laura L., 2022, High-resolution geophysical and geological data collected in Cape Cod Bay, Massachusetts during USGS Field Activities 2019-002-FA and 2019-034-FA: data release DOI:10.5066/P99DR4PN, U.S. Geological Survey, Reston, VA.

    Online Links:

    Other_Citation_Details:
    Suggested citation: Ackerman, S.D., Foster, D.S., Andrews, B.D., Danforth, W.W., Baldwin, W.E., Huntley, E.C., Worley, C.R., and Brothers, L.L., 2022, High-resolution geophysical and geological data collected in Cape Cod Bay, Massachusetts during USGS Field Activities 2019-002-FA and 2019-034-FA: U.S. Geological Survey data release, https://doi.org/10.5066/P99DR4PN.
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -70.510075
    East_Bounding_Coordinate: -70.104511
    North_Bounding_Coordinate: 42.065233
    South_Bounding_Coordinate: 41.747986
  3. What does it look like?
    https://cmgds.marine.usgs.gov/data-releases/media/2020/10.5066-P99DR4PN/a2ebde514b784809890e6817f4eedb64/2019-002-FA_SB512i_browse.jpg (JPEG)
    Thumbnail image showing the extent of chirp seismic-reflection profile data collected in Cape Cod Bay, Massachusetts.
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 01-Aug-2019
    Ending_Date: 29-Aug-2019
    Currentness_Reference:
    ground condition
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: Shapefile, CSV, PNG Image, SEG-Y
  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 (616)
    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.000001. Longitudes are given to the nearest 0.000001. 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.257224.
  7. How does the data set describe geographic features?
    2019-002-FA_SB512iTracklines.shp
    SB-512i Trackline shapefile for survey 2019-002-FA (616 polyline features). (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.
    LineName
    Name of the trackline along which seismic-reflection data were collected in the format: LineFileNumber as follows L#F# (i.e.'l1f1'). (Source: U.S. Geological Survey) Character set
    ImageName
    PNG image name of seismic-reflection profile corresponding to survey line. (Source: U.S. Geological Survey) Character set
    Shot_init
    Shot number at the start of the survey line. (Source: U.S. Geological Survey)
    Range of values
    Minimum:1
    Maximum:92
    Units:shot
    Resolution:1
    Shot_end
    Shot number at the end of the survey line. (Source: U.S. Geological Survey)
    Range of values
    Minimum:96
    Maximum:13863
    Units:shot
    Resolution:1
    Year
    Calendar year the data were collected (Source: U.S. Geological Survey) Character set
    JD_UTC_ini
    Julian day and UTC time at the start of the survey line in the format: JD:HH:MM:SS; Julian day is the integer number (although recorded here in text string format) representing the interval of time in days since January 1 of the year of collection. (Source: U.S. Geological Survey) Character set
    JD_UTC_end
    Julian day and UTC time at the end of the survey line in the format: JD:HH:MM:SS; Julian day is the integer number (although recorded here in text string format) representing the interval of time in days since January 1 of the year of collection. (Source: U.S. Geological Survey) Character set
    SurveyID
    WHCMSC field activity identifier (e.g. "2019-002-FA" where 2019 is the survey year, 002 is survey number of that year, and FA is Field Activity). (Source: U.S. Geological Survey) Character set
    VehicleID
    Survey vessel name. (Source: U.S. Geological Survey) Character set
    DeviceID
    Sonar device used to collect seismic-reflection data. (Source: U.S. Geological Survey) Character set
    Length_km
    Length of seismic-reflection data line in kilometers (UTM Zone 19N, WGS 84) calculated in the SQLite database. (Source: U.S. Geological Survey)
    Range of values
    Minimum:0.123
    Maximum:16.686
    Units:kilometers
    Resolution:0.01
    2019-002-FA_SB512i_sht500.shp
    SB512i 500-interval shot point shapefile for survey 2019-002-FA (1068 point features). (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.
    East
    Easting coordinate in UTM Zone 19 N meters, WGS 84 (Source: U.S. Geological Survey)
    Range of values
    Minimum:374598.26
    Maximum:408456.98
    Units:meters
    Resolution:.01
    North
    Northing coordinate in UTM Zone 19 N meters, WGS 84 (Source: U.S. Geological Survey)
    Range of values
    Minimum:4622653.92
    Maximum:4658032.5
    Units:meters
    Resolution:.01
    Lon
    Longitude coordinate in decimal degrees, WGS 84 (Source: U.S. Geological Survey)
    Range of values
    Minimum:-70.510075
    Maximum:-70.104511
    Units:degrees
    Resolution:1E-06
    Lat
    Latitude coordinate in decimal degrees, WGS 84 (Source: U.S. Geological Survey)
    Range of values
    Minimum:41.747986
    Maximum:42.065233
    Units:degrees
    Resolution:1E-06
    LineName
    Name of the trackline along which seismic-reflection data were collected in the format: LineFileNumber as follows L#F# (i.e.'l1f1'). (Source: U.S. Geological Survey) Character set
    ImageName
    PNG image name of seismic-reflection profile corresponding to survey line. (Source: U.S. Geological Survey) Character set
    Shot
    Shot number (values are first, last, and every 500 shot between). (Source: U.S. Geological Survey)
    Range of values
    Minimum:1
    Maximum:13863
    Units:shot
    Resolution:1
    Year
    Year the data were collected YYYY. (Source: U.S. Geological Survey) Character set
    JD_UTC
    Julian day and UTC time for first, last, and every 500 shot point between of the survey line in the format: JD:HH:MM:SS; Julian day is the integer number (although recorded here in text string format) representing the interval of time in days since January 1 of the year of collection. (Source: U.S. Geological Survey) Character set
    SurveyID
    WHCMSC field activity identifier (e.g. "2019-002-FA" where 2019 is the survey year, 002 is survey number of that year, and FA is Field Activity). (Source: U.S. Geological Survey) Character set
    VehicleID
    Survey vessel name. (Source: U.S. Geological Survey) Character set
    DeviceID
    Sonar device used to collect seismic-reflection data. (Source: U.S. Geological Survey) Character set
    2019-002-FA_512i_shtnav.csv
    SB512i shot point comma separated values file for survey 2019-002-FA (1887785 point features). (Source: U.S. Geological Survey)
    2019-002-FA_512i_Images
    Portable network graphic images of processed SB512i profiles for survey 2019-002-FA (616 PNG images). (Source: U.S. Geological Survey)
    2019-002-FA_512i_SegyData
    SEG-Y format files of processed SB512i profiles for survey 2019-002-FA (616 SEG-Y files). (Source: U.S. Geological Survey)
    Entity_and_Attribute_Overview:
    The column headings and range domain values in '2019-002-FA_SB512i_shtnav.csv' match those in '2019-002-FA_SB512i_sht500.shp'. The PNG seismic reflection images can be hyperlinked to their corresponding trackline or shotpoint locations in ArcGIS using the shapefiles '2019-002-FA_SB512iTracklines.shp' or '2019-002-FA_SB512i_sht500.shp', respectively. The fist, last, and multiple of 500 shot features in '2019-002-FA_SB512i_sht500.shp' correspond to the x-axis ticks on the PNG images, which show two-way travel time (seconds) on the y-axis and distance along profile (annotation at 500 shot intervals) on the x-axis.
    Entity_and_Attribute_Detail_Citation: U.S. Geological Survey

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • David S. Foster
  2. Who also contributed to the data set?
    The authors acknowledge our fellow participants of the Cape Cod Bay field activities 2019-002-FA (Walter Barnhardt, Luke Bennett, Eric Moore, Alex Nichols, Jake Fredericks, and Dan Kennedy) and 2019-034-FA (Dann Blackwood, Eric Moore, and Alex Nichols); the crew of the M/V Warren Jr and the R/V Tioga; and our sea floor mapping group onshore support team during these surveys (Jane Denny, PJ Bernard, Barry Irwin, and Emile Bergeron).
  3. To whom should users address questions about the data?
    David S. Foster
    U.S. Geological Survey
    Geologist
    384 Woods Hole Road
    Woods Hole, Massachusetts
    US

    508-548-8700 x2271 (voice)
    508-457-2310 (FAX)
    dfoster@usgs.gov

Why was the data set created?

This dataset contains shotpoint and trackline navigation, profile images, and raw SEG-Y trace data for approximately 4585 km of EdgeTech SB512i chirp seismic-reflection data collected by the U.S. Geological Survey during USGS field activity 2019-002-FA in Cape Cod Bay. Images of each seismic profile were generated in order to provide portable and easily viewable alternatives to the SEG-Y versions of the data. Each profile image can be hyperlinked to its corresponding trackline navigation contained within the Esri polyline shapefile '2019-002-FA_SB512iTracklines.shp'. Shotpoint index and tick marks along the top of the PNG images correlate to the positions of 500 shot intervals within the Esri point shapefile '2019-002-FA_SB512i_sht500.shp'. This information allows for spatial correlation of chirp seismic-reflection profiles images with other geophysical and sample data for investigating sea-floor morphology and stratigraphy in the area.

How was the data set created?

  1. From what previous works were the data drawn?
    SEG-Y SB-512i data (source 1 of 1)
    U.S. Geological Survey, unpublished material, SB-512i SEG-Y trace data.

    Type_of_Source_Media: disc
    Source_Contribution:
    The EdgeTech SB-512i subbottom profiler was mounted on a catamaran raft (cataraft) that was towed on the sea surface from the starboard stern section of the M/V Warren Jr. The transducers were approximately 0.5 m below the water line, and approximately 30.8 meters astern of the DGPS antenna mounted on the acquisition van. Chirp seismic data were collected using an EdgeTech Geo-Star FSSB sub-bottom profiling system and an SB-0512i towfish. SonarWiz 7 (version 7.04.04) seismic acquisition software was used to control the Geo-Star FSSB topside unit, digitally log three trace data (envelope, real, and imaginary) in the SEG-Y Rev. 1 format (IEEE floating point), and record GPS navigation coordinates to the SEG-Y trace headers (in arc seconds of Latitude and Longitude, multiplied by a scalar of 100). Data were acquired using 25-ms shot rates, a 30-ms pulse length, and a 0.5 to 7.2 kHz frequency sweep. Traces were recorded with a 46-microsecond sample interval with a trace length of 250 ms.
  2. How were the data generated, processed, and modified?
    Date: Sep-2019 (process 1 of 3)
    PROCESS STEP 1:
    SIOSEIS (version 2013.1.1), Seismic Unix (version 4.2), Shearwater Reveal (version 2019), and python were used to process SEG-Y data and extract navigation data. The processing flows and scripts used are summarized below and in the following processing steps.
    (1.) The SIOSEIS script sio_renum read the raw SEG-Y files, extracted the envelope-detected trace, renumbered shots starting from one, and wrote out new SEG-Y files. The original shot numbers, which were assigned by SonarWiz sequentially over the duration of an acquisition session despite SEG-Y file changes, are preserved in the raw SEG-Y data.
    (2.) If navigation was absent or had spurious coordinates in the SEG-Y trace headers, Hypack raw navigation was merged with trace headers using the Reveal software DBMerge tool based on year seconds derived from the SEG-Y trace headers and the raw Hypack data. This step was done for line13 (l13f1) through line 16 (l16f3) and lines 54 (l54f1) through line 56 (l56f4). For some of these SEG-Y filles (L14F3, L15F3, and L56F3) the Hypack files did not record positions exactly at the beginning or end of the SEG-Y files. These shots that had no position were eliminated.
    (3.) Lines 13 (l13f1) through line 56 (l56f4) required a layback shift to be applied with Reveal software. All other files skipped this step. The Reveal flow read_segy called the following modules: SegyTapeRead read the traces. HeaderMath and UTMLatLong converted the navigation reference point lat/lon positions from seconds of arc to decimal degrees, projected them to UTM Zone 19N WGS 84 meters, and wrote each to new header words (NRP_LAT, NRP_LON, NRP_X, and NRP_Y). DBWrite wrote the UTM positions for each shot to an internal Reveal database table '*.shots.raw.db'. Finally, Output wrote the traces to a new file '*.seis' in the internal Reveal format. The custom Python module ShotlineLayback (developed by Nathan Miller of USGS-WHCMSC) defined the horizontal offset between the GPS antenna and the SB-512i transducers (approximately 30.8 m astern). The algorithm interpolated a sail line from the navigation reference point positions (NRP_X and NRP_Y), then computed layback positions for the SB-512i shots by translating them back along the sail line by the total offset, and wrote the calculated layback positions to new header words (SRC_X, SRC_Y, REC_X, REC_Y). A limitation of the ShotlineLayback module is the inability to layback source shot/receiver locations that would have occurred prior to the start of the interpolated sail line (i.e. it does not project the sail line backward). Consequently, lines 13 (l13f1) through line 56 (l56f4) start at shot 16. UTMLatLong converted the layback positions from UTM Zone 19N WGS 84 meters to decimal degrees and wrote each to new header words (NRP_LAT, NRP_LON, SRC_LAT, SRC_LON, REC_LAT, and REC_LON). HeaderMath converted the layback REC_LAT and REC_LON values from decimal degrees to seconds of arc with a scalar of 100, and set header words for navigation coordinate units (geographic seconds of arc with scalar) and time basis code (UTC). Output wrote the processed traces to a new SEG-Y files in which the trace header words SRC_X, SRC_Y, REC_X, and REC_Y represent the calculated layback coordinates.
    (4.) The SIOSEIS script sio_medianstk, run on all files, applied a median stack of two-trace gathers (two shots) where a percentage (50 percent) of the trace values furthest from the median value were summed. For each time sample, trace values within the two-trace gather are examined and the median value is determined by sorting the values. This was done to minimize noise introduced when the boomer system was operated simultaneously. The noise reduction simplified automatic sea-floor (water bottom) picking conducted prior to swell filtering in step 6. New SEG-Y files were written with the shot numbers reduced by a factor of two.
    (5.) A Seismic Unix script read512i was used to read the median stacked SEG-Y files, extract the cataraft or the layback corrected coordinates, and write a Seismic Unix file. Along with the extracted coordinates, other SEG-Y trace header information, including shot number, year, Julian day, and time of day (UTC) were extracted. Header information from each SEG-Y file was saved to text files after an AWK (no version) filter was used to maintain the first and last shots, shots at multiples of 500 and shots with unique navigation coordinates. Geographic coordinates (WGS 84) were converted to UTM zone 19 N coordinates (WGS 84) using Proj (version 4.6.0). End shots and shots at multiples of 500 may not have unique navigation coordinates. Separate text files containing the first and last shots and even 500 shot intervals were also saved. A 500 shot interval was chosen because it corresponds to the annotation interval provided along the top of the seismic-reflection profile images. Read512i called a Python script 512itoSQL_19002.py, written by Wayne Baldwin, which imported the CSV files to a Spatialite (version 4.3.0) enabled SQLite (version 3.21.0) database, creating three tables containing point geometries for the unique and 500 shotpoint navigation and trackline features.
    (6.) The SIOSEIS script siothresh_pltwbt called the process wbt that was used to predict water-bottom times from the envelope SEG-Y traces in each file and write the predicted two-way travel times to a trace header. Files 209F1 and l279f1 skipped picking the water-botom time for the first 4 shots to avoid noisy traces. As a result, the processed files begin at shot 5. A top mute was applied to removewater-column noise and a amplitude threshold set to pick the water-bottom time. To apply a static shift and remove the effect of heave of the cataraft, the SIOSEIS process swell was used to apply a 21-trace smoothing filter to the water bottom picks. Swell computes the average water bottom time of a group of traces, then shifts the middle trace of the group by the difference between the middle trace water bottom time and the average water bottom time. Not all files were processed to remove heave if the sea state was calm enough to eliminate this step. The files that include this step have file names *_s.sgy for SEG-Y files and include the notation "Swell Filter" in the figure title for the PNG image files. These process steps and all subsequent process steps were conducted by the same person - David S. Foster. Person who carried out this activity:
    U.S. Geological Survey
    Attn: David S. Foster
    Geologist
    384 Woods Hole Rd.
    Woods Hole, MA

    (508) 548-8700 x2271 (voice)
    (508) 457-2310 (FAX)
    dfoster@usgs.gov
    Date: 18-May-2022 (process 2 of 3)
    PROCESS STEP 2:
    The SB-512i 500 shot and trackline features were added (Add Data) into ArcGIS Pro (version 2.4.1) from the SQLite database, then exported (Right click on database feature class > Data > Export Feature) to the new Esri polyline shapefiles '2019-002-FA_SB512i_sht500.shp' and '2019-002-FA_SB512iTracklines.shp', respectively. This step was original done on 20191218 but was redone in May 2022 to correct for missing shapefile attributes that was noted during the data release review. This correction does not affect the subsequent prcoessing step.
    Date: 18-Dec-2019 (process 3 of 3)
    PROCESS STEP 3:
    The Seismic Unix script Plot512i created variable density postscript plots of the seismic profiles showing two-way travel time (seconds) along the y-axis (left margin) and shots along profile (labeled at 500 shot intervals) on the x-axis (along top of profile). The postscript images were converted to 200 dpi portable network graphic (PNG) images using ImageMagick (version 6.9.9-40). The plots are labeled along the bottom of the X axis. Plots with fewer than approximately 1000 traces may have truncated labels.
  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 - SEG Technical Standards Committee: Society of Exploration Geophysicists, Tullsa, OK.

    Online Links:

    Pendleton, E.A., Baldwin, W.E., Barnhardt., W.A., Ackerman, S.D., Foster, D.S., Andrews, B.D., and Schwab, W.C., 2013, Shallow Geology, Sea-floor Texture, and Physiographic Zones of the Inner Continental Shelf from Nahant to Northern Cape Cod Bay, Massachusetts: Open-File Report 2012-1157, U.S. Geological Survey, Coastal and Marine Geology Program, Woods Hole Coastal and Marine Science Center, Woods Hole, MA.

    Online Links:

    Andrews, B.D., Ackerman, S.D., Baldwin, W.E., and Barnhardt, W.A., 2010, Geophysical and Sampling Data from the Inner Continental Shelf: Northern Cape Cod Bay, Massachusetts: Open-File Report 2010-1006, U.S. Geological Survey, Coastal and Marine Geology Program, Woods Hole Coastal and Marine Science Center, Woods Hole, MA.

    Online Links:

    Ackerman, Seth D., Foster, David S., Danforth, William W., and Huntley, Emily C., 2019, High-resolution geophysical and sampling data collected off Town Neck Beach in Sandwich, Massachusetts, 2016: data release DOI:10.5066/P9HZHXXV, U.S. Geological Survey, Reston, VA.

    Online Links:

    Other_Citation_Details:
    Suggested citation: Ackerman S.D., Foster D.S., Danforth W.W., and Huntley, E.C., 2019, High-resolution geophysical and sampling data collected off Town Neck Beach in Sandwich, Massachusetts, 2016: U.S. Geological Survey data release, https://doi.org/10.5066/P9HZHXXV.

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?
    The EdgeTech SB-512i subbottom profiler was mounted on a catamaran raft that was towed on the sea surface from the starboard stern section of the M/V Warren Jr. The transducers were approximately 0.5 m below the water line, and approximately 30.8 meters astern of the DGPS antenna mounted on the acquisition van. Navigation data for the SB-512i were collected using a DGPS receiver mounted on the catamaran except for periods when the receiver malfunctioned, lines 13 (l13f1) through 56 (l56f4). For these lines, the navigation source was the Proflex DGPS receiver mounted on the acquisition van and layback positioning of the transducer relative to the GPS antenna was calculated during processing. Positioning data were recorded using SonarWiz 7 (version 7.04.04) acquisition software, which logged coordinates to individual trace headers in SEG-Y format except for lines 13 (l13f1) through line 16 (l16f3) and lines 54 (l54f1) through line 56 (l56f4) when the navigation feed to SonarWiz failed or provided spurious coordinates. For these files, the position and time were derived from the Hypack raw files and merged using Shearwater Reveal software (v. 2019) using year seconds derived from the SEG-Y trace headers. DGPS horizontal positional accuracy is assumed to be within 3 m.
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
    Sections of tracklines where navigation was recorded but no seismic data were logged are not included such as during testing, some turns, and very short files.
  5. How consistent are the relationships among the observations, including topology?
    Chirp seismic-reflection data were collected from August 1 through 29. '2019-002-FA_SB512i_sht500.shp' contains the first (1, 5, 16, or 92), last (x), and 500-interval shotpoints for each seismic trackline, and '2019-002-FA_SB512i_shtnav.csv' contains all unique shot point navigation. The attribute fields 'LineName' and 'ImageName' for each polyline feature in '2019-002-FA_SB512iTracklines.shp' correspond to the SEG-Y data files in '2019-002-FA_SB512i_SegyData.zip' and the PNG profile images in "2019-002-FA_SB512i_Images.zip", respectively. One SEG-Y file, and PNG image exists for each feature. Processed seismic data were converted to PNG format for ease of seismic trace display. Quality control was conducted during processing.

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 Public domain data from the U.S. Government are freely distributable with proper metadata and source attribution. Please recognize the U.S. Geological Survey as the originator of the dataset.
  1. Who distributes the data set? (Distributor 1 of 1)
    Seth Ackerman
    U.S. Geological Survey
    Geologist
    384 Woods Hole Rd.
    Woods Hole, MA
    USA

    508-548-8700 x2315 (voice)
    508-457-2310 (FAX)
    sackerman@usgs.gov
  2. What's the catalog number I need to order this data set? USGS data release of EdgeTech SB512i chirp seismic-reflection data collected in Cape Cod Bay during USGS field activity 2019-002-FA: includes '2019-002-FA_SB512i_sht500.shp' containing the first, last and 500-interval shotpoint locations, '2019-002-FA_SB512i_shtnav.csv' containing unique shot point locations, '2019-002-FA_SB512iTracklines.shp' containing trackline features, '2019-002-FA_SB512i_Images.zip' containing 616 PNG images named according to line convention, '2019-002-FA_SB512i_SegyData.zip' containing 616 SEG-Y files of the processed traces, the browse graphic 2019-002-FA_SB512iTracklines_browse.jpg, and Federal Geographic Data Committee (FGDC) Content Standards for Digital Geospatial Metadata (CSDGM) metadata file '2019-002-FA_SB512i_meta.xml'. These datasets can be downloaded individually (see the Digital Transfer Option section).
  3. What legal disclaimers am I supposed to read?
    Neither the U.S. Government, the Department of the Interior, nor the USGS, nor any of their employees, contractors, or subcontractors, make any warranty, express or implied, nor assume any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or process disclosed, nor represent that its use would not infringe on privately owned rights. The act of distribution shall not constitute any such warranty, and no responsibility is assumed by the USGS in the use of these data or related materials. Although these data and associated metadata have been reviewed for accuracy and completeness and approved for release by the U.S. Geological Survey (USGS), and have been processed successfully on a computer system at the USGS, no warranty expressed or implied is made regarding the display or utility of the data for other purposes, nor on all computer systems, nor shall the act of distribution constitute any such warranty. The USGS or the U.S. Government shall not be held liable for improper or incorrect use of the data described and/or contained herein. Any use of trade, firm, or product names is for descriptive purposes only and does not imply endorsement by the U.S. Government.
  4. How can I download or order the data?
  5. What hardware or software do I need in order to use the data set?
    To utilize these data, the user must have software capable of reading shapefiles, CSV files, PNG images, and/or SEG-Y seismic trace files.

Who wrote the metadata?

Dates:
Last modified: 18-Jul-2022
Metadata author:
U.S. Geological Survey
Attn: David S. Foster
Geologist
384 Woods Hole Rd.
Woods Hole, MA

(508) 548-8700 x2271 (voice)
(508) 457-2310 (FAX)
dfoster@usgs.gov
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)
This page is <https://cmgds.marine.usgs.gov/catalog/whcmsc/DRB_data_release/DRB_P99DR4PN/2019-002-FA_SB512i_meta.faq.html>
Generated by mp version 2.9.51 on Mon Sep 19 09:45:24 2022