<?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>20181026</pubdate>
				<title>South Central Pennsylvania 2017 QL2 LiDAR; Contours</title>
				<geoform>Vector digital data</geoform>
			</citeinfo>
		</citation>
		<descript>
			<abstract> Product: Contours with a 2-foot interval in Esri file geodatabase format.
				Geographic Extent: 13 counties in Pennsylvania, covering approximately 6,602 total
				square miles. Dataset Description: The South Central Pennsylvania 2017 QL2 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 NAD 1983 (2011), UTM Zone 18, meters and vertical datum of NAVD
				1988 (GEOID 12B), meters. LiDAR data were delivered as processed Classified LAS 1.4
				files formatted to 7,975 individual 1,500-meter x 1,500-meter tiles, as tiled
				intensity imagery, and as tiled bare earth DEMs; all tiled to the same 1,500-meter x
				1,500-meter schema. Continuous breaklines were produced in Esri file geodatabase
				format. Ground Conditions: LiDAR was collected in fall 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. utilized a total of 150 ground control points that
				were used to calibrate the LiDAR to known ground locations established throughout
				the project area. An additional 245 independent accuracy checkpoints, 142 in Bare
				Earth and Urban landcovers (142 NVA points), 103 in Tall Weeds categories (103 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. G16PC00016, Task Order No. G17PD01254; CONTRACTOR: Quantum
				Spatial, Inc.</supplinf>
		</descript>
		<timeperd>
			<timeinfo>
				<rngdates>
					<begdate>20171121</begdate>
					<enddate>20171221</enddate>
				</rngdates>
			</timeinfo>
			<current>ground condition</current>
		</timeperd>
		<status>
			<progress>Complete</progress>
			<update>None planned</update>
		</status>
		<spdom>
			<bounding>
				<westbc>-78.10056682</westbc>
				<eastbc>-76.15029659</eastbc>
				<northbc>41.59758202</northbc>
				<southbc>39.71890736</southbc>
			</bounding>
		</spdom>
		<keywords>
			<theme>
				<themekt>None</themekt>
				<themekey>Model</themekey>
				<themekey>Contours</themekey>
			</theme>
			<place>
				<placekt>None</placekt>
				<placekey>Pennsylvania</placekey>
				<placekey>Adams County</placekey>
				<placekey>Columbia County</placekey>
				<placekey>Cumberland County</placekey>
				<placekey>Franklin County</placekey>
				<placekey>Juniata County</placekey>
				<placekey>Lebanon County</placekey>
				<placekey>Lycoming County</placekey>
				<placekey>Mifflin County</placekey>
				<placekey>Montour County</placekey>
				<placekey>Northumberland County</placekey>
				<placekey>Perry County</placekey>
				<placekey>Snyder County</placekey>
				<placekey>Union 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>Contour Processing: Using automated scripting routines within ArcMap, a
					terrain surface was created using the ground (ASPRS Class 2) LiDAR data as well
					as the hydro-flattened breaklines. This surface was then used to generate the
					final 2-foot contour dataset in Esri File Geodatabase format.</procdesc>
				<procdate>2018</procdate>
			</procstep>
		</lineage>
	</dataqual>
	<spdoinfo>
		<direct>Vector</direct>
	</spdoinfo>
	<spref>
		<horizsys>
			<planar>
				<gridsys>
					<gridsysn>Universal Transverse Mercator</gridsysn>
					<utm>
						<utmzone>18</utmzone>
						<transmer>
							<sfctrmer>0.9996</sfctrmer>
							<longcm>-75</longcm>
							<latprjo>0</latprjo>
							<feast>500000</feast>
							<fnorth>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>NAD 1983 (2011)</horizdn>
				<ellips>Geodetic Reference System 80</ellips>
				<semiaxis>6378137.0</semiaxis>
				<denflat>298.257222101</denflat>
			</geodetic>
		</horizsys>
		<vertdef>
			<altsys>
				<altdatum>NAVD 1988 (GEOID 12B)</altdatum>
				<altres>2.0</altres>
				<altunits>feet</altunits>
				<altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
			</altsys>
		</vertdef>
	</spref>
	<eainfo>
		<detailed>
			<enttyp>
				<enttypl>Contour line</enttypl>
				<enttypd>A line on a map that connects points of equal elevation based on a vertical
					datum, usually sea level.</enttypd>
				<enttypds>Esri GIS Dictionary
					http://support.esri.com/en/knowledgebase/GISDictionary/term/contour%20line</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 - PolylineZM</udom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>Type</attrlabl>
				<attrdef>Contour Type</attrdef>
				<attrdefs>LiDAR Data</attrdefs>
				<attrdomv>
					<edom>
						<edomv>Intermediate</edomv>
						<edomvd>LiDAR Data</edomvd>
						<edomvds>LAS version 1.4</edomvds>
					</edom>
				</attrdomv>
				<attrdomv>
					<edom>
						<edomv>Index</edomv>
						<edomvd>LiDAR Data</edomvd>
						<edomvds>LAS version 1.4</edomvds>
					</edom>
				</attrdomv>
			</attr>
		</detailed>
		<overview>
			<eaover>Contours with the types of Intermediate and Index.</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>20181026</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>
