<?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>PolygonZ</geoform>
			</citeinfo>
		</citation>
		<descript>
			<abstract>Product: Washington Olympic Peninsula Area 2 Lidar Water's Edge Breaklines. The water's edge breaklines were used to hydroflatten DEMs created for the project.
			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. 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>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.
				Breakline File Type = SHP
				Breakline Elevation Units = US Survey Feet
				Downhill Treatment Applied = Proprietary
				Type of Hydro Treatment Required = Hydro-flattened
			</supplinf>
		</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.165289</westbc>
				<eastbc>-123.173926</eastbc>
				<northbc>46.986834</northbc>
				<southbc>46.118543</southbc>
			</bounding>
			<lboundng>
				<leftbc>725542.297577</leftbc>
				<rightbc>962792.236134</rightbc>
				<topbc>614649.118260</topbc>
				<bottombc>307270.921994</bottombc>
			</lboundng>
		</spdom>
		<keywords>
			<theme>
				<themekt>none</themekt>
				<themekey>breakline</themekey>
				<themekey>remote sensing</themekey> 
				<themekey>Elevation data</themekey>
				<themekey>lidar</themekey>
				<themekey>Hydrology</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>
	</idinfo>
	<dataqual>
		<logic>
			Data covers the entire area specified for this project. Water's edge breaklines were collected in all inland ponds and lakes ~2 acres or greater. These features were flat and level water bodies at a single elevation for each vertex along the bank. The entire water surface edge is at or below the immediate surrounding terrain. Breaklines were collected for all streams and rivers ~100' nominal width or wider. These features are flat and level bank to bank, gradient will follow the surrounding terrain and the water surface will be at or below the surrounding terrain. Streams/river channels will break at culvert locations however not at elevated bridge locations.
		</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>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>
			<procstep>
				<procdesc>Hydro-flattening Breaklines and Hydro-flattened DEM creation: Water boundary polygons were developed using an algorithm which weights lidar-derived slopes, intensities, and return densities to detect the water's edge. The water's edge was then manually reviewed and edited as necessary. Elevations were assigned to the water’s edge through neighborhood statistics identifying the lowest lidar return from the water surface. Lakes were assigned a consistent elevation for an entire polygon while rivers were assigned consistent elevations on opposing banks and smoothed to ensure downstream flow through the entire river channel. These breaklines were incorporated into the hydro-flattened DEM by enforcing triangle edges (adjacent to the breakline) to the elevation values derived from the breakline. This implementation corrected interpolation along the hard edge. Breaklines were also used to classify all ground points within the identified water bodies to class 9 (water).</procdesc>
				<procdate>20190425</procdate>
			</procstep>
		</lineage>
	</dataqual>
	<spdoinfo>
		<direct>Vector</direct>
	</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>Order</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>