<?xml version="1.0" encoding="ISO-8859-1"?>
<metadata>
	<idinfo>
		<citation>
			<citeinfo>
				<origin>(creation): US Geological Survey and the US Environmental Protection Agency</origin>
				<origin>(compilation): Bernardin, Lochmueller and Associates</origin>
				<pubdate>20021200</pubdate>
				<title Sync="TRUE">lakes_clip</title>
				<edition>National Hydography Dataset, 2002</edition>
				<geoform Sync="TRUE">vector digital data</geoform>
				<pubinfo>
					<pubplace>Evansville, IN</pubplace>
					<publish>Bernardin, Lochmueller and Associates</publish>
				</pubinfo>
				<othercit>
This dataset is derived from
the National Hydrography Dataset created by the US Geological
Survey and the US Environmental Protection Agency;
&lt;http://nhd.usgs.gov/&gt;  Dataset is one layer in the Indiana
Statewide GIS Database funded by Indiana Department of Transportation.
</othercit>
				<ftname Sync="TRUE">lakes_clip</ftname><onlink Sync="TRUE">\\dnrfile1\DOW\TS\Water_Resources_and_Rights\future_mxds\clark\lakes_clip</onlink></citeinfo>
		</citation>
		<descript>
			<abstract>HydrographyPoly_NHD_BLA is a polygon shapefile that contains features
of lakes, ponds, rivers, large streams, and swamps or marshes in Indiana.
This layer is derived from the National Hydrography Dataset.
This layer is intended for use with its companion layers of Hydrography
points and Hydrography Lines.
National Hydrography Dataset metadata, USGS, states -

"The National Hydrography Dataset (NHD) is a feature-based
database that interconnects and uniquely identifies the
stream segments or reaches that comprise the nations
surface water drainage system. It is based initially on the
content of the U.S. Geological Survey 1:100,000-scale
Digital Line Graph (DLG) hydrography data, integrated with
reach-related information from the U.S. Environmental
Protection Agency Reach File Version 3.0 (RF3). More
specifically, it contains reach codes for networked
features and isolated lakes, flow direction, names, stream
level, and centerline representations for aerial water
bodies. The NHD also incorporates the National Spatial
Data Infrastructure framework criteria set out by the
Federal Geographic Data Committee."</abstract>
			<purpose>
Broad, general information for planning, development, and research
in Indiana.
National Hydrography Dataset metadata, USGS, states -

"The National Hydrography Dataset combines elements of the
DLG and RF3: spatial accuracy and comprehensiveness from
the DLG and network relationships, names, stream level, and
a unique identifier (reach code) for surface water features
from RF3. The NHD supersedes DLG and RF3 by incorporating
them, not by replacing them. Users of DLG and RF3 will find
the National Hydrography Dataset both familiar and greatly
expanded and refined. The NHD provides a national framework
for assigning reach addresses to water-related entities,
such as industrial dischargers, drinking water supplies,
fish habitat areas, wild and scenic rivers. Reach addresses
establish the locations of these entities relative to one
another within the NHD surface water drainage network in
a manner similar to street addresses. Once linked to the
NHD by their reach addresses, the upstream/downstream
relationships of these water-related entities and any
associated information about them can be analyzed using
software tools ranging from spreadsheets to geographic
information systems (GIS). GIS can also be used to combine
NHD-based network analysis with other data layers, such as
soils, land use and population, to help better understand
and display their respective effects upon one another.
Furthermore, because the NHD provides a nationally
consistent framework for addressing and analysis,
water-related information linked to reach addresses by one
organization(national, state, local) can be shared with
other organizations and easily integrated into many
different types of applications to the benefit of all. The
National Hydrography Dataset is designed to provide
comprehensive coverage of hydrologic data for the U.S.
While initially based on 1:100,000-scale data, the NHD is
designed to incorporate - and encourage the development of
- higher-resolution data required by many users. It will
facilitate the improved integration of water-related data
in support of the application requirements of a growing
national user community and will enable shared maintenance and enhancement."
</purpose>
			<supplinf>
Data is derived from the National Hydrography Dataset
(USGS, EPA). Metadata for unique 8-digit cataloging unit hydrography as well as
documents for standards and creation procedures can be found at the NHD website
&lt;http://nhd.usgs.gov/&gt;.
</supplinf>
			<langdata Sync="TRUE">en</langdata></descript>
		<timeperd>
			<timeinfo>
				<sngdate>
					<caldate>20010101</caldate>
				</sngdate>
			</timeinfo>
			<current>NHD Publication Date</current>
		</timeperd>
		<status>
			<progress>Complete</progress>
			<update>As needed</update>
		</status>
		<spdom>
			<bounding>
				<westbc Sync="TRUE">-88.163330</westbc>
				<eastbc Sync="TRUE">-84.682100</eastbc>
				<northbc Sync="TRUE">41.781024</northbc>
				<southbc Sync="TRUE">37.744099</southbc>
			</bounding>
			<lboundng><leftbc Sync="TRUE">403316.601450</leftbc><rightbc Sync="TRUE">692695.700017</rightbc><bottombc Sync="TRUE">4179674.832894</bottombc><topbc Sync="TRUE">4625464.504569</topbc></lboundng></spdom>
		<keywords>
			<theme>
				<themekt>None</themekt>
				<themekey>Hydrography</themekey>
				<themekey>Lake</themekey>
				<themekey>Pond</themekey>
				<themekey>Reservoir</themekey>
				<themekey>Stream</themekey>
				<themekey>River</themekey>
				<themekey>Inundation Area</themekey>
				<themekey>Flooded Area</themekey>
				<themekey>Swamp</themekey>
				<themekey>Marsh</themekey>
				<themekey>Hydrology</themekey>
				<themekey>National Hydrography Dataset</themekey>
				<themekey>Waterbody</themekey>
			</theme>
			<place>
				<placekt>None</placekt>
				<placekey>Indiana</placekey>
				<placekey>Adams County</placekey>
				<placekey>Allen County</placekey>
				<placekey>Bartholomew County</placekey>
				<placekey>Benton County</placekey>
				<placekey>Blackford County</placekey>
				<placekey>Boone County</placekey>
				<placekey>Brown County</placekey>
				<placekey>Carroll County</placekey>
				<placekey>Cass County</placekey>
				<placekey>Clark County</placekey>
				<placekey>Clay County</placekey>
				<placekey>Clinton County</placekey>
				<placekey>Crawford County</placekey>
				<placekey>Daviess County</placekey>
				<placekey>Dearborn County</placekey>
				<placekey>Decatur County</placekey>
				<placekey>DeKalb County</placekey>
				<placekey>Delaware County</placekey>
				<placekey>Dubois County</placekey>
				<placekey>Elkhart County</placekey>
				<placekey>Fayette County</placekey>
				<placekey>Floyd County</placekey>
				<placekey>Fountain County</placekey>
				<placekey>Franklin County</placekey>
				<placekey>Fulton County</placekey>
				<placekey>Gibson County</placekey>
				<placekey>Grant County</placekey>
				<placekey>Greene County</placekey>
				<placekey>Hamilton County</placekey>
				<placekey>Hancock County</placekey>
				<placekey>Harrison County</placekey>
				<placekey>Hendricks County</placekey>
				<placekey>Henry County</placekey>
				<placekey>Howard County</placekey>
				<placekey>Huntington County</placekey>
				<placekey>Jackson County</placekey>
				<placekey>Jasper County</placekey>
				<placekey>Jay County</placekey>
				<placekey>Jefferson County</placekey>
				<placekey>Jennings County</placekey>
				<placekey>Johnson County</placekey>
				<placekey>Knox County</placekey>
				<placekey>Kosciusko County</placekey>
				<placekey>Lagrange County</placekey>
				<placekey>Lake County</placekey>
				<placekey>LaPorte County</placekey>
				<placekey>Lawrence County</placekey>
				<placekey>Madison County</placekey>
				<placekey>Marion County</placekey>
				<placekey>Marshall County</placekey>
				<placekey>Martin County</placekey>
				<placekey>Miami County</placekey>
				<placekey>Monroe County</placekey>
				<placekey>Montgomery County</placekey>
				<placekey>Morgan County</placekey>
				<placekey>Newton County</placekey>
				<placekey>Noble County</placekey>
				<placekey>Ohio County</placekey>
				<placekey>Orange County</placekey>
				<placekey>Owen County</placekey>
				<placekey>Parke County</placekey>
				<placekey>Perry County</placekey>
				<placekey>Pike County</placekey>
				<placekey>Porter County</placekey>
				<placekey>Posey County</placekey>
				<placekey>Pulaski County</placekey>
				<placekey>Putnam County</placekey>
				<placekey>Randolph County</placekey>
				<placekey>Ripley County</placekey>
				<placekey>Rush County</placekey>
				<placekey>Scott County</placekey>
				<placekey>Shelby County</placekey>
				<placekey>Spencer County</placekey>
				<placekey>Starke County</placekey>
				<placekey>Steuben County</placekey>
				<placekey>St Joseph County</placekey>
				<placekey>Sullivan County</placekey>
				<placekey>Switzerland County</placekey>
				<placekey>Tippecanoe County</placekey>
				<placekey>Tipton County</placekey>
				<placekey>Union County</placekey>
				<placekey>Vanderburgh County</placekey>
				<placekey>Vermillion County</placekey>
				<placekey>Vigo County</placekey>
				<placekey>Wabash County</placekey>
				<placekey>Warren County</placekey>
				<placekey>Warrick County</placekey>
				<placekey>Washington County</placekey>
				<placekey>Wayne County</placekey>
				<placekey>Wells County</placekey>
				<placekey>White County</placekey>
				<placekey>Whitley County</placekey>
			</place>
		</keywords>
		<accconst>None</accconst>
		<useconst>
DATA DISCLAIMER
This data set was compiled by Bernardin, Lochmueller and Associates,
using data believed to be accurate; however, a degree of error
is inherent in all data. This product is distributed "AS-IS" without
warranties of any kind, either expressed or implied, including but not
limited to warranties of suitability of a particular purpose or use. No
attempt has been made in either the designed format or production of these data to
define the limits or jurisdiction of any federal, state, or local government.
These data are intended for use only at the published scale or smaller and are for
reference purposes only. They are not to be construed as a legal document or survey
instrument. A detailed on-the-ground survey and historical analysis of a single
site may differ from this data.
CREDIT
Acknowledgment of the USGS and USEPA would be
appreciated in products derived from these data.
</useconst>
		<ptcontac>
			<cntinfo>
				<cntorgp>
					<cntorg>Bernardin, Lochmueller and Associates</cntorg>
					<cntper>Neal Schroeder</cntper>
				</cntorgp>
				<cntpos>Geographer, Environmental Planner</cntpos>
				<cntaddr>
					<addrtype>mailing and physical address</addrtype>
					<address>6200 Vogel Road</address>
					<city>Evansville</city>
					<state>IN</state>
					<postal>47715-4006</postal>
					<country>USA</country>
				</cntaddr>
				<cntvoice>800-423-7411</cntvoice>
				<cntfax>812-479-6262</cntfax>
				<cntemail>nschroeder@blainc.com</cntemail>
				<hours>8am-5pm CST</hours>
			</cntinfo>
		</ptcontac>
		<datacred>
Indiana Statewide GIS database was produced under an Indiana Department of
Transportation contract. Data is derived from the USGS/USEPA National Hydrography
Dataset.
US Geological Survey requests -

" Acknowledgment of the USGS and USEPA would be
appreciated in products derived from these data."
</datacred>
		<native Sync="TRUE">Microsoft Windows 2000 Version 5.0 (Build 2195) Service Pack 4; ESRI ArcCatalog 9.0.0.535</native>
		<natvform Sync="TRUE">Shapefile</natvform></idinfo>
	<dataqual>
		<attracc>
			<attraccr>
National Hydrography Dataset metadata, USGS, reports -

"The accuracy of the attributes of the Digital Line Graph
data is estimated to be 98.5 percent. One or more of the
following methods were used to test attribute accuracy: -
manual comparison of the source with hardcopy plots. -
symbolized display of the digital line graph on an
interactive computer graphic system. - Selected attributes
that could not be visually verified on plots or on screen
were interactively queried and verified on screen. In
addition, software validated feature types and
characteristics against a master set of types and
characteristics, checked that combinations of types and
characteristics were valid, and that types and
characteristics were valid for the delineation of the
feature. Feature types, characteristics, and other
attributes conform to the Standards for National
Hydrography Dataset (USGS, 1999) as of the date they were
loaded into the database. All names on reaches were
validated against a
March 1999 extract from the Geographic Names Information
System. The entry and identifier for the names match those
in the Geographic Names Information System. The association
of each name to reaches has not been methodically checked,
and so a name may be applied to the wrong reaches.
Anecdotal reviews indicate that 80 percent or more of the
named reaches have the correct name. Reaches were
delineated with a batch procedure and were checked
extensively during the visual pass steps of processing.
Based on automated quality assurance/quality control checks
performed at various intervals during the processing,
approximately 99 percent of the reaches are delineated
according to standards."
</attraccr>
		</attracc>
		<logic>
National Hydrography Dataset metadata, USGS, reports -

"Areas conform to topological rules. Gaps and overlaps among
areas do not exist. All areas close."
</logic>
		<complete>
National Hydrography Dataset metadata, USGS, reports -

"The completeness of the data reflects the content of the
sources, which, in the initial release of the National
Hydrography Dataset, most often are U.S. Geological Survey
topographic maps. Features found on the ground may have
been eliminated or generalized on the source graphic
because of scale and legibility constraints. In general,
streams longer than one mile (approximately 1.6 kilometers)
were collected. Most streams that flow from a lake were
collected regardless of their length. Only definite
channels were collected so not all swamp/marsh features
have stream/rivers delineated through them. Lake/ponds
having an area greater than 6 acres (approximately 2.4
hectares) were collected. Note, however, that these general
rules were applied unevenly among maps during compilation.
Some map quadrangles have a much sparser pattern of
hydrography than do adjoining maps and these differences
continue in the digital rendition of these
features. A priority for maintenance of the National
Hydrography Dataset is the rectification of these
differences. Transport reaches are defined on nearly all
features of type stream/river, canal/ditch, artificial
path, pipeline, and connector. Most attention in applying geographic
names was given to transport reaches that follow
stream/rivers and waterbody reaches. Detailed capture
conditions are provided for every feature type in the
Standards for National Hydrography Dataset (USGS, 1999),
available online through http://mapping.usgs.gov/standards/."
</complete>
		<posacc>
			<horizpa>
				<horizpar>
National Hydrography Dataset metadata, USGS, reports -

"Statements of horizontal positional accuracy are based on
accuracy statements made for U.S. Geological Survey
topographic quadrangle maps. These maps were compiled to
meet National Map Accuracy Standards. For horizontal
accuracy, this standard is met if at least 90 percent of
points tested are within 0.02 inch (at map scale) of their
true position. Additional offsets to positions may have
been introduced where there are many features to improve
the legibility of map symbols. In addition, the digitizing
of maps is estimated to contain a horizontal positional
error of less than or equal to 0.003 inch standard error
(at map scale) in the two component directions relative to
the source maps. Visual comparison between the map graphic
(including digital scans of the graphic), and plots or
digital displays of points, lines, and areas, is used to
assess the positional accuracy of digital data. Linear
features of the same type along the adjoining edges of data
sets are aligned if they are within a 0.02 inch tolerance
(at map scale). To align the features, the midpoint between
the end of the corresponding features is computed, and the
ends of features are moved to this point. Features outside
the tolerance are not moved; instead, a feature of type
connector was added to join the features."
</horizpar>
			</horizpa>
			<vertacc>
				<vertaccr>
National Hydrography Dataset metadata, USGS, reports -

"Statements of vertical positional accuracy for elevation of water surfaces are
based on accuracy statements made for U.S. Geological Survey topographic
quadrangle maps. These maps were compiled to meet National Map Accuracy
Standards. For vertical accuracy, this standard is met if at least 90 percent
of well-defined points tested are within one-half contour interval of the
correct value. Elevations of water surface printed on the published map meet
this standard; the contour intervals of the maps vary. These elevations were
transcribed into the digital data; the accuracy of this transcription was
checked by visual comparison between the data and the map."
</vertaccr>
			</vertacc>
		</posacc>
		<lineage>
			<srcinfo>
				<srccite>
					<citeinfo>
						<origin>
U.S. Geological Survey in cooperation with U.S.
Environmental Protection Agency(creator)
Bernardin-Lochmueller &amp; Associates (compiler)
</origin>
						<pubdate>20010101</pubdate>
						<title>National Hydrography Dataset</title>
						<geoform>vector data</geoform>
						<pubinfo>
							<pubplace>Reston, VA</pubplace>
							<publish>U.S. Geological Survey</publish>
						</pubinfo>
						<onlink>http://nhd.usgs.gov/index.html</onlink>
					</citeinfo>
				</srccite>
				<srcscale>100000</srcscale>
				<typesrc>ESRI ArcInfo coverage</typesrc>
				<srctime>
					<timeinfo>
						<sngdate>
							<caldate>20010101</caldate>
						</sngdate>
					</timeinfo>
					<srccurr>NHD Publication Date</srccurr>
				</srctime>
				<srccitea>NHD</srccitea>
				<srccontr>Digital features and attributes</srccontr>
			</srcinfo>
			<procstep>
				<procdesc>
National Hydrography Dataset metadata, USGS, reports -

"Flow validation performed after initial release of data:
1.Convert RF3 to RF3 double prime. This batch operation
processed Reach File version 3 to delete duplicate reaches,
reassign reaches to the correct cataloging unit, validate geographic
names assigned to reaches against data from the Geographic
Names Information System (December 1996
extract), apply updates supplied by the States of
California and Arizona, redelineate reaches based on the
standards used for the National Hydrography Dataset, and
identify inflow/outflow points where transport reaches
entered and exited waterbodies.
2. Create artificial paths. Using waterbodies from the
features data and inflow/outflow points extracted from RF3
double prime, this process automatically generated the
lines used to delineate artificial paths within waterbodies
using the ESRI ARC/INFO GRID routine.
3. Blind pass. This batch step conflated RF3 double prime
reaches, and transferred reach information (reach code,
reach date, name, stream level, and flow relationships), to
the features. It also integrated the artificial
paths	generated in the previous step with the other
features, built reaches on the	artificial paths, and
assigned geographic names to waterbodies (February 1995
extract).
4. Quadrangle-based visual pass. During this interactive step,
analysts ensured that the data developed in the previous
batch processes conformed to reach delineation rules and
that reaches were assigned to the appropriate cataloging
unit. Batch procedures identified and developed a list	of
possible errors. Using the list, software presented each
case to analysts to make appropriate edits to the data.
Analysts recorded notes where repairs could not be made;
these notes are encoded in the cataloging unit digital
update units under a separate process description.
5. Build superquads. After the quadrangle-based visual pass
was complete, all quadrangles that cover all or part of
each cataloging unit using were paneled into a superquad.
In this batch process, reaches that cross quad boundaries
were corrected to conform to reach delineation rules.
6. Cataloging unit-based visual pass. Like the
quadrangle-based visual pass, analysts ensured that reaches
conformed to reach delineation rules. Batch procedures
identified and developed a list of possible errors. (Errors
not detected by the software may continue in the data.)
Analysts examined each error, and corrected the data.
Analysts recorded notes about repairs that could not be
made, and other errors in the data; these notes are encoded
in the cataloging unit digital update units under a
separate process description.
7. Central quality assurance/quality control. This step (1)
confirmed that integrity checks were performed successfully
during the visual pass activity, and (2) assessed
statistics gathered during the earlier processes to
determine if additional review was needed. A check of data
from the cataloging unit-based visual pass was run in
batch; any data that did not pass the procedure were
reviewed interactively. If substantive changes were
required, the data were reprocessed using procedures (as
required) described in previous steps. The edited data then
were rechecked using the central quality assurance/quality
control process.
8. Data preparation and database load. This batch procedure
performed final processing to the data emerging from the
quality assurance/quality control step. Some of the
activities include assigning the final reach codes,
building waterbody reaches, adding final artificial paths
in waterbodies, and implementing any recent changes in
standards for the National Hydrography Dataset. The
spelling of geographic names were replaced from the March
1999, data extract from the Geographic Names Information
System. Following this procedure, reaches, features,
characteristics, geographic names, and relations were
loaded into the database that holds the National
Hydrography Dataset.
9. Flow relation correction and validation. The flow relations
were checked for consistency through a batch procedure,
which generated a list of possible errors. Software
presented possible errors to analysts, who corrected flow
relations and, occasionally, the delineation of reaches.
Changes were posted to the database.
10. Extract distribution copies of data. Data for a cataloging
unit were extracted from the database, and converted into
an ESRI ARC/INFO workspace containing coverages and other files
related to the National Hydrography Dataset. Data available
in the 	Spatial Data Transfer Standard format were
developed from the workspaces. The workspaces, and the
Spatial Data Transfer Standard-formatted files, were made
available to the public.
This process converted Digital Line Graph (DLG-3) data to
the features and converted the coordinate system to geographic
(longitude-latitude) coordinates in the North
American Datum of 1983, in five steps:
1. The U.S. Geological Surveys Batch DLG-3 to DLG-F
Conversion System converted DLG-3 nodes, lines, areas, and
associated attribute codes to temporary features and
associated characteristics. Known conversion problems or
uncertain conversions (for example, the DLG-3 attribute
code for reservoir sometimes should convert to the feature
type Reservoir and other times to feature type Lake/Pond)
were flagged for later inspection. Only known conversion
problems were flagged and no additional steps to detect or
repair discrepancies in the original DLG-3 or the converted
NHD were taken.
2. A default value of a characteristic was added in cases
where the description was incomplete.
3. All instances in which problems and uncertainties were
flagged were inspected and resolved interactively.
4. Feature delineation rules were applied to the temporary
features in a batch process to create the final version of
features.
5. Coordinate values were converted to geographic
coordinates, the North American Datum of 1983, using
version 2.1 of NADCON software (National Geodetic Survey,
n.d.).This process generated the features data."
</procdesc>
				<srcused>USGS 100K DLG; EPA Rf3</srcused>
				<procdate>20010101</procdate>
				<srcprod>NHD</srcprod>
				<proccont>
					<cntinfo>
						<cntperp>
							<cntper>Unknown</cntper>
							<cntorg>U.S. Geological Survey</cntorg>
						</cntperp>
						<cntaddr>
							<addrtype>mailing and physical address</addrtype>
							<address>509 National Center</address>
							<city>Reston</city>
							<state>Virginia</state>
							<postal>20192</postal>
							<country>USA</country>
						</cntaddr>
						<cntvoice>
703-648-4544
Contact_Electronic _Mail_Address: nhd@usgs.gov
</cntvoice>
						<hours>0730-1700</hours>
					</cntinfo>
				</proccont>
			</procstep>
			<procstep>
				<procdesc>
Region.wb files, region.rch files and region.lm files for
each 8-digit HUCs in Indiana were merged (union) to create
single region.rch, region.wb and region.lm file for the
entire state. Files were cut to the IGS Indiana clip boundary
with the exception of rivers and streams on the state border.
Names from region.rch were applied to the features
of region.wb by a script (data overlay) which transferred
attributes between shapefiles. Features of region.lm were
then unioned. The resulting file was then transformed from geographic
to UTM 16, NAD83. Feature overlaps were identified
and addressed so that no known overlaps exist in the data.
</procdesc>
				<srcused>NHD</srcused>
				<procdate>20021201</procdate>
				<srcprod>HYDROGRAPHY_POLY_NHD_IN</srcprod>
				<proccont>
					<cntinfo>
						<cntperp>
							<cntper>Cinda Bonds</cntper>
							<cntorg>Bernardin, Lochmueller and Associates</cntorg>
						</cntperp>
						<cntpos>Environmental Biologist</cntpos>
						<cntaddr>
							<addrtype>mailing and physical address</addrtype>
							<address>6200 Vogel Road</address>
							<city>Evansville</city>
							<state>IN</state>
							<postal>47715</postal>
							<country>USA</country>
						</cntaddr>
						<cntvoice>812-479-6200</cntvoice>
						<cntfax>
812-479-6262
Contact_Website:  www.blainc.com
</cntfax>
						<hours>0800-1700 CST</hours>
					</cntinfo>
				</proccont>
			</procstep>
			<procstep>
				<procdesc>
This metadata was pre-parsed and parsed using CNS (Chew and Spit. v 2.6.1) and
MP (Metadata Parser, v 2.7.1) software written by Peter N. Schweitzer (United
States Geological Survey).  The errors generated by MP were all
addressed and corrected, except that no values were assigned to
"Abscissa_Resolution" and "Ordinate_Resolution."
</procdesc>
				<procdate>20030513</procdate>
				<proccont>
					<cntinfo>
						<cntperp>
							<cntper>Neal Schroeder</cntper>
							<cntorg>Bernardin, Lochmueller and Associates</cntorg>
						</cntperp>
						<cntpos>Geographer, Environmental Planner</cntpos>
						<cntaddr>
							<addrtype>mailing and physical address</addrtype>
							<address>6200 Vogel Road</address>
							<city>Evansville</city>
							<state>IN</state>
							<postal>47715-4006</postal>
							<country>USA</country>
						</cntaddr>
						<cntvoice>800-423-7411</cntvoice>
						<cntfax>812-479-6262</cntfax>
						<cntemail>nschroeder@blainc.com</cntemail>
						<hours>8am-5pm CST</hours>
					</cntinfo>
				</proccont>
			</procstep>
			<procstep><procdesc>Downloaded from Indiana Geologic Survey's Indiana Atlas website, renamed, metadata edited.</procdesc><srcused>HYDROGRAPHY_POLY_NHD_IN</srcused><date Sync="TRUE">20030728</date><time Sync="TRUE">14183000</time><srcprod>HydrographyPoly_NHD_BLA</srcprod><proccont><cntinfo><cntorgp><cntorg>Indiana Department of Natural Resources</cntorg><cntper>Mike Martin</cntper></cntorgp><cntpos>GIS Coordinator</cntpos><cntvoice>317-232-4068</cntvoice><cntfax>317-233-4648</cntfax><cntemail>mmartin@dnr.state.in.us</cntemail></cntinfo></proccont></procstep><procstep><procdesc Sync="TRUE">Dataset copied.</procdesc><srcused Sync="TRUE">C:\future_clips\Clark\lakes_clip</srcused><date Sync="TRUE">20040615</date><time Sync="TRUE">15262800</time></procstep></lineage>
	</dataqual>
	<spdoinfo>
		<indspref>Indiana</indspref>
		<direct Sync="TRUE">Vector</direct>
		<ptvctinf>
			<sdtsterm Name="lakes_clip">
				<sdtstype Sync="TRUE">G-polygon</sdtstype>
				<ptvctcnt Sync="TRUE">0</ptvctcnt>
			</sdtsterm>
			<esriterm Name="lakes_clip"><efeatyp Sync="TRUE">Simple</efeatyp><efeageom Sync="TRUE">Polygon</efeageom><esritopo Sync="TRUE">FALSE</esritopo><efeacnt Sync="TRUE">0</efeacnt><spindex Sync="TRUE">FALSE</spindex><linrefer Sync="TRUE">FALSE</linrefer></esriterm></ptvctinf>
	</spdoinfo>
	<spref>
		<horizsys>
			<planar>
				<planci>
					<plance Sync="TRUE">coordinate pair</plance>
					<coordrep>
						<absres Sync="TRUE">0.000218</absres>
						<ordres Sync="TRUE">0.000218</ordres>
					</coordrep>
					<plandu Sync="TRUE">meters</plandu>
				</planci>
				<gridsys><gridsysn Sync="TRUE">Universal Transverse Mercator</gridsysn><utm><utmzone Sync="TRUE">16</utmzone><transmer><sfctrmer Sync="TRUE">0.999600</sfctrmer><longcm Sync="TRUE">-87.000000</longcm><latprjo Sync="TRUE">0.000000</latprjo><feast Sync="TRUE">500000.000000</feast><fnorth Sync="TRUE">0.000000</fnorth></transmer></utm></gridsys></planar>
			<geodetic>
				<horizdn Sync="TRUE">North American Datum of 1983</horizdn>
				<ellips Sync="TRUE">Geodetic Reference System 80</ellips>
				<semiaxis Sync="TRUE">6378137.000000</semiaxis>
				<denflat Sync="TRUE">298.257222</denflat>
			</geodetic>
			<cordsysn><geogcsn Sync="TRUE">GCS_North_American_1983</geogcsn><projcsn Sync="TRUE">NAD_1983_UTM_Zone_16N</projcsn></cordsysn></horizsys>
	</spref>
	<eainfo>
		<detailed Name="lakes_clip">
			<enttyp>
				<enttypl Sync="TRUE">lakes_clip</enttypl>
				<enttypd>Shapefile Attribute Table</enttypd>
				<enttypds>None</enttypds>
				<enttypt Sync="TRUE">Feature Class</enttypt><enttypc Sync="TRUE">0</enttypc></enttyp>
			<attr>
				<attrlabl Sync="TRUE">FID</attrlabl>
				<attrdef Sync="TRUE">Internal feature number.</attrdef>
				<attrdefs Sync="TRUE">ESRI</attrdefs>
				<attrdomv>
					<udom Sync="TRUE">Sequential unique whole numbers that are automatically generated.</udom>
				</attrdomv>
				<attalias Sync="TRUE">FID</attalias><attrtype Sync="TRUE">OID</attrtype><attwidth Sync="TRUE">4</attwidth><atprecis Sync="TRUE">0</atprecis><attscale Sync="TRUE">0</attscale></attr>
			<attr>
				<attrlabl Sync="TRUE">Shape</attrlabl>
				<attrdef Sync="TRUE">Feature geometry.</attrdef>
				<attrdefs Sync="TRUE">ESRI</attrdefs>
				<attrdomv>
					<udom Sync="TRUE">Coordinates defining the features.</udom>
				</attrdomv>
				<attalias Sync="TRUE">Shape</attalias><attrtype Sync="TRUE">Geometry</attrtype><attwidth Sync="TRUE">0</attwidth><atprecis Sync="TRUE">0</atprecis><attscale Sync="TRUE">0</attscale></attr>
			<attr>
				<attrlabl Sync="TRUE">AREA</attrlabl>
				<attrdef>Common Identifier - unique</attrdef>
				<attrdefs>USGS/USEPA</attrdefs>
				<attrdomv>
					<rdom>
						<rdommin>-9999 no data</rdommin>
						<rdommax>20101068</rdommax>
					</rdom>
				</attrdomv>
				<attalias Sync="TRUE">AREA</attalias><attrtype Sync="TRUE">Number</attrtype><attwidth Sync="TRUE">18</attwidth><atnumdec Sync="TRUE">5</atnumdec></attr>
			<attr>
				<attrlabl Sync="TRUE">PERIMETER</attrlabl>
				<attrdef>Reach Common Identifier</attrdef>
				<attrdefs>USGS/USEPA</attrdefs>
				<attrdomv>
					<rdom>
						<rdommin>-9998</rdommin>
						<rdommax>26874121</rdommax>
					</rdom>
				</attrdomv>
				<attalias Sync="TRUE">PERIMETER</attalias><attrtype Sync="TRUE">Number</attrtype><attwidth Sync="TRUE">18</attwidth><atnumdec Sync="TRUE">5</atnumdec></attr>
			<attr>
				<attrlabl Sync="TRUE">COM_ID</attrlabl>
				<attrdef>Feature Type</attrdef>
				<attrdefs>USGS</attrdefs>
				<attrdomv>
					<edom>
						<edomv>CANAL/DITCH</edomv>
						<edomvd>
artificial open waterway constructed to
transport water, to irrigate or drain land, to connect two or more bodies
of water, or to serve as a waterway for watercraft
</edomvd>
						<edomvds>USGS</edomvds>
					</edom>
					<edom>
						<edomv>INUNDATION AREA</edomv>
						<edomvd>area of land subject to flooding</edomvd>
						<edomvds>USGS</edomvds>
					</edom>
					<edom>
						<edomv>LAKE/POND</edomv>
						<edomvd>
standing body of water with a predominantly natural
shoreline surrounded by land
</edomvd>
						<edomvds>USGS</edomvds>
					</edom>
					<edom>
						<edomv>RESERVOIR</edomv>
						<edomvd>
constructed basin formed to contain water
or other liquids
</edomvd>
						<edomvds>USGS</edomvds>
					</edom>
					<edom>
						<edomv>STREAM/RIVER</edomv>
						<edomvd>body of flowing water</edomvd>
						<edomvds>USGS</edomvds>
					</edom>
					<edom>
						<edomv>SUBMERGED STREAM</edomv>
						<edomvd>
old river course inundated by an impounded
water body
</edomvd>
						<edomvds>USGS</edomvds>
					</edom>
					<edom>
						<edomv>SWAMP/MARSH</edomv>
						<edomvd>
noncultivated, vegetated area that is inundated or
saturated for a significant part of the year. The
vegetation is adapted for life in saturated soil conditions.
</edomvd>
						<edomvds>USGS</edomvds>
					</edom>
				</attrdomv>
				<attalias Sync="TRUE">COM_ID</attalias><attrtype Sync="TRUE">Number</attrtype><attwidth Sync="TRUE">11</attwidth></attr>
			<attr>
				<attrlabl Sync="TRUE">RCH_COM_ID</attrlabl>
				<attrdef>Code with detailed explanations of Ftype in table nhd.fcode</attrdef>
				<attrdefs>National Hydrography Dataset Users Guide</attrdefs>
				<attrdomv>
					<rdom>
						<rdommin>33602</rdommin>
						<rdommax>46600</rdommax>
					</rdom>
				</attrdomv>
				<attalias Sync="TRUE">RCH_COM_ID</attalias><attrtype Sync="TRUE">Number</attrtype><attwidth Sync="TRUE">11</attwidth></attr>
			<attr>
				<attrlabl Sync="TRUE">FTYPE</attrlabl>
				<attrdef>Elevation of water body</attrdef>
				<attrdefs>USGS</attrdefs>
				<attrdomv>
					<rdom>
						<rdommin>-9999</rdommin>
						<rdommax>760</rdommax>
					</rdom>
				</attrdomv>
				<attalias Sync="TRUE">FTYPE</attalias><attrtype Sync="TRUE">String</attrtype><attwidth Sync="TRUE">24</attwidth></attr>
			<attr>
				<attrlabl Sync="TRUE">FCODE</attrlabl>
				<attrdef>height of water surface</attrdef>
				<attrdefs>USGS</attrdefs>
				<attrdomv>
					<edom>
						<edomv>Average Water Elevation</edomv>
						<edomvd>
stage of a natural water body that prevails for the greater
part of the year
</edomvd>
						<edomvds>USGS</edomvds>
					</edom>
					<edom>
						<edomv>Normal Pool</edomv>
						<edomvd>
stage of an artificially impounded water body that prevails
for the greater part of the year
</edomvd>
						<edomvds>USGS</edomvds>
					</edom>
				</attrdomv>
				<attalias Sync="TRUE">FCODE</attalias><attrtype Sync="TRUE">Number</attrtype><attwidth Sync="TRUE">5</attwidth></attr>
			<attr>
				<attrlabl Sync="TRUE">STAGE</attrlabl>
				<attrdef>square kilometers</attrdef>
				<attrdefs>Software generated</attrdefs>
				<attrdomv>
					<udom>Software computed</udom>
				</attrdomv>
				<attalias Sync="TRUE">STAGE</attalias><attrtype Sync="TRUE">String</attrtype><attwidth Sync="TRUE">24</attwidth></attr>
			<attr>
				<attrlabl Sync="TRUE">SQ_KM</attrlabl>
				<attrdef>Common Name identifier</attrdef>
				<attrdefs>USGS, GNIS database</attrdefs>
				<attrdomv>
					<udom>Character Field</udom>
				</attrdomv>
				<attalias Sync="TRUE">SQ_KM</attalias><attrtype Sync="TRUE">Number</attrtype><attwidth Sync="TRUE">18</attwidth><atnumdec Sync="TRUE">3</atnumdec></attr>
			<attr>
				<attrlabl Sync="TRUE">GNIS_ID</attrlabl>
				<attrdef>Common Name</attrdef>
				<attrdefs>USGS</attrdefs>
				<attrdomv>
					<udom>Character Field</udom>
				</attrdomv>
				<attalias Sync="TRUE">GNIS_ID</attalias><attrtype Sync="TRUE">String</attrtype><attwidth Sync="TRUE">8</attwidth></attr>
			<attr><attrlabl Sync="TRUE">NAME</attrlabl><attalias Sync="TRUE">NAME</attalias><attrtype Sync="TRUE">String</attrtype><attwidth Sync="TRUE">99</attwidth></attr></detailed>
	</eainfo>
	<distinfo>
		<distrib>
			<cntinfo>
				<cntorgp>
					<cntorg>Bernardin, Lochmueller and Associates</cntorg>
				</cntorgp>
				<cntpos>Environmental Division</cntpos>
				<cntaddr>
					<addrtype>mailing and physical address</addrtype>
					<address>6200 Vogel Road</address>
					<city>Evansville</city>
					<state>IN</state>
					<postal>47715-4006</postal>
					<country>USA</country>
				</cntaddr>
				<cntvoice>800-423-7411</cntvoice>
				<cntfax>
812-479-6262
Contact_Website:  www.blainc.com
</cntfax>
				<hours>8am-5pm CST</hours>
			</cntinfo>
		</distrib>
		<resdesc>
HYDROGRAPHY_POLY_NHD_IN: Hydrography Water Bodies in Indiana
(United States Geological Survey, 1:100000, Polygon Shapefile)
</resdesc>
		<distliab>
No claims to accuracy are made on this data. It is intended
to be used only for general planning purposes. Detailed
planning or analysis will require more accurate data.
LIMITATION OF LIABILITY
The product is provided "AS IS",
without any other warranties or conditions, expressed or implied,
including, but not limited to, warranties for product quality, or
suitability to a particular purpose or use. The risk or liability
resulting from the use of this product is assumed by the user.
Bernardin, Lochmueller and Associates shares no liability with product
users indirect, incidental, special, or consequential damages whatsoever,
including, but not limited to, loss of revenue or profit, lost or damaged
data or other commercial or economic loss. Bernardin, Lochmueller and Associates
is not responsible for claims by a third party. The
maximum aggregate liability to the original purchaser shall not exceed
the amount paid by you for the product.
</distliab>
		<stdorder><digform><digtinfo><transize Sync="TRUE">0.000</transize><dssize Sync="TRUE">0.000</dssize></digtinfo></digform></stdorder></distinfo>
	<metainfo>
		<metd Sync="TRUE">20040615</metd>
		<metrd>20030513</metrd>
		<metc>
			<cntinfo>
				<cntorgp>
					<cntorg>Bernardin, Lochmueller and Associates</cntorg>
					<cntper>Cinda Bonds</cntper>
				</cntorgp>
				<cntpos>Environmental Biologist</cntpos>
				<cntaddr>
					<addrtype>Mailing and physical address</addrtype>
					<address>6200 Vogel Road</address>
					<city>Evansville</city>
					<state>IN</state>
					<postal>47715-4006</postal>
					<country>USA</country>
				</cntaddr>
				<cntvoice>800-423-7411</cntvoice>
				<cntfax>812-479-6262</cntfax>
				<cntemail>cbonds@blainc.com</cntemail>
				<hours>8am-5pm CST</hours>
			</cntinfo>
		</metc>
		<metstdn Sync="TRUE">FGDC Content Standards for Digital Geospatial Metadata</metstdn>
		<metstdv Sync="TRUE">FGDC-STD-001-1998</metstdv>
		<metac>None</metac>
		<metuc>
This metadata file is intended to accompany the
data set identified and received from the BLA/IGS.  It should not to be altered
or summarized.  BLA/IGS does not support secondary distribution.  If this
data set was received from anyone besides the BLA/IGS, this metadata file and
the data set it describes may lack integrity.
</metuc>
		<langmeta Sync="TRUE">en</langmeta><mettc Sync="TRUE">local time</mettc><metextns><onlink Sync="TRUE">http://www.esri.com/metadata/esriprof80.html</onlink><metprof Sync="TRUE">ESRI Metadata Profile</metprof></metextns></metainfo>
	<Esri><CreaDate>20040615</CreaDate><CreaTime>15262800</CreaTime><SyncOnce>FALSE</SyncOnce><SyncDate>20040615</SyncDate><SyncTime>14300600</SyncTime><ModDate>20040615</ModDate><ModTime>14300600</ModTime><DataProperties><lineage><Process Name="Clip_25" ToolSource="C:\Documents and Settings\jlphillips\Application Data\ESRI\ArcToolbox\My Toolboxes\Handy.tbx\Clip" Date="20040615" Time="143007">Clip HydrographyPoly_NHD_BLA clark_boundary C:\future_clips\Clark\lakes_clip.shp #</Process></lineage></DataProperties><MetaID>{8C613CE5-A86C-43B6-984A-BE38A422BDE8}</MetaID></Esri><dataIdInfo><envirDesc Sync="TRUE">Microsoft Windows 2000 Version 5.0 (Build 2195) Service Pack 4; ESRI ArcCatalog 9.0.0.535</envirDesc><dataLang><languageCode Sync="TRUE" value="en"></languageCode></dataLang><idCitation><resTitle Sync="TRUE">lakes_clip</resTitle><presForm><PresFormCd Sync="TRUE" value="005"></PresFormCd></presForm></idCitation><spatRpType><SpatRepTypCd Sync="TRUE" value="001"></SpatRepTypCd></spatRpType><dataExt><geoEle><GeoBndBox esriExtentType="native"><westBL Sync="TRUE">403316.60145</westBL><eastBL Sync="TRUE">692695.700017</eastBL><northBL Sync="TRUE">4625464.504569</northBL><southBL Sync="TRUE">4179674.832894</southBL><exTypeCode Sync="TRUE">1</exTypeCode></GeoBndBox></geoEle></dataExt><geoBox esriExtentType="decdegrees"><westBL Sync="TRUE">-88.16333</westBL><eastBL Sync="TRUE">-84.6821</eastBL><northBL Sync="TRUE">41.781024</northBL><southBL Sync="TRUE">37.744099</southBL><exTypeCode Sync="TRUE">1</exTypeCode></geoBox></dataIdInfo><mdLang><languageCode Sync="TRUE" value="en"></languageCode></mdLang><mdStanName Sync="TRUE">ISO 19115 Geographic Information - Metadata</mdStanName><mdStanVer Sync="TRUE">DIS_ESRI1.0</mdStanVer><mdChar><CharSetCd Sync="TRUE" value="004"></CharSetCd></mdChar><mdHrLv><ScopeCd Sync="TRUE" value="005"></ScopeCd></mdHrLv><mdHrLvName Sync="TRUE">dataset</mdHrLvName><distInfo><distributor><distorTran><onLineSrc><orDesc Sync="TRUE">002</orDesc><linkage Sync="TRUE">file://\\dnrfile1\DOW\TS\Water_Resources_and_Rights\future_mxds\clark\lakes_clip</linkage><protocol Sync="TRUE">Local Area Network</protocol></onLineSrc><transSize Sync="TRUE">0.000</transSize></distorTran><distorFormat><formatName Sync="TRUE">Shapefile</formatName></distorFormat></distributor></distInfo><refSysInfo><RefSystem><refSysID><identCode Sync="TRUE">NAD_1983_UTM_Zone_16N</identCode></refSysID></RefSystem></refSysInfo><spatRepInfo><VectSpatRep><topLvl><TopoLevCd Sync="TRUE" value="001"></TopoLevCd></topLvl><geometObjs Name="lakes_clip"><geoObjTyp><GeoObjTypCd Sync="TRUE" value="001"></GeoObjTypCd></geoObjTyp><geoObjCnt Sync="TRUE">0</geoObjCnt></geometObjs></VectSpatRep></spatRepInfo><mdDateSt Sync="TRUE">20040615</mdDateSt></metadata>
