<?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>20180605</pubdate>
				<title>Oklahoma 2016 LiDAR - UTM 15 AOIs; 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: Twelve counties in Eastern Oklahoma, covering approximately 8,606 total square miles, including five counties partially covering approximately 410 square miles in the City of Tulsa AOI. Please note that the entire project area covers UTM Zones 14 and 15 and encompasses 14,869 square miles across 23 counties in the State of Oklahoma.
				Dataset Description: Oklahoma 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 for counties in the eastern AOIs were developed based on a horizontal projection/datum of NAD83 (2011), UTM Zone 15, 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 9890 individual 1500 x 1500 m UTM 15 tiles at QL2, as tiled intensity imagery, and as tiled bare earth DEMs; all tiled to the same schema. For the City of Tulsa, processed Classified LAS 1.4 files were formatted to 2164 individual 750 x 750 m UTM 15 tiles at QL1. Continuous breaklines were produced in Esri file geodatabase format. Building footprints were created in Esri file geodatabase format.
				Ground Conditions: Lidar was collected between December 2016 and April 2017, 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 369 ground control points that were used to calibrate the lidar to known ground locations established throughout the Oklahoma project area. An additional 458 independent accuracy checkpoints, 271 in Bare Earth and Urban landcovers (271 raw NVA points, 270 NVA points), 187 in Forested, Brushland/Trees, and Tall Weeds/Crops categories (187 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. The purpose of these lidar data was to produce high accuracy 3D hydro-flattened digital elevation models (DEMs) with a 1-meter cell size. These raw lidar point cloud data were used to create classified lidar LAS files, intensity images, 3D breaklines, and hydro-flattened DEMs as necessary.</purpose>
			<supplinf>USGS Contract No. G10PC00016 CONTRACTOR: Quantum Spatial, Inc. SUBCONTRACTOR: Aerial Surveys International, LLC, Kucera International, Inc. Lidar data were acquired by Quantum Spatial, Inc., Aerial Surveys International, LLC, and Kucera International, Inc. All follow-on processing was completed by the prime contractor.</supplinf>
		</descript>
		<timeperd>
			<timeinfo>
				<rngdates>
					<begdate>20161213</begdate>
					<enddate>20170417</enddate>
				</rngdates>
			</timeinfo>
			<current>ground condition</current>
		</timeperd>
		<status>
			<progress>Complete</progress>
			<update>None planned</update>
		</status>
		<spdom>
			<bounding>
				<westbc>-97.091445</westbc>
				<eastbc>-94.784343</eastbc>
				<northbc>37.053909</northbc>
				<southbc>33.975886</southbc>
			</bounding>
		</spdom>
		<keywords>
			<theme>
				<themekt>None</themekt>
				<themekey>Model</themekey>
				<themekey>Processing Boundary</themekey>
			</theme>
			<place>
				<placekt>None</placekt>
				<placekey>Oklahoma</placekey>
				<placekey>Kay County</placekey>
				<placekey>Osage County</placekey>
				<placekey>Tulsa County</placekey>
				<placekey>Wagoner County</placekey>
				<placekey>Muskogee County</placekey>
				<placekey>McIntosh County</placekey>
				<placekey>Haskell County</placekey>
				<placekey>Pittsburg County</placekey>
				<placekey>Atoka County</placekey>
				<placekey>Pushmataha County</placekey>
				<placekey>Chocktaw County</placekey>
				<placekey>Sequoya 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>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 Creation: 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>15</utmzone>
						<transmer>
							<sfctrmer>0.9996</sfctrmer>
							<longcm>-93.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>BUFF_DIST</attrlabl>
				<attrdef>Buffer distance</attrdef>
				<attrdefs>LiDAR Data</attrdefs>
				<attrdomv>
					<edom>
						<edomv>100 meters</edomv>
						<edomvd>Distance added as buffer from client-provided project area</edomvd>
						<edomvds>QSI</edomvds>
					</edom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>SqMi</attrlabl>
				<attrdef>Calculated Area in square miles</attrdef>
				<attrdefs>LiDAR Data</attrdefs>
				<attrdomv>
					<udom>Area of shape calculated in square miles</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 USGS Contract: G10PC00016, Task Order Number: G17PD00013.</eadetcit>
		</overview>
	</eainfo>
	<distinfo>
		<distrib>
			<cntinfo>
				<cntperp>
					<cntper>Chris Stoner</cntper>
					<cntorg>USDA - Natural Resources Conservation Service (NRCS), Oklahoma</cntorg>
				</cntperp>
				<cntpos>NRCS State Conservation Engineer</cntpos>
				<cntaddr>
					<addrtype>mailing and physical address</addrtype>
					<address>224 N. Orchard</address>
					<city>Stillwater</city>
					<state>OK</state>
					<postal>74074</postal>
					<country>USA</country>
				</cntaddr>
				<cntvoice>405-742-1260</cntvoice>
				<cntemail>Chris.Stoner@ok.usda.gov</cntemail>
			</cntinfo>
		</distrib>
		<resdesc>The NRCS distributes data directly to program partners. Public access to the data is available from the USGS.
		</resdesc>
		<distliab>In no event shall the creators, custodians, or distributors of these data be liable for any damages arising out of its use, or from the inability of the customer to use these data for their intended application.
		</distliab>
	</distinfo>
	<distinfo>
		<distrib>
			<cntinfo>
				<cntperp>
					<cntper>Jennifer Knecht</cntper>
					<cntorg>Federal Emergency Management Agency (FEMA) Region VI</cntorg>
				</cntperp>
				<cntpos>FEMA Regional Flood Map Geospatial Lead</cntpos>
				<cntaddr>
					<addrtype>mailing and physical address</addrtype>
					<address>800 North Loop 288</address>
					<city>Denton</city>
					<state>TX</state>
					<postal>76209</postal>
					<country>USA</country>
				</cntaddr>
				<cntvoice>940-898-5553</cntvoice>
				<cntemail>Jennifer.Knecht@fema.dhs.gov</cntemail>
			</cntinfo>
		</distrib>
		<resdesc>FEMA distributes data directly to program partners. Public access to the data is available from the USGS.
		</resdesc>
		<distliab>In no event shall the creators, custodians, or distributors of these data be liable for any damages arising out of its use, or from
			the inability of the customer to use these data for their intended application.
		</distliab>
	</distinfo>
	<distinfo>
		<distrib>
			<cntinfo>
				<cntperp>
					<cntper>Edgar Mersiovsky</cntper>
					<cntorg>Arkansas United States Department of Agriculture (USDA)</cntorg>
				</cntperp>
				<cntpos>State Soil Scientist</cntpos>
				<cntaddr>
					<addrtype>mailing and physical address</addrtype>
					<address>USDA - Natural Resources Conservation Service</address>
					<address>Room 3416 Federal Building</address>
					<address>700 West Capitol Avenue</address>
					<city>Little Rock</city>
					<state>AR</state>
					<postal>72201-3225</postal>
					<country>USA</country>
				</cntaddr>
				<cntvoice>501-301-3161</cntvoice>
				<cntemail>edgar.mersiovsky@ar.usda.gov</cntemail>
			</cntinfo>
		</distrib>
		<resdesc>The Arkasas USDA distributes data directly to program partners. Public access to the data is available from the USGS.</resdesc>
		<distliab>In no event shall the creators, custodians, or distributors of these data be liable for any damages arising out of its use, or from
			the inability of the customer to use these data for their intended application.
		</distliab>
	</distinfo>	
	<metainfo>
		<metd>20180605</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>