<?xml version="1.0" encoding="UTF-8"?>
<metadata>
	<idinfo>
		<citation>
			<citeinfo>
				<origin>NV5 Geospatial</origin>
				<pubdate>20230413</pubdate>
				<title>Task Name: CA North Sierra B22 Contract: 140G0221D0012, Task Order: 140G0222F0176 </title>
				<geoform>Raster Digital Data</geoform>
			</citeinfo>
		</citation>
		<descript>
			<abstract>Product: These are Highest Hit Digital Surface Model (DSM) data covering the CA North Sierra 2 2022 project area.
				Geographic Extent: This dataset and derived products encompass an area covering approximately 1,079,690 acres of Sierra Nevada Northern region.
				Dataset Description: Lidar flight line swaths were processed to create 4,425 classified LAS 1.4 files delineated in 1,000m x 1,000m tiles. Each LAS file contains lidar point information, which has been calibrated, controlled, and classified. All valid/non noise classes were were used to create 4,425 0.5 meter DSMs delineated in 1,000m x 1,000m tiles. Additional products include classified LAS files, intensity images, Hydroflattened Bare Earth Digital Elevation Models (DEMs), and 3D waters edge breaklines.
				Ground Conditions: Acquisition occurred free of smoke, fog and cloud cover.</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 3D Elevation Program and the CA North Sierra 2 2022 contract. The 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 and lakes within the study area.</purpose>
			<supplinf>USGS Contract No. 140G0221D0012
				Raster File Type = TIFF
				Bit Depth/Pixel Type = 32-bit float
				Raster Cell Size = 0.5 meter
				Interpolation or Resampling Technique = Highest Hit Method
			</supplinf>
		</descript>
		<timeperd>
			<timeinfo>
				<rngdates>
					<begdate>20211116</begdate>
					<enddate>20211201</enddate>
				</rngdates>
			</timeinfo>
			<current>ground condition</current>
		</timeperd>
		<status>
			<progress>In work</progress>
			<update>As needed</update>
		</status>
		<spdom>
			<bounding>
				<westbc>-121.437338</westbc>
				<eastbc>-120.380923</eastbc>
				<northbc>39.270645</northbc>
				<southbc>38.486708</southbc>
			</bounding>
			<lboundng>
				<leftbc>636255.333800</leftbc>
				<rightbc>726000.000000</rightbc>
				<topbc>4263000.000000</topbc>
				<bottombc>4348000.000000</bottombc>
			</lboundng>
		</spdom>
		<keywords>
			<theme>
				<themekt>none</themekt>
				<themekey>model</themekey>
				<themekey>Raster</themekey>
				<themekey>DSM</themekey>
				<themekey>High Hit</themekey>
				<themekey>remote sensing</themekey>
				<themekey>Elevation data</themekey>
				<themekey>Lidar</themekey>
			</theme>
			<place>
				<placekt>none</placekt>
				<placekey>California</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>DEM files were tested by NV5 for vertical accuracy. All data is seamless from one tile to the next, no gaps or no data areas.</logic>
		<complete>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>
		<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 18 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>CA North Sierra 2 2022 Ground Control</srcused>
				<procdate>20230413</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 final NVA and VVA values for the project using ground control quality check points. Final density information will also be calculated.</procdesc>
				<procdate>20230413</procdate>
			</procstep>
			<procstep>
				<procdesc>High Hit DSM creation: High Hit DSMs were created using the highest hit method from all valid return. In order to provide adequate coverage within this model for areas lacking valid point cloud returns, this highest hit model has been mosaicked with the hydroflattened bare earth model using the maximum mosaic operator. </procdesc>
				<procdate>20230413</procdate>
			</procstep>
		</lineage>
	</dataqual>
	<spdoinfo>
		<direct>Raster</direct>
		<rastinfo>
			<rasttype>Pixel</rasttype>
			<rowcount>2,000</rowcount>
			<colcount>2,000</colcount>
		</rastinfo>
	</spdoinfo>
	<spref>
		<horizsys>
			<planar>
				<gridsys>
					<gridsysn>Universal Transverse Mercator</gridsysn>
					<utm>
						<utmzone>10</utmzone>
						<transmer>
							<sfctrmer>0.9996</sfctrmer>
							<longcm>-123.0</longcm>
							<latprjo>0.0</latprjo>
							<feast>500000.0</feast>
							<fnorth>0.0</fnorth>
						</transmer>
					</utm>
				</gridsys>
				<planci>
					<plance>row and column</plance>
					<coordrep>
						<absres>0.5</absres>
						<ordres>0.5</ordres>
					</coordrep>
					<plandu>Meters</plandu>
				</planci>
			</planar>
			<geodetic>
				<horizdn>North American Datum of 1983 2011</horizdn>
				<ellips>GRS_1980</ellips>
				<semiaxis>6378137.0</semiaxis>
				<denflat>298.257222101</denflat>
			</geodetic>
		</horizsys>
		<vertdef>
			<altsys>
				<altdatum>North American Vertical Datum of 1988 Geoid 18</altdatum>
				<altres>0.01</altres>
				<altunits>Meters</altunits>
				<altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
			</altsys>
		</vertdef>
	</spref>
	<metainfo>
		<metd>20230413</metd>
		<metrd>20230413</metrd>
		<metc>
			<cntinfo>
				<cntorgp>
					<cntorg>NV5 Geospatial</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>