<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE metadata SYSTEM "http://fgdc.gov/metadata/fgdc-std-001-1998.dtd">
<metadata>	
	<idinfo>
		<citation>
			<citeinfo>
				<origin>Quantum Spatial, Inc.</origin>
				<pubdate>20170301</pubdate>
				<title>Utah 2016 LiDAR - Minidoka QL1 AOI; Processing Boundary</title>
				<geoform>Vector digital data</geoform>
			</citeinfo>
		</citation>
		<descript>
			<abstract>Product: Processing boundary with a 100-meter buffer in Esri shapefile format.
				Geographic Extent: Fourteen partial counties in Utah, covering approximately 7,005 total square kilometers; partial coverage of three counties covering approximately 182 square kilometers in the Minidoka QL1 AOI. This area is part of the Bear Lake / Cache Valley QL1 AOI.
				Dataset Description: The Utah 2016 Lidar project called for the planning, acquisition, processing, and derivative products of lidar data to be collected at a nominal pulse spacing (NPS) of 0.35 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), UTM Zone 12, meters and vertical datum of NAVD88 (GEOID12B), meters. Lidar data was delivered as flightline-extent unclassified LAS swaths, as processed Classified LAS 1.4 files formatted to 215 individual 1,000 meter x 1,000 meter tiles; as tiled intensity imagery, as tiled bare earth DEMs, and as tiled first return DSMs all tiled a 2,000 meter x 2,000 meter schema (82 tiles). Continuous breaklines were produced in Esri shapefile format.
				Ground Conditions: Lidar was partially collected in fall 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 28 ground control points that were used to calibrate the lidar to known ground locations established throughout the project area. An additional 5 independent accuracy checkpoints, 5 in Bare Earth and Urban landcovers (5 NVA points), 6 in the Shrubs and Tall Grass category (6 VVA points), were used to assess the vertical accuracy of the data. These checkpoints were not used to calibrate or post process the data.</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 and DSMs. The purpose of these lidar data was to produce high accuracy 3D hydro-flattened digital elevation models (DEMs) with a 0.5 meter cell size. These raw lidar point cloud data were used to create classified lidar LAS files, intensity images, 3D breaklines, hydro-flattened DEMs, and first return DSMs as necessary.</purpose>
			<supplinf>State of Utah Contract No. AV2408 CONTRACTOR: Quantum Spatial, Inc. Lidar data were acquired by Quantum Spatial, Inc. All follow-on processing was completed by the prime contractor.</supplinf>
		</descript>
		<timeperd>
			<timeinfo>
				<sngdate>
					<caldate>20161023</caldate>
				</sngdate>
			</timeinfo>
			<current>ground condition</current>
		</timeperd>
		<status>
			<progress>Complete</progress>
			<update>None planned</update>
		</status>
		<spdom>
			<bounding>
				<westbc>-113.514517142334</westbc>
				<eastbc>-112.965015794335</eastbc>
				<northbc>42.7075128476455</northbc>
				<southbc>42.583483416452</southbc>
			</bounding>
		</spdom>
		<keywords>
			<theme>
				<themekt>None</themekt>
				<themekey>Model</themekey>
				<themekey>Processing Boundary</themekey>
			</theme>
			<place>
				<placekt>None</placekt>
				<placekey>Idaho</placekey>
				<placekey>Blaine County</placekey>
				<placekey>Cassia County</placekey>
				<placekey>Power 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.</useconst>
	</idinfo>
	<dataqual>
		<logic>Data covers the entire area specified for this project.</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>Processing Boundary Processing: The processing boundary was created using the original client-provided AOI shapefile. The original file was buffered by 100 meters in order to meet task order requirements for data coverage.</procdesc>
				<procdate>2017</procdate>
			</procstep>
		</lineage>
	</dataqual>
	<spdoinfo>
		<direct>Vector</direct>
	</spdoinfo>
	<spref>
		<horizsys>
			<planar>
				<gridsys>
					<gridsysn>Universal Transverse Mercator</gridsysn>
					<utm>
						<utmzone>12</utmzone>
						<transmer>
							<sfctrmer>0.9996</sfctrmer>
							<longcm>-111.0</longcm>
							<latprjo>0.0</latprjo>
							<feast>500000.0</feast>
							<fnorth>0.0</fnorth>
						</transmer>
					</utm>
				</gridsys>
				<planci>
					<plance>coordinate pair</plance>
					<coordrep>
						<absres>0.01</absres>
						<ordres>0.01</ordres>
					</coordrep>
					<plandu>meters</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>meters</altunits>
				<altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
			</altsys>
		</vertdef>
	</spref>
	<eainfo>
		<detailed>
			<enttyp>
				<enttypl>Polygons</enttypl>
				<enttypd>On a map, a closed shape defined by a connected sequence of x,y coordinate pairs, where the first and last coordinate pair are the same and all other pairs are unique.</enttypd>
				<enttypds>Esri GIS Dictionary http://support.esri.com/en/knowledgebase/GISDictionary/term/polygon</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 - Polygon ZM</udom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>Id</attrlabl>
				<attrdef>Boundary ID</attrdef>
				<attrdefs>LiDAR Data</attrdefs>
				<attrdomv>
					<udom>Identifying Name</udom>
				</attrdomv>
			</attr>
		</detailed>
		<overview>
			<eaover>Polygons showing the boundary of the area of interest.</eaover>
			<eadetcit>More detail about the attributes of this data set can be found in the State of Utah Contract No. AV2408.</eadetcit>
		</overview>
	</eainfo>
	<metainfo>
		<metd>20170301</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>
				<cntfax>859-277-8901</cntfax>
				<hours>Monday through Friday 8:00 AM to 5: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 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>
	</metainfo>
</metadata>