<?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>20190617</pubdate>
				<title>Hamilton County, Indiana 2016 LiDAR; Tile Index</title>
				<geoform>Vector digital data</geoform>
			</citeinfo>
		</citation>
		<descript>
			<abstract> Product: Tile index with a size of 2,500 feet x 2,500 feet in Esri shapefile
				format. Geographic Extent: One county in Indiana, covering approximately 434 total
				square miles. Dataset Description: The Hamilton County, Indiana 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.7 meters. Project
				specifications are based on the U.S. Geological Survey National Geospatial Program
				Base LiDAR Specification, Version 1.2. The data were developed based on a horizontal
				projection/datum of NAD83 (2011), Indiana State Plane East, US survey feet and
				vertical datum of NAVD88 (GEOID12B), US survey feet. LiDAR data were delivered as
				processed Classified LAS 1.4 files formatted to 1,936 individual 2,500 feet x 2,500
				feet tiles, as tiled intensity imagery, and as tiled bare earth DEMs; all tiled to
				the same 2,500 feet x 2,500 feet schema. Continuous breaklines were produced in Esri
				file geodatabase format. Ground Conditions: LiDAR was collected in spring 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. utilized a total of 39 ground
				control points that were used to calibrate the LiDAR to known ground locations
				established throughout the project area. An additional 53 independent accuracy
				checkpoints, 32 in Bare Earth and Urban landcovers (32 NVA points), 21 in Tall Weeds
				categories (21 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 3.125-foot 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>CONTRACTOR: Quantum Spatial; Lidar data were acquired and calibrated by
				Quantum Spatial. All follow-on processing was completed by the prime
				contractor.</supplinf>
		</descript>
		<timeperd>
			<timeinfo>
				<rngdates>
					<begdate>20160321</begdate>
					<enddate>20160322</enddate>
				</rngdates>
			</timeinfo>
			<current>ground condition</current>
		</timeperd>
		<status>
			<progress>Complete</progress>
			<update>None planned</update>
		</status>
		<spdom>
			<bounding>
				<westbc>-86.25069095</westbc>
				<eastbc>-85.85593198</eastbc>
				<northbc>40.22440278</northbc>
				<southbc>39.92113439</southbc>
			</bounding>
		</spdom>
		<keywords>
			<theme>
				<themekt>None</themekt>
				<themekey>Model</themekey>
				<themekey>Tile Index</themekey>
			</theme>
			<place>
				<placekt>None</placekt>
				<placekey>Indiana</placekey>
				<placekey>Hamilton County</placekey>
			</place>
		</keywords>
		<accconst>No restrictions apply to these 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 their limitations.</useconst>
	</idinfo>
	<dataqual>
		<logic>Data cover 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>Tile Index Creation: Tiles were created using a 0,0 origin point to ensure
					proper divisibility of raster and image cells. A 2,500 foot x 2,500 foot tile
					size was used as called for in the Task Order. Tile index was output in Esri
					shapefile format.</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>1301</spcszone>
						<transmer>
							<sfctrmer>0.9999666666666667</sfctrmer>
							<longcm>-85.66666666666667</longcm>
							<latprjo>37.5</latprjo>
							<feast>328083.3333333333</feast>
							<fnorth>820208.3333333333</fnorth>
						</transmer>
					</spcs>
				</gridsys>
				<planci>
					<plance>coordinate pair</plance>
					<coordrep>
						<absres>0.01</absres>
						<ordres>0.01</ordres>
					</coordrep>
					<plandu>US survey feet</plandu>
				</planci>
			</planar>
			<geodetic>
				<horizdn>NAD83 (2011)</horizdn>
				<ellips>Geodetic Reference System 80</ellips>
				<semiaxis>6378137.0</semiaxis>
				<denflat>298.257222101</denflat>
			</geodetic>
		</horizsys>
		<vertdef>
			<altsys>
				<altdatum>NAVD88 (GEOID12B)</altdatum>
				<altres>0.01</altres>
				<altunits>US survey feet</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>Name</attrlabl>
				<attrdef>Tile name</attrdef>
				<attrdefs>LiDAR Data</attrdefs>
				<attrdomv>
					<udom>Tile Names</udom>
				</attrdomv>
			</attr>
		</detailed>
		<overview>
			<eaover>Polygons showing the boundary of the tiles.</eaover>
			<eadetcit>More detail about the attributes of this data set can be found in the
				contract.</eadetcit>
		</overview>
	</eainfo>
	<metainfo>
		<metd>20190617</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>
				<cntemail>jbowen@quantumspatial.com</cntemail>
				<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>
