Archive of Digital Boomer Subbottom Data Collected During USGS Cruise 05FGS01, Offshore East-Central Florida, July 17-29, 2005

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

Frequently anticipated questions:


What does this data set describe?

Title:
Archive of Digital Boomer Subbottom Data Collected During USGS Cruise 05FGS01, Offshore East-Central Florida, July 17-29, 2005
Abstract:
In July of 2005, the U.S. Geological Survey (USGS), in cooperation with the Florida Geological Survey (FGS), conducted a geophysical survey of the Atlantic Ocean offshore of Florida's east coast from Flagler Beach to Daytona Beach. This report serves as an archive of unprocessed digital boomer subbottom data, trackline maps, navigation files, GIS information, and formal FGDC metadata. Filtered and gained digital images of the seismic profiles are also provided. The archived trace data are in standard Society of Exploration Geophysicists (SEG) SEG Y revision 0 format (Barry and others, 1975) and may be downloaded and processed with commercial or public domain software such as Seismic Unix (SU). Example SU processing scripts and USGS software for viewing the SEG Y files (Zihlman, 1992) are also provided. These data are also available for viewing using GeoMapApp (<http://www.geomapapp.org/>) and Virtual Ocean (<http://www.virtualocean.org/>) multi-platform open source software. In addition, the SEG Y files can also be downloaded from the USGS Coastal and Marine Geoscience Data System (<http://cmgds.marine.usgs.gov>)
Supplemental_Information:
The USGS Saint Petersburg Coastal and Marine Science Center (SPCMSC) - St. Petersburg, FL, assigns a unique identifier to each cruise or field activity. For example, 05FGS01 tells us the data were collected in 2005 for the Florida Geological Survey (FGS) cooperative agreement and the data were collected during the first field activity for that project in that calendar year. Refer to <http://walrus.wr.usgs.gov/infobank/programs/html/definition/activity.html> for a detailed description of the method used to assign the cruise ID. The naming convention used for each subbottom line is as follows: yye##a, where 'yy' are the last two digits of the year in which the data were collected, 'e' is a 1-letter abbreviation for the equipment type (for example, b for boomer), '##' is a 2-digit number representing a specific track, and 'a' is a letter representing the section of a line if recording was prematurely terminated or rerun for quality or acquisition problems.The boomer subbottom processing system consists of an acoustic energy source that is made up of capacitors charged to a high voltage and discharged through a transducer in the water. The transducer is towed on a sled floating on the water surface and when discharged emits a short acoustic pulse, or shot, that propagates through the water column and shallow stratigraphy below. The acoustic energy is reflected at density boundaries (such as the seafloor or sediment layers beneath the seafloor), detected by the receiver (hydrophone streamer), and recorded by a PC-based seismic acquisition system. This process is repeated at timed intervals (for example, 0.5 s) and recorded for specific intervals of time (for example, 100 ms). In this way, a 2-D vertical image of the shallow geologic structure beneath the ship track is produced.An Applied Acoustic Engineering CSP 300 provided 100 Joules of energy per shot. Reflected energy was received by a Benthos Mesh 15-m-long streamer and recorded by Triton Elics International, Inc. (TEI) Delph Seismic v. 2.7 acquisition software. The streamer contains 10 hydrophones evenly spaced every 0.305 m. The streamer was positioned directly behind the research vessel (parallel to the boomer sled), with a lateral separation of approximately 7 m. Refer to figure 1 included with this archive for a diagram of the acquisition geometry. The sample frequency of the data was 24 kHz, and record length was 100 ms. The shot spacing was highly variable; however, based on survey speeds of 3 knots and a shot rate of every 0.5 s, shot spacing was about 0.514 m.The unprocessed seismic data are stored in SEG Y rev. 0, integer, Motorola format, which is a standard digital format that can be read and manipulated by most seismic processing software packages (Barry and others, 1975). The SEG Y formatted trace files have a .tra extension.The printable profiles provided here are GIF images that were filtered and gained using Seismic Unix software. The processed SEG Y data were exported to Chesapeake Technology, Inc. (CTI) SonarWeb software to produce a geospatially interactive version of the profile that allows the user to obtain a geographic location and depth from the profile for a given cursor position on the profile; this information is displayed in the status bar of the browser. Please note that clicking on the profile image switches it to "Expanded View" (a compressed image of the entire line) and cursor tracking is not available in this mode. NOTE: The only supported Web browsers that properly display all features of the geospatial profiles are Internet Explorer 6 or greater for Windows and Firefox 3.6 or greater for all platforms. PC Instructions: For both browsers, the status bar and JavaScript must be enabled. If using Internet Explorer 6 or greater, you must disable scripts/Active X controls. To do this, right click the information bar (found at the top of the page), left click "Allow Blocked Content...", and then select "Yes". Use of other browsers may result in spurious or no information given in the status window. Firefox may be downloaded at <http://www.mozilla.org/products/firefox>. Macintosh Instructions (Firefox Only): From the Menu Bar go to Preferences > Content (tab) > Checkmark "Enable JavaScript"> Click Advanced... > Checkmark "Change Status Bar Text". Verify that the status bar is enabled by selecting View from the Menu Bar and looking for a checkmark next to "Status Bar"; if the check is missing, highlight and select the text to activate the bar.
  1. How might this data set be cited?
    Forde, Arnell S., Dadisman, Shawn V., Wiese, Dana S., and Phelps, Daniel C., 2012, Archive of Digital Boomer Subbottom Data Collected During USGS Cruise 05FGS01, Offshore East-Central Florida, July 17-29, 2005: U.S. Geological Survey Data Series 647, U.S. Geological Survey, St. Petersburg, FL.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -81.151788
    East_Bounding_Coordinate: -80.832257
    North_Bounding_Coordinate: 29.650501
    South_Bounding_Coordinate: 29.183042
  3. What does it look like?
    http://pubs.usgs.gov/ds/647/maps/cruisenav/05fgs01_location.jpg (JPEG)
    Location map of digital boomer subbottom data collected during USGS Field Activity 05FGS01. This map was created at a scale of 1:321,000. Refer to the Lineage section below for the trackline map creation process.
    http://pubs.usgs.gov/ds/647/profiles/printable/ (GIF)
    Directory containing printable images of all subbottom profiles.
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 17-Jul-2005
    Ending_Date: 25-Jul-2005
    Currentness_Reference:
    Data collection interval
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: Archive for Subbottom Profile Data
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
      Indirect_Spatial_Reference:
      Horizontal X and Y locations (latitude and longitude and Zone 17 UTM coordinates) for each shot are provided as ASCII text files, along with the date and time (UTC) the shot was recorded.
    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 WGS84.
      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.25722210100002.
  7. How does the data set describe geographic features?
    05fgs01.txt, s05fgs01.txt, and 05fgs01_s.txt
    Shotpoint navigation files (Source: Society of Exploration Geophysicists (SEG) Y headers (<http://www.seg.org/publications/tech-stand>).)
    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 coordinate (Zone 17) (Source: Universal Transverse Mercator Geographic Coordinate System)
    Range of values
    Minimum:485419
    Maximum:516280
    Units:meters
    UTMY
    UTM-Y coordinate (Zone 17) (Source: Universal Transverse Mercator Geographic Coordinate System)
    Range of values
    Minimum:3228278
    Maximum:3280044
    Units:meters
    Line
    Trackline number (Source: U.S. Geological Survey) The naming convention used for each subbottom line is as follows: yye##a, where 'yy' are the last two digits of the year in which the data were collected, 'e' is a 1-letter abbreviation for the equipment type (for example, b for boomer), '##' is a 2-digit number representing a specific track, and 'a' is a letter representing the section of a line if recording was prematurely terminated or rerun for quality or acquisition problems.
    Shot
    Shotpoint number (Source: U.S. Geological Survey)
    Range of values
    Minimum:1
    Maximum:20000
    Lon
    Longitude (decimal degrees) (Source: World Geodetic System 1984 Geographic Coordinate System)
    Range of values
    Minimum:-81.15062
    Maximum:-80.832379
    Units:decimal degrees
    Lat
    Latitude (decimal degrees) (Source: World Geodetic System 1984 Geographic Coordinate System)
    Range of values
    Minimum:29.183103
    Maximum:29.650282
    Units:decimal degrees
    YEAR
    Year (Source: U.S. Geological Survey)
    Range of values
    Minimum:2005
    Maximum:2005
    DOY:HR:MIN:SEC
    Day of year:hour:minute:second (Source: U.S. Geological Survey) Day of year, hour, minute and second of data acquisition
    Entity_and_Attribute_Overview:
    Binary data file: Trace data are available as binary files in SEG Y format. These files have a .tra extension and range in size from 4.3 to 110 MB. These data can be found by going to <http://pubs.usgs.gov/ds/647/segy/>
    Entity_and_Attribute_Overview:
    Graphic image file: Printable versions of the subbottom profiles are available as GIF images, links to these images can be found on the Profiles page or by going to <http://pubs.usgs.gov/ds/647/profiles/printable/>.
    Entity_and_Attribute_Overview:
    Navigation file: Navigation files are available as ASCII text files. Provided are raw (unprocessed) shotpoint navigation files (05b**.txt), processed shotpoint navigation (05fgs01.txt), processed 500-shot-interval location (s05fgs01.txt), and a start of line file (05fgs01_s.txt). Fields/Attributes [FID, Shape] marked above with an asterisk (*) were created by ESRI ArcGIS and are used exclusively by the shapefiles created from the aforementioned .txt files; these fields are not included in the original navigation files. All remaining attributes listed in the above section that do not have an accompanying asterisk are found in 05fgs01.txt, s05fgs01.txt, and 05fgs01_s.txt. Raw and processed navigation data files can be found by going to <http://pubs.usgs.gov/ds/647/nav/>.
    Entity_and_Attribute_Overview:
    GIS file: The GIS project used to create the trackline maps is provided as a .zip file composed of ESRI map documents, shapefiles, and metadata.
    Entity_and_Attribute_Detail_Citation: Information is derived from SEG Y headers.

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
    • Shawn V. Dadisman
    • Dana S. Wiese
    • Daniel C. Phelps
  2. Who also contributed to the data set?
    Funding and (or) support for this study was provided by the USGS Coastal and Marine Geology Program and FGS. This document was improved by the reviews of Lisa Robinson (USGS) and Marilyn Montgomery (Jacobs Technology Inc.) of the USGS - St. Petersburg, FL.Disc Image Credit: Schmaltz, Jeff, MODIS Rapid Response Team at the NASA Goddard Space Flight Center, 2004, UnitedStates.A2004106.1855.500m.jpg. Also available on-line at <http://eoimages.gsfc.nasa.gov/ve/6886/UnitedStates.A2004106.1855.500m.jpg>
  3. To whom should users address questions about the data?
    Arnell S. Forde
    U.S. Geological Survey
    Geologist
    600 4th Street South
    Saint Petersburg, FL
    USA

    (727) 803-8747 ext. 3111 (voice)
    aforde@usgs.gov

Why was the data set created?

The data archived here were collected under a cooperative agreement between the Florida Geological Survey and the USGS.

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: 2011 (process 1 of 6)
    Boomer processing: The SEG Y data were processed with Seismic Unix to produce GIF images of the seismic profiles included in this report. A representative boomer processing sequence consisted of (1) running a bandpass filter of 300-500-2500-3000 Hz, (2) applying automatic gain control, (3) displaying PostScript, and (4) converting of PostScript image to a GIF image.All the processed SEG Y data were then exported to CTI SonarWeb software to produce a geospatial version of each profile that allows the user to obtain a geographic location and depth for a given cursor position on the profile. Refer to the Supplemental Information section above for details on how to use the geospatial profiles. Person who carried out this activity:
    Arnell S. Forde
    U.S. Geological Survey
    Geologist
    600 4th Street South
    St. Petersburg, FL

    (727) 803-8747, ext. 3111 (voice)
    aforde@usgs.gov
    Data sources used in this process:
    • SEG Y
    Data sources produced in this process:
    • printable/SEG Y.gif
    • geospatial/SEG Y.jpg
    Date: 2011 (process 2 of 6)
    Navigation processing: Shotpoint navigation, start of line, and 500-shot-interval location files were extracted using Seismic Unix software and output as ASCII text files; they were then processed with PROJ.4.7.0 (<http://trac.osgeo.org/proj/>) to generate UTM coordinates from latitude and longitude coordinates. Text files for each seismic line were concatenated into two comma-delimited text files (for use with ESRI software), one containing unique shotpoint positions (05fgs01.txt) and another containing the 500-shot-interval locations (s05fgs01.txt); both can be viewed within the nav folder. Person who carried out this activity:
    Arnell S. Forde
    U.S. Geological Survey
    Geologist
    600 4th Street South
    St. Petersburg, FL

    (727) 803-8747, ext. 3111 (voice)
    aforde@usgs.gov
    Data sources used in this process:
    • 05b**.txt
    Data sources produced in this process:
    • 05fgs01.txt
    • s05fgs01.txt
    Date: 2011 (process 3 of 6)
    All concatenated, comma-delimited text files were imported into ArcGIS and saved as either a point or polyline file in the ESRI shapefile format.Trackline map creation: The trackline map was created using ESRI ArcGIS 10 software. The processed navigation file, 05fgs01.txt, was imported into ArcMap 10 and processed using the Points to Lines ArcScript (D. Rathert, <http://arcscripts.esri.com/details.asp?dbid=12702>) to create a line shapefile of the cruise tracklines (05fgs01_trkln). The 500-shot-interval file s05fgs01.txt and the start of line file 05fgs01_s.txt were imported into ArcMap as point shapefiles 05fgs01_shots and 05fgs01_sol. Please refer to the shapefile metadata included in the ArcGIS map document located under the Software section of this archive for additional details. The location map was exported to Adobe Illustrator v. 14 for further editing then later converted into JPEG format by Adobe Dreamweaver v. 10 Build 4117. The map is unprojected (geographic coordinates, WGS84). The interstates layer used on the trackline map was created by ESRI. The USGS is the originator of all other layers used. A map of trackline navigation for each subbottom profile was also produced with CTI SonarWeb software. Please see the ArcGIS readme file for detailed information about the GIS files used in this report. Data sources used in this process:
    • 05fgs01.txt
    • s05fgs01.txt
    • 05fgs01_s.txt
    Data sources produced in this process:
    • 05fgs01_trkln.shp
    • 05fgs01_shots.shp
    • 05fgs01_sol.shp
    Date: 2011 (process 4 of 6)
    Data Series preparation: In addition to the process steps described above, the following steps were taken to produce this Data Series report: the handwritten (<http://pubs.usgs.gov/ds/647/logbooks/handwritten/>) cruise logs were scanned and saved as a PDF file, digital (<http://pubs.usgs.gov/ds/647/logbooks/digital/>) logs were created by A. Forde using the cruise logs and personal accounts of the crew members and saved as PDF files, and an HTML-based format was used to present the various parts of this archive. Person who carried out this activity:
    Arnell S. Forde
    U.S. Geological Survey
    Geologist
    600 4th Street South
    St. Petersburg, FL

    (727) 803-8747, ext. 3111 (voice)
    aforde@usgs.gov
    Date: 24-Jan-2017 (process 5 of 6)
    Keywords section of metadata optimized for discovery in USGS Coastal and Marine Geology Data Catalog. Person who carried out this activity:
    U.S. Geological Survey
    Attn: Alan O. Allwardt
    Contractor -- Information Specialist
    2885 Mission Street
    Santa Cruz, CA

    831-460-7551 (voice)
    831-427-4748 (FAX)
    aallwardt@usgs.gov
    Date: 13-Oct-2020 (process 6 of 6)
    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, J.K., and Stockwell, J.W., Jr., CWP/SU, 2010, Seismic Unix Release 41: A free package for seismic research and processing, Center for Wave Phenomena, Colorado School of Mines.

    Online Links:

    Zihlman, F.N., USGS, 1992, DUMPSEGY V1.0: A program to examine the contents of SEG Y disk-image seismic data: U.S. Geological Survey Open-File Report 92-590.

    Online Links:

    Other_Citation_Details: 28 pages
    Barry, K.M., Cavers, D.A., and Kneale, C.W., 1975, Recommended standards for digital tape formats: Geophysics v. 40, no. 2.

    Online Links:

    Other_Citation_Details: pages 344-352

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. Visual inspection of the images rendered from the data did not show any major anomalies.
  2. How accurate are the geographic locations?
    As the subbottom data were acquired, the position of the vessel was continuously determined by a CSI Wireless DGPS Max receiver, which is accurate within 1 m if WAAS is available, or 3-5 m otherwise. Positions were recorded and written to the trace headers in latitude and longitude coordinates about every 1 s. The approximately 30-m offset between the Boomer shot and GPS was not accounted for during acquisition nor have the ASCII navigation files and trackline map been corrected to reflect the offset. Line navigation maps and geospatial profiles generated with CTI SonarWeb software have been corrected for the GPS offsets.
  3. How accurate are the heights or depths?
    Boomer data are relative to sea level. However, varying recorded static shifts of the data have been known to occur. Therefore, these data are not to be used for bathymetry.
  4. Where are the gaps in the data? What is missing?
    These data are collected along tracklines (2-D) and are therefore inherently incomplete. Geologic details between lines must be inferred. No data were collected for lines 05b02 and 05b19-05b23.
  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. These data are held in the public domain.
Use_Constraints:
The U.S. Geological Survey and Florida Geological Survey (FGS) request to be acknowledged as originators of the data in future products or derivative research.
  1. Who distributes the data set? (Distributor 1 of 1)
    Arnell Forde
    U.S. Geological Survey
    Geologist
    600 4th Street South
    St. Petersburg, FL
    USA

    (727) 803-8747, ext. 3111 (voice)
    aforde@usgs.gov
    Contact_Instructions:
    All of this report is available online. The SEG Y files are downloadable from the Coastal and Marine Geoscience Data System (<http://cmgds.marine.usgs.gov>).
  2. What's the catalog number I need to order this data set? U.S. Geological Survey Data Series 647
  3. What legal disclaimers am I supposed to read?
    This DVD publication was prepared by an agency of the United States Government. Although these data have been 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: The SEG Y standard format (Barry and others, 1975) consists of the following: a 3,600-byte reel identification header, with the first 3,200 bytes consisting of an ASCII header block followed by a 400-byte binary header block, both of which include information specific to line and reel number; a trace data block that follows the reel identification header, with the first 240 bytes of each trace block consisting of the binary trace identification header; and seismic data samples that follow the trace identification header. in format SEG Y rev. 0 Size: 1580
      Media you can order: DVD (format ISO 9660)
      Note: Unix, Linux, DOS, Macintosh
      Data format: The GIS project used to create the trackline maps is composed of map documents, shapefiles, and metadata. Map documents were created with ESRI ArcGIS 10 software. The shapefiles provided may also be viewed using other versions of ESRI desktop software including their free software ArcGIS Explorer (<http://www.esri.com/software/arcgis/explorer/index.html>). in format map document, shapefile, metadata Size: 48
      Network links: http://pubs.usgs.gov/ds/647/software/arc/arc.zip
    • Cost to order the data: None, if obtained online; otherwise, prices vary.

    • Special instructions:
      Publications are available from USGS Information Services, Box 25286, Federal Center, Denver, CO 80225-0046 (telephone: 1-888-ASK-USGS, e-mail: infoservices@usgs.gov).
  5. What hardware or software do I need in order to use the data set?
    Use of SEG Y data requires specialized seismic processing software, such as public domain software Seismic Unix (<http://www.cwp.mines.edu/cwpcodes/index.html>).

Who wrote the metadata?

Dates:
Last modified: 13-Oct-2020
Metadata author:
Arnell Forde
U.S. Geological Survey
Geologist
600 4th Street South
St. Petersburg, FL
USA

(727) 803-8747, ext. 3111 (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/ds-647metadata.faq.html>
Generated by mp version 2.9.50 on Tue Sep 21 18:18:54 2021