Seismic Shotpoint Navigation: USF 100-shot shotpoint navigation of seismic data collected in the Pulley Ridge area

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

Frequently-anticipated questions:

What does this data set describe?

Title:
Seismic Shotpoint Navigation: USF 100-shot shotpoint navigation of seismic data collected in the Pulley Ridge area
Abstract:
These seismic data were collected to infer the paleodepositional environment of Pulley Ridge through seismic facies analysis. Without actual rock cores, remote sensing is the next best tool. It was uncertain if Pulley Ridge represented a drowned reef or paleoshoreline. Through seismic imaging, it was determined from the high-amplitude, level-bedded nature of material in the sub-surface that Pulley Ridge represents several stages of barrier-island development.
  1. How should this data set be cited?

    Jarrett, Brett, Hine, Al, and Locker, Steve, 2005, Seismic Shotpoint Navigation: USF 100-shot shotpoint navigation of seismic data collected in the Pulley Ridge area:.

    Online Links:

    This is part of the following larger work.

    Cross, VeeAnn A. , Twichell, David C. , Halley, Robert B. , Ciembronowicz, Kate T. , Jarrett, Bret D. , Hammar-Klose, Erika S. , Hine, Al C. , Locker, Stan D. , and Naar, Dave F. , 2005, GIS Compilation of Data Collected from the Pulley Ridge Deep Coral Reef Region: Open-File Report 2005-1089, U.S. Geological Survey, Coastal and Marine Geology Program, Woods Hole Science Center, Woods Hole, MA.

    Online Links:

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -83.744921
    East_Bounding_Coordinate: -83.625017
    North_Bounding_Coordinate: 24.892753
    South_Bounding_Coordinate: 24.761096

  3. What does it look like?

  4. Does the data set describe conditions during a particular time period?

    Beginning_Date: 20-Jun-1996
    Ending_Date: 11-Sep-2001
    Currentness_Reference: ground condition

  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 Point data set. It contains the following vector data types (SDTS terminology):

      • Entity point (513)

    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.000000. Longitudes are given to the nearest 0.000000. Latitude and longitude values are specified in Decimal degrees.

      The horizontal datum used is North American Datum of 1983.
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257222.

  7. How does the data set describe geographic features?

    allusf100sht

    FID
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    Shape
    Feature geometry. (Source: ESRI)

    Coordinates defining the features.

    LONGITUDE
    Longitude of the point.

    Range of values
    Minimum:-83.744921
    Maximum:-83.625017
    Units:decimal degrees

    LATITUDE
    Latitude of the point.

    Range of values
    Minimum:24.761096
    Maximum:24.892753
    Units:decimal degrees

    LINE
    Seismic line number along which the shotpoint occurs. (Source: University of South Florida.)

    Range of values
    Minimum:23
    Maximum:48

    SHOT
    Shot point number corresponding to the point. (Source: software generated.)

    Range of values
    Minimum:1
    Maximum:12665

    UTCTIME
    Time the shotpoint was acquired - in UTC. (Source: software generated.)

    character set

    DATE
    Date the navigation point was collected. (Source: Data processor.)

    character set - format month/day/year

    JDAY
    Julian day of the point acquisition. (Source: Data processor.)

    Range of values
    Minimum:172
    Maximum:254

    YEAR
    Year the data point was acquired. (Source: Data processor.)

    Range of values
    Minimum:1996
    Maximum:2001

    Entity_and_Attribute_Overview:
    Lines 47 and 48 were collected in 1996, the remainder of the seismic lines (23-32 and 34) were collected in 2001. The 1996 seismic data were collected with ORE boomer sled, Geopulse power supply (375 joules), ITI streamer, Elics acquisition and processing software, and DGPS. The 2001 seismic data were collected with Huntec boomer sled, Applied Acoustics power supply (375 joules), ITI streamer, Elics acquisition and processing software, and DGPS.

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)

  2. Who also contributed to the data set?

  3. To whom should users address questions about the data?

    Bret Jarrett
    University of South Florida
    Graduate Student
    College of Marine Science
    St. Petersburg, FL 33701

    (727) 553-1183 (voice)
    bjarrett@seas.marine.usf.edu

Why was the data set created?

This GIS layer is provided to enable a correlation between seismic-reflection profile images and their geographic location based on shotpoints.

How was the data set created?

  1. From what previous works were the data drawn?

  2. How were the data generated, processed, and modified?

    (process 1 of 5)
    Navigation was acquired from USF (University of South Florida) in a format suitable for import into an Excel spreadsheet with shotpoint navigation for each seismic line in a separate file.

    (process 2 of 5)
    The individual navigation files were export from excel in to a comma delimited format.

    Person who carried out this activity:

    VeeAnn A. Cross
    U.S. Geological Survey
    Marine Geologist
    384 Woods Hole Rd.
    Woods Hole, MA 02543-1598

    (508) 548-8700x2251 (voice)
    (508) 457-2310 (FAX)
    vatnipp@usgs.gov

    (process 3 of 5)
    The comma delimited navigation was run through an AWK script to extract every 100th shotpoint, but also keeping the first and last shot of each line.

    Person who carried out this activity:

    VeeAnn A. Cross
    U.S. Geological Survey
    Marine Geologist
    384 Woods Hole Rd.
    Woods Hole, MA 02543-1598

    (508) 548-8700x2251 (voice)
    (508) 457-2310 (FAX)
    vatnipp@usgs.gov

    (process 4 of 5)
    These individual shotpoint navigation files were then concatenated together into one file and imported to ArcView as an event theme.

    Person who carried out this activity:

    VeeAnn A. Cross
    U.S. Geological Survey
    Marine Geologist
    384 Woods Hole Rd.
    Woods Hole, MA 02543-1598

    (508) 548-8700x2251 (voice)
    (508) 457-2310 (FAX)
    vatnipp@usgs.gov

    (process 5 of 5)
    This event theme was then converted to a shapefile. Attributes date, jday, and year were added to the existing attribute information.

    Person who carried out this activity:

    VeeAnn A. Cross
    U.S. Geological Survey
    Marine Geologist
    384 Woods Hole Rd.
    Woods Hole, MA 02543-1598

    (508) 548-8700x2251 (voice)
    (508) 457-2310 (FAX)
    vatnipp@usgs.gov

  3. What similar or related data should the user be aware of?

    Jarrett, B.D., 2003, Late Quaternary carbonate sediments and facies distribution patterns across a ramp to rim transition: A new conceptual model for the southwest Florida platform: Ph.D. Dissertation, University of South Florida, St. Petersburg, FL.

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?

  3. How accurate are the heights or depths?

  4. Where are the gaps in the data? What is missing?

  5. How consistent are the relationships among the observations, including topology?

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:
University of South Florida must be referenced as the originator of the dataset in any future products or research derived from these data.

  1. Who distributes the data set? (Distributor 1 of 1)

    Al Hine
    University of South Florida
    Professor
    College of Marine Science
    St. Petersburg, FL 33701

    (727) 553-1161 (voice)
    hine@seas.marine.usf.edu

  2. What's the catalog number I need to order this data set?

    Downloadable Data

  3. What legal disclaimers am I supposed to read?

    These data were prepared by an agency of the United States Government. Neither the United States government nor any agency thereof, nor any of their employees, make any warranty, expressed or implied, or assumes any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or process disclosed in this report, or represents that its use would not infringe privately owned rights. Reference therein to any specific commercial product, process, or service by trade name, trademark, manufacturer, or otherwise does not necessarily constitute or imply its endorsement, recommendation, or favoring by the United States government or any agency thereof. Any views and opinions of authors expressed herein do not necessarily state or reflect those of the United States government or any agency thereof. Although all data published in this report have been used by the USGS, no warranty, expressed or implied, is made by the USGS as to the accuracy of the data and related materials and/or the functioning of the software. The act of distribution shall not constitute any such warranty, and no responsibility is assumed by the USGS in the use of this data, software, or related materials.

  4. How can I download or order the data?

Who wrote the metadata?

Dates:
Last modified: 13-May-2005
Metadata author:
VeeAnn A. Cross
U.S. Geological Survey
Marine Geologist
384 Woods Hole Rd.
Woods Hole, MA 02543-1598

(508) 548-8700 x2251 (voice)
(508) 457-2310 (FAX)
vatnipp@usgs.gov

Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)
Metadata extensions used:

Generated by mp version 2.8.6 on Fri May 13 13:41:43 2005