<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE metadata SYSTEM "csdgm2.dtd">
<metadata>
	<idinfo>
		<citation>
			<citeinfo>
				<origin>
					<!--The name of the organization that developed the dataset.-->
          Aero-Metric, Inc.
        </origin>
				<pubdate>
					<!--Use the date that the data was collected
Format YYYYMMDD   For example, 20020425 is April 25, 2002

Domain: "Unknown" "Unpublished material" free date-->
          20060404
        </pubdate>
				<title>DuPage County, IL LiDAR</title>
				<geoform>
          remote-sensing image
          <!--Enter the mode in which the geospatial data are represented.

Domain: (the listed domain is partially from pp. 88-91 in Anglo-American Committee on Cataloguing of Cartographic Materials, 1982, Cartographic materials: A manual of interpretation for AACR2: Chicago, American Library Association):

"atlas" "audio" "diagram" "document" "globe" "map" "model" "multimedia
presentation" "profile" "raster digital data" "remote-sensing image" "section" "spreadsheet" "tabular digital data" "vector digital data" "video" "view" free text-->
				</geoform>
			</citeinfo>
		</citation>
		<descript>
			<abstract>
				<!--Enter a brief narrative summary of the data set.

Domain: free text-->
        DuPage County, IL LiDAR
      </abstract>
			<purpose>
				<!--Enter a summary of the intentions with which the data set was developed.

Domain: free text-->
        The DuPage County Light Detection and Ranging (LIDAR) project is to provide high accuracy bare-earth processed LiDAR and a geodatabase containing bare earth points, breaklines, 2ft contours, a feature terrain dataset, and ties to adjacient counties for approximately 334 square miles.

The project utilized data acquired in 2006 to post-process and classify the LiDAR data in 2008.  The classified bare-earth data achieves the following:  nominal horizontal spacing of 3.6 feet based on the Illinois State Plane Coordinate System, East Zone, related to the North American Datum of 1983 (NSRS2007).   Vertical accuracy was to achieve a Fundamental Vertical Accuarcy at a 95% confidence level of less than 1.19 feet using the both FEMA and ASPRS category classification.

Accuracy statement is based on the area of moderate to flat terrain. Diminished accuracies are to be expected in areas in dense vegetation. The accuracy of the LiDAR data as tested met the vertical accuracy to support the contour interval of 2 feet or less standards, however, derived products may be less accurate in areas of dense vegetation due to a lesser number of points defining the bare-earth in these areas.
      </purpose>
		</descript>
		<timeperd>
			<timeinfo>
				<sngdate>
					<caldate>
						<!--Enter the year, month, and day  for which the data corresponds to the currentness reference (for these orthoimage chips, this would be the oldest photo date).

Domain: "Unknown" free date-->
            20060404
          </caldate>
				</sngdate>
			</timeinfo>
			<current>
        ground condition
        <!--Enter the basis on which the time period of content information is determined.

Domain: "ground condition" "publication date" free text-->
			</current>
		</timeperd>
		<status>
			<progress>
        Complete
        <!--Enter the state of the data set.

Domain: "Complete" "In work" "Planned"-->
			</progress>
			<update>
				<!--Enter the frequency with which changes and additions are made to the data
set after the initial data set is completed.

Domain: "Continually" "Daily" "Weekly" "Monthly" "Annually" "Unknown" "As
needed" "Irregular" "None planned" free text-->
        unknown
      </update>
		</status>
		<spdom>
			<bounding>
				<westbc>
					<!--Enter western-most coordinate of the limit of coverage expressed in longitude (decimal degrees).

Domain: -180.0 <= West Bounding Coordinate < 180.0-->
          -88.2597339225
        </westbc>
				<eastbc>
					<!--Enter eastern-most coordinate of the limit of coverage expressed in longitude (decimal degrees).

Domain: -180.0 <= East Bounding Coordinate <= 180.0-->
          -87.9182261179
        </eastbc>
				<northbc>
					<!--Enter northern-most coordinate of the limit of coverage expressed in latitude (decimal degrees).

Domain: -90.0 <= North Bounding Coordinate <= 90.0;
North Bounding Coordinate >= South Bounding Coordinate-->
          41.9967349365
        </northbc>
				<southbc>
					<!--Enter southern-most coordinate of the limit of coverage expressed in latitude (decimal degrees).

Domain: -90.0 <= South Bounding Coordinate <= 90.0;
South Bounding Coordinate <= North Bounding Coordinate
-->
          41.7271988659
        </southbc>
			</bounding>
		</spdom>
		<keywords>
			<theme>
				<themekt>
          None
          <!--Reference a formally registered thesaurus or similar authoritative source for theme keywords.-->
				</themekt>
				<themekey>
					<!--A common-use word or phrase used to describe the subject of the data set.

Domain: free text-->
          Light Detection and Ranging
        </themekey>
				<themekey>
					<!--A common-use word or phrase used to describe the subject of the data set.

Domain: free text-->
          LIDAR
        </themekey>
				<themekey>
					<!--A common-use word or phrase used to describe the subject of the data set.

Domain: free text-->
          Bare Earth
        </themekey>
				<themekey>
					<!--A common-use word or phrase used to describe the subject of the data set.

Domain: free text-->
          Point Cloud
        </themekey>
				<themekey>
					<!--A common-use word or phrase used to describe the subject of the data set.

Domain: free text-->
          Geodatabase
        </themekey>
			</theme>
			<place>
				<placekt>
					<!--Reference to a formally registered thesaurus or a similar authoritative source of place keywords.

Domain: "None" "Geographic Names Information System" free text-->
          None
        </placekt>
				<placekey>
          US
          <!--Enter the geographic name of a location covered by a data set.

Domain: free text-->
				</placekey>
				<placekey>
					<!--Enter the geographic name of a location covered by a data set.

Domain: free text-->
          Illinois
        </placekey>
				<placekey>
					<!--Enter the geographic name of a location covered by a data set.

Domain: free text-->
          County
        </placekey>
				<placekey>
					<!--Enter the geographic name of a location covered by a data set.

Domain: free text-->
          DuPage
        </placekey>
			</place>
		</keywords>
		<accconst>
			<!--Enter restrictions and legal prerequisites for accessing the data set. These include any access constraints applied to assure the protection of privacy or intellectual property, and any special restrictions or limitations on obtaining the data set.

Domain: "None" free text-->
      None
    </accconst>
		<useconst>
			<!--Enter restrictions and legal prerequisites for using the data set after access is granted. These include any use constraints applied to assure the protection of privacy or intellectual property, and any special
restrictions or limitations on using the data set.

Domain: "None" free text-->
      None.
    </useconst>
		<datacred>
			<!--Recognition of those who contributed to the data set. Contractor may enter company name of primary contractor.

Domain: free text-->
      Aero-Metric, Inc.
    </datacred>
	</idinfo>
	<dataqual>
		<attracc>
			<attraccr>
				<!--Contractor should enter description of photographic quality control.-->
        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.
      </attraccr>
		</attracc>
		<logic>None</logic>
		<complete>
			<!--Describe any specific void areas in the dataset.-->
      Complete
    </complete>
		<posacc>
			<horizpa>
				<horizpar>
					<!--An explanation of the accuracy of the horizontal coordinate measurements and a description of the tests used. This must be entered by the contractor to reflect their methods. This is provided only as a sample of the type of information needed. "Tested" can only be used when data testing is performed against independent checkpoints from a source of higher accuracy.

Domain: free text-->
          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>
			</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>
			</vertacc>
		</posacc>
		<lineage>
			<procstep>
				<procdesc>
					<!--Describe the process used to create the dataset.-->
          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; 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
        </procdesc>
				<procdate>
					<!--The date (year and month or year, month, and day) that the LiDAR data was produced; format  yyyymm, or yyyymmdd-->
          20091218
        </procdate>
			</procstep>
		</lineage>
		<cloud>Unknown</cloud>
	</dataqual>
	<spdoinfo>
		<direct>Point</direct>
	</spdoinfo>
	<spref>
		<horizsys>
			<planar>
				<gridsys>
					<gridsysn>State Plane Coordinate System</gridsysn>
					<spcs>
						<spcszone>
							<!--Enter identifier for the SPCS zone.

Domain: Four-digit numeric codes for the State Plane Coordinate Systems based on the North
American Datum of 1927 are found in Department of Commerce, 1986, Representation of
geographic point locations for information interchange (Federal Information Processing Standard
70-1): Washington: Department of Commerce, National Institute of Standards and Technology.
Codes for the State Plane Coordinate Systems based on the North American Datum of 1983 are
found in Department of Commerce, 1989 (January), State Plane Coordinate System of 1983
(National Oceanic and Atmospheric Administration Manual NOS NGS 5): Silver Spring, Maryland,
National Oceanic and Atmospheric Administration, National Ocean Service, Coast and Geodetic
Survey.-->
              1201
            </spcszone>
						<transmer>
							<sfctrmer>
								<!--Enter a multiplier for reducing a distance obtained from a map by computation or scaling to the actual distance along the central meridian.

Domain: Scale Factor at Central Meridian > 0.0-->
                0.99999166666
              </sfctrmer>
							<longcm>
								<!--Enter the line of longitude at the center of a map projection generally used as the basis for constructing the projection.
Type: real
Domain: -180.0 <= Longitude of Central Meridian < 180.0-->
                -88.333333333333
              </longcm>
							<latprjo>
								<!--Enter latitude chosen as the origin of rectangular coordinates for a map projection.

Domain: -90.0 <= Latitude of Projection Origin <= 90.0-->
                36.6666666666666666
              </latprjo>
							<feast>
								<!--Enter the value added to all "x" values in the rectangular coordinates for a map projection. This value frequently is assigned to eliminate negative numbers. Expressed in the unit of measure identified in Planar Coordinate Units.

Domain: free real-->
                300000
              </feast>
							<fnorth>
								<!--Enter the value added to all "y" values in the rectangular coordinates for a map projection. This value frequently is assigned to eliminate negative numbers. Expressed in the unit of measure identified in Planar Coordinate Units.

Domain: free real-->
                0
              </fnorth>
						</transmer>
					</spcs>
				</gridsys>
				<planci>
					<plance>
						<!--Enter the means used to represent horizontal positions.

Domain: "coordinate pair" "distance and bearing" "row and column"-->
            coordinate pair
          </plance>
					<coordrep>
						<absres>
							<!--Enter the (nominal) minimum distance between the "x" or column values of two adjacent points, expressed in Planar Distance Units of measure.

Domain: Abscissa Resolution > 0.0-->
              0.01
            </absres>
						<ordres>
							<!--Enter the (nominal) minimum distance between the "y" or row values of two adjacent points, expressed in Planar Distance Units of measure.

Domain: Ordinate Resolution > 0.0-->
              0.01
            </ordres>
					</coordrep>
					<plandu>
						<!--Enter units of measure used for distances.

Domain: "meters" "international feet" "survey feet" free text-->
            survey feet
          </plandu>
				</planci>
			</planar>
			<geodetic>
				<horizdn>
					<!--Enter the identification given to the reference system used for defining the coordinates of points.

Domain: "North American Datum of 1927" "North American Datum of 1983" free text-->
          North American Datum of 1983 (NSRS 2007)
        </horizdn>
				<ellips>
          Geodetic Reference System 80
          <!--Enter identification given to established representations of the Earth's shape.

Domain: "Clarke 1866" "Geodetic Reference System 80" free text-->
				</ellips>
				<semiaxis>
					<!--Enter radius of the equatorial axis of the ellipsoid.

Domain: Semi-major Axis > 0.0-->
          6378137.000000
        </semiaxis>
				<denflat>
					<!--Enter the denominator of the ratio of the difference between the equatorial and polar radii of the ellipsoid when the numerator is set to 1.

Domain: Denominator of Flattening > 0.0-->
          298.257222
        </denflat>
			</geodetic>
		</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>
			<!--Enter the date that the metadata were created or last updated.

Domain: free date-->
      20091218
    </metd>
		<metc>
			<cntinfo>
				<cntorgp>
					<cntorg>
						<!--Enter the name of the organization to which the contact type applies.

Domain: free text-->
            Aero-Metric, Inc.
          </cntorg>
				</cntorgp>
				<cntaddr>
					<addrtype>
						<!--Enter the information provided by the address.

Domain: "mailing" "physical" "mailing and physical", free text-->
            Mailing and physical address
          </addrtype>
					<address>
						<!--Enter an address line for the address. Enter contractor's mailing address here.

Domain: free text-->
            4020 Technology Parkway
          </address>
					<city>
						<!--Enter name of the city where the contractor is located.-->
            Sheboygan
          </city>
					<state>
						<!--Enter the name of the State in which the contractor is located.-->
            WI
          </state>
					<postal>
						<!--Enter the zip code for the address above.-->
            53083
          </postal>
					<country>US</country>
				</cntaddr>
				<cntvoice>
					<!--Enter the telephone number for the POC for this dataset.-->
          1-920-457-3631
        </cntvoice>
				<cntfax>1-920-457-0410</cntfax>
				<hours>Monday through Friday 8:00 AM to 5:00 PM (Central Time)</hours>
			</cntinfo>
		</metc>
		<metstdn>
      FGDC Content Standard for Digital Geospatial Metadata
      <!--Enter the name of the metadata standard used to document the data set.

Domain: "FGDC Content Standard for Digital Geospatial Metadata" free text-->
		</metstdn>
		<metstdv>
      FGDC-STD-001-1998
      <!--Enter identification of the version of the metadata standard used to document the data set.

Domain: free text-->
		</metstdv>
	</metainfo>
	<Esri><MetaID>{A3619B99-F802-4506-B0FA-3BC8628EF604}</MetaID><CreaDate>20091219</CreaDate><CreaTime>09072500</CreaTime><SyncOnce>TRUE</SyncOnce><ModDate>20091219</ModDate><ModTime>09085900</ModTime></Esri><mdDateSt Sync="TRUE">20091219</mdDateSt></metadata>
