<metadata>
	<idinfo>
		<citation>
			<citeinfo>
				<origin>Quantum Spatial</origin>
				<pubdate>20160225</pubdate>
				<title>LiDAR data for Wallowa 2015 LiDAR DOGAMI Purchase Order WS-2015-11B
					Wallowa_LiDAR_2015</title>
				<geoform>LiDAR point cloud</geoform>
			</citeinfo>
		</citation>
		<descript>
			<abstract>Geographic Extent: This dataset is LiDAR point cloud data and derived products encompassing a 100 meter buffer around an area of interest (AOI) consisting of approximately 553 total square miles near Hells Canyon National Recreational Park and the surrounding areas located in northeast Oregon. RAW flight line swaths were processed to create 1247 classified LAS 1.4 files delineated in 1/100th USGS Quadrangles and named according to the USGS Quadrangle schema. Each LAS file contains LiDAR point information, which has been calibrated, controlled, and classified.  Additional derived products include tiled hydro flattened bare earth DEMs (tiled in 1/4 USGS Quandrangles), intensity images (tiled in 1/4 USGS Quandrangles), and hydro-flattening Breaklines in ESRI Shapefile format.  Data was collected between 07/04/15 and 07/15/15.</abstract>
			<LiDAR>
				<ldrinfo>
					<ldrspec>USGS NGP Base Specification v1.2</ldrspec>
					<ldrsens>Leica ALS70</ldrsens>
					<ldrmaxnr>15</ldrmaxnr>
					<ldrnps>0.5</ldrnps>
					<ldrdens>4</ldrdens>
					<ldranps>0.354</ldranps>
					<ldradens>8</ldradens>
					<ldrfltht>1400</ldrfltht>
					<ldrfltsp>110</ldrfltsp>
					<ldrscana>30</ldrscana>
					<ldrscanr>58.1</ldrscanr>
					<ldrpulsr>198</ldrpulsr>
					<ldrpulsd>9</ldrpulsd>
					<ldrpulsw>.32</ldrpulsw>
					<ldrwavel>1064</ldrwavel>
					<ldrmpia>1</ldrmpia>
					<ldrbmdiv>0.22</ldrbmdiv>
					<ldrswatw>750</ldrswatw>
					<ldrswato>60</ldrswato>
					<ldrcrs>NAD_1983_2011_Oregon_Statewide_Lambert_Feet</ldrcrs>
					<ldrgeoid>National Geodetic Survey (NGS) Geoid12A</ldrgeoid>
				</ldrinfo>
				<ldraccur>
					<ldrchacc>0.17</ldrchacc>
					<rawnva>0.073</rawnva>
					<rawnvan>137</rawnvan>					
				</ldraccur>
				<lasinfo>
					<lasver>1.4</lasver>
					<lasprf>7</lasprf>
					<laswheld>Witheld points were identified in these files using the standard las witheld 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>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 (breakline proximity)</clasitem>
					</lasclass>
					<lasclass>
						<clascode>11</clascode>
						<clasitem>Withheld</clasitem>
					</lasclass>
					<lasclass>
						<clascode>17</clascode>
						<clasitem>Bridge Deck</clasitem>
					</lasclass>
				</lasinfo>
			</LiDAR>
			<purpose>Data was collected to aid OLC in assessing the topographic and geophysical properties of the study area. The LiDAR point cloud data were used to create classified LiDAR LAS files, intensity images, 3D breaklines, and bare earth hydro-flattened DEMs.</purpose>
			<supplinf>Acquisition and all subsequent processing was completed by Quantum Spatial.  
			In some areas of heavy vegetation or forest cover, there may be relatively few ground points in the LiDAR data. TINing the points produces large triangles and hence the elevations may be less accurate within such areas.</supplinf>
		</descript>
		<timeperd>
			<timeinfo>
				<rngdates>
					<begdate>20150704</begdate>
					<enddate>20150715</enddate>
				</rngdates>
			</timeinfo>
			<current>ground condition</current>
		</timeperd>
		<status>
			<progress>Complete</progress>
			<update>None planned</update>
		</status>
		<spdom>
			<bounding>
				<westbc>-118.136995</westbc>
				<eastbc>-116.894580</eastbc>
				<northbc>45.794744</northbc>
				<southbc>45.241094</southbc>
			</bounding>
			<lboundng>
				<leftbc>1920575.993533</leftbc>
				<rightbc>2232336.157728</rightbc>
				<topbc>1483256.376922</topbc>
				<bottombc>1292559.673569</bottombc>
			</lboundng>
		</spdom>
		<keywords>
			<theme>
				<themekt>None</themekt>
				<themekey>Elevation data</themekey>
				<themekey>LiDAR</themekey>
				<themekey>Hydrology</themekey>
				<themekey>Light Detection and Ranging</themekey>
				<themekey>Topography</themekey>
				<themekey>Bare Earth</themekey>
				<themekey>Bare Earth Hydroflattened</themekey>
				<themekey>Breaklines</themekey>
				<themekey>DEM</themekey>
				<themekey>Digital Elevation Model</themekey>
				<themekey>Intensity</themekey>
			</theme>
			<place>
				<placekt>None</placekt>
				<placekey>Wallowa County</placekey>
				<placekey>United States</placekey>
				<placekey>Oregon</placekey>
				<placekey>Grande Ronde</placekey>
				<placekey>Wallowa</placekey>
				<placekey>Enterprise</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 it's limitations. </useconst>
		<ptcontac>
			<cntinfo>
				<cntorgp>
					<cntorg>Quantum Spatial</cntorg>
					<cntper>Cathy Power</cntper>
				</cntorgp>
				<cntaddr>
					<addrtype>mailing and physical</addrtype>
					<address>517 SW 2nd St., Suite 400</address>
					<city>Corvallis</city>
					<state>OR</state>
					<postal>97333</postal>
					<country>USA</country>
				</cntaddr>
				<cntvoice>541-752-1204</cntvoice>
				<cntemail>cpower@quantumspatial.com</cntemail>
				<hours>Monday through Friday 8:30 AM to 5:00 PM (Pacific Standard Time)</hours>
				<cntinst>If unable to reach the contact by telephone, please send an email.</cntinst>
			</cntinfo>
		</ptcontac>
		<native>Waypoint Inertial Explorer v.8.5 ; Trimble Business Center v.3.00; Geographic Calculator 2013; IPAS TC v.3.1; ALS Post Processing Software v.2.74; TerraScan v.15; TerraMatch v.15; TerraModeler v.15; ArcMap v.10.1; Windows 7 Operating System</native>
	</idinfo>
	<dataqual>
		<logic>Data cover the entire area specified for this project. All data is seamless from one tile to the next.</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 Fundamental Vertical Accuracy specifications.</complete>
		<posacc>
			<vertacc>
				<vertaccr>The vertical accuracy was tested with ground control quality check points located in open terrain. Ground control quality check points (QCPs) were distributed throughout the AOI as feasible given ground access constraints. Specifications for this project require that the NVA be 17.6 cm or better AccuracyZ at 95 percent confidence level.</vertaccr>
				<qvertpa>
					<vertaccv>0.073</vertaccv>
					<vertacce>Accuracy was assessed using 137 ground survey RTK (real time kinematic) points. The RMSE was computed to be 0.037 meters. AccuracyZ has been tested to meet 17.6 cm Fundamental Vertical Accuracy at 95 Percent 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)/ASPRS Guidelines.</vertacce>
				</qvertpa>
			</vertacc>
		</posacc>
		<lineage>
			<srcinfo>
				<srccite>
					<citeinfo>
						<origin>Quantum Spatial</origin>
						<pubdate>20160225</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>20160225</caldate>
						</sngdate>
					</timeinfo>
					<srccurr>publication date</srccurr>
				</srctime>
				<srccitea>Wallowa_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>20160225</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>20160225</caldate>
						</sngdate>
					</timeinfo>
					<srccurr>publication date</srccurr>
				</srctime>
				<srccitea>Wallowa_SBETs</srccitea>
				<srccontr>This data source was used (along with ground control data) to georeference the LiDAR point cloud data.</srccontr>
			</srcinfo>
			<srcinfo>
				<srccite>
					<citeinfo>
						<origin>Quantum Spatial</origin>
						<pubdate>20160225</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>20160225</caldate>
						</sngdate>
					</timeinfo>
					<srccurr>publication date</srccurr>
				</srctime>
				<srccitea>Wallowa_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>20160225</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>on-line</typesrc>
				<srctime>
					<timeinfo>
						<sngdate>
							<caldate>20160225</caldate>
						</sngdate>
					</timeinfo>
					<srccurr>publication date</srccurr>
				</srctime>
				<srccitea>Wallowa_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>20160225</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>20160225</caldate>
						</sngdate>
					</timeinfo>
					<srccurr>publication date</srccurr>
				</srctime>
				<srccitea>Wallowa_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>20160225</pubdate>
						<title>LiDAR RAW Data for Wallowa 2015</title>
						<geoform>LiDAR data</geoform>
						<pubinfo>
							<pubplace>Corvallis</pubplace>
							<publish>20160225</publish>
						</pubinfo>
					</citeinfo>
				</srccite>
				<typesrc>hard drive</typesrc>
				<srctime>
					<timeinfo>
						<rngdates>
							<begdate>20150704</begdate>
							<enddate>20150715</enddate>
						</rngdates>
					</timeinfo>
					<srccurr>ground condition</srccurr>
				</srctime>
				<srccitea>Wallowa_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 geoid03 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>Wallowa_Base_Station_Control, Wallowa_SBETs, Wallowa_SGCPs, Wallowa_RAW_LiDAR</srcused>
				<procdate>20160225</procdate>
					<proccont>
						<cntinfo>
							<cntorgp>
								<cntorg>Quantum Spatial</cntorg>
							</cntorgp>
							<cntaddr>
								<addrtype>mailing and physical</addrtype>
									<address>517 SW 2nd Street, Suite 400</address>
									<city>Corvallis</city>
									<state>OR</state>
									<postal>97333</postal>
									<country>USA</country>
							</cntaddr>
							<cntvoice>541-752-1204</cntvoice>
							<cntfax>541-752-3770</cntfax>
							<hours>Monday through Friday 8:30 AM to 5:00 PM (Pacific Standard Time)</hours>
						</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 NVA and VVA and density information for the project using ground control quality check points.</procdesc>
				<srcused>Wallowa_Base_Station_Control, Wallowa_SBETs, Wallowa_QCPs, Wallowa_RAW_LiDAR</srcused>
				<procdate>2015</procdate>
				<srcprod>Wallowa_LiDAR_2015</srcprod>
					<proccont>
						<cntinfo>
							<cntorgp>
								<cntorg>Quantum Spatial</cntorg>
							</cntorgp>
							<cntaddr>
								<addrtype>mailing and physical</addrtype>
									<address>517 SW 2nd Street, Suite 400</address>
									<city>Corvallis</city>
									<state>OR</state>
									<postal>97333</postal>
									<country>USA</country>
							</cntaddr>
							<cntvoice>541-752-1204</cntvoice>
							<cntfax>541-752-3770</cntfax>
							<hours>Monday through Friday 8:30 AM to 5:00 PM (Pacific Standard Time)</hours>
						</cntinfo>
					</proccont>
			</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>3601</spcszone>
							<lambertc>
								<stdparll>43.0</stdparll>
								<longcm>-120.5</longcm>
								<latprjo>41.75</latprjo>
								<feast>1312335.958005249</feast>
								<fnorth>0.0</fnorth>
							</lambertc>
						</spcs>
				</gridsys>
				<planci>
					<plance>coordinate pair</plance>
					<coordrep>
						<absres>0.01</absres>
						<ordres>0.01</ordres>
					</coordrep>
					<plandu>international feet</plandu>
				</planci>
			</planar>
			<geodetic>
				<horizdn>North American Datum of 1983</horizdn>
				<ellips>GRS_1980</ellips>
				<semiaxis>6378137.0</semiaxis>
				<denflat>298.257222101</denflat>
			</geodetic>
		</horizsys>
		<vertdef>
			<altsys>
				<altdatum>North American Vertical Datum of 1988</altdatum>
				<altres> 0.01</altres>
				<altunits>international feet</altunits>
				<altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
			</altsys>
		</vertdef>
	</spref>
	<metainfo>
		<metd>20160225</metd>
		<metrd>20160225</metrd>
		<metc>
			<cntinfo>
				<cntorgp>
					<cntorg>Quantum Spatial</cntorg>
				</cntorgp>
				<cntaddr>
					<addrtype>mailing and physical</addrtype>
					<address>517 SW 2nd Street, Suite 400</address>
					<city>Corvallis</city>
					<state>OR</state>
					<postal>97333</postal>
					<country>USA</country>
				</cntaddr>
				<cntvoice>541-752-1204</cntvoice>
				<cntfax>541-752-3770</cntfax>
				<hours>Monday through Friday 8:30 AM to 5:00 PM (Pacific Standard Time)</hours>
				<cntinst> If unable to reach the contact by telephone, please send an email. </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>
			<metextns>
				<onlink>None</onlink>
				<metprof>None</metprof>
			</metextns>
	</metainfo>
</metadata>

