<!DOCTYPE metadata SYSTEM "http://fgdc.gov/metadata/fgdc-std-001-1998.dtd">
<!--DOCTYPE metadata SYSTEM "fgdc-std-001-1998.dtd"--><metadata>	
	<idinfo>
		<citation>
			<citeinfo>
				<origin>Quantum Spatial, Inc.</origin>
				<pubdate>20170126</pubdate>
				<title>Mississippi 2016 QL2 LiDAR - South AOI; 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 1,791 individual 5,000-foot x 5,000-foot tiles; used to create intensity images, 3D breaklines and hydro-flattened DEMs as necessary.
				Geographic Extent: Four whole and partial counties in south central Mississippi, covering approximately 1,507 square miles of the 3,825 total square mile project area.
				Dataset Description: The Mississippi 2016 Aerial LiDAR Mapping project called for the planning, acquisition, processing and derivative products of LIDAR data to be collected at an aggregate 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 1.2. The data was developed based on a horizontal projection/datum of NAD83 (2011) State Plane Mississippi East Zone, US survey feet and vertical datum of NAVD1988 (Geoid 12B), US survey feet. LiDAR data was delivered in RAW flight line swath format, processed to create Classified LAS 1.4 Files formatted to 1,791 individual 5,000-foot x 5,000-foot tiles. Corresponding 2.5-foot intensity images in GeoTIFF format and 2.5-foot bare-earth DEM files in ERDAS .IMG format were created with the same tile schema. Tiles names follow the US National Grid naming schema. Hydro-flattened breaklines were produced in Esri file geodatabase format. Continuous contours with a 1-foot interval were produced in Esri file geodatabase format. 
				Ground Conditions: Lidar was collected in winter of 2016, 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, Quantum Spatial, Inc. established a total of 38 ground control points that were used to calibrate the lidar to known ground locations established throughout the Mississippi project area. An additional 96 independent accuracy checkpoints, 43 in Bare Earth and Urban landcovers (43 NVA points), 35 in Forested, Shrubs, and Tall Weeds categories (35 VVA points), were used to assess the vertical accuracy of the data. These checkpoints were not used to calibrate or post process the data. One point was removed from the NVA calculations due to drastic change in the area.</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 DEMs. The purpose of these lidar data was to produce high accuracy 3D hydro-flattened digital elevation models (DEMs) with a 2.5 foot cell size. These raw lidar point cloud data were used to create classified lidar LAS files, intensity images, 3D breaklines, hydro-flattened DEMs, and contours as necessary.</purpose>
			<lidar>
				<ldrinfo>
					<ldrspec>USGS-NGP Base Specification v1.2</ldrspec>
					<ldrsens>Leica ALS 70</ldrsens>
					<ldrmaxnr>4</ldrmaxnr>
					<ldrnps>0.68</ldrnps>
					<ldrdens>2.14</ldrdens>
					<ldranps>0.68</ldranps>
					<ldradens>2.14</ldradens>
					<ldrfltht>2000</ldrfltht>
					<ldrfltsp>170</ldrfltsp>
					<ldrscana>40.0</ldrscana>
					<ldrscanr>53.4</ldrscanr>
					<ldrpulsr>273.0</ldrpulsr>
					<ldrpulsd>4</ldrpulsd>
					<ldrpulsw>0.26</ldrpulsw>
					<ldrwavel>1064</ldrwavel>
					<ldrmpia>1</ldrmpia>
					<ldrbmdiv>0.45</ldrbmdiv>
					<ldrswatw>1455.88</ldrswatw>
					<ldrswato>11.27</ldrswato>
					<ldrgeoid>g2012bu0.bin</ldrgeoid>
				</ldrinfo>
				<ldrinfo_80>
					<ldrspec>USGS-NGP Base Specification v1.2</ldrspec>
					<ldrsens>Leica ALS 80</ldrsens>
					<ldrmaxnr>4</ldrmaxnr>
					<ldrnps>0.69</ldrnps>
					<ldrdens>2.13</ldrdens>
					<ldranps>0.69</ldranps>
					<ldradens>2.14</ldradens>
					<ldrfltht>2000</ldrfltht>
					<ldrfltsp>170</ldrfltsp>
					<ldrscana>40.0</ldrscana>
					<ldrscanr>39.0</ldrscanr>
					<ldrpulsr>271.0</ldrpulsr>
					<ldrpulsd>4</ldrpulsd>
					<ldrpulsw>0.45</ldrpulsw>
					<ldrwavel>1064</ldrwavel>
					<ldrmpia>1</ldrmpia>
					<ldrbmdiv>0.22</ldrbmdiv>
					<ldrswatw>1455.88</ldrswatw>
					<ldrswato>17.85</ldrswato>
					<ldrgeoid>g2012bu0.bin</ldrgeoid>
				</ldrinfo_80>
				<ldraccur>
					<ldrchacc>0.196</ldrchacc>
					<rawnva>0.090</rawnva>
					<rawnvan>42</rawnvan>
				</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>10</clascode>
						<clasitem>Ignored Ground</clasitem>
					</lasclass>
					<lasclass>
						<clascode>17</clascode>
						<clasitem>Bridge Decks</clasitem>
					</lasclass>
					<lasclass>
						<clascode>18</clascode>
						<clasitem>High noise</clasitem>
					</lasclass>
				</lasinfo>
			</lidar>
			<supplinf>USGS Contract No.: G16PC00016 CONTRACTOR: Quantum Spatial, Inc. SUBCONTRACTOR: Woolpert. Lidar data were acquired by Quantum Spatial, Inc. and Woolpert. All follow-on processing was completed by the prime contractor.
				Tile MS845675 contains data flown on both 1/19/2016 (flightline 130) and  1/27/2016 (flightline 137).  The hydro-flattened double line drain flows monotonically, based on the corresponding data used to collect the breakline from each date.  A step was introduced in the location between flightlines because of a 5 foot rise in the water elevation between these 2 lifts.</supplinf>
		</descript>
		<timeperd>
			<timeinfo>
				<rngdates>
					<begdate>20160119</begdate>
					<enddate>20160204</enddate>
				</rngdates>
			</timeinfo>
			<current>ground condition</current>
		</timeperd>
		<status>
			<progress>Complete</progress>
			<update>None planned</update>
		</status>
		<spdom>
			<bounding>
				<westbc>-89.6645579701677</westbc> 
				<eastbc>-88.6871709429993</eastbc> 
				<northbc>31.4380733391558</northbc>
				<southbc>30.9012662914909</southbc>
			</bounding>
		</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>Mississippi</placekey>
				<placekey>Forrest County</placekey>
				<placekey>Greene County</placekey>
				<placekey>Lamar County</placekey>
				<placekey>Perry County</placekey>
			</place>
		</keywords>
		<accconst>No restrictions apply to 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. Acknowledgement of the U.S. Geological Survey would be appreciated for products derived from these data.</useconst>
	</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>
		<lineage>
			<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 ground (ASPRS Class 2) lidar data inside of the Lake Pond and Double Line Drain hydro-flattened breaklines were then classified to Water (ASPRS Class 9) using TerraScan macro functionality. A buffer of 3 feet was also used around each hydro-flattened feature to classify these ground (ASPRS Class 2) points to Ignored ground (ASPRS Class 10). All Lake Pond Island and Double Line Drain Island features were checked to ensure that the ground (ASPRS Class 2) 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 TerraScan and TerraModeler. Global Mapper us used as a final check of the bare earth dataset. GeoCue was then used to create the deliverable industry-standard LAS files for both the All Point Cloud Data and the Bare Earth. Quantum Spatial, 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>2016</procdate>
			</procstep>
		</lineage>
	</dataqual>
	<spdoinfo>
		<direct>Point</direct>
	</spdoinfo>
	<spref>
		<horizsys>
			<planar>
				<gridsys>
					<gridsysn>State Plane Coordinate System 1983</gridsysn>
					<spcs>
						<spcszone>2301</spcszone>
						<transmer>
							<sfctrmer>0.99995</sfctrmer>
							<longcm>-88.83333333333333</longcm>
							<latprjo>29.5</latprjo>
							<feast>984250.0</feast>
							<fnorth>0.0</fnorth>
						</transmer>
					</spcs>
				</gridsys>
				<planci>
					<plance>coordinate pair</plance>
					<coordrep>
						<absres>0.01</absres>
						<ordres>0.01</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.0</semiaxis>
				<denflat>298.257222101</denflat>
			</geodetic>
		</horizsys>
		<vertdef>
			<altsys>
				<altdatum>North American Vertical Datum of 1988 (GEOID12B)</altdatum>
				<altres>0.01</altres>
				<altunits>feet</altunits>
				<altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
			</altsys>
		</vertdef>
	</spref>
	<metainfo>
		<metd>20170126</metd>
		<metc>
			<cntinfo>
				<cntorgp>
					<cntorg>Quantum Spatial</cntorg>
				</cntorgp>
				<cntaddr>
					<addrtype>mailing and physical</addrtype>
					<address>523 Wellington Way</address>
					<city>Lexington</city>
					<state>KY</state>
					<postal>40503</postal>
					<country>USA</country>
				</cntaddr>
				<cntvoice>859-277-8700</cntvoice>
			</cntinfo>
		</metc>
		<metstdn>FGDC Content Standard for Digital Geospatial Metadata</metstdn>
		<metstdv>FGDC-STD-001-1998</metstdv>
	</metainfo>
</metadata>