Survey lines along which seismic reflection data were collected in 2016 by the U.S. Geological Survey off Town Neck Beach in Sandwich, Massachusetts, during field activity 2016-017-FA (polyline shapefile)

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

Frequently anticipated questions:


What does this data set describe?

Title:
Survey lines along which seismic reflection data were collected in 2016 by the U.S. Geological Survey off Town Neck Beach in Sandwich, Massachusetts, during field activity 2016-017-FA (polyline shapefile)
Abstract:
Geophysical and geological survey data were collected off Town Neck Beach in Sandwich, Massachusetts, in May and July 2016. Approximately 130 linear kilometers of subbottom (seismic-reflection) and 234-kilohertz interferometric sonar (bathymetric and backscatter) data were collected along with sediment samples, sea floor photographs, and (or) video at 26 sites within the geophysical survey area. Sediment grab samples were collected at 19 of the 26 sampling sites and video and (or) photographic imagery of the sea floor were taken at all 26 sites. These survey data are used to characterize the sea floor by identifying sediment-texture, seabed morphology, and underlying geologic structure and stratigraphy. Data collected during these 2016 surveys are included in this data release: https://doi.org/10.5066/P9HZHXXV.
More information can be found on the websites for the Woods Hole Coastal and Marine Science Center field activities at https://cmgds.marine.usgs.gov/fan_info.php?fan=2016-017-FA and https://cmgds.marine.usgs.gov/fan_info.php?fan=2016-037-FA.
Supplemental_Information:
Seismic profile images (2016-017-FA_SeismicImages.zip) can be hotlinked to their corresponding tracklines in the polyline shapefile. Even 500-shot index markers along the top of the seismic profile images correlate to the positions of 500-shot intervals within the point shapefile '2016-017-FA_SeismicShot500.shp'. The seismic images and shotpoint shapefile can be found online at https://doi.org/10.5066/P9HZHXXV.
  1. How might this data set be cited?
    U.S. Geological Survey, 2019, Survey lines along which seismic reflection data were collected in 2016 by the U.S. Geological Survey off Town Neck Beach in Sandwich, Massachusetts, during field activity 2016-017-FA (polyline shapefile): data release DOI:10.5066/P9HZHXXV, 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., 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.
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -70.494732
    East_Bounding_Coordinate: -70.456610
    North_Bounding_Coordinate: 41.786529
    South_Bounding_Coordinate: 41.761278
  3. What does it look like?
    https://www.sciencebase.gov/catalog/file/get/5c926dbfe4b0938824573d55/?name=2016-017-FA_SeismicTracklines_browse.jpg (JPEG)
    Knudsen 3202 trackline navigation off Town Neck Beach in Sandwich, Massachusetts.
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 17-May-2016
    Ending_Date: 23-May-2016
    Currentness_Reference:
    Ground condition of survey dates: 20160517-20160523. No geophysical data were collected on May 18 (JD 139), 21 (JD 142), and 22 (JD 143), 2016 ; see Completeness_Report for more information.
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: vector digital data
  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 (62)
    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 D_WGS_1984.
      The ellipsoid used is WGS_1984.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257224.
  7. How does the data set describe geographic features?
    2016-017-FA_SeismicTracklines
    Trackline for seismic profiles (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
    Survey line/seismic data file name; generally in the format l###f@ where ### is the name of the trackline along which seismic data were collected, and @ is the file iteration (a file iteration greater than 1 indicates that the survey line was split into multiple files during acquisition). For example, survey line 38 was interrupted 5 minutes into the line and then continued with recording to a new seismic file; therefore, there are two tracklines for line 38: "l38f1" and "l38f2". (Source: U.S. Geological Survey) String up to 10 characters
    ImageName
    Name of seismic profile image used as hyperlink. ImageName is in the format 2016017FA_Knudsen_LineName_s.png, where 2016017FA_Kundsen is the field activity identifier followed by the sonar system( Knudsen), and _s indicates that the image is the swell-filtered seismic profile. (Source: U.S. Geological Survey) String up to 35 characters
    Shot_st
    First shot number in seismic profile (Source: U.S. Geological Survey)
    Range of values
    Minimum:1
    Maximum:1
    Units:shot
    Resolution:1
    Shot_end
    Last shot number in seismic profile (Source: U.S. Geological Survey)
    Range of values
    Minimum:277
    Maximum:5091
    Units:shot
    Resolution:1
    Year
    Calendar year data were collected (Source: U.S. Geological Survey)
    Range of values
    Minimum:2016
    Maximum:2016
    Units:Calendar year
    Resolution:1
    DayUTC_st
    Start Julian day and UTC time data were collected (DAY:HH:MM:SS), where Julian day is the integer number representing the interval of time in days since January 1 of the year of collection. (Source: U.S. Geological Survey) String up to 12 characters
    DayUTC_end
    End Julian day and UTC time data were collected (DAY:HH:MM:SS), where Julian day is the integer number representing the interval of time in days since January 1 of the year of collection. (Source: U.S. Geological Survey) String up to 12 characters
    SurveyID
    WHCMSC field activity identifier (e.g. "2016-017-FA" where 2016 is the survey year, 017 is survey number of that year, and FA is Field Activity) (Source: USGS) String up to 11 characters
    VehicleID
    Name of the survey vessel used for data collection (Source: USGS) String up to 10 characters
    DeviceID
    Name of the sonar device used to collect seismic-reflection data (Source: USGS) String up to 20 characters
    Length_km
    Length of the seismic survey line in kilometers (UTM Zone 19N, WGS 84) as calculated in the SQLite database. (Source: USGS)
    Range of values
    Minimum:0.27
    Maximum:3.43
    Units:kilometers
    Resolution:0.01
    Entity_and_Attribute_Overview:
    These tracklines, in conjunction with the seismic shotpoints (500-shot interval and unique), can be used with the PNG seismic-reflection images. These tracklines can be hyperlinked to the corresponding PNG seismic-reflection images in ArcGIS. The 500-shotpoint intervals correspond to the x-axis ticks on the PNG images.
    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)
    • U.S. Geological Survey
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
    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

Why was the data set created?

The seismic data associated with these navigation tracklines are used to define the sea-floor morphology and sediment thickness as part of a mapping project in coastal Massachusetts. This dataset contains trackline navigation for approximately 130 linear km of chirp seismic-reflection data collected by the U.S. Geological Survey during survey 2016-017-FA off Town Neck Beach in Sandwich, Massachusetts. This information can help spatially correlate the subbottom data with other data in the GIS.

How was the data set created?

  1. From what previous works were the data drawn?
    Knudsen 3202 seismic data (source 1 of 1)
    U.S. Geological Survey, Unpublished Material, raw seismic navigation.

    Type_of_Source_Media: disc
    Source_Contribution:
    Seismic-reflection data acquisition 2016-017-FA: Seismic profile data were collected using a Knudsen Engineering Limited (KEL) Chirp 3202 system with transducers mounted on a rigid pole on the starboard side of the R/V Rafael of Woods Hole, MA. Knudsen SounderSuite seismic acquisition software was used to control the 3202 system, digitally log trace data in the SEG-Y Revision 1 format (Norris and Faichney, 2002), and record DGPS navigation coordinates to the SEG-Y trace headers in arc seconds. The transducer draft was 0.5 m below the water surface, and the draft offset was accounted for during data acquisition. Navigation coordinates and water depths from the 200-kHz channel were logged together in ASCII formatted files for each survey line. Data were acquired at a peak frequency of 3.5 kHz, a 0.25-second fire inverval, a 36-38 microsecond sample interval, and record lengths between 26 and 130 milliseconds. A total of 128 km of seismic data were collected. DGPS navigation was supplied by a Hemisphere receiver with the antenna mounted on the aft of the R/V Rafael's cabin just port of the centerline. Seismic-reflection data were processed using SIOSEIS (Henkart, 2011) and Seismic Unix (Cohen and Stockwell, 2011).
  2. How were the data generated, processed, and modified?
    Date: 2016 (process 1 of 7)
    SIOSEIS (version 2015.3.1) was used to read SEG-Y files, renumber shots starting from one, and write out new SEG-Y files. The original shot numbers, which were assigned by SounderSuite sequentially over the duration of an acquisition session despite SEG-Y file changes, are preserved in the raw SEG-Y data. This process step and all subsequent process steps, unless otherwise noted, were performed by the same person - David Foster. Person who carried out this activity:
    David Foster
    U.S. Geological Survey
    Geologist
    384 Woods Hole Rd
    Woods Hole, MA
    USA

    508-548-8700 x2271 (voice)
    508-457-2310 (FAX)
    dfoster@usgs.gov
    Date: 2016 (process 2 of 7)
    SIOSEIS was used to insert Kingdom Suite corrected sea-floor values into the SEG-Y trace headers, minimize the effect of sea surface heave using process 'swell', and write SEG-Y files for creation of browse images and digital interpretation.
    Date: 2016 (process 3 of 7)
    Seismic Unix (version 4.2) was used to read all processed SEG-Y files, write a Seismic Unix file, and extract SEG-Y trace header information, including shot number, longitude, latitude, year, Julian day, and time of day (UTC). Geographic coordinates (WGS 84) were converted to UTM Zone 19N coordinates (WGS 84) using PROJ (version 4.9.3). Header information from each SEG-Y file was saved to CSV text files after an AWK filter was used to maintain the first and last shots, shots at multiples of 500, and shots with unique navigation coordinates. End shots and shots at multiples of 500 may not have unique navigation coordinates. A 500-shot interval was chosen because it corresponds to the annotation interval provided along the top of the seismic-reflection profile PNG images. In the process of extracting the navigation from the SEG-Y files and saving it to the CSV files, a temporary plot was made to visually check the navigation fixes and identify if there were any issues or extreme outliers.
    Date: 22-Feb-2019 (process 4 of 7)
    A Python script (3202intoSQL_2016-017-FA.py), originally written by Wayne Baldwin, was used to import the CSV text files containing navigation information into the SpatiaLite (version 4.3.0a) enabled SQLite (version 3.27.1) database. The geographic locations for each shotpoint were used to create point and line feature geometries in the SQL database. Additional survey information is populated in the SQL database including identifiers for the survey name, vessel, and seismic equipment used. This process step and all subsequent process steps were performed by the same person - Seth Ackerman. Person who carried out this activity:
    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
    Date: 01-Mar-2019 (process 5 of 7)
    An Esri polyline shapefile was exported directly from the SQLite database using spatialite-tools (version 4.3.0_3).
    spatialite_tool -e -shp 2016-017-FA_SeismicTracklines -d ./2016-017-FA-SQLdb.sqlite -t SeisTrack_ln -g geom_t -c CP1252 -s 4326 --type LINESTRING
    
    Date: Mar-2019 (process 6 of 7)
    XTools Pro (version 17.0.7234) for ArcGIS Desktop was used (Table Operations - Table Restructure) to clean up the attribute headings in the polyline shapefile's attribute table. The ImageName field was updated to reflect the renamed seismic image names with the field activity prepended to the line name.
    Date: 07-Aug-2020 (process 7 of 7)
    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, Jack, and Stockwell, John, 2011, CWP/SU: Seismic Un*x Release No. 4.2: Center for Wave Phenomena - Colorado School of Mines, Golden, CO.

    Online Links:

    Henkart, Paul, 2011, SIOSEIS: Scripps Institution of Oceanography, University of California - San Diego, LaJolla, CA.

    Online Links:

    Norris, Michael W., and Faichney, Alan K., 2002, SEGY Rev.1 Data Exchange Format 1: Society of Exploration Geophysicists, Tulsa, OK.

    Online Links:


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?
    Field activity 2016-017-FA: Differential Global Positioning System (DGPS) navigation data were acquired with a Hemisphere DGPS receiver. Navigation data were sent to the Knudsen SounderSuite acquisition application, which logged the coordinates to individual trace headers in the Society of Exploration Geophysicists Y (SEG-Y) Revision 1 format (Norris and Faichney, 2002). A 2-m horizontal offset between the seismic transducers and the DGPS receiver was not accounted for during data acquisition, and resulting positional accuracy is assumed to be better than 10 m.
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
    Sections of survey data where navigation was recorded but no seismic data were logged are not included. Time gaps occurred during this field activity on days when no survey data were collected due to bad weather, rough seas, and stops in surveying for equipment issues (on May 18, 21, and 22, 2016). Any sections of seismic data that were collected outside the survey area (such as short segments during the transit to or from the dock at the Sandwich Marina) were not processed and are therefore not included in this dataset.
  5. How consistent are the relationships among the observations, including topology?
    Any spurious data points were removed during processing. For each seismic trackline there is one seismic-profile image that is hyperlinked by the field 'ImageName'. No duplicates exist. There is no data for what would be lines 8 and 41.

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 redistributable with proper metadata and source attribution. Please recognize the U.S. Geological Survey as the source of this information.
  1. Who distributes the data set? (Distributor 1 of 1)
    U.S. Geological Survey-ScienceBase
    Denver Federal Center, Building 810, Mail Stop 302
    Denver, CO
    USA

    1-888-275-8747 (voice)
    sciencebase@usgs.gov
  2. What's the catalog number I need to order this data set? USGS data release 2016-017-FA seismic trackline navigation from offshore of Town Neck Beach in Sandwich, Massachusetts. This dataset contains a shapefile (2016-017-FA_SeismicTracklines.shp), browse graphic (2016-017-FA_SeismicTracklines_browse.jpg) and metadata files in standard formats.
  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. Any use of trade, product, or firm 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?
    This dataset contains data available in shapefile format. The user must have software capable of reading shapefile format to use the shapefile. Free geospatial data viewers can be found online.

Who wrote the metadata?

Dates:
Last modified: 07-Aug-2020
Metadata author:
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
Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)

This page is <https://cmgds.marine.usgs.gov/catalog/whcmsc/SB_data_release/DR_P9HZHXXV/2016-017-FA_SeismicTracklines_meta.faq.html>
Generated by mp version 2.9.50 on Tue Sep 21 18:19:02 2021