<metadata>
  <idinfo>
    <citation>
      <citeinfo>
        <origin>Quantum Spatial, Inc.</origin>
        <pubdate>20210121</pubdate>
        <title>Pennsylvania North Central Lidar QL2; Classified Point Cloud</title>
        <geoform>LiDAR point cloud</geoform>
      </citeinfo>
    </citation>
    <descript>
      <abstract>
       Product: These lidar data are processed Classified LAS 1.4 files, formatted to 6,269 individual 5,000 ft x 5,000 ft tiles; used to create intensity images, 3D breaklines, and hydro-flattened DEMs as necessary.
       Geographic Extent: 35 counties in Pennsylvania, covering approximately 5922 total square miles. 
       Dataset Description: The Pennsylvania North Central Lidar QL2 project called for the planning, acquisition, processing, and derivative products of lidar data to be collected at a nominal pulse spacing (NPS) of 0.71 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base LiDAR Specification, Version 1.3. The data were developed based on a horizontal projection/datum of NAD 1983 StatePlane Pennsylvania South FIPS 3702 Feet, Foot US and vertical datum of NAVD88 GEOID12B, Foot US. LiDAR data were delivered as processed Classified LAS 1.4 files formatted to 6,269 individual 5,000 ft x 5,000 ft tiles; 1651 individual 10,000 ft x 10,000 ft tiles, as tiled intensity imagery, and as tiled bare earth DEMs.Continuous breaklines were produced in Esri file geodatabase format.
       Ground Conditions: LiDAR was collected in spring and fall 2019, while no snow was on the ground and rivers were at or below normal levels. In order to post process the LiDAR data to meet task order specifications and meet ASPRS vertical accuracy guidelines, Quantum Spatial, Inc. utilized a total of 326 ground control points that were used to calibrate the LiDAR to known ground locations established throughout the project area. An additional 546 independent accuracy checkpoints, 322 in Bare Earth and Urban landcovers (322 NVA points), 224 in Tall Weeds categories (224 VVA points), were used to assess the vertical accuracy of the data. These checkpoints were not used to calibrate or post process the data.</abstract>
      <purpose>To acquire detailed surface elevation data for use in conservation planning, design, research, floodplain mapping, dam safety assessments and elevation modeling, etc. Classified LAS files are used to show the manually reviewed bare earth surface. This allows the user to create intensity images, breaklines and raster DEMs. The purpose of these LiDAR data was to produce high accuracy 3D hydro-flattened digital elevation models (DEMs) with a 2.5 foot cell size. These raw LiDAR point cloud data were used to create classified LiDAR LAS files, intensity images, 3D breaklines, and hydro-flattened DEMs as necessary.</purpose>
      <supplinf>Contract No. G16PC00016, Task Order No. 140G0219F0103; CONTRACTOR: Quantum Spatial, Inc.</supplinf>
      <lidar>
        <ldrinfo>
          <ldrspec>USGS-NGP Base Specification v1.3</ldrspec>
          <ldrsens>Riegl VQ1560i</ldrsens>
          <ldrmaxnr>unlimited</ldrmaxnr>
          <ldrnps>0.71</ldrnps>
          <ldrdens>2.0</ldrdens>
          <ldranps>0.71</ldranps>
          <ldradens>1.98</ldradens>
          <ldrfltht>2000</ldrfltht>
          <ldrfltsp>160</ldrfltsp>
          <ldrscana>29</ldrscana>
          <ldrscanr>30</ldrscanr>
          <ldrpulsr>100</ldrpulsr>
          <ldrpulsd>3</ldrpulsd>
          <ldrpulsw>0.36</ldrpulsw>
          <ldrwavel>1064</ldrwavel>
          <ldrmpia>1</ldrmpia>
          <ldrbmdiv>0.18</ldrbmdiv>
          <ldrswatw>2217.0</ldrswatw>
          <ldrswato>30</ldrswato>
          <ldrgeoid>GEOID12B</ldrgeoid>
          <ldrcrs>NAD 1983 StatePlane Pennsylvania South FIPS 3702 Feet, Foot US</ldrcrs>
        </ldrinfo>
        <ldrinfo>
          <ldrspec>USGS-NGP Base Specification v1.3</ldrspec>
          <ldrsens>Leica ALS80</ldrsens>
          <ldrmaxnr>unlimited</ldrmaxnr>
          <ldrnps>0.71</ldrnps>
          <ldrdens>2.0</ldrdens>
          <ldranps>0.71</ldranps>
          <ldradens>1.98</ldradens>
          <ldrfltht>2200</ldrfltht>
          <ldrfltsp>150</ldrfltsp>
          <ldrscana>20</ldrscana>
          <ldrscanr>48</ldrscanr>
          <ldrpulsr>138</ldrpulsr>
          <ldrpulsd>2.5</ldrpulsd>
          <ldrpulsw>0.48</ldrpulsw>
          <ldrwavel>1064</ldrwavel>
          <ldrmpia>1</ldrmpia>
          <ldrbmdiv>0.22</ldrbmdiv>
          <ldrswatw>1601.0</ldrswatw>
          <ldrswato>30</ldrswato>
          <ldrgeoid>GEOID12B</ldrgeoid>
          <ldrcrs>NAD 1983 StatePlane Pennsylvania South FIPS 3702 Feet, Foot US</ldrcrs>
        </ldrinfo>
        <ldrinfo>
          <ldrspec>USGS-NGP Base Specification v1.3</ldrspec>
          <ldrsens>Optech Galaxy T1000</ldrsens>
          <ldrmaxnr>8</ldrmaxnr>
          <ldrnps>0.71</ldrnps>
          <ldrdens>2.0</ldrdens>
          <ldranps>0.71</ldranps>
          <ldradens>1.98</ldradens>
          <ldrfltht>1575</ldrfltht>
          <ldrfltsp>170</ldrfltsp>
          <ldrscana>20</ldrscana>
          <ldrscanr>64</ldrscanr>
          <ldrpulsr>250</ldrpulsr>
          <ldrpulsd>3</ldrpulsd>
          <ldrpulsw>0.39</ldrpulsw>
          <ldrwavel>1064</ldrwavel>
          <ldrmpia>1</ldrmpia>
          <ldrbmdiv>0.25</ldrbmdiv>
          <ldrswatw>1147.0</ldrswatw>
          <ldrswato>30</ldrswato>
          <ldrgeoid>GEOID12B</ldrgeoid>
          <ldrcrs>NAD 1983 StatePlane Pennsylvania South FIPS 3702 Feet, Foot US</ldrcrs>
        </ldrinfo>
        <ldraccur>
          <ldrchacc>0</ldrchacc>
          <rawnva>0.134</rawnva>
          <rawnvan>320</rawnvan>
          <clsnva>0.098</clsnva>
          <clsnvan>322</clsnvan>
          <clsvva>0.158</clsvva>
          <clsvvan>224</clsvvan>
        </ldraccur>
        <lasinfo>
          <lasver>1.4</lasver>
          <lasprf>6</lasprf>
          <laswheld>Withheld (ignore) points were 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</clasitem>
          </lasclass>
          <lasclass>
            <clascode>21</clascode>
            <clasitem>Snow (where identifiable)</clasitem>
          </lasclass>
          <lasclass>
            <clascode>22</clascode>
            <clasitem>Temporal Exclusion (if applicable)</clasitem>
          </lasclass>
        </lasinfo>
      </lidar>
    </descript>
    <timeperd>
      <timeinfo>
        <rngdates>
          <begdate>20190323</begdate>
          <enddate>20191123</enddate>
        </rngdates>
      </timeinfo>
      <current>Ground condition</current>
    </timeperd>
    <status>
      <progress>Complete</progress>
      <update>None planned</update>
    </status>
    <spdom>
      <bounding>
        <westbc>-78.8500205092</westbc>
        <eastbc>-75.0269484431</eastbc>
        <northbc>41.0352262157</northbc>
        <southbc>39.6727305013</southbc>
      </bounding>
      <lboundng>
        <leftbc>1665000.0</leftbc>
        <rightbc>2720000.0</rightbc>
        <topbc>620000.0</topbc>
        <bottombc>135000.0</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>Pennsylvania</placekey>
        <placekey>Allegany County</placekey>
        <placekey>Bedford County</placekey>
        <placekey>Berks County</placekey>
        <placekey>Blair County</placekey>
        <placekey>Bucks County</placekey>
        <placekey>Cambria County</placekey>
        <placekey>Carbon County</placekey>
        <placekey>Cecil County</placekey>
        <placekey>Centre County</placekey>
        <placekey>Chester County</placekey>
        <placekey>Clearfield County</placekey>
        <placekey>Dauphin County</placekey>
        <placekey>Franklin County</placekey>
        <placekey>Fulton County</placekey>
        <placekey>Harford County</placekey>
        <placekey>Hunterdon County</placekey>
        <placekey>Huntingdon County</placekey>
        <placekey>Indiana County</placekey>
        <placekey>Jefferson County</placekey>
        <placekey>Juniata County</placekey>
        <placekey>Lancaster County</placekey>
        <placekey>Lebanon County</placekey>
        <placekey>Lehigh County</placekey>
        <placekey>Luzerne County</placekey>
        <placekey>Mifflin County</placekey>
        <placekey>Monroe County</placekey>
        <placekey>Montgomery County</placekey>
        <placekey>Northampton County</placekey>
        <placekey>Schuylkill County</placekey>
        <placekey>Somerset County</placekey>
        <placekey>Union County</placekey>
        <placekey>Warren County</placekey>
        <placekey>Washington County</placekey>
        <placekey>York 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 their limitations. Acknowledgement of the organization providing these data to the public would be appreciated for products derived from these data.</useconst>
    <ptcontac>
      <cntinfo>
        <cntorgp>
          <cntorg>Quantum Spatial, Inc.</cntorg>
          <cntper>John DiGiovanni</cntper>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing and physical</addrtype>
          <address>523 Wellington Way</address>
          <city>Lexington</city>
          <state>KY</state>
          <postal>40503</postal>
          <country>USA</country>
        </cntaddr>
        <cntvoice>859-277-8700</cntvoice>
        <cntfax>859-277-8901</cntfax>
        <cntemail>jdigiovanni@quantumspatial.com</cntemail>
        <hours>Monday through Friday 8:00 AM to 5:00 PM (Eastern Time)</hours>
        <cntinst>If unable to reach the contact by telephone, please send an email. You should get a response within 24 hours.</cntinst>
      </cntinfo>
    </ptcontac>
    <native>MicroStation Connect; TerraScan Version 20.011; TerraModeler Version 20.004; GeoCue Version 2017.1.14.1; Esri ArcGIS 10.6; Global Mapper 19/20; Optech LMS 4.4, Leica Cloud Pro 1.2.4, RiProcess 1.8.5; Windows 10 Operating System
      \\point_cloud\tilecls\*.las
     </native>
  </idinfo>
  <dataqual>
    <logic>Data cover the entire area specified for this project.</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 the data pass Non-Vegetated Vertical Accuracy specifications.</complete>
    <posacc>
      <vertacc>
        <vertaccr>
          The specifications require that only nonvegetated vertical accuracy (NVA) be computed for raw LiDAR data swath files. The vertical accuracy was tested with 320 independent survey points located in open terrain. These check points were not used in the calibration or post processing of the LiDAR data. The survey check points were distributed throughout the project area.</vertaccr>
        <qvertpa>
          <vertaccv>0.134</vertaccv>
          <vertacce>
            Tested 0.134 meters NVA at a 95% confidence level using 320 independent survey points located in open terrain. The survey check points were distributed throughout the project area. The 320 independent check points were surveyed using GPS techniques. See survey report for additional survey methodologies. Elevations from the unclassified LiDAR surface were measured for the x,y location of each checkpoint. Elevations interpolated from the LiDAR surface were then compared to the elevation values of the surveyed control points. The root mean square error vertical (RMSEz) was computed to be 0.068 meters. AccuracyZ has been tested to meet 19.0 cm NVA at 95-percent confidence level using (RMSEz * 1.9600) as defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using American Society of Photogrammetry and Remote Sensing (ASPRS) Guidelines.</vertacce>
        </qvertpa>
      </vertacc>
    </posacc>
    <lineage>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>Quantum Spatial, Inc.</origin>
            <pubdate>20210121</pubdate>
            <title>Ground Control for the Pennsylvania North Central Lidar QL2 Project</title>
            <geoform>Vector digital data and tabular digital data</geoform>
            <pubinfo>
              <pubplace>Quantum Spatial, Inc.</pubplace>
              <publish>Quantum Spatial, Inc.</publish>
            </pubinfo>
            <othercit>None</othercit>
          </citeinfo>
        </srccite>
        <typesrc>external hard drive</typesrc>
        <srctime>
          <timeinfo>
            <sngdate>
              <caldate>20190729</caldate>
            </sngdate>
          </timeinfo>
          <srccurr>Ground condition</srccurr>
        </srctime>
        <srccitea>Pennsylvania_North_Central_Lidar_QL2_gnd_ctrl</srccitea>
        <srccontr>This data source was used (along with airborne GPS/IMU data) to georeference the LiDAR point cloud data.</srccontr>
      </srcinfo>
      <procstep>
        <procdesc>Raw Data and Boresight Processing: The boresight for each lift was done individually as the solution may change slightly from lift to lift. The following steps describe the Raw Data Processing and Boresight process: 1) Technicians processed the raw data to LAS format flight lines using the final GPS/IMU solution. This LAS data set was used as source data for boresight. 2) Technicians first used Quantum Spatial, Inc. proprietary and commercial software to calculate initial boresight adjustment angles based on sample areas selected in the lift. These areas cover calibration flight lines collected in the lift, cross tie, and production flight lines. These areas are well distributed in the lift coverage and cover multiple terrain types that are necessary for boresight angle calculation. The technicians then analyzed the results and made any necessary additional adjustment until it was acceptable for the selected areas. 3) Once the boresight angle calculation was completed for the selected areas, the adjusted settings were applied to all of the flight lines of the lift and checked for consistency. The technicians utilized commercial and proprietary software packages to analyze how well flight line overlaps matched for the entire lift and adjusted as necessary until the results met the project specifications. 4) Once all lifts were completed with individual boresight adjustment, the technicians checked and corrected the vertical misalignment of all flight lines and also the matching between data and ground truth. The relative accuracy was less than or equal to 7 cm RMSEz within individual swaths and less than or equal to 10 cm RMSEz or within swath overlap (between adjacent swaths). 5) The technicians ran a final vertical accuracy check of the boresighted flight lines against the surveyed checkpoints after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level (Required Accuracy) was met.</procdesc>
        <srcused>Pennsylvania_North_Central_Lidar_QL2_gnd_ctrl</srcused>
        <procdate>2021</procdate>
      </procstep>
      <procstep>
        <procdesc>LAS Point Classification: The point classification was performed as described below. The bare earth surface was manually reviewed to ensure correct classification on the Class 2 (Ground) points. After the bare-earth surface was finalized, it was then used to generate all hydro-breaklines through heads-up digitization. All ground (ASPRS Class 2) LiDAR data inside of the Lake Pond and Double Line Drain hydro-flattened breaklines were then classified to Water (ASPRS Class 9) using TerraScan macro functionality. A buffer of 1 meter was also used around each hydro-flattened feature to classify these ground (ASPRS Class 2) points to Ignored ground (ASPRS Class 20). All Lake Pond Island and Double Line Drain Island features were checked to ensure that the ground (ASPRS Class 2) points were reclassified to the correct classification after the automated classification was completed. All overlap data was processed through automated functionality provided by TerraScan to classify the overlapping flight line data to approved classes. The overlap data was classified using standard LAS overlap bit. These classes were created through automated processes only and were not verified for classification accuracy. Due to software limitations within TerraScan, these classes were used to trip the withheld bit within various software packages. These processes were reviewed and accepted through numerous conference calls and pilot study areas. All data were manually reviewed and any remaining artifacts removed using functionality provided by TerraScan and TerraModeler. Global Mapper was used as a final check of the bare earth dataset. GeoCue was then used to create the deliverable industry-standard LAS files for both the All Point Cloud Data and the Bare Earth. Quantum Spatial, Inc. proprietary software was used to perform final statistical analysis of the classes in the LAS files, on a per tile level to verify final classification metrics and full LAS header information.</procdesc>
        <procdate>2021</procdate>
      </procstep>
    </lineage>
  </dataqual>
  <spdoinfo>
    <direct>Point</direct>
  </spdoinfo>
  <spref>
    <horizsys>
      <planar>
        <gridsys>
          <gridsysn>State Plane Coordinate System 1983</gridsysn>
          <spcs>
            <spcszone>3702</spcszone>
            <lambertc>
              <stdparll>39.9333333333</stdparll>
              <stdparll>40.9666666667</stdparll>
              <longcm>-77</longcm>
              <latprjo>39.3333333333</latprjo>
              <feast>1968500</feast>
              <fnorth>0.0</fnorth>
            </lambertc>
            </spcs>
        </gridsys>
        <planci>
          <plance>coordinate pair</plance>
          <coordrep>
            <absres>0.001</absres>
            <ordres>0.001</ordres>
          </coordrep>
          <plandu>Foot US</plandu>
        </planci>
      </planar>
      <geodetic>
        <horizdn>D North American 1983</horizdn>
        <ellips>Geodetic Reference System 80</ellips>
        <semiaxis>6378137.0</semiaxis>
        <denflat>298.257222101</denflat>
      </geodetic>
    </horizsys>
    <vertdef>
      <altsys>
        <altdatum>NAVD88 GEOID12B</altdatum>
        <altres>0.001</altres>
        <altunits>Foot US</altunits>
        <altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
      </altsys>
    </vertdef>
  </spref>
  <metainfo>
    <metd>20210121</metd>
    <metc>
      <cntinfo>
        <cntorgp>
          <cntorg>Quantum Spatial, Inc.</cntorg>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing and physical</addrtype>
          <address>523 Wellington Way</address>
          <city>Lexington</city>
          <state>KY</state>
          <postal>40503</postal>
          <country>USA</country>
        </cntaddr>
        <cntvoice>859-277-8700</cntvoice>
        <cntfax>859-277-8901</cntfax>
        <hours>Monday through Friday 8:00 AM to 5:00 PM (Eastern Time)</hours>
      </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>
