John Day Reservoir Shoreline, NOAA

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

Frequently-anticipated questions:

What does this data set describe?
    Title: John Day Reservoir Shoreline, NOAA
    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, John Day Reservoir Shoreline, NOAA: Biological Resources Division, U.S. Geological Survey, Cook, WA.

    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.699404
    East_Bounding_Coordinate: -119.297601
    North_Bounding_Coordinate: 45.940532
    South_Bounding_Coordinate: 45.687789

  3. What does it look like?

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

    Calendar_Date: 2003
    Currentness_Reference: Post-processing date

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

    2. What coordinate system is used to represent geographic features?

      Horizontal positions are specified in geographic coordinates, that is, latitude and longitude. 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?

    jdashore

    FID
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    Shape
    Feature geometry. (Source: ESRI)

    Coordinates defining the features.

    FNODE_
    From-node identifier of linear feature carried over from Arc/Info processing and the Arc/Info attribute FNODE_. It is an Arc/Info internal control parameter and has no applicable relevance to the use of the data. (Source: software computed)

    Range of values
    Minimum:1
    Maximum:472

    TNODE_
    To-node identifier of linear feature carried over from Arc/Info processing and the Arc/Info attribute TNODE_. It is an Arc/Info internal control parameter and has no applicable relevance to the use of the data. (Source: software computed)

    Range of values
    Minimum:1
    Maximum:472

    LPOLY_
    Internal number of polygon to left of arc carried over from Arc/Info processing and the Arc/Info attribute LPOLY_. It is an Arc/Info internal control parameter and has no applicable relevance to the use of the data. (Source: software computed)

    Range of values
    Minimum:1
    Maximum:238

    RPOLY_
    Internal number of polygon to right of arc carried over from Arc/Info processing and the Arc/Info attribute RPOLY_. It is an Arc/Info internal control parameter and has no applicable relevance to the use of the data. (Source: software computed)

    Range of values
    Minimum:1
    Maximum:257

    LENGTH
    Length of the line in native units. Since the original projection was Washington State Plane South, NAD27, these units are feet. (Source: BRD)

    Range of values
    Minimum:36.871
    Maximum:29039.121

    JDASHORE_
    Value from ARC assigned JDASHORE# from jdashore.dbf table. Generally has no meaning in ArcView shapefile.

    Range of values
    Minimum:1
    Maximum:575

    JDASHORE_I
    Value from ARC assigned JDASHORE1# from jdashore.dbf table. Generally has no meaning in ArcView shapefile.

    Range of values
    Minimum:1
    Maximum:308

    ENTITY
    unknown (Source: unknown)

    character set

    LAYER
    unknown (Source: unknown)

    character set

    ELEVATION
    unknown (Source: unknown)

    ValueDefinition
    0 

    THICKNESS
    unknown (Source: unknown)

    ValueDefinition
    0 

    COLOR
    unknown (Source: unknown)

    ValueDefinition
    7 

    Entity_and_Attribute_Overview:
    These attributes are from the original dataset from the Biological Resources Division. Most of these attributes appear to be a function of the data having been Arc/Info coverage files. The remaining attributes are probably associated with the digitizing process.

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?

    Appropriate credit should be given to BRD and NOAA for the creation of this dataset.

  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?
This data set was originally created for the John Day Reservoir Decision Support System by the Biological Resources Division in Cook, Washington. These data are provided here as basemap information indicating the location of the John Day Reservoir shoreline.

How was the data set created?
  1. From what previous works were the data drawn?

    (source 1 of 1)
    Columbia River Research Laborat, Western Fisheries Research Center, Biol, 1999, A Digital Atlas for John Day Reservoir: Biological Resources Division, U.S. Geological Survey, Cook, WA.

    Type_of_Source_Media: CD-ROM
    Source_Contribution:
    The original sources from which this data set was derived are the hardcopy NOAA navigational charts, scale 1:20000, covering John Day Reservoir. The charts are 18535_1, 18535_2, 18536_1, 18536_2, 18537_1, 18537_2, 18539_1, 18539_2. The reservoir shoreline was digitized originally in Eppl7 circa 1991 and later reprojected and converted to an ArcView line shapefile for this study.

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

    Date: 01-Jul-1999 (process 1 of 2)
    WARNING: THIS IS NOT THE OFFICIAL METADATA RECORD FOR THE SOURCE DATA, but merely describes from where the source data set was acquired and any post-processing that may have been done by the USGS/BRD/CRRL. The original sources from which this data set was derived are the hardcopy NOAA navigational charts, scale 1:20000, covering John Day Reservoir. The charts are 18535_1, 18535_2, 18536_1, 18536_2, 18537_1, 18537_2, 18539_1, 18539_2. The reservoir shoreline was digitized originally in Eppl7 circa 1991 and later reprojected and converted to an ArcView line shapefile for this study.

    Person who carried out this activity:

    David E. Rupp
    U.S. Geological Survey, Biological Resources
    Research Fishery Biologist
    5501-A Cook-Underwood Rd
    Cook, Washington 98605
    USA

    509 538-2299 (voice)
    509 538-2843 (FAX)
    David_Rupp@usgs.gov

    Hours_of_Service: 7:30 a.m. to 4:00 p.m. Monday Through Friday
    Date: 2003 (process 2 of 2)
    This shapefile was reprojected to geographic, NAD83 using ArcToolbox from ArcGIS 8.2.

    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-8700 x2251 (voice)
    (508) 457-2310 (FAX)
    vatnipp@usgs.gov

How reliable are the data; what problems remain in the data set?
  1. How well have the observations been checked?

    No report

  2. How accurate are the geographic locations?

    The accuracy is no better than that of the source charts, plus any error added during the digitization process.

  3. How accurate are the heights or depths?

    No report.

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

    The entire shoreline of John Day Reservoir as it appears on the navigation charts was digitized. Islands were included. Tributaries were excluded.

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

    No report

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

  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?

    Although these data have been processed successfully on a computer system at the U.S. Geological Survey, no warranty expressed or implied is made regarding the accuracy or utility of the data on any other system or for general or scientific purposes, nor shall the act of distribution constitute any such warranty. This disclaimer applies both to individual use of the data and aggregate use with other data. It is strongly recommended that these data are directly acquired from a U.S. Geological Survey server, and not indirectly through other sources which may have changed the data in some way. It is also strongly recommended that careful attention be paid to the contents of the metadata file associated with these data. The U.S. Geological Survey shall not be held liable for improper or incorrect use of the data described and/or contained herein.

  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:11:07 2004