<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE metadata SYSTEM "http://thor-f5.er.usgs.gov/ngtoc/metadata/fgdc-std-001-1998.dtd">
<metadata>
 <idinfo>
  <citation>
   <citeinfo>
    <origin>Sanborn Map Company, Inc.</origin>
    <pubdate>20201217</pubdate>
    <title>MISAIL_2020_Lidar_Chippewa_Luce_Schoolcraft; Classified Point Cloud</title>
    <geoform>Lidar point cloud</geoform>
   </citeinfo>
  </citation>
  <descript>
   <abstract>Product: These lidar data are processed Classified LAS 1.4 files, formatted to 9948 individual 2500 ft x 2500 ft tiles; used to create intensity rasters, 3D breaklines and hydro-flattened DEMs as necessary.
   	Geographic Extent: The Chippewa_Luce_Schoolcraft AOI,  Michigan, covering approximately 2230 square miles. Dataset Description: The 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 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 2.1.
   	The data was developed based on a horizontal projection/datum of NAD83 (2011), State Plane, International Feet and vertical datum of NAVD88 (GEOID12B), International Feet. Lidar data was delivered as processed Classified LAS 1.4 files, formatted to 9948 individual 2500 ft x 2500 ft tiles, as tiled intensity rasters, and as tiled bare-earth DEMs; all tiled to the same 2500 ft x 2500 ft schema.
   	Ground Conditions: Lidar was collected in spring 2020, 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., utilized a total of 24 ground control points that were used to calibrate the lidar to known ground locations established throughout the project area.
   	An additional 73 independent accuracy checkpoints, 42 in Bare Earth and Urban landcovers (42 NVA points), 31 in Tall Grass and Brushland/Low Trees categories (31 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. These lidar point cloud data were used to create intensity images, 3D breaklines, and hydro-flattened DEMs as necessary.</purpose>
   <supplinf>USGS Contract No. G16PC00051 CONTRACTOR: Sanborn Map Company, Inc. All follow-on processing was completed by the prime contractor.</supplinf>
   <lidar>
    <ldrinfo>
     <ldrspec>U.S. Geological Survey (USGS) - National Geospatial Program (NGP) Lidar Base Specification v2.1</ldrspec>
     <ldrsens>Leica TerrainMapper</ldrsens>
     <ldrmaxnr>4</ldrmaxnr>
     <ldrnps>0.66</ldrnps>
     <ldrdens>2.3</ldrdens>
     <ldranps>0.51</ldranps>
     <ldradens>3.9</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.5</ldrchacc>
     <rawnva>0.172</rawnva>
     <rawnvan>42</rawnvan>
     <clsnva>0.167</clsnva>
     <clsnvan>42</clsnvan>
     <clsvva>0.180</clsvva>
     <clsvvan>31</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>
     <lasclass>
      <clascode>21</clascode>
      <clasitem>Snow</clasitem>
     </lasclass>
     <lasclass>
      <clascode>22</clascode>
      <clasitem>Temporal Exclusion</clasitem>
     </lasclass>
    </lasinfo>
   </lidar>
  </descript>
  <timeperd>
   <timeinfo>
    <rngdates>
     <begdate>20200513</begdate>
     <enddate>20200519</enddate>
    </rngdates>
   </timeinfo>
   <current>ground condition</current>
  </timeperd>
  <status>
   <progress>Complete</progress>
   <update>None planned</update>
  </status>
  <spdom>
   <bounding>
    <westbc>-86.466014</westbc>
    <eastbc>-84.936045</eastbc>
    <northbc>46.766527</northbc>
    <southbc>45.733992</southbc>
   </bounding>
   <lboundng>
   	<leftbc>541300.00</leftbc>
   	<rightbc>658020.00</rightbc>
   	<topbc>5181370.00</topbc>
   	<bottombc>5064780.00</bottombc>
   </lboundng>
  </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>Chippewa_Luce_Schoolcraft</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>
  <native>Optech-LMS; GeoCue v2017.1.14.1; Windows 10 Operating System</native>
 </idinfo>
 <dataqual>
  <logic>Data covers the entire area 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>
   <vertacc>
    <vertaccr>This data set was tested to meet ASPRS Positional Accuracy Standard for Digital Geospatial Data (2014) for a 10cm RMSEz Vertical Accuracy Class.
    Actual NVA accuracy was found to be RMSEz = 0.167ft, equating to +/- 0.328ft at 95% confidence level. Actual VVA accuracy was found to be +/- 0.330ft at the 95th percentile.</vertaccr>
   </vertacc> 
  </posacc>
  <lineage>
   <procstep>
    <procdesc>The boresight was completed prior to project execution. The following steps describe the Raw Data Processing process:
    1) Technicians processed the raw data to LAS format flight lines using the final GNSS/IMU solution. This LAS data set was used as source data for lidar matching.
    2) Technicians utilized commercial and proprietary software packages to analyze how well flight line overlaps match for the entire lift and adjusted as necessary until the results met the project specifications.
    3) Once all lifts were completed with lidar matching, 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 RMSEz or within swath overlap (between adjacent swaths).
    4) The technicians ran a final vertical accuracy check of the flight lines against the surveyed check points after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level (Required Accuracy) was met. Point classification was performed according to USGS Lidar Base Specification v2.1, 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_Chippewa_Luce_Schoolcraft</srcused>
    <procdate>2020</procdate>
   </procstep>
   <procstep>
    <procdesc>LAS Point Classification: The point classification is performed as described below. The bare-earth surface is then manually reviewed to ensure correct classification on the Class 2 (Ground) points. After the bare-earth surface is finalized, it is then used to generate all hydro-breaklines through heads-up digitization. All Class 2 (Ground) lidar data inside of the Lake Pond and Double Line Drain hydro-flattened breaklines were then classified to Class 9 (Water) using LP360 functionality.
    A buffer of 2 feet was also used around each hydro-flattened feature to classify these Class 2 (Ground) points to Class 20 (Ignored Ground). All Lake Pond Island and Double Line Drain Island features were checked to ensure that the Class 2 (Ground) 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. Due to software limitations within TerraScan, these classes were used to trip the withheld bit within various software packages. These processes were reviewed and accepted by USGS through numerous conference calls and pilot study areas. All data was manually reviewed and any remaining artifacts removed using functionality provided by LP360, TerraScan and TerraModeler.
    Global Mapper was used as a final check of the bare-earth dataset. GeoCue was then used to create the deliverable industry-standard LAS files. Sanborn Map Company, Inc. proprietary software was used to perform final statistical analysis of the classes in the LAS files, on a per tile level to verify final classification metrics and full LAS header information.</procdesc>
    <procdate>20201214</procdate>
   </procstep>
   <procstep>
    <procdesc>Data was tested at 0.50 meter aggregate nominal pulse spacing and at 3.9 aggregate points per meter. The aggregate nominal pulse spacing was tested on classified tiled LAS using geometrically reliable first-return points without overlap. ANPS was tested using Delaunay Triangulation that produced average point spacing between all nearest neighbors.</procdesc>
    <procdate>20201216</procdate>
   </procstep>
  </lineage>
 </dataqual>
 <spdoinfo>
  <direct>Point</direct>
   <ptvctinf>
  	<sdtsterm>
  		<sdtstype>Point</sdtstype>
  		<ptvctcnt>23,965,111,746</ptvctcnt>
  	</sdtsterm>
  </ptvctinf>
 </spdoinfo>
 <spref>
  <horizsys>
   <planar>
    <mapproj>
     <mapprojn>NAD 1983 (2011) StatePlane Michigan North Intl Feet</mapprojn>
     <lambertc>
      <stdparll>47.08333333333334</stdparll>
      <stdparll>45.48333333333333</stdparll>
      <longcm>-87</longcm>
      <latprjo>44.78333333333333</latprjo>
      <feast>26246719.16</feast>
      <fnorth>0</fnorth>
     </lambertc>
    </mapproj>
    <planci>
     <plance>coordinate pair</plance>
     <coordrep>
      <absres>0.001</absres>
      <ordres>0.001</ordres>
     </coordrep>
     <plandu>foot_intl</plandu>
    </planci>
   </planar>
   <geodetic>
    <horizdn>NAD83 National Spatial Reference System 2011</horizdn>
    <ellips>GRS 1980</ellips>
    <semiaxis>6378137.0</semiaxis>
    <denflat>298.257222101</denflat>
   </geodetic>
  </horizsys>
  <vertdef>
   <altsys>
    <altdatum>North American Vertical Datum of 1988, Geoid 12B</altdatum>
    <altres>0.001</altres>
    <altunits>foot_intl</altunits>
    <altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
   </altsys>
  </vertdef>
 </spref>
 <metainfo>
  <metd>20201217</metd>
  <metrd>20201217</metrd>
  <metc>
   <cntinfo>
    <cntorgp>
     <cntorg>Sanborn Map Company, Inc.</cntorg>
    </cntorgp>
    <cntaddr>
     <addrtype>mailing and physical</addrtype>
     <address>1935 Jamboree Drive, 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>
  <metac>None.</metac>
  <metuc>None.</metuc>
  <metsi>
  	<metscs>None.</metscs>
  	<metsc>Unclassified.</metsc>
  	<metshd>None.</metshd>
  </metsi>
  <metextns>
   <onlink>None.</onlink>
   <metprof>None.</metprof>
  </metextns>
 </metainfo>
</metadata>