<?xml version="1.0" encoding="UTF-8"?>
<metadata>
	<idinfo>
		<citation>
			<citeinfo>
				<origin>NV5 Geospatial</origin>
				<pubdate>20221231</pubdate>
				<title>Task Name: Alaska Native Villages Lidar USGS Contract: Example, Task Order: Example </title>
				<geoform>Lidar Point Cloud</geoform>
			</citeinfo>
		</citation>
		<descript>
			<abstract>Product: Classified LAS 1.4 files, formatted to 1000 individual 1500m x 1500m tiles covering the Alaska Native Villages Lidar project area.
			Geographic Extent: This dataset and derived products encompass an area covering approximately 100,000 acres of Alaska. 
			Dataset Description: The Alaska Native Villages Lidar Lidar project called for the planning, acquisition, and processing of lidar data collected to QL2. Project specifications are based on the U.S. Geological Survey National Geospatial Program LIDAR Base Specification, Version 2.1. The data was developed based on the NAD83 2011 horizontal datum and the NAVD88 Geoid 12B vertical datum.  Data was projected in UTM Zone 3 N, Meters. Lidar data was delivered as calibrated and classified LAS 1.4 files. Non-Vegetated Vertical Accuracy (NVA) was assessed using 17 check points located on bare earth in clear, unobstructed areas. Vegetated Vertical Accuracy (VVA) was assessed using 19 check points in Tall Grass and Shrub landcover types. Single swath nominal pulse spacing (NPS) was designed to be 0.707 at nadir. Aggregate Nominal Pulse Spacing (ANPS) was calculated to be 0.457 using all valid first return points. Derived products include: Intensity Imagery, Hydro-flattened Bare Earth Digital Elevation Models (DEMs), Highest Hit Digital Surface Models (DSMs), and 3D waters edge breaklines. 
			Ground Condition: Ground condition was free of snow and acquisition occured 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 Alaska Native Villages Lidar contract. The lidar point cloud data were used to create classified lidar LAS files, intensity images, hydro-flattened DEMs, highest hit DSMs, and 3D breaklines of rivers and lakes within the study area.</purpose>
			<supplinf>USGS Contract No. Example
			CONTRACTOR: NV5 Geospatial 
			Ground Control Points were acquired and calibrated by DOWL 
			All lidar data acquisition, calibration, and follow-on processing were completed by NV5 Geospatial
			</supplinf>
			<lidar>
				<ldrinfo>
					<ldrspec>U.S. Geological Survey National Geospatial Program LIDAR Base Specification, Version 2.1</ldrspec>
					<ldrsens>Riegl 1560ii-S</ldrsens>
					<ldrmaxnr>15</ldrmaxnr>
					<ldrnps>0.707</ldrnps>
					<ldrdens>2</ldrdens>
					<ldranps>0.457</ldranps>
					<ldradens>4.78</ldradens>
					<ldrfltht>2500</ldrfltht>
					<ldrfltsp>145</ldrfltsp>
					<ldrscana>58.5</ldrscana>
					<ldrscanr>uniform point spacing</ldrscanr>
					<ldrpulsr>757</ldrpulsr>
					<ldrpulsd>3</ldrpulsd>
					<ldrpulsw>0.57</ldrpulsw>
					<ldrwavel>1064</ldrwavel>
					<ldrmpia>1</ldrmpia>
					<ldrbmdiv>0.23</ldrbmdiv>
					<ldrswatw>2800</ldrswatw>
					<ldrswato>20</ldrswato>
					<ldrgeoid>Geoid 12B</ldrgeoid>
				</ldrinfo>
				<ldraccur>
					<ldrchacc>0.235 m</ldrchacc>
					<rawnva>0.093 m</rawnva>
					<rawnvan>17</rawnvan>
				</ldraccur>
				<lasinfo>
					<lasver>1.4</lasver>
					<lasprf>6</lasprf>
					<laswheld>Withheld (ignore) points are 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>Water</clasitem>
					</lasclass>
					<lasclass>
						<clascode>17</clascode>
						<clasitem>Bridge Decks</clasitem>
					</lasclass>
					<lasclass>
						<clascode>18</clascode>
						<clasitem>High Noise</clasitem>
					</lasclass>
					<lasclass>
						<clascode>20</clascode>
						<clasitem>Ignored Ground Near Breaklines</clasitem>
					</lasclass>
				</lasinfo>
			</lidar>
		</descript>
		<timeperd>
			<timeinfo>
				<sngdate>
					<caldate></caldate> 
				</sngdate>
				<rngdates>
					<begdate>20220811</begdate>
					<enddate>20221014</enddate>
				</rngdates>
			</timeinfo>
			<current>ground condition</current>
		</timeperd>
		<status>
			<progress>Complete</progress>
			<update>None Planned</update>
		</status>
		<spdom>
			<bounding>
				<westbc>1</westbc>
				<eastbc>1</eastbc>
				<northbc>1</northbc>
				<southbc>1</southbc>
			</bounding>
			<lboundng>
				<leftbc>1</leftbc>
				<rightbc>1</rightbc>
				<topbc>1</topbc>
				<bottombc>1</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>Alaska</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>LiDAR Mapping Suite 2.4, Applanix PosPac 7.1, Microstation CONNECT version, TerraScan Version 23, TerraModeler Version 21, TerraMatch Version 22, ESRI ArcGIS 10.3, Windows 10 Operating</native>
	</idinfo>
	<dataqual>
		<logic>Classified LAS files were tested by NV5 Geospatial for vertical accuracy. All data is seamless from one tile to the next, no gaps or no data areas.</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>
			<horizpa>
				<horizpar>This data set was produced to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 0.235 (m) RMSEx / RMSEy Horizontal Accuracy Class which equates to the Positional Horizontal Accuracy = +/- 0.407 m at a 95% confidence level.</horizpar>
				<qhorizpa>
					<horizpav>0.407</horizpav>
					<horizpae>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 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 flying altitude of 2500 meters, an IMU error of 0.003 decimal degrees, and a GNSS positional error of 0.023 meters, this project was compiled to meet 0 meters horizontal accuracy at the 95% confidence level.</horizpae>
				</qhorizpa>
			</horizpa>
			<vertacc>
				<vertaccr>This data set was produced to meet ASPRS Positional Accuracy Standard for Digital Geospatial Data (2014) for a 10-cm RMSEz Vertical Accuracy Class. The NVA was tested with 17 independent check points located in open terrain and distributed throughout the project as feasible. 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 0.196 meters or better AccuracyZ at 95% confidence level.</vertaccr>
				<qvertpa>
					<vertaccv>0.093 m</vertaccv>
					<vertacce>The 17 independent NVA check points were surveyed using the closed level loop technique. Elevations interpolated from the unclassified lidar surface were compared to the elevation values of the surveyed NVA check points. The RMSE was computed to be 0.047 m meters resulting in an AccuracyZ at the 95% confidence level of 0.093 m meters. NVA AccuracyZ has been tested and meets the required 0.196 meter NVA at 95% confidence level using (RMSEz * 1.9600) for the unclassified lidar point cloud as defined by the National Standards for Spatial Data Accuracy (NSSDA) and herein reported using National Digital Elevation Program (NDEP)/ASPRS Guidelines.</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 12B 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>Alaska Native Villages Lidar Ground Control</srcused>
				<procdate>20221231</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, VVA, and density information for the project using ground control quality check points.</procdesc>
				<procdate>20221231</procdate>
			</procstep>
		</lineage>
	</dataqual>
	<spdoinfo>
		<direct>Vector</direct>
		<ptvctinf>
			<sdtsterm>
				<sdtstype>Point</sdtstype>
				<ptvctcnt>100,000,000,000</ptvctcnt>
			</sdtsterm>
		</ptvctinf>
	</spdoinfo>
	<spref>
		<horizsys>
			<planar>
				<gridsys>
					<gridsysn>Universal Transverse Mercator</gridsysn>
					<utm>
						<utmzone>3</utmzone>
						<transmer>
							<sfctrmer></sfctrmer>
							<longcm></longcm>
							<latprjo></latprjo>
							<feast></feast>
							<fnorth></fnorth>
						</transmer>
					</utm>
				</gridsys>
				<planci>
					<plance>coordinate pair</plance>
					<coordrep>
						<absres>0.01</absres>
						<ordres>0.01</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.257223563</denflat>
			</geodetic>
		</horizsys>
		<vertdef>
			<altsys>
				<altdatum>North American Vertical Datum of 1988 Geoid 12B</altdatum>
				<altres>0.01</altres>
				<altunits>Meters</altunits>
				<altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
			</altsys>
		</vertdef>
	</spref>
	<metainfo>
		<metd>20221231</metd>
		<metrd>20221231</metrd>
		<metc>
			<cntinfo>
				<cntorgp>
					<cntorg>NV5 Geospatial</cntorg>
				</cntorgp>
				<cntaddr>
					<addrtype>mailing and physical</addrtype>
					<address>2014 Merrill Field Drive</address>
					<city>Anchorage</city>
					<state>AK</state>
					<postal>99501</postal>
					<country>USA</country>
				</cntaddr>
				<cntvoice>907-272-4495</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>