<?xml version="1.0" encoding="UTF-8"?>
<metadata>
	<idinfo>
		<citation>
			<citeinfo>
				<origin>Digital Aerial Solutions, LLC</origin>
				<pubdate>Unpublished Material</pubdate>
				<title>Classifed LAS, IA_SouthCentral_2020_D20</title>
				<geoform>.LAS Lidar format</geoform>
				<pubinfo>
					<pubplace>None Available</pubplace>
					<publish>None Available</publish>
				</pubinfo>
			</citeinfo>
		</citation>
		<descript>
			<abstract>The Project data set consists of the Classified Point Cloud. The Geographical Extent of this data set extends to the entirety of the IA_SouthCentral_2020_D20_QL2 UTM Zone 15N  boundary, approximately 10,238 square miles of the AOIs. Ground Conditions: water at normal levels; no unusual inundation; no snow; leaf off. How the Withheld Points are Identified: Withheld (ignore) points were identified in the files using the standard LAS Withheld bit.</abstract>
			<purpose>The USGS/NRCS/IDALS contracted Digital Aerial Solutions, LLC to obtain professional services related to the planning, acquisition and development of Light Detection and Ranging (Lidar) data and derivative products. The task order is for a QL2 LiDAR survey to be collected over Adair, Appanoose, Clarke, Davis, Decatur, Iowa, Jefferson, Keokuk, Lucas, Madison, Mahaska, Marion, Monroe, Poweshiek, Ringgold, Union, Van Buren, Wapello, Warren and Wayne counties in Iowa. The deliverable products would be used by the USGS/NRCS/IDALS for conservation planning, design, research, floodplain mapping, wetlands identification, dam safety assessments, hydrologic modeling, and other environmental purposes.</purpose>
			<supplinf>All Lidar data and associated products were acquired, calibrated, and used in the creation of Lidar derived products by Digital Aerial Solutions, LLC.
ANPS: 0.71 Meters
Tile Size: 1,000 Meters
Spec: National Geospatial Program(NGP) Lidar Base Specification v2.1
LAS File Type: 1.4 type 6</supplinf>
			<lidar>
				<ldrinfo>
					<ldrspec>U.S. Geological Survey (USGS) - National Geospatial Program(NGP) Lidar Base Specification v2.1</ldrspec>
					<ldrsens>Leica Terrian SN# 90524</ldrsens>
					<ldrmaxnr>15</ldrmaxnr>
					<ldrnps>0.58</ldrnps>
					<ldrdens>3.02</ldrdens>
					<ldranps>0.58</ldranps>
					<ldradens>3.02</ldradens>
					<ldrfltht>6562</ldrfltht>
					<ldrfltsp>155</ldrfltsp>
					<ldrscana>40.0</ldrscana>
					<ldrscanr>150.0</ldrscanr>
					<ldrpulsr>550.0</ldrpulsr>
					<ldrpulsd>3</ldrpulsd>
					<ldrpulsw>0.47</ldrpulsw>
					<ldrwavel>1064</ldrwavel>
					<ldrmpia>0</ldrmpia>
					<ldrbmdiv>0.15</ldrbmdiv>
					<ldrswatw>1455.88</ldrswatw>
					<ldrswato>30</ldrswato>
					<ldrgeoid>National Geodetic Survey (NGS) Geoid 18</ldrgeoid>
				</ldrinfo>
				<ldraccur>
					<ldrchacc>0.620</ldrchacc>
					<rawnva>0.088</rawnva>
					<rawnvan>210</rawnvan>
					<clsnva>0.088</clsnva>
					<clsnvan>210</clsnvan>
					<clsvva>0.196</clsvva>
					<clsvvan>145</clsvvan>
				</ldraccur>
				<lasinfo>
					<lasver>1.4</lasver>
					<lasprf>6</lasprf>
					<laswheld>Withheld (ignore) points were identified in the 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>Undetermined/Unclassified</clasitem>
					</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>17</clascode>
						<clasitem>Bridges</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>
				<sngdate>
					<caldate>20200330</caldate>
				</sngdate>
			</timeinfo>
			<current>ground condition</current>
		</timeperd>
		<status>
			<progress>Complete</progress>
			<update>As needed</update>
		</status>
		<spdom>
			<bounding>
				<westbc>-94.735009</westbc>
				<eastbc>-91.686570</eastbc>
				<northbc>41.875921</northbc>
				<southbc>40.557255</southbc>
			</bounding>
			<lboundng>
				<leftbc>356000.000000</leftbc>
				<rightbc>609000.000000</rightbc>
				<topbc>4636000.000000</topbc>
				<bottombc>4491000.000000</bottombc>
			</lboundng>
		</spdom>
		<keywords>
			<theme>
				<themekt>None</themekt>
				<themekey>Elevation Data</themekey>
				<themekey>Lidar</themekey>
			</theme>
			<place>
				<placekt>None</placekt>
				<placekey>Adair</placekey>
				<placekey>Appanoose</placekey>
				<placekey>Clarke</placekey>
				<placekey>Davis</placekey>
				<placekey>Decatur</placekey>
				<placekey>Iowa</placekey>
				<placekey>Jefferson</placekey>
				<placekey>Keokuk</placekey>
				<placekey>Lucas</placekey>
				<placekey>Madison</placekey>
				<placekey>Mahaska</placekey>
				<placekey>Marion</placekey>
				<placekey>Monroe</placekey>
				<placekey>Poweshiek</placekey>
				<placekey>Ringgold</placekey>
				<placekey>Union</placekey>
				<placekey>Van Buren</placekey>
				<placekey>Wapello</placekey>
				<placekey>Warren</placekey>
				<placekey>Wayne</placekey>
				<placekey>IA</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 data set 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 the US Geological Survey 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>
		<native>Inertial Explorer ver: 8.9;GeoCue Ver: 2014.1.21.4; Microstation V8i; Terresolid ver: 2015; LP360 ver: 2014.1.51.1; Arcmap ver: 10.4; Global Mapper ver: 16</native>
	</idinfo>
	<dataqual>
		<logic>Aerial LiDAR data covers the entire 10,238 square mile Area of Interest intended for this project task. 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>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>
			<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>0.620</horizpav>
					<horizpae>This data set was produced to meet ASPRS “Positional Accuracy Standards for Digital Geospatial Data” (2014) for a 0.316 Meters RMSEx / RMSEy Horizontal Accuracy Class which equates to Positional Horizontal Accuracy =+/- 0.620 Meters at a 95% confidence level Estimated LiDAR Horizontal Error Per Point.</horizpae>
				</qhorizpa>
			</horizpa>
			<vertacc>
				<vertaccr>Vertical Accuracy of the bare-earth lidar data was assessed and reported in accordance with the ASPRS Positional Accuracy Standards for Digital Geospatial Data; Three- Hundred Fifty Five (355) surveyed points were measured for the purpose of assessing the accuracy of the IA_SouthCentral_2020_D20 UTM Zone 15N data (210 NVA + 145 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 Non Vegetated Vertical Accuracy (NVA): 0.196 Meters. Required Vegetated Vertical Accuracy (VVA): 0.300 Meters.</vertaccr>
				<qvertpa>
					<vertaccv>0.088</vertaccv>
					<vertacce>Classified LiDAR: Tested to be 0.088 Meters NVA at 95-percent confidence level using RSME(z) x 1.9600 as defined by the National Standards for spatial Data Accuracy (NSSDA). The root mean square error vertical (RMSEz) was computed to be 0.045 Meters. The NVA of the Classified LiDAR point cloud was calculated against TINs derived from the final calibrated and controlled swath data using 210 NVA checkpoints located in Bare Earth land cover class.</vertacce>
				</qvertpa>
				<qvertpa>
					<vertaccv>0.196</vertaccv>
					<vertacce>The VVA of the Classified LiDAR point cloud was calculated against TINs derived from the final calibrated and controlled swath data using 145 VVA checkpoints located in the Brushlands and Low Trees and Tall Weeds and Crops land cover categories. The the Accuracy Z was tested to be 0.196 Meters VVA at 95th percentile using RSME(z) x 1.9600 as defined by the National Standards for spatial Data Accuracy (NSSDA); assessed and reported using American Society of Photogrammetry and Remote Sensing (ASPRS) Guidelines.</vertacce>
				</qvertpa>
			</vertacc>
		</posacc>
		<lineage>
			<procstep>
				<procdesc>Aerial LiDAR Acquisition: LiDAR acquisition was done using Ottumwa Regional Airport (KOTM) and Creston Municipal Airport (KCSQ) as the base airport. DAS used one dedicated GPS base station located at the respected airport to support the aerial LiDAR acquisition. DAS used Leica’s Terrian LiDAR Sensor (SN90524) for the acquisition. The project consisted of 296 flightlines totaling 13,416.14 nautical miles. The acquisition was completed in 25 lift from March 30th, 2020- May 8, 2020.

Ground Control Survey: A survey was performed to support the acquisition of Light Detection and Ranging (LiDAR). The control network involved a total of Three-Hundred Fifty Five (355) check points (210 NVA + 145 VVA). The points were a combination of the following ground cover classification: Open Terrain, Urban Terrain, Bare Earth, High Grass, and Low Trees. All field survey observations were completed April 25, 2020 with Leica GPS GS15 and 1200 equipment.</procdesc>
				<procdate>2020425</procdate>
			</procstep>
			<procstep>
				<procdesc>LiDAR Data Processing: Inertial Explorer 8.9 software was used to compute inertial solution file (*.sol) for each mission using ground GPS base station. The resulting solution was checked to ensure a minimum accuracy of +/- 0.05m, combined separation, for horizontal and vertical positions. Inertial Explorer methodology integrates Inertial Navigation Solution by processing the GPS data and Inertial Measurement Unit (IMU). The software applies the reference lever arms for the GPS and IMU during the process to determine the trajectory (position and orientation) of the LiDAR sensor during the acquisition mission. Inertial Explorer generated graphical results was reviewed to ensure that the IMU data was healthy. These results are found in Appendix C.
				
Raw LiDAR sensor ranging data and the final solution sensor trajectory (*.sol), from Inertial Explorer, were processed in Leica’s HxMap software to produce LiDAR point cloud swath for each flight line in LAS version 1.4 file format.Quality control of the swath point cloud was performed to validate proper functioning of the sensor system, full coverage of the project area and point density of the LiDAR data. Swath point clouds were assigned unique file source identification. The data was found to be complete and consistent with the sensor calibration parameters.</procdesc>
				<procdate>20200709</procdate>
			</procstep>
			<procstep>
				<procdesc>LiDAR Calibration:HxMap is the common workflow platform for Leica airborne sensors. The processing workflow involves; Ingest, Block Creation, LiDAR Matching, Quality Assurance (QA) and Product Generation.
				
LiDAR is processed in HxMap by generating point clouds from raw sensor data during the Ingest step. Noise filtering, sensor installation calibration and atmospheric condition parameters are also applied during the ingest process. Once all data is processed through ingest, they are assembled into a block for LiDAR Matching. The LiDAR Matching step resolves LiDAR registration errors which remain in the point clouds after sensor and installation calibration parameters are applied in the ingest step. QA tool is run on the Block after LiDAR Matching to verify quality of results. QA results are reviewed to ensure that, 95% of patches less thand 5cm for Vertical Scan Direction and Vertical Line Separation. Ground control points are also included to assess absolute accuracy for the point cloud data. LiDAR products are finally generated in the Product Generation step as LAS swaths (LAS 1.4). Vertical (Z) shift (calculated from QA step) is also applied during the product generation.</procdesc>				
				<procdate>20200709</procdate>
			</procstep>
		</lineage>
	</dataqual>
	<spdoinfo>
		<direct>Point</direct>
		<ptvctinf>
			<sdtsterm>
				<sdtstype>Point</sdtstype>
				<ptvctcnt>283,462,356,426</ptvctcnt>
			</sdtsterm>
		</ptvctinf>
	</spdoinfo>
	<spref>
		<horizsys>
			<planar>
				<gridsys>
					<gridsysn>Universal Transverse Mercator</gridsysn>
					<utm>
						<utmzone>15N</utmzone>
						<transmer>
							<sfctrmer>0.99960000</sfctrmer>
							<longcm>-93.00000000</longcm>
							<latprjo>0.000000000</latprjo>
							<feast>500000.000000000</feast>
							<fnorth>0.000000000</fnorth>
						</transmer>
					</utm>
				</gridsys>
				<planci>
					<plance>Coordinate Pair</plance>
					<coordrep>
						<absres>0.001</absres>
						<ordres>0.001</ordres>
					</coordrep>
					<plandu>meters</plandu>
				</planci>
			</planar>
			<geodetic>
				<horizdn>NAD83, National Reference System 2011</horizdn>
				<ellips>Geodetic Reference System 80</ellips>
				<semiaxis>6378137.000000</semiaxis>
				<denflat>298.255822101</denflat>
			</geodetic>
		</horizsys>
		<vertdef>
			<altsys>
				<altdatum>North American Vertical Datum of 1988 (Geoid18)</altdatum>
				<altres>0.001</altres>
				<altunits>meters</altunits>
				<altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
			</altsys>
		</vertdef>
	</spref>
	<eainfo>
		<overview>
			<eaover>None</eaover>
			<eadetcit>None</eadetcit>
		</overview>
	</eainfo>
	<distinfo>
		<distrib>
			<cntinfo>
				<cntorgp>
					<cntorg>None</cntorg>
					<cntper>None</cntper>
				</cntorgp>
				<cntpos>None</cntpos>
				<cntaddr>
					<addrtype>None</addrtype>
					<address>None</address>
					<city>None</city>
					<state>None</state>
					<postal>None</postal>
					<country>None</country>
				</cntaddr>
				<cntvoice>None</cntvoice>
				<cntfax>None</cntfax>
				<cntemail>None</cntemail>
				<hours>None</hours>
				<cntinst>None</cntinst>
			</cntinfo>
		</distrib>
		<resdesc>None</resdesc>
		<distliab>None</distliab>
	</distinfo>
	<metainfo>
		<metd>20210930</metd>
		<metc>
			<cntinfo>
				<cntorgp>
					<cntorg>Digital Aerial Solutions, LLC</cntorg>
					<cntper>Josh Helton</cntper>
				</cntorgp>
				<cntpos>VP/Assistant General Manager</cntpos>
				<cntaddr>
					<addrtype>mailing and physical address</addrtype>
					<address>4027-A Crescent Park Drive</address>
					<city>Riverview</city>
					<state>FL</state>
					<postal>33578</postal>
					<country>United States</country>
				</cntaddr>
				<cntvoice>813-628-0788</cntvoice>
				<cntfax>813-628-0777</cntfax>
				<cntemail>jhelton@digitalaerial.com</cntemail>
				<hours>Monday through Friday 8:00 AM to 4:00 PM (Eastern 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>
		</metc>
		<metstdn>FGDC Content Standards 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>