<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSPY v2004 rel. 3 U (http://www.xmlspy.com) by Kenneth Lanfear (private) -->
<?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>Jennifer L. Krstolic</origin>
				<origin>Sarah K. Martucci</origin>
				<origin>Katharine J. Hopkins</origin>
				<origin>Jeff P. Raffensperger</origin>
				<pubdate>2005</pubdate>
				<title>SIR2005-5073_CBRWM_watersheds</title>
				<geoform>vector digital data</geoform>
				<serinfo>
					<sername>SIR</sername>
					<issue>2005-5073</issue>
				</serinfo>
				<pubinfo>
					<pubplace>Baltimore, MD</pubplace>
					<publish>U.S. Geological Survey</publish>
				</pubinfo>
				<othercit>Spatial data associated with the Scientific Investigations Report, 'Development of Land Segmentation, Stream-Reach Network, and Watersheds in Support of Hydrological Simulation Program-Fortran (HSPF) Modeling, Chesapeake Bay Watershed, and Adjacent Parts of Maryland, Delaware, and Virginia'

By Sarah K. Martucci, Jennifer L. Krstolic, and Jeff P. Raffensperger (U.S. Geological Survey), and Katharine J. Hopkins (University of Maryland Center for Environmental Science)</othercit>
				<onlink>http://water.usgs.gov/lookup/getspatial?sir2005-5073_CBRWM_watersheds</onlink>
			</citeinfo>
		</citation>
		<descript>
			<abstract>This is an ArcGIS dataset depicting watershed segments in the Chesapeake Bay Watershed and adjacent states of New York, Pennsylvania, Maryland, West Virginia, Delaware, Virginia, North Carolina, and Tennessee.  Thirty-meter-resolution Digital Elevation Model data were used to delineate watersheds for each stream reach. State watershed boundaries replaced the Digital Elevation Model-derived watersheds where coincident. The data are projected to the UTM grid coordinate system - Zone 18 NAD27.
</abstract>
			<purpose>The U.S. Geological Survey, Chesapeake Bay Program, Interstate Commission on the Potomac River Basin, Maryland Department of the Environment, Virginia Department of Conservation and Recreation, and the University of Maryland are collaborating on the Chesapeake Bay Regional Watershed Model (CBRWM), using Hydrological Simulation Program - FORTRAN to simulate streamflow and concentrations and loads of nutrients and sediment. In order to establish a framework for model simulation, digital spatial datasets were created defining the discretization of the model region the (including the Chesapeake Bay Watershed, as well as the adjacent parts of Maryland, Delaware, Virginia, Tennessee, and North Carolina outside the watershed) into land segments, a stream-reach network, and associated watersheds.
The stream-reach network for the Chesapeake Bay Watershed part of the model region was based on the USGS Chesapeake Bay SPARROW model stream-reach network. Since that network was created only for the Chesapeake Bay Watershed, the rest of the model region uses a 1:500,000-scale stream-reach network. To standardize watershed size, streams with mean annual streamflow of less than 100 cubic feet per second were excluded based on attributes from the dataset. Additional changes were made to enhance the data and to allow for inclusion of stream reaches with monitoring data that were not part of the original network. The watersheds were coded to indicate major and minor basin, mean annual streamflow, and each watershed's unique identifier as well as that of the downstream watershed. 

The watershed dataset represents the watershed areas included in the CBRWM.  The derived product of the watersheds intersected with land segments serves as the model units.  The watersheds are to be used with the CBRWM.  Other uses are not suggested.
</purpose>
			<supplinf>Any use of trade, product, or firm names is for descriptive purposes only and does not imply endorsement by the U.S. Geological Survey. 

Although this Federal Geographic Data Committee-compliant metadata file is intended to document the data set in nonproprietary form, as well as in ARC/INFO format, this metadata file may include some ARC/INFO-specific terminology.

Related websites:
Chesapeake Bay Program Home: 
http://www.chesapeakebay.net/index.cfm

Chesapeake Bay Program Modeling efforts:
http://www.chesapeakebay.net/model.htm

Chesapeake Bay Program work related to this GIS dataset:
http://www.chesapeakebay.net/phase5.htm

SPARROW Modeling and stream-reach network development
http://md.water.usgs.gov/publications/wrir-99-4054/

Maryland Department of the Environment (MDE)
http://www.mde.state.md.us/

Interstate Commission on the Potomac River Basin (ICPRB)
http://www.potomacriver.org/

Virginia Department of Conservation and Recreation (DCR)
http://www.dcr.state.va.us/

University of Maryland
http://www.umd.edu/</supplinf>
		</descript>
		<timeperd>
			<timeinfo>
				<sngdate>
					<caldate>2005</caldate>
				</sngdate>
			</timeinfo>
			<current>publication date</current>
		</timeperd>
		<status>
			<progress>Complete</progress>
			<update>As needed</update>
		</status>
		<spdom>
			<bounding>
				<westbc>
-84.464484</westbc>
				<eastbc>
-74.577530</eastbc>
				<northbc>
42.987273</northbc>
				<southbc>
35.921916</southbc>
			</bounding>
		</spdom>
		<keywords>
			<theme>
				<themekt>ISO19119 Topic Category</themekt>
				<themekey>inlandWaters</themekey>
				<themekey>environment</themekey>
				<themekey>farming</themekey>
				<themekey>biota</themekey>
			</theme>
			<theme>
				<themekt>none</themekt>
				<themekey>Watershed</themekey>
				<themekey>Topography</themekey>
				<themekey>elevation</themekey>
				<themekey>HSPF model</themekey>
				<themekey>Segmentation</themekey>
			</theme>
			<place>
				<placekt>none</placekt>
				<placekey>Chesapeake Bay Watershed</placekey>
				<placekey>DE</placekey>
				<placekey>MD</placekey>
				<placekey>NC</placekey>
				<placekey>NY</placekey>
				<placekey>PA</placekey>
				<placekey>TN</placekey>
				<placekey>VA</placekey>
				<placekey>WV</placekey>
			</place>
			<temporal>
				<tempkt/>
				<tempkey>2000-2005</tempkey>
			</temporal>
		</keywords>
		<accconst>none</accconst>
		<useconst>These watersheds are to be used with the Chesapeake Bay Regional Watershed Model or projects related to this work.  The watershed areas are not USGS published drainage areas for stream gages.</useconst>
		<ptcontac>
			<cntinfo>
				<cntorgp>
					<cntorg>U.S. Geological Survey</cntorg>
				</cntorgp>
				<cntpos>Ask USGS ? Water Webserver Team</cntpos>
				<cntaddr>
					<addrtype>mailing and physical address</addrtype>
					<address>445 National Center</address>
					<city>Reston</city>
					<state>Virginia</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+sir2005-5073_CBRWM</cntemail>
			</cntinfo>
		</ptcontac>
		<browse>
			<browsen>http://water.usgs.gov/GIS/browse/SIR2005-5073_Cbshed.jpg</browsen>
			<browsed>Watershed segments of the Chesapeake Bay Regional Watershed Model</browsed>
			<browset>JPEG</browset>
		</browse>
		<native>Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.0.0.535</native>
	</idinfo>
	<dataqual>
		<attracc>
			<attraccr>Each attribute value within this coverage has been examined to ensure it contains quality information. Specific attributes that have been calculated from ancillary data are included, such as Up elevation, Down Elevation, stream length, and total upstream area.  These attributes have accuracy values approximately in line with their data sources.  Specific attributes of special concern are mentioned here.  Others are defined in the "entity Attribute" section.</attraccr>
			<qattracc>
				<attraccv>PROV</attraccv>
				<attracce>Physiographic Province.  This attribute was assigned to each watershed from a 1:2 million province coverage.  Watersheds which cross between two provinces were manually assigned to one province.  These are for visualization and grouping only.  They do not necessarily represent correct physiographic conditions in the watersheds.</attracce>
			</qattracc>
			<qattracc>
				<attraccv>FLOW</attraccv>
				<attracce>Flow is a value representing the relative size of the river in the watershed.  The value of Flow is calculated from the mean monthly discharge which was recorded in the EPA RF3 enhanced stream coverage.  The following formula was used to calculate the FLOW:    Round(log10(mean Monthly Q) * 3 - 5)

EXCEPTIONS:
For segments that have a value equal to or less than zero for mean annual flow (MeanQ), the Flow term was set to zero. Some streams do not have MeanQ in the data base, they have 99999. These areas are all coastal or small headwater streams, so the Flow term was set to zero.  For watersheds that do not have streams (DE, west corner MD, a few VA) the flow parameter was set to zero.</attracce>
			</qattracc>
			<qattracc>
				<attraccv>STRM_LENG_M</attraccv>
				<attracce>Stream Length in Meters.  
The stream network was intersected with the watershed coverage to attribute each river with the UNIQID for each watershed it flows through.  Stream length was summarized for each watershed. Lengths are only calculated for watersheds that have modeled rivers.  Reservoirs have no stream lengths, nor do watersheds with DSID= 0.  Lengths were calculated while datasets were projected in Albers NAD83.  

Confluences of the stream coverage do not exactly match the watershed boundaries, in that some confluences meet downstream of a watershed boundary.  This creates a little extra length in some watersheds where 'two' streams are present in stead of one.</attracce>
			</qattracc>
			<qattracc>
				<attraccv>tot_UPAREA_m2</attraccv>
				<attracce>Total upstream area in square meters.
The polygon area from the coverage was extracted and summed in a spreadsheet using the UNIQID and DSID relationship.  This field represents the total upstream area including the area of the polygon being queried.  Areas were calculated while dataset was projected in Albers NAD83.  </attracce>
			</qattracc>
			<qattracc>
				<attraccv>UP_Elev_M</attraccv>
				<attracce>Up elevation meters. The lowest elevation in the stream channel at the upstream end of the watershed. Used in conjunction with the DN_elev_m and stream length to calculate channel slope. 30-meter National Elevation Data was used to gather elevation information.  The elevation data is in meters with accuracy ranging from 1--15 meters.  The DEM has the greatest error associated with low relief, such as in the coastal plain.</attracce>
			</qattracc>
			<qattracc>
				<attraccv>DN_elev_M</attraccv>
				<attracce>Down elevation meters. The lowest elevation in the stream channel at the downstream end of the watershed. Used in conjunction with the UP_elev_m and stream length to calculate channel slope.  30-meter National Elevation Data was used to gather elevation information.  The elevation data is in meters with accuracy ranging from 1 - 15 meters.  The DEM has the greatest error associated with low relief, such as in the coastal plain.</attracce>
			</qattracc>
			<qattracc>
				<attraccv>fp_slope</attraccv>
				<attracce>Flood Plain slope.  The slope of the flood plain in a representative section of the watershed.  
National Elevation Data was used to gather elevation information along a line drawn perpendicular to the floodplain.  The elevation change and length of floodplain were calculated from a digital hand-drawn line approximating the width of the floodplain.   The elevation data is in meters with accuracy ranging from 1 - 15 meters.  

These slopes are ratios, not multiplied by 100 to calculate percent.  They have been reviewed using digital raster graphics of USGS topos, stream coverages, and other related data sources.  Without field confirmation, these data represent the most viable approximation of the floodplain slope.</attracce>
			</qattracc>
			<qattracc>
				<attraccv>Totuparea_mi</attraccv>
				<attracce>Total upstream area in square miles.
The polygon area from the coverage was extracted and summed in a spreadsheet using the UNIQID and DSID relationship.  This field represents the total upstream area including the area of the polygon being queried.  Areas were calculated while dataset was projected in Albers NAD83.</attracce>
			</qattracc>
		</attracc>
		<logic>Original data was in ArcInfo coverage format. Topology was built using the Build command (08/30/2004).  The data layer is "topologically clean" as tested with the ArcInfo Build command.  Tolerances: Fuzzy = 0.900, Dangle = 0.000.  

Shapefiles have been compared to the original dataset. Data was converted to shapefile format 07/08/2005.</logic>
		<complete>All watersheds within the states of Virgina, Maryland, and Delaware were included. Only a selected set of watersheds from New York, Pennsylvania, West Virginia, Tennessee, and North Carolina were included.  Upstream portions of watersheds that begin outside the study area, and flow through the study area were included.  Downstream portions of watersheds that exit the study area were excluded.  </complete>
		<posacc>
			<horizpa>
				<horizpar>Most State HUC layers have originially been digitized from USGS 1:240000 quadrangles.  The resulting accuracy of the linework should be consistent with hand-drawn watersheds on paper maps, that were subsequently digitized on-screen.  Lines delineated with the 30-meter NED have been smoothed to remove grid cell edges.</horizpar>
			</horizpa>
		</posacc>
		<lineage>
			<srcinfo>
				<srccite>
					<citeinfo>
						<origin>Virginia Dept of Conservation and Recreation - DSWC</origin>
						<pubdate>19951101</pubdate>
						<title>Virginia's 14 digit hydrologic unit boundaries</title>
						<edition>Edition:  2</edition>
						<geoform>vector digital data</geoform>
						<othercit>The boundaries of the 494 hydrologic units in Virginia at the 14-digit level of detail.  This data set covers the whole state and these units are the immediate subsets of the 11 digit level of hydrologic units in Virginia.

Contact: Karl Huber, 
khuber@dcr.state.va.us, 
(804) 371-7484

This is version 2.  Its primary differences with version 1 are the  following improvements:  

(1) better agreement with the USDA NRCS planned and approved watershed projects, 
(2) incorporation of the  July 1992 NRCS document "Guidelines For Mapping and Digitizing Hydrologic Units", particularly (a) the breaking of water features into different units where physical features (dams, confluences, etc.) exist, (b) the effort to make hydrologic unit boundaries continue across state boundaries, and (c) the coding of units upstream beginning and proceeding downstream,
(3) the incorporation of local and regional watershed geography, 
(4) improved listing of water features within a hydrologic unit, beginning with the most significant feature and stepping down from there, and 
(5) greater linework accuracy to reflect the increased use of this data in a digital file form.</othercit>
					</citeinfo>
				</srccite>
				<typesrc/>
				<srctime>
					<timeinfo>
						<sngdate>
							<caldate>2005</caldate>
						</sngdate>
					</timeinfo>
					<srccurr>publication date</srccurr>
				</srctime>
				<srccitea>DCR HUCS</srccitea>
				<srccontr>Watershed boundary in Virginia</srccontr>
			</srcinfo>
			<srcinfo>
				<srccite>
					<citeinfo>
						<origin>Maryland Department of Natural Resources</origin>
						<pubdate>1998</pubdate>
						<pubtime>Unknown</pubtime>
						<title>swshed12 - Maryland's Third Order Watershed</title>
						<edition>1998</edition>
						<geoform>vector digital data</geoform>
						<pubinfo>
							<pubplace>Annapolis, MD</pubplace>
							<publish>Maryland Department of Natural Resources</publish>
						</pubinfo>
						<othercit>This file is a statewide digital watershed file. It was created primarily for state and federal agency use. The watersheds define Strahler (Strahler 1952 p. 1120) third order stream drainage by contours on U.S. Geological Survey (USGS) 7.5 minute quadrangle map sheets. Some watersheds drainage areas were defined for streams less than third order and some large area watershed were split to maintain a maximum size of 15,000 acres. The watershed boundaries in this file were developed in a joint state and federal effort to create a consistent watershed file for use by all government agencies with an interest in Maryland's watersheds. The U.S. Natural Resources Conservation Service (NRCS) redefined the third order watersheds creating the HUA14 file. This file contains all of the HUA14 watersheds and some added watersheds to maintain water quality sampling sites. It was also used to create the Maryland Sub-Watershed file.</othercit>
						<onlink>http://www.msgic.state.md.us/techtool</onlink>
						<onlink>ftp://dnrftp.dnr.state.md.us/public/SpatialData/Watershed/WShedBndry/swshed12.htm</onlink>
					</citeinfo>
				</srccite>
				<typesrc/>
				<srctime>
					<timeinfo>
						<sngdate>
							<caldate>2005</caldate>
						</sngdate>
					</timeinfo>
					<srccurr>publication date</srccurr>
				</srctime>
				<srccitea>MD HUCS</srccitea>
				<srccontr>Watershed boundary in Maryland</srccontr>
			</srcinfo>
			<srcinfo>
				<srccite>
					<citeinfo>
						<origin>U.S. Geological Survey</origin>
						<pubdate>1999</pubdate>
						<title>National Elevation Dataset</title>
						<edition>1</edition>
						<geoform>raster digital data</geoform>
						<pubinfo>
							<pubplace>Sioux Falls, SD</pubplace>
							<publish>U.S. Geological Survey</publish>
						</pubinfo>
						<othercit>accessed November 16, 2004 at http://ned.usgs.gov/

</othercit>
						<onlink>http://ned.usgs.gov/</onlink>
						<onlink>http://ned.usgs.gov/ned/ned.html</onlink>
						<onlink>http://gisdata.usgs.net/ned/</onlink>
					</citeinfo>
				</srccite>
				<typesrc/>
				<srctime>
					<timeinfo>
						<sngdate>
							<caldate>2005</caldate>
						</sngdate>
					</timeinfo>
					<srccurr>publication date</srccurr>
				</srctime>
				<srccitea>NED</srccitea>
				<srccontr>Data were used for delineation of watersheds as the base-map of the watershed segment coverage.</srccontr>
			</srcinfo>
			<srcinfo>
				<srccite>
					<citeinfo>
						<origin>USDA, Natural Resources Conservation Service</origin>
						<pubdate>19981201</pubdate>
						<title>Hydrologic Units - North Carolina Subbasins</title>
						<edition>1</edition>
						<geoform>vector digital data</geoform>
						<pubinfo>
							<pubplace>Raleigh, North Carolina</pubplace>
							<publish>USDA, Natural Resources Conservation Service</publish>
						</pubinfo>
						<othercit>The USDA-Natural Resources Conservation Service, Raleigh Office in cooperation with the NC Center for Geographic Information &amp; Analysis, and the NC Dept. of Environment, Health and Natural Resources, Division of Water Quality developed the Hydrologic Units-North Carolina digital data to track resource and conservation activities in the state's river basins and subbasins. Using the 14-digit hydrologic unit code the regional, sub-regional, accounting, cataloging, NRCS sub-unit, and NRCS reporting unit boundaries id's are recorded. The area attributes allow the user to see hydrologic unit, river basin and sub-basin levels of geography. This file specifically shows the North Carolina subbasins.

Contact: Silvia Terziotti  USGS, MD,  seterzio@usgs.gov, 
(919) 571-4090</othercit>
						<onlink>http://www.cgia.state.nc.us/cgdb/index.html</onlink>
						<onlink>http://www.cgia.state.nc.us/cgdb/wsw.html</onlink>
					</citeinfo>
				</srccite>
				<typesrc/>
				<srctime>
					<timeinfo>
						<sngdate>
							<caldate>2005</caldate>
						</sngdate>
					</timeinfo>
					<srccurr>publication date</srccurr>
				</srctime>
				<srccitea>NC HUCS</srccitea>
				<srccontr>Watershed boundary in North Carolina</srccontr>
			</srcinfo>
			<srcinfo>
				<srccite>
					<citeinfo>
						<origin>USDA-Natural Resources Conservation Service, Tennessee</origin>
						<pubdate>January 10, 2000</pubdate>
						<title>Tennessee Sub-Watershed Boundaries</title>
						<geoform>Vector Digital Data, Map</geoform>
						<pubinfo>
							<pubplace/>
							<publish>USDA Natural Resources Conservation Service</publish>
						</pubinfo>
						<othercit>This coverage contains Hydrologic Unit Areas and their associated coding for Tennessee watersheds.  The boundaries of these areas were hand delineated at a scale of 1:24,000 and then digitized on screen over DRG's obtained from the Tennessee Valley Authority.</othercit>
						<onlink>http://www.tn.nrcs.usda.gov/</onlink>
					</citeinfo>
				</srccite>
				<typesrc/>
				<srctime>
					<timeinfo>
						<sngdate>
							<caldate>2005</caldate>
						</sngdate>
					</timeinfo>
					<srccurr>publication date</srccurr>
				</srctime>
				<srccitea>TN HUCS</srccitea>
				<srccontr>Watershed boundary in Tennessee</srccontr>
			</srcinfo>
			<srcinfo>
				<srccite>
					<citeinfo>
						<origin>Delaware Department of Natural Resources and Environmental Control (DNREC)</origin>
						<pubdate>1990</pubdate>
						<title>Delaware HUCS</title>
						<geoform>vector digital data</geoform>
						<othercit>The Watersheds were originally digitized from lines that were hand drawn onto 1:24000 USGS topo maps.  The digitizing occurred in the early 1990's. Since then, some of the lines have been slightly modified to correct errors where the lines may have crossed streams.   The data is currently State Plane NAD 83 meters.  It was probably digitized originally inState Plane NAD 27 feet.

Sullivan Deborah S. (DNREC), Deborah.Sullivan@state.de.us, 
302-739-6308</othercit>
					</citeinfo>
				</srccite>
				<typesrc/>
				<srctime>
					<timeinfo>
						<sngdate>
							<caldate>2005</caldate>
						</sngdate>
					</timeinfo>
					<srccurr>publication date</srccurr>
				</srctime>
				<srccitea>DE HUCS</srccitea>
				<srccontr>Watershed boundary in Delaware</srccontr>
			</srcinfo>
			<srcinfo>
				<srccite>
					<citeinfo>
						<origin>Chesapeake Bay Program</origin>
						<pubdate>1999</pubdate>
						<title>West Virginia HUCS</title>
						<geoform>vector digital data</geoform>
						<othercit>The West Virginia HUCS were selected out of the HUC-11 coverage for the Mid-Atlantic level aggregate of the individual state coverages clipped to the Chesapeake Bay Basin boundaries.  </othercit>
						<onlink>ftp://ftp.chesapeakebay.net/pub/Geographic/MidAtlantic/Watersheds/Huc11/</onlink>
					</citeinfo>
				</srccite>
				<typesrc/>
				<srctime>
					<timeinfo>
						<sngdate>
							<caldate>2005</caldate>
						</sngdate>
					</timeinfo>
					<srccurr>publication date</srccurr>
				</srctime>
				<srccitea>WV HUCS</srccitea>
				<srccontr>Watershed boundary in West Virginia</srccontr>
			</srcinfo>
			<srcinfo>
				<srccite>
					<citeinfo>
						<origin>Pennsylvania Department of Environmental Resources (PaDER)</origin>
						<origin>U.S. Geological Survey, Water Resources Division</origin>
						<pubdate>07-01-1996</pubdate>
						<title>Digital drainage basin boundaries of named streams in Pennsylvania</title>
						<edition>1</edition>
						<geoform>vector digital data</geoform>
						<serinfo>
							<sername>Open-File-Report</sername>
							<issue>1996-354</issue>
						</serinfo>
						<pubinfo>
							<pubplace/>
							<publish>USGS</publish>
						</pubinfo>
						<onlink>http://pa.water.usgs.gov/pa_digit.v2.html</onlink>
					</citeinfo>
				</srccite>
				<typesrc/>
				<srctime>
					<timeinfo>
						<sngdate>
							<caldate>2005</caldate>
						</sngdate>
					</timeinfo>
					<srccurr>publication date</srccurr>
				</srctime>
				<srccitea>PA HUCS</srccitea>
				<srccontr>Watershed boundary in Pennsylvania</srccontr>
			</srcinfo>
			<srcinfo>
				<srccite>
					<citeinfo>
						<origin>Upper Susquehanna Coalition</origin>
						<origin>US Geological Survey</origin>
						<origin>US Department of Agriculture</origin>
						<origin>Natural Resources Conservation Service</origin>
						<pubdate>05-01-2002</pubdate>
						<title>11 Digit Hydrologic Unit Code - Watersheds Boundaries for Upper Susquehanna River Watershed</title>
						<edition>1</edition>
						<geoform>vector digital data</geoform>
						<pubinfo>
							<pubplace>Horseheads, New York</pubplace>
							<publish>Upper Susquehanna Coalition</publish>
						</pubinfo>
						<othercit>This geospatial dataset is a hydrologic unit boundary layer that is at the Subwatershed (11-digit) level for the Upper Susquehanna River Watershed. The dataset was developed from original USGS/NRCS HUC data from both Pennsylvania and New York. The dataset was developed by delineating the boundary lines on 1:24,000 base maps and digitizing the delineated lines. Digital Elevation Model data may have been used in part of the process to establish preliminary boundaries.</othercit>
						<onlink>http://www.u-s-c.org/html/GIS_Data.htm</onlink>
					</citeinfo>
				</srccite>
				<typesrc/>
				<srctime>
					<timeinfo>
						<sngdate>
							<caldate>2005</caldate>
						</sngdate>
					</timeinfo>
					<srccurr>publication date</srccurr>
				</srctime>
				<srccitea>Upper-Susq sheds</srccitea>
				<srccontr>Watershed boundary in New York and Pennsylvania</srccontr>
			</srcinfo>
			<procstep>
				<procdesc>Delineated watersheds using 30-meter resolution National Elevation Dataset DEM data, confluences, and streamflow-gaging station locations.  Delineated watersheds were used as boundaries when State HUCS were not available.  </procdesc>
				<srcused>NED</srcused>
				<procdate>September 2001</procdate>
			</procstep>
			<procstep>
				<procdesc>HUC boundaries from each state in the Chesapeake Bay Drainage were combined into one watershed coverage.  The whole states of Virginia, Delaware, and Maryland were included even though some portions do not drain to the Chesapeake Bay.  Adjacent state watersheds were included in Tennessee and North Carolina.  Watershed size was standardized to coincide with a selected stream network.  Watersheds containing streams with at least 100 ft3/sec mean-annual flow were included.  If State HUCS included watershed boundaries for sub-basins, these were omitted.  Watersheds were split at gaging stations as well.  DEM-derived lines were put into the watershed coverage to serve as these breaks.  Some lines were re-drawn manually to correct for DEM errors.  Arc Edit was used for all these editing processes.

General Processing Timeline:
DCR HUCS                November  2001 to July 2002
MD HUCS                   January     2002 to July 2002
Upper-Susq sheds       January     2002 to Dec 2002
PA HUCS                    January     2002 to Dec 2002
WV HUCS                   January     2002 to Dec 2002
NC HUCS                    July           2002 to July 2003
DE HUCS                    July           2002 to July 2003
TN HUCS                    January     2003 to Dec 2003</procdesc>
				<srcused>DCR Hucs</srcused>
				<srcused>MD HUCS</srcused>
				<srcused>Upper-Susq sheds</srcused>
				<srcused>WV HUCS</srcused>
				<srcused>NC HUCS</srcused>
				<srcused>DE HUCS</srcused>
				<srcused>PA HUCS</srcused>
				<procdate>November 2001 - December 2005</procdate>
			</procstep>
			<procstep>
				<procdesc>Attributed dataset with calculated and text fields.  Table editing was done within ArcInfo as well as ArcMap (prior to 9.0).  Calculated fields were created in spreadhseets outside of ArcInfo based on watershed UNIQID.  For example, the flood plain slope calculation was calculated for each model watershed based on UNIQID, the slope calculated in a separate table.  The flood plain slope table was joined to the watershed table, and the attributes were calculated into a new field.</procdesc>
				<procdate>2003 - 2005</procdate>
			</procstep>
			<procstep>
				<procdesc>Dataset projected to UTM zone 18 NAD83.  The original dataset was created in Albers NAD83, and was projected after all the state watersheds were combined into one coverage.   </procdesc>
				<procdate>2003</procdate>
			</procstep>
		</lineage>
	</dataqual>
	<spdoinfo>
		<direct>Vector</direct>
		<ptvctinf>
			<sdtsterm>
				<sdtstype>Complete chain</sdtstype>
				<ptvctcnt>3476</ptvctcnt>
			</sdtsterm>
			<sdtsterm>
				<sdtstype>Label point</sdtstype>
				<ptvctcnt>1062</ptvctcnt>
			</sdtsterm>
			<sdtsterm>
				<sdtstype>GT-polygon composed of chains</sdtstype>
				<ptvctcnt>1062</ptvctcnt>
			</sdtsterm>
			<sdtsterm>
				<sdtstype>Point</sdtstype>
				<ptvctcnt>4</ptvctcnt>
			</sdtsterm>
		</ptvctinf>
	</spdoinfo>
	<spref>
		<horizsys>
			<planar>
				<gridsys>
					<gridsysn>Universal Transverse Mercator</gridsysn>
					<utm>
						<utmzone>18</utmzone>
						<transmer>
							<sfctrmer>0.999600</sfctrmer>
							<longcm>-75.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.000420</absres>
						<ordres>0.000420</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>
cbshedutm.pat</enttypl>
				<enttypd>Polygon Attribute Table</enttypd>
				<enttypds>ESRI</enttypds>
			</enttyp>
			<attr>
				<attrlabl>FID</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>AREA</attrlabl>
				<attrdef>Polygon Area</attrdef>
				<attrdefs>ESRI</attrdefs>
				<attrdomv>
					<rdom>
						<rdommin>0</rdommin>
						<rdommax>undetermined maximum</rdommax>
						<attrunit>square meters</attrunit>
					</rdom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>PERIMETER</attrlabl>
				<attrdef>length of outer boundary</attrdef>
				<attrdefs>ESRI</attrdefs>
				<attrdomv>
					<rdom>
						<rdommin>0</rdommin>
						<rdommax>undetermined maximum</rdommax>
						<attrunit>meters</attrunit>
					</rdom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>CBSHEDUTM#</attrlabl>
				<attrdef>Internal feature number.</attrdef>
				<attrdefs>ESRI</attrdefs>
				<attrdomv>
					<udom>Sequential unique whole numbers that are automatically generated.</udom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>CBSHEDUTM-ID</attrlabl>
				<attrdef>User-defined feature number.</attrdef>
				<attrdefs>ESRI</attrdefs>
				<attrdomv>
					<edom>
						<edomv/>
						<edomvd/>
						<edomvds/>
					</edom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>MAJOR</attrlabl>
				<attrdef>Major Basin Code </attrdef>
				<attrdefs>Data set developer</attrdefs>
				<attrdomv>
					<edom>
						<edomv>P</edomv>
						<edomvd>Potomac River</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>S</edomv>
						<edomvd>Susquehanna River</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>J</edomv>
						<edomvd>James River</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>Y</edomv>
						<edomvd>York River</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>R</edomv>
						<edomvd>Rappahnnock River</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>X</edomv>
						<edomvd>Patuxent River</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>W</edomv>
						<edomvd>Upper West Shore, Cove Point to Susquehanna</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>E</edomv>
						<edomvd>Eastern Shore</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>Y</edomv>
						<edomvd>Youghiogheny River, Maryland west of the CB watershed</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>D</edomv>
						<edomvd>Delaware Bay and coastal</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>T</edomv>
						<edomvd>Upper Tennessee River (Clinch-Powell-Holston)</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>B</edomv>
						<edomvd>Big Sandy River</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>N</edomv>
						<edomvd>New River</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>O</edomv>
						<edomvd>Roanoke-Dan River</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>M</edomv>
						<edomvd>Nottoway-Meherin (and coastal plain)</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>K</edomv>
						<edomvd>Upper Yadkin Basin, (North Carolina drainage)</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>MINOR</attrlabl>
				<attrdef>Minor Basin code (sub basins)</attrdef>
				<attrdefs>Data set developer</attrdefs>
				<attrdomv>
					<edom>
						<edomv>U</edomv>
						<edomvd>Upper</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>L</edomv>
						<edomvd>Lower</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>B</edomv>
						<edomvd>Below the Fall Line (east)</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>W</edomv>
						<edomvd>West Branch Susquehanna</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>J</edomv>
						<edomvd>Juniata River</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>S</edomv>
						<edomvd>Shenandoah River, Potomac Basin</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>A</edomv>
						<edomvd>Appomattox, or Rappahannock, or Patuxent</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>P</edomv>
						<edomvd>Pamunkey River</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>M</edomv>
						<edomvd>Mattaponi River, or Cove Point to Susquehanna</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>O</edomv>
						<edomvd>Youghiogheny (Maryland west of the CB watershed)</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>E</edomv>
						<edomvd>Delaware Bay and coastal</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>S</edomv>
						<edomvd>Big Sandy River</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>R</edomv>
						<edomvd>New River, or Roanoke River</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>D</edomv>
						<edomvd>Roanoke-Dan River</edomvd>
						<edomvds/>
					</edom>
					<edom>
						<edomv>N</edomv>
						<edomvd>Nottoway-Meherin (and coastal plain)</edomvd>
						<edomvds/>
					</edom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>UNIQID</attrlabl>
				<attrdef>Unique ID number of Watershed</attrdef>
				<attrdefs>Data set developer</attrdefs>
				<attrdomv>
					<udom>Unique Number assigned to each watershed </udom>
				</attrdomv>
				<attrvai>
					<attrva>automatically assigned, with some manually assigned, but reviewed</attrva>
					<attrvae/>
				</attrvai>
			</attr>
			<attr>
				<attrlabl>DSID</attrlabl>
				<attrdef>UNIQID of Downstream Watershed</attrdef>
				<attrdefs>data set developer</attrdefs>
				<attrdomv>
					<edom>
						<edomv>any one UNIQID</edomv>
						<edomvd>the value of the downstream watershed that this watershed flows into</edomvd>
						<edomvds>data set developer</edomvds>
					</edom>
					<edom>
						<edomv>0</edomv>
						<edomvd>No modeled river reach (no F-Table), most of these are estuarine watersheds. some are areas that drain out of the study area. </edomvd>
						<edomvds>data set developer</edomvds>
					</edom>
					<edom>
						<edomv>1</edomv>
						<edomvd>Modeled reach drains directly to Estuary, no other watershed</edomvd>
						<edomvds>data set developer</edomvds>
					</edom>
				</attrdomv>
				<attrvai>
					<attrva>manually assigned, but reviewed</attrva>
					<attrvae/>
				</attrvai>
			</attr>
			<attr>
				<attrlabl>FLOW</attrlabl>
				<attrdef>Calculater term representing relative size of the river:  Round (log10 (mean Monthly Q) * 3 - 5)</attrdef>
				<attrdefs>data set developer</attrdefs>
				<attrdomv>
					<rdom>
						<rdommin>0</rdommin>
						<rdommax>9</rdommax>
						<attrunit>relative units, Log scale</attrunit>
					</rdom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>LAKE</attrlabl>
				<attrdef>Reservoir category (Binary)</attrdef>
				<attrdefs>Data set developer</attrdefs>
				<attrdomv>
					<edom>
						<edomv>0</edomv>
						<edomvd>No reservoir modeled</edomvd>
						<edomvds>data set developer</edomvds>
					</edom>
					<edom>
						<edomv>1</edomv>
						<edomvd>Entire watershed modeled as reservoir</edomvd>
						<edomvds>data set developer</edomvds>
					</edom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>PROV</attrlabl>
				<attrdef>Physiographic Province code</attrdef>
				<attrdefs>U.S. Geological Survey</attrdefs>
				<attrdomv>
					<edom>
						<edomv>CP</edomv>
						<edomvd>Coastal Plain</edomvd>
						<edomvds>U.S. Geological Survey</edomvds>
					</edom>
					<edom>
						<edomv>VR</edomv>
						<edomvd>Valley and Ridge</edomvd>
						<edomvds>U.S. Geological Survey</edomvds>
					</edom>
					<edom>
						<edomv>PD</edomv>
						<edomvd>Piedmont</edomvd>
						<edomvds>U.S. Geological Survey</edomvds>
					</edom>
					<edom>
						<edomv>AP</edomv>
						<edomvd>Appalachian Plateau</edomvd>
						<edomvds>U.S. Geological Survey</edomvds>
					</edom>
					<edom>
						<edomv>BR</edomv>
						<edomvd>Blue Ridge</edomvd>
						<edomvds>U.S. Geological Survey</edomvds>
					</edom>
				</attrdomv>
				<attrvai>
					<attrva>small scale map used, and some manual assignment</attrva>
					<attrvae/>
				</attrvai>
			</attr>
			<attr>
				<attrlabl>STRM_LENG_M</attrlabl>
				<attrdef>Length of Stream Reach (meters) for modeled river reaches. Watersheds without modeled reaches have zero values for stream length.</attrdef>
				<attrdefs>dataset developer</attrdefs>
				<attrdomv>
					<rdom>
						<rdommin>0</rdommin>
						<rdommax>Undetermined maximum</rdommax>
						<attrunit>meters</attrunit>
					</rdom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>TOT_UPAREA_M</attrlabl>
				<attrdef>Total contributing drainage area to bottom of reach (square meters)</attrdef>
				<attrdefs>Data set developer</attrdefs>
				<attrdomv>
					<rdom>
						<rdommin>0</rdommin>
						<rdommax>Undetermined maximum</rdommax>
						<attrunit>square meters</attrunit>
					</rdom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>TOTUPAREA_MI</attrlabl>
				<attrdef>Total contributing drainage area to bottom of reach (square miles)</attrdef>
				<attrdefs>Data set developer</attrdefs>
				<attrdomv>
					<rdom>
						<rdommin>0</rdommin>
						<rdommax>Undetermined maximum</rdommax>
						<attrunit>square miles</attrunit>
					</rdom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>UP_ELEV_M</attrlabl>
				<attrdef>Up stream elevation of channel (meters)</attrdef>
				<attrdefs>Data set developer</attrdefs>
				<attrdomv>
					<rdom>
						<rdommin>0</rdommin>
						<rdommax>Undetermined maximum</rdommax>
						<attrunit>meters</attrunit>
					</rdom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>DN_ELEV_M</attrlabl>
				<attrdef>Down stream elevation of channel (meters)</attrdef>
				<attrdefs>Data set developer</attrdefs>
				<attrdomv>
					<rdom>
						<rdommin>0</rdommin>
						<rdommax>Undetermined maximum</rdommax>
						<attrunit>meters</attrunit>
					</rdom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>FP_SLOPE</attrlabl>
				<attrdef>Floodplain slope (unitless)</attrdef>
				<attrdefs>Data set developer</attrdefs>
				<attrdomv>
					<rdom>
						<rdommin>greater than zero</rdommin>
						<rdommax>Undetermined maximum</rdommax>
						<attrunit>ratio</attrunit>
					</rdom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>CATCODE2</attrlabl>
				<attrdef>Concatenation of Major Minor FLOW UNIQID DSID</attrdef>
				<attrdefs>Data set developer</attrdefs>
				<attrdomv>
					<udom>Concatenation of Major Minor FLOW UNIQID DSID fields</udom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>DAM_NAME</attrlabl>
				<attrdef>Name of the dam or reservior if present</attrdef>
				<attrdefs>Data set developer</attrdefs>
				<attrdomv>
					<codesetd>
						<codesetn>Dam_name</codesetn>
						<codesets>various sources based upon state</codesets>
					</codesetd>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>MAJMIN</attrlabl>
				<attrdef>Major_Minor Concatanation</attrdef>
				<attrdefs>Data set developer</attrdefs>
				<attrdomv>
					<edom>
						<edomv>SU</edomv>
						<edomvd>Susquehanna Upper, above confluence with West Branch</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>SW</edomv>
						<edomvd>West Branch Susquehanna</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>SJ</edomv>
						<edomvd>Juniata River</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>SL</edomv>
						<edomvd>Susquehanna, below confluence with West Branch</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>PU</edomv>
						<edomvd>Potomac Upper, above confluence with Shenandoah</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>PS</edomv>
						<edomvd>Shenandoah River</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>PL</edomv>
						<edomvd>Monocacy and Potomac, below Shenandoah to fall line</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>PB</edomv>
						<edomvd>Potomac, below fall line</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>JU</edomv>
						<edomvd>James Upper, to Blue Ridge Mtns, near or below Glasgow, VA</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>JL</edomv>
						<edomvd>James Lower, below Glasgow to fall line</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>JA</edomv>
						<edomvd>Appomattox</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>JB</edomv>
						<edomvd>James River, below fall line</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>YP</edomv>
						<edomvd>Pamunkey River</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>YM</edomv>
						<edomvd>Mattaponi River</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>YB</edomv>
						<edomvd>York, below fall line</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>RA</edomv>
						<edomvd>Rappahannock River</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>RB</edomv>
						<edomvd>Rappahannock, below fall line</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>XA</edomv>
						<edomvd>Patuxent River, above fall line</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>XB</edomv>
						<edomvd>Patuxent River, below fall line</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>WM</edomv>
						<edomvd>Cove Point to Susquehanna</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>EU</edomv>
						<edomvd>Upper Eastern Shore, Susquehanna to Choptank</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>EL</edomv>
						<edomvd>Lower Eastern Shore, below Choptank</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>YO</edomv>
						<edomvd>Youghiogheny (Maryland west of the CB watershed)</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>DE</edomv>
						<edomvd>Delaware Bay and coastal</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>KU</edomv>
						<edomvd>NC basin Upper Yadkin basin</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>TU</edomv>
						<edomvd>Upper Tennessee (Clinch-Powell-Holston)</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>BS</edomv>
						<edomvd>Big Sandy</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>NR</edomv>
						<edomvd>New River</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>OD</edomv>
						<edomvd>Roanoke-Dan River</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>OR</edomv>
						<edomvd>Roanoke River</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
					<edom>
						<edomv>MN</edomv>
						<edomvd>Nottoway-Meherin (and coastal plain)</edomvd>
						<edomvds>Data set developer</edomvds>
					</edom>
				</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>
		<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>ARCE</formname>
					<formcont>Polygon coverage</formcont>
					<filedec>zipped, Arc Interchange file named cb_shed_e00.zip</filedec>
					<transize>8792 KB</transize>
				</digtinfo>
				<digtopt>
					<onlinopt>
						<computer>
							<networka>
								<networkr>http://water.usgs.gov/GIS/dsdl/sir2005-5073_shed_e00.zip</networkr>
							</networka>
						</computer>
					</onlinopt>
				</digtopt>
			</digform>
			<digform>
				<digtinfo>
					<formname>shapefile</formname>
					<filedec>zipped Shapefile named cb_shed_shape.zip</filedec>
					<transize>13987</transize>
				</digtinfo>
				<digtopt>
					<onlinopt>
						<computer>
							<networka>
								<networkr>http://water.usgs.gov/GIS/dsdl/sir2005-5073_shed_shape.zip</networkr>
							</networka>
						</computer>
					</onlinopt>
				</digtopt>
			</digform>
			<digform>
				<digtinfo>
					<formname>SDTS</formname>
					<filedec>Zipped SDTS format named cb_shed_SDTS.zip</filedec>
					<transize>4492 KB</transize>
				</digtinfo>
				<digtopt>
					<onlinopt>
						<computer>
							<networka>
								<networkr>http://water.usgs.gov/GIS/dsdl/sir2005-5073_shed_sdts.zip</networkr>
							</networka>
						</computer>
					</onlinopt>
				</digtopt>
			</digform>
			<fees>None.  This dataset is provided by USGS as a public service.</fees>
		</stdorder>
	</distinfo>
	<metainfo>
		<metd>20041122</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://water.usgs.gov/user_feedback_form.html</cntemail>
			</cntinfo>
		</metc>
		<metstdn>FGDC Content Standards for Digital Geospatial Metadata</metstdn>
		<metstdv>FGDC-STD-001-1998</metstdv>
	</metainfo>
</metadata>
