Interpretation of road locations in the John Day Reservoir based on sidescan-sonar imagery

Frequently-anticipated questions:

• What does this data set describe?
  1. How should this data set be cited?
  2. What geographic area does the data set cover?
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
  5. What is the general form of this data set?
  6. How does the data set represent geographic features?
  7. How does the data set describe geographic features?
• Who produced the data set?
  1. Who are the originators of the data set?
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
• Why was the data set created?
• How was the data set created?
  1. From what previous works were the data drawn?
  2. How were the data generated, processed, and modified?
• 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 data, including topology?
• How can someone get a copy of the data set?
  1. Are there legal restrictions on access or use of the data?
  2. Who distributes the data?
  3. What's the catalog number I need to order this data set?
  4. What legal disclaimers am I supposed to read?
  5. How can I download or order the data?
• Who wrote the metadata?

Title:

Interpretation of road locations in the John Day Reservoir based on sidescan-sonar imagery

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?

   Twichell, David C. , 2004, Interpretation of road locations in the John Day Reservoir based on sidescan-sonar imagery:.

   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.677344

   East_Bounding_Coordinate: -119.476547

   North_Bounding_Coordinate: 45.919159

   South_Bounding_Coordinate: 45.688790

3. What does it look like?

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

   Beginning_Date: 01-Jul-2007

   Ending_Date: 02-Aug-2007

   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 (105)

   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?

   road

   FID

   Internal feature number. (Source: ESRI)

   Sequential unique whole numbers that are automatically generated.

   Shape

   Feature geometry. (Source: ESRI)

   Coordinates defining the features.

   ID

   Automatically generated by the software. (Source: Software.)

   Value	Definition
   0

   INTERP

   Type of linear feature. This is typically road or causeway, but there are 2 linear features that are listed as unknown. (Source: David C. Twichell)

   character set

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

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
   

This shapefile was generated to indicate the locations of roads and causeways as interpreted in the sidescan-sonar mosaic. This information can be used to compare with pre-impoundment photos to indicate navigational or mapping error of the sidescan-sonar imagery.

1. From what previous works were the data drawn?

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

   (process 1 of 1)

   Once the sidescan-sonar mosaic was completed, linear features interpreted to be roads or causeways were digitized based on the mosaic as a basemap.

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?

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?

4. How can I download or order the data?
   • Availability in digital form:

     Data format:	SHAPEFILE Size: 0.038

   • Cost to order the data:

Dates:

Last modified: 25-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:

• <http://www.esri.com/metadata/esriprof80.html>