<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="fgdc_classic.xsl"?>
<metadata xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://water.usgs.gov/GIS/metadata/usgswrd/fgdc-std-001-1998.xsd">
<idinfo>
<citation>
<citeinfo>
<origin>U.S. Geological Survey</origin>
<pubdate>20091030</pubdate>
<title>Sprague River Oregon Water 2000</title>
<geoform>vector digital data</geoform>
<pubinfo>
<pubplace>Portland, OR</pubplace>
<publish>U.S. Geological Survey</publish>
</pubinfo>
<onlink>http://water.usgs.gov/lookup/getspatial?spragueriveroregon_water_2000</onlink>
</citeinfo>
</citation>
<descript>
<abstract>The Sprague River drains 4090 square kilometers in south-central Oregon before flowing into the Williamson River and upper Klamath Lake. In cooperation with the U.S. Fish and Wildlife Service, the USGS and University of Oregon conducted a study to evaluate channel and floodplain processes for the 131 km of the Sprague River and its major tributaries, including the lower 20 km of the South Fork Sprague River, the lower 16 km of the North Fork Sprague River, and the lower 62 km of the Sycan River. The study involved multiple analyses, including assessments of historical channel change, riparian and floodplain vegetation, and surficial geology. To support these analyses, digital floodplain and channel maps were prepared from historic notes, maps, and aerial photos to depict channel and floodplain conditions at different times between 1866 and 2005. The geospatial database of current and historic channel and floodplain conditions will also enable evaluation of long-term trends pertaining to aquatic and riparian habitat conditions.</abstract>
<purpose>These data were created to support understanding of geomorphic conditions and historical changes to channel and floodplain conditions for the Sprague River and the lower portions of its major tributaries. GIS layers depicting channel centerlines, water features, fluvial bars, floodplain vegetation, and floodplain features such as irrigation canals, levees and dikes, and roads were created from aerial photographs dating from 1940, 1968, and 2000. The purpose of this mapping was to track changes in channel and floodplain morphology and vegetation over time and to measure changes in channel position. Historical aerial photographs from 1940 and 1968 were acquired, scanned, and rectified for this project, while digital orthophotographs from 2000 are publicly available. (See metadata for each photograph set for more information on the rectification process and resolution of each dataset). In addition, channel centerlines were mapped from publicly available coverages for 1975 (Natural Resources Conservation Service Soil Survey of Klamath County) and 2005 (U.S. Department of Agriculture NAIP imagery). The surficial geologic mapping was done to support understanding of the geologic context of the modern floodplain, and encompasses the alluvial valleys of the Sprague River and the lower portions of the Sycan, North Fork, and South Fork Sprague Rivers.</purpose>
</descript>
<timeperd>
<timeinfo>
<sngdate>
<caldate>2000</caldate>
</sngdate>
</timeinfo>
<current>ground condition</current>
</timeperd>
<status>
<progress>Complete</progress>
<update>None planned</update>
</status>
<spdom>
<bounding>
<westbc>
-121.874766</westbc>
<eastbc>
-121.081563</eastbc>
<northbc>
42.615297</northbc>
<southbc>
42.435597</southbc>
</bounding>
</spdom>
<keywords>
<theme>
<themekt>None</themekt>
<themekey>geomorphology</themekey>
<themekey>channel analysis</themekey>
<themekey>floodplain analysis</themekey>
<themekey>inlandWaters</themekey>
</theme>
<place>
<placekt>None</placekt>
<placekey>Sprague River Oregon</placekey>
<placekey>Klamath Basin</placekey>
</place>
</keywords>
<accconst>None</accconst>
<useconst>The U.S. Geological Survey and the University of Oregon should be acknowledged as the data source in products derived from these data.</useconst>
<ptcontac>
<cntinfo>
<cntperp>
<cntper>Tana Haluska</cntper>
<cntorg>U.S. Geological Survey</cntorg>
</cntperp>
<cntpos>Geographer</cntpos>
<cntaddr>
<addrtype>mailing address</addrtype>
<address>2130 SW 5th Avenue</address>
<city>Portland</city>
<state>OR</state>
<postal>97201</postal>
<country>USA</country>
</cntaddr>
<cntvoice>503-251-3212</cntvoice>
<cnttdd>N/A</cnttdd>
<cntfax>503-251-3470</cntfax>
<cntemail>thaluska@usgs.gov</cntemail>
<cntinst>(Warning: Although accurate at the time of production, this information may have become obsolete. See the Metadata_Reference_Information section for a current contact.)</cntinst>
</cntinfo>
</ptcontac>
<browse>
<browsen>http://water.usgs.gov/GIS/browse/spragueriveroregon_water_2000.gif</browsen>
<browsed>Illustration of data set</browsed>
<browset>GIF</browset>
</browse>
<native>Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 9.3.1.3000</native>
</idinfo>
<dataqual>
<attracc>
<attraccr>Image evaluation and feature interpretation occurred at a scale of 1:10,000 - 1:500.  Digitization of features occurred at a scale of 1:1,000.</attraccr>
</attracc>
<logic>Topology rules were used to clean and edit features digitized within the floodplain boundary data set for overlap and boundary accuracy.  A separate topology was run to edit digitizing overlap with the floodplain boundary data set and the features digitized within it to ensure all features were enclosed within the final floodplain boundary.</logic>
<complete>Data are complete. Digitization of features occurred at a scale of 1:1000.  In general, all features that were clearly visible at that scale were digitized.  Minimum size and density specifications for digitizing are listed in each attribute definition. Where vegetation overhang and shadows overlapped with other features within the floodplain boundary digitizing an accurate boundary of the covered feature was attempted.  Interpreting the boundary of the covered feature (Water, Built Feature or Bar) was done by extrapolating edges from visible data. Varied discharge associated with different photo dates occasionally resulted in discontinuity of water features at photo overlap and boundaries.  In the situation of discontinuity at overlap one photo was exchanged for a bordering photo at approximately the mid-point of overlap and features were digitized to the photo being utilized. When discontinuity occurred at image boundaries or the photo exchange point the water feature with the greatest area was digitized. Mean daily discharges associated with different photo dates are recorded in the Photo Sets and Related Stream Discharge.xls spreadsheet located inside the SpragueRiverAnalysis.mdb file. Water is defined as all wetted features (visible surface water) within the floodplain boundary data set.  This includes wetted areas with aquatic vegetation mats and emergent vegetation.  Identification and classification of wetted features were based on location of the feature, knowledge of the landscape (based on fieldwork), USGS 7.5 topo maps, and aerial photo interpretation of tone and texture.  Water is relatively dark gray or black in color and usually a darker tone than non-wetted surfaces (unless the vegetation is shadowed).  Water usually appears smooth and consistent in texture except where aquatic or emergent vegetation are present and/or depth varies.  With these exceptions Water features may have a gray to black speckled texture appearance.  Texture and color may also vary where sunlight was reflected off the surface of the water.  In this situation Water features appear white with a very slightly blurred boundary edge. The digital boundary of a wetted feature was defined on the landward/terrestrial side of the boundary between surface water and land.  Where vegetation or its shadow overlaped the wetted/terrestrial surface boundary, the boundary of the wetted feature was digitized.  The attribute table associated with this feature class identifies the primary channel with which the wetted features is associated (Sprague, South Fork,  North Fork or Sycan Rivers).</complete>
<posacc>
<horizpa>
<horizpar>A goal of an RMSE less than 5 meters was established for the georectification process. Photo scanning and DPI were calculated to ensure that 2000, 1968, and 1940 photo sets all had the same 1 meter pixel resolution.</horizpar>
</horizpa>
<vertacc>
<vertaccr>N/A</vertaccr>
</vertacc>
</posacc>
<lineage>
<srcinfo>
<srccite>
<citeinfo>
<origin>U.S. Fish and Wildlife Service</origin>
<pubdate>2000</pubdate>
<title>Aerial Photography</title>
<geoform>remote-sensing image</geoform>
<othercit>U.S. Fish and Wildlife Service (USFWS). 1998 Natural color photo images, 1:12000.
Sprague River Riparian Vegetation Characterization. Spatial Solutions, Inc. Bend, OR. 2000.</othercit>
</citeinfo>
</srccite>
<srcscale>12,000</srcscale>
<typesrc>aerial photography</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate>1998</caldate>
</sngdate>
</timeinfo>
<srccurr>ground condition</srccurr>
</srctime>
<srccitea>USFWSDAP</srccitea>
<srccontr>Aerial Photography</srccontr>
</srcinfo>
<srcinfo>
<srccite>
<citeinfo>
<origin>Watershed Sciences, LLC</origin>
<pubdate>2005</pubdate>
<title>LiDAR Digital Elevation Model</title>
<geoform>raster digital data</geoform>
<othercit>Watershed Science. 2005.  Sprague River LiDAR Remote Sensing and Data Collection.  Submitted to the Klamath Tribes.</othercit>
</citeinfo>
</srccite>
<typesrc>digital elevation model</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate>2005</caldate>
</sngdate>
</timeinfo>
<srccurr>ground condition</srccurr>
</srctime>
<srccitea>WS2005</srccitea>
<srccontr>Used to identify topographic details that assisted in feature classification
during digitizing as well as floodplain delineation.  Also used for analysis of
relative elevation and proximity of features within the delineated floodplain.</srccontr>
</srcinfo>
<srcinfo>
<srccite>
<citeinfo>
<origin>Watershed Sciences, LLC</origin>
<pubdate>2000</pubdate>
<title>Thermal Infrared Data</title>
<geoform>raster digital data</geoform>
<othercit>Watershed Sciences, LLC.  2000.  Remote Sensing Survey of the Upper
Klamath River Basin; Thermal Infrared Data.  Prepared for the Oregon
Department of Environmental Quality. Data collected in 1999.</othercit>
</citeinfo>
</srccite>
<typesrc>digital thermal infrared data</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate>1999</caldate>
</sngdate>
</timeinfo>
<srccurr>ground condition</srccurr>
</srctime>
<srccitea>WS2000TIR</srccitea>
<srccontr>Used in identifying the location of cold-water springs on the landscape.</srccontr>
</srcinfo>
<srcinfo>
<srccite>
<citeinfo>
<origin>Watershed Sciences, LLC</origin>
<pubdate>2000</pubdate>
<title>Aerial Photography</title>
<geoform>raster digital data</geoform>
<othercit>Watershed Sciences, LLC.  2000.  Remote Sensing Survey of the Upper Klamath River Basin; Color Aerial Photography.  Prepared for the Oregon Department of Environmental Quality. Data collected in 1999.</othercit>
</citeinfo>
</srccite>
<typesrc>aerial photography</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate>1999</caldate>
</sngdate>
</timeinfo>
<srccurr>ground condition</srccurr>
</srctime>
<srccitea>WS2000AP</srccitea>
<srccontr>Used in identifying the location of cold-water springs on the landscape.</srccontr>
</srcinfo>
<srcinfo>
<srccite>
<citeinfo>
<origin>Department of the Interior and Department of Agriculture</origin>
<pubdate>1985</pubdate>
<title>Topographic Map</title>
<geoform>map</geoform>
<othercit>U.S. Geological Survey.  Oregon-Klamath Co Quadrangle 7.5-Minute series Topographic Map.  1:24,000.  U.S. Department of the Interior and U.S. Department of Agriculture.  Variable dates (1985-1998).</othercit>
</citeinfo>
</srccite>
<srcscale>24,000</srcscale>
<typesrc>digital topographic map</typesrc>
<srctime>
<timeinfo>
<rngdates>
<begdate>1985</begdate>
<enddate>1998</enddate>
</rngdates>
</timeinfo>
<srccurr>ground condition</srccurr>
</srctime>
<srccitea>USGSTOPO</srccitea>
<srccontr>Used as a reference for digitizing roads, railroads and feature names.</srccontr>
</srcinfo>
<srcinfo>
<srccite>
<citeinfo>
<origin>U.S. Geological Survey</origin>
<pubdate>2000</pubdate>
<title>Digital Orthophoto Quadrangle</title>
<geoform>remote-sensing image</geoform>
</citeinfo>
</srccite>
<srcscale>20,000</srcscale>
<typesrc>digital orthophoto quadrangle</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate>2000</caldate>
</sngdate>
</timeinfo>
<srccurr>ground condition</srccurr>
</srctime>
<srccitea>USGSDOQ2000</srccitea>
<srccontr>Used to digitize channel and floodplain features for 2000.</srccontr>
</srcinfo>
<procstep>
<procdesc>Data Acquisition:  Remotely sensed imagery (historic aerial photos and LiDAR) researched and obtained.</procdesc>
<procdate>2005</procdate>
</procstep>
<procstep>
<procdesc>Digitizing:  Began digitizing channel and floodplain features and river centerlines for 2000. Completed in 2008.  Digitizing Protocol: The Sprague River Project is focused on geomorphic and vegetation changes over time within the active geomorphic floodplain of the Sprague River watershed. We defined the active geomorphic floodplain as the area adjacent to the channel system that is low-lying and displays geomorphic features typical of channel erosion and depositional processes clearly on imagery, including aerial photos, 7.5 min USGS topo maps, and LIDAR images (Watershed Sciences, 2005).  Geomorphic features used to define the extent of the active geomorphic floodplain included point bars, scroll bars, abandoned channels (including oxbows ponds and filled channels), and swell and swale topography.  The active geomorphic floodplain was distinguished from adjacent alluvial surfaces that are smoother and show less evidence of erosion and deposition, although some of these adjacent surfaces may be flooded regularly by overbank flows. Digital data sets were first digitized from the 2000 DOQs.  High resolution LiDAR imagery data (Watershed Sciences, 2005) was used to identify topographic details that assisted in feature classification.  If the feature visible in the LiDAR was not visible in the 2000 DOQ the feature was not digitized.  Additional comparison with the 1998 color air photo mosaic (USFWS 1998) aided in evaluating the 2000 DOQs. The 2000 digital data was then used as a template for digitizing features from the 1968 and 1940s photo sets.  Because the spatial context of this project is focused within the active geomorphic floodplain, interpreting and digitizing the floodplain boundary was prioritized to define area of digitization in all three year sets. Original data sets were digitized in ArcMap as separate shapefiles (line or polygon).  Line files were "buffered" in ArcMAP to generate polygons with a calculable area for these features. All digitizing was reviewed and edited by the graduate research assistants or project leaders for interpretation consistency and data accuracy.  After editing, the shapefiles were input into a geodatabase.  The geodatabase was used to organize the data sets by data type and subtype, feature prioritization, and topology rules.</procdesc>
<srcused>WS2005</srcused>
<srcused>USGSTOPO</srcused>
<srcused>WS2000AP</srcused>
<srcused>WS2000TIR</srcused>
<srcused>USFWSDAP</srcused>
<srcused>USGSDOQ2000</srcused>
<procdate>2005</procdate>
</procstep>
<procstep>
<procdesc>Quality Assurance:  Ran two stages of topology as discussed in the Logical Consistency Report</procdesc>
<procdate>2008</procdate>
</procstep>
</lineage>
</dataqual>
<spdoinfo>
<direct>Vector</direct>
<ptvctinf>
<sdtsterm>
<sdtstype>G-polygon</sdtstype>
<ptvctcnt>664</ptvctcnt>
</sdtsterm>
</ptvctinf>
</spdoinfo>
<spref>
<horizsys>
<planar>
<gridsys>
<gridsysn>Universal Transverse Mercator</gridsysn>
<utm>
<utmzone>10</utmzone>
<transmer>
<sfctrmer>0.999600</sfctrmer>
<longcm>-123.000000</longcm>
<latprjo>0.000000</latprjo>
<feast>500000.000000</feast>
<fnorth>0.000000</fnorth>
</transmer>
</utm>
</gridsys>
<planci>
<plance>coordinate pair</plance>
<coordrep>
<absres>0.000100</absres>
<ordres>0.000100</ordres>
</coordrep>
<plandu>meters</plandu>
</planci>
</planar>
<geodetic>
<horizdn>North American Datum of 1983</horizdn>
<ellips>Geodetic Reference System 80</ellips>
<semiaxis>6378137.000000</semiaxis>
<denflat>298.257222</denflat>
</geodetic>
</horizsys>
</spref>
<eainfo>
<detailed>
<enttyp>
<enttypl>
Sprague_River_Oregon_Water_2000</enttypl>
<enttypd>Water features in 2000</enttypd>
<enttypds>U.S. Geological Survey</enttypds>
</enttyp>
<attr>
<attrlabl>OBJECTID</attrlabl>
<attrdef>Internal feature number.</attrdef>
<attrdefs>ESRI</attrdefs>
<attrdomv>
<udom>Sequential unique whole numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>Shape</attrlabl>
<attrdef>Feature geometry.</attrdef>
<attrdefs>ESRI</attrdefs>
<attrdomv>
<udom>Coordinates defining the features.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>TYPE</attrlabl>
<attrdef>Type of water</attrdef>
<attrdefs>U.S. Geological Survey</attrdefs>
<attrdomv>
<edom>
<edomv>PC - Primary Channel</edomv>
<edomvd>The main channel of the Sprague, Sycan, South Fork Sprague and North Fork Sprague rivers.  The primary channel was identified as the widest channel (at the upstream and branching junction) of the linear wetted river feature within the floodplain boundary.</edomvd>
<edomvds>U.S. Geological Survey</edomvds>
</edom>
<edom>
<edomv>SC - Secondary Channel</edomv>
<edomvd>A linear wetted channel feature connected to a Primary Channel feature (or another secondary channel feature) at both the downstream and upstream ends.</edomvd>
<edomvds>U.S. Geological Survey</edomvds>
</edom>
<edom>
<edomv>BW - Backwater</edomv>
<edomvd>A wetted feature connected to a Primary Channel or Secondary Channel feature at only the downstream or upstream end.</edomvd>
<edomvds>U.S. Geological Survey</edomvds>
</edom>
<edom>
<edomv>TC - Tributary Channel</edomv>
<edomvd>A wetted feature that originates outside the floodplain boundary at a separate source than channel features.  Tributaries must connect at the most downstream end to a Primary or Secondary Channel feature.</edomvd>
<edomvds>U.S. Geological Survey</edomvds>
</edom>
<edom>
<edomv>PD - Pond</edomv>
<edomvd>A wetted feature on the floodplain that is not visibly connected on the surface to a channel feature.  Ponds are commonly located in abandoned channels or other depressions on the floodplain.  Ponds most often have an oblong or rounded shape with a clearly defined feature boundary.</edomvd>
<edomvds>U.S. Geological Survey</edomvds>
</edom>
<edom>
<edomv>BP - Built Pond</edomv>
<edomvd>A wetted feature that is not visibly connected to a channel feature.  Built ponds are constructed by humans.  Built ponds often have a more geometric shape and boundary than natural ponds.  Usually there was a levee around part or all of this feature  boundary.</edomvd>
<edomvds>U.S. Geological Survey</edomvds>
</edom>
<edom>
<edomv>SP - Spring</edomv>
<edomvd>A wetted feature that is identified as a spring on U.S.G.S. topographic maps, has a cooler water temperature than adjacent ponds and channels on the FLIR data (Watershed Sciences, 2000), or is known to be a spring from field observations.  Springs were present on all sets of aerial photos used, but shape varied slightly on each photo set.   Boundaries of springs are well defined, likely because of a consistent base flow.</edomvd>
<edomvds>U.S. Geological Survey</edomvds>
</edom>
<edom>
<edomv>SPC - Spring Channel</edomv>
<edomvd>A wetted feature that connects a spring to a channel feature (Primary or Secondary Channel) or other wetted feature on the floodplain.</edomvd>
<edomvds>U.S. Geological Survey</edomvds>
</edom>
<edom>
<edomv>IW - Irrigation Water</edomv>
<edomvd>A wetted feature on the floodplain contained or connected to an irrigation ditch feature or other irrigation water source (pump, well or pond).  Irrigation water features are temporary features that occupy low areas on the floodplain. Distribution of Irrigation Water depends on irrigation practices at the time the photo set was taken.  Irrigation water features are often irregularly shaped with diffuse boundaries.  Because of their diffuse nature, boundaries of irrigation water features were defined based on a majority pixels with gray-black coloration against an otherwise lighter floodplain surface.  Distinguishing between pond features and irrigation water features was often difficult.  In general a feature was designated as irrigation water if it had irregular boundaries, connection to other irrigation water features, presence of feature in only one year of aerial photos, relative elevation of the feature to channel features would not have allowed it to be naturally wetted, and presence of levees or other structures separating the water feature from channel features.  In some instances, an irrigation water feature in one year may overlap a pond feature present in other years due to active irrigation that inundated the pond area. In this case, the pond feature was not mapped in the irrigation year.</edomvd>
<edomvds>U.S. Geological Survey</edomvds>
</edom>
<edom>
<edomv>OW - Other Water</edomv>
<edomvd>Any other wetted feature within the floodplain boundary not otherwise classified.  No Water features were attributed as Other.</edomvd>
<edomvds>U.S. Geological Survey</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>SUBTYPE</attrlabl>
<attrdef>Subtype code</attrdef>
<attrdefs>U.S. Geological Survey</attrdefs>
<attrdomv>
<edom>
<edomv>20</edomv>
<edomvd>Primary Channel</edomvd>
<edomvds>U.S. Geological Survey</edomvds>
</edom>
<edom>
<edomv>21</edomv>
<edomvd>Secondary Channel</edomvd>
<edomvds>U.S. Geological Survey</edomvds>
</edom>
<edom>
<edomv>22</edomv>
<edomvd>Backwater</edomvd>
<edomvds>U.S. Geological Survey</edomvds>
</edom>
<edom>
<edomv>23</edomv>
<edomvd>Pond</edomvd>
<edomvds>U.S. Geological Survey</edomvds>
</edom>
<edom>
<edomv>24</edomv>
<edomvd>Spring</edomvd>
<edomvds>U.S. Geological Survey</edomvds>
</edom>
<edom>
<edomv>25</edomv>
<edomvd>Spring Channel</edomvd>
<edomvds>U.S. Geological Survey</edomvds>
</edom>
<edom>
<edomv>26</edomv>
<edomvd>Irrigation Water</edomvd>
<edomvds>U.S. Geological Survey</edomvds>
</edom>
<edom>
<edomv>27</edomv>
<edomvd>Built Pond</edomvd>
<edomvds>U.S. Geological Survey</edomvds>
</edom>
<edom>
<edomv>28</edomv>
<edomvd>Tributary Channel</edomvd>
<edomvds>U.S. Geological Survey</edomvds>
</edom>
<edom>
<edomv>29</edomv>
<edomvd>Other Water</edomvd>
<edomvds>U.S. Geological Survey</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>NAME</attrlabl>
<attrdef>Name of water feature</attrdef>
<attrdefs>U.S. Geological Survey</attrdefs>
<attrdomv>
<udom>Unique name of water feature</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>NOTE_</attrlabl>
<attrdef>Notes</attrdef>
<attrdefs>U.S. Geological Survey</attrdefs>
<attrdomv>
<udom>Notes</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>Shape_Length</attrlabl>
<attrdef>Length of feature in internal units.</attrdef>
<attrdefs>ESRI</attrdefs>
<attrdomv>
<udom>Positive real numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>SHAPE_Area</attrlabl>
<attrdef>Area of feature in internal units squared.</attrdef>
<attrdefs>ESRI</attrdefs>
<attrdomv>
<udom>Positive real numbers that are automatically generated.</udom>
</attrdomv>
</attr>
</detailed>
</eainfo>
<distinfo>
<distrib>
<cntinfo>
<cntorgp>
<cntorg>U.S. Geological Survey</cntorg>
</cntorgp>
<cntpos>Ask USGS -- Water Webserver Team</cntpos>
<cntaddr>
<addrtype>mailing address</addrtype>
<address>445 National Center</address>
<city>Reston</city>
<state>VA</state>
<postal>20192</postal>
<country>USA</country>
</cntaddr>
<cntvoice>1-888-275-8747 (1-888-ASK-USGS)</cntvoice>
<cntemail>http://water.usgs.gov/user_feedback_form.html</cntemail>
</cntinfo>
</distrib>
<resdesc>Downloadable Data</resdesc>
<distliab>Although these data have been used by the U.S. Geological Survey, U.S. Department of the Interior, no warranty expressed or implied is made by the U.S. Geological Survey as to the accuracy of the data.  The act of distribution shall not constitute any such warranty, and no responsibility is assumed by the U.S. Geological Survey in the use of these data, software, or related materials. The use of firm, trade, or brand names in this report is for identification purposes only and does not constitute endorsement by the U.S. Geological Survey.  The names mentioned in this document may be trademarks or registered trademarks of their respective trademark owners.</distliab>
<stdorder>
<digform>
<digtinfo>
<formname>ESRI Geodatabase Feature Class</formname>
<formcont>PKZIP compression</formcont>
<filedec>Winzip</filedec>
<transize>1000</transize>
</digtinfo>
<digtopt>
<onlinopt>
<computer>
<networka>
<networkr>http://water.usgs.gov/GIS/dsdl/SpragueRiverAnalysis.zip</networkr>
</networka>
</computer>
</onlinopt>
</digtopt>
</digform>
<fees>None. This dataset is provided by USGS as a public service.</fees>
</stdorder>
</distinfo>
<metainfo>
<metd>20090930</metd>
<metc>
<cntinfo>
<cntorgp>
<cntorg>U.S. Geological Survey</cntorg>
</cntorgp>
<cntpos>Ask USGS -- Water Webserver Team</cntpos>
<cntaddr>
<addrtype>mailing address</addrtype>
<address>445 National Center</address>
<city>Reston</city>
<state>VA</state>
<postal>20192</postal>
<country>USA</country>
</cntaddr>
<cntvoice>1-888-275-8747 (1-888-ASK-USGS)</cntvoice>
<cntemail>http://answers.usgs.gov/cgi-bin/gsanswers?pemail=h2oteam&amp;subject=GIS+Dataset+spragueriveroregon_water_2000</cntemail>
</cntinfo>
</metc>
<metstdn>FGDC Content Standards for Digital Geospatial Metadata</metstdn>
<metstdv>FGDC-STD-001-1998</metstdv>

</metainfo>
</metadata>
