<?xml version="1.0"?>
<!--<!DOCTYPE metadata SYSTEM "http://www.esri.com/metadata/esriprof80.dtd">-->
<metadata xml:lang="en"><Esri><MetaID>{47A8C7BE-658E-4B12-B542-94268D8A78E8}</MetaID><CreaDate>20110409</CreaDate><CreaTime>03525200</CreaTime><SyncOnce>FALSE</SyncOnce><SyncDate>20110409</SyncDate><SyncTime>04572900</SyncTime><ModDate>20110409</ModDate><ModTime>11011400</ModTime></Esri><idinfo><native Sync="TRUE">Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 9.3.0.1770</native><descript><langdata Sync="TRUE">en</langdata><abstract>Contours in ESRI 3d polyline shapefile format</abstract><purpose>The purpose of this survey is to provide the Vicksburg District with bare earth and top surface elevation data for providing geometry input to USACE hydraulic modeling programs.</purpose></descript><citation><citeinfo><origin>USACE, Vicksburg District</origin><pubdate>Unpublished Material</pubdate><title>MSD3_Contours</title><ftname Sync="TRUE">MSD3_Contours</ftname><geoform Sync="TRUE">vector digital data</geoform></citeinfo></citation><timeperd><current>ground condition</current><timeinfo><rngdates><begdate>20091200</begdate><enddate>201007</enddate></rngdates></timeinfo></timeperd><status><progress>In work</progress><update>As needed</update></status><spdom><bounding><westbc Sync="TRUE">-90.092421</westbc><eastbc Sync="TRUE">-88.826903</eastbc><northbc Sync="TRUE">34.983223</northbc><southbc Sync="TRUE">33.667827</southbc></bounding><lboundng><leftbc Sync="TRUE">2369875.710000</leftbc><rightbc Sync="TRUE">2747898.550000</rightbc><bottombc Sync="TRUE">1519327.100000</bottombc><topbc Sync="TRUE">1994875.850000</topbc></lboundng></spdom><keywords><theme><themekey>Contours</themekey></theme><place><placekey>Mississippi</placekey></place></keywords><accconst>Data are to be used by U.S. Government personnel only unless a written request to the USACE, Vicksburg District POC has been approved.</accconst><useconst>Users must abide by the terms of the non-disclosure agreement or the data sharing agreement under which the geospatial data were obtained.</useconst><natvform>shapefile</natvform><ptcontac><cntinfo><cntperp><cntper>Elijah C. Hunt</cntper><cntorg>U.S. Army Corps of Engineers, Vicksburg District</cntorg></cntperp><cntaddr><addrtype>mailing and physical address</addrtype><address>4155 East Clay St</address><city>Vicksburg</city><state>MS</state><postal>39183-3435</postal><country>USA</country></cntaddr><cntvoice>(601) 631-7040</cntvoice><cntemail>elijah.c.hunt@us.army.mil</cntemail></cntinfo></ptcontac><secinfo><secclass>Unclassified</secclass></secinfo></idinfo><dataIdInfo><envirDesc Sync="TRUE">Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 9.3.0.1770</envirDesc><dataLang><languageCode Sync="TRUE" value="en"></languageCode></dataLang><idCitation><resTitle Sync="TRUE">MSD3_Contours</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">2369875.71</westBL><eastBL Sync="TRUE">2747898.55</eastBL><northBL Sync="TRUE">1994875.85</northBL><southBL Sync="TRUE">1519327.1</southBL><exTypeCode Sync="TRUE">1</exTypeCode></GeoBndBox></geoEle></dataExt><geoBox esriExtentType="decdegrees"><westBL Sync="TRUE">-90.092421</westBL><eastBL Sync="TRUE">-88.826903</eastBL><northBL Sync="TRUE">34.983223</northBL><southBL Sync="TRUE">33.667827</southBL><exTypeCode Sync="TRUE">1</exTypeCode></geoBox></dataIdInfo><metainfo><langmeta Sync="TRUE">en</langmeta><metstdn Sync="TRUE">FGDC Content Standards for Digital Geospatial Metadata</metstdn><metstdv Sync="TRUE">FGDC-STD-001-1998</metstdv><mettc Sync="TRUE">local time</mettc><metc><cntinfo><cntorgp><cntper>Elijah C. Hunt</cntper><cntorg>USACE, Vicksburg District</cntorg></cntorgp><cntaddr><addrtype>mailing and physical address</addrtype><city>Vicksburg</city><state>MS</state><postal>39183-3435</postal><address>4155 East Clay St</address><country>USA</country></cntaddr><cntvoice>(601) 631-7040</cntvoice><cntemail>elijah.c.hunt@us.army.mil</cntemail></cntinfo></metc><metd Sync="TRUE">20110409</metd><metsi><metsc>Unclassified</metsc></metsi><metextns><onlink Sync="TRUE">http://www.esri.com/metadata/esriprof80.html</onlink><metprof Sync="TRUE">ESRI Metadata Profile</metprof></metextns></metainfo><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><resdesc Sync="TRUE">Downloadable Data</resdesc><stdorder><digform><digtinfo><formname>Shapfile</formname></digtinfo></digform></stdorder><distrib><cntinfo><cntorgp><cntorg>U.S. Army Corps of Engineers, Vicksburg District</cntorg></cntorgp></cntinfo></distrib></distinfo><distInfo><distributor><distorTran><onLineSrc><orDesc Sync="TRUE">002</orDesc><linkage Sync="TRUE">file://\\FLIGHT11\E$\Deliveries\MS_Delta\20471_MXD\SHAPES\MSD3_Contours</linkage><protocol Sync="TRUE">Local Area Network</protocol></onLineSrc><transSize Sync="TRUE">0.185</transSize></distorTran><distorFormat><formatName Sync="TRUE">Shapefile</formatName></distorFormat></distributor></distInfo><spdoinfo><direct Sync="TRUE">Vector</direct><ptvctinf><sdtsterm Name="MSD3_Contours"><sdtstype>String</sdtstype></sdtsterm></ptvctinf></spdoinfo><spref><horizsys><cordsysn><geogcsn Sync="TRUE">GCS_North_American_1983</geogcsn><projcsn Sync="TRUE">NAD_1983_StatePlane_Mississippi_West_FIPS_2302_Feet</projcsn></cordsysn><planar><planci><plance Sync="TRUE">coordinate pair</plance><plandu Sync="TRUE">survey feet</plandu><coordrep><absres Sync="TRUE">0.000000</absres><ordres Sync="TRUE">0.000000</ordres></coordrep></planci><mapproj><mapprojn Sync="TRUE">Transverse Mercator</mapprojn><transmer><sfctrmer Sync="TRUE">0.999950</sfctrmer><longcm Sync="TRUE">-90.333333</longcm><latprjo Sync="TRUE">29.500000</latprjo><feast Sync="TRUE">2296583.333333</feast><fnorth Sync="TRUE">0.000000</fnorth></transmer></mapproj></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></horizsys><vertdef><altsys><altdatum>North American Vertical Datum of 1988</altdatum><altunits>feet</altunits></altsys></vertdef></spref><refSysInfo><RefSystem><refSysID><identCode Sync="TRUE">NAD_1983_StatePlane_Mississippi_West_FIPS_2302_Feet</identCode></refSysID></RefSystem></refSysInfo><spatRepInfo><VectSpatRep><topLvl><TopoLevCd Sync="TRUE" value="001"></TopoLevCd></topLvl><geometObjs Name="MSD3_Contours"><geoObjTyp><GeoObjTypCd Sync="TRUE" value="001"></GeoObjTypCd></geoObjTyp><geoObjCnt Sync="TRUE">1247</geoObjCnt></geometObjs></VectSpatRep></spatRepInfo><mdDateSt Sync="TRUE">20110409</mdDateSt><dataqual><lineage><srcinfo><srccite><citeinfo><origin>Aeroquest Optimal, Inc.</origin><pubdate>Unpublished Material</pubdate><title>Light Detection and Ranging Data</title><geoform>vector digital data</geoform></citeinfo></srccite><srctime><timeinfo><rngdates><begdate>20091200</begdate><enddate>20100700</enddate></rngdates></timeinfo><srccurr>ground condition</srccurr></srctime></srcinfo><procstep><proccont><cntinfo><cntperp><cntper>Chris Jaeger</cntper><cntorg>Aeroquest Optimal, Inc.</cntorg></cntperp><cntpos>Project Manager</cntpos><cntaddr><addrtype>mailing and physical address</addrtype><address>4975 Bradford Dr. NW, Ste 100</address><city>Huntsville</city><state>AL</state><postal>35805</postal><country>USA</country></cntaddr><cntvoice>(256) 882-7788</cntvoice><cntemail>chris.jaeger@optimalgeo.com</cntemail></cntinfo></proccont><procdesc>DATA ACQUISITION:

     -  Ground Control Survey:  A ground control survey was conducted for the purpose of establishing aerial targets to validate the accuracy of the LiDAR and imagery data.  LiDAR test points were collected using RTK methods in accordance with FEMA guidelines and were used to validate the vertical accuracy of the LiDAR data.

     -  LiDAR Acquisition:  The LiDAR data was collected using a combination of three OPTECH ALTM sensores (3100, 3100EA, and Gemini).  Planned acquisition altitudes of 1,000m for the 3100 and 3100EA and 1,800' for the Gemini were used to support the generation of elevation data capable of supporting 2' contours meeting ASPRS Class 1 vertical accuracy standards.  The LiDAR collection was support by two ground base stations positioned so that the aircraft was no further than 20-miles from a base station at any given time during flight.</procdesc><procdate>20100700</procdate></procstep><procstep><proccont><cntinfo><cntperp><cntper>Chris Jaeger</cntper><cntorg>Aeroquest Optimal, Inc.</cntorg></cntperp><cntpos>Project Manager</cntpos><cntaddr><addrtype>mailing and physical address</addrtype><address>4975 Bradford Dr NW, Ste 100</address><city>Huntsville</city><state>AL</state><postal>35805</postal><country>USA</country></cntaddr><cntvoice>(256) 882-7788</cntvoice><cntemail>chris.jaeger@optimalgeo.com</cntemail></cntinfo></proccont><procdesc>LIDAR PROCESSING:

     -  LiDAR Calibration:  Initial processing of the GPS data was processed using POSPC MMS.  The SBET was generated and DASHMap software was used to generate georeferenced laser returns which were then processed in strip form allowing for the QC of the overlap between strips (lines).  The data from each line were combined and automated classification routines run to determine the initial surface model.  This initial surface model was then verified to the LiDAR test points.

     -  LiDAR Classification:  The calibrated LiDAR data was run through automated classification routines and then manually checked.  The data was classified int the following classes:  ground, hydrography, unclassified.  

     -  Breakline Collection:  LiDARgrammetry was used to collect hydro-enforced breaklines in stereo using synthetic stereo pairs generated in GeoCue using the LiDAR Intensity data.  The data was collected in the MicroStation environment and then converted into 3D shapefile format for inclusion in the Digital Elevation Models.

     - Contour Generation:  Two-foot contours were generated and checked using TerraModeler.  The contours were then imported into Shapefile format and the topology validated.  They were clipped to the tile boundaries for delivery.</procdesc><procdate>20110400</procdate></procstep><procstep><proccont><cntinfo><cntperp><cntper>Chris Jaeger</cntper><cntorg>Aeroquest Optimal, Inc.</cntorg></cntperp><cntpos>Project Manager</cntpos><cntaddr><addrtype>mailing and physical address</addrtype><address>4975 Bradford Dr NW, Ste 100</address><city>Huntsville</city><state>AL</state><postal>35805</postal><country>USA</country></cntaddr><cntvoice>(256) 882-7788</cntvoice><cntemail>chris.jaeger@optimalgeo.com</cntemail></cntinfo></proccont><procdesc>CONTOUR CREATION:  

     -  The contours were generated from the Bare Earth LAS and breaklines in MicroStation format using TerraScan and TerraModel.  The contours were then coverted to ESRI Shapefiles and merged by deliverable area into an ESRI 9.3 File Geodatabase.  Topology was built and validated on the deliverable area and corrected where necessary.  The final contour feature class was then clipped into tiles using ETGeoWizard's Split Layer by Location tool and output into shapefile format.</procdesc><procdate>20110400</procdate></procstep></lineage><attracc><attraccr>Attribute value domains and ranges are verified against a set domain of values according to SDSFIE.  Content is populated according to the Standard Operating Procedures for that layer.  Specific value content is verified by and authority with site knowledge and access to other sources.</attraccr></attracc><logic>Topological integrity of the data was validated using the validation tools in ESRI's ArcGIS 9.3.</logic><complete>Complete data set.</complete><posacc><horizpa><horizpar>The expected horizontal accuacy of elevation products derived using the OPTECH 3100 LiDAR sensor as determined from system  studies and other methods is 1/2000 of the flight height, which in the instance of this particular project was 1000m (3280.8 feet), giving a horizontal tolerance of less than 0.5m (1.64 survey feet).</horizpar></horizpa><vertacc><vertaccr>The DEMs for these survey areas are believed to be accurate.  The inclusion of breaklines collected from the LiDAR data provides for a more accurate DEM around hydro edges than could be achieved with the LiDAR points alone.

The data was processed in four separate acquisition areas and accuracy was reported by area (see LiDAR DEM Quality Report for details).  The accuracy statements below are based on the area having the highest RMSE(z) for all four errors and therefore some areas are of higher quality than this.

The following statements are derived in accordance with the ASPRS Guidelines for Vertical Accuracy Reporting for LiDAR Data (Flood, M., 2004).

Tested 0.34 US Survey Foot fundamental vertical accuracy at the 95% confidence level in open terrain using RMSE(z) x 1.9600.

Tested 0.56 US Survey Foot consolidated vertical accuracy at the 95% confidence level in open terrain, low &amp; high grass, and treed areas using RMSE(z) x 1.9600.</vertaccr></vertacc></posacc><cloud>0%</cloud></dataqual></metadata>
