<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="fgdc_classic.xsl"?>
<metadata xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://water.usgs.gov/GIS/metadata/usgswrd/fgdc-std-001-1998.xsd">
<idinfo>
<citation>
<citeinfo>
<origin>S. Mike Linhart and Kris D. Lund</origin>
<pubdate>2006</pubdate>
<title>Individual Target Data-Collection Points for Nine Eagles Lake, Decatur County, Iowa</title>
<geoform>vector digital data</geoform>
<serinfo>
<sername>Scientic Investigations Map</sername>
<issue>2006-2949-D</issue>
</serinfo>
<pubinfo>
<pubplace>Raleigh, NC</pubplace>
<publish>U.S. Geological Survey</publish>
</pubinfo>
<onlink>http://water.usgs.gov/lookup/getspatial?sim06_2949D_eag_targpts</onlink>
<lworkcit>
<citeinfo>
<origin>S. Mike Linhart and Kris D. Lund</origin>
<pubdate>2006</pubdate>
<title>Bathymetric Contour Maps of Lakes Surveyed in Iowa in 2004</title>
<geoform>pdf document</geoform>
<serinfo>
<sername>Scientific Investigations Map</sername>
<issue>2006-2949</issue>
</serinfo>
<pubinfo>
<pubplace>Raleigh, NC</pubplace>
<publish>U.S. Geological Survey</publish>
</pubinfo>
<onlink>http://pubs.water.usgs.gov/sim2006-2949</onlink>
</citeinfo>
</lworkcit>
</citeinfo>
</citation>
<descript>
<abstract>Point coverage of bathymetry target points for Nine Eagles Lake in Decatur Co., Iowa. The U.S. Geological Survey conducted a bathymetric survey of Nine Eagles Lake in 2004.</abstract>
<purpose>This digital, geographically referenced data set was developed by the U.S. Geological Survey to be used with the Lake Bathymetric project, Eastern Field Unit, Iowa City, Iowa.</purpose>
<supplinf>Present limitations of the data-collection equipment restrict data collection to depths greater than approximately 3.3 feet. For areas that were too shallow to profile or that were congested with debris, depths were collected manually along with a corresponding GPS location. The target point depths were converted to elevation and input into a geographic information system (GIS) software package, ArcInfo, to create a point coverage representing discrete point locations. This point coverage was one of two point coverages used to generate a three-dimensional surface representing the lake-bottom elevations.</supplinf>
</descript>
<timeperd>
<timeinfo>
<sngdate>
<caldate>2004</caldate>
</sngdate>
</timeinfo>
<current>ground condition</current>
</timeperd>
<status>
<progress>Complete</progress>
<update>None planned</update>
</status>
<spdom>
<bounding>
<westbc>
-93.774078</westbc>
<eastbc>
-93.763882</eastbc>
<northbc>
40.602854</northbc>
<southbc>
40.595284</southbc>
</bounding>
</spdom>
<keywords>
<theme>
<themekt>None</themekt>
<themekey>Lakes</themekey>
<themekey>Bathymetry</themekey>
<themekey>InlandWaters</themekey>
<themekey>Hydrology</themekey>
<themekey>Contours</themekey>
<themekey>USGS</themekey>
</theme>
<place>
<placekt>None</placekt>
<placekey>Nine Eagles Lake</placekey>
<placekey>Decatur County</placekey>
<placekey>Iowa</placekey>
</place>
</keywords>
<accconst>This digital, geographically referenced data set was developed by the U.S. Geological Survey to be used with the Lake Bathymetric project, Eastern Field Unit, Iowa City, Iowa.</accconst>
<useconst>The data are released on condition that neither the USGS nor the United States Government may be held liable for any damages resulting from its authorized or unauthorized use.</useconst>
<ptcontac>
<cntinfo>
<cntorgp>
<cntorg>U.S. Geological Survey</cntorg>
<cntper>Greg Nalley</cntper>
</cntorgp>
<cntpos>Project Chief - Eastern Field Unit Supervisory Hydrologist</cntpos>
<cntaddr>
<addrtype>mailing address</addrtype>
<address>P.O. Box 1230</address>
<city>Iowa City</city>
<state>Iowa</state>
<postal>52244</postal>
<country>USA</country>
</cntaddr>
<cntvoice>319-337-4191</cntvoice>
<cntfax>319-358-3606</cntfax>
<cntemail>gmnalley@usgs.gov</cntemail>
</cntinfo>
</ptcontac>
<datacred>Compilation of this data set prepared in cooperation with Iowa Department of Natural Resources.</datacred>
<native>Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.1.0.722</native>
</idinfo>
<dataqual>
<logic>Topologically Clean</logic>
<complete>Point coverage of bathymetry target points collected in areas of the lake where it was too shallow to collect bathymetry data using the 200-KHz transducer.</complete>
<posacc>
<horizpa>
<horizpar>Accuracy is tested by visual comparison of source with digital data on an interactive computer system.</horizpar>
</horizpa>
</posacc>
<lineage>
<srcinfo>
<srccite>
<citeinfo>
<origin>Iowa Department of Natural Resources</origin>
<pubdate>Unknown</pubdate>
<title>Digital Orthophoto Quad</title>
<edition>2002</edition>
<geoform>remote-sensing image</geoform>
</citeinfo>
</srccite>
<typesrc>Aerial Photo</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate>2002</caldate>
</sngdate>
</timeinfo>
<srccurr>ground condition</srccurr>
</srctime>
<srccitea>None</srccitea>
<srccontr>Digital orthophoto quads (DOQ's) were used in further adjusting and smoothing the coverage of the lake boundary. The coverage was overlain on the DOQ and additional vertices were digitized into the arcs at locations corresponding the shoreline shown on the DOQ.</srccontr>
</srcinfo>
<procstep>
<procdesc>Water-surface elevation: Initial measurements determined the elevation of the water surface of Nine Eagles Lake referenced to the North American Vertical Datum of 1988 (NAVD88) using standard surveying techniques. A reference point (point from which to measure the water-surface) elevation was established by leveling from a nearby reference mark (chiseled square on concrete slab 40 ft downstream from the boat ramp) with a known elevation. The reference point was established on the lip of a concrete slab 10 ft downstream from the boat ramp. The elevation of the reference point was found to be 937.53 ft (NAVD88). The elevation of the reference mark was determined by a static GPS survey. The static GPS survey data was submitted to the National Geodetic Survey's OPUS (Online Positioning Users Service) website for processing. The peak-to-peak error (difference between the maximum and minimum values obtained for the orthometric height during processing) of the OPUS solution was 0.148 feet (0.045 meters). Measuring down from the reference point (using a steel tape), the water-surface elevation of the lake was found to be 937.0 ft (NAVD88) on July 26, 2004.</procdesc>
<procdate>2004</procdate>
</procstep>
<procstep>
<procdesc>Data collection: Bathymetry data were collected using the Bathymetric Survey System (BSS+5) with a 200-kHZ intelligent depth sounder (IDS) and a differential GPS (Novatel DGPS beacon or omnistar receiver) (Specialty Devices, Inc., 2003, Bathymetric Survey System BSS+5 with omnistar manual: Specialty Devices, Inc., Plano, Texas, 38 p.). The depth sounder emits pulses of sound that are reflected off the lake bottom and are received by a transducer. The differential GPS has a horizontal accuracy of about 1 meter (3.281 ft). Bathymetry and position data were collected and stored in Hypack Max software (ver. 2.12a) (Hydrographic Survey Software, User's Manual, Hypack Max, Coastal Oceanographics, Inc., Middlefield, Conn.). In Hypack Max, the geodetic parameters were set to UTM north, Zone 15, and ellipsoid GRS-1980. Distance (easting and northing) and depth units were both collected in feet. Current limitations of the Bathymetric Survey System (BSS+5) restrict data collection to depths greater than approximately 3.3 ft.

A bar check calibration on the echo sounder was performed at the start of each day following established protocols (U.S. Army Corps of Engineers, 1994, Engineering and design: Hydrographic survey EM 1110-2-1003, chap. 9-3, p. 9-4 to 9-9). This was done to ensure that the echo sounder was calibrated correctly. The bar check involves suspending a 2-ft-diameter flat aluminum plate directly below the echo sounder. The suspension line is marked in 5-ft increments. An initial calibration is made at 5 ft by entering the speed of sound in water (based on water temperature) and then adjusting the offset of the transducer in the computer software. The offset is the draft of the transducer below the lake surface. The aluminum plate is then lowered in 5-ft increments (depending on the range of depths expected to be encountered on the day of data collection) and adjustments in the speed of sound are made until depth readings and the depth of the aluminum plate agree to within approximately 0.1 ft.

Bathymetry data were collected along planned transect lines that were set-up in Hypack Max using the internal line editor prior to data collection. Transect lines were spaced at 75-ft intervals perpendicular to the long axis of Nine Eagles Lake. Depending on boat speed, bathymetry data points were collected at approximately 5- to 10-ft intervals. Data points may be much closer in areas where transect or perimeter runs overlap. Bathymetry data points also were collected while driving the boat once around the perimeter of the lake. The distance of the boat from shore during the perimeter run varied, depending upon the depths encountered, due to the depth limitations of the data-collection equipment. The raw bathymetry data were recorded in Hypack Max as depths (in feet below water-surface to the lake bottom). Target points were collected in areas of the lake where it was too shallow to collect data with the BSS+5 system. Target point depths were collected manually, using a measuring device marked in 0.10-ft increments, along with a corresponding easting and northing location. Depending on lake-bottom type and surface conditions of the lake, accuracy of these measurements can vary between 0.05 ft and 0.5 ft. The number and location of target points were based on a judgment made in the field that was thought to be spatially representative of the area. In addition, shore point locations (easting and northing) were collected to define the shoreline of the lake. These locations are collected by touching the bow of the boat to the shoreline at various intervals along the shoreline and recording the position using a bow-mounted GPS antenna.</procdesc>
<procdate>2004</procdate>
</procstep>
<procstep>
<procdesc>Post-processing: Bathymetry data were processed using the Hypack Max software. Post-processing involved removing obvious spikes, inputting depths for the time-tagged target points, and editing extraneous points within the shore point files. In addition, tide corrections were applied in Hypack Max to convert raw sounding depths to elevation. The tide file subtracts the depths from the assigned lake-surface elevation (obtained from measurement from reference point elevation to lake water surface). The processed bathymetry data in Hypack Max were sorted and exported to XYZ format. The perimeter and transect bathymetry data were weeded (thinned) to reduce the density of points in one direction (along data-collection transects) to minimize the spatial pull of contours toward the densified lines. Of the original 5,600 data points, 1,367 data points remained. A total of three separate files were exported into XYZ format: (1) transect and perimeter bathymetry data; (2) shore point location data; and (3) the target point data. The XYZ files were then converted to ASCII text files for input into ESRI-ArcGIS (ver. 8.3).</procdesc>
<procdate>2004-2005</procdate>
</procstep>
<procstep>
<procdesc>Generation of Bathymetry Map: The output text files (containing northing, easting, and elevation) were input into an arc macro language (AML) script called CREATEPOINT in ARC to generate three corresponding coverages (eag_edgepts, eag_tinpts20, and eag_targpts). The eag_edgepts coverage contains the shore point locations. The eag_tinpts20 coverage contains the weeded bathymetry points collected with the depth sounder. The eag_targpts coverage contains the bathymetry target points collected manually. The projections for the coverages were then defined in ARC as UTM zone 15, NAD83, and units in feet.

To generate contours and calculate lake volume, a three-dimensional surface (TIN model) was created using 3-D Analyst in ArcMap. The TIN (eag_tinsmooth) model was generated to create the preliminary contours. The point coverages, eag_tinpts20 and eag_targpts, were input into eag_tinsmooth and triangulated as mass points. Height source was the "elevation" field in the point coverage attribute table. The eag_bndelev line coverage was input as a hard line using the "elev" field as the height source (elevation value = 937.0 ft). The eag_bndry coverage (polygon) was input as a hard clip to clip the TIN to the lake shoreline.</procdesc>
<procdate>2005-2006</procdate>
</procstep>
</lineage>
</dataqual>
<spdoinfo>
<direct>Vector</direct>
<ptvctinf>
<sdtsterm>
<sdtstype>Entity point</sdtstype>
<ptvctcnt>43</ptvctcnt>
</sdtsterm>
<sdtsterm>
<sdtstype>Point</sdtstype>
<ptvctcnt>4</ptvctcnt>
</sdtsterm>
</ptvctinf>
</spdoinfo>
<spref>
<horizsys>
<planar>
<mapproj>
<mapprojn>Transverse Mercator</mapprojn>
<transmer>
<sfctrmer>0.999600</sfctrmer>
<longcm>-93.000000</longcm>
<latprjo>0.000000</latprjo>
<feast>1640416.666667</feast>
<fnorth>0.000000</fnorth>
</transmer>
</mapproj>
<planci>
<plance>coordinate pair</plance>
<coordrep>
<absres>0.000005</absres>
<ordres>0.000005</ordres>
</coordrep>
<plandu>survey feet</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>
<vertdef>
<altsys>
<altdatum>North American Vertical Datum of 1988</altdatum>
<altres>0.1</altres>
<altunits>feet</altunits>
<altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
</altsys>
</vertdef>
</spref>
<eainfo>
<detailed>
<enttyp>
<enttypl>
eag_targpts.pat</enttypl>
<enttypd>Point Attribute Table</enttypd>
<enttypds>ARC/INFO(R) GIS Software</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>Area of feature in internal units squared.</attrdef>
<attrdefs>ESRI</attrdefs>
<attrdomv>
<udom>Area is always zero for point coverages.  Values are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>PERIMETER</attrlabl>
<attrdef>Perimeter of feature in internal units.</attrdef>
<attrdefs>ESRI</attrdefs>
<attrdomv>
<udom>Perimeter is always zero for point coverages.  Values are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>EAG_TARGPTS#</attrlabl>
<attrdef>Internal feature number.</attrdef>
<attrdefs>ESRI</attrdefs>
<attrdomv>
<udom>Sequential unique whole numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>EAG_TARGPTS-ID</attrlabl>
<attrdef>User-defined feature number.</attrdef>
<attrdefs>ESRI</attrdefs>
<attrdomv>
<udom>Sequential unique whole numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>EASTING</attrlabl>
<attrdef>X coordinate</attrdef>
<attrdefs>User defined</attrdefs>
<attrdomv>
<rdom>
<rdommin>1425552.43</rdommin>
<rdommax>1428359.20</rdommax>
<attrunit>U.S. Survey Feet</attrunit>
</rdom>
</attrdomv>
<attrvai>
<attrva>3.281</attrva>
<attrvae>Based on GPS manufacturers specifications (with differential correction).</attrvae>
</attrvai>
</attr>
<attr>
<attrlabl>NORTHING</attrlabl>
<attrdef>Y coordinate</attrdef>
<attrdefs>User defined</attrdefs>
<attrdomv>
<rdom>
<rdommin>14744455.83</rdommin>
<rdommax>14747188.50</rdommax>
<attrunit>U.S. Survey Feet</attrunit>
</rdom>
</attrdomv>
<attrvai>
<attrva>3.281</attrva>
<attrvae>Based on GPS manufacturers specifications (with differential correction).</attrvae>
</attrvai>
</attr>
<attr>
<attrlabl>ELEVATION</attrlabl>
<attrdef>Lake-bottom elevation</attrdef>
<attrdefs>User defined</attrdefs>
<attrdomv>
<rdom>
<rdommin>932.4</rdommin>
<rdommax>936.1</rdommax>
<attrunit>U.S. Survey Feet</attrunit>
</rdom>
</attrdomv>
<attrvai>
<attrva>0.1</attrva>
<attrvae>Most measurements +/- 0.1 ft. Varying lake-bottom types and lake-surface conditions can affect the accuracy of manual depth measurements.</attrvae>
</attrvai>
</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://answers.usgs.gov/cgi-bin/gsanswers?pemail=h2oteam&amp;subject=GIS+Dataset+sim06-2949D_eag_targpts</cntemail>
</cntinfo>
</distrib>
<resdesc>None</resdesc>
<distliab>The Lake Bathymetric project of the Eastern Field Unit, Iowa Water Science Center, the Water Resources Discipline (WRD), and the U.S. Geological Survey make no guarantee nor offer any warranty concerning the accuracy, condition, or application of the information contained in these geographic data.

The burden for determining fitness for use of this data lies entirely with the user. Although these data have been processed successfully on computers of WRD, no warranty, expressed or implied, is made by WRD regarding the use of these data on any other system, nor does the fact of distribution constitute or imply any such warranty.

In no event shall the WRD have any liability whatsoever for payment of any consequential, incidental, indirect, special, or tort damages of any kind, including, but not limited to, any loss of profits arising out of the delivery, installation, operation, or support by WRD.

Any use of trade, product, or firm names is for descriptive purposes only and does not imply endorsement by the U.S. Government.</distliab>
<stdorder>
<digform>
<digtinfo>
<formname>ARCE</formname>
<formcont>Full coverage</formcont>
<transize>0.028</transize>
</digtinfo>
<digtopt>
<onlinopt>
<computer>
<networka>
<networkr>http://water.usgs.gov/GIS/dsdl/sim06-2949D_eag_targpts.e00.gz</networkr>
</networka>
</computer>
</onlinopt>
</digtopt>
</digform>
<fees>None. This dataset is provided by USGS as a public service.</fees>
</stdorder>
</distinfo>
<metainfo>
<metd>20070207</metd>
<metc>
<cntinfo>
<cntorgp>
<cntorg>U.S. Geological Survey</cntorg>
</cntorgp>
<cntpos>Ask USGS -- Water Webserver Team</cntpos>
<cntaddr>
<addrtype>mailing address</addrtype>
<address>445 National Center</address>
<city>Reston</city>
<state>VA</state>
<postal>20192</postal>
<country>USA</country>
</cntaddr>
<cntvoice>1-888-275-8747 (1-888-ASK-USGS)</cntvoice>
<cntemail>http://answers.usgs.gov/cgi-bin/gsanswers?pemail=h2oteam&amp;subject=GIS+Dataset+sim06-2949D_eag_tarpts</cntemail>
</cntinfo>
</metc>
<metstdn>FGDC Content Standards for Digital Geospatial Metadata</metstdn>
<metstdv>FGDC-STD-001-1998</metstdv>
<mettc>local time</mettc>
<metac>None</metac>
<metuc>None</metuc>
</metainfo>
</metadata>
