Stafford, Jim N.19991124OEPA_ohio_huc14_NRCSVersion 1.02vector digital dataColumbus, Ohio, USANatural Resources Conservation Service (NRCS)withheldOEPA_ohio_huc14_NRCS
This coverage contains 14 Digit Hydrologic Unit Boundaries and Codes for
the State of Ohio.
This data set will be used by various agencies concerned with water and
other natural resource conservation in Ohio to locate data by watershed.
It is subject to use by others to locate other data by watershed. .
en19991124publication dateAs needed-84.918519-80.47970741.99389238.3802221310232.6378032518339.431888146857.9347771455206.012027Reference to a formally registered thesaurus or a similar authoritative source of theme keywords. REQUIRED.HydrologicWatershedSubwatershedOhioNone
The U.S. Department of Agriculture, Natural Resources Conservation Service,
should be acknowledged as the data source in products derived from these
data. These data should not be used at scales greater than 1:24,000. This
data set is to be used as a primary reference source. This is public
information and may be interpreted by organizations, agencies, units of
government, or others based on needs; however, they are responsible for the
appropriate application. Federal, State, or local regulatory bodies are not
to reassign to the Natural Resources Conservation Service any authority for
the decisions they make. The Natural Resources Conservation Service will not
perform any evaluations of these maps for purposes related solely to State
or local regulatory programs. Photographic or digital enlargement of these
maps to scales greater than that at which they were originally delineated
can cause misrepresentation of the data. If enlarged, the maps will not
include the fine detail that would be appropriate for mapping at the small
scale. Digital data files are periodically updated. Files are dated, and
users are responsible of obtaining the latest version of the data.
Jim N.StaffordNatural Resources Conservation Servicemailing address
200 N. High Street, Rm. 522
ColumbusOH43215USA(614) 255-2466(614) 255-2548jim.stafford@oh.nrcs.usda.govESRI ArcCatalog 9.2.0.1324
U. S. Department of Agriculture, Natural Resources
Conservation Service
Geospatial_Data_Presentation_Form: Map, Table, TextFile Geodatabase Feature Class
Polygon identifiers were manually checked with the original base map using
the attribute file. Verification on polygon identification continuity on
each side of a neatline is done visually on the screen as adjacent
quandrangles representations are assembled into larger area data layers.
Certain node/geometry and topology (GT) polygon/chain relationships are
collected or generated to satisfy topological requirements. (The GT-polygon
corresponds to a hydrologic unit or a portion of a hydrologic unit.) Some of
these requirements include: chains must begin and end at nodes, left and
right GT-polygons are defined for each chain element and are consistent
throughout, and the chains representing the limits of the file (neatlines)
are free of gaps. The tests of logical consistency are performed using
vendor software. The neatline is generated by connecting the explicitly
entered four corners of the digital file. All data outside the enclosed
region are ignored and data crossing geographically straight lines are
clipped at the neatline. Neatline straightening aligns the digitized edges
of the digital data with the generated neatline (i.e., with the
longitude/latitude lines in geographic coordinates). All internal polygons
are tested for closure with vendor software and are checked on hard copy
plots. All data are checked for common boundary lines (i.e., adjacent
polygons with the same label). Quadrangles are edge matched within the
Subbasin area and edge locations generally do not deviate from centerline
more than 0.01 inches.
Having been reviewed various times and by various interested parties, most
omissions and errors have hopefully been removed. Selection of boundary
locations were largely dependent on the original digitization where
watershed boundaries were indiscriminately digitized from all divides
contained on the USGS base maps. By aggregation of original polygons,
appropriate watershed and subwatersheds boundaries were obtained in almost
all cases. As enumerated below, additional lines were digitized in a few
instances to allow for coordination across state lines, to subdivide large
polygons to more closely follow acreage guidelines for 14-digit
subwatersheds, and to fix errors.
A Hydrologic unit is an area that has a common surface water drainage
outlet. For the purposes of this effort, areas (not pure hydrologic
units) are often grouped together depending upon their size, to form the
desired size of hydrologic unit. Areas grouped at or below the 250,000
acre size, are referred to as watersheds with an eleven character code.
The watersheds are then hydrologically and hydraulically divided into
subareas called subwatersheds that are assigned a fourteen character
code. The accuracy of these maps is generally based on the contour
information or DEM data available for the base maps. Such data may be
supplemented with site visits to locate ridge lines for hydrologic unit
boundaries in flat terrain areas or changes in drainage patterns due to
man's activities. The differences in positional accuracy between the
hydrologic unit boundaries and their digitized map locations is unknown.
U.S. Geological Survey in cooperation with Ohio DNR1967Drainage Areas of Ohio Streams (Supplement to Gazetteer ofmap24000USGS 7 1/2 minute quadrangles (paper)1967publication dateGazetteer
Simple check of location and areas of Hydrologic
Units. Base maps containing watershed boundaries. Copied to mylar for digitization.
The following steps were done to develop the 14-digit subwatershed
hydrologic units:
a) 1 to 24,000 scale (7 1/2 minute topographic quadrangles) maps
were obtained from Ohio USGS District office. These contained
drainage boundary delineations done by their office over many
years for all Ohio quadrangles (about 800 quadrangles).
b) Using funds from Ohio DNR and Ohio EPA, the Ohio DNR, Real
Estate and Land Management Section (REALM) carried out the
digitization of the drainage boundaries. The ODNR funded the Lake
Erie portion of the digitizing which was done first. The Ohio EPA
funded the Ohio River drainage portion to complete the state
coverage. The process of translating the boundaries from hard copy
maps to digital files included copying the USGS quads onto stable
mylar copies, digitizing all boundaries on quads regardless of the
polygon size, and edge-matching the quads. Also, during this
process, ODNR assigned a 4-digit code to each polygon along with a
short narrative description of the area enclosed.
c) Through coordination of the various agencies (Ohio EPA, ODNR,
NRCS and USGS) a common hydrologic boundary layer was agreed upon.
This layer was the watersheds that Ohio EPA was using for their
Clean Water Act, Section 319 program. These watersheds were of the
appropriate size for NRCS's 11-digit watersheds (i.e. typically
from 40,000 to 250,000 acres.) Therefore, the original digitized
drainage boundaries were aggregated to develop the common 11-digit
watershed layer. The NRCS coordinated assignment of the 3-digit
extension of the USGS existing 8-digit codes to arrive at the
11-digit code. Coordination included working with the surrounding
states of West Virginia, Kentucky, Indiana, Michigan and
Pennsylvania, especially with the latter 3 states which further
along in following the new guidelines. Short narrative
descriptions were developed for each 11-digit watershed (331
watersheds.)
d) For the 14-digit subwatersheds, the NRCS guidelines called for
areas typically between 10,000 and 40,000 acres, with nothing
mapped smaller than 3,000 acres. The boundaries digitized off the
USGS quads were again aggregated within the previously developed
11-digit layer to give consistency to area size of the 14-digit
subwatersheds. Again, coordination was done across state lines to
arrive at drainage boundaries that ignored state boundaries and
that had a common 14-digit code. Original narrative descriptions
were modified to arrive at a narrative description for the
aggregated 14-digit subwatersheds (1756 subwatersheds in, or
partially in, Ohio.)
e) Subwatershed delination and the coding for watersheds and
subwatersheds were revisited for the 8-digit basins that straddled
the Ohio River. Previous coordination with West Virginia and
Kentucky had used the Ohio River as a boundary for 11 and 14-digit
areas. This situation was corrected through coordination with West
Virginia and allowance was made for Kentucky drainage patterns. At
this time, Kentucky has decided not to develop a layer that fits
in with the national guidelines but is sticking with its own
14-digit delineation.
Reviews Applied to Data. The ODNR REALM Division, which did the
digitizing, checked the digital files against the source
compilation of the boundaries. After aggregration of digitized
polygons as described above, checking of the 11 and 14-digit
watersheds occurred in the following ways:
1. Since the 11 and 14-digit watersheds were aggregated in two
different procedures, they were used to check each other. That is,
several errors were found when a 11-digit boundary did not
coincide with a 14-digit boundary.
2. Ohio EPA's Reach File 3 stream network was used as an
auxcillary layer against which to check the watershed boundaries.
The stream network was not perfect but discrepancies were a flag
to make further checks. Some errors were found and corrected.
3. 11 and 14-digit maps and digital files were exchanged with
Indiana, Michigan and Pennsylvania to develop and check
consistency of boundaries and codes across state lines.
4. Draft 14-digit maps were made for each Ohio county and sent to
the NRCS field offices for review. Corrections were made from
errors found by the field review.
5. Images of the county maps were placed on the Ohio NRCS web site
for others use and inspection.
6. The digital layer was sent to the Ohio District USGS office and
the Ohio EPA office for review.
Additions were made to the original digitization in order to
coordinate across state boundaries, fix errors, and meet acreage
guidelines of NRCS National Instruction 170-304. Additions made
are enumerated below:
1. Slab Lousy Run (on the Frendship and West Portsmouth
quadrangles in Scioto County) was corrected to show its whole
drainage area draining to the Ohio River rather than divided
between the Ohio and the Scioto River. It is wholly part of the
8-digit basin of 05090103 and no part of 05060002. Its 14-digit
code is 05090103040070.
2. In order to match 14-digit areas of Indiana, lines were added
to define boundaries for Howard Cr. and Sours Run (tribs. to Dry
Fork.) Areas are in Hamilton and Butler counties on the Harrison
and Shandon Quads. Digitized lines were added, partly from Indiana
District of USGS and partly from Ohio NRCS. Lines form part of
boundaries for subwatersheds -130, -140, -150 and -160 of the
11-digit watershed 05080003-080.
3. In order to match 14-digit areas of Indiana, a line was added
to separate headwater portions of Indian Creek (tributary to Great
Miami River) in Butler County. This line is on the College Corner
quadrangle and forms part of the boundary between 05080002-080-020
and 05080002-080-030.
4. In order to match 14-digit areas of Indiana, a line was added
to separate headwater portions of Middle Fork of East Fork
Whitewater River in Darke County. This line is on the Whitewater
quadrangle and forms part of the boundary between 05080003070030
and 05080003070040.
5. In order to match 14-digit areas of Indiana, lines were added
to define boundaries for Big Run and Buck Run. These creeks are
tributary to St. Joseph River near the northwest corner of
Defiance County, on the Butler East and Edgerton quadrangles.
Digitized lines were added, partly from Indiana District of USGS
and partly from Ohio NRCS. Lines form part of boundaries for
subwatersheds 020, 040, 050 and 070 of the 11-digit watershed
04100003060.
6. A line was added to separate Bear Creek headwaters from Little
Bear Creek to match subwatersheds with Michigan. (On Assumption
and Lyons quads in Fulton County.) Bear Creek headwaters is coded
04100002030050.
7. A line was added to show new boundary of Shantee Creek that has
been diverted upstream of its original outlet into Halfway Creek.
This area is in Lucas County and on the Toledo quadrangle. This
line forms part of the boundary between the 14-digit subwatersheds
of 04100001020110 and 0410001020120.
8. Drainage to Swan Creek (namely, 04100009080030) included land
crossing the Maumee River at Missionary Island (Lucas County,
Grand Rapids Quad.) A line was added to transfer this land to a
Maumee subwatershed, namely, 04100009060030.
9. Cedar Creek of Lucas County (Reno Beach quadrangle) outlets to
Lake Erie by way of Wards Canal and the Reno Side Cut. A new line
was digitized to include both outlet paths in the same 14-digit
area (i.e. 04100010010040).
10. Lacarpe Creek in Ottawa County has been diverted to the
Portage River per field review. A line was added on the Lindsey,
Elmore and Genoa quadrangles to subdivide the Lacarpe watershed.
This line forms part of the boundary to subwatershed
04100010-060-010.
11. In oder to match 14-digit areas of Pennsylvania,
Pennsylvania's digitizing of the boundary of Pymatuning Reservoir
(in Ashtabula County, on the Andover and Leon quadrangles) was
incorporated into the Ohio portion of the lake boundary. This line
forms part of the boundary between 05030102010280 and
05030102010300.
12. The original polygon digitization left a few very large areas
that were subdivided to obtain a more typical size for the
14-digit subwatersheds. These areas are described as follows:
12a. In the headwaters of the Mahoning River in Columbiana County
a line was added to subdivide the large area. This line is on the
Alliance, Damascus and Homeworth quadrangles and separates the
subwatersheds 05030103010010 and 05030103010020.
12b. Leatherwood Creek, tributary of Wills Creek in Guernsey
County, was subdivided by an added line on the Quaker City and
Antrim quadrangles. This line separates 05040005030010 and
05040005030020.
12c. The "boot" area of Meigs County was subdivided into 4
subwatersheds. The lines added are on the New Haven, Portland and
Ravenswood quadrangles and form part of the boundaries for
subwatersheds 010, 030, 040, and 050 of the 11-digit watershed
05030202050. 12d. The Wabash River watershed above Beaver Creek in
Darke and Mercer Counties was subdivided into 3 subwatersheds. The
lines added are on the Coldwater, Cosmos, Fort Recovery,
Montezuma, North Star and Rossburg quadrangles and form part of
the boundaries for subwatersheds 010, 020, 030 of the 11-digit
watershed 05120101010.
13. In order to match West Virginia across the Ohio River, a line
was added across from Graves Cr.(West Virginia.) This line is on
the Businessburg quad and separates 05030106110010 and
05030106110040.
14. In order to match West Virginia across the Ohio River, a line
was added across from Fishing Cr.(West Virginia.) This line is on
the Round Bottom and New Martinsville quads and separates
05030201020010 and 05030201020040.
15. In order to match West Virginia across the Ohio River, a line
was added across from Middle Island Cr.(West Virginia.) This line
is on the Raven Rock quad and separates 05030201020050 and
05030201020060.
16. In order to match West Virginia across the Ohio River, a line
was added across from Bull Creek (West Virginia.) This line is on
the Willow Island quad and separates 05030201020060 and
05030201020090.
17. In order to match West Virginia across the Ohio River, a line
was added across from Little Kanawha R. (West Virginia.) This line
is on the Parkersburg quad and separates 05030202010010 and
05030202010030.
18. In order to make a common boundary with Kentucky across the
Ohio River, a line was added across from the Little Sandy River
(Kentucky.) This line is on the Greenup quad and separates
05090103010060 and 05090103010100.
19. In order to tie in the 8-digit boundary between 05090103 and
05090201 at the Ohio/Kentucky border, a line was added to the
Friendship quad.
20. In order to make a common boundary with Kentucky across the
Ohio River, a line was added across from the Kinniconick Creek
(Kentucky.) This line is on the Garrison and Pond Run quads and
separates 05090201010010 and 05090201010070.
21. In order to make a common boundary with Kentucky across the
Ohio River, a line was added across from Salt Lick Creek
(Kentucky.) This line is on the Buena Vista and Vanceburg quads
and separates 05090201010070 and 05090201010150.
22. In order to make a common boundary with Kentucky across the
Ohio River, a line was added across from Cabin Creek (Kentucky.)
This line is on the Maysville East quad and separates
05090201060010 and 05090201060110.
withheld1997-1999withheldDataset copied.withheldMetadata imported.withheld20041210VectorSimpleFALSE1756TRUEFALSEcoordinate pair0.0005120.000512survey feetNorth American Datum of 1983Geodetic Reference System 806378137.000000298.257222GCS_North_American_1983NAD_1983_StatePlane_Ohio_South_FIPS_3402_Feet0.000122Explicit elevation coordinate included with horizontal coordinatesOEPA_ohio_huc14Feature Class1756HUC_1111 digit Hydrologic Unit CodeHUC_11String25400ShapeFeature geometry.ESRICoordinates defining the features.ACRESDouble800ACRESNARRATIVEString25400NARRATIVEHUC_14String25400HUC_14STATESString25400STATESCOUNTPOLYGDouble800COUNTPOLYGHUC_8String25400HUC_8ShapeGeometry000Feature geometry.EsriCoordinates defining the features.SHAPEFeature geometry.ESRICoordinates defining the features.OBJECTIDOID400OBJECTIDInternal feature number.ESRISequential unique whole numbers that are automatically generated.Shape_LengthDouble800SHAPE_LengthShape_AreaDouble800Length of feature in internal units.ESRIPositive real numbers that are automatically generated.SHAPE_AreaSHAPE_AreaDouble800Area of feature in internal units squared.ESRIPositive real numbers that are automatically generated.
Hydrologic Unit delineations are closed polygons that encompass all
area draining toward the lowest point (called the outlet) in the
polygon. Because of nominal sizes for the different hydrologic unit
levels, Watershed (40,000 to 250,000 acres) and Subwatershed
(generally 10,000 to 40,000 acres with nothing smaller that 3,000
acres), some polygons do not include all areas up to the drainage
divide but all areas to one or more other upstream hydrologic units. A
unique hydrologic unit code is used to identify each hydrologic unit.
The watershed hydrologic unit codes start with the 8-digit subbasin
(Cataloging Unit) number that contains the watershed. Likewise the
subwatershed hydrologic unit codes start with the 11-digit watershed
number that contains the subwatershed. Attributes associated with a
hydrologic unit code may include, in the future, where appropriate:
non-contributing area (acres); type of non-contributing area (number
of areas, scatter throughout); trans-basin areas inflowing to
hydrologic unit; trans basin area (acres); trans basin area
originating hydrologic unit code; and notes concerning delineation of
hydrologic unit boundary.
U.S.D.A. Natural Resources Conservation Servicemailing address
200 N. High Street, Room 522
ColumbusOH43215USA(614) 255-2466jim.stafford@oh.nrcs.usda.govPlease use email.Downloadable Data
Although these data have been processed successfully on a computer
system at the U.S. Department of Agriculture, no warranty expressed or
implied is made by the agency regarding the utility of the data on any
other system, nor shall the act of distribution constitute any such
warranty.
SHPNo compression applied18.626http://www.ftw.nrcs.usda.gov/nsdi_node.htmlLocal area network20070907U.S.D.A. Natural Resources Conservation ServiceThe person responsible for the metadata information. REQUIRED.State Hydraulic Engineer, State GIS Specalistmailing address
200 N. High Street, Room 522
ColumbusOH43215USAThe telephone number by which individuals can speak to the organization or individual. REQUIRED.FGDC Content Standards for Digital Geospatial MetadataFGDC-STD-001-1998local timehttp://www.esri.com/metadata/esriprof80.htmlESRI Metadata Profilehttp://www.esri.com/metadata/esriprof80.htmlESRI Metadata Profileen{C13CC2BE-E981-4A45-861A-324C0E1EA23F}2004121014034600FALSE20190628114225002019062811422500OEPA_ohio_huc140021310232.6378032518339.431888146857.9347771455206.0120271ProjectedGCS_North_American_1983Linear Unit: Foot_US (0.304801)NAD_1983_StatePlane_Ohio_South_FIPS_3402_Feet<ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/10.7'><WKT>PROJCS["NAD_1983_StatePlane_Ohio_South_FIPS_3402_Feet",GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Lambert_Conformal_Conic"],PARAMETER["False_Easting",1968500.0],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-82.5],PARAMETER["Standard_Parallel_1",38.73333333333333],PARAMETER["Standard_Parallel_2",40.03333333333333],PARAMETER["Latitude_Of_Origin",38.0],UNIT["Foot_US",0.3048006096012192],AUTHORITY["EPSG",3735]]</WKT><XOrigin>-119670699.99890123</XOrigin><YOrigin>-95612899.998886466</YOrigin><XYScale>1953.1249981810081</XYScale><ZOrigin>-100000</ZOrigin><ZScale>10000</ZScale><MOrigin>-100000</MOrigin><MScale>10000</MScale><XYTolerance>0.0040960000038147027</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>102723</WKID><LatestWKID>3735</LatestWKID></ProjectedCoordinateSystem> Version 6.2 (Build 9200) ; Esri ArcGIS 10.7.0.10450OEPA_ohio_huc141310232.6378032518339.4318881455206.012027146857.9347771-84.918519-80.47970741.99389238.38022211-84.918519-80.47970741.99389238.380222ISO 19115 Geographic Information - MetadataDIS_ESRI1.0dataset002withheldLocal Area NetworkFile Geodatabase Feature ClassFile Geodatabase Feature ClassNAD_1983_StatePlane_Ohio_South_FIPS_3402_FeetEPSG6.13(9.3.0.0)175620190628