<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE metadata SYSTEM "http://www.fgdc.gov/metadata/fgdc-std-001-1998.dtd">
<metadata><idinfo><citation><citeinfo><origin>Wilson &amp; Company, Inc.</origin><pubdate>2011</pubdate><pubtime>Unknown</pubtime><title>LAS data</title><geoform>vector digital data</geoform><onlink>\\opknas02\jobs\0930025400\LiDAR\06_Misc\Individual_Tile_Shps\08084130.shp</onlink></citeinfo></citation><descript><abstract>This dataset consists of modified FEMA-grade LiDAR point cloud data for the Illinois River floodplain in the following pools:

Marseilles Pool (only the portion in La Salle County)
Starved Rock Pool
Peoria Pool
LaGrange Pool
Alton Pool

The contract used to acquire this data also covered the acquisition of county-wide point clouds for the following counties:

Calhoun County, IL
Jersey County, IL
Union County, IL
Alexander County, IL
Perry County, MO

It also covered the acquisition of floodplain wide point cloud data for the Middle Mississippi River from the confluence with the Illinois River down to the confluence with the Ohio River.

The data was collected between the dates of 12/16/2009 and 12/28/2011. 

The program spanned multiple years and the dynamic nature of the floodplain will likely create surface inconsistencies caused by these temporal differences between flightlines of different dates.  Please be aware of these differences while analyzing the data.

Wilson &amp; Company and Sanborn Map Company combined to complete acquisition and processing of the LiDAR data.</abstract><purpose>This data will primarily be used for watershed modeling, storm water planning, floodplain determination, and structure design and estimation. Additional uses for this data by other agencies include roadway design, wetland restoration, and conservation practice design, placement, and estimating.</purpose><supplinf>This dataset contains the LAS bare earth data for the project.

Individual LiDAR tiles contain multiple flightlines flown on different dates.  Please consult the table below for specific coordination of flightline and ground conditions:
12/16/2009	1201-1220	
12/17/2009	1221-1233   1132-1145
2/14/2011	901-909	    1044-1057
2/15/2011	1027-1043	
2/18/2011	1001-1026	
3/16/2011	601-631	
3/17/2011	632-645	
3/23/2011	646-653	
4/12/2011	101-114	
4/13/2011	201-220	
4/14/2011	301-322	
12/7/2011	704-724	
12/8/2011	701-703	655-674
12/10/2011	401-416	
12/11/2011	417-432	501-517
12/12/2011	801-814	
12/18/2011	1101-1131	
12/28/2011	1234-1249  1146-1152</supplinf></descript><timeperd><timeinfo><mdattim><sngdate><caldate>2009-12-16</caldate></sngdate><sngdate><caldate>2009-12-17</caldate></sngdate><sngdate><caldate>2011-2-14</caldate></sngdate><sngdate><caldate>2011-2-15</caldate></sngdate><sngdate><caldate>2011-2-18</caldate></sngdate><sngdate><caldate>2011-3-16</caldate></sngdate><sngdate><caldate>2011-3-17</caldate></sngdate><sngdate><caldate>2011-3-23</caldate></sngdate><sngdate><caldate>2011-4-12</caldate></sngdate><sngdate><caldate>2011-4-13</caldate></sngdate><sngdate><caldate>2011-4-14</caldate></sngdate><sngdate><caldate>2011-12-7</caldate></sngdate><sngdate><caldate>2011-12-8</caldate></sngdate><sngdate><caldate>2011-12-10</caldate></sngdate><sngdate><caldate>2011-12-11</caldate></sngdate><sngdate><caldate>2011-12-12</caldate></sngdate><sngdate><caldate>2011-12-18</caldate></sngdate><sngdate><caldate>2011-12-28</caldate></sngdate></mdattim></timeinfo><current>ground condition</current></timeperd><status><progress>Complete</progress><update>Unknown</update></status><spdom><bounding><westbc>-90.55</westbc><eastbc>-88.32</eastbc><northbc>41.24</northbc><southbc>36.53</southbc></bounding></spdom><keywords><theme><themekt>Mississippi River, Illinois Waterway, LiDAR, 5 County</themekt><themekey>LiDAR</themekey><themekey>Mississippi River Illinois Waterway 5 County</themekey></theme></keywords><accconst>None.</accconst><useconst>None.  However, users should be aware that temporal changes may have occurred since this data set was collected and that some parts of this data may no longer represent actual surface conditions. Users should not use this data for critical applications without a full awareness of its limitations. Acknowledgment of Wilson &amp; Company, Inc. would be appreciated for products derived from these data.</useconst><ptcontac><cntinfo><cntorgp><cntorg>US Army Corps of Engineers, Rock Island District</cntorg><cntper>Michael Dougherty</cntper></cntorgp><cntaddr><addrtype>mailing and physical address</addrtype><address>800 E 101st Terrace, Suite 200</address><city>Kansas City</city><state>MO</state><postal>64131</postal><country>United States of America</country></cntaddr><cntvoice>309-794-5491</cntvoice><cntemail>michael.p.dougherty@usace.army.mil</cntemail><hours>8:00 A.M. to 4:30 P.M.</hours><cntpos>Rock Island District Enterprise GIS Data Manager</cntpos></cntinfo></ptcontac><native>Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 9.3</native><secinfo><secclass>Unclassified</secclass><secsys>NA</secsys><sechandl>NA</sechandl></secinfo></idinfo><dataqual>All LiDAR products are reviewed upon generation in commercially available geospatial software.
<attracc><attraccr>The LiDAR data is checked for quality and completeness during, and immediately following each mission.  Coverage and accuracy is verified in the office as the data is sent.  The collected elevation data meets the SOW requirements. The flight altitude and speed was optimized to acquire the specified point resolution and accuracy. The highest resolution, and absolute referenced elevation data was produced. Density of ground mass points is appropriate for meeting the stated accuracies. Nominal Pulse Spacing of the LiDAR System was planned to 1.4 meters; multiple discrete returns-3 per pulse.
LiDAR data was acquired from Dec. 2009 and is ongoing.</attraccr><qattracc><attraccv>18.5cm</attraccv><attracce>LiDAR data processed to a modified FEMA specification. Fundamental vertical accuracies to meet or exceed 18.5cm, and supplemental vertical accuracies to meet or exceed 37cm.</attracce></qattracc></attracc><complete>The LiDAR data is checked for quality and completeness during, and immediately following each mission.  Coverage and accuracy is verified in the office as the data is sent.  Elevation products are opened and visually reviewed for completeness.  File sizes and numbers of files are also reviewed as products are loaded onto hard drives for delivery.</complete><posacc><horizpa><horizpar>Horizontal Accuracy for the acquired LiDAR is based upon calibration field results.  Data processed to modified FEMA specifications to meet or exceed 1m.</horizpar><qhorizpa><horizpav>.7m</horizpav><horizpae>Horizontal Accuracy for the acquired LiDAR is based upon calibration field results.  Data processed to modified FEMA specifications to meet or exceed 1m.  Horizontal accuracy tested at fliigh altitude of 1850m AMT to 0.7m</horizpae></qhorizpa></horizpa><vertacc><vertaccr>LiDAR data processed to a modified FEMA specification. Fundamental vertical accuracies to meet or exceed 18.5cm, and supplemental vertical accuracies to meet or exceed 37cm. Over 400 survey checkpoints were collected across the project site for analysis and validation.  The detailed results are listed in the accompanying vertical accuracy report.</vertaccr><qvertpa><vertaccv>0.119</vertaccv><vertacce>LiDAR data processed to a modified FEMA specification. Fundamental vertical accuracies to meet or exceed 18.5cm, and supplemental vertical accuracies to meet or exceed 37cm.  Analysis of the checkpoints across mulitple land cover classes returned a consolidated RMSE of 0.119m</vertacce></qvertpa></vertacc></posacc><lineage><srcinfo><typesrc>disc</typesrc><srctime><timeinfo><mdattim><sngdate><caldate>2009-12-16</caldate></sngdate><sngdate><caldate>2009-12-17</caldate></sngdate><sngdate><caldate>2011-2-14</caldate></sngdate><sngdate><caldate>2011-2-15</caldate></sngdate><sngdate><caldate>2011-2-18</caldate></sngdate><sngdate><caldate>2011-3-16</caldate></sngdate><sngdate><caldate>2011-3-17</caldate></sngdate><sngdate><caldate>2011-3-23</caldate></sngdate><sngdate><caldate>2011-4-12</caldate></sngdate><sngdate><caldate>2011-4-13</caldate></sngdate><sngdate><caldate>2011-4-14</caldate></sngdate><sngdate><caldate>2011-12-7</caldate></sngdate><sngdate><caldate>2011-12-8</caldate></sngdate><sngdate><caldate>2011-12-10</caldate></sngdate><sngdate><caldate>2011-12-11</caldate></sngdate><sngdate><caldate>2011-12-12</caldate></sngdate><sngdate><caldate>2011-12-18</caldate></sngdate><sngdate><caldate>25011-12-28</caldate></sngdate></mdattim></timeinfo><srccurr>ground condition</srccurr></srctime><srccontr>Individual LiDAR tiles contain multiple flightlines flown on different dates.  Please consult the table below for specific coordination of flightline and ground conditions:
12/16/2009	1201-1220	
12/17/2009	1221-1233	1132-1145
2/14/2011	901-909	                1044-1057
2/15/2011	1027-1043	
2/18/2011	1001-1026	
3/16/2011	601-631	
3/17/2011	632-645	
3/23/2011	646-653	
4/12/2011	101-114	
4/13/2011	201-220	
4/14/2011	301-322	
12/7/2011	704-724	
12/8/2011	701-703	655-674
12/10/2011	401-416	
12/11/2011	417-432	501-517
12/12/2011	801-814	
12/18/2011	1101-1131	
12/28/2011	1234-1249	1146-1152</srccontr><srccite><citeinfo><origin>Wilson &amp; Company</origin><pubdate>2011</pubdate><title>LiDAR Deliverables</title><onlink>NA</onlink></citeinfo></srccite><srccitea>citeinfo</srccitea></srcinfo><procstep><procdesc>LiDAR Processing:
The collected elevation data meets the SOW's requirements for 2-foot contours. The flight altitude and speed was optimized to acquire the specified point resolution and accuracy. The highest resolution, and absolute referenced elevation data was produced. Density of ground mass points is appropriate for meeting the stated accuracies. Nominal Pulse Spacing of the LiDAR System was planned to 1.4 meters; multiple discrete returns-3 per pulse.
LiDAR data was acquired from Dec. 2009 to Fall of 2011.

LiDAR acquisition and processing was performed using modified USGS and FEMA guidelines as base specifications.  Modifications were made to the base specifications to suit specific project needs.</procdesc><procdate>Unknown</procdate></procstep><procstep><procdesc>LiDAR Processing:
The LiDAR data is checked for quality and completeness during, and immediately following each mission.  Upon verification, the laser range data is processed and output in Optech's DashMap using the SBET generated from processing the ABGPS/IMU data with ground ABGPS base stations in Applanix's POS MMS.  On-site calibration flights are performed to validate the initial calibration values generated during calibration flights over Wilson &amp;amp; Company's LiDAR Calibration Range.  The calibrated missions are then combined and adjusted to project control using the TerraSolid suite of products, which are used for most LiDAR processing and editing steps.  An accuracy assessment is performed to validate the LiDAR surface prior to classification. Upon surface validation, the LiDAR point cloud is classified using a series of algorithms to find bare earth and other associated features.  The processed bare earth surface is manually further refined to a final surface, free from anomalies and other non-ground objects.  GeoCue is used as a process management tool to track process steps through a series of checklists and assigned tasks.  The final point cloud data set was provided in LAS v1.2. </procdesc><procdate>Unknown</procdate></procstep><procstep><procdesc>Metadata imported.</procdesc><srcused>J:\0930025400\LiDAR\06_Misc\XML_working\07404464.shp.xml</srcused><procdate>20120531</procdate><proctime>14025500</proctime></procstep></lineage><logic>The LiDAR acquisition missions were executed over a wide range of dates and conditions due to weather and project schedule.  This temporal discrepancy may cause some spatial discrepancy between the two datasets.  The user should be aware that this deviation exists.
The elevation products generated during this project were cross-checked as a complete data set as well as being subjected to independent QA/QC.  All elevation products were generated from the unified and classified LiDAR point cloud.

Independent QA performed by EC-TS Survey Section Defer, Bigelow and Giger in June and July 2012
Acceptance and ownership of W912EK-05-D-0004 TO 8, TO 18 and TO 21 has been approved by Scott Kool, Chief of Surveys, Rock Island District, US Army Corps of Engineers.</logic><cloud>0</cloud></dataqual><eainfo><detailed><enttyp><enttypl>Bare Earth LAS</enttypl><enttypd>Mississippi River/Illinois Waterway/5 County LiDAR Product</enttypd><enttypds>ALTM Gemini</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>NAME</attrlabl><attrdef>Name</attrdef><attrdefs>ESRI</attrdefs><attrdomv><udom>Feature Name</udom></attrdomv></attr></detailed></eainfo><distinfo><resdesc>Downloadable Data</resdesc><stdorder><digform><digtinfo><transize>1</transize><formname>SHP</formname><formvern>Unknown</formvern><formspec>Unknown</formspec><formcont>Unknown</formcont><filedec>Unknown</filedec></digtinfo><digtopt><onlinopt><computer><networka><networkr>Unknown</networkr></networka></computer><accinstr>Unknown</accinstr><oncomp>Unknown</oncomp></onlinopt><offoptn><offmedia>Unknown</offmedia><reccap><recden>1</recden><recdenu>Unknown</recdenu></reccap><recfmt>Unknown</recfmt><compat>Unknown</compat></offoptn></digtopt></digform><fees>Unknown</fees><ordering>Unknown</ordering><turnarnd>Unknown</turnarnd></stdorder><distrib><cntinfo><cntorgp><cntorg>US Army Corps of Engineers, Rock Island District</cntorg><cntper>Michael Dougherty</cntper></cntorgp><cntvoice>309-794-5491</cntvoice><hours>0800-1700</hours><cntaddr><addrtype>mailing and physical address</addrtype><address>800 E 101st Terrace, Suite 200</address><city>Kansas City</city><state>MO</state><postal>64131</postal><country>USA</country></cntaddr><cntpos>Rock Island District Enterprise GIS Data Manager</cntpos></cntinfo></distrib><distliab>Users should be aware that temporal changes may have occurred since this data set was collected and that some parts of this data may no longer represent actual surface conditions. Users should not use this data for critical applications without a full awareness of its limitations. Acknowledgment of Wilson &amp; Company, Inc. would be appreciated for products derived from these data.</distliab><availabl><timeinfo><sngdate><caldate>unknown</caldate><time>unknown</time></sngdate></timeinfo></availabl></distinfo><metainfo><metc><cntinfo><cntorgp><cntorg>Wilson &amp; Company, Inc.</cntorg><cntper>Wilson &amp; Company Personnel</cntper></cntorgp><cntaddr><addrtype>mailing and physical address</addrtype><address>800 E 101st Terrace, Suite 200</address><city>Kansas City</city><state>MO</state><postal>64131</postal><country>USA</country></cntaddr><cntvoice>816.701.3100</cntvoice></cntinfo></metc><metstdn>FGDC Content Standards for Digital Geospatial Metadata</metstdn><metstdv>FGDC-STD-001-1998</metstdv><mettc>local time</mettc><metd>20120507</metd></metainfo><dataIdInfo><envirDesc>Microsoft Windows Vista Version 6.1 (Build 7600) ; ESRI ArcCatalog 9.3.0.1770</envirDesc><dataLang><languageCode value="en"/></dataLang><idCitation><resTitle>08084130</resTitle><presForm><PresFormCd value="005"/></presForm></idCitation><spatRpType><SpatRepTypCd value="001"/></spatRpType><dataExt><geoEle><GeoBndBox esriExtentType="native"><westBL>808000</westBL><eastBL>810000</eastBL><northBL>4132000</northBL><southBL>4130000</southBL><exTypeCode>1</exTypeCode></GeoBndBox></geoEle><vertEle><vertMinVal>576.52</vertMinVal><vertMaxVal>1006.04</vertMaxVal></vertEle></dataExt><geoBox esriExtentType="decdegrees"><westBL>-89.526845</westBL><eastBL>-89.503497</eastBL><northBL>37.283654</northBL><southBL>37.264996</southBL><exTypeCode>1</exTypeCode></geoBox></dataIdInfo><mdLang><languageCode value="en"/></mdLang><mdStanName>ISO 19115 Geographic Information - Metadata</mdStanName><mdStanVer>DIS_ESRI1.0</mdStanVer><mdChar><CharSetCd value="004"/></mdChar><mdHrLv><ScopeCd value="005"/></mdHrLv><mdHrLvName>dataset</mdHrLvName><distInfo><distributor><distorTran><onLineSrc><orDesc>002</orDesc><linkage>file://\\opknas02\jobs\0930025400\LiDAR\06_Misc\Individual_Tile_Shps\08084130.shp</linkage><protocol>Local Area Network</protocol></onLineSrc><transSize>0.000</transSize></distorTran><distorFormat><formatName>Shapefile</formatName></distorFormat></distributor></distInfo><spdoinfo><direct>Point</direct><ptvctinf><sdtsterm><sdtstype>Point</sdtstype><ptvctcnt>1</ptvctcnt></sdtsterm></ptvctinf></spdoinfo><spref><horizsys><planar><planci><plance>coordinate pair</plance><plandu>meters</plandu><coordrep><absres>.01</absres><ordres>.01</ordres></coordrep></planci><gridsys><gridsysn>Universal Transverse Mercator</gridsysn><utm><utmzone>15</utmzone><transmer><sfctrmer>0.999600</sfctrmer><longcm>-93.000000</longcm><latprjo>0.000000</latprjo><feast>500000.000000</feast><fnorth>0.000000</fnorth></transmer></utm></gridsys></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><altenc>Explicit elevation coordinate included with horizontal coordinates</altenc><altres>0.01</altres><altdatum>North American Vertical Datum of 1988</altdatum><altunits>meters</altunits></altsys></vertdef></spref><refSysInfo><RefSystem><refSysID><identCode>NAD_1983_UTM_Zone_15N</identCode></refSysID></RefSystem></refSysInfo><spatRepInfo><VectSpatRep><topLvl><TopoLevCd value="001"/></topLvl><geometObjs><geoObjTyp><GeoObjTypCd value="001"/></geoObjTyp><geoObjCnt>1</geoObjCnt></geometObjs></VectSpatRep><GridSpatRep><numDims>2</numDims><cellGeo><CellGeoCd value="002"/></cellGeo><tranParaAv>1</tranParaAv><axDimProps><Dimen><dimName><DimNameTypCd value="002"/></dimName><dimSize>10000</dimSize><dimResol><value>0.5</value><uom><UomLength><uomName>unknown</uomName></UomLength></uom></dimResol></Dimen><Dimen><dimName><DimNameTypCd value="001"/></dimName><dimSize>10000</dimSize><dimResol><value>0.5</value><uom><UomLength><uomName>unknown</uomName></UomLength></uom></dimResol></Dimen></axDimProps></GridSpatRep></spatRepInfo><mdDateSt>20120531</mdDateSt><Esri><DataProperties><copyHistory><copy source="\\mvr-netapp1\egis\Data\Elevation\MVR\LiDAR\ILWW\MS_River_ILWW_5County\01_Metadata\LAS\Alexander\08084130.las" dest="\\mvr-netapp1\egis\Data\Elevation\MVR\LiDAR\ILWW\MS_River_ILWW_5County\01_Metadata\Project-Level\08084130.las" date="20120801" time="10092100"></copy></copyHistory></DataProperties></Esri></metadata>
