<metadata>
 <idinfo>
 
  <citation>
   
   <citeinfo>
    
    <origin>The Atlantic Group, LLC</origin>
        
        <pubdate>Unknown</pubdate>
    
    <title>FR_2018_14SPH6030</title>
    
    <geoform>Raster</geoform>
    
   </citeinfo>
  </citation>
  <descript>
   
   <abstract>First Return DSM ERDAS .IMG format
		The State of Kansas Contract 0000000000000000000039891 required Leaf-off 2018 QL 2 LiDAR surveys to be collected over 54,663 square miles covering part or all of 86 counties in Kansas in support of the Kansas Department of Agriculture and Kansas Data Access and Support Center. Aerial LiDAR data for this task order was planned, acquired, processed and produced at an aggregate nominal pulse spacing (ANPS) of 0.71 meters and in compliance with USGS National Geospatial Program LiDAR Base Specification version 1.2.  Project Block 5 encompasses part or all of 7 counties in Southern Kansas and covers 3,079.2 square miles. </abstract>
   
   <purpose>The State of Kansas, on behalf of the Kansas Department of Agriculture and Kansas Data Access and Support Center, has contracted with Atlantic for professional services related to the development of Light Detection and Ranging (LiDAR). Additional partners include the USDA Natural Resource Conservation Service, the U.S. Geological Survey, the Kansas GIS Policy Board, the Kansas Department of Transportation and the Kansas Water Office. These LiDAR elevation data will be used for conservation planning, design, research, floodplain mapping, wetlands identification, dam safety assessments, hydrologic modeling, and subsidence monitoring.</purpose>
   
   <supplinf>
    	Raster File Type = ERDAS .IMG format
    	Bit Depth/Pixel Type = 32 bit floating point
    	Raster Cell Size = 1.0 meter
    	Interpolation or Resampling Technique = Bi-linear Interpolation
    	Required Vertical Accuracy = "24.5 cm nva" for 1.2 spec
  	
    
   </supplinf>
  </descript>
  <timeperd>
   
   <timeinfo>
    
    <rngdates>
     
     <begdate>20180118</begdate>
     
     <enddate>20180302</enddate>
     
    </rngdates>
   </timeinfo>
   <current>ground condition</current>
   
  </timeperd>
   <status>
      
      <progress>Complete</progress>
      
      <update>None Planned</update>
   
  </status>
  <spdom>
   
   <bounding>
        
        <westbc>-97.700715</westbc>
        
        <eastbc>-96.878083</eastbc>
        
        <northbc>38.525971</northbc>
        
        <southbc>37.388315</southbc>
        
      </bounding>
  
  </spdom>
   <keywords>
      
      <theme>
        
         <themekt>None</themekt>
    
    <themekey>Elevation</themekey>
		<themekey>LiDAR</themekey>
		<themekey>Relief</themekey>
		<themekey>Digital Terrain Model</themekey>
		<themekey>Intensity Imagery</themekey>
		<themekey>LAS</themekey>
		<themekey>Breakline</themekey>
        
      </theme>
      <place>
        
        <placekt>None</placekt>
        
        <placekey>Kansas</placekey>

        
      </place>
    </keywords>
    <accconst>No restrictions apply to this data the data represented is the result of data collection and processing per contract specifications and indicates the general existing conditions at the time of the data collection. As such, it is only valid for its intended use, content, time, and accuracy specifications. The user is responsible for the results of any application of the data for other than its intended purpose.</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 the limitations of the data. Acknowledgment of owner would be appreciated for products derived from these data.The data represented is the result of data collection and processing per contract specifications and indicates the general existing conditions at the time of the data collection. As such, it is only valid for its intended use, content, time, and accuracy specifications. The user is responsible for the results of any application of the data for other than its intended purpose.</useconst>
    
	
  </idinfo>
  <dataqual>
    
    <logic>All lidar data and lidar derived data covers the entire  area of interest. All lidar point cloud tiles show no edge artifacts or mismatches from tile to tile. Void areas (i.e. areas outside the project boundary but within the tiling scheme) are coded using a unique NODATA value. This value is identified in the appropriate location within the file header. Data cover the entire area specified for this project.</logic>
    
    <complete>Area of interest covers project area.  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 NVA specifications. Void areas (i.e., areas outside the project boundary but within the tiling scheme) are coded using a unique NODATA value. This value is identified in the appropriate location within the file header.</complete>
    
 <posacc>
      
      <vertacc>
        
        <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>
        
      </vertacc> 
    </posacc>
    <lineage>
      
     
      <procstep>
        
        <procdesc>Aircraft and Sensor Information and Flight Plan Execution
		Atlantic operated a Cessna (N732JE) outfitted with a Leica ALS70-HP LiDAR system during the collection of the project area.  Atlantic acquired 122 passes of the AOI as a series of perpendicular and/or adjacent flight-lines executed in 10 flight missions conducted between January 18, 2018 and March 2, 2018.  Onboard differential Global Navigation Satellite System (GNSS) unit(s) recorded sample aircraft positions at 2 hertz (Hz) or more frequency. LiDAR data was only acquired when a minimum of six (6) satellites were in view. 
		</procdesc>
              
        <procdate>20180429</procdate>
        

      </procstep>
      <procstep>
        
        <procdesc>Ground Control Survey
		A total of 115 ground survey points were collected in support of this project, including 38 LiDAR Control Points (LCP), 52 Non-vegetated Vertical Accuracy (NVA) and 25 Vegetated Vertical Accuracy (VVA). 

		Point cloud data accuracy was tested against a Triangulated Irregular Network (TIN) constructed from LiDAR points in clear and open areas.  A clear and open area can be characterized with respect to topographic and ground cover variation such that a minimum of five (5) times the Nominal Pulse Spacing (NPS) exists with less than 1/3 of the RMSEZ deviation from a low-slope plane. Slopes that exceed ten (10) percent were avoided.
 
		Each land cover type representing ten (10) percent or more of the total project area were tested and reported with a VVA. In land cover categories other than dense urban areas, the tested points did not have obstructions forty-five (45) degrees above the horizon to ensure a satisfactory TIN surface. The VVA value is provided as a target. It is understood that in areas of dense vegetation, swamps, or extremely difficult terrain, this value may be exceeded. 

		The NVA value is a requirement that must be met, regardless of any allowed &#8220;busts&#8221; in the VVA(s) for individual land cover types within the project. Checkpoints for each assessment (NVA and VVA) are required to be well-distributed throughout the land cover type, for the entire project area.  

		</procdesc>
        
        <procdate>20190429</procdate>
        
      </procstep>
	  
	   <procstep>
        
        <procdesc>LiDAR Point Cloud Generation
		Atlantic used Leica software products to download the IPAS ABGNSS/IMU data and raw laser scan files from the airborne system. Waypoint Inertial Explorer is used to extract the raw IPAS ABGNSS/IMU data, which is further processed in combination with controlled base stations to provide the final Smoothed Best Estimate Trajectory (SBET) for each mission. The SBETs are combined with the raw laser scan files to export the LiDAR ASCII Standard (*.las) formatted swath point clouds.
		</procdesc>
        
        <procdate>20191121</procdate>
        
      </procstep>
	  
	   <procstep>
        
        <procdesc>LiDAR Calibration
		Using a combination of GeoCue, TerraScan and TerraMatch; overlapping swath point clouds are corrected for any orientation or linear deviations to obtain the best fit swath-to-swath calibration. Relative calibration was evaluated using advanced plane-matching analysis and parameter corrections derived. This process was repeated interactively until residual errors between overlapping swaths, across all project missions, was reduced to &#8804;2cm. A final analysis of the calibrated lidar is preformed using a TerraMatch tie line report for an overall statistical model of the project area.  Individual control point assessments for this project can be found in Section VI of this report. 
		Upon completion of the data calibration, a complete set of elevation difference intensity rasters (dZ Orthos) are produced. A user-defined color ramp is applied depicting the offsets between overlapping swaths based on project specifications. The dZ orthos provide an opportunity to review the data calibration in a qualitative manner. Atlantic assigns green to all offset values that fall below the required RMSDz requirement of the project.  A yellow color is assigned for offsets that fall between the RMSDz value and 1.5x of that value. Finally, red values are assigned to all values that fall beyond 1.5x of the RMSDz requirements of the project.
		</procdesc>
        
        <procdate>20191121</procdate>
        
      </procstep>

	   <procstep>
        
        <procdesc>LiDAR Classification
			  Multiple automated filtering routines are applied to the calibrated LiDAR point cloud identifying and extracting bare-earth and above ground features. GeoCue, TerraScan, and TerraModeler software was used for the initial batch processing, visual inspection and any manual editing of the LiDAR point clouds. Atlantic utilized collected breakline data to preform classification for classes 9 (Water) and 10 (Ignored Ground). 
		Code	Description
		1	Unclassified
		2	Ground
		7	Low point (noise)
		9	Water
		10	Ignored ground (breakline proximity)
		17	Bridge
		18	High point (noise)
		</procdesc>
        
        <procdate>20191121</procdate>
        
      </procstep>
	  
	    <procstep>
        
        <procdesc>LiDAR Intensity Imagery
		LiDAR intensity imagery was created from the final calibrated and classified lidar point cloud. Intensity images were produced from all classified points and posted to a 0.5-meter cell size. Intensity images were cut to match the tile index and its corresponding tile names and delivered in .img format.
		</procdesc>
        
        <procdate>20191121</procdate>
        
      </procstep>
	     
	   <procstep>
        
        <procdesc>Hydro-line Collection/Conflation
		Hydro breaklines were compiled using LiDAR intensity data and surface terrain models of the entire project area. After the collection, all delineated hydro features were validated for monotonicity and vertical variance.  This procedure ensures that no points were floating above ground. Hydro-lines were then encoded into the LiDAR surface and used to hydro-enforce/flatten all significant water bodies. These final hydro-lines were then used in the production of bare Earth digital models to hydro flatten significant water bodies.  This product was delivered as an ESRI geodatabase for the entire project area.
		</procdesc>
        
        <procdate>20191121</procdate>
        
      </procstep>
	  
	  <procstep>
        
        <procdesc>Surface-Digital Elevation Model (DSM)
		Surface digital elevation models (DSMs) were derived using all first return LiDAR points, excluding LiDAR points classified as high or low noise. All DSMs were created with a grid spacing of 1 meter.  DSMs for this project were cut to match the tile index and its corresponding tile names and delivered in 32-bit floating point .img format.
		</procdesc>
        
        <procdate>20191121</procdate>
        
      </procstep>

    </lineage>
  </dataqual>
  
  <spdoinfo>
  
  <direct>raster</direct>
  
  <rastinfo>
      <rasttype>Pixel</rasttype>
      <rowcount>101</rowcount>
      <colcount>5000</colcount>
    </rastinfo>
 </spdoinfo>
 <spref>
    
        <horizsys>
      <planar>
        <mapproj>
          <mapprojn>NAD 1983 HARN UTM Zone 14N</mapprojn>
          <transmer>
            <sfctrmer>0.9996</sfctrmer>
            <longcm>-99.0</longcm>
            <latprjo>0.0</latprjo>
            <feast>500000.0</feast>
            <fnorth>0.0</fnorth>
          </transmer>
        </mapproj>
        <planci>
          <plance>coordinate pair</plance>
          <coordrep>
            <absres>0.0001</absres>
            <ordres>0.0001</ordres>
          </coordrep>
          <plandu>meter</plandu>
        </planci>
      </planar>
      <geodetic>
        <horizdn>D North American 1983 HARN</horizdn>
        <ellips>GRS 1980</ellips>
        <semiaxis>6378137.0</semiaxis>
        <denflat>298.257222101</denflat>
      </geodetic>
    </horizsys>
   <vertdef>
      
      <altsys>
        
        <altdatum>NAVD88</altdatum>
        
        <altres>1200</altres>
        
        <altunits>meter</altunits>
        
        <altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
        
      </altsys>
    </vertdef>
  </spref>

 <metainfo>
    
    <metd>20191221</metd>
    
    <metrd>20191221</metrd>
    
    <metc>
      
      <cntinfo>
        
            <cntorgp>
			 
              <cntorg>Atlantic</cntorg>
              <cntper>Benjamin Litter</cntper>
            </cntorgp>
            <cntpos>Project Manager</cntpos>
            <cntaddr>
              <addrtype>mailing and physical</addrtype>
              <address>2223 Drake Ave. SW Suite 200</address>
              <city>Huntsville</city>
              <state>AL</state>
              <postal>35805</postal>
              <country>USA</country>
            </cntaddr>
            <cntvoice>256.971.9991</cntvoice>
            <cntfax>256.971.1154</cntfax>
            <cntemail>Benjamin.Litter@atlantic.tech</cntemail>
          </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>