<!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; Hydro-Flattened Breaklines</title>
				<geoform>Vector digital data</geoform>
			</citeinfo>
		</citation>
		<descript>
			<abstract>Product: Breakline data is used to hydroflatten the DEMs created for the Mississippi lidar project. Breaklines are reviewed against lidar intensity imagery to verify completeness of capture.
				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>
			<supplinf>
				Breakline File Type = GDB
				Breakline Elevation Units = US Survey Feet
				Downhill Treatment Applied = Monotonic, Proprietary
				Type of Hydro Treatment Required = Hydro-flattened
				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>Breaklines</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. Breaklines were collected in all inland ponds and lakes ~2 acres or greater. These features were flat and level water bodies at a single elevation for each vertex along the bank. The entire water surface edge is at or below the immediate surrounding terrain. Breaklines were collected for all streams and rivers ~100 foot nominal width or wider. These features are flat and level bank to bank, gradient will follow the surrounding terrain and the water surface will be at or below the surrounding terrain. Streams/river channels will break at culvert locations however not at elevated bridge locations.</logic>
		<complete>All files are inspected to ensure that they conform to the specified file naming conventions, all files load in their correct geographic position, all files conform to the project specifications for file standard and content.</complete>
		<lineage>
			<procstep>
				<procdesc>Hydro-Flattened Breakline Processing: Class 2 (ground) lidar points was used to create a bare earth surface model. The surface model was then used to heads-up digitize 2D breaklines of inland streams and rivers with a 100-foot nominal width and inland ponds and lakes of 2 acres or greater surface area. Elevation values were assigned to all Inland Ponds and Lakes, Inland Pond and Lake Islands, Inland Stream and River Islands, using TerraModeler functionality. Elevation values were assigned to all inland streams and rivers using Quantum Spatial, Inc. proprietary software. All Ground (ASPRS Class 2) lidar data inside of the collected inland 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. These points were moved from ground (ASPRS Class 2) to Ignored Ground (ASPRS Class 10). The breakline files were then translated to Esri file geodatabase format using Esri conversion tools. Breaklines are reviewed against lidar intensity imagery to verify completeness of capture. All breaklines are then compared to TINs (triangular irregular networks) created from ground only points prior to water classification. The horizontal placement of breaklines is compared to terrain features and the breakline elevations are compared to lidar elevations to ensure all breaklines match the lidar within acceptable tolerances. Some deviation is expected between breakline and lidar elevations due to monotonicity, connectivity, and flattening rules that are enforced on the breaklines. Once completeness, horizontal placement, and vertical variance is reviewed, all breaklines are reviewed for topological consistency and data integrity using a combination of Esri Data Reviewer tools and proprietary tools.</procdesc>
				<procdate>2016</procdate>
			</procstep>
		</lineage>
	</dataqual>
	<spdoinfo>
		<direct>Vector</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>
		<eainfo>
		<detailed>
			<enttyp>
				<enttypl>Breaklines</enttypl>
				<enttypd>A line in a surface that represents a distinct interruption in the slope of a surface, such as a ridge, road, or stream.</enttypd>
				<enttypds>Esri GIS Dictionary http://support.esri.com/en/knowledgebase/GISDictionary/term/breakline</enttypds>
			</enttyp>
			<attr>
				<attrlabl>FID</attrlabl>
				<attrdef>Internal feature number.</attrdef>
				<attrdefs>Esri</attrdefs>
				<attrdomv>
					<udom>Sequential unique whole numbers that are automatically generated.</udom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>Shape</attrlabl>
				<attrdef>Feature geometry.</attrdef>
				<attrdefs>Esri</attrdefs>
				<attrdomv>
					<udom>Feature geometry - Polyline ZM</udom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>B_LINE_TY</attrlabl>
				<attrdef>Breakline Type</attrdef>
				<attrdefs>LiDAR Data</attrdefs>
				<attrdomv>
					<edom>
						<edomv>Lake Pond</edomv>
						<edomvd>LiDAR Data</edomvd>
						<edomvds>LAS version 1.4</edomvds>
					</edom>
					<edom>
						<edomv>Lake Pond Island</edomv>
						<edomvd>LiDAR Data</edomvd>
						<edomvds>LAS version 1.4</edomvds>
					</edom>
					<edom>
						<edomv>Double Drain</edomv>
						<edomvd>LiDAR Data</edomvd>
						<edomvds>LAS version 1.4</edomvds>
					</edom>
					<edom>
						<edomv>Double Drain Island</edomv>
						<edomvd>LiDAR Data</edomvd>
						<edomvds>LAS version 1.4</edomvds>
					</edom>
					<edom>
						<edomv>Bridge</edomv>
						<edomvd>LiDAR Data</edomvd>
						<edomvds>LAS version 1.4</edomvds>
					</edom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>Shape_Length</attrlabl>
				<attrdef>Shape Length in feet</attrdef>
				<attrdefs>Esri</attrdefs>
				<attrdomv>
					<udom>Length of the feature in feet.</udom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>RuleID</attrlabl>
				<attrdef>Breakline Type</attrdef>
				<attrdefs>LiDAR Data</attrdefs>
				<attrdomv>
					<edom>
						<edomv>Lake Pond</edomv>
						<edomvd>LiDAR Data</edomvd>
						<edomvds>LAS version 1.4</edomvds>
					</edom>
					<edom>
						<edomv>Lake Pond Island</edomv>
						<edomvd>LiDAR Data</edomvd>
						<edomvds>LAS version 1.4</edomvds>
					</edom>
					<edom>
						<edomv>Double Drain</edomv>
						<edomvd>LiDAR Data</edomvd>
						<edomvds>LAS version 1.4</edomvds>
					</edom>
					<edom>
						<edomv>Double Drain Island</edomv>
						<edomvd>LiDAR Data</edomvd>
						<edomvds>LAS version 1.4</edomvds>
					</edom>
					<edom>
						<edomv>Bridge</edomv>
						<edomvd>LiDAR Data</edomvd>
						<edomvds>LAS version 1.4</edomvds>
					</edom>
				</attrdomv>
			</attr>
		</detailed>
		<overview>
			<eaover>Breaklines with the types of Lake Pond, and Bridge.</eaover>
			<eadetcit>More detail about the attributes of this data set can be found in LAS 1.4 specifications and USGS LiDAR Base Specification Version 1.2.</eadetcit>
		</overview>
	</eainfo>
	<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>