<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<metadata>
<idinfo>
<citation>
<citeinfo>
<origin>Illinois State Geological Survey (ISGS), a division of the Prairie Research Institute of the University of Illinois</origin>
<pubdate>Unpublished Material</pubdate>
<title>Digital Elevation Model (DEM) for Dupage County, Illinois. 2006</title>
<geoform>raster digital data</geoform>
<onlink>http://www.isgs.illinois.edu</onlink>
<othercit>Recommended Publishing Citation:Illinois Height Modernization Program, Illinois State Geological Survey, and DuPage County, 2002–2014, Illinois LiDAR county database: Illinois State Geological Survey http://crystal.isgs.uiuc.edu/nsdihome/webdocs/ilhmp/ (accessed September 18, 2014)</othercit>
</citeinfo>
</citation>
<descript>
<abstract>This Digital Elevation Model (DEM) data was produced all or in part from LiDAR information as of 2006. The LiDAR derived DEM covers Dupage County, Illinois and include inland streams, rivers, lakes ponds and tidal features. These data are appropriate for use in local and regional analysis. This data set has a vertical accuracy of 6.09 centimeters RMSEz, horizontal accuracy of 0.57 meters and point spacing of 1.09 meters. Digital Elevation Models (including terrain and surface models) are raster data sets created from whole LiDAR point cloud data sets (LAS files). The LAS files are the standard LiDAR file format which contains the raw point cloud data, these data are normally classified and distinguished between points on the ground, water or elevated features such as buildings, trees, towers, bridges, etc.. These LAS files are processed into elevation models to create gridded rasters. The first returns can be used to map the top reflective surface (Digital Surface Models - DSM), these normally include open terrain areas, as well as the tops of buildings, trees, towers, and other features elevated above the bare earth. The last returns are used to map the bare-earth terrain (Digital Terrain Models - DTM), these are normally produced with irregularly-spaced points rather than the uniform grid structure of a Digital Elevation Model (DEM), Digital Terrain Models will often include breaklines to help define edges of water bodies.</abstract>
<purpose>These acquisitions of the LiDAR data and its derivatives were made possible by a grant from the National Geodetic Survey for the National Height Modernization Program. The program is in place to enable states access to accurate, reliable heights using global positioning satellite (GPS) technology in conjunction with traditional leveling, gravity, and modern remote sensing technologies. LiDAR data and its derivatives assist in real-world uses around the state of Illinois such as; highway engineering, flood prediction, agricultural land management, mining subsidence, monitoring archaeological features, locating sinkholes and applied geologic science.
The data do not replace the need for detailed site-specific studies. The information is not appropriate for, and is not to be used as, a geodetic, legal, or engineering base. The information has no legal basis in the definition of boundaries or property lines and is not intended as a substitute for surveyed locations such as can be determined by a registered Public Land Surveyor.</purpose>
<supplinf>none</supplinf>
</descript>
<timeperd>
<timeinfo>
<sngdate>
<caldate>20060404</caldate>
</sngdate>
</timeinfo>
<current>
ground condition
</current>
</timeperd>
<status>
<progress>Complete</progress>
<update>Unknown</update>
</status>
<spdom>
<bounding>
<westbc>-88.2597339225</westbc>
<eastbc>-87.9182261179</eastbc>
<northbc>41.9967349365</northbc>
<southbc>41.7271988659</southbc>
</bounding>
</spdom>
<keywords>
<theme>
<themekt>
None
</themekt>
<themekey>
Light Detection and Ranging
</themekey>
<themekey>
LiDAR
</themekey>
<themekey>
Bare Earth
</themekey>
<themekey>
Point Cloud
</themekey>
<themekey>Digital Elevation Model</themekey>
<themekey>DEM</themekey>
<themekey>Elevation</themekey>
<themekey>Surface Model</themekey>
<themekey>Digital Surface Model</themekey>
<themekey>DSM</themekey>
<themekey>Hillshade</themekey>
</theme>
<place>
<placekt>
None
</placekt>
<placekey>
US
</placekey>
<placekey>
Illinois Department of Transportation
</placekey>
<placekey>
Illinois
</placekey>
<placekey>Dupage County</placekey>
</place>
<temporal>
<tempkt>None</tempkt>
<tempkey>2006</tempkey>
</temporal>
</keywords>
<accconst>ISGS information must be obtained directly from the ISGS or from an authorized distributor. Be aware that ISGS information obtained from an unauthorized third party may have been altered subsequent to original distribution, or may no longer be current. Any access to these data, Web sites, computer systems, electronic services, and electronic networks is governed by University and campus policies, in particular, but not limited to, the Policy on Appropriate Use of Computers and Network Systems at the University of Illinois at Urbana-Champaign, the ISGS Terms of Use document available at the ISGS Web site, and the University of Illinois Web Privacy Notice. Links to these are provided in the Cross References section.</accconst>
<useconst>ISGS information is the property of and copyrighted by the Board of Trustees of the University of Illinois with all rights reserved. University copyright policy is stated in the General Rules Concerning University Organization and Procedure, Article III, Section 4. A link is provided in the Cross References section. Individuals or entities may make fair use of copyrighted ISGS material, such as reproducing a single figure or table, or using a brief text quotation, without obtaining formal permission, but in all cases the Illinois State Geological Survey must be credited as the source of the material. To reproduce ISGS information beyond the fair use standard, permission must be obtained from the ISGS Information Office, 615 East Peabody Drive, Champaign, Illinois 61820, 217-333-4747, isgs@isgs.illinois.edu. License fees and a license agreement may be required, depending on the proposed usage. Any use of these data is governed by University and campus policies, in particular, but not limited to, the Policy on Appropriate Use of Computers and Network Systems at the University of Illinois at Urbana-Champaign, the ISGS Terms of Use document available at the ISGS Web site, and the University of Illinois Web Privacy Notice. Links to these are provided in the Cross References section. Map information is to be used at a scientifically and cartographically appropriate scale, that is, at a scale no greater than indicated on the map or as described in the documentation of the map or map data. Map information is not appropriate for, and is not to be used as, a geodetic, legal, or engineering base. Map information has no legal basis in the definition of boundaries or property lines and is not intended as a substitute for surveyed locations such as can be determined by a registered Public Land Surveyor. The data do not replace the need for detailed site-specific studies.</useconst>
<datacred>Aero Metric Inc, Illinois State Geological Survey, Illinois Department of Transportation, DuPage County</datacred>
<ptcontac>
<cntinfo>
<cntorgp>
<cntorg>Illinois State Geological Survey (ISGS), a division of the Prairie Research Institute of the University of Illinois</cntorg>
</cntorgp>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>615 E. Peabody</address>
<city>Champaign</city>
<state>IL</state>
<postal>61820</postal>
<country>USA</country>
</cntaddr>
<cntvoice>217-333-4747</cntvoice>
<cntemail>info@isgs.illinois.edu</cntemail>
<hours>Monday thru Friday, 8am - 5pm</hours>
<cnttdd>217-785-0211</cnttdd>
</cntinfo>
</ptcontac>
<crossref>
<citeinfo>
<title>Policy on Appropriate Use of Computers and Network Systems at the University of Illinois at Urbana-Champaign</title>
<onlink>http://www.cam.illinois.edu/viii/VIII-1.1.htm</onlink>
</citeinfo>
</crossref>
<crossref>
<citeinfo>
<title>ISGS Terms of Use </title>
<onlink>http://www.isgs.illinois.edu </onlink>
</citeinfo>
</crossref>
<crossref>
<citeinfo>
<title>University of Illinois Web Privacy Notice </title>
<onlink>http://www.vpaa.uillinois.edu/policies/web_privacy.cfm </onlink>
</citeinfo>
</crossref>
<crossref>
<citeinfo>
<title>University Copyright Policy (stated in the General Rules Concerning University Organization and Procedure, Article III, Section 4) </title>
<onlink>http://www.uillinois.edu/trustees/rules.cfm#sec34 </onlink>
</citeinfo>
</crossref>
</idinfo>
<dataqual>
<attracc>
<attraccr>The Fundamental Vertical Accuracy (FVA) of the TIN achieved a 0.40 feet at a 95% confidence level in the "Hard Surface" land cover category. 20 control points were used in this evaluation.
Refer also to the Disclaimer of Warranties and Accuracy of Data section of the Legal Notices of Terms and Conditions section of the University of Illinois Web Privacy Policy. A link is provided in the Cross References section.</attraccr>
</attracc>
<logic>All data have had QAQC visual and statistical testing using observations performed to compare the derivative products (breaklines, classified LAS, DEM and DSM/DTM) as well as aerial photography to check for the logical consistency of the data.</logic>
<complete>
Complete
</complete>
<posacc>
<horizpa>
<horizpar>All these data products were acquired at 1150 meters above mean terrain (AMT) and have a horizontal accuracy of 1.9 feet, with a nominal point spacing of 3.6 feet.</horizpar>
<qhorizpa>
<horizpav>0.57 meters</horizpav>
</qhorizpa>
</horizpa>
<vertacc>
<vertaccr>The Fundamental Vertical Accuracy (FVA) of the TIN achieved a 0.4 at a 95% confidence level in the "Hard Surface" land cover category. 20 control points were used in this evaluation.
The Consolidated Vertical Accuracy (CVA) of the TIN achieved a 0.33 feet at a 95% confidence level according to ASPRS Guidelines, Vertical Accuracy Reporting for LiDAR for all land cover categories. 132 points covering 5 land cover categories were tested. Land Cover categories are the following: Hard Surface, Tall Grass, Brush, Woods, and Short Grass.
Supplemental Vertical Accuracy (SVA) of the TIN are shown below at a 95% confidence level, derived by the ASPRS Guidelines, Vertical Accuracy Report for LiDAR Data based on the 95th percentile error in all of the individual land cover categories. Below is the land cover categories with the achieved accuracy reported at a 95th percentile error and the number of test points.
Hard Surface 0.31ft 20
Tall Grass 0.29ft 21
Brush 0.33ft 22
Woods 0.29ft 20
Short Grass 0.22ft 21
In addition to the above tests, Aero-Metric performed additonal profiles during the week of November 23, 2009 to verify contouring error that occurred in the northwest corner of the County. A total of 277 points were collected and the 0.151 feet RMSE accuracy was achieved. The minimum difference was -0.399 feet and the maximum was 0.363 feet.</vertaccr>
<qvertpa>
<vertaccv>6.09 cm RMSEz</vertaccv>
</qvertpa>
</vertacc>
</posacc>
<lineage>
<procstep>
<procdesc>The LiDAR data was captured using AERO-METRIC's twin-engine Piper Navajo equipped with a LiDAR system. The LiDAR system includes a differential GPS unit and inertial measurement system to provide superior accuracy.
2006 Acquisition parameters: 1. Scanner - Optech ALTM 3100EA 2. Flight Height - 1150m above mean terrain 3. Swath Width - 19degrees 4. Sidelap - 50% 5. Nominal Post Spacing - 3.6 feet.
2006 GPS and IMU processing parameters: 1. Processing Programs and version - Applanix - POSGPS and POSProc, versions 4.3 2. Maximum baseline length - Not greater than 30km.
3. Number of base stations during LiDAR collection - A minimum of 2 with a maximum of 5 stations were occupied during any of the lifts to acquire the LiDAR data. The following were the occupied base stations: DP1A, DP2A, DP3A, DP4A, VODG, ZAU1, and an Aero-Metric set station "1" ) 4. Max separation between base stations during LiDAR collection - 0.05m 5. IMU processing monitored for consistency and smoothness - Yes.
2006 Point Cloud Processing: 1. Program and version - REALM Survey Suite, version 3.5.3 2. Horizontal Datum - NAD83(NSRS2007) 3. Horizontal Coordinates - Illinois State Plane Coordinates, East Zone, in US Survey Feet 4. Vertical Datum - NAVD88 5. Geoid Model used to reduce satellite derived elevations to orthometric heights - NGS Geoid03.
2008 LIDAR Processing: 1. Processing Programs and versions - TerraSolid TerraScan, TerraModeler and TerraMatch, Intergraph MicroStation, and GeoCue.
2. Point Cloud data is imported to TerraScan in a Microstation V8 (V) CAD environment on a specified 5000 feet by 5000 feet tiling scheme.
3. Analyze the data for overall compleness and consistency. This is to ensure that there are no voids in the data collection. 4. Inspect for calibration errors in the dataset using the TerraMatch software. This is accomplished by sampling the data collected accross all flight lines and classify the idividual lines to ground. The sofware will use the ground-classified lines to compute corrections (Heading, Pitch, Roll, and Scale). 5. Orientation corrections (i.e. Calibration corrections) are then applied to the entire dataset. 6. Automatic ground classification is performed using algorithms with customized parameters to best fit the project area. Several areas of varying relief and planimetric features were inspected to verify the final ground surface. 7. AERO-METRIC, INC. provided Quality Assurance and Quality Control (QAQC) data for this project. AERO-METRIC captured 132 QA/QC points in multipled land cover categories that were used to test the accuracy of the LiDAR ground surface. TerraScan's Output Control Report (OCR) was used to compare the QAQC data to the LIDAR data. This routine searches the LIDAR dataset by X &amp;amp; Y coordinate, finds the closest LIDAR point and compares the vertical (Z) values to the known data collected in the field. Based on the QAQC data, a bias adjustment was determined, and the results were applied to the LIDAR data. A final OCR was performed with a resulting RMSE of 0.175 feet. 8. Once the automatic processing and the testing of LiDAR is complete, AERO-METRIC meticulously reviews the generated bare-earth surface data to insure that proper classification was achieved as part of a Quality Control process. 9. Final deliverable are generated.
Breakline Processing:
1. GeoCue was employed to create stereomates from the LiDAR intensity information to compile breakline data as required.
2. Soft copy compilers collected breaklines for all areas except Naperville.
3. Breaklines included were the following: Road edge, Road centerline, water edge, stream, river edge, river centerline, ditches, and breaklines (sharp features other than the described features above).
Contour Processing:
1. Two foot contours were generated in Microstation from the LIDAR and breakline data.
2. Topology checks were run on the dataset to identify dangles, gaps, and self-intersecting contours. Contours were edited to fix any topology errors.
3. Contours were tied to Kane, Cook, and Will counties where possible. Polygons were placed in areas where contours did not tie between counties due to different dates of photography.
4. Contours were converted to shapefile format using ESRI ArcInfo software. The shapefiles were imported into the final geodatebase.
City of Naperville Note
The City of Naperville was previously collected by another vendor. During the tying phase of this project, it was detected that a systematic difference was evident by the vendor which prevented a successful tie. It was later decided that the County would utilze the LiDAR data that Aero-Metric collected in 2006 over the City. Breaklines were utilzed as collected by the vendor to reduce any duplication of data and only the LiDAR as collected from Aero-Metric 2006 flight was edited to ensure that the accuracy was met. Contour generation and Geodatabase inclussion was completed the same as the rest of the County.
Geodatabase Creation:
1. Planimetric and topographic data from LIDAR, breakline, and contour processing was imported into an ESRI ArcGIS version 9.3 file geodatabase. Bare earth LIDAR points were imported as a single multipoint feature class, to be incorprated into a terrain dataset, as will as individual point feature classses representing the 421 tile blocks. Breaklines were divided into eight feature classes representing different types of breaklines. Contours and spot elevation were each imported into a single feature class covering the entire project area. A terrain dataset was then built using the bare earth and breakline data. In addition to data derived directly from the Dupage County LIDAR project, tie data from the surrounding three counties (Cook, Kane, and Will) is included in the geodatabase, in separate feature datasets for each county, and a layer is included representing areas that do not successfully tie across county boundaries. The following feature datasets and underlying feature classes populate the geodatabase:
Dupage_County_IL.gdb (File Geodatabase)
Dupage_County_Features (Feature Dataset)
Bare_Earth_Points
Breaklines
Buildings
Contours
Ditches
Dupage_Boundary
Dupage_Terrain
Dupage_Terrain_Boundary
No_Tie_Areas
River_Centerlines
Rivers
Road_Centerlines
Spot_Elevations
Streams
Tile_Boundaries
Water
Dupage_County_LAS_Points (Feature Dataset)
POINTS_001
...
POINTS_421
Tie_Data_Cook_County (Feature Dataset)
Cook_County_Contours
Cook_County_Spot_Elevations
Tie_Data_Kane_County (Feature Dataset)
Kane_County_Bare_Earth_Points
Kane_County_Contours
Tie_Data_Will_County (Feature Dataset)
Will_County_Bare_Earth_Points
Will_County_Contours
Will_County_Spot_Elevations
Final Deliverables:
1. One paper copy of the LiDAR Accuracy Assessment Report.
2. One firewire hard drive containing the following data:
a. Digital copy of the LiDAR Accuracy Assessment Report
b. Tiled Bare Earth LAS data
c. One ESRI File Geodatabase (version 9.3)
d. FGDC Compliant metadata
ISGS Secondary Processing:
1. Thorough QAQC check was completed to ensure and evaluate the quality of the data delivered and that all the specifications have been met in accordance to the contract and national specifications set for LiDAR data.
2. Through ArcGIS 10.1 the following steps were completed to created Terrain and hillshade products:
a. LAS to Mulitpoint conversion using 3D analyst tools.ASPRS Classifications were used below:
1-Unclassified
2-Ground
3-Low Vegetation
4-Medium Vegetation
5-High Vegetation
6-Building
8-Model Key Points
9-Water
b. Terrains are then created and pyramids are calculated.
c. Terrain to Raster tool was used in 3D Analyst. The parameters of data type float, natural neighbors method, sampling distance is cell size and the point spaceing value from the LiDAR data.
d. Hillshades are created from the above rasters with a Z value of 2.
3. These derivatives were checked again visually for errors. If any errors were perceived corrections were coordinated with vendor and products were updated with corrections.
4. When product was finalized then metadata was completed before making data available.</procdesc>
<procdate>20091218</procdate>
</procstep>
</lineage>
<cloud>Unknown</cloud>
</dataqual>
<spdoinfo>
<direct>Raster</direct>
</spdoinfo>
<spref>
<horizsys>
<planar>
<planci>
<plance>coordinate pair</plance>
<coordrep>
<absres>0.001</absres>
<ordres>0.001</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>
<cordsysn>
<projcsn>NAD_1983_StatePlane_Illinois_East_FIPS_1201_Feet</projcsn>
</cordsysn>
</horizsys>
<vertdef>
<altsys>
<altdatum>North American Vertical Datum of 1988</altdatum>
<altres>0.01</altres>
<altunits>survey feet</altunits>
<altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
</altsys>
</vertdef>
</spref>
<metainfo>
<metd>20140923</metd>
<metc>
<cntinfo>
<cntorgp>
<cntorg>Illinois State Geological Survey (ISGS), a division of the Prairie Research Institute of the University of Illinois</cntorg>
</cntorgp>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>615 East Peabody Drive</address>
<city>Champaign</city>
<state>IL</state>
<postal>61820</postal>
<country>US</country>
</cntaddr>
<cntvoice>217-333-4747</cntvoice>
<cntemail>isgs@isgs.illinois.edu</cntemail>
<hours>Monday through Friday 8:00 AM to 5:00 PM (Central Time)</hours>
</cntinfo>
</metc>
<metstdn>
FGDC Content Standard for Digital Geospatial Metadata
</metstdn>
<metstdv>
FGDC-STD-001-1998
</metstdv>
<metac>The access constraints as stated for the data apply also to the metadata. Refer to the Access Constraints section of the Identification Information section.</metac>
<metuc>The use constraints as stated for the data apply also to the metadata. Refer to the Use Constraints section of the Identification Information section.</metuc>
</metainfo>
<Esri>
<CreaDate>20130301</CreaDate>
<CreaTime>12273000</CreaTime>
<ArcGISstyle>FGDC CSDGM Metadata</ArcGISstyle>
<SyncOnce>FALSE</SyncOnce>
<DataProperties>
<itemProps>
<itemLocation>
<linkage Sync="TRUE">file://H:\counties\dupage\dupage_dem</linkage>
<protocol Sync="TRUE">Local Area Network</protocol>
</itemLocation>
<itemName Sync="TRUE">dupage_dem</itemName>
<imsContentType Sync="TRUE">002</imsContentType>
<nativeExtBox>
<westBL Sync="TRUE">1003289.428605</westBL>
<eastBL Sync="TRUE">1098758.928605</eastBL>
<southBL Sync="TRUE">1827940.557070</southBL>
<northBL Sync="TRUE">1940738.557070</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
</itemProps>
<copyHistory>
<copy date="20130301" dest="\\ISGS-HEIGHTMOD3\C$\Lidar\SupportingFiles\FINAL_Alton_Project" source="\\TERRAIN\incoming2\alton_connector_IDOT_4th_delivery\Metadata\FINAL_Alton_Project" time="12273100"/>
</copyHistory>
<coordRef>
<type Sync="TRUE">Projected</type>
<geogcsn Sync="TRUE">GCS_North_American_1983_HARN</geogcsn>
<csUnits Sync="TRUE">Linear Unit: Foot_US (0.304801)</csUnits>
<projcsn Sync="TRUE">NAD_1983_HARN_StatePlane_Illinois_East_FIPS_1201_Feet</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.1'&gt;&lt;WKT&gt;PROJCS[&amp;quot;NAD_1983_HARN_StatePlane_Illinois_East_FIPS_1201_Feet&amp;quot;,GEOGCS[&amp;quot;GCS_North_American_1983_HARN&amp;quot;,DATUM[&amp;quot;D_North_American_1983_HARN&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],AUTHORITY[&amp;quot;EPSG&amp;quot;,3443]],VERTCS[&amp;quot;NAVD_1988&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;3443&lt;/WKID&gt;&lt;LatestWKID&gt;3443&lt;/LatestWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
</coordRef>
<RasterProperties>
<General>
<PixelDepth Sync="TRUE">32</PixelDepth>
<HasColormap Sync="TRUE">FALSE</HasColormap>
<CompressionType Sync="TRUE">RLE</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">489.07999</NoDataValue>
</General>
</RasterProperties>
</DataProperties>
<SyncDate>20140911</SyncDate>
<SyncTime>11384300</SyncTime>
<ModDate>20140911</ModDate>
<ModTime>11384300</ModTime>
</Esri>
<distinfo>
<distrib>
<cntinfo>
<cntorgp>
<cntorg>Illinois State Geological Survey (ISGS), a division of the Prairie Research Institute of the University of Illinois</cntorg>
</cntorgp>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>615 East Peabody Drive</address>
<city>Champaign</city>
<state>IL</state>
<postal>61820</postal>
<country>USA</country>
</cntaddr>
<cntvoice>217-244-2414</cntvoice>
<cntemail>isgs@isgs.illinois.edu</cntemail>
</cntinfo>
</distrib>
<distliab>Refer to the Legal Notices of Terms and Conditions of the University of Illinois Web Privacy Policy (there is a link in the Cross References section) for policy statements regarding the following:
Disclaimer of Liability
Disclaimer of Warranties and Accuracy of Data
Disclaimer of Endorsement
Disclaimer for External Links
Disclaimer of Duty to Continue Provision of Data
Security
Choice of Law
By obtaining these data you agree to the provisions of the University of Illinois Web Privacy Policy, regardless of the manner in which the information was obtained.
</distliab>
<stdorder>
<digform>
<digtinfo>
<formname>other</formname>
<filedec>no compression applied</filedec>
</digtinfo>
<digtopt>
<onlinopt>
<accinstr>http://www.isgs.uiuc.edu/nsdihome/webdocs/ilhmp/</accinstr>
<computer>
<networka>
<networkr>http://www.isgs.uiuc.edu/nsdihome/webdocs/ilhmp/</networkr>
</networka>
</computer>
<oncomp>Windows 7</oncomp>
</onlinopt>
<offoptn>
<offmedia>CD-ROM</offmedia>
<recfmt>none</recfmt>
</offoptn>
</digtopt>
</digform>
<fees>no fees</fees>
</stdorder>
<techpreq>The data are intended for use with GIS software. The ISGS uses ESRI ArcGIS software, however, ESRI formats can be imported into many different GIS software packages. It is expected that customers who obtain these data have the technical expertise to use GIS software. The ISGS does not provide software support of any kind.</techpreq>
</distinfo>
<eainfo>
<detailed>
<enttyp>
<enttypl>GRID</enttypl>
<enttypd>Raster</enttypd>
<enttypds>ISGS</enttypds>
</enttyp>
</detailed>
<overview>
<dsoverv>Raster Grid Values</dsoverv>
<eaover>Raster Grid Values</eaover>
<eadetcit>ISGS</eadetcit>
</overview>
</eainfo>
<dataIdInfo>
<envirDesc Sync="TRUE">Microsoft Windows 7 Version 6.1 (Build 7601) Service Pack 1; Esri ArcGIS 10.2.1.3497</envirDesc>
<dataLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<idCitation>
<resTitle Sync="TRUE">IL_DuPage_DEM_2006</resTitle>
<presForm>
<PresFormCd Sync="TRUE" value="005"/>
</presForm>
</idCitation>
<spatRpType>
<SpatRepTypCd Sync="TRUE" value="002"/>
</spatRpType>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<exTypeCode Sync="TRUE">1</exTypeCode>
<westBL Sync="TRUE">-88.263630</westBL>
<eastBL Sync="TRUE">-87.912094</eastBL>
<northBL Sync="TRUE">41.994898</northBL>
<southBL Sync="TRUE">41.684605</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
<idAbs/>
<idPurp/>
<idCredit/>
<resConst>
<Consts>
<useLimit/>
</Consts>
</resConst>
</dataIdInfo>
<mdLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</mdLang>
<mdChar>
<CharSetCd Sync="TRUE" value="004"/>
</mdChar>
<distInfo>
<distFormat>
<formatName Sync="TRUE">Raster Dataset</formatName>
</distFormat>
</distInfo>
<mdHrLv>
<ScopeCd Sync="TRUE" value="005"/>
</mdHrLv>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE" code="3443"/>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">8.2.6</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<spatRepInfo>
<Georect>
<cellGeo>
<CellGeoCd Sync="TRUE" value="002"/>
</cellGeo>
<numDims Sync="TRUE">2</numDims>
<tranParaAv Sync="TRUE">1</tranParaAv>
<chkPtAv Sync="TRUE">0</chkPtAv>
<cornerPts>
<pos Sync="TRUE">1003289.428605 1827940.557070</pos>
</cornerPts>
<cornerPts>
<pos Sync="TRUE">1003289.428605 1940738.557070</pos>
</cornerPts>
<cornerPts>
<pos Sync="TRUE">1098758.928605 1940738.557070</pos>
</cornerPts>
<cornerPts>
<pos Sync="TRUE">1098758.928605 1827940.557070</pos>
</cornerPts>
<centerPt>
<pos Sync="TRUE">1051024.178605 1884339.557070</pos>
</centerPt>
<axisDimension type="002">
<dimSize Sync="TRUE">27277</dimSize>
<dimResol>
<value Sync="TRUE" uom="Foot_US">3.500000</value>
</dimResol>
</axisDimension>
<axisDimension type="001">
<dimSize Sync="TRUE">32228</dimSize>
<dimResol>
<value Sync="TRUE" uom="Foot_US">3.500000</value>
</dimResol>
</axisDimension>
<ptInPixel>
<PixOrientCd Sync="TRUE" value="001"/>
</ptInPixel>
</Georect>
</spatRepInfo>
<contInfo>
<ImgDesc>
<contentTyp>
<ContentTypCd Sync="TRUE" value="003"/>
</contentTyp>
<covDim>
<Band>
<dimDescrp Sync="TRUE">dupage_dem3ft</dimDescrp>
<maxVal Sync="TRUE">970.877625</maxVal>
<minVal Sync="TRUE">490.131073</minVal>
<bitsPerVal Sync="TRUE">32</bitsPerVal>
<valUnit>
<UOM type="length"/>
</valUnit>
</Band>
</covDim>
</ImgDesc>
</contInfo>
<mdDateSt Sync="TRUE">20140911</mdDateSt>
</metadata>
