<?xml version="1.0" encoding="UTF-8"?>
<metadata>
	<idinfo>
		<citation>
			<citeinfo>
				<origin>Continental Mapping Consultants</origin>
				<pubdate>20170124</pubdate>
				<title>USACE Bare Earth LiDAR for Fort Indiantown Gap near Lebanon, Pennsylvania</title>
			</citeinfo>
		</citation>
		<descript>
			<abstract>The National Guard Bureau (NGB) required high accruacy classified LiDAR data in combination with raster digital elevation models and hydrographic breaklines. For this effort, Continental Mapping Consultants (Continental) will collect and process high accuracy classified LiDAR data in .LAS format as well as a combination of raster digital elevation models.</abstract>
			<purpose>The National Guard Bureau (NGB) requires the collection and processing of high accuracy classified LiDAR data in .LAS format as well as a combination of raster digital elevation models and additional hydrographic breaklines. The data is to be acquired during the Spring 2017 timeframe, during leaf-off conditions. The acquired LiDAR data will be used for various planning, design, research and mapping purposes. The NGB requires this data collection for Fort Indiantown Gap near Lebanon, Pennsylvania.</purpose>
			<langdata>en</langdata></descript>
		<timeperd>
			<timeinfo>
				<sngdate>
					<caldate>20170329</caldate>
				</sngdate>
			</timeinfo>
			<current>ground condition</current>
		</timeperd>
		<status>
			<progress>Complete</progress>
			<update>Unknown</update>
		</status>
		<spdom>
			<bounding>
				<westbc>-76.755715</westbc>
				<eastbc>-76512210</eastbc>
				<northbc>40.493479</northbc>
				<southbc>40.384648</southbc>
			</bounding>
		</spdom>
		<keywords>
			<theme>
				<themekt>None</themekt>
				<themekey>Elevation Data</themekey>
				<themekey>LiDAR</themekey>
				<themekey>DTM</themekey>
				<themekey>Land Surface</themekey>
				<themekey>Bare Earth LAS</themekey>
				<themekey>DEM</themekey>
				<themekey>LAS</themekey>
				<themekey>Ground Control</themekey>
				<themekey>Point Cloud</themekey>
				<themekey>GeoTIFF</themekey><themekey>ERDAS Imagine</themekey><themekey>Tile Index</themekey><themekey>US Army Corps of Engineers</themekey><themekey>USACE</themekey><themekey>IMG</themekey></theme>
			<place>
				<placekt>None</placekt>
				<placekey>Fort Indiantown Gap</placekey><placekey>Lebanon</placekey><placekey>Lebanon County</placekey><placekey>Pennsylvania</placekey><placekey>USA</placekey><placekey>PA</placekey></place>
		</keywords>
		<accconst>None</accconst>
		<useconst>None</useconst>
		<ptcontac>
			<cntinfo>
				<cntorgp>
					<cntorg>Continental Mapping Consultants</cntorg>
				</cntorgp>
				<cntaddr>
					<addrtype>mailing and physical address</addrtype>
					<address>121 S Bristol Street</address>
					<city>Sun Prairie</city>
					<state>WI</state>
					<postal>53590</postal>
					<country>USA</country>
				</cntaddr>
				<cntvoice>888-815-3327</cntvoice>
			</cntinfo>
		</ptcontac>
		<datacred>Data credit goes to Continental Mapping Consultants who was contracted by US Army Corps of Engineers St. Loius.</datacred>
		<secinfo>
			<secsys>N/A</secsys>
			<secclass>Unclassified</secclass>
			<sechandl>N/A</sechandl>
		</secinfo>
		<native>Environment as of Metadata Creation: Microsoft Windows 7 Professional; Esri ArcGIS 10.2.2; Microstation V8i Select Series 3 (version 8.11.09.459); TerraScan (version 016.001)</native>
		<natvform>LAS</natvform></idinfo>
	<dataqual>
		<attracc>
			<attraccr>N/A</attraccr>
		</attracc>
		<logic>Survey data have been confirmed to be in proper units, coordinate systems and format.  The terrain data have been confirmed as complete LAS format data files.</logic>
		<complete>Survey data have been checked for completeness, points have been collected in correct vegetation locations, and distributed throughout the AOI.  The terrain data have been checked for completeness against AOI polygons.</complete>
		<posacc>
			<horizpa>
				<horizpar>N/A</horizpar>
			</horizpa>
			<vertacc>
				<vertaccr>USACE EM 1110-1-1000, 30, APR 2015 Requirements
Vertical Accuracy Class: 10 cm
RMSE Non-Vegetated: 10 cm
NVA at 95% Confidence Level: 19.6 cm
VVA at 95th Percentile: 30 cm

Non-Vegetated Vertical Accuracy
Vertical RMSE: 0.028

Vegetated Vertical Accuracy
Vertical RMSE: 0.041</vertaccr>
				<qvertpa>
					<vertaccv>0.035 centimeters</vertaccv>
					<vertacce>Non-Vegetated Vertical Accuracy (NVA) equal to the 95th Percentile confidence level calculated in open terrain.  Reported in centimeters.</vertacce>
				</qvertpa>
				<qvertpa>
					<vertaccv>0.035 centimeters</vertaccv>
					<vertacce>It passes the Vegetated Vertical Accuracy (VVA) requirements at 95th percentile.  Reported in centimeters.</vertacce>
				</qvertpa>
			</vertacc>
		</posacc>
		<lineage>
			<procstep>
				<procdesc>Continental Mapping Consultants was tasked with performing a LiDAR ground control survey in support of LiDAR collection of Fort Indiantown Gap (FIG) in central Pennsylvania. The Global Positioning System (GPS) was used to establish the ground control network, and a total station was also used to survey the woods VVA checkpoints. The map in figure 1 shows the location of the ten ground control points (GCP, shown as red dots) and the twenty-five checkpoints (CP, shown as green dots). Also shown are two control stations which provided a tie to the NSRS (red cross inside white square).

The National Spatial Reference System (NSRS) was used to provide control for the network. An existing ground station of the National Spatial Reference System (NSRS) was occupied during the survey to provide a direct tie to the NSRS. In addition, a private CORS which is rigorously tied to the NSRS was also included.  The horizontal datum was NAD83 (2011) epoch 2010.0, and the vertical
datum was NAVD88, realized through the use of the GEOID12B model.

The field survey was done by using the KeyNetVirtual Reference Station Network. In the VRS method, a GPS receiver (a R10 dual frequency receivers was used) equipped with a data connection is used as a rover to occupy each survey point. Data is received via the cellular network for a “virtual” reference station nearby. The data is processed in real time to compute a position and elevation for the unknown station. The rover is positioned from the nearest physical CORS point and the vector data is stored in a data collector as a vector from this position, along with statistical data for the solution.</procdesc>
				<procdate>2017</procdate>
			</procstep>
			<procstep>
				<procdesc>The aerial LiDAR acquisition was completed by Keystone Aerial Surveys.  The sensor used was an Optech Galaxy.  There were 25 project flight lines, and 1 cross flights collected.  The LiDAR acquisition was completed in one (1) aircraft lift occurring on March 29, 2017.  

Altitude: 1800 meters
Aircraft Ground Speed: 113 knots average
Pulse Rate: 300 kHz
Scan Rate: 72 Hz
Full Field of View: 35 degrees
Full Swath Width: 680 meters
Swath Overlap: 30%
Average Point Density: 4.179 pts/m^2</procdesc>
				<procdate>2017</procdate>
			</procstep>
			<procstep>
				<procdesc>The Continental team utilized Optech's LMS to initially process the data and convert into LAS format.  TerraMatch was then used to refine the calibration of the LiDAR dataset.</procdesc>
				<procdate>2017</procdate>
			</procstep>
			<procstep>
				<procdesc>The trajectory files and point cloud swaths are imported into GeoCue to perform project setup.  This project set up phase sets the project parameters, tiling scheme, and is the platform for initial macro runs. After import, checkpoints are run against the point cloud to verify the accuracy of the data prior to classification. The detailed description of this process is below in 4.0 Accuracy Assessment. After verifying the accuracy, the processing continues. Multiple macros are run through TerraScan to flag overlap, and to classify the ground. Due to differing terrain, this step may take multiple iterations. Once the analyst has verified the results with the ground macro, the ground classification QC begins. During the QC phase, analysts are reclassifying the point cloud in areas where the macro was not able to, or were misclassified.
Multiple macros are run on the dataset after the ground classification is complete including the building and water macros. The same rigorous quality steps are performed each classification.  The bare earth lidar points that were within 1 meter of the water were classified to class 10. After the analysts have completed the QC process in TerraScan, raster files were produced into 32-bit floating GeoTiffs and Erdas Imagine IMG files using Global Mapper. These files were created using only the ground and building classes.</procdesc>
				<procdate>2017</procdate>
			</procstep>
			<procstep>
				<procdesc>The calibrated and controlled lidar files were processed using automatic point classification routines in proprietary software. These routines operate against the entire collection (all swaths, all lifts), eliminating character differences between files.  The trajectory files and point cloud swaths were imported into GeoCue to perform project setup.  This project set up phase set the project parameters, tiling scheme, and was the platform for initial macro runs.  After import, checkpoints were run against the point cloud to verify the accuracy of the data prior to classification.  After verifying the NVA accuracy, the processing continued.  Multiple macros were run through TerraScan to flag overlap, ground, low points, etc.  Points below ground surface that were identified as low points were classified to class 7. A bare earth ground surface was derived from the unclassed points and put to class 2 using a suitable macro function for the project's terrain type. Points above the treeline that were not identified as a feature were classified to class 18. Ground points inside of water features were classifed to class 9 to represent water and ground points outside of hydro features but within 1 meter of hydro breaklines were classified to class 10. All remaining points were classified to class 1.  Final lidar LAS delivery classes for the fully classed LAS tiles consistent with ASPRS LAS classes to be compliant with USGS LiDAR Guidelines and Base Specifications v13 consist of: Class 1 - Unclassified; Class 2 - Ground; Class 7 – Low Noise; Class 8 – Model Key; Class 9 - Water; Class 10 - Ignored Ground (including 2-meter buffer around water breaklines); Class 12 - Overlap points exceeding scan angles of +/- 20 degrees; and Class 18 - High Noise.  Once the analyst was comfortable with the ground macro results, the ground classification QC began using TerraScan.  During the QC phase, analysts reclassified the point cloud in areas where the macro was not able to, or created misclassifications.  The same rigorous quality steps were performed on each classification.

Data were then distributed as virtual tiles to experienced lidar analysts for localized automatic classification, manual editing, and peer-based QC checks. Supervisory QC monitoring of work in progress and completed editing ensured consistency of classification character and adherence to project requirements across the entire project.

Upon completion of point classification, an automated process was executed to turn any points to class 1 in the Fully Classified LAS files and to delete any point for the Bare Earth and Key Point LAS Files that fell outside of the provided project buffered boundary.

Breaklines were digitized at water elevation for any bodies of water over the entire project area including streams greater than 25ft in nominal width, water bodies greater than 0.5 acres in area, and islands greater than 0.5 acre. A macro was then run to classify points that lay at nominal water elevation to class 9 that fell within bodies of water. Concurrently a 1-meter buffer zone around water polygons was derived from the ground class and put to class 10. Water bodies and streams with flow were hydro-enforced using the Ponds, Islands, and Double Line Drain shapefiles to demonstrate the removal of unnatural surface artifacts in both ponds and streams and to show downward flow for streams.

A DEM data set was generated for both the Bare Earth LAS set and Model Key Point LAS set as 32-bit Erdas Imagine .IMG files at a resolution of 1.0 m (meter) supported by the Hydro Breaklines.

1-foot contours were generated in LP360 using the hydro breaklines and Bare Earth data.  </procdesc>
				<procdate>2017</procdate>
			</procstep>
			<procstep><procdesc>Continental utilized various software packages and techniques to verify the accuracy of the data. Utilizing QCoherent’s LP360, Continental ran a survey to las check, followed by seamline analysis. The survey to las check calculates the deviation between the survey point elevation and the point cloud elevation and export a Non-Vegetated Vertical Accuracy (NVA) report. The second check, calculates the deviation between the seamlines of the point cloud swaths. The third check, the Vegetated Vertical Accuracy (VVA) testing occurred after the ground classification has been completed. The VVA testing utilized both the points that were labeled VVA and NVA if those points were either located in or under vegetation. Other software like Terra Solid and Global Mapper were utilized to verify the results of LP360.

Continental appreciates the time-critical nature of this product. The field survey and aerial survey teams were deployed at the first opportunity based on availability of acceptable weather conditions and base personnel (for coordination). The area of interest contains subareas of dense vegetation which present fewer bare ground returns, higher variability, and potentially less accuracy than typical vegetated areas.  Per the table below the survey accuracy results meet industry standards for both NVA and VVA based on the ground survey control points collected in December.

Once all of the deliverables have been produced and verified, the data was moved to the Quality office for final review. The Quality Office verifies that the correct procedures were followed, tests the data, and verifies that all of the deliverables in the SOW are finished.</procdesc><procdate>2017</procdate></procstep></lineage>
	</dataqual>
	<spdoinfo>
		<direct>Raster</direct>
		<rastinfo><rasttype>Pixel</rasttype><rastdtyp>pixel RGB</rastdtyp><rowcount>1000</rowcount><colcount>1000</colcount><vrtcount>1</vrtcount><rastorig>Upper Left</rastorig><rastband>1</rastband><rastxsz>0.500000</rastxsz><rastysz>0.500000</rastysz><rastbpp>32</rastbpp><rastifor>LAS</rastifor><rastityp>Leica ALS80-UP</rastityp><rastcmap>FALSE</rastcmap><rastcomp>Run-Length Encoding (ESRI)</rastcomp></rastinfo></spdoinfo>
	<spref>
		<horizsys>
			<planar>
				<gridsys>
					<gridsysn>Universal Transverse Mercator</gridsysn>
					<utm>
						<utmzone>18</utmzone>
						<transmer>
							<sfctrmer>0.9996</sfctrmer>
							<longcm>-75.000000</longcm>
							<latprjo>0.0</latprjo>
							<feast>500000.000000</feast>
							<fnorth>0.0</fnorth>
						</transmer>
					</utm>
				</gridsys>
				<planci>
					<plance>coordinate pair</plance>
					<coordrep>
						<absres>0.500000</absres>
						<ordres>0.500000</ordres>
					</coordrep>
					<plandu>meters</plandu>
				</planci>
			</planar>
			<geodetic>
				<horizdn>D_NAD_1983_2011</horizdn>
				<ellips>WGS_1984</ellips>
				<semiaxis>6378137.00</semiaxis>
				<denflat>298.257224</denflat>
			</geodetic>
			<cordsysn><geogcsn>GCS_NAD_1983_2011</geogcsn><projcsn>NAD_1983_2011_UTM_Zone_18N</projcsn></cordsysn></horizsys>
		<vertdef>
			<altsys>
				<altdatum>North American Vertical Datum of 1988</altdatum>
				<altres>0.01</altres>
				<altunits>meters</altunits>
				<altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
			</altsys>
		</vertdef>
	</spref>
	<eainfo>
		<detailed>
			<enttyp>
				<enttypl>GroundControl</enttypl>
				<enttypd>Ground Control Survey for LiDAR collection</enttypd>
				<enttypds>USACE Guidelines and Specifications, USACE EM 1110-1-1000 for Photogrammetric and LiDAR mapping dated 30 April 2015</enttypds>
			</enttyp>
		</detailed>
		<detailed>
			<enttyp>
				<enttypl>NVA_VVA</enttypl>
				<enttypd>Survey for Horizontal and Vertical LiDAR QC</enttypd>
				<enttypds>USACE Guidelines and Specifications, USACE EM 1110-1-1000 for Photogrammetric and LiDAR mapping dated 30 April 2015</enttypds>
			</enttyp>
		</detailed>
		<detailed>
			<enttyp>
				<enttypl>Collection_Area</enttypl>
				<enttypd>Area Spatial File</enttypd>
				<enttypds>USACE Guidelines and Specifications, USACE EM 1110-1-1000 for Photogrammetric and LiDAR mapping dated 30 April 2015</enttypds>
			</enttyp>
		</detailed>
		<detailed>
			<enttyp>
				<enttypl>All_Returns</enttypl>
				<enttypd>LAS 1.3 files</enttypd>
				<enttypds>USACE Guidelines and Specifications, USACE EM 1110-1-1000 for Photogrammetric and LiDAR mapping dated 30 April 2015</enttypds>
			</enttyp>
		</detailed>
		<detailed>
			<enttyp>
				<enttypl>PreFlightReport</enttypl>
				<enttypd>Digital Document</enttypd>
				<enttypds>USACE Guidelines and Specifications, USACE EM 1110-1-1000 for Photogrammetric and LiDAR mapping dated 30 April 2015</enttypds>
			</enttyp>
		</detailed>
		<detailed>
			<enttyp>
				<enttypl>PostFlightReport</enttypl>
				<enttypd>Digital Document</enttypd>
				<enttypds>USACE Guidelines and Specifications, USACE EM 1110-1-1000 for Photogrammetric and LiDAR mapping dated 30 April 2015</enttypds>
			</enttyp>
		</detailed>
		<detailed>
			<enttyp>
				<enttypl>Tile_Index</enttypl>
				<enttypd>Area Spatial File</enttypd>
				<enttypds>USACE Guidelines and Specifications, USACE EM 1110-1-1000 for Photogrammetric and LiDAR mapping dated 30 April 2015</enttypds>
			</enttyp>
		</detailed>
		<detailed>
			<enttyp>
				<enttypl>Testing Results NVA</enttypl>
				<enttypd>Digital Document</enttypd>
				<enttypds>USACE Guidelines and Specifications, USACE EM 1110-1-1000 for Photogrammetric and LiDAR mapping dated 30 April 2015</enttypds>
			</enttyp>
		</detailed>
		<detailed>
			<enttyp>
				<enttypl>Testing Results VVA</enttypl>
				<enttypd>Digital Document</enttypd>
				<enttypds>USACE Guidelines and Specifications, USACE EM 1110-1-1000 for Photogrammetric and LiDAR mapping dated 30 April 2015</enttypds>
			</enttyp>
		</detailed>
	</eainfo>
	<distinfo>
		<distrib>
			<cntinfo>
				<cntorgp>
					<cntorg>
Leave blank unless an organization outside of USGS has
distribution rights to the data.
</cntorg>
					<cntper>
Leave blank unless an organization outside of USGS has
distribution rights to the data.
</cntper>
				</cntorgp>
				<cntaddr>
					<addrtype>
Leave blank unless an organization outside of USGS has
distribution rights to the data.
</addrtype>
					<address>
Leave blank unless an organization outside of USGS has
distribution rights to the data.
</address>
					<city>
Leave blank unless an organization outside of USGS has
distribution rights to the data.
</city>
					<state>
Leave blank unless an organization outside of USGS has
distribution rights to the data.
</state>
					<postal>
Leave blank unless an organization outside of USGS has
distribution rights to the data.
</postal>
					<country>
Leave blank unless an organization outside of USGS has
distribution rights to the data.
</country>
				</cntaddr>
				<cntvoice>
Leave blank unless an organization outside of USGS has
distribution rights to the data.
</cntvoice>
				<cntemail>
Leave blank unless an organization outside of USGS has
distribution rights to the data.
</cntemail>
			</cntinfo>
		</distrib>
		<resdesc>N/A</resdesc>
		<distliab>N/A</distliab>
		<stdorder>
			<nondig>N/A</nondig>
			<fees>None. No fees are applicable for obtaining the data set.</fees>
		</stdorder>
		<custom>N/A</custom>
		<techpreq>N/A</techpreq>
	</distinfo>
	<metainfo>
		<metd>20170625</metd>
		<metc>
			<cntinfo>
				<cntorgp>
					<cntorg>Continental Mapping Consultants</cntorg>
				</cntorgp>
				<cntaddr>
					<addrtype>mailing and physical address</addrtype>
					<address>121 S Bristol Street</address>
					<city>Sun Prairie</city>
					<state>WI</state>
					<postal>53590</postal>
					<country>USA</country>
				</cntaddr>
				<cntvoice>888-815-3327</cntvoice>
			</cntinfo>
		</metc>
		<metstdn>FGDC Content Standards for Digital Geospatial Metadata</metstdn>
		<metstdv>FGDC-STD-001-1998</metstdv>
		<mettc>local time</mettc>
		<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>
		<langmeta>en</langmeta></metainfo>
	<Esri><CreaDate>20170625</CreaDate><CreaTime>13245300</CreaTime><SyncOnce>TRUE</SyncOnce><DataProperties><itemProps><itemLocation><linkage Sync="TRUE">file://\\cmcfs02\w\Client\USACE St. Louis\J16092_Camp Dodge and Fort Indian Town Gap Lidar\Deliver\Fort Indiantown Gap\a_LAS_V1.3</linkage><protocol Sync="TRUE">Local Area Network</protocol></itemLocation></itemProps><copyHistory><copy source="W:\Client\USACE St. Louis\J16092_Camp Dodge and Fort Indian Town Gap Lidar\Deliver\Camp Dodge\a_LAS_V1.3" dest="\\cmcfs02\w\Client\USACE St. Louis\J16092_Camp Dodge and Fort Indian Town Gap Lidar\Deliver\Fort Indiantown Gap\a_LAS_V1.3\USACE_Fort_Indiantown_Gap_ClassifiedLAS" date="20170625" time="13245300"></copy></copyHistory></DataProperties></Esri></metadata>
