Tracklines for multichannel seismic data collected by the USGS in the Atwater Valley area aboard the R/V GYRE Cruise G1-03-GM (03001) - AV_G103GM_LINES.SHP

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

Frequently anticipated questions:

What does this data set describe?

Title:
Tracklines for multichannel seismic data collected by the USGS in the Atwater Valley area aboard the R/V GYRE Cruise G1-03-GM (03001) - AV_G103GM_LINES.SHP
Abstract:
This line shapefile contains navigation of the lines for the multichannel seismic survey that was conducted in the Atwater Valley area of the Gulf of Mexico during USGS cruise G1-03-GM aboard the R/V Gyre in the Gulf of Mexico in May, 2003. The purpose of this cruise was to collect multichannel seismic data in support of USGS and Department of Energy gas hydrate studies. About 253 km of data were collected along 35 short lines in and around lease block Atwater Valley 14 on the floor of the Mississippi Canyon.
  1. How might this data set be cited?
    Ackerman, Seth, Hart, Pat, Sliter, Ray, and Dugan, Brandon, 2005, Tracklines for multichannel seismic data collected by the USGS in the Atwater Valley area aboard the R/V GYRE Cruise G1-03-GM (03001) - AV_G103GM_LINES.SHP: Open-File Report 2005-1071, U.S. Geological Survey, Coastal and Marine Geology Program, Woods Hole Coastal and Marine Science Center, Woods Hole, MA.

    Online Links:

    This is part of the following larger work.

    Twichell, D.C., Cross, V.A., Paskevich, V.F., Hutchinson, D.R., Winters, W.J., and Hart, P.E., 2005, GIS of selected geophysical and core data in the northern Gulf of Mexico continental slope collected by the U.S. Geological Survey: Open-File Report 2005-1071, U.S. Geological Survey, Reston, VA.

    Online Links:

    Other_Citation_Details: 1 DVD-ROM
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -89.699738
    East_Bounding_Coordinate: -89.248831
    North_Bounding_Coordinate: 28.157523
    South_Bounding_Coordinate: 27.910096
  3. What does it look like?
    https://pubs.usgs.gov/of/2005/1071/data/seismic/2003/atwater/nav/av_g103gm_lines-thumb.gif (GIF)
    Thumbnail image showing the extent and coverage of the data layer.
    https://pubs.usgs.gov/of/2005/1071/data/seismic/2003/atwater/nav/av_g103gm_lines.gif (GIF)
    Overview image showing the extent and coverage of the data layer.
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 03-May-2003
    Ending_Date: 16-May-2003
    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 Vector data set. It contains the following vector data types (SDTS terminology):
      • String (38)
    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 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?
    av_g103gm_lines
    shapefile (Source: ESRI)
    FID
    Internal feature number. (Source: ESRI) Sequential unique whole numbers that are automatically generated.
    Shape
    Feature geometry. (Source: ESRI) Coordinates defining the features.
    ID
    Internal feature number (Source: ESRI)
    Range of values
    Minimum:1
    Maximum:37
    LINENAME
    Line name and number which corresponds with names of seismic profiles. (Source: USGS) Character string identifying the survey line.
    LENGTH
    Length of survey line in meters (Source: USGS)
    Range of values
    Minimum:4884.367
    Maximum:27364.822
    Units:meters
    Resolution:.001
    IMAGE
    Directory path to seismic image that corresponds with the survey line. (Source: USGS) Character string containing relative path to image that corresponds with the survey line.

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Seth Ackerman
    • Pat Hart
    • Ray Sliter
    • Brandon Dugan
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
    U.S. Geological Survey
    Attn: Deborah Hutchinson
    Geologist
    384 Woods Hole Rd.
    Woods Hole, MA
    USA

    (508) 548-8700 x2263 (voice)
    (508) 457-2310 (FAX)
    dhutchinson@usgs.gov

Why was the data set created?

This GIS overlay is a component of the U.S. Geological Survey, Woods Hole Science Center's, Gulf of Mexico GIS database. The Gulf of Mexico GIS database is intended to organize and display USGS held data and provide on-line (WWW) access to the data and/or metadata.

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: 07-May-2003 (process 1 of 14)
    Navigation file exported from seg-y headers in ProMAX and saved to Marfac Snap2. NOTE: Navigation reflects the location of the GPS antenna. Shift to the actual shot location will be applied later. Person who carried out this activity:
    Ray Sliter
    U.S. Geological Survey
    USGS - Menlo Park
    Menlo Park, CA
    USA

    (650) 329-5194 (voice)
    (650) 329-5190 (FAX)
    rsliter@usgs.gov
    Data sources produced in this process:
    • ProMAX created .nav file
    Date: 07-May-2003 (process 2 of 14)
    Navigation file opened in MS Excel, arc milliseconds for X and Y coordinates were converted to decimal degrees (by dividing the each of the arc-millisecond values by 3,600,000 and creating the two new attribute fields X_DD and Y_DD) [excel file ##to##sda.xls]. A header line was added to the table in Excel. Person who carried out this activity:
    Seth Ackerman
    U.S. Geological Survey
    GIS Technician
    384 Woods Hole Rd.
    Woods Hole, MA
    USA

    (508) 548-8700 x2315 (voice)
    (508) 457-2310 (FAX)
    sackerman@usgs.gov
    Data sources used in this process:
    • ProMAX created .nav file
    Data sources produced in this process:
    • ##to##_2gis.txt
    Date: 07-May-2003 (process 3 of 14)
    Imported the text file of X/Y coordinates (Decimal Degrees) into ArcMap 8.2. Set projection to Geographic - NAD83 and exported as a point shapefile (##to##_geo.shp) Person who carried out this activity:
    Seth Ackerman
    U.S. Geological Survey
    GIS Technician
    384 Woods Hole Rd.
    Woods Hole, MA
    USA

    (508) 548-8700 x2315 (voice)
    (508) 457-2310 (FAX)
    sackerman@usgs.gov
    Data sources used in this process:
    • ##to##_2gis.txt
    Data sources produced in this process:
    • ##to##_geo.shp
    Date: 07-May-2003 (process 4 of 14)
    In ArcToolbox 8.2 reprojected the point theme (##to##_geo.shp) to the appropriate UTM zone (zone 15 for Keathley Canyon or zone 16 for Atwater Valley) Person who carried out this activity:
    Seth Ackerman
    U.S. Geological Survey
    GIS Technician
    384 Woods Hole Rd.
    Woods Hole, MA
    USA

    (508) 548-8700 x2315 (voice)
    (508) 457-2310 (FAX)
    sackerman@usgs.gov
    Data sources used in this process:
    • ##to##_geo.shp
    Data sources produced in this process:
    • ##to##_utm##.shp where for utm##, the ## is the utm zone (zone 15 for Keathley Canyon or zone 16 for Atwater Valley regions)
    Date: 07-May-2003 (process 5 of 14)
    XY values were added to the UTM projected shapefile creating 2 new attribute fields (X_COORD and Y_COORD) with the utm coordinates for the points. Person who carried out this activity:
    Seth Ackerman
    U.S. Geological Survey
    GIS Technician
    384 Woods Hole Rd.
    Woods Hole, MA
    USA

    (508) 548-8700 x2315 (voice)
    (508) 457-2310 (FAX)
    sackerman@usgs.gov
    Data sources used in this process:
    • ##to##_utm##.shp
    Data sources produced in this process:
    • ##to##_utm##.shp with utm coordinates added to the attribute table
    Date: 07-May-2003 (process 6 of 14)
    Navigation exported as ASCII text file. Matlab process to shift the navigation fixes to reflect that of the actual shot location (currently nav reflects the location of the GPS antenna). Outfile header will be "yr jd time GPS_x_utm GPS_y_utm Line shot ffid sht_x_utm sht_y_utm" Person who carried out this activity:
    Brandon Dugan
    U.S. Geological Survey
    GIS Technician
    384 Woods Hole Rd.
    Woods Hole, MA
    USA

    (508) 548-8700 x2218 (voice)
    (508) 457-2310 (FAX)
    bdugan@usgs.gov
    Data sources used in this process:
    • ##to##_utm##.shp with utm coordinates added to the attribute table
    Data sources produced in this process:
    • KC##new.txt or AV##new.txt
    Date: 07-May-2003 (process 7 of 14)
    Navigation (corrected with a shift to reflect the shot location) taken back into ProMAX. Then file of CDP locations (g1cdp.nav) exported from ProMAX. File split into kc_cdp.nav and av_cdp.nav, then awk script to reformat the output. CDP points into ArcView 3.3 and saved as shapefiles g1cdp_nav_kc_geo.shp and g1cdp_nav_av_geo.shp. Person who carried out this activity:
    Seth Ackerman
    U.S. Geological Survey
    GIS Technician
    384 Woods Hole Rd.
    Woods Hole, MA
    USA

    (508) 548-8700 x2315 (voice)
    (508) 457-2310 (FAX)
    sackerman@usgs.gov
    Data sources used in this process:
    • g1cdp.nav (kc_cdp.nav/av_cdp.nav)
    Data sources produced in this process:
    • g1cdp_nav_kc_utm15.shp/g1cdp_nav_av_utm16.shp
    Date: 07-May-2003 (process 8 of 14)
    In ArcToolbox 8.2, reprojected the UTM point shapefiles to geographic NAD83 projection creating the files: g1cdp_nav_kc_utm15.shp --> g1cdp_nav_kc_geo.shp g1cdp_nav_av_utm16.shp --> g1cdp_nav_av_geo.shp
    and added the geographic coordinates in ArcMap using the Xtools extension. Person who carried out this activity:
    Seth Ackerman
    U.S. Geological Survey
    GIS Technician
    384 Woods Hole Rd.
    Woods Hole, MA
    USA

    (508) 548-8700 x2315 (voice)
    (508) 457-2310 (FAX)
    sackerman@usgs.gov
    Data sources used in this process:
    • g1cdp_nav_kc_utm15.shp/g1cdp_nav_av_utm16.shp
    Data sources produced in this process:
    • g1cdp_nav_kc_geo.shp/g1cdp_nav_av_geo.shp
    Date: 28-Oct-2004 (process 9 of 14)
    point shapefiles converted to lines with VeeAnn Cross' avenue script "navpnts2line.ave": g1cdp_nav_kc_geo.shp (pts) --> kc_g103gm_lines.shp (polyline) g1cdp_nav_av_geo.shp (pts) --> av_g103gm_lines.shp (polyline) Person who carried out this activity:
    Seth Ackerman
    U.S. Geological Survey
    GIS Technician
    384 Woods Hole Rd.
    Woods Hole, MA
    USA

    (508) 548-8700 x2315 (voice)
    (508) 457-2310 (FAX)
    sackerman@usgs.gov
    Data sources used in this process:
    • g1cdp_nav_kc_geo.shp/g1cdp_nav_av_geo.shp
    Data sources produced in this process:
    • kc_g103gm_lines.shp/av_g103gm_lines.shp
    Date: 28-Oct-2004 (process 10 of 14)
    Metadata created in TKME and imported with ArcCatalog9. Data sources used in this process:
    • c:\temp\xmlB6C.tmp
    Date: 28-Feb-2017 (process 11 of 14)
    Edits to the metadata were made to fix any errors that MP v 2.9.36 flagged. This is necessary to enable the metadata to be successfully harvested for various data catalogs. In some cases, this meant adding text "Information unavailable" or "Information unavailable from original metadata" for those required fields that were left blank. Other minor edits were probably performed (title, publisher, publication place, etc.). Attempted to modify http to https where appropriate. The link to the larger work citation had to be fixed. The metadata date (but not the metadata creator) was edited to reflect the date of these changes. The metadata available from a harvester may supersede metadata bundled within a download file. Compare the metadata dates to determine which metadata file is most recent. 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
    Date: 20-Jul-2018 (process 12 of 14)
    USGS Thesaurus keywords added to the keyword section. 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
    Date: 18-Nov-2019 (process 13 of 14)
    Crossref DOI link was added as the first link in the metadata. 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
    Date: 08-Sep-2020 (process 14 of 14)
    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?

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?
    DGPS navigation was collected using a Trimble (model G-437) receiver
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
    Information unavailable from original metadata.
  5. How consistent are the relationships among the observations, including topology?
    No additional checks for topological consistency were performed on the data. No duplicate features are present.

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 (USGS) as the source of this information.
  1. Who distributes the data set? (Distributor 1 of 1)
    Deborah Hutchinson
    U.S. Geological Survey
    Geologist
    384 Woods Hole Road
    Woods Hole, MA
    USA

    508-548-8700 x2263 (voice)
    508-457-2301 (FAX)
    dhutchinson@usgs.gov
  2. What's the catalog number I need to order this data set? Downloadable Data
  3. What legal disclaimers am I supposed to read?
    Although this data set has been used by the U.S. Geological Survey (USGS), no warranty, expressed or implied, is made by the USGS as to the accuracy of the data and/or related materials. 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?
    • Availability in digital form:
      Data format: The SHP file contains the geospatial data. The SHX file contains the index of the geospatial data. The DBF file contains the attribute data in dBase format. The PRJ file contains the coordinate system information (optional). The AVL file contains the legend information (optional). The SBN and SBX files contain the spatial index of the geospatial data (optional). The XML file contains the metadata describing the data set <data set name>.shp.xml. An ASCII version of the metadata file. A browse graphic showing the data layer coverage and extent (optional). in format SHP (version 3.3) ESRI polyline shapefile Size: 0.742
      Network links: https://pubs.usgs.gov/of/2005/1071/data/seismic/2003/atwater/nav/av_g103gm_lines.zip
      Media you can order: DVD-ROM (Density 4.75 Gbytes) (format UDF)
    • Cost to order the data: None

  5. What hardware or software do I need in order to use the data set?
    The data are available in Environmental Systems Research Institute (ESRI) shapefile format. The user must have ArcGIS® or ArcView® 3.0 or greater software to read and process the data file. In lieu of ArcView or ArcGIS, the user may utilize another GIS application package capable of importing data. A free data viewer, arcexplorer, capable of displaying the data is available from ESRI at www.esri.com.

Who wrote the metadata?

Dates:
Last modified: 18-Mar-2024
Metadata author:
Seth Ackerman
U.S. Geological Survey
GIS Technician
384 Woods Hole Rd.
Woods Hole, MA
USA

(508) 548-8700 x2315 (voice)
(508) 457-2310 (FAX)
whsc_data_contact@usgs.gov
Contact_Instructions:
The metadata contact email address is a generic address in the event the person is no longer with USGS. (updated on 20240318)
Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)
This page is <https://cmgds.marine.usgs.gov/catalog/whcmsc/open_file_report/ofr2005-1071/av_g103gm_linesmeta.faq.html>
Generated by mp version 2.9.51 on Mon Mar 25 16:05:22 2024