Chirp Seismic Survey Tracklines - Lake Mead 1999

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

Frequently-anticipated questions:

What does this data set describe?
    Title: Chirp Seismic Survey Tracklines - Lake Mead 1999
    Abstract:
    Lake Mead is a large interstate reservoir located in the Mojave Desert of southeastern Nevada and northwestern Arizona. It was impounded in 1935 by the construction of Hoover Dam and is one of a series of multi-purpose reservoirs on the Colorado River. The lake extends 183 km from the mouth of the Grand Canyon to Black Canyon, the site of Hoover Dam, and provides water for residential, commercial, industrial, recreational, and other non-agricultural users in communities across the southwestern United States. Extensive research has been conducted on Lake Mead, but a majority of the studies have involved determining levels of anthropogenic contaminants such as synthetic organic compounds, heavy metals and dissolved ions, furans/dioxins, and nutrient loading in lake water, sediment, and biota (Preissler, et al., 1998; Bevans et al, 1996; Bevans et al., 1998; Covay and Leiker, 1998; LaBounty and Horn, 1997; Paulson, 1981). By contrast, little work has focused on the sediments in the lake and the processes of deposition (Gould, 1951). To address these questions, sidescan-sonar imagery and high-resolution seismic-reflection profiles were collected throughout Lake Mead by the USGS in cooperation with researchers from University of Nevada Las Vegas (UNLV). These data allow a detailed mapping of the surficial geology and the distribution and thickness of sediment that has accumulated in the lake since the completion of Hoover Dam. Results indicate that the accumulation of post-impoundment sediment is primarily restricted to former river and stream beds that are now submerged below the lake while the margins of the lake appear to be devoid of post-impoundment sediment. The sediment cover along the original Colorado River bed is continuous and is typically greater than 10 m thick through much of its length. Sediment thickness in some areas exceeds 35 m while the smaller tributary valleys typically are filled with less than 4 m of sediment. Away from the river beds that are now covered with post-impoundment sediment, pre-impoundment alluvial deposits and rock outcrops are still exposed on the lake floor.

  1. How should this data set be cited?

    Twichell, David C. , and Cross, VeeAnn A. , 2003, Chirp Seismic Survey Tracklines - Lake Mead 1999:.

    Online Links:

    This is part of the following larger work.

    Twichell, David C. , Cross, VeeAnn A. , and Belew, Stephen D. , 2003, Mapping the floor of Lake Mead (Nevada and Arizona): Preliminary discussion and GIS data release: Open-File Report 03-320, U.S. Geological Survey, Woods Hole Field Center, Woods Hole, MA.

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -114.857591
    East_Bounding_Coordinate: -114.589473
    North_Bounding_Coordinate: 36.145382
    South_Bounding_Coordinate: 36.018801

  3. What does it look like?

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

    Beginning_Date: 14-May-1999
    Ending_Date: 25-May-1999
    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 (80)

    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.0002. Longitudes are given to the nearest 0.0002. 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?

    seisnav_99
    ArcView shapefile attribute table (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.

    LINENUM
    A numeric value indicating a line number. (Source: VeeAnn A. Cross)

    Range of values
    Minimum:0
    Maximum:505

    FILENAME
    Prefix of the filename assigned to each line of data collected. (Source: Kenneth F. Parolski)

    character set

    FIRERATE
    The rate at which the transducer "fired" or emitted the sonar pulse. (Source: VeeAnn A. Cross)

    character set

    LENGTHM
    The length of each line segment in meters. (Source: Software computerd.)

    Range of values
    Minimum:820
    Maximum:12350
    Units:meters

    SWATH
    The total swath (in meters) that was covered by the sidescan portion of the instrument. Related to firerate. (Source: Acquisition system.)

    character set

    HOTLINK
    Path to the location of the hotlink file, uses a variable ($MYDATA) that can be set to make the data more portable.

    character set

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?

    David C. Twichell
    U.S. Geological Survey
    Oceanographer
    384 Woods Hole Rd.
    Woods Hole, MA 02543-1598

    508-548-8700 x2266 (voice)
    508-457-2310 (FAX)
    dtwichell@usgs.gov

Why was the data set created?
This GIS overlay indicates the tracklines along which chirp seismic-reflection profiles were collected during the 1999 survey.

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 4)
    Navigation was acquired and stored with the SIS-1000 chirp subbottom system. The navigation was corrected for instrument layback relative to the navigation antenna within the Hypack navigation system. A unique navigation point was sent to the acquisition system approximately every 10 seconds. These original navigation points are stored in the seismic data as UTM, Zone 11, NAD83 coordinates. These navigation positions reflect the best known position of the acquisition system. In other words, the layback of the instrument is taken into account for the positional fix.

    (process 2 of 4)
    This seismic navigation was then extracted from each individual trackline and projected into the geographic coordinate system using PROJ.

    Data sources used in this process:

    • Evenden, 1990, Cartographic Projection Procedures for the UNIX Environment -- A User's Manual: Open-file Report 90-284

    (process 3 of 4)
    This file was then formatted to represent an Arc/Info generate format so that the lines could be imported into ArcView.

    (process 4 of 4)
    Within ArcView, additional attribute information describing each trackline was added.

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?

    These data represent the navigation for all the chirp seismic lines collected on this cruise.

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

    These data have been checked to remove obviously erroneous data points.

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:
The U.S. Geological Survey 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)

    David C. Twichell
    U.S. Geological Survey
    Oceanographer
    384 Woods Hole Rd.
    Woods Hole, MA 02543-1598

    508-548-8700 x2266 (voice)
    508-457-2310 (FAX)
    dtwichell@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?

    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: 23-Jan-2003

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.7.3 on Mon Oct 06 12:10:58 2003