<?xml version="1.0" encoding="UTF-8"?>
<!--DOCTYPE metadata SYSTEM "csdgm2.dtd"-->
<metadata>
 <idinfo>
  <citation>
   <citeinfo>
    <origin>Aero-Graphics</origin>
    <pubdate>20200226</pubdate>
    <title>DCS Terrain Submission for Dawson County MT</title>
    <geoform>model</geoform>
   </citeinfo>
  </citation>
  <descript>
   <abstract>
   		LiDAR was collected at a 0.35 meter nominal post spacing for approximately 573 square miles of Dawson County, Montana. Data was acquired during leaf-off 
   		conditions while no snow was on the ground and rivers were at or below normal levels. The project area required a relative accuracy of less than 10 cm RMSEz within swath overlap
   		a 0.35 meter nominal post spacing and a required 10cm Non-vegetated Vertical Accuracy.
   </abstract>
   <purpose>
   	Lifts are planned to meet project specifications and are flown under cloud-free conditions in 
   	order to collect LIDAR points at an average of 0.35 meter point spacing. This allows the user to create 
   	bare earth models, 1ft contours, and fully Classified LiDAR LAS files.
   </purpose>
  </descript>
  <timeperd>
   <timeinfo>
    <rngdates>
     <begdate>20190814</begdate>
     <enddate>20190818</enddate>
    </rngdates>
   </timeinfo>
   <current>ground condition</current>
  </timeperd>
  <status>
   <progress>Complete</progress>
   <update>Unknown</update>
  </status>
  <spdom>
    <bounding>
      <westbc>-105.124847</westbc>
      <eastbc>-104.320903</eastbc>
      <northbc>47.441002</northbc>
      <southbc>46.797146</southbc>
    </bounding>
  </spdom>
  <keywords>
   <theme>
    <themekt>none</themekt>
    <themekey>model</themekey>
    <themekey>LiDAR</themekey>
    <themekey>remote sensing</themekey>
   </theme>
   <place>
    <placekt>None</placekt>
    <placekey>REGION VIII</placekey>
				<placekey>STATE MT</placekey>
				<placekey>Dawson County</placekey>
				<placekey>Montana</placekey>
   </place>
  </keywords>
  <accconst>None</accconst>
  <useconst>
  		None. However, users should be aware that temporal changes may have occurred since 
  		this data set was collected and that some parts of this data may no longer represent actual 
  		surface conditions. Users should not use this data for critical applications without a full 
  		awareness of its limitations. Acknowledgement of the Federal Emergency Management Agency (FEMA)
  		would be appreciated for products derived from these data.
  </useconst>
  <datacred> Aero-Graphics acquired the LiDAR, performed all initial and post-processing of the data 
  	and created all deliverable products.</datacred>
  <native>
  		MicroStation Connect Version 10.09.01.01; TerraScan Version 018_099; TerraMatch Version 018_099; LP360 Version 2018.2.59.7; GeoCue Version 2017.1.14.1 
  		ESRI ArcGIS 10.6; Windows 10 Operating System
  </native>		
 </idinfo>
 <dataqual>
  <attracc>
    <attraccr>
	The project area requires LiDAR to be collected on 0.35 meter NPS and vertical accuracy 
    of 10 centimeters RMSE or better to support 1ft contour generation.
    </attraccr> 
  </attracc>
  <logic>
  Raster DEMs were tested by Aero-Graphics for vertical accuracy. 
  All data is seamless from one tile to the next, no gaps or no data areas.
  </logic>
  <complete>Datasets contain complete coverage of tiles.</complete>
  <posacc>
   <vertacc>
    <vertaccr>Raster DEMs were tested by Aero-Graphics for both vertical and horizontal 
    accuracy. All data is seamless from one tile to the next, no gaps or no data areas. 
    The vertical unit of the data file is in decimal meters with 2-decimal point precision.</vertaccr>
	<qvertpa>
		<vertaccv>0.380</vertaccv>
		<vertacce> Final 1.96 RMSE in feet of non vegetated ground check points witheld from the calibration and post processing of the LiDAR point cloud within the Dawson County project site.</vertacce>
	</qvertpa>
   </vertacc>
  </posacc>
  <lineage>
   <srcinfo>
    <srccite>
     <citeinfo>
      <origin>Aero-Graphics</origin>
      <pubdate>2020</pubdate>
      <title>LiDAR</title>
      <geoform>digital data</geoform>
     </citeinfo>
    </srccite>
    <typesrc>hard drive</typesrc>
    <srctime>
     <timeinfo>
      <rngdates>
        <begdate>20190814</begdate>
        <enddate>20190818</enddate>
      </rngdates>
     </timeinfo>
     <srccurr>ground condition</srccurr>
    </srctime>
    <srccitea>LiDAR</srccitea>
    <srccontr>LiDAR points were used to produce the deliverables.</srccontr>
   </srcinfo>
   <procstep>
    <procdesc>1. Flight lines and data were reviewed to ensure complete coverage of the study area and positional accuracy of the laser points. 
	2. Laser point return coordinates were computed using Waypoint Inertial Explorer software based on independent data from the LiDAR system, IMU, and aircraft. 
	3. The raw LiDAR file was assembled into flight lines per return with each point having an associated x, y, and z coordinate. 
	4. Visual inspection of swath to swath laser point consistencies within the study area were used to perform manual refinements of system alignment. 
	5. Custom algorithms were designed to evaluate points between adjacent flight lines. Automated system alignment was computed based upon randomly selected swath to swath accuracy measurements that consider elevation, slope, and intensities. Specifically, refinement in the combination of system pitch, roll and yaw offset parameters optimize internal consistency. 
	6. Noise (e.g., pits and birds) was filtered using postprocessing software, based on known elevation ranges and included the removal of any cycle slips. 
	7. Using TerraScan and Microstation, ground classifications utilized custom settings appropriate to the study area. 
	8. The corrected and filtered return points were compared to the RTK ground survey points collected to verify the vertical accuracy.
					</procdesc>
    <srcused>LiDAR</srcused>
    <procdate>2020</procdate>
    <srcprod>LiDAR post-processed data</srcprod>
   </procstep>
  </lineage>
 </dataqual>
 	<spref>
		<horizsys>
			<planar>
				<gridsys>
					<gridsysn>State Plane Coordinate System 1983</gridsysn>
					<spcs>
						<spcszone>2500</spcszone>
						<lambertc>
							<stdparll>45.0</stdparll>
							<longcm>-109.5</longcm>
							<latprjo>44.25</latprjo>
							<feast>1968503.937007874</feast>
							<fnorth>0.0</fnorth>
						</lambertc>
					</spcs>
				</gridsys>
				<planci>
					<plance>row and column</plance>
					<coordrep>
						<absres>0.01</absres>
						<ordres>0.01</ordres>
					</coordrep>
					<plandu>Intl. feet</plandu>
				</planci>
			</planar>
			<geodetic>
				<horizdn>North American Datum of 1983 (2011)</horizdn>
				<ellips>Geodetic Reference System 80</ellips>
				<semiaxis>6378137.000000</semiaxis>
				<denflat>298.257222101</denflat>
			</geodetic>
		</horizsys>
		<vertdef>
			<altsys>
				<altdatum>North American Vertical Datum of 1988</altdatum>
				<altres>0.01</altres>
				<altunits>US feet</altunits>
				<altenc>Attribute values</altenc>
			</altsys>
		</vertdef>
	</spref>
 <eainfo>
  <overview>
   <eaover>GeoTIFF files with a 3 foot pixel. No Data values outside of the project area are represented with -9999.</eaover>
   <eadetcit>All deliverables meet specifications in contract.</eadetcit>
  </overview>
 </eainfo>
 <metainfo>
  <metd>20200226</metd>
  <metc>
   <cntinfo>
    <cntorgp>
     <cntorg>Aero-Graphics</cntorg>
    </cntorgp>
    <cntaddr>
		 <addrtype>mailing and physical</addrtype>
     			<address>40 W Oakland Ave</address>
			<city>Salt Lake City</city>
			<state>UT</state>
			<postal>84105</postal>
			<country>USA</country>
    </cntaddr>
		<cntvoice>801-487-3273</cntvoice>
		<cntfax>801-487-3313</cntfax>
   </cntinfo>
  </metc>
  <metstdn>FGDC Content Standard for Digital Geospatial Metadata</metstdn>
  <metstdv>FGDC-STD-001-1998</metstdv>
 </metainfo>
</metadata>

