<metadata xml:lang="en"><Esri><CreaDate>20220319</CreaDate><CreaTime>10180900</CreaTime><ArcGISFormat>1.0</ArcGISFormat><SyncOnce>FALSE</SyncOnce><DataProperties><lineage><Process ToolSource="c:\program files (x86)\arcgis\desktop10.8\ArcToolbox\Toolboxes\3D Analyst Tools.tbx\TerrainToRaster" Date="20220319" Time="101809" Name="" export="">TerrainToRaster G:\WillCo_IL_Lidar_2021\Will_DTM.gdb\DTM\DTM_Terrain G:\WillCo_IL_Lidar_2021\rasters\Will_DTM FLOAT NATURAL_NEIGHBORS "CELLSIZE 1.0" 0</Process></lineage><itemProps><itemName Sync="TRUE">will_dtm</itemName><itemLocation><linkage Sync="TRUE">file://U:\Workarea\Will\1st_Delivery\rasters\will_dtm</linkage><protocol Sync="TRUE">Local Area Network</protocol></itemLocation><nativeExtBox><westBL Sync="TRUE">1002589.415572</westBL><eastBL Sync="TRUE">1207209.415572</eastBL><southBL Sync="TRUE">1650355.564475</southBL><northBL Sync="TRUE">1845260.564475</northBL><exTypeCode Sync="TRUE">1</exTypeCode></nativeExtBox><imsContentType Sync="TRUE">002</imsContentType></itemProps><coordRef><type Sync="TRUE">Projected</type><geogcsn Sync="TRUE">GCS_NAD_1983_2011</geogcsn><csUnits Sync="TRUE">Linear Unit: Foot_US (0.304801)</csUnits><projcsn Sync="TRUE">NAD_1983_2011_StatePlane_Illinois_East_FIPS_1201_Ft_US</projcsn><peXml Sync="TRUE">&lt;ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/10.8'&gt;&lt;WKT&gt;PROJCS[&amp;quot;NAD_1983_2011_StatePlane_Illinois_East_FIPS_1201_Ft_US&amp;quot;,GEOGCS[&amp;quot;GCS_NAD_1983_2011&amp;quot;,DATUM[&amp;quot;D_NAD_1983_2011&amp;quot;,SPHEROID[&amp;quot;GRS_1980&amp;quot;,6378137.0,298.257222101]],PRIMEM[&amp;quot;Greenwich&amp;quot;,0.0],UNIT[&amp;quot;Degree&amp;quot;,0.0174532925199433]],PROJECTION[&amp;quot;Transverse_Mercator&amp;quot;],PARAMETER[&amp;quot;False_Easting&amp;quot;,984250.0],PARAMETER[&amp;quot;False_Northing&amp;quot;,0.0],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,-88.33333333333333],PARAMETER[&amp;quot;Scale_Factor&amp;quot;,0.999975],PARAMETER[&amp;quot;Latitude_Of_Origin&amp;quot;,36.66666666666666],UNIT[&amp;quot;Foot_US&amp;quot;,0.3048006096012192]],VERTCS[&amp;quot;NAVD88_height_(ftUS)&amp;quot;,VDATUM[&amp;quot;North_American_Vertical_Datum_1988&amp;quot;],PARAMETER[&amp;quot;Vertical_Shift&amp;quot;,0.0],PARAMETER[&amp;quot;Direction&amp;quot;,1.0],UNIT[&amp;quot;Foot_US&amp;quot;,0.3048006096012192]]&lt;/WKT&gt;&lt;XOrigin&gt;-17463800&lt;/XOrigin&gt;&lt;YOrigin&gt;-46132600&lt;/YOrigin&gt;&lt;XYScale&gt;137244822.07846552&lt;/XYScale&gt;&lt;ZOrigin&gt;-100000&lt;/ZOrigin&gt;&lt;ZScale&gt;3048.0060960121923&lt;/ZScale&gt;&lt;MOrigin&gt;-100000&lt;/MOrigin&gt;&lt;MScale&gt;10000&lt;/MScale&gt;&lt;XYTolerance&gt;0.0032808333333333331&lt;/XYTolerance&gt;&lt;ZTolerance&gt;0.0032808333333333331&lt;/ZTolerance&gt;&lt;MTolerance&gt;0.001&lt;/MTolerance&gt;&lt;HighPrecision&gt;true&lt;/HighPrecision&gt;&lt;WKID&gt;103037&lt;/WKID&gt;&lt;LatestWKID&gt;6455&lt;/LatestWKID&gt;&lt;VCSWKID&gt;105703&lt;/VCSWKID&gt;&lt;LatestVCSWKID&gt;6360&lt;/LatestVCSWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml></coordRef><RasterProperties><General><PixelDepth Sync="TRUE">32</PixelDepth><HasColormap Sync="TRUE">FALSE</HasColormap><CompressionType Sync="TRUE">None</CompressionType><NumBands Sync="TRUE">1</NumBands><Format Sync="TRUE">GRID</Format><HasPyramids Sync="TRUE">TRUE</HasPyramids><SourceType Sync="TRUE">continuous</SourceType><PixelType Sync="TRUE">floating point</PixelType><NoDataValue Sync="TRUE">-3.4028235e+38</NoDataValue></General></RasterProperties></DataProperties><SyncDate>20220331</SyncDate><SyncTime>13333800</SyncTime><ModDate>20220331</ModDate><ModTime>13333800</ModTime><ArcGISProfile>FGDC</ArcGISProfile></Esri><mdLang><languageCode value="eng"/><countryCode value="USA" Sync="TRUE"></countryCode></mdLang><mdChar><CharSetCd value="004"/></mdChar><mdHrLv><ScopeCd value="005"/></mdHrLv><mdContact><rpOrgName>Ayres Associates</rpOrgName><rpCntInfo><cntPhone><voiceNum>(608) 443-1200</voiceNum></cntPhone><cntAddress addressType="both"><delPoint>5201 E Terrace Drive, Suite 200</delPoint><city>Madison</city><adminArea>Wisconsin</adminArea><postCode>53718</postCode><country>US</country></cntAddress></rpCntInfo><role><RoleCd value="007"/></role></mdContact><mdDateSt>20220331</mdDateSt><mdStanName>ArcGIS Metadata</mdStanName><mdStanVer>1.0</mdStanVer><dataIdInfo><idCitation><resTitle>Will County, Illinois Lidar 2021</resTitle><date><pubDate>2021-08-13</pubDate></date><citRespParty><rpOrgName>Ayres Associates</rpOrgName><role><RoleCd value="006"/></role></citRespParty><presForm><fgdcGeoform>Lidar point cloud</fgdcGeoform><PresFormCd value="005" Sync="TRUE"></PresFormCd></presForm></idCitation><idAbs>The Will County, IL lidar project area covers approximately 887 square miles. The lidar data was acquired at an aggregate nominal point density (ANPD) of 10. Project specifications are based on Will County requirements. The data was developed based on a horizontal projection/datum of NAD83(2011) / Illinois State Plane East Zone (ftUS) (EPSG Code: 3435), and vertical datum of NAVD88 - Geoid12B (US Survey Feet)--ISGS comment: all the data uses Geoid 18--. LiDAR data was acquired using a Optech Galaxy T2000 sensor from March 29, 2021 to April, 13, 2021 in 8 total lifts. Acquisition occurred with leaves absent from deciduous trees, when no snow was present on the ground, and with rivers at or below normal levels. Note: ISGS QAQC review found that there are numerous noise points on the DSM, making that DSM unusable in some areas.</idAbs><idStatus><ProgCd value="001"/></idStatus><resMaint><maintFreq><MaintFreqCd value="011"/></maintFreq></resMaint><placeKeys><keyword>Will County</keyword><keyword>City of Joilet</keyword><keyword>Illinois</keyword></placeKeys><themeKeys><keyword>elevation</keyword><thesaName><resTitle>ISO 19115 Topic Categories</resTitle></thesaName></themeKeys><themeKeys><keyword>Elevation Data</keyword><keyword>Lidar</keyword><keyword>LAS Point Cloud</keyword><keyword>Remote Sensing</keyword><keyword>Model</keyword></themeKeys><searchKeys><keyword>Elevation Data</keyword><keyword>Lidar</keyword><keyword>LAS Point Cloud</keyword><keyword>Remote Sensing</keyword><keyword>Will County</keyword><keyword>City of Joilet</keyword><keyword>Model</keyword><keyword>Illinois</keyword><keyword>elevation</keyword></searchKeys><resConst><LegConsts><othConsts>No restrictions apply to this data.</othConsts></LegConsts></resConst><resConst><Consts><useLimit>None. However, users should be aware that temporal changes may have occurred since this dataset was collected and that some parts of these data may no longer represent actual surface conditions. Users should not use these data for critical applications without a full awareness of its limitations.</useLimit></Consts></resConst><spatRpType><SpatRepTypCd value="001"/></spatRpType><dataLang><languageCode value="eng"/><countryCode value="USA" Sync="TRUE"></countryCode></dataLang><tpCat><TopicCatCd value="006"/></tpCat><envirDesc>Terrasolid</envirDesc><dataExt><exDesc>ground condition</exDesc><tempEle><TempExtent><exTemp><TM_Period><tmBegin>2021-03-29</tmBegin><tmEnd>2021-04-13</tmEnd></TM_Period></exTemp></TempExtent></tempEle><geoEle/></dataExt><dataExt><geoEle><GeoBndBox><westBL>-88.266693</westBL><eastBL>-87.516512</eastBL><southBL>41.195142</southBL><northBL>41.732882</northBL></GeoBndBox></geoEle></dataExt><dataExt><geoEle><GeoBndBox esriExtentType="search"><exTypeCode Sync="TRUE">1</exTypeCode><westBL Sync="TRUE">-88.266693</westBL><eastBL Sync="TRUE">-87.516512</eastBL><northBL Sync="TRUE">41.732882</northBL><southBL Sync="TRUE">41.195142</southBL></GeoBndBox></geoEle></dataExt></dataIdInfo><mdMaint><maintFreq><MaintFreqCd value="012"/></maintFreq><maintNote>Last metadata review date: 20220331</maintNote></mdMaint><mdConst><SecConsts><class><ClasscationCd value="001"/></class><classSys>None</classSys><handDesc>None</handDesc></SecConsts></mdConst><dqInfo><dqScope><scpLvl><ScopeCd value="005"/></scpLvl></dqScope><report type="DQConcConsis"><measDesc>Data covers the entire area specified for this project.</measDesc></report><report type="DQCompOm"><measDesc>These LAS data files include all data points collected. No points have been removed or excluded. A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. The raw point cloud is complete and data passes Vertical Accuracy specifications.</measDesc></report><report type="DQAbsExtPosAcc" dimension="vertical"><measDesc>The project specifications require that only Non-Vegetated Vertical Accuracy (NVA) be computed for raw lidar point cloud swath files. The required accuracy (ACCz) is: 19.6 cm at a 95% confidence level, derived according to NSSDA, i.e., based on RMSE of 10 cm in the “bare earth” and "urban" land cover classes. These 63 points were not used in the calibration or post processing of the lidar point cloud data. The checkpoints were distributed throughout the project area and were surveyed using GPS techniques. Elevations from the unclassified lidar surface were measured for the x,y location of each check point. Elevations interpolated from the lidar surface were then compared to the elevation values of the surveyed control points. AccuracyZ has been prepared to meet 19.6 cm or better Non-Vegetated Vertical Accuracy at 95% confidence level using RMSE(z) x 1.9600 as defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASRPS Guidelines.</measDesc><evalMethDesc>Tested 0.059 meters NVA at a 95% confidence level using RMSE(z) x 1.9600 as defined by the National Standards for Spatial Data Accuracy (NSSDA). These 63 survey points were not used in the calibration or post processing of the lidar point cloud data</evalMethDesc><measResult><QuanResult><quanVal>0.059</quanVal></QuanResult></measResult></report><dataLineage><prcStep><stepDesc>LAS Point Cloud Classification: LiDAR data processing for the point cloud deliverable consists of classifying the LiDAR using a combination of automated classification and manual edit/reclassification processes. On most projects the automated classification routines will correctly classify 90-95 percent of the LiDAR points. The remaining 5-10 percent of the bare earth ground class must undergo manual edit and reclassification. Because the classified points serve as the foundation for the Terrain, DEM and breakline products, it is necessary for the QA/QC supervisor to review the completed point cloud deliverables prior to the production of any additional products. The following workflow steps are followed for automated LiDAR classification: 1. Lead technicians review the group of LiDAR tiles to determine which automated classification routines will achieve the best results. Factors such as vegetation density, cultural features, and terrain can affect the accuracy of the automated classification. The lead technicians have the ability to edit or tailor specific routines in order to accommodate the factors mentioned above, and achieve the best results and address errors. 2. Distributive processing is used to maximize the available hardware resources and speed up the automated processing as this is a resource-intensive process. 3. Once the results of the automated classification have been reviewed and passed consistent checks, the supervisor then approves the data tiles for manual classification. The following workflow steps are followed for manual edits of the LiDAR bare earth ground classification: 1. LiDAR technicians review each tile for errors made by the automated routines and correctly address errors any points that are in the wrong classification. By methodically panning through each tile, the technicians view the LiDAR points in profile, with a TIN surface, and as a point cloud. 2. Any ancillary data available, such as Google Earth, is used to identify any features that may not be identifiable as points so that the technician can make the determination to which classification the feature belongs. The QA/QC processes for the LiDAR processing phase consist of: 1. The lead technician reviews all automated classification results and adjust the macros as necessary to achieve the optimal efficiency. This is an iterative process, and the technician may need to make several adjustments to the macros, depending upon the complexity of the features in the area being processed.  During the manual editing process, the LiDAR technicians use a system of QA, whereby they check each other’s edits. This results in several benefits to the process:  There is a greater chance of catching minor blunders  It increases communication between technicians on technique and appearance  Solutions to problems are communicated efficiently  To ensure consistency across the project area, the supervisor reviews the data once the manual editing is complete. For this phase of a project, the following specifications are checked against: • Point cloud – all points must be classified according to the USGS classification standard for LAS. The all-return point cloud must be delivered in fully-compliant LAS version 1.4. • LAS files will use the Spatial Reference Framework according to project specification and all files shall be projected and defined. • General Point classifications:  Class 1. Processed, but unclassified  Class 2. Bare Earth  Class 7. Noise  Class 9. Water  Class 17. Bridge Decks  Class 18. High Noise  Class 20. Ignored ground (Breakline proximity)--ISGS comment: points are in classes 0,5,6,10,14 and 15 and not identified | All of the class 7 points should be flagged as withheld -- • Outliers, noise, blunders, duplicates, geometrically unreliable points near the extreme edge of the swath, and other points deemed unusable are to be identified using the "Withheld" flag. This applies primarily to points which are identified during pre-processing or through automated post-processing routines. Subsequently identified noise points may be assigned to the standard Noise Classes (Class 7). • Point classification shall be consistent across the entire project. Noticeable variations in the character, texture, or quality of the classification between tiles, swaths, lifts, or other non-natural divisions will be cause for rejection. • Once the data is imported into GeoCue and has undergone and passed the QC process, the strip data will be tiled to the 4500’ x 4500’ tiling scheme.</stepDesc><stepDateTm>2021-08-13</stepDateTm></prcStep><prcStep><stepDesc>The boresight for each lift was done individually as the solution may change slightly from lift to lift. The following steps describe the Raw Data Processing and Boresight process: 1) Technicians processed the raw data to LAS format flight lines using the final GPS/IMU solution. This LAS data set was used as source data for boresight. 2) Technicians first used Leica software to calculate initial boresight adjustment angles based on sample areas selected in the lift. These areas cover calibration flight lines collected in the lift, cross tie and production flight lines. These areas are well distributed in the lift coverage and cover multiple terrain types that are necessary for boresight angle calculation. The technician then analyzed the results and made any necessary additional adjustment until it is acceptable for the selected areas. 3) Once the boresight angle calculation was completed for the selected areas, the adjusted settings were applied to all of the flight lines of the lift and checked for consistency. The technicians utilized commercial and proprietary software packages to analyze how well flight line overlaps match for the entire lift and adjusted as necessary until the results met the project specifications. 4) Once all lifts were completed with individual boresight adjustment, the technicians checked and corrected the vertical misalignment of all flight lines and also the matching between data and ground truth. The relative accuracy was less than or equal to 7 cm RMSEz within individual swaths and less than or equal to 10 cm RMSEz or within swath overlap (between adjacent swaths). 5) The technicians ran a final vertical accuracy check of the boresighted flight lines against the surveyed check points after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level (Required Accuracy) was met. Point classification was performed according to USGS Lidar Base Specification 2.1, and breaklines were collected for water features. Bare earth DEMs were exported from the classified point cloud using collected breaklines for hydroflattening.</stepDesc><stepDateTm>2021-08-13</stepDateTm></prcStep></dataLineage></dqInfo><spatRepInfo><Georect><numDims>2</numDims><axisDimension type="001"><dimSize>194905</dimSize><dimResol><value Sync="TRUE" uom="ftUS">1.000000</value></dimResol></axisDimension><axisDimension type="002"><dimSize>204620</dimSize><dimResol><value Sync="TRUE" uom="ftUS">1.000000</value></dimResol></axisDimension><cellGeo><CellGeoCd value="002" Sync="TRUE"/></cellGeo><tranParaAv Sync="TRUE">1</tranParaAv><chkPtAv Sync="TRUE">0</chkPtAv><cornerPts><pos Sync="TRUE">1002589.415572 1650355.564475</pos></cornerPts><cornerPts><pos Sync="TRUE">1002589.415572 1845260.564475</pos></cornerPts><cornerPts><pos Sync="TRUE">1207209.415572 1845260.564475</pos></cornerPts><cornerPts><pos Sync="TRUE">1207209.415572 1650355.564475</pos></cornerPts><centerPt><pos Sync="TRUE">1104899.415572 1747808.064475</pos></centerPt><ptInPixel><PixOrientCd Sync="TRUE" value="001"></PixOrientCd></ptInPixel></Georect></spatRepInfo><spatRepInfo><VectSpatRep><geometObjs><geoObjTyp><GeoObjTypCd value="004"/></geoObjTyp></geometObjs></VectSpatRep><Georect><tranParaAv Sync="TRUE">1</tranParaAv><chkPtAv Sync="TRUE">0</chkPtAv><cornerPts><pos Sync="TRUE">1002589.415572 1650355.564475</pos></cornerPts><cornerPts><pos Sync="TRUE">1002589.415572 1845260.564475</pos></cornerPts><cornerPts><pos Sync="TRUE">1207209.415572 1845260.564475</pos></cornerPts><cornerPts><pos Sync="TRUE">1207209.415572 1650355.564475</pos></cornerPts><centerPt><pos Sync="TRUE">1104899.415572 1747808.064475</pos></centerPt><axisDimension><dimResol><value/></dimResol></axisDimension><axisDimension><dimResol><value/></dimResol></axisDimension><ptInPixel><PixOrientCd Sync="TRUE" value="001"></PixOrientCd></ptInPixel></Georect></spatRepInfo><distInfo><distFormat><formatName Sync="TRUE">Raster Dataset</formatName></distFormat></distInfo><mdHrLvName Sync="TRUE">dataset</mdHrLvName><refSysInfo><RefSystem><refSysID><identCode code="6455" Sync="TRUE"></identCode><idCodeSpace Sync="TRUE">EPSG</idCodeSpace><idVersion Sync="TRUE">8.9.3(10.3.1)</idVersion></refSysID></RefSystem></refSysInfo><contInfo><ImgDesc><contentTyp><ContentTypCd Sync="TRUE" value="003"></ContentTypCd></contentTyp><covDim><Band><dimDescrp Sync="TRUE">Will_DTM</dimDescrp><maxVal Sync="TRUE">874.661560</maxVal><minVal Sync="TRUE">400.017914</minVal><bitsPerVal Sync="TRUE">32</bitsPerVal><valUnit><UOM type="length"></UOM></valUnit></Band></covDim></ImgDesc></contInfo></metadata>
