<?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>20181011</pubdate>
				<title>Task Name: WA 3 County LiDAR 2017 B17
				USGS Contract: G16PC00016, Task Order: G17PD01222
				</title>
				<geoform>LiDAR Point Cloud</geoform>
			</citeinfo>
		</citation>
		<descript>
			<abstract>Product: These lidar data are processed Classified LAS 1.4 files, formatted to 9,312 3000 ft x 3000 ft tiles. (Please note that 5 tiles contain no data due to their size and location over water and therefore do not exist.  These tiles include WA3_07786, WA3_08558, WA3_08745, WA3_08821, and WA3_08825.)
			Geographic Extent: This dataset and derived products encompass an area covering approximately 2,917 square miles of south eastern Washington.  The full area is a mix of QL1 and QL2 lidar. 
			Dataset Description: RAW flight line swaths were processed to create 9,312 classified LAS 1.4 files delineated in 3000 ft x 3000 ft tiles. Each LAS file contains LiDAR point information, which has been calibrated, controlled, and classified. From the classified point cloud additional derived products include intensity images, hydro-flattened breaklines, hydro-flattened DEMs, and highest hit surface models of the study area. Ground Control Points were acquired and calibrated by Quantum Spatial, Inc.
			Data acquisition was coordinated by Quantum Spatial and all lidar data calibration, and follow-on processing were completed by Quantum Spatial
			Ground Conditions: Acquisition below aircraft free of smoke, fog and cloud cover.  A small area with remaining snow on the ground was noticed in the data.  The difference was only noticed due to the area being acquired at two different times.  The high snow level was classified to class 21 and the overlapping mission acquired without snow on the ground was used for ground model creation.  A shape of this area has been provided.   
			</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 3DEP initiative. The raw lidar point cloud data were used to create classified lidar LAS files, intensity images, hydro-flattened DEMs, highest hit surface models, and 3D breaklines of rivers, lakes, 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 and all lidar data calibration, and follow-on processing were completed by Quantum Spatial, the prime contractor.
			</supplinf>
			<lidar>
				<ldrinfo>
					<ldrspec>U.S. Geological Survey National Geospatial Program LIDAR Base Specification, Version 1.2</ldrspec>
					<ldrsens>Leica ALS80</ldrsens>
					<ldrmaxnr>15</ldrmaxnr>
					<ldrnps>0.5 m</ldrnps>
					<ldrdens>4</ldrdens>
					<ldranps>0.35</ldranps>
					<ldradens>8</ldradens>
					<ldrfltht>1650</ldrfltht>
					<ldrfltsp>145</ldrfltsp>
					<ldrscana>30</ldrscana>
					<ldrscanr>48</ldrscanr>
					<ldrpulsr>335000</ldrpulsr>
					<ldrpulsd>2.5</ldrpulsd>
					<ldrpulsw>0.75</ldrpulsw>
					<ldrwavel>1064</ldrwavel>
					<ldrmpia>1</ldrmpia>
					<ldrbmdiv>0.22</ldrbmdiv>
					<ldrswatw>884</ldrswatw>
					<ldrswato>67</ldrswato>
					<ldrgeoid>National Geodetic Survey (NGS) Geoid12B</ldrgeoid>
				</ldrinfo>
				<ldrinfo>
					<ldrspec>U.S. Geological Survey National Geospatial Program LIDAR Base Specification, Version 1.2</ldrspec>
					<ldrsens>Leica ALS80</ldrsens>
					<ldrmaxnr>15</ldrmaxnr>
					<ldrnps>1</ldrnps>
					<ldrdens>1</ldrdens>
					<ldranps>0.70</ldranps>
					<ldradens>2</ldradens>
					<ldrfltht>2100</ldrfltht>
					<ldrfltsp>145</ldrfltsp>
					<ldrscana>40</ldrscana>
					<ldrscanr>38</ldrscanr>
					<ldrpulsr>250000</ldrpulsr>
					<ldrpulsd>2.5</ldrpulsd>
					<ldrpulsw>0.75</ldrpulsw>
					<ldrwavel>1064</ldrwavel>
					<ldrmpia>1</ldrmpia>
					<ldrbmdiv>0.22</ldrbmdiv>
					<ldrswatw>1529</ldrswatw>
					<ldrswato>63</ldrswato>
					<ldrgeoid>National Geodetic Survey (NGS) Geoid12B</ldrgeoid>
				</ldrinfo>
				<ldraccur>
					<ldrchacc>0.5</ldrchacc>
					<rawnva>0.083</rawnva>
					<rawnvan>85</rawnvan>
					<clsnva>0.077</clsnva>
					<clsnvan>85</clsnvan>
					<clsvva>.206</clsvva>
					<clsvvan>79</clsvvan>
				</ldraccur>
				<lasinfo>
					<lasver>1.4</lasver>
					<lasprf>6</lasprf>
					<laswheld>Witheld points are identified in these files using the standard LAS Witheld bits.</laswheld>
					<lasolap>Swath overage points are identified in these files using the standard LAS Overlap bits</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>Water</clasitem>
					</lasclass>
					<lasclass>
						<clascode>10</clascode>
						<clasitem>Ignored Ground Near Breakline</clasitem>
					</lasclass>
					<lasclass>
						<clascode>17</clascode>
						<clasitem>Bridge Decks</clasitem>
					</lasclass>
					<lasclass>
						<clascode>21</clascode>
						<clasitem>Snow</clasitem>
					</lasclass>
				</lasinfo>
			</lidar>
		</descript>
		<timeperd>
			<timeinfo>
				<rngdates>
					<begdate>20171003</begdate>
					<enddate>20180704</enddate>
				</rngdates>
			</timeinfo>
			<current>ground condition</current>
		</timeperd>
		<status>
			<progress>Complete</progress>
			<update>None Planned</update>
		</status>
		<spdom>
			<bounding>
				<westbc>-119.048030</westbc>
				<eastbc>-117.183731</eastbc>
				<northbc>46.732836</northbc>
				<southbc>45.961812</southbc>
			</bounding>
			<lboundng>
				<leftbc>2009394.211531</leftbc>
				<rightbc>2472308.459371</rightbc>
				<topbc>513792.507063</topbc>
				<bottombc>246441.682612</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>
			</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. 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>These LAS data files include all data points collected. No points have been removed or excluded. A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. The raw point cloud is of good quality and data passes Non-Vegetated Vertical Accuracy specifications.</complete>
		<posacc>
			<vertacc>
				<vertaccr>The specifications require that raw Non-vegetated Vertical Accuracy (NVA) be computed from the both the raw lidar point cloud swath files and the derived DEMs. Additionally, the Vegetated Vertical Accuracy (VVA) is computed from the derived DEMs. The NVA was tested with 85 independent check points located in open terrain, and distributed throughout the project as feasible, while VVA was tested with 79 independent check points located in a variety of vegetation classes distributed throughout the project area. These check points were not used in the calibration or post processing of the lidar point cloud data. Specifications for this project require that the NVA be 19.6 cm meters or better AccuracyZ at 95% confidence level and that the VVA be 29.4 cm or better AccuracyZ at the 95th percentile.
				</vertaccr>
				<qvertpa>
					<vertaccv>0.083</vertaccv>
					<vertacce>Tested 0.083 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 data using 85 independent checkpoints located in Bare Earth and Urban land cover classes. 
					</vertacce>
				</qvertpa>
				<qvertpa>
					<vertaccv>0.077</vertaccv>
					<vertacce>Tested 0.077 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 classified lidar point cloud files was calculated against rasters derived from the final calibrated, controlled, and classified data using 85 independent checkpoints located in Bare Earth and Urban land cover classes. 
					</vertacce>
				</qvertpa>
				<qvertpa>
					<vertaccv>0.206</vertaccv>
					<vertacce>Tested 0.206 meters VVA at the 95th percentile as defined by the National Standards for Spatial Data Accuracy (NSSDA). The VVA of the classified lidar point cloud files was calculated against rasters derived from the final calibrated, controlled, and classified data using 85 independent checkpoints located in forest, shrub, and tall grass land cover classes. 
					</vertacce>
				</qvertpa>
			</vertacc>
		</posacc>
		<lineage>
			<srcinfo>
				<srccite>
					<citeinfo>
						<origin>Quantum Spatial</origin>
						<pubdate>20181011</pubdate>
						<title>Base Station Control</title>
						<geoform>vector digital and tabular data</geoform>
						<pubinfo>
							<pubplace>Corvallis, OR</pubplace>
							<publish>Quantum Spatial</publish>
						</pubinfo>
					</citeinfo>
				</srccite>
				<typesrc>hard drive</typesrc>
				<srctime>
					<timeinfo>
						<sngdate>
							<caldate>20181011</caldate>
						</sngdate>
					</timeinfo>
					<srccurr>publication date</srccurr>
				</srctime>
				<srccitea>Base_Station_Control</srccitea>
				<srccontr>This data source was used (along with the airborne GPS/IMU data) to georeference the LiDAR point cloud data.</srccontr>
			</srcinfo>
			<srcinfo>
				<srccite>
					<citeinfo>
						<origin>Quantum Spatial</origin>
						<pubdate>20181011</pubdate>
						<title>Smooth Best Estimate Trajectories</title>
						<geoform>vector digital and tabular data</geoform>
						<pubinfo>
							<pubplace>Corvallis, OR</pubplace>
							<publish>Quantum Spatial</publish>
						</pubinfo>
					</citeinfo>
				</srccite>
				<typesrc>hard drive</typesrc>
				<srctime>
					<timeinfo>
						<sngdate>
							<caldate>20181011</caldate>
						</sngdate>
					</timeinfo>
					<srccurr>publication date</srccurr>
				</srctime>
				<srccitea>SBETs</srccitea>
				<srccontr>This data source was used (along with base station control data) to georeference the LiDAR point cloud data.</srccontr>
			</srcinfo>
			<srcinfo>
				<srccite>
					<citeinfo>
						<origin>Quantum Spatial</origin>
						<pubdate>20181011</pubdate>
						<title>Supplemental Ground Control Points</title>
						<geoform>vector digital and tabular data</geoform>
						<pubinfo>
							<pubplace>Corvallis, OR</pubplace>
							<publish>Quantum Spatial</publish>
						</pubinfo>
					</citeinfo>
				</srccite>
				<typesrc>hard drive</typesrc>
				<srctime>
					<timeinfo>
						<sngdate>
							<caldate>20181011</caldate>
						</sngdate>
					</timeinfo>
					<srccurr>publication date</srccurr>
				</srctime>
				<srccitea>SGCPs</srccitea>
				<srccontr>This data source was used to refine airborne GPS positional accuracy during the calibration process.</srccontr>
			</srcinfo>
			<srcinfo>
				<srccite>
					<citeinfo>
						<origin>Quantum Spatial</origin>
						<pubdate>20181011</pubdate>
						<title>Ground Control Quality Check Points </title>
						<geoform>vector digital and tabular data</geoform>
						<pubinfo>
							<pubplace>Corvallis, OR</pubplace>
							<publish>Quantum Spatial</publish>
						</pubinfo>
					</citeinfo>
				</srccite>
				<typesrc>hard drive</typesrc>
				<srctime>
					<timeinfo>
						<sngdate>
							<caldate>20181011</caldate>
						</sngdate>
					</timeinfo>
					<srccurr>publication date</srccurr>
				</srctime>
				<srccitea>QCPs</srccitea>
				<srccontr>This data source was used to assess the accuracy of LiDAR point cloud data.</srccontr>
			</srcinfo>
			<srcinfo>
				<srccite>
					<citeinfo>
						<origin>Quantum Spatial</origin>
						<pubdate>20181011</pubdate>
						<title>LiDAR RAW Data</title>
						<geoform>LiDAR data</geoform>
						<pubinfo>
							<pubplace>Corvallis</pubplace>
							<publish>20181011</publish>
						</pubinfo>
					</citeinfo>
				</srccite>
				<typesrc>hard drive</typesrc>
				<srctime>
					<timeinfo>
						<rngdates>
							<begdate>20171003</begdate>
							<enddate>20180704</enddate>
						</rngdates>
					</timeinfo>
					<srccurr>ground condition</srccurr>
				</srctime>
				<srccitea>RAW_LiDAR</srccitea>
				<srccontr>This data source was used to populate the LiDAR point cloud data.</srccontr>
			</srcinfo>
			<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 (less than 500 MB) 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>20181011</procdate>
					<proccont>
						<cntinfo>
							<cntorgp>
								<cntorg>Quantum Spatial</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>
					</proccont>
			</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 final NVA and VVA for the project using ground control quality check points.</procdesc>
				<srcused>Base_Station_Control, SBETs, QCPs, RAW_LiDAR</srcused>
				<procdate>20181011</procdate>
				<srcprod>Classified_LiDAR</srcprod>
					<proccont>
						<cntinfo>
							<cntorgp>
								<cntorg>Quantum Spatial</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>
					</proccont>
			</procstep>
		</lineage>
	</dataqual>
	<spdoinfo>
		<direct>Point</direct>
	</spdoinfo>
	<spref>
		<horizsys>
			<planar>
				<gridsys>
					<gridsysn>State Plane Coordinate System 1983</gridsysn>
					<spcs>
						<spcszone>4602</spcszone>
						<lambertc>
							<stdparll>45.83333333333334</stdparll>
							<longcm>-120.5</longcm>
							<latprjo>45.33333333333334</latprjo>
							<feast>1640416.666666667</feast>
							<fnorth>0.0</fnorth>
						</lambertc>
					</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>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>US survey feet</altunits>
				<altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
			</altsys>
		</vertdef>
	</spref>
	<metainfo>
		<metd>20181011</metd>
		<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>
	</metainfo>
</metadata>