<?xml version="1.0" encoding="ISO-8859-1"?>
<metadata>
	<idinfo>
		<citation>
			<citeinfo>
				<origin>State of Michigan (SOM)</origin>
				<pubdate>2015</pubdate>
				<title>South Michigan - Allegan LiDAR - Michigan 2015</title>
				<edition>1.0</edition>
				<geoform>raster digital data</geoform>
				<pubinfo>
					<pubplace>Michigan</pubplace>
					<publish>State of Michigan</publish>
				</pubinfo>
				<onlink>http://www.michigan.gov</onlink>
			</citeinfo>
		</citation>
		<descript>
			<abstract>This metadata record describes all LiDAR derived products for the 2015 Michigan LiDAR project covering approximately 842 square miles, in which its extents cover Allegan County.</abstract>
			<lidar>
				<ldrinfo>
					<ldrspec>FEMA Specification QL2 meeting 18.13cm FVA</ldrspec>
					<ldrsens>Leica ALS70</ldrsens>
					<ldrmaxnr>4</ldrmaxnr>
					<ldrnps>0.65</ldrnps>
					<ldrdens>1.67</ldrdens>
					<ldradens>2.2</ldradens>
					<ldranps>0.71</ldranps>
					<ldrfltht>2250</ldrfltht>
					<ldrfltsp>135</ldrfltsp>
					<ldrscana>32</ldrscana>
					<ldrscanr>64</ldrscanr>
					<ldrpulsr>167</ldrpulsr>
					<ldrpulsd>10</ldrpulsd>
					<ldrpulsw>3</ldrpulsw>
					<ldrwavel>1064</ldrwavel>
					<ldrmpia>1</ldrmpia>
					<ldrbmdiv>0.3</ldrbmdiv>
					<ldrswatw>1222</ldrswatw>
					<ldrswato>30</ldrswato>
					<ldrcrs>NAD_1983_2011_State_Plane_Michigan_South_2113_Ft_Intl</ldrcrs>
					<ldrgeoid>NGS Geoid12a</ldrgeoid>
				</ldrinfo>
				<ldraccur>
					<ldrchacc>1.0</ldrchacc>
					<rawfva>0.161</rawfva>
					<clsfva>0.131</clsfva>
					<clscva>0.192</clscva>
					<clssvas>
						<svalctyp>Urban</svalctyp>
						<svavalue>0.159</svavalue>
					</clssvas>
					<clssvas>
						<svalctyp>LowVeg</svalctyp>
						<svavalue>0.215</svavalue>
					</clssvas>
					<clssvas>
						<svalctyp>MedVeg</svalctyp>
						<svavalue>0.192</svavalue>
					</clssvas>
					<clssvas>
						<svalctyp>HighVeg</svalctyp>
						<svavalue>0.196</svavalue>
					</clssvas>
				</ldraccur>
				<lasinfo>
					<lasver>1.2</lasver>
					<lasprf>1</lasprf>
					<laswheld>Withheld (ignore) points were identified in these files using class 10.</laswheld>
					<lasolap>Swath "overage" points were identified in these files by classifying to class 11.</lasolap>
					<lasintr>10</lasintr>
					<lasclass>
						<clascode>1</clascode>
						<clasitem>Unclassified</clasitem>
					</lasclass>
					<lasclass>
						<clascode>2</clascode>
						<clasitem>Bare-earth</clasitem>
					</lasclass>
					<lasclass>
						<clascode>7</clascode>
						<clasitem>All noise</clasitem>
					</lasclass>
					<lasclass>
						<clascode>9</clascode>
						<clasitem>Water</clasitem>
					</lasclass>
					<lasclass>
						<clascode>10</clascode>
						<clasitem>Ignored Ground (Breakline Proximity)</clasitem>
					</lasclass>
					<lasclass>
						<clascode>11</clascode>
						<clasitem>Withheld (overlap)</clasitem>
					</lasclass>
				</lasinfo>
			</lidar>
			<purpose>To acquire detailed surface elevation data for use in conservation planning, design, research, floodplain mapping, dam safety assessments, and hydrologic modeling. LAS and bare earth DEM data products are suitable for 1 foot contour generation.  USGS LiDAR Base Specification 1.0, QL2. 18.13 cm FVA.</purpose>
			<supplinf>Project Projection, Datums and Units.  Projection - State Plane Michigan South.  Horizontal datum - North American Datum of 1983 (NAD83 (2011)).  Vertical datum - North American Vertical Datum of 1988 (NAVD88) using the latest geoid (Geoid12a) for converting ellipsoidal heights to orthometric heights.  Units - intl feet</supplinf>
			<langdata>en</langdata></descript>
		<timeperd>
			<timeinfo>
				<rngdates><begdate>20141210</begdate><enddate>20141223</enddate></rngdates></timeinfo>
			<current>ground condition</current>
		</timeperd>
		<status>
			<progress>Complete</progress>
			<update>Unknown</update>
		</status>
		<spdom>
			<bounding>
				<westbc>-86.272384</westbc>
				<eastbc>-85.543668</eastbc>
				<northbc>42.765409</northbc>
				<southbc>42.417596</southbc>
			</bounding>
			<lbounding>
				<leftbc>770000</leftbc>
				<rightbc>805000</rightbc>
				<topbc>4220000</topbc>
				<bottombc>4141400</bottombc>
			</lbounding>
		</spdom>
		<keywords>
			<theme>
				<themekt>MI</themekt>
				<themekey>LiDAR</themekey>
				<themekey>mapping</themekey>
				<themekey>point cloud</themekey>
				<themekey>Ground points</themekey>
				<themekey>Unclassified points</themekey>
				<themekey>Water points</themekey>
				<themekey>Overlap points</themekey>
				<themekey>ALS70</themekey>
				<themekey>Intensity return</themekey>
				<themekey>LAS</themekey>
				<themekey>Digital Elevation Model (DEM)</themekey>
				<themekey>Digital Terrain Model (DTM)</themekey>
				<themekey>Digital Surface Model (DSM)</themekey>
				<themekey>IMG</themekey>
				<themekey>Grid</themekey>
				<themekey>Bare Earth</themekey>
				<themekey>First Return</themekey>
				<themekey>Contour</themekey>
			</theme>
			<place>
				<placekt>MI</placekt>
				<placekey>Michigan</placekey>
				<placekey>Allegan</placekey>
				<placekey>United States</placekey></place>
			<temporal>
				<tempkt>none</tempkt>
				<tempkey>2015</tempkey>
			</temporal>
		</keywords>
		<accconst>This data may be used by the requested party for stated purposes and should not be re-distributed.</accconst>
		<useconst>This data is for planning purposes only and should not be used for legal or cadastral purposes. Any conclusions drawn from analysis of this information are not the responsibility of Sanborn Map Company. Users should be aware that temporal changes may have occurred since this dataset was collected and some parts of this dataset may no longer represent actual surface conditions. Users should not use these data for critical applications without a full awareness of its limitations.

Contact:
State of Michigan</useconst>
		<ptcontac>
			<cntinfo>
				<cntperp>
					<cntper>Everett Root</cntper>
					<cntorg>State of Michigan</cntorg>
				</cntperp>
				<cntpos>Manager, Geodata Services Section</cntpos>
				<cntaddr>
					<addrtype>mailing address</addrtype>
					<address>111 S. Capitol Ave</address>
					<city>Lansing</city>
					<state>MI</state>
					<postal>48933</postal>
					<country>U.S.A.</country>
					<address>10th Floor Romney</address></cntaddr>
				<cntvoice>517-335-7180</cntvoice>
				<cntemail>roote@michigan.gov</cntemail>
				<hours>8:00 AM - 5:00 PM</hours>
			</cntinfo>
		</ptcontac>
		<native>Microsoft Windows 7; ESRI ArcCatalog 9.3.1.1850</native>
		<secinfo><secsys>unknown</secsys><secclass>Unclassified</secclass><sechandl>unknown</sechandl></secinfo><natvform>DEM, LAS, GDB, TIF</natvform></idinfo>
	<dataqual>
		<attracc>
			<attraccr>Allegan County (Area 5):

The LiDAR surface was evaluated using a collection of 31 GPS surveyed checkpoints for the FVA report. The DEM was compared to this checkpoint class yielding a better result than was required for the project. 

Allegan County FVA Control Accuracy Report (feet)

      --------- Report Disclaimer ---------

      This report does not guarantee accuracy. The report only reflects one statistical representation of the control points, LIDAR data and surface used. This report does not replace a through quality control process.

      --------- Report Summary ---------
Average dz       	0.079
Minimum dz       	-0.409
Maximum dz       	0.728
Average magnitude	0.204
Root mean square 	0.270
Std deviation    	0.263

----------------------------------------------------------------------------------------

Attribute accuracy is tested after the LiDAR processing stage.  After classification of the LiDAR data, DEMs are created using the bare earth points. The FVA, SVA, and CVA reports are generated from the comparison of the DEM and the ground control collected within the project area.

The DEM surface was evaluated using a collection of 38 GPS surveyed checkpoints for the FVA report. The DEM was compared to this checkpoint class yielding much better result than was required for the project. 

Allegan County FVA Control Accuracy Report (feet)

      --------- Report Disclaimer ---------

      This report does not guarantee accuracy. The report only reflects one statistical representation of the control points, LIDAR data and surface used. This report does not replace a through quality control process.

      --------- Report Summary ---------
Average dz       	-0.015
Minimum dz       	-0.443
Maximum dz       	0.564
Average magnitude	0.165
Root mean square 	0.219
Std deviation    	0.221

----------------------------------------------------------------------------------------

Attribute accuracy is tested after the LiDAR processing stage.  After classification of the LiDAR data, DEMs are created using the bare earth points. The SVA report is generated from the comparison of the DEM and the ground control collected within the project area. This report includes the SVA classes of Urban.

The DEM was evaluated using a collection of 36 GPS surveyed checkpoints. The DEM was compared to this checkpoint class yielding much better result than was required for the project. 

Allegan County SVA Control Accuracy Report (feet)

      --------- Report Disclaimer ---------

      This report does not guarantee accuracy. The report only reflects one statistical representation of the control points, LIDAR data and surface used. This report does not replace a through quality control process.

      --------- Report Summary ---------
Average dz       	-0.026
Minimum dz       	-0.682
Maximum dz       	0.654
Average magnitude	0.203
Root mean square 	0.264
Std deviation    	0.266

----------------------------------------------------------------------------------------

Attribute accuracy is tested after the LiDAR processing stage.  After classification of the LiDAR data, DEMs are created using the bare earth points. The SVA report is generated from the comparison of the DEM and the ground control collected within the project area. This report includes the SVA classes of Low Veg.

The DEM was evaluated using a collection of 17 GPS surveyed checkpoints. The DEM was compared to this checkpoint class yielding much better result than was required for the project. 

Allegan County SVA Control Accuracy Report (feet)

      --------- Report Disclaimer ---------

      This report does not guarantee accuracy. The report only reflects one statistical representation of the control points, LIDAR data and surface used. This report does not replace a through quality control process.

      --------- Report Summary ---------
Average dz       	0.159
Minimum dz       	-0.385
Maximum dz       	0.926
Average magnitude	0.278
Root mean square 	0.354
Std deviation    	0.326

----------------------------------------------------------------------------------------

Attribute accuracy is tested after the LiDAR processing stage.  After classification of the LiDAR data, DEMs are created using the bare earth points. The SVA report is generated from the comparison of the DEM and the ground control collected within the project area. This report includes the SVA classes of Medium Veg.

The DEM was evaluated using a collection of 27 GPS surveyed checkpoints. The DEM was compared to this checkpoint class yielding much better result than was required for the project. 

Allegan County SVA Control Accuracy Report (feet)

      --------- Report Disclaimer ---------

      This report does not guarantee accuracy. The report only reflects one statistical representation of the control points, LIDAR data and surface used. This report does not replace a through quality control process.

      --------- Report Summary ---------
Average dz       	0.165
Minimum dz       	-0.633
Maximum dz       	0.674
Average magnitude	0.321
Root mean square 	0.381
Std deviation    	0.350

----------------------------------------------------------------------------------------
Attribute accuracy is tested after the LiDAR processing stage.  After classification of the LiDAR data, DEMs are created using the bare earth points. The SVA report is generated from the comparison of the DEM and the ground control collected within the project area. This report includes the SVA classes of High Veg.

The DEM was evaluated using a collection of 37 GPS surveyed checkpoints. The DEM was compared to this checkpoint class yielding much better result than was required for the project. 

Allegan County SVA Control Accuracy Report (feet)

      --------- Report Disclaimer ---------

      This report does not guarantee accuracy. The report only reflects one statistical representation of the control points, LIDAR data and surface used. This report does not replace a through quality control process.

      --------- Report Summary ---------
Average dz       	0.068
Minimum dz       	-0.479
Maximum dz       	0.825
Average magnitude	0.246
Root mean square 	0.323
Std deviation    	0.320

----------------------------------------------------------------------------------------

Attribute accuracy is tested after the LiDAR processing stage.  After classification of the LiDAR data, DEMs are created using the bare earth points. The CVA report is generated from the comparison of the DEM and the ground control collected within the project area.

The DEM was evaluated using a collection of 155 GPS surveyed checkpoints. The DEM was compared to all checkpoint classes yielding much better result than was required for the project. 

Allegan County CVA Control Accuracy Report (feet)

      --------- Report Disclaimer ---------

      This report does not guarantee accuracy. The report only reflects one statistical representation of the control points, LIDAR data and surface used. This report does not replace a through quality control process.

      --------- Report Summary ---------
Average dz       	0.053
Minimum dz       	-0.682
Maximum dz       	0.926
Average magnitude	0.233
Root mean square 	0.303
Std deviation    	0.299</attraccr>
		</attracc>
		<logic>LiDAR data is collected within the project area and processed. After all of the deliverables were created, the dataset was verified against control.  Control was collected in 5 areas.  Area 5 includes Allegan, Berrien, and Van Buren.  Accuracy results are reported for Area 5.</logic>
		<complete>LiDAR data is collected for the project area.  Post processing of the simultaneously acquired GPS/INS is performed and applied to the laser returns to output a point cloud in the specified project coordinate system and datums.  The point cloud data is then subjected to automated classification routines to assign all points in the point cloud to ground, water, overlap and unclassified point classes.  Anomalous laser returns that occur infrequently are removed entirely from the data set.  Once clean bare earth points are established, all products are created.. The products are then compared to the survey checkpoints. These accuracies must pass the Fundamental Vertical Accuracy, Supplemental Vertical Accuracy, and Consolidated Vertical Accuracy specifications.</complete>
		<posacc>
			<horizpa>
				<horizpar>Horizontal positional accuracy for Allegan LiDAR is dependent upon the quality of the GPS/INS solution, sensor calibration and ground conditions at the time of data capture.  The standard system results for horizontal accuracy meet or exceed the project specified 1.0 meter RMSE.</horizpar>
				<qhorizpa>
					<horizpav>1.0</horizpav>
					<horizpae>Allegan County, this value is computed by comparing ground control to a DEM derived from the classified LiDAR data and represents the RMSE of residuals on controls within the project area.</horizpae>
				</qhorizpa>
			</horizpa>
			<vertacc>
				<vertaccr>For the DEM data derived from the classified point cloud, the FVA, SVA, and CVA were computed. The vertical accuracy was tested with independent survey check points located in various terrain types within Allegan County. These check points were not used in the calibration or post processing of the lidar point cloud data. The survey check points were distributed throughout the block area. Specifications for this project require that the FVA be 9.25 cm  (18.13 cm or better @ 95 percent confidence level).</vertaccr>
				<qvertpa>
					<vertaccv>0.067m RMSE, or 0.131m FVA @ 95 percent Confidence Interval</vertaccv>
					<vertacce>The FVA was tested using 38 independent survey check points located in flat terrain types within Area 5. The survey checkpoints were distributed throughout the block area. The 38 independent check points were surveyed using static GPS base stations collecting point location for 20 minute intervals. Elevations were measured for the x,y,z location of each check point. Elevations interpolated from the DEM surface were then compared to the elevation values of the surveyed control. The RMSE was computed to be 0.067 m. AccuracyZ has been tested to meet 9.25 cm Fundamental Vertical Accuracy at 95 Percent 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.</vertacce>
				</qvertpa>
				<qvertpa><vertaccv>0.092m RMSE, or 0.192m CVA @ 95th Percentile using all FVA and SVA class checkpoints (CVA)</vertaccv><vertacce>The CVA was tested using 155 independent survey check points located in various terrain types within Area 5. The survey checkpoints were distributed throughout the block area. The 155 independent check points contained all FVA and SVA class points and were surveyed using static GPS base stations collecting point location for 20 minute intervals. Elevations were measured for the x,y,z location of each check point. Elevations interpolated from the DEM surface were then compared to the elevation values of the surveyed control. The RMSE was computed to be 0.092m, or 0.192m @ 95th Percentile defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASRPS Guidelines.</vertacce></qvertpa><qvertpa><vertaccv>0.080m RMSE, or 0.159m SVA @ 95th Percentile</vertaccv><vertacce>The SVA for the Urban class was tested using 36 independent survey check points located in urban terrain types within Area 5. The survey checkpoints were distributed throughout the block area. The 36 independent check points were surveyed using static GPS base stations collecting point location for 20 minute intervals. Elevations were measured for the x,y,z location of each check point. Elevations interpolated from the DEM surface were then compared to the elevation values of the surveyed control. The RMSE was computed to be 0.080m, or 0.159m @ 95th Percentile defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASRPS Guidelines.</vertacce></qvertpa><qvertpa><vertaccv>0.108m RMSE, or 0.215m SVA @ 95th Percentile</vertaccv><vertacce>The SVA for the Low Veg class was tested using 17 independent survey check points located in low vegetation terrain types within Area 5. The survey checkpoints were distributed throughout the block area. The 17 independent check points were surveyed using static GPS base stations collecting point location for 20 minute intervals. Elevations were measured for the x,y,z location of each check point. Elevations interpolated from the DEM surface were then compared to the elevation values of the surveyed control. The RMSE was computed to be 0.108m, or 0.215m @ 95th Percentile defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASRPS Guidelines.</vertacce></qvertpa><qvertpa><vertaccv>0.116m RMSE, or 0.192m SVA @ 95th Percentile</vertaccv><vertacce>The SVA for the Medium Veg class was tested using 27 independent survey check points located in medium vegetation terrain types within Area 5. The survey checkpoints were distributed throughout the block area. The 27 independent check points were surveyed using static GPS base stations collecting point location for 20 minute intervals. Elevations were measured for the x,y,z location of each check point. Elevations interpolated from the DEM surface were then compared to the elevation values of the surveyed control. The RMSE was computed to be 0.116m, or 0.192m @ 95th Percentile defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASRPS Guidelines.</vertacce></qvertpa><qvertpa><vertaccv>0.098m RMSE, or 0.196m SVA @ 95th Percentile</vertaccv><vertacce>The SVA for the High Veg class was tested using 37 independent survey check points located in high vegetation terrain types within Area 5. The survey checkpoints were distributed throughout the block area. The 37 independent check points were surveyed using static GPS base stations collecting point location for 20 minute intervals. Elevations were measured for the x,y,z location of each check point. Elevations interpolated from the DEM surface were then compared to the elevation values of the surveyed control. The RMSE was computed to be 0.098m, or 0.196m @ 95th Percentile defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASRPS Guidelines.</vertacce></qvertpa></vertacc>
		</posacc>
		<lineage>
			<srcinfo>
				<srccite>
					<citeinfo>
						<origin>Sanborn Map Company Inc.</origin>
						<pubdate>Unpublished Material</pubdate>
						<title>LiDAR Data</title>
						<edition>1.0</edition>
						<geoform>Remote sensing image</geoform>
						<pubinfo>
							<pubplace>None</pubplace>
							<publish>None</publish>
						</pubinfo>
					</citeinfo>
				</srccite>
				<typesrc>disc</typesrc>
				<srctime>
					<timeinfo>
						<sngdate><caldate>2015</caldate></sngdate></timeinfo>
					<srccurr>ground condition</srccurr>
				</srctime>
				<srccitea>LIDAR and GPS_RAW</srccitea>
				<srccontr>Aerial LiDAR and GPS/IMU data are recorded for the defined project area at an altitude, flight speed, scanner swath width and scanner pulse frequency to achieve the design goals of the project.</srccontr>
			</srcinfo>
			<srcinfo>
				<srccite>
					<citeinfo>
						<origin>Sanborn Map Company Inc.</origin>
						<pubdate>2010</pubdate>
						<title>Ground control</title>
						<edition>1.0</edition>
						<geoform>tabular digital data</geoform>
						<pubinfo>
							<pubplace>None</pubplace>
							<publish>None</publish>
						</pubinfo>
					</citeinfo>
				</srccite>
				<typesrc>disc</typesrc>
				<srctime>
					<timeinfo>
						<sngdate>
							<caldate>2015</caldate>
						</sngdate>
					</timeinfo>
					<srccurr>Ground condition</srccurr>
				</srctime>
				<srccitea>CONT</srccitea>
				<srccontr>Targeted ground control is used to create a digital control file and control report as well as QC check of LiDAR accuracy.  Predefined points (NGS when available) within the project area are targeted.</srccontr>
			</srcinfo>
			<srcinfo>
				<srccite>
					<citeinfo>
						<origin>Sanborn Map Company Inc.</origin>
						<pubdate>Unpublished material</pubdate>
						<title>Post processed GPS/INS</title>
						<edition>1.0</edition>
						<geoform>Tabular digital data</geoform>
					</citeinfo>
				</srccite>
				<srcscale>1200</srcscale>
				<typesrc>disk</typesrc>
				<srctime>
					<timeinfo>
						<sngdate>
							<caldate>2015</caldate>
						</sngdate>
					</timeinfo>
					<srccurr>Ground condition</srccurr>
				</srctime>
				<srccitea>GPS</srccitea>
				<srccontr>Post processed GPS/INS is applied to the lidar point data to georeference each point in the project coordinate system</srccontr>
			</srcinfo>
			<srcinfo>
				<srccite>
					<citeinfo>
						<origin>Sanborn Map Company Inc.</origin>
						<pubdate>Unpublished material</pubdate>
						<title>Post processed lidar</title>
						<edition>1.0</edition>
						<geoform>Point digital data</geoform>
					</citeinfo>
				</srccite>
				<srcscale>1200</srcscale>
				<typesrc>Disk</typesrc>
				<srctime>
					<timeinfo>
						<sngdate>
							<caldate>2015</caldate>
						</sngdate>
					</timeinfo>
					<srccurr>ground condition</srccurr>
				</srctime>
				<srccitea>LAS</srccitea>
				<srccontr>The post processed lidar data has been projected and oriented in the specified coordinate system as an un-classified point cloud.</srccontr>
			</srcinfo>
			<srcinfo>
				<srccite>
					<citeinfo>
						<origin>Sanborn Map Company Inc.</origin>
						<pubdate>Unpublished material</pubdate>
						<title>Classified lidar</title>
						<edition>1.0</edition>
						<geoform>Point digital data</geoform>
					</citeinfo>
				</srccite>
				<srcscale>1200</srcscale>
				<typesrc>disk</typesrc>
				<srctime>
					<timeinfo>
						<sngdate>
							<caldate>2015</caldate>
						</sngdate>
					</timeinfo>
					<srccurr>ground condition</srccurr>
				</srctime>
				<srccitea>LAS</srccitea>
				<srccontr>The classified lidar point cloud is used to derive various data products such as, but not limited to, bare earth gridded DEM, triangulated irregular networks (TIN), contours, digital surface models (DSM).  The output format is fully compliant LAS v1.2 or v1.3, Point Record Format 1</srccontr>
			</srcinfo>
			<srcinfo>
				<srccite>
					<citeinfo>
						<origin>State of Michigan</origin>
						<pubdate>Unpublished Material</pubdate>
						<title>Tile Definition</title>
						<edition>1.0</edition>
						<geoform>raster digital data</geoform>
					</citeinfo>
				</srccite>
				<srcscale>1200</srcscale>
				<typesrc>disk</typesrc>
				<srctime>
					<timeinfo>
						<sngdate>
							<caldate>2015</caldate>
						</sngdate>
					</timeinfo>
					<srccurr>ground condition</srccurr>
				</srctime>
				<srccitea>TLDEF</srccitea>
				<srccontr>The tile definition defines discreet non-overlapping rectangular areas used as cut lines to break up the large classified lidar dataset into smaller, more manageable data tiles.  Each tile is 2500ft by 2500ft in dimension.</srccontr>
			</srcinfo>
			<procstep>
				<procdesc>At selected locations throughout the site, accurate GPS coordinates and elevations are surveyed and the points are marked with targets.</procdesc>
				<srcused>None</srcused>
				<procdate>2015</procdate>
				<srcprod>CONT</srcprod>
			</procstep>
			<procstep>
				<procdesc>New LiDAR data is captured for the project area using a Leica ALS80 w/MPiA LiDAR instrument an integrated IPAS20 GPS/INS system mounted within a Aero Commander twin engine airplane.</procdesc>
				<srcused>None</srcused>
				<procdate>2015</procdate>
				<srcprod>LIDAR, GPS_RAW</srcprod>
			</procstep>
			<procstep>
				<procdesc>The airborne GPS data is post-processed in Intertial Explorer software and LEICA CloudPro software to determine the LiDAR sensor's angle and orientation in the terrain (project) coordinate system and datums during the survey.</procdesc>
				<srcused>GPS_RAW</srcused>
				<procdate>2015</procdate>
				<srcprod>GPS_SOL</srcprod>
			</procstep>
			<procstep>
				<procdesc>The post processed GPS/INS solution is applied to the raw lidar data to orient and project the data points into the project area reference system as an unclassified point cloud.</procdesc>
				<srcused>LIDAR, GPS_SOL</srcused>
				<procdate>2015</procdate>
				<srcprod>LAS</srcprod>
			</procstep>
			<procstep>
				<procdesc>The georeferenced lidar data is then classified and edited in Terrasolid Terrascan software.  Data is classified to produce:  Class 1:  unclassified,  Class 2:  ground,  Class 7:  low point,  Class 9: water, Class 10: ignored ground, Class 11:  withheld.</procdesc>
				<srcused>CONT, GPS_SOL, LIDAR</srcused>
				<procdate>2015</procdate>
				<srcprod>LAS</srcprod>
			</procstep>
			<procstep>
				<procdesc>The bare earth points of the processed lidar data are then output to a DEM tile format. The DEM is compared to the ground control and elevation differences between the surface and surveyed elevation are recorded in tabular form.  Vertical accuracy statistics are then developed to produce vertical RMSE and overall accuracy estimates and reports.</procdesc>
				<srcused>CONT, LIDAR</srcused>
				<procdate>2015</procdate>
				<srcprod>None</srcprod>
			</procstep>
		</lineage>
	</dataqual>
	<spdoinfo>
		<direct>Point</direct>
	</spdoinfo>
	<spref>
		<horizsys>
			<geodetic>
				<horizdn>North American Datum of 1983</horizdn>
				<ellips>Geodetic Reference System 80</ellips>
				<semiaxis>6378137.000000</semiaxis>
				<denflat>298.257222101004</denflat>
			</geodetic>
			<cordsysn><geogcsn>GCS_North_American_1983</geogcsn><projcsn>NAD_1983_2011_State_Plane_MIchigan_South_FIPS_2113</projcsn></cordsysn><planar><mapproj><mapprojn>Lambert Conformal Conic</mapprojn><lambertc><stdparll>42.1</stdparll><stdparll>43.6666666666667</stdparll><longcm>-84.3666666666667</longcm><latprjo>41.5</latprjo><feast>13123359.5800525</feast><fnorth>0</fnorth></lambertc></mapproj><planci><plance>coordinate pair</plance><coordrep><absres>0.01</absres><ordres>0.01</ordres></coordrep><plandu>international feet</plandu></planci></planar></horizsys>
		<vertdef>
			<altsys>
				<altdatum>North American Vertical Datum of 1988(GEOID12a)</altdatum>
				<altres>0.1</altres>
				<altunits>feet</altunits>
				<altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
			</altsys>
		</vertdef>
	</spref>
	<distinfo>
		<distrib>
			<cntinfo>
				<cntperp>
					<cntper>Everett Root</cntper>
					<cntorg>State of Michigan</cntorg>
				</cntperp>
				<cntpos>Manager, Geodata Services Section</cntpos>
				<cntaddr>
					<addrtype>mailing address</addrtype>
					<address>111 S. Capitol Ave</address>
					<city>Lansing</city>
					<state>MI</state>
					<postal>48933</postal>
					<country>U.S.A.</country>
					<address>10th Floor Romney</address></cntaddr>
				<cntvoice>517-335-7180</cntvoice>
				<cntemail>roote@michigan.gov</cntemail>
				<hours>8:00 AM - 5:00 PM</hours>
			</cntinfo>
		</distrib>
		<resdesc>Michigan 2015 LiDAR project</resdesc>
		<distliab>The State of Michigan Geographic Information Systems digital data have been tested and their documentation carefully reviewed.  However, the State of Michigan and its representatives make no warranty or representation, either expressed or implied, with respect to the digital data and their documentation, their quality, performance, merchantability, or fitness for a particular purpose.  The digital data are distributed on "as is" basis, and the user assumes all risk to their quality, the results obtained from their use, and the performance of the data.  In no event will the State of Michigan or its representatives be liable for any direct, indirect, special, incidental or consequential damages resulting from and defect in the State of Michigan or in their documentation.  This disclaimer of warranty is exclusive and in lieu of all others, oral or written, express or implied.  No agent or employee is authorized to make any modification, extension, or addition to this warranty.</distliab>
		<stdorder>
			<digform>
				<digtinfo>
					<formname>LAS</formname>
					<formvern>1.2</formvern><transize>2000</transize><dssize>2000</dssize></digtinfo>
				<digtopt>
					<onlinopt>
						<computer>
							<networka>
								<networkr>http://www.michigan.gov</networkr>
							</networka>
						</computer>
						<accinstr>unknown</accinstr>
					</onlinopt>
					<offoptn><offmedia>5 - 1/2 inch hard drive</offmedia><recfmt>LAS</recfmt></offoptn></digtopt>
			</digform>
			<fees>unknown</fees>
			<ordering>State of Michigan</ordering>
			<turnarnd>unknown</turnarnd></stdorder>
		<availabl>
			<timeinfo>
				<sngdate>
					<caldate>2015</caldate>
				</sngdate>
			</timeinfo>
		</availabl>
	</distinfo>
	<metainfo>
		<metd>2015</metd>
		<metc>
			<cntinfo>
				<cntperp>
					<cntper>Kris Andersen</cntper>
					<cntorg>Sanborn Map Co</cntorg>
				</cntperp>
				<cntpos>Project Manager</cntpos>
				<cntaddr>
					<addrtype>mailing address</addrtype>
					<address>1935 Jamboree Dr</address>
					<city>Colorado Springs</city>
					<state>CO</state>
					<postal>80920</postal>
					<country>U.S.A.</country>
				</cntaddr>
				<cntvoice>719.264.5490</cntvoice>
				<cntemail>kandersen@sanborn.com</cntemail>
				<hours>8:00 AM - 5:00 PM</hours>
			</cntinfo>
		</metc>
		<metstdn>FGDC CSDGM</metstdn>
		<metstdv>FGDC-STD-001-1998</metstdv>
	</metainfo>
	<Esri><CreaDate>20120330</CreaDate><CreaTime>08500700</CreaTime><SyncOnce>TRUE</SyncOnce><ModDate>20160301</ModDate><ModTime>15021200</ModTime><MetaID>{8DE3DE1B-30AB-48D1-9B5B-D8574399589A}</MetaID></Esri><distInfo><distributor><distorTran><onLineSrc><linkage Sync="FALSE"></linkage><protocol Sync="TRUE">Local Area Network</protocol></onLineSrc></distorTran></distributor></distInfo><eainfo><overview><eadetcit>FEMA Specification Version QL2 meeting 9.25cm FVA</eadetcit><dsoverv>Bare Earth DEM
Classified LAS
Raw point cloud LAS
Breakline GDB
Intensity Images</dsoverv><eaover>Bare Earth DEM:
Classes-
2 - Bare-Earth Ground

Classified LAS:
Classes:
1 - Unclassified (Processed)
2 - Bare-Earth Ground
7 - Noise (Low or High Points)
9 - Water
10 - Ignored Ground
11 - Withheld

Raw Point Cloud LAS:
Classes-
0 - not processed

Breaklines:
Geodatabase

Intensity Images:
TIF format</eaover></overview></eainfo><mdDateSt Sync="TRUE">20160301</mdDateSt></metadata>
