<?xml version="1.0" encoding="UTF-8"?>

<metadata>
 <idinfo>
   <citation>
    <citeinfo>
    <origin>Quantum Spatial, Inc.</origin>
     <pubdate>20140609</pubdate>
  <title>Logan County Illinois, LiDAR Acquisition, Bare Earth DEM
  </title>
       <geoform>LiDAR point cloud</geoform>
    </citeinfo>
   </citation>
   <descript>
       <abstract> Task Order:G13PD00885 Contract ID: G10PC00025
  
       This dataset is LiDAR point cloud data and derivative models of Logan County, Illinois.  The area of acquisition is approximately 618 square miles (1600 square kilometers).

        This dataset consists of LiDAR LAS swath files and tiled LAS files. Tiled LAS files contain LiDAR point information which has been calibrated, controlled, and classified. Tiled LAS and derived data models are named according to a tiling scheme in accordance with the conventions of the U.S. National Grid, using the coordinates at the SW corner of the tile as the tile name.

	Quantum Spatial Project No: 1130905

    </abstract> 
       <lidar>
       <ldrinfo>
        <ldrspec>USGS NGP Base Specification v1</ldrspec>
        <ldrsens>Leica ALS70 sensor SN7220</ldrsens>
        <ldrmaxnr>4</ldrmaxnr> 
        <ldrnps>0.5</ldrnps> 
        <ldrdens>4.20</ldrdens> 
        <ldrfltht>1475</ldrfltht> 
        <ldrfltsp>150</ldrfltsp> 
        <ldrscana>40</ldrscana> 
        <ldrscanr>53.4</ldrscanr> 
        <ldrpulsr>358</ldrpulsr> 
        <ldrpulsd>4</ldrpulsd> 
        <ldrpulsw>NA</ldrpulsw> 
        <ldrwavel>1064</ldrwavel> 
        <ldrmpia>1</ldrmpia> 
        <ldrbmdiv>0.15</ldrbmdiv>
        <ldrswatw>1105.16</ldrswatw> 
        <ldrswato>12</ldrswato> 
        <ldrcrs>NAD_1983_2011_StatePlane_Illinois_West_FIPS_1202_Ft_US</ldrcrs> 
        <ldrgeoid>National Geodetic Survey (NGS) Geoid12A</ldrgeoid> 
       </ldrinfo> 
       
      <ldraccur> 
         <ldrchacc> 0.1</ldrchacc> 
        <rawfva>0.107</rawfva> 
        <clsfva> 0.106</clsfva>
         
         <clscva>0.1350</clscva>
           <clssvas>
           <svalctyp>Urban</svalctyp> 
           <svavalue>0.0923</svavalue> 
            </clssvas>
           <clssvas>
           <svalctyp>Open Terrain</svalctyp>
           <svavalue>0.0990</svavalue>
            </clssvas>
           <clssvas>
           <svalctyp>Tall Grass/Agriculture</svalctyp>
           <svavalue>0.1267</svavalue>
            </clssvas>
           <clssvas>
           <svalctyp>Brush/Scrub/Shrub</svalctyp>
           <svavalue>0.1783</svavalue>
            </clssvas>
           <clssvas>
           <svalctyp>Woods/Forest</svalctyp>
           <svavalue>0.1338</svavalue>
            </clssvas>

       </ldraccur>
       <lasinfo>
          <lasver>1.2</lasver> 
          <lasprf>1</lasprf> 
           <laswheld>Withheld (ignore) points were identified in these files using the standard LAS Withheld bit
           </laswheld> 
           <lasolap> To maintain high point density overage points were not indicated by class
           </lasolap> 
           <lasintr>8-bit</lasintr> 
           <lasclass> 
            <clascode>0</clascode> 
            <clasitem>Never Processed</clasitem> 
           </lasclass>
           <lasclass>
               <clascode>1</clascode>
               <clasitem>Undetermined/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</clasitem>
           </lasclass>

       </lasinfo>
    </lidar>
       <purpose>LiDAR data collection is to produce high accuracy models of the Logan County, Illinois in accordance with requirements outlined in the Task Order Agreement.  

        The raw LiDAR point cloud data is used to create surface models as requested; classified LiDAR LAS files, bare-earth Digital Elevation Models (DEM), Intensity raster of first return,  shapefiles of breaklines representative of surface hydro features. 
    </purpose>
       <supplinf>
       	Project data includes an area in the northeast of Logan county, from Oran into Chester Townships, where LiDAR data was collected at 8 points per meter. The data is incorporated with the county wide data set which is at 4 points per meter.

       8 point per meter collection rate:

       Average Point Spacing 0.5 meters
       Average Point Density  8.36 meters
       Flying Height AGL 775 meters
       Recommended Ground Speed 150 knots
       Field of View (FOV) 36 degrees
       Scan Rate Setting used 56 Hz
       Laser Pulse Rate used 33.5 Hz
       Full Swath Width 1105 meters
       Minimum Sidelap 19 degrees
        
    </supplinf>
   </descript>
   <timeperd>
 <timeinfo>
        <rngdates>
          <begdate>20131123</begdate>
          <enddate>20131130</enddate>
        </rngdates>
 </timeinfo>
     <current>ground condition</current> 
   </timeperd>
   <status>
     <progress>complete</progress> 
     <update>none</update>
   </status>
   <spdom>
     <bounding>
       <westbc>-89.606</westbc> 
       <eastbc>-89.141</eastbc>
       <northbc>40.327</northbc>
       <southbc>39.916</southbc>
     </bounding>

   </spdom>
   <keywords>
       <theme>
       <themekt>None</themekt>
       <themekey>Elevation data</themekey> 
       <themekey>LiDAR</themekey> 
       <themekey>LAS</themekey>
       <themekey>Bare Earth</themekey>
       <themekey>First Return</themekey>
       <themekey>Breakline</themekey>
       <themekey>Intensity Raster</themekey> 
       </theme>
       <place>
       <placekt>None</placekt>
       <placekey>Illinois</placekey> 
       <placekey>Logan County</placekey>
       <placekey>Lincoln</placekey>
       </place>
   </keywords>
   <accconst>No restrictions apply to accessing this 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.
     </useconst>
   <ptcontac>
     <cntinfo> 
       <cntorgp>
         <cntorg>Quantum Spatial, Inc.</cntorg>
         <cntper>Chris Guy</cntper>
       </cntorgp>
       <cntaddr>
         <addrtype>mailing and physical</addrtype>
         <address>4020 Technology Parkway </address>
         <city>Sheboygan</city>
         <state>WI</state>
         <postal>53083</postal>
         <country>USA</country>
       </cntaddr>
       <cntvoice>920-457-3631</cntvoice>
       <cntfax>920-457-0410</cntfax> 
       <cntemail>cguy@quantumspatial.com</cntemail> 
       <hours>Monday through Friday 8:00 AM to 4:00 PM (Central Time)</hours> 
     </cntinfo>
   </ptcontac>
   <native> ALS Post Processor 2.75 Build#25; GeoCue Version 13.1.45.1; Windows XP Operating System
    </native> 
 </idinfo>
 <dataqual> 
   <logic>Data cover the entire area specified for this project.</logic>
   <complete>These data files include all data points collected.
  No points have been removed or excluded.
  The raw point cloud is of good quality and data passes Fundamental Vertical Accuracy specifications.
   </complete>
   <posacc>
    <vertacc>
   <vertaccr>Project specifications require that vertical accuracy, as RMSE, of LiDAR data be less than 9.25 cm in open terrain. Vertical accuracy is determined by comparison of a TIN or DEM derived from the final LiDAR ground points and ground survey check point elevations. Differences are calculated to establish a RSME. 

   The vertical accuracy of the LiDAR data set meets the requirement of RMSE less than 9.25 cm and of FVA less than 18.13 cm.
   </vertaccr> 
   <qvertpa>
   <vertaccv>0.0377 meters. RMSE as tested against a TIN derived from LiDAR Ground points</vertaccv>
   <vertacce>     A TIN derived from the final LiDAR ground points is compared to ground survey check points. Elevation differences are calculated to establish a RMSE.
   </vertacce> 
  </qvertpa>
  
     <qvertpa>
   <vertaccv>0.0739 meters. FVA as tested against a TIN derived from LiDAR Ground points</vertaccv>
   <vertacce>
      The FVA is tested using Open Terrain ground survey points.  The check points are compared to elevation values of a TIN derived from the final LiDAR ground points. Differences in elevations are calculated to determine a RSME. The RMSE value is multiplied by 1.96 to establish the FVA.
   </vertacce> 
  </qvertpa>

      <qvertpa>
   <vertaccv>0.054 meters. RMSE as tested against a DEM derived from LiDAR Ground points</vertaccv>
   <vertacce>
      A DEM derived from the final LiDAR ground points is compared to ground survey check points. Elevation differences are calculated to establish a RMSE.
   </vertacce> 
  </qvertpa>

       <qvertpa>
   <vertaccv>0.106 meters. FVA as tested against a DEM derived from LiDAR Ground points</vertaccv>
   <vertacce>
      The FVA is tested using Open Terrain ground survey points.  The check points are compared to elevation values of a DEM derived from the final LiDAR ground points. Differences in elevations are calculated to determine a RSME. The RMSE value is multiplied by 1.96 to establish the FVA.
   </vertacce> 
  </qvertpa>
 </vertacc>
   </posacc>
   <lineage>
     <srcinfo>    
       <srccite> 
    <citeinfo>
    <origin>Compass Data, Inc.</origin>
    <pubdate>20140328</pubdate>
    <title>LiDAR Control, Logan Co, IL</title>
    <geoform>point data</geoform>
     <pubinfo>
     <pubplace>Compass Data, Inc.</pubplace>
     <publish>Compass Data, Inc.</publish>
     </pubinfo>
    <othercit>None</othercit>
    <onlink> none </onlink>
    </citeinfo>
   </srccite>
       
       <typesrc>disk</typesrc>
       <srctime>
         <timeinfo>
           <rngdates>
          <begdate>20131201</begdate>
          <enddate>20131212</enddate>
        </rngdates>
         </timeinfo>
         <srccurr>ground condition</srccurr>
       </srctime>
       <srccitea>Compass_gnd_survey</srccitea>
       <srccontr>This data source is used (along with the airborne GPS/IMU data) to index the LiDAR point cloud data. Additional survey data from particular ground cover categories are used to assess vertical accuracy of LiDAR point data or models derived from LiDAR point data in those categories appropriate.
         </srccontr>
     </srcinfo>
     <srcinfo>  
       <srccite>
    <citeinfo>
    <origin>Quantum Spatial, Inc.</origin>
    <pubdate>20140328</pubdate>
    <title>LiDAR Acquisition Logan Co, IL</title>
    <geoform>point cloud</geoform>
     <pubinfo>
     <pubplace>Quantum Spatial, Inc.</pubplace>
     <publish>Quantum Spatial, Inc.</publish>
     </pubinfo>
    <othercit>None</othercit>
    <onlink> none </onlink>
    </citeinfo>
   </srccite>
       
       <typesrc>disk</typesrc>
       <srctime>
         <timeinfo>
           <rngdates>
          <begdate>20131123</begdate>
          <enddate>20131130</enddate>
        </rngdates>
         </timeinfo>
         <srccurr>ground condition</srccurr>
       </srctime>
       <srccitea>QSI_LiDAR_Acquire</srccitea>
       <srccontr>This data source is used to acquire and record airborne LiDAR point set and GPS and IMU data.
   </srccontr>
     </srcinfo>
     <srcinfo>
       <srccite> 
    <citeinfo>
    <origin>Quantum Spatial, Inc.</origin>
    <pubdate>20140328</pubdate>
    <title>LiDAR Processing, Logan Co, IL</title>
    <geoform>point cloud</geoform>
     <pubinfo>
     <pubplace>Quantum Spatial, Inc.</pubplace>
     <publish>Quantum Spatial, Inc.</publish>
     </pubinfo>
    <othercit>None</othercit>
    <onlink>none </onlink>
    </citeinfo>
   </srccite>
       
       <typesrc>disk</typesrc>
       <srctime>
         <timeinfo>
           <sngdate>
             <caldate>201403</caldate>
           </sngdate>
         </timeinfo>
         <srccurr>ground condition</srccurr>
       </srctime>
       <srccitea>QSI_LiDAR_Proc_Class</srccitea>
       <srccontr>This data source is to process the LiDAR data set; indexing, classification, producing hydro breaklines and producing requested surface models.
        </srccontr>
     </srcinfo>
     <procstep> 
       <procdesc>Ground based survey points were collected to be compared as check points with airborne data points. These measurements were recorded and provided to Quantum Spatial for use in establishment of the LiDAR data set to ground elevations (indexing). Additional ground survey points may be made to provide for vertical accuracy assessment of LiDAR data or derivative models.
       </procdesc> 
       <srcused>Compass_gnd_survey</srcused>
       <procdate>201312</procdate>
       <proccont>
         <cntinfo>
           <cntorgp>
             <cntorg>Compass Data, Inc.</cntorg>
             <cntper>unknown</cntper>
           </cntorgp>
           <cntaddr>
             <addrtype>mailing and physical</addrtype>
             <address>12353 East Easter Ave #200</address>
             <city>Centennial6/2/2014 4:33:08 PM</city>
             <state>CO</state>
             <postal>80112</postal>
             <country>USA</country>
           </cntaddr>
           <cntvoice>303-627-40581</cntvoice>
           <cntemail>unknown</cntemail>
           <hours>week day business hours (MST)</hours>

         </cntinfo>
       </proccont>
     </procstep>
     <procstep> 
       <procdesc>Airborne LiDAR collection survey is conducted using fixed wing aircraft equipped with a LiDAR scanning system following specifications of the flight plan.  The system includes a differential GPS unit and inertial measurement system that provide data to aide in assembly of single best estimate trajectory files.


       </procdesc> 
       <srcused>QSI_LiDAR_Acquire</srcused>
       <procdate>20131130</procdate>
       <proccont>
         <cntinfo>
           <cntorgp>
             <cntorg>Quantum Spatial, Inc.</cntorg>
             <cntper>Chris Guy</cntper>
           </cntorgp>
           <cntaddr>
             <addrtype>mailing and physical</addrtype>
             <address>4020 Technology Parkway</address>
             <city>Sheboygan</city>
             <state>WI</state>
             <postal>53083</postal>
             <country>USA</country>
           </cntaddr>
           <cntvoice>1-920-457-3631</cntvoice>
           <cntfax>1-920-457-0410</cntfax>
           <cntemail>cguy@quantumspatial.com</cntemail>
           <hours>Monday through Friday 8:00 AM to 4:00 PM (Central Time)</hours>

         </cntinfo>
       </proccont>
     </procstep>
     <procstep> 
       <procdesc>
Collected data alignment is established per flightline resolving for aircraft attitude and position utilizing in-flight GPS and IMU data. Swath data is saved in LAS format where points are differentiated by discreet time, position, return value, intensity, etc. Relative accuracy of swath strips is checked. Data is arranged into a tile layout and point classification routines are accomplished. Classified points are inspected, manually reclassed where necessary and breaklines added. Derivative data products and quality assessments are produced.

	1. Automatic surface 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. 

	2. Each tile is reviewed for accuracy and consistency of the macro ground classification.

	3. As automatic processing and the testing of LiDAR is complete technicians review the generated bare-earth surface data to ensure that proper classification was achieved as part of a Quality Control process. Point classification follows the standard established by The American Society for Photogrammetry and Remote Sensing (ASPRS) for LAS data:

	Code 1	Processed, but unclassified / non-ground

	Code 2	Bare Earth / Ground

	Code 7	Noise / Low Points

	Code 9	Water

	Code 10	Ignored Ground (Breakline proximity) 

	4.  Linework is created of water bodies and drainage. A routine is used to drape line work following monotonic elevation change of drainage.

	5. LAS data and breaklines are processed to derive various surface model types.

	6. Bare earth DEM files are generated from classified LAS data and output as hydro flattened models according to the tile layout scheme. 

	Using LP360 the DEMs are generated in an ASCII format on a per tile basis with neighboring tile information available to minimize seams between tiles and with hydro breaklines in place to delineate surface water. These DEM are reviewed using GlobalMapper for adherence and completeness to the data and tile layout used during the creation process.

	The ASCII files are processed through GlobalMapper into a FLOAT format. These files are converted using ArcMap to the delivered IMG format.

   </procdesc>
       <srcused>QSI_LiDAR_Proc_Class</srcused>
       <procdate>201403</procdate>
       <proccont>
          <cntinfo>
           <cntorgp>
             <cntorg>Quantum Spatial, Inc.</cntorg>
             <cntper>Chris Guy</cntper>
           </cntorgp>
           <cntaddr>
             <addrtype>mailing and physical</addrtype>
             <address>4020 Technology Parkway</address>
             <city>Sheboygan</city>
             <state>WI</state>
             <postal>53083</postal>
             <country>USA</country>
           </cntaddr>
           <cntvoice>1-920-457-3631</cntvoice>
           <cntfax>1-920-457-0410</cntfax>
           <cntemail>cguy@quantumspatial.com</cntemail>
           <hours>Monday through Friday 8:00 AM to 4:00 PM (Central Time)</hours>
         </cntinfo>
       </proccont>
     </procstep>
   </lineage>
 </dataqual>
 <spdoinfo>
   <indspref>
	Data and models conform to the a tiling scheme of 5280 x 5280 feet. Tiles are named according the coordinates at the south west corner of the tile.
</indspref>
   <direct>Point</direct> 
   <ptvctinf>
     <sdtsterm>
       <sdtstype>Point</sdtstype> 
      </sdtsterm>
   </ptvctinf>
 </spdoinfo>
  <spref>
    <horizsys>
      <planar>
        <gridsys>
          <gridsysn>
            State Plane Coordinate System 1983
          </gridsysn>
          <spcs>
            <spcszone>
              1202 Illinois State Plane West
            </spcszone>
            <transmer>
              <sfctrmer>
                .999941176
              </sfctrmer>
              <longcm>
                -90.16666667
              </longcm>
              <latprjo>
              36.6666667
              </latprjo>
              <feast>
                2296583.333
              </feast>
              <fnorth>
                0
              </fnorth>
            </transmer>
          </spcs>
        </gridsys>
        <planci>
          <plance>
            coordinate pair
          </plance>
          <coordrep>
            <absres>
              3.2
            </absres>
            <ordres>
              3.2
            </ordres>
          </coordrep>
          <plandu>
            survey feet
          </plandu>
        </planci>
      </planar>
      <geodetic>
        <horizdn>
          North American Datum of 1983 2011
        </horizdn>
        <ellips>
          Geodetic Reference System 80
        </ellips>
        <semiaxis>
          6378137.000000
        </semiaxis>
        <denflat>
          298.257222101
        </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>
 <distinfo> 
   <distrib> 
     <cntinfo>
       <cntperp>
         <cntper>Robert Kelly</cntper>
         <cntorg>United States Geological Survey</cntorg>
       </cntperp>
       <cntpos>unknown</cntpos>
       <cntaddr>
         <addrtype>mailing and physical address</addrtype>
         <address>1400 Independence Road</address>
         <city>Rolla</city>
         <state>MO</state>
         <postal>65401</postal>
         <country>USA</country>
       </cntaddr>
       <cntvoice>573-308-3612</cntvoice>
       <cntemail>ckelly@usgs.gov</cntemail>
    </cntinfo>
  </distrib>
   <resdesc>Access to the data is available as the USGS makes it public.
   </resdesc> 
   <distliab>In no event shall the creators, custodians, or distributors of these data be liable for any damages arising out of its use, or from the inability of the customer to use these data for their intended application.
   </distliab> 
  </distinfo>
 <metainfo> 
   <metd> 20140609</metd> 
   <metc>
     <cntinfo>
       <cntorgp>
         <cntorg>Quantum Spatial, Inc.</cntorg>
         <cntper>Chris Guy</cntper>
       </cntorgp>
       <cntaddr>
         <addrtype>mailing and physical</addrtype>
         <address>4020 Technology Parkway</address>
         <city>Sheboygan</city>
         <state>WI</state>
         <postal>53083</postal>
         <country>USA</country>
       </cntaddr>
       <cntvoice>1-920-457-3631</cntvoice>
       <cntfax>1-920-457-0410</cntfax>
       <cntemail>cguy@quantumspatial.com</cntemail> 
       <hours>Monday through Friday 8:00 AM to 4:00 PM (Central Time)</hours> 
       
     </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>