<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE metadata SYSTEM "http://www.fgdc.gov/metadata/fgdc-std-001-1998.dtd">
<metadata>
	<idinfo>
		<citation>
			<citeinfo>
				<origin>Sanborn Map Company, Inc.</origin>
				<pubdate>20200810</pubdate>
				<title>Gogebic AOI, Michigan</title>
				<geoform>Lidar point cloud</geoform>
			</citeinfo>
		</citation>
		<descript>
			<abstract>Product: These lidar data are processed Classified LAS 1.4 files, formatted to 1046 individual 2500 ft x 2500 ft tiles; used to create intensity images, 3D breaklines and hydro-flattened DEMs as necessary. 
Geographic Extent: Gogebic AOI, Michigan, covering approximately 235 square miles.
Dataset Description: Gogebic AOI, Michigan 2019 Lidar project called for the Planning, Acquisition, processing and derivative products of lidar data to be collected at a nominal pulse spacing (NPS) of 0.7 meter. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 1.3. The data was developed based on a horizontal projection/datum of NAD83 (2011), State Plane Coordinate System, international feet and vertical datum of NAVD88 (GEOID12B), international feet. Lidar data was delivered as processed Classified LAS 1.4 files, formatted to 1046 individual 2500 ft x 2500 ft tiles, as tiled Intensity Imagery, and as tiled bare earth DEMs; all tiled to the same 2500 ft x 2500 ft schema.
Ground Conditions: Lidar was collected in spring 2019, while no snow was on the ground and rivers were at or below normal levels. In order to post process the lidar data to meet task order specifications and meet ASPRS vertical accuracy guidelines, Sanborn Map Company, Inc. established a total of 4 ground control points that were used to calibrate the lidar to known ground locations established throughout the project area. An additional 10 independent accuracy check points, 6 in Open Terrain/Bare-Earth and Urban landcovers (6 NVA points), 4 in Grass, Brush and Trees categories (4 VVA points), were used to assess the vertical accuracy of the data. These check points were not used to calibrate or post process the data.</abstract>
			<purpose>To acquire detailed surface elevation data for use in conservation planning, design, research, floodplain mapping, dam safety assessments and elevation modeling, etc. Classified LAS files are used to show the manually reviewed bare earth surface. This allows the user to create Intensity Images, Breaklines and Raster DEM. The purpose of these lidar data was to produce high accuracy 3D hydro-flattened Digital Elevation Model (DEM) with a 2 ft cell size. These lidar point cloud data were used to create intensity images, 3D breaklines, and hydro-flattened DEMs as necessary.</purpose>
			<supplinf>CONTRACTOR: Sanborn Map Company</supplinf>
			<lidar>
				<ldrinfo>
					<ldrspec>USGS Lidar Base Specification v1.3</ldrspec>
					<ldrsens>Leica TerrainMapper</ldrsens>
					<ldrmaxnr>4</ldrmaxnr>
					<ldrnps>0.66</ldrnps>
					<ldrdens>2.3</ldrdens>
					<ldranps>0.66</ldranps>
					<ldradens>2.3</ldradens>
					<ldrfltht>3050</ldrfltht>
					<ldrfltsp>160</ldrfltsp>
					<ldrscana>40</ldrscana>
					<ldrscanr>87.9</ldrscanr>
					<ldrpulsr>659</ldrpulsr>
					<ldrpulsd>4</ldrpulsd>
					<ldrpulsw>0.71</ldrpulsw>
					<ldrwavel>1064</ldrwavel>
					<ldrmpia>1</ldrmpia>
					<ldrbmdiv>0.25</ldrbmdiv>
					<ldrswatw>2220</ldrswatw>
					<ldrswato>20</ldrswato>
					<ldrgeoid>National Geodetic Survey (NGS) Geoid12B</ldrgeoid>
				</ldrinfo>
				<ldraccur>
					<ldrchacc>0</ldrchacc>
					<rawnva>0</rawnva>
					<rawnvan>0</rawnvan>
					<clsnva>0</clsnva>
					<clsnvan>0</clsnvan>
					<clsvva>0</clsvva>
					<clsvvan>0</clsvvan>
				</ldraccur>
				<lasinfo>
					<lasver>1.4</lasver>
					<lasprf>6</lasprf>
					<laswheld>Withheld (ignore) points were identified in these files using the standard LAS Withheld bit.</laswheld>
					<lasolap>Swath "overage" points were identified in these files using the standard LAS overlap bit.</lasolap>
					<lasintr>16</lasintr>
					<lasclass>
						<clascode>1</clascode>
						<clasitem>Processed, but Unclassified</clasitem>
					</lasclass>
					<lasclass>
						<clascode>2</clascode>
						<clasitem>Bare Earth Ground</clasitem>
					</lasclass>
					<lasclass>
						<clascode>7</clascode>
						<clasitem>Low Noise</clasitem>
					</lasclass>
					<lasclass>
						<clascode>9</clascode>
						<clasitem>Water</clasitem>
					</lasclass>
					<lasclass>
						<clascode>17</clascode>
						<clasitem>Bridge Decks</clasitem>
					</lasclass>
					<lasclass>
						<clascode>18</clascode>
						<clasitem>High Noise</clasitem>
					</lasclass>
					<lasclass>
						<clascode>20</clascode>
						<clasitem>Ignored Ground</clasitem>
					</lasclass>
				</lasinfo>
			</lidar>
			</descript>
		<timeperd>
			<timeinfo>
				<rngdates>
					<begdate>20190521</begdate>
					<enddate>20200528</enddate>
				</rngdates>
			</timeinfo>
			<current>ground condition</current>
		</timeperd>
		<status>
			<progress>Complete</progress>
			<update>None planned</update>
		</status>
		<spdom>
			<bounding>
				<westbc>-90.426006</westbc>
				<eastbc>-89.869963</eastbc>
				<northbc>46.629204</northbc>
				<southbc>46.279124</southbc>
			</bounding>
		</spdom>
		<keywords>
			<theme>
				<themekt>None</themekt>
				<themekey>Model</themekey>
				<themekey>LAS Point Cloud</themekey>
				<themekey>Remote Sensing</themekey>
				<themekey>Elevation Data</themekey>
				<themekey>Lidar</themekey>
			</theme>
			<place>
				<placekt>None</placekt>
				<placekey>Michigan</placekey>
				<placekey>Gogebic AOI</placekey>
			</place>
		</keywords>
		<accconst>No restrictions apply to these data.</accconst>
		<useconst>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. Acknowledgement of the U.S. Geological Survey would be appreciated for products derived from these data.</useconst>
	</idinfo>
	<dataqual>
		<logic>Data covers the BPA specified for this project.</logic>
		<complete>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 of good quality and data passes Non-Vegetated Vertical Accuracy specifications.</complete>
		<posacc>
    <!-- Positional Accuracy - an assessment of the accuracy of the positions of spatial objects. Type: compound. -->
     <vertacc>
      <!-- Vertical Positional Accuracy - an estimate of accuracy of the vertical positions in the data set. Type: compound. -->
      <vertaccr>This data set was produced to meet ASPRS Positional Accuracy Standard for Digital Geospatial Data (2014) for a 10-cm RMSEz Vertical Accuracy Class.</vertaccr>
      <!-- Vertical Positional Accuracy Report - Please see ground survey report. Type: text. Domain: free text. -->
     </vertacc>
		</posacc>
		<lineage>
			<srcinfo>
				<srccite>
					<citeinfo>
						<origin>Steven A. Wood Professional Surveyor</origin>
						<pubdate>20190723</pubdate>
						<title>8235_Survey_Gogebic</title>
						<geoform>vector digital data and tabular digital data</geoform>
						<pubinfo>
							<pubplace>Junction City, Oregon</pubplace>
							<publish>Steven A. Wood Professional Surveyor</publish>
						</pubinfo>
						<othercit>None</othercit>
					</citeinfo>
				</srccite>
				<srcscale>50</srcscale>
				<typesrc>Email</typesrc>
				<srctime>
					<timeinfo>
						<sngdate>
							<caldate>20190723</caldate>
						</sngdate>
					</timeinfo>
					<srccurr>ground condition</srccurr>
				</srctime>
				<srccitea>8235_Survey_Gogebic</srccitea>
				<srccontr>This data source was used (along with airborne GNSS/IMU data) to georeference the lidar point cloud data.</srccontr>
			</srcinfo>
			<procstep>
				<procdesc>The following steps describe the Raw Data Processing and Calibration process: 1) Technicians processed the raw data to LAS format flight lines using the ABGNSS/IMU solution. 2) Technicians use TerraSolid TerraMatch to calculate initial calibration adjustment angles by mission and/or block. This is accomplished by identifying ground and above ground feature observations between flight-lines and calculating the offsets. The technician then analyzed the results and made any necessary additional adjustment until it is acceptable. 3) Once the angle calculation was completed the adjusted settings were applied to all of the flight-lines of the mission and/or block and checked for consistency. The technicians utilized commercial and proprietary software packages to analyze how well flight-line overlaps match and adjusted as necessary until the results met the project specifications. 4) 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 6 cm RMSEz within individual swaths and less than or equal to 8 cm RMSDz or within swath overlap (between adjacent swaths). 5) The technicians ran a final vertical accuracy check of the calibrated point cloud 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 1.3, and breaklines were collected for water features. Bare earth DEMs were exported from the classified point cloud using collected breaklines for hydroflattening.</procdesc>
				<srcused>8235_Survey_Gogebic</srcused>
				<procdate>2019</procdate>
				<proccont>
					<cntinfo>
						<cntorgp>
							<cntorg>Sanborn Map Company, Inc.</cntorg>
							<cntper>Shawn Benham</cntper>
						</cntorgp>
						<cntaddr>
							<addrtype>mailing and physical</addrtype>
							<address>1935 Jamboree Drive</address>
							<address>Suite 100</address>
							<city>Colorado Springs</city>
							<state>CO</state>
							<postal>80920</postal>
							<country>USA</country>
						</cntaddr>
						<cntvoice>(719)502-1296</cntvoice>
						<cntfax>(719)528-5090</cntfax>
						<cntemail>sbenham@sanborn.com</cntemail>
						<hours>Monday - Friday 8 a.m. to 5 p.m. (Mountain Time)</hours>
						<cntinst>If unable to reach the contact by telephone, please send an email. You should get a response within 24 hours.</cntinst>
					</cntinfo>
				</proccont>
			</procstep>
			<procstep>
				<procdesc>LAS Point Classification: The point classification is performed as described below. The bare-earth surface is manually reviewed to ensure correct classification on the Class 2 (Ground) points. After the bare-earth surface is edited and QC'd, it is then used to generate all hydro-breaklines through heads-up digitization. All ground (ASPRS Class 2) lidar data inside of the Lake Pond and River Pond hydro flattening breaklines were then classified to water (ASPRS Class 9) using LP360 functionality. A buffer of 2 feet was also used around each hydro-flattened feature to classify these ground (ASPRS Class 2) points to Ignored ground (ASPRS Class 20). All Lake Pond Island and River Stream Island features were checked to ensure that the ground (ASPRS Class 2) points were reclassified to the correct classification after the automated classification was completed. All overlap data was processed through automated functionality provided by TerraScan to classify the overlapping flight-line data to approved classes by USGS. The overlap data was classified using standard LAS overlap bit. These classes were created through automated processes only and were not verified for classification accuracy. All data was manually reviewed and any remaining artifacts removed using functionality provided by TerraScan and TerraModeler. Global Mapper is used as a final check of the bare-earth dataset. GeoCue was then used to create the deliverable industry-standard LAS files for the Classified Point Cloud Data. LAStools, LP360 and TerraScan software was used to perform statistical analysis of the classes in the LAS files, on a per tile level to verify classification metrics and full LAS header information.</procdesc>
				<procdate>20200717</procdate>
			</procstep>
		</lineage>
	</dataqual>
	<spdoinfo>
		<direct>Point</direct>
	</spdoinfo>
	<spref>
		<horizsys>
			<planar>
				<gridsys>
					<gridsysn>State Plane Coordinate System 1983</gridsysn>
					<spcs>
						<spcszone>2111</spcszone>
						<transmer>
							<sfctrmer>0.9999</sfctrmer>
							<longcm>-87</longcm>
							<latprjo>44.78333333333333</latprjo>
							<feast>26246719.16</feast>
							<fnorth>0</fnorth>
						</transmer>
					</spcs>
				</gridsys>
				<planci>
					<plance>coordinate pair</plance>
					<coordrep>
						<absres>0.001</absres>
						<ordres>0.001</ordres>
					</coordrep>
					<plandu>feet</plandu>
				</planci>
			</planar>
			<geodetic>
				<horizdn>NAD83 National Spatial Reference System 2011</horizdn>
				<ellips>Geodetic Reference System 80</ellips>
				<semiaxis>6378137</semiaxis>
				<denflat>298.257222101</denflat>
			</geodetic>
		</horizsys>
		<vertdef>
			<altsys>
				<altdatum>North American Vertical Datum of 1988</altdatum>
				<altres>0.001</altres>
				<altunits>feet</altunits>
				<altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
			</altsys>
		</vertdef>
	</spref>
	<metainfo>
		<metd>20200810</metd>
		<metc>
			<cntinfo>
				<cntorgp>
					<cntorg>Sanborn Map Company, Inc.</cntorg>
				</cntorgp>
				<cntaddr>
					<addrtype>mailing and physical</addrtype>
					<address>1935 Jamboree Drive</address>
					<address>Suite 100</address>
					<city>Colorado Springs</city>
					<state>CO</state>
					<postal>80920</postal>
					<country>USA</country>
				</cntaddr>
				<cntvoice>(866)726-2676</cntvoice>
			</cntinfo>
		</metc>
		<metstdn>FGDC Content Standard for Digital Geospatial Metadata</metstdn>
		<metstdv>FGDC-STD-001-1998</metstdv>
	</metainfo>
</metadata>