<?xml version="1.0" encoding="UTF-8"?>
<metadata>
	<idinfo>
		<citation>
			<citeinfo>
				<origin>Quantum Spatial, Inc.</origin>
				<pubdate>20191113</pubdate>
				<title>Task Name: WA Olympic Peninsula LiDAR 2017 B17, USGS Contract: G16PC00016, Task Order: G17PD00827</title>
				<geoform>LiDAR Point Cloud</geoform>
			</citeinfo>
		</citation>
		<descript>
			<abstract>
			Geographic Extent: This dataset and derived products encompass Olympic Peninsula Area 2, an approximately 1,547 square mile portion of the Olympic Peninsula 3DEP project area, which covers approximately 5,352 square miles of Western Washington in the Olympic Peninsula region. 
			Dataset Description: RAW flight line swaths were processed to create 3,371 classified LAS 1.4 files delineated in 1/100th USGS Quadrangle tiles. (The following tile does not exist as no points fall within its boundary due its small size and the fact it falls completely over water: 46123B2312) Each LAS file contains LiDAR point information, which has been calibrated, controlled, and classified. Additional derived products include intensity images, hydro-flattened DEMs, highest hit surface models, and 3D breaklines of rivers, lakes, coastlines and bridges within the study area. Tiled deliverables that are split between delivery boundaries have been given an extension of "_[delivery#]" at the end of the file name. For this delivery, tiled deliverables have been given an "_2" extension. 
			Ground Conditions: Acquisition below aircraft free of smoke, fog and cloud cover. Ground Control Points were acquired and calibrated by Quantum Spatial, Inc.
			Tidal Conditions: The Olympic Peninsula Area 2 project area is bounded by miles of coastline and includes many tidally influenced lakes and river deltas.  Since the project was acquired over many months, it is expected that there is data captured at varying tide levels which lends issues to the hydroflattening process.  To accommodate these tidal and temporal differences, it is not uncommon to "stair-step" the flattened water surface to most accurately reflect the different missions in the project while capturing as much ground as permitted.  Please reference section C.1.c.(ii).(d) of the task order and the Hydroflattening section of the USGS LiDAR Base Specification, V. 1.2 for more information.
			</abstract>
			<purpose>The purpose of the lidar data was to produce a high accuracy 3D dataset that meets all necessary standards laid out by the Olympic Peninsula 3DEP contract. The raw lidar point cloud data were used to create classified lidar LAS files, intensity images, hydro-flattened DEMs, and 3D breaklines of rivers, lakes, coastlines and bridges within the study area.</purpose>
			<supplinf>
				USGS Contract No. G16PC00016
				CONTRACTOR: Quantum Spatial, Inc. 
				Ground Control Points were acquired and calibrated by Quantum Spatial, Inc. 
				Data acquisition was coordinated by Quantum Spatial. Quantum Spatial, Eagle Aerial, and Airborne Imaging all acquired portions of this project area. All lidar data calibration, and follow-on processing were completed by Quantum Spatial.
			</supplinf>
			<lidar>
				<ldrinfo>
					<ldrspec>U.S. Geological Survey National Geospatial Program LIDAR Base Specification, Version 1.2</ldrspec>
					<ldrsens>Riegl Q1560 and VQ-1560i</ldrsens>
					<ldrmaxnr>Unlimited</ldrmaxnr>
					<ldrnps>0.7</ldrnps>
					<ldrdens>4</ldrdens>
					<ldranps>0.35</ldranps>
					<ldradens>8</ldradens>
					<ldrfltht>1200</ldrfltht>
					<ldrfltsp>170</ldrfltsp>
					<ldrscana>58.5</ldrscana>
					<ldrscanr>107 lines per second</ldrscanr>
					<ldrpulsr>400</ldrpulsr>
					<ldrpulsd>3</ldrpulsd>
					<ldrpulsw>0.9</ldrpulsw>
					<ldrwavel>1064</ldrwavel>
					<ldrmpia>1</ldrmpia>
					<ldrbmdiv>0.25</ldrbmdiv>
					<ldrswatw>1344</ldrswatw>
					<ldrswato>60</ldrswato>
					<ldrgeoid>National Geodetic Survey (NGS) Geoid03</ldrgeoid>
					<ldrcrs>NAD_1983_HARN_StatePlane_Washington_South_FIPS_4602_Feet</ldrcrs>
				</ldrinfo>
				<ldrinfo>
					<ldrspec>U.S. Geological Survey National Geospatial Program LIDAR Base Specification, Version 1.2</ldrspec>
					<ldrsens>Riegl Q780</ldrsens>
					<ldrmaxnr>Unlimited</ldrmaxnr>
					<ldrnps>0.7</ldrnps>
					<ldrdens>4</ldrdens>
					<ldranps>0.35</ldranps>
					<ldradens>8</ldradens>
					<ldrfltht>1300</ldrfltht>
					<ldrfltsp>140</ldrfltsp>
					<ldrscana>58.5</ldrscana>
					<ldrscanr>207 lines per second</ldrscanr>
					<ldrpulsr>400</ldrpulsr>
					<ldrpulsd>3</ldrpulsd>
					<ldrpulsw>0.9</ldrpulsw>
					<ldrwavel>1064</ldrwavel>
					<ldrmpia>1</ldrmpia>
					<ldrbmdiv>0.25</ldrbmdiv>
					<ldrswatw>1456</ldrswatw>
					<ldrswato>60</ldrswato>
					<ldrgeoid>National Geodetic Survey (NGS) Geoid03</ldrgeoid>
					<ldrcrs>NAD_1983_HARN_StatePlane_Washington_South_FIPS_4602_Feet</ldrcrs>
				</ldrinfo>
				<ldrinfo>
					<ldrspec>U.S. Geological Survey National Geospatial Program LIDAR Base Specification, Version 1.2</ldrspec>
					<ldrsens>ALS 80</ldrsens>
					<ldrmaxnr>Unlimited</ldrmaxnr>
					<ldrnps>0.7</ldrnps>
					<ldrdens>4</ldrdens>
					<ldranps>0.35</ldranps>
					<ldradens>8</ldradens>
					<ldrfltht>1550</ldrfltht>
					<ldrfltsp>120</ldrfltsp>
					<ldrscana>40</ldrscana>
					<ldrscanr>48</ldrscanr>
					<ldrpulsr>341.6</ldrpulsr>
					<ldrpulsd>2.5</ldrpulsd>
					<ldrpulsw>0.9</ldrpulsw>
					<ldrwavel>1064</ldrwavel>
					<ldrmpia>1</ldrmpia>
					<ldrbmdiv>0.22</ldrbmdiv>
					<ldrswatw>1128</ldrswatw>
					<ldrswato>60</ldrswato>
					<ldrgeoid>National Geodetic Survey (NGS) Geoid03</ldrgeoid>
					<ldrcrs>NAD_1983_HARN_StatePlane_Washington_South_FIPS_4602_Feet</ldrcrs>
				</ldrinfo>
				<ldrinfo>
					<ldrspec>U.S. Geological Survey National Geospatial Program LIDAR Base Specification, Version 1.2</ldrspec>
					<ldrsens>Riegl VQ-1560i</ldrsens>
					<ldrmaxnr>Unlimited</ldrmaxnr>
					<ldrnps>0.7</ldrnps>
					<ldrdens>4</ldrdens>
					<ldranps>0.35</ldranps>
					<ldradens>8</ldradens>
					<ldrfltht>1650</ldrfltht>
					<ldrfltsp>160</ldrfltsp>
					<ldrscana>58.5</ldrscana>
					<ldrscanr>Auto</ldrscanr>
					<ldrpulsr>400</ldrpulsr>
					<ldrpulsd>3</ldrpulsd>
					<ldrpulsw>0.9</ldrpulsw>
					<ldrwavel>1064</ldrwavel>
					<ldrmpia>1</ldrmpia>
					<ldrbmdiv>0.25</ldrbmdiv>
					<ldrswatw>1848</ldrswatw>
					<ldrswato>60</ldrswato>
					<ldrgeoid>National Geodetic Survey (NGS) Geoid03</ldrgeoid>
					<ldrcrs>NAD_1983_HARN_StatePlane_Washington_South_FIPS_4602_Feet</ldrcrs>
				</ldrinfo>
				<ldraccur>
					<ldrchacc>0.457</ldrchacc>
					<rawnva>0.081</rawnva>
					<rawnvan>68</rawnvan>
					<clsnva>0.086</clsnva>
					<clsnvan>68</clsnvan>
					<clsvva>0.219</clsvva>
					<clsvvan>55</clsvvan>
				</ldraccur>
				<lasinfo>
					<lasver>1.4</lasver>
					<lasprf>6</lasprf>
					<laswheld>Withheld points were identified in these files using the standard LAS Withheld bit.</laswheld>
					<lasolap>Swath overage points were identified in these files using the standard LAS overlap bit.</lasolap>
					<lasintr>16</lasintr>
					<lasclass>
						<clascode>1</clascode>
						<clasitem>Processed, but Unclassified</clasitem>
					</lasclass>
					<lasclass>
						<clascode>2</clascode>
						<clasitem>Bare earth ground</clasitem>
					</lasclass>
					<lasclass>
						<clascode>7</clascode>
						<clasitem>Low Noise</clasitem>
					</lasclass>
					<lasclass>
						<clascode>9</clascode>
						<clasitem>NIR Water Surface</clasitem>
					</lasclass>
					<lasclass>
						<clascode>17</clascode>
						<clasitem>Bridge Decks</clasitem>
					</lasclass>
					<lasclass>
						<clascode>20</clascode>
						<clasitem>Ignored Ground Near Breaklines</clasitem>
					</lasclass>
					<lasclass>
						<clascode>22</clascode>
						<clasitem>Temporal Exclusion</clasitem>
					</lasclass>
				</lasinfo>
			</lidar>
		</descript>
		<timeperd>
			<timeinfo>
				<rngdates>
					<begdate>20180219</begdate>
					<enddate>20190425</enddate>
				</rngdates>
			</timeinfo>
			<current>ground condition</current>
		</timeperd>
		<status>
			<progress>Complete</progress>
			<update>None Planned</update>
		</status>
		<spdom>
			<bounding>
				<westbc>-124.165360</westbc>
				<eastbc>-123.019618</eastbc>
				<northbc>46.991462</northbc>
				<southbc>46.118543</southbc>
			</bounding>
			<lboundng>
				<leftbc>725542.297654</leftbc>
				<rightbc>1001924.230949</rightbc>
				<topbc>615029.021279</topbc>
				<bottombc>307270.921794</bottombc>
			</lboundng>
		</spdom>
		<keywords>
			<theme>
				<themekt>none</themekt>
				<themekey>model</themekey>
				<themekey>LAS Point Cloud</themekey>
				<themekey>remote sensing</themekey>
				<themekey>Elevation data</themekey>
				<themekey>lidar</themekey>
			</theme>
			<place>
				<placekt>none</placekt>
				<placekey>Washington</placekey>
				<placekey>Olympic Peninsula</placekey>
				<placekey>Pacific County</placekey>
				<placekey>Lewis County</placekey>
				<placekey>Wahkiakum County</placekey>
				<placekey>Grays Harbor 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 its limitations. Acknowledgment of the U.S. Geological Survey would be appreciated for products derived from these data.</useconst>
		<native>POSPac 8.1, RiProcess 1.8.4, RiWorld 5.1.3, SDC Import 2.2.5, Waypoint Inertial Explorer 8.7, Leica Cloudpro 1.2.4, Microstation Version 10.0, TerraScan Version 18, TerraModeler Version 18, TerraMatch Version 18, ESRI ArcGIS 10.3.1, LasMonkey 2.3.4 (Proprietary), Las Product Creator 3.1 (Proprietary), Windows 7 Operating System</native>
	</idinfo>
	<dataqual>
		<logic>Classified LAS files were tested by QSI for both vertical and horizontal accuracy. All data is seamless from one tile to the next, no gaps or no data areas.</logic>
		<complete>LAS files	include	all	data points collected. No points have been removed or excluded.  Shaded relief images have been visually inspected for data errors such as pits, border artifacts, and shifting. Lidar flight lines have been examined to ensure consistent elevation values across overlapping flight lines. The raw point cloud is of good quality and data passes Non Vegetated Vertical Accuracy specifications.</complete>
		<posacc>
			<horizpa>
				<horizpar>LiDAR horizontal accuracy is a function of Global Navigation Satellite System (GNSS) derived positional error, flying altitude, and INS-derived attitude error.  The obtained RMSEr value is multiplied by a conversion factor of 1.7308 to yield the horizontal component (ACCr) of the National Standards for Spatial Data Accuracy (NSSDA) reporting standard where a theoretical point will fall within the obtained radius 95 percent of the time.  Using a maximum flying height of 1,650m, this data set was produced to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 6.8 cm RMSEx / RMSEy Horizontal Accuracy Class which equates to Positional Horizontal Accuracy = +/- 45.7 cm at a 95% confidence level.</horizpar>
			</horizpa>
			<vertacc>
				<vertaccr>The project specifications require that Non-Vegetated Vertical Accuracy (NVA) be computed for raw lidar point cloud swath files. The required accuracy (ACCz) is: 19.6 cm at a 95% confidence level, derived according to NSSDA, i.e., based on RMSE of 10 cm in the “bare earth” and "urban" land cover classes. The NVA was tested with 82 checkpoints located in bare earth and urban (non-vegetated) areas. These check points were not used in the calibration or post processing of the lidar point cloud data. The checkpoints were distributed throughout the project area and were surveyed using GPS techniques. See survey report for additional survey methodologies. Elevations from the unclassified lidar surface were measured for the x,y location of each check point. Elevations interpolated from the lidar surface were then compared to the elevation values of the surveyed control points. AccuracyZ has been tested to meet 19.6 cm or better Non-Vegetated Vertical Accuracy at 95% confidence level using RMSE(z) x 1.9600 as defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASRPS Guidelines.
				</vertaccr>
				<qvertpa>
					<vertaccv>0.081</vertaccv>
					<vertacce>Tested 0.081 meters NVA at a 95% confidence level using RMSE(z) x 1.9600 as defined by the National Standards for Spatial Data Accuracy (NSSDA). The NVA of the raw lidar point cloud files was calculated against TINs derived from the final calibrated and controlled swath data using 68 independent checkpoints located in Bare Earth and Urban land cover classes with a resulting RMSE of 0.041 meters. 
					</vertacce>
				</qvertpa>
			</vertacc> 
		</posacc>
		<lineage>
			<procstep>
				<procdesc>LiDAR Pre-Processing:
					1. Review flight lines and data to ensure complete coverage of the study area and positional accuracy of the laser points.
					2. Resolve kinematic corrections for aircraft position data using kinematic aircraft GPS and static ground GPS data.
					3. Develop a smoothed best estimate of trajectory (SBET) file that blends post-processed aircraft position with sensor head position and attitude recorded throughout the survey.
					4. Calculate laser point position by associating SBET position to each laser point return time, scan angle, intensity, etc. Create raw laser point cloud data for the entire survey in *.las format. Convert data to orthometric elevations by applying a geoid correction.
					5. Import raw laser points into manageable blocks to perform manual relative accuracy calibration and filter erroneous points. Classify ground points for individual flight lines.
					6. Using ground classified points per each flight line, test the relative accuracy. Perform automated line-to-line calibrations for system attitude parameters (pitch, roll, heading), mirror flex (scale) and GPS/IMU drift. Calculate calibrations on ground classified points from paired flight lines and apply results to all points in a flight line. Use every flight line for relative accuracy calibration.
					7. Adjust the point cloud by comparing ground classified points to supplemental ground control points.</procdesc>
				<srcused>Base_Station_Control, SBETs, SGCPs, RAW_LiDAR</srcused>
				<procdate>20190425</procdate>
			</procstep>
			<procstep>
				<procdesc>LiDAR Post-Processing:
					1. Classify data to ground and other client designated classifications using proprietary classification algorithms.
					2. Manually QC data classification
					3. After completion of classification and final QC approval, calculate NVA and VVA, and density information for the project.</procdesc>
				<procdate>20190425</procdate>
			</procstep>
		</lineage>
	</dataqual>
	<spdoinfo>
		<direct>Vector</direct>
		<ptvctinf>
			<sdtsterm>
				<sdtstype>Point</sdtstype>
			</sdtsterm>
		</ptvctinf>
	</spdoinfo>
	<spref>
		<horizsys>
			<planar>
				<gridsys>
					<gridsysn>State Plane Coordinate System 1983</gridsysn>
					<spcs>
						<spcszone>4602</spcszone>
						<lambertc>
							<stdparll>45.83333333</stdparll>
							<stdparll>47.33333333</stdparll>
							<longcm>-120.5</longcm>
							<latprjo>45.33333333</latprjo>
							<feast>1640416.667</feast>
							<fnorth>0</fnorth>
						</lambertc>
					</spcs>
				</gridsys>
				<planci>
					<plance>coordinate pair</plance>
					<coordrep>
						<absres>0.01</absres>
						<ordres>0.01</ordres>
					</coordrep>
					<plandu>U.S. Survey Feet</plandu>
				</planci>
			</planar>
			<geodetic>
				<horizdn>North American Datum of 1983 (CORS96) defined (HARN)</horizdn>
				<ellips>GRS_1980</ellips>
				<semiaxis>6378137.0</semiaxis>
				<denflat>298.257223563</denflat>
			</geodetic>
		</horizsys>
		<vertdef>
			<altsys>
				<altdatum>North American Vertical Datum of 1988, Geoid 03</altdatum>
				<altres> 0.01</altres>
				<altunits>U.S. Survey Feet</altunits>
				<altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
			</altsys>
		</vertdef>
	</spref>
	<metainfo>
		<metd>20190810</metd>
		<metrd>20190810</metrd>
		<metc>
			<cntinfo>
				<cntorgp>
					<cntorg>Quantum Spatial, Inc.</cntorg>
				</cntorgp>
				<cntaddr>
					<addrtype>mailing and physical</addrtype>
					<address>1100 NE Circle Blvd., Suite 126</address>
					<city>Corvallis</city>
					<state>OR</state>
					<postal>97330</postal>
					<country>USA</country>
				</cntaddr>
				<cntvoice>541-752-1204</cntvoice>
			</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>
		<metextns>
			<onlink>None</onlink>
			<metprof>None</metprof>
		</metextns>
	</metainfo>
</metadata>