<?xml version="1.0" encoding="UTF-8"?>
<!--DOCTYPE metadata SYSTEM "fgdc-std-001-1998.dtd"-->
<metadata>
	<idinfo>
		<citation>
			<citeinfo>
				<pubdate>Unpublished Material</pubdate>
				<title>Kansas LiDAR Project AOI 1</title>
				<geoform>.LAS Lidar Format</geoform>
				<pubinfo><pubplace>None Available</pubplace><publish>None Available</publish></pubinfo><origin>Atlantic</origin></citeinfo>
		</citation>
		<descript>
			<abstract>This data set is consisting of QL2 LiDAR Point Cloud, Classified LiDAR, Digital Elevation Model (DEM), Digital Surface Model (DSM), and LiDAR Intensity Images which all pieces encompasses a 100 meter buffer around Kansas AOI 1 area, approximately 1708 square miles. Data set Description: This data set consists of LiDAR point cloud LAS swath files and tiled Las files. Each LAS file contains LiDAR point information, which has been calibrated, controlled, and classified.
Ground Conditions were as follows: water at normal levels; no unusual inundation; no snow; leaf off
USGS-NGP Base Lidar Specification v1.2
All Withhled (ignore) points were identified in the files using the standard LAS Withheld bit.

Class Code:0
Class Item:Never Classified
Class Code:1
Class Item:Undetermined/Unclassified
Class Code:2
Class Item:Bare Earth
Class Code:7
Class Item:Low Noise
Class Code:9
Class Item:Water
Class Code:10
Class Item:Ignored Ground
Class Code:17
Class Item:Bridges
Class Code:18
Class Item:High Noise</abstract>
			<lidar>
				<!--REQUIRED Section: for Project, Lift, and classified LAS metadata
					files
				-->
				<ldrinfo>
					<!--REQUIRED Group: This group of tags contains metadata about the
						sensor and collection conditions.
					-->
					<ldrspec>USGS-NGP Base Lidar Specification v1.2
						<!--REQUIRED Element: the lidar specification applicable to the
							point cloud
						-->
					</ldrspec>
					<ldrsens>Leica ALS70-HP
						<!--REQUIRED Element: the lidar sensor make and model -->
					</ldrsens>
					<ldrmaxnr>Unlimited
						<!--REQUIRED Element: the maximum number of returns per pulse -->
					</ldrmaxnr>
					<ldrnps>0.6
						<!--REQUIRED Element: the Nominal Pulse Spacing, in Meters -->
					</ldrnps>
					<ldrdens>2.78
						<!--REQUIRED Element: the Nominal Pulse Density, in Points Per
							Square Meter
						-->
					</ldrdens>
					<ldranps>0.5743 
						<!--REQUIRED Element: the Nominal Pulse Spacing, in Meters -->
					</ldranps>
					<ldradens>3.03
						<!--REQUIRED Element: the Nominal Pulse Density, in Points Per
							Square Meter
						-->
					</ldradens>
					<ldrfltht>2000
						<!--REQUIRED Element: the nominal flight height Above Mean Terrain
							for the collection, in Meters
						-->
					</ldrfltht>
					<ldrfltsp>125
						<!--REQUIRED Element: the nominal flight speed for the collection,
							in Knots
						-->
					</ldrfltsp>
					<ldrscana>40
						<!--REQUIRED Element: the sensor scan angle, total, in Degrees -->
					</ldrscana>
					<ldrscanr>34.5
						<!--REQUIRED Element: the scan frequency of the scanner, in Hertz
						-->
					</ldrscanr>
					<ldrpulsr>265.6
						<!--REQUIRED Element: the pulse rate of the scanner, in Kilohertz
						-->
					</ldrpulsr>
					<ldrpulsd>4
						<!--REQUIRED Element: the pulse duration of the scanner, in
							Nanoseconds
						-->
					</ldrpulsd>
					<ldrpulsw>0.46
						<!--REQUIRED Element: the pulse width of the scanner, in Meters -->
					</ldrpulsw>
					<ldrwavel>1064
						<!--REQUIRED Element: the central wavelength of the sensor laser, in
							Nanometers
						-->
					</ldrwavel>
					<ldrmpia>1
						<!--REQUIRED Element: Whether the sensor was operated with Multiple
							Pulses In The Air, 0=No; 1=Y
						-->
					</ldrmpia>
					<ldrbmdiv>0.15
						<!--REQUIRED Element: the beam divergence, in Milliradians -->
					</ldrbmdiv>
					<ldrswatw>1657
						<!--REQUIRED Element: the nominal swath width on the ground, in
							Meters
						-->
					</ldrswatw>
					<ldrswato>20
						<!--REQUIRED Element: the nominal swath overlap, as a Percentage
						-->
					</ldrswato>
					<ldrgeoid>National Geodetic Survey (NGS) Geoid12A
						<!--REQUIRED Element: Geoid used for vertical reference. -->
					</ldrgeoid>
				</ldrinfo>
				<ldraccur>
					<!--REQUIRED Group: This group of tags contains information on point
						cloud accuracy. Not all tags within this group are mandatory. The
						NVA of the raw point cloud is required. A VVA value for the
						classified point cloud is optional, but is required to be reported
						if it is available.
						ALL Values are reported in Meters.
					-->
					<ldrchacc>0.196
						<!--REQUIRED Element: the required nonvegetated vertical accuracy
							(NVA) for the point cloud data.
							If none specified, enter 0.
						-->
					</ldrchacc>
					<rawnva>0.084
						<!--REQUIRED Element: the calculated nonvegetated vertical accuracy
							of the raw point cloud data
						-->
					</rawnva>
					<rawnvan>58
						<!--REQUIRED Element: the number of check points used to calculate
							the reported nonvegetated vertical accuracy of the raw point cloud
							data
						-->
					</rawnvan>
					<clsnva>0.103
						<!--OPTIONAL Element: the calculated nonvegetated vertical accuracy
							of the classified point cloud data (required if available)
						-->
					</clsnva>
					<clsnvan>58
						<!--REQUIRED Element: the number of check points used to calculate
							the reported nonvegetated vertical accuracy of the classified
							point cloud data (required if available)
						-->
					</clsnvan>
					<clsvva>0.131
						<!--OPTIONAL Element: the calculated vegetated vertical accuracy of
							the classified point cloud data (required if available)
						-->
					</clsvva>
					<clsvvan>52
						<!--OPTIONAL Element: the number of check points used to calculate
							the vegetated vertical accuracy of the classified point cloud data
							(required if available)
						-->
					</clsvvan>
				</ldraccur>
				<lasinfo>
					<!--REQUIRED Group: This group of tags contains information on the
						LAS version and classification values for the point cloud.
					-->
					<lasver>1.4
						<!--REQUIRED Element: The version of the LAS Standard applicable to
							this dataset.
						-->
					</lasver>
					<lasprf>6
						<!--REQUIRED Element: The Point Data Record Format used for the
							point cloud.
						-->
					</lasprf>
					<laswheld>Withhled (ignore) points were identified in the files using the standard LAS Withheld bit.
						<!--REQUIRED Element: Describe how withheld points are identified.
						-->
					</laswheld>
					<lasolap>Swath “overage” points were identified in these files using the standard LAS overlap bit.
						<!--REQUIRED Element: This element describes how overage points are
							identified.
						-->
					</lasolap>
					<lasintr>16
						<!--REQUIRED Element: This element specifies the native radiometric
							resolution of intensity values, in Bits.
						-->
					</lasintr>
					<lasclass>
						<clascode>0</clascode>
						<clasitem>Never Classified</clasitem>
					</lasclass>
					<lasclass>
						<!--REQUIRED Section if LAS data are classified: Each lasclass
							section provides a code value and a description for that code.
						-->
						<clascode>1</clascode>
						<!--REQUIRED Element: This element specifies classification code.
								Domain: positive integer between 0 and 255
							-->
						<clasitem>Undetermined/Unclassified</clasitem>
						<!--REQUIRED Element: This element describes the object
								identified by the classification code; the type of object from
								which the lidar point was reflected, or the status of the
								classification of point.
								Domain: free text
							-->
					</lasclass>
					<lasclass>
						<clascode>2</clascode>
						<clasitem>Bare earth</clasitem>
					</lasclass>
					<lasclass>
						<clascode>7</clascode>
						<clasitem>Low Noise</clasitem>
					</lasclass>
					<lasclass>
						<clascode>9</clascode>
						<clasitem>Water</clasitem>
					</lasclass>
					<lasclass>
						<clascode>10</clascode>
						<clasitem>Ignored Ground</clasitem>
					</lasclass>
					<lasclass>
						<clascode>17</clascode>
						<clasitem>Bridges</clasitem>
					</lasclass>
					<lasclass>
						<clascode>18</clascode>
						<clasitem>High Noise</clasitem>
					</lasclass>
				</lasinfo>
			</lidar>
			<purpose>The Kansas Department of Agriculture and Kansas Data Access and Support Center to obtain professional services related to the development of Light Detection and Ranging (LiDAR) data between October 2014 and March 2015.  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>All Lidar data was acquired, calibrated, and used in the creation of Lidar derived products by Atlantic.</supplinf></descript>
		<timeperd>
			<timeinfo>
				<!--REQUIRED Group: Time info: will be either:
					single date,
					OR multiple dates,
					OR a range of dates.
					Examples are provided for all three formats.
					Delete the ones that do not apply.
				-->
				<rngdates><begdate>20150224</begdate><begtime>0800</begtime><enddate>20150306</enddate><endtime>1200</endtime></rngdates></timeinfo>
			<current>ground condition</current>
		</timeperd>
		<status>
			<progress>Complete</progress>
			<update>As needed</update>
		</status>
		<spdom>
			<bounding>
				<westbc>-95.995625752</westbc>
				<eastbc>-94.969234879</eastbc>
				<northbc>39.451657071</northbc>
				<southbc>38.686518908 </southbc>
			</bounding>
		</spdom>
		<keywords>
			<theme><themekt>None</themekt><themekey>Elevation Data</themekey><themekey>LiDAR</themekey><themekey>DEM</themekey><themekey>DSM</themekey><themekey>Intensity Image</themekey></theme><place><placekt>None</placekt><placekey>AOI 1</placekey><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. Acknowledgement of the Kansas Department of Agriculture 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>
		<ptcontac>
			<cntinfo>
				<cntorgp>
					<cntorg>Kansas Department of Agriculture</cntorg>
					<cntper>Tom Morey</cntper>
				</cntorgp>
				<cntaddr>
					<addrtype>mailing and physical address</addrtype>
					<city>Topeka</city>
					<state>KS</state>
					<postal>66619</postal>
					<country>USA</country>
					<address>6531 SE Forbes Avenue Suit B</address></cntaddr>
				<cntvoice>785-296-5440</cntvoice>
				<cntemail>tom.morey@kda.ks.gov</cntemail>
				<hours>Monday through Friday 8:00 AM to 4:00 PM </hours>
				<cntinst>If unable to reach the contact by telephone, please send an email. You should get a response within 24 hours.		</cntinst>
				<cntpos>State NFIP Coordinator</cntpos></cntinfo>
		</ptcontac>
		<native>CloudPro 1.2.0 Build 85620; GeoCue Version 2014.1.21.2; Windows 7 Operating System
\\lidarsrv\GC_Warehouse_5\80658\30\*.las
184 GB</native>
		<datacred>Tom Morey
Kansas Department of Agriculture
State NFIP Coordinator
785-296-5440
tom.morey@kda.ks.gov</datacred><secinfo><secsys>None Available Contact kansas Department of Agriculture</secsys><secclass>None Available Contact kansas Department of Agriculture</secclass><sechandl>None Available Contact kansas Department of Agriculture</sechandl></secinfo></idinfo>
	<dataqual>
		<logic>All LiDAR data and LiDAR Derived products cover the entire 1708 square mile Area of Interest for AOI 1 that has been completed. 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 covers the entire area specified for AOI 1.</logic>
		<complete>The raw LAS data files included 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 Fundamental Vertical Accuracy 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>Vertical Accuracy of the point cloud and bare-earth lidar data was assessed and reported in accordance with the ASPRS Positional Accuracy Standards for Digital Geospatial Data;
A hundred and ten (110) surveyed points were measured for the purpose of assessing the accuracy of the Kansas Lidar, AOI 01 data. (58 NVA + 52 VVA). Both data sets, Lidar and Digital Elevation Models (DEMs) have been tested for there individual vertical accuracy levels. The Lidar was tested by using interpolation while the DEMs where tested by extracting the elevation of a pixel containing the checkpoint. All DEM Vertical accuracy results are reported in the DEM metadata reports while this project wide metadata file is reporting the vertical accuracy results from the the source Lidar. Required Vegetated Vertical Accuracy (VVA): 0.294(m), Required Non-Vegetated Vertical Accuracy (NVA): 0.196(m)</vertaccr>
				<qvertpa>
					<vertaccv>10.3 cm</vertaccv>
					<vertacce>This data set was tested at ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 10.0(cm) RMSEz Vertical Accuracy Class. Actual NVA accuracy of the bare-earth was found to be RMSEz = 5.3 cm, equating to +/-10.3 cm at 95% confidence level.</vertacce>
				</qvertpa>
				<qvertpa><vertaccv>13.1 cm</vertaccv><vertacce>This data set was tested at ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 10.0(cm) RMSEz Vertical Accuracy Class. Actual VVA accuracy was found to be +/-13.1 cm at the 95th percentile.</vertacce></qvertpa></vertacc>
			<horizpa><horizpar>Horizontal error in LiDAR derived elevation data is largely a function of positional error as derived from the Global Navigation Satellite System (GNSS), attitude (angular orientation) error (as derived from the INS) and flying altitude; and can be estimated based on these parameters</horizpar><qhorizpa><horizpav>13.0 cm</horizpav><horizpae>As described in Section 7.5 of the ASPRS Positional Accuracy Standards for Digital Geospatial Data the horizontal errors in lidar data are largely a function of GNSS positional error, INS angular error, and flying altitude. Therefore lidar data collected with GNSS error of 0.05m and the IMU error of 0.03492 degrees at an altitude of 6650 feet MSL; the expected radial horizontal positional error will be RMSEr = 13.0cm.</horizpae></qhorizpa></horizpa></posacc>
		<lineage>
			<srcinfo>
				<!--The srcinfo section of the metadata MUST be repeated for each data
					source that contributed to making this unclassified LAS swath dataset,
					including, but not limited to, 1) ground control used for calibrating
					the lidar data, 2) the actual lidar acquisition data, and 3)
					independent ground control used to assess the accuracy of the lidar
					point cloud.
				-->
				<srccite>
					<citeinfo>
						<pubdate>Unpublished Material</pubdate>
						<title>Kansas LiDAR AOI 1</title>
						<geoform>vector digital data</geoform>
						<pubinfo>
							<pubplace>None Available</pubplace><publish>None Available</publish></pubinfo>
						<othercit> None Available</othercit>
						<pubtime>0800</pubtime><origin>Atlantic</origin></citeinfo>
				</srccite>
				<srcscale>1200</srcscale>
				<typesrc>Portable Hard Drive</typesrc>
				<srctime>
					<timeinfo>
						<rngdates><begdate>20150303</begdate><begtime>1200</begtime><enddate>20150306</enddate><endtime>1200</endtime></rngdates></timeinfo>
					<srccurr>ground condition</srccurr>
				</srctime>
				<srccontr>This data source was used (along with the airborne GPS/IMU Data) to georeferencing of the lidar point cloud data used to create all contracted LiDAR deriveted products. Version of the LAS Standard 1.4 / point data record format 6.</srccontr>
				<srccitea>Kansas LiDAR (AOI 1)</srccitea></srcinfo>
			<procstep><proccont><cntinfo><cntorgp><cntorg>Atlantic</cntorg><cntper>H. Alan Kimbrough</cntper></cntorgp><cntpos>Survey Manager</cntpos><cntaddr><addrtype>mailing and physical address</addrtype><address>2223 Drake Ave. SW Suite 200</address><city>Huntsville</city><state>AL</state><postal>35805</postal><country>United States</country></cntaddr><cntvoice>256-971-9991</cntvoice><cntfax>256-971-1154</cntfax><cntemail>hakimbrough@theatlgrp.com</cntemail><hours>8:00 - 5:00 </hours></cntinfo></proccont><procdesc>Aerial LiDAR Acquisition: Aerial data collection was acquired, in 27 missions ending on March 20th 2015 , using the ALS70 SN#7123. This was to support a 2.5 ppm^2 LiDAR point cloud. Airborne GPS and IMU data was collected during the acquisition and supported by Topcon Viper GPS for Set point KNOX_SET, Data acquisition was completed on March 20th 2015. 

Ground Control Survey: A survey was performed to support the acquisition of Light Detection and Ranging (LiDAR). The control network involved a total of 37 control points and 110 check points (58 NVA and 52 VVA). The check points were a combination of the following ground cover classification: Bare Earth, Open Terrain, Urban Terrain, Brush, High Grass and Low Trees. All control point survey observations were conducted utilizing Leica SR530. All check point survey observations were conducted with a Topcon GRS-1 VRS capable unit. All VRS survey sessions began and ended with redundant occupations against known NGS point values to validate the accuracy and repeat-ability of the survey.</procdesc><procdate>20150306</procdate><proctime>0800</proctime></procstep><procstep><procdesc>LiDAR Pre-processing: Airborne GPS and IMU data were merged to develop a Single Best Estimate (SBET) of the LiDAR system trajectory for each lift. LiDAR ranging data were initially calibrated using previous best parameters for this instrument and aircraft. 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 lifts, was reduced to 2 cm or less. Data were then block adjusted to match surveyed calibration control. Raw data NVA were checked using independently surveyed check points. Swath overage points were identified and tagged within each swath file</procdesc><proccont><cntinfo><cntorgp><cntorg>Atlantic</cntorg><cntper>Chris Cannon</cntper></cntorgp><cntpos>Associate Vice President Production Manager</cntpos><cntaddr><addrtype>mailing and physical address</addrtype><address>2223 Drake Ave. SW Suite 200</address><city>Huntsville</city><state>AL</state><postal>35805</postal><country>United States</country></cntaddr><cntvoice>256-971-9991</cntvoice><cntfax>256-971-1154</cntfax><cntemail>jccannon@theatlgrp.com</cntemail><hours>8:00 - 5:00</hours></cntinfo></proccont><procdate>20150310</procdate><proctime>0800</proctime></procstep><procstep><proccont><cntinfo><cntorgp><cntorg>Atlantic</cntorg><cntper>Chirs Cannon</cntper></cntorgp><cntpos>Associate Vice President Production Manager</cntpos><cntaddr><addrtype>mailing and physical address</addrtype><address>2223 Drake Ave. SW Suite 200</address><city>Huntsville</city><state>AL</state><postal>35805</postal><country>United States</country></cntaddr><cntvoice>256-971-9991</cntvoice><cntfax>256-971-1154</cntfax><cntemail>jccannon@theatlgrp.com</cntemail><hours>8:00 - 5:00</hours></cntinfo></proccont><procdesc>Initial processing of the GPS data was processed using Inertial Explorer. The solution file was generated and CloudPro software was used to generate georeferenced laser returns which were then processed in strip form allowing for the QC of the overlap between strips (lines). The data from each line were combined and automated classification routines run to determine the initial surface model. This initial surface model was then verified to the surveyed test points.</procdesc><procdate>20150315</procdate><proctime>0800</proctime></procstep><procstep><proccont><cntinfo><cntorgp><cntorg>Atlantic</cntorg><cntper>Chris Cannon</cntper></cntorgp><cntpos>Associate Vice President Production Manager</cntpos><cntaddr><addrtype>mailing and physical address</addrtype><address>2223 Drake Ave. SW Suite 200</address><city>Huntsville</city><state>AL</state><postal>35805</postal><country>United States</country></cntaddr><cntvoice>256-971-9991</cntvoice><cntfax>256-971-1154</cntfax><cntemail>jccannon@theatlgrp.com</cntemail><hours>8:00 - 5:00</hours></cntinfo></proccont><procdesc>LiDAR Post-Processing: The calibrated and controlled LiDAR swaths were processed using automatic point classification routines in TerraSolid software. These routines operate against the entire collection (all swaths, all lifts), eliminating character differences between files. Data were then distributed as virtual tiles to experienced LiDAR analysts for localized automatic classification, manual editing, and peer-based QC checks. Supervisory QC monitoring of work in progress and completed editing ensured consistency of classification character and adherence to project requirements across the entire project. All classification tags are stored in the original swath files. After completion of classification and final QC approval, the NVA and VVA for the project are calculated. Sample areas for each land cover type present in the project were extracted and forwarded to the client, along with the results of the accuracy tests. Upon acceptance, the complete classified LiDAR swath files were delivered to the client.
</procdesc><procdate>20150315</procdate><proctime>0800</proctime></procstep><procstep><proccont><cntinfo><cntorgp><cntorg>Atlantic</cntorg><cntper>Chris Cannon</cntper></cntorgp><cntpos>Associate Vice President Production Manager</cntpos><cntaddr><addrtype>mailing and physical address</addrtype><address>2223 Drake Ave. SW Suite 200</address><city>Huntsville</city><state>AL</state><postal>35805</postal><country>United States</country></cntaddr><cntvoice>256-971-9991</cntvoice><cntfax>256-971-1154</cntfax><cntemail>jccannon@theatlgrp.com</cntemail><hours>8:00 - 5:00</hours></cntinfo></proccont><procdesc>LiDAR Classification:  The calibrated LiDAR data was run through automated classification routines and then manually checked and edited. The data was classified into the following classes:  1-unclassified*, 2-ground, 7-low noise, 9-water, 10-buffer, 17-bridges, and 18-high noise.</procdesc><procdate>20150401</procdate><proctime>0800</proctime></procstep><procstep><proccont><cntinfo><cntorgp><cntorg>Atlantic</cntorg><cntper>Chris Cannon</cntper></cntorgp><cntpos>Associate Vice President Production Manager</cntpos><cntaddr><addrtype>mailing and physical address</addrtype><address>2223 Drake Ave. SW Suite 200</address><city>Huntsville</city><state>AL</state><postal>35805</postal><country>United States</country></cntaddr><cntvoice>256-971-9991</cntvoice><cntfax>256-971-1154</cntfax><cntemail>jccannon@theatlgrp.com</cntemail><hours>8:00 - 5:00 </hours></cntinfo></proccont><procdesc>LiDAR Intensity Imagery Creation: All LiDAR Intensity Imagery was created from the final calibrated and classified LiDAR Point Cloud. Intensity Images where produced from all classified points and are posted to a 1 meter cell size. Intensity Images where cut to match the provided Kansas Department of Agriculture Tile Index and have corresponding names to match tile names.</procdesc><proctime>20150401</proctime><procdate>20150401</procdate></procstep><procstep><proccont><cntinfo><cntorgp><cntorg>Atlantic</cntorg><cntper>Chris Cannon</cntper></cntorgp><cntpos>Associate Vice President Production Manager</cntpos><cntaddr><addrtype>mailing and physical address</addrtype><address>2223 Drake Ave. SW Suite 200</address><city>Huntsville</city><state>AL</state><postal>35805</postal><country>United States</country></cntaddr><cntvoice>256-971-9991</cntvoice><cntfax>256-971-1154</cntfax><cntemail>jccannon@theatlgrp.com</cntemail><hours>8:00 - 5:00</hours></cntinfo></proccont><procdesc>Hydro line Collection: Hydro break lines were compiled using the LiDAR intensity data and surface terrain model of the entire project area. After the collection of hydro lines all features were validated for monotonicity and vertical variance, to ensure that no points were floating above ground. The hydro break lines were 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 and Contours to hydro flatten significant water bodies.</procdesc><procdate>20150410</procdate><proctime>0800</proctime></procstep><procstep><proccont><cntinfo><cntorgp><cntorg>Atlantic</cntorg><cntper>Chris Cannon</cntper></cntorgp><cntpos>Assocaite Vice President Production Manager</cntpos><cntaddr><addrtype>mailing and physical address</addrtype><address>2223 Drake Ave. SW suite 200</address><city>Huntsville</city><state>Al</state><postal>35805</postal><country>United States</country></cntaddr><cntvoice>256-971-9991</cntvoice><cntfax>256-971-1154</cntfax><cntemail>jccannon@theatlgrp.com</cntemail><hours>8:00 - 5:00</hours></cntinfo></proccont><procdesc>Bare-Earth DEM Creation: Bare-Earth Digital Elevation Models (DEMs) were derived using the hydro break line and bare-earth (ground) LiDAR points, all DEMs were created with a grid spacing of 1 meter. The DEMs were cut to tiles of 5000 meters X 5000 meters index, provided by the Kansas Department of Agriculture.</procdesc><procdate>20150501</procdate><proctime>0800</proctime></procstep><procstep><proccont><cntinfo><cntorgp><cntorg>Atlantic</cntorg><cntper>Chris Cannon</cntper></cntorgp><cntpos>Associate Vice President Production Manager</cntpos><cntaddr><addrtype>mailing and physical address</addrtype><address>2223 Drake Ave. SW Suite 200</address><city>Huntsville</city><state>AL</state><postal>35805</postal><country>United States</country></cntaddr><cntvoice>256-971-9991</cntvoice><cntfax>256-971-1154</cntfax><cntemail>jccannon@theatlgrp.com</cntemail><hours>8:00 - 5:00</hours></cntinfo></proccont><procdesc>First Return DSM Creation: First Return DSMs were created using First Return LiDAR data, at a grid spacing of 1 meter X 1 meter. The DSMs were then tiled out to 5000 meter X 5000 meter index, provided by the Kansas Department of Agriculture.</procdesc><procdate>20150501</procdate><proctime>0800</proctime></procstep></lineage>
		<cloud>0</cloud><attracc><attraccr>Required Non-Vegetated Vertical Accuracy (NVA) for the Point Cloud:0.196 
Calculated Non-Vegetated Vertical Accuracy (NVA) for the Point Cloud:0.084
Number of Check Points used to calculate the Reported (NVA) for the RAW Point Cloud:58
Calculated (NVA) of the Classified Point Cloud:0.103
Number of Check Points used to calculate the Reported (NVA) for the Classified Point Cloud:58
Required Vegetated Vertical Accuracy (VVA): 0.294 
Calculated (VVA) of the Classified Point Cloud:0.131
Number of Check Points used to calculate the Reported (VVA) for the Classified Point Cloud:52</attraccr></attracc></dataqual>
	<spdoinfo>
		<direct>Point</direct>
		<ptvctinf><sdtsterm><sdtstype>Point</sdtstype><ptvctcnt>18109370370</ptvctcnt></sdtsterm></ptvctinf></spdoinfo>
	<spref>
		<horizsys>
			<planar>
				<gridsys>
					<!--REQUIRED Section: The section should be filled out with the
							relevant parameters for the coordinate reference system for the
							data. Usually it will be UTM or a State Plane Zone. Delete the
							irrelevant section below.
						-->
					<gridsysn>Universal Transverse Mercator</gridsysn>
					<utm><utmzone>15</utmzone><transmer><sfctrmer>0.99960000</sfctrmer><longcm>-93.00000000</longcm><latprjo>0.00000000</latprjo><feast>500000.00000000</feast><fnorth>0.00000000</fnorth></transmer></utm></gridsys>
				<planci>
					<plance>coordinate pair</plance>
					<!--REQUIRED Element: Planar Coordinate Encoding Method - the means
							used to represent horizontal positions.
							Domain: : "coordinate pair" "distance and bearing" "row and column"
							free text
						-->
					<coordrep>
						<absres>1.0</absres>
						<ordres>1.0</ordres>
					</coordrep>
					<plandu>meters</plandu>
				</planci>
			</planar>
			<geodetic>
				<horizdn>North American Datum of 1983 (HARN)</horizdn>
				<ellips>Geodetic Reference System 80</ellips>
				<semiaxis>6378137.0</semiaxis>
				<denflat>298.257222101</denflat>
			</geodetic>
		</horizsys>
		<vertdef>
			<altsys>
				<altdatum>North American Vertical Datum of 1988 (Geoid12A)</altdatum>
				<altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
				<altres>1200</altres><altunits>meters</altunits></altsys>
		</vertdef>
	</spref>
	<eainfo>
		<!--OPTIONAL Section: Entity and Attribute Information
				THIS SECTION IS NOT REQUIRED FOR LIDAR LAS DELIVERABLES.
				This section is only required for deliverable data classified as a
				Feature Class.
			-->
		<overview><eaover>LiDAR Tiles and associated derived products for Kansas AOI 1</eaover><eadetcit>LiDAR Tiles and associated derived products for Kansas AOI 1</eadetcit></overview></eainfo>
	<distinfo>
		<!--OPTIONAL Section: Distribution Information: Information about the distributor
				of and options for obtaining the dataset.
				THIS SECTION SHOULD ONLY BE POPULATED IF SOME ORGANIZATION OTHER THAN
				USGS HAS DISTRIBUTION RIGHTS TO THE DATA.
			-->
		<distrib>
			<cntinfo>
				<cntorgp>
					<cntorg>Kansas Department of Agriculture</cntorg>
					<cntper>Tom Morey</cntper>
				</cntorgp>
				<cntaddr>
					<addrtype>mailing and physical address</addrtype>
					<address>6531 SE Forbes Ave. Suit B</address>
					<city>Topeka</city>
					<state>KS</state>
					<postal>66619</postal>
					<country>United States</country>
				</cntaddr>
				<cntvoice>785-296-5440</cntvoice>
				<cntemail>tom.morey@kda.ks.gov</cntemail>
				<cntpos>NFIP Coordinator</cntpos><hours>8:00 am - 5:00 pm</hours></cntinfo>
		</distrib>
		<resdesc>No formal constraints although the present data set does belong to Kansas Department of Agriculture and more information can be obtained by contacting Kansas Department of Agriculture at: 

Tom Morey
NFIP Coordinator
785-296-5440
tom.morey@kda.ks.gov</resdesc>
		<distliab>The data represented is the result of data collection and processing per contract specifications and indicates the general existing conditions at the time of 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.</distliab>
		<stdorder><nondig>No formal constraints although the present data set does belong to Kansas Department of Agriculture and more information can be obtained by contacting Kansas Department of Agriculture at: 

Tom Morey
NFIP Coordinator
785-296-5440
tom.morey@kda.ks.gov</nondig><fees>Contact Kansas Department of Agriculture</fees><ordering>No formal constraints although the present data set does belong to Kansas Department of Agriculture and more information can be obtained by contacting Kansas Department of Agriculture at: 

Tom Morey
NFIP Coordinator
785-296-5440
tom.morey@kda.ks.gov</ordering><turnarnd>Contact Kansas Department of Agriculture</turnarnd></stdorder><custom>No formal constraints although the present data set does belong to Kansas Department of Agriculture and more information can be obtained by contacting Kansas Department of Agriculture at: 

Tom Morey
NFIP Coordinator
785-296-5440
tom.morey@kda.ks.gov</custom><techpreq>No formal constraints although the present data set does belong to Kansas Department of Agriculture and more information can be obtained by contacting Kansas Department of Agriculture at: 

Tom Morey
NFIP Coordinator
785-296-5440
tom.morey@kda.ks.gov</techpreq><availabl><timeinfo><sngdate><caldate>20150815</caldate><time>0800</time></sngdate></timeinfo></availabl></distinfo>
	<metainfo>
		<!--REQUIRED Section: Metadata Reference Information: Information on the
			currentness of the metadata information, and the party responsible for
			the metadata.
		-->
		<metd>20150812</metd>
		<metrd>20150812</metrd>
		<metc>
			<cntinfo>
				<cntorgp>
					<cntorg>Kansas Department of Agriculture</cntorg>
					<cntper>Tom Morey</cntper>
				</cntorgp>
				<cntaddr>
					<addrtype>mailing and physical address</addrtype>
					<address>6531 SE Forbes Ave. Suite B</address>
					<city>Topeka</city>
					<state>KS</state>
					<postal>66619</postal>
					<country>United States</country>
				</cntaddr>
				<cntvoice>785-296-5440</cntvoice>
				<cntemail>tom.morey@kda.ks.gov</cntemail>
				<hours>Monday through Friday 8:00 AM to 5:00 PM</hours>
				<cntinst> If unable to reach the contact by telephone, please send an email. You should get a response within 24 hours.		</cntinst>
				<cntpos>NFIP Coordinator</cntpos></cntinfo>
		</metc>
		<metstdn>FGDC Content Standards for Digital Geospatial Metadata</metstdn>
		<metstdv>FGDC-STD-001-1998</metstdv>
		<metac>No formal constraints although the present data set does belong to Kansas Department of Agriculture and more information can be obtained by contacting Kansas Department of Agriculture at: 

Tom Morey
NFIP Coordinator
785-296-5440
tom.morey@kda.ks.gov</metac>
		<metuc>No formal constraints although the present data set does belong to Kansas Department of Agriculture and more information can be obtained by contacting Kansas Department of Agriculture at: 

Tom Morey
NFIP Coordinator
785-296-5440
tom.morey@kda.ks.gov</metuc>
		<metsi>
			<metscs>None</metscs>
			<metsc>Unclassified</metsc>
			<metshd>No formal constraints although the present data set does belong to Kansas Department of Agriculture and more information can be obtained by contacting Kansas Department of Agriculture at: 

Tom Morey
NFIP Coordinator
785-296-5440
tom.morey@kda.ks.gov</metshd>
		</metsi>
		<metfrd>20150812</metfrd><mettc>local time</mettc></metainfo>
</metadata>
