Columbia River ESTR00030 Survey Tracklines

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

Frequently-anticipated questions:


What does this data set describe?

    Title: Columbia River ESTR00030 Survey Tracklines
    Abstract:
    A two-week field operation was conducted in the John Day Reservoir on the Columbia River to image the floor of the pool, to measure the distribution and thickness of post-impoundment sediment, and to verify these geophysical data with video photography and bottom sediment samples. The field program was a cooperative effort between the USGS Coastal and Marine Geology Team of the Geologic Division and the USGS Columbia River Research Laboratory of the Biological Resources Division. The data collection was completed aboard the R/V ESTERO during September 13-27, 2000. The interest in sediment accumulation in the reservoir was two-fold. First, it was unknown how effective this reservoir was as a sediment trap to material that otherwise would have been transported down-river to the estuary and eventually to the ocean. The recent erosion of beaches along the Washington coast has been attributed to a decreased contribution of sediment from the Columbia River to the coastal system due to the damming of the river. Second, sediment accumulation on the floors of reservoirs along the Columbia River has been suggested to be diminishing salmon spawning grounds. The extent of changes in habitat since construction of the John Day Dam, however, had not been documented. Common data sets were needed to address both of these questions, and for these reasons this geophysical and sampling program was undertaken.

  1. How should this data set be cited?

    Cross, VeeAnn A. , and Twichell, David C. , 2004, Columbia River ESTR00030 Survey Tracklines:.

    Online Links:

    This is part of the following larger work.

    Cross, VeeAnn A. , and Twichell, David C. , 2004, Geophysical, Sedimentologic, and Photographic Data from the John Day Reservoir, Washington and Oregon: Data Archive and Preliminary Discussion: Open-File Report 2004-1014, U.S. Geological Survey, Woods Hole Science Center, Woods Hole, MA.

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -120.684160
    East_Bounding_Coordinate: -119.325900
    North_Bounding_Coordinate: 45.932460
    South_Bounding_Coordinate: 45.688390

  3. What does it look like?

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

    Beginning_Date: 11-Sep-2000
    Ending_Date: 22-Sep-2000
    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 (44)

    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?

    tracklines

    FID
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    Shape
    Feature geometry. (Source: ESRI)

    Coordinates defining the features.

    LINENUM
    Numeric value indicating the line number the polyline represents. (Source: user defined)

    Range of values
    Minimum:1
    Maximum:40

    FILENAME
    String indicating the filename to which the logged data was recorded. (Source: user defined)

    character set

    HOTLINK
    String field indicating the location of the images to hotlink to each line. Has a variable for the initial part of the path. (Source: user defined)

    character set

    FIRERATE
    String representing the fire rate (in seconds) of the acquisition system. (Source: system defined)

    character set

    SWATH
    Total swath coverage (in meters) of the acquisition system at a given fire rate. (Source: system defined.)

    Range of values
    Minimum:800
    Maximum:1200


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?

    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


Why was the data set created?

The chirp seismic-reflection profiles were collected to measure the thickness and distribution of sediment that has accumulated in the John Day Reservoir since impoundment in 1968.


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: 2000 (process 1 of 3)
    The SIS-1000 system acquires chirp sidescan-sonar and chirp seismic-reflection data. Navigation is merged with these data. Since one system acquires both sets of data, only one trackline file is needed. In this case, the navigation extraced from the sidescan-sonar data was reformatted and converted to an Arc ungenerated format using awk scripts.

    (process 2 of 3)
    This ungenerate file (polyline format) was then imported into ArcView3.2 using an avenue script.

    (process 3 of 3)
    Additional attributes were added to the table of the shapefile to further describe each line of data, as well as allow hotlinking to seismic-reflection profile images.


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?

    The navigation was collected with a P-Code plugger navigation system. Although the navigation antenna was mounted on the ship rather than the towfish, the system was towed shallow and extremely close to the boat therefore making the "layback" error negligible. Because of the high fire rates of the system, each "shot" does not have a navigation point, therefore these values have to be interpolated.

  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:
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)

    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

  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: 09-Mar-2004

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 Tue Mar 09 13:51:16 2004