PA_17County_2024; Classified Point Cloud


Identification_Information:
Citation:
Citation_Information:
Originator:NV5 Geospatial
Publication_Date:20260917
Title:
PA_17County_2024; Classified Point Cloud
Geospatial_Data_Presentation_Form:LiDAR point cloud
Description:
Abstract:
       Product: These lidar data are processed Classified LAS 1.4 files, formatted to 11982 individual 2500 ft x 2500 ft tiles; used to create intensity images, 3D breaklines, and hydro-flattened DEMs as necessary.
       Geographic Extent: 20 counties in Pennsylvania, covering approximately 3039 total square miles.
       Dataset Description: The PA_17County_2024 project called for the planning, acquisition, processing, and derivative products of lidar data to be collected at a nominal pulse spacing (NPS) of 0.35 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base LiDAR Specification, 2024 Rev. A. The data were developed based on a horizontal projection/datum of NAD 1983 2011 StatePlane Pennsylvania North FIPS 3701 Ft US, Foot US and vertical datum of NAVD88 Geoid 18, Foot US. LiDAR data were delivered as processed Classified LAS 1.4 files formatted to 11982 individual 2500 ft x 2500 ft tiles. All rasters were tiled to a 5000 ft x 5000 ft schema. Continuous breaklines were produced in shapefile format.
       Ground Conditions: LiDAR was collected in spring 2024 through winter 2024, 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, NV5 Geospatial utilized a total of 119 ground control points that were used to calibrate the LiDAR to known ground locations established throughout the project area. An additional 153 independent accuracy checkpoints, 123 in Bare Earth and Urban landcovers (123 NVA points), 30 in Tall Weeds categories (30 VVA points), were used to assess the vertical accuracy of the data. These checkpoints were not used to calibrate or post process the data.
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 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.
Supplemental_Information:
CONTRACTOR: NV5 Geospatial
Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date:20240416
Ending_Date:20241214
Currentness_Reference:
Ground condition
Status:
Progress:Complete
Maintenance_and_Update_Frequency:None planned
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate:-77.6179532841
East_Bounding_Coordinate:-75.5692573906
North_Bounding_Coordinate:41.6075057372
South_Bounding_Coordinate:40.8873203777
Keywords:
Theme:
Theme_Keyword_Thesaurus:None
Theme_Keyword:Model
Theme_Keyword:LAS Point Cloud
Theme_Keyword:Remote Sensing
Theme_Keyword:Elevation Data
Theme_Keyword:Withheld Bit Flag Proof of Performance
Theme_Keyword:Swath Separation
Theme_Keyword:LiDAR
Place:
Place_Keyword_Thesaurus:None
Place_Keyword:Pennsylvania
Place_Keyword:Bradford County
Place_Keyword:Carbon County
Place_Keyword:Clinton County
Place_Keyword:Columbia County
Place_Keyword:Lackawanna County
Place_Keyword:Luzerne County
Place_Keyword:Lycoming County
Place_Keyword:Monroe County
Place_Keyword:Montour County
Place_Keyword:Northumberland County
Place_Keyword:Potter County
Place_Keyword:Schuylkill County
Place_Keyword:Sullivan County
Place_Keyword:Tioga County
Place_Keyword:Union County
Place_Keyword:Wyoming County
Access_Constraints:No restrictions apply to these data.
Use_Constraints:
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.
Point_of_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization:NV5 Geospatial
Contact_Person:Greg Williams
Contact_Address:
Address_Type:mailing and physical
Address:
523 Wellington Way
City:Lexington
State_or_Province:KY
Postal_Code:40503
Country:USA
Contact_Voice_Telephone:859-277-8700
Contact_Facsimile_Telephone:859-277-8901
Contact_Electronic_Mail_Address:gregory.williams@nv5.com
Hours_of_Service:Monday through Friday 8:00 AM to 5:00 PM (Eastern Time)
Contact Instructions:
If unable to reach the contact by telephone, please send an email. You should get a response within 24 hours.
Native_Data_Set_Environment:
MicroStation Connect; TerraScan Version 21.016; STRIPALIGN 2.21 ; TerraModeler Version 21.008; GeoCue Version 2020.1.22.1; Esri ArcGIS 10.6; Global Mapper 19/20; RiProcess 1.8.6; Windows 10 Operating System \\point_cloud\tilecls\*.las
Back to Top
Data_Quality_Information:
Logical_Consistency_Report:
Data cover the entire area specified for this project.
Completeness_Report:
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.
Positional_Accuracy:
Horizontal_Positional_Accuracy:
Horizontal_Positional_Accuracy_Report:
This data set was produced to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 18 (cm) RMSEh Horizontal Accuracy Class which equates to Positional Horizontal Accuracy = +/- 33 cm at a 95% confidence level.
Vertical_Positional_Accuracy:
Vertical_Positional_Accuracy_Report:
          The specifications require that only nonvegetated vertical accuracy (NVA) be computed for raw LiDAR data swath files. The vertical accuracy was tested with 123 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.
Quantitative_Vertical_Positional_Accuracy_Assessment:
Vertical_Positional_Accuracy_Value:0.0547
Vertical_Positional_Accuracy_Explanation:
            Tested 0.0547 meters NVA at a 95% confidence level using 123 independent survey points located in open terrain. The survey check points were distributed throughout the project area. The 123 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.0279 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.
Lineage:
Source_Information:
Source_Citation:
Citation_Information:
Originator:NV5
Publication_Date:20260917
Title:
Ground Control for the PA_17County_2024 Project
Geospatial_Data_Presentation_Form:Vector digital data and tabular digital data
Publication_Information:
Publication_Place:NV5
Publisher:NV5
Other_Citation_Details:
None
Type_of_Source_Media:external hard drive
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date:20240528
Source_Currentness_Reference:
Ground condition
Source_Citation_Abbreviation:
PA_17County_2024_gnd_ctrl
Source_Contribution:
This data source was used (along with airborne GPS/IMU data) to georeference the LiDAR point cloud data.
Process_Step:
Process_Description:
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 NV5 Geospatial 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.
Source_Used_Citation_Abbreviation:
PA_17County_2024_gnd_ctrl
Process_Date:2026
Process_Step:
Process_Description:
LAS Point Classification: The point classification is performed as described below. The bare earth surface is then manually reviewed to ensure correct classification on the Class 2 (Ground) points. After the bare-earth surface is finalized, it is 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 flattening breaklines were then classified to water (ASPRS Class 9) using TerraScan macro functionality. A buffer of 0.5 feet 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 by USGS. 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 by USGS through numerous conference calls and pilot study areas. All data was manually reviewed and any remaining artifacts removed using functionality provided by TerraScan and TerraModeler. Global Mapper us 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. 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.
Process_Date:2026
Process_Step:
Process_Description:
Maximum Surface Height Rasters were produced as ancillary data from the classified lidar point cloud in order to evaluate the withheld bit flag proof of performance for points that cannot be reasonably interpreted as valid surface returns. These were produced using all returns, withheld flagged points excluded, and using the highest elevation point value from each pixel. These rasters are 32-bit, floating point format and delivered as GeoTIFF files per tile. MSHR are generated from the point cloud data and will not be altered after creation nor will there be further maintenance on this product.
Process_Date:2026
Process_Step:
Process_Description:
Swath Separation Imagery was produced for the entire project area. Swath separation images use color-coding to illustrate differences in elevation (z-) values where swaths overlap. The color-coded images are semi-transparent and overlay the lidar intensity image. They are ancillary data used as visual aids to more easily identify regions within point cloud datasets that may have suspect interswath alignment or other geometric issues. Imagery was created using last returns with all classification and bit flags, except for noise and withheld bit flag are included. SSI are generated from the point cloud data and will not be altered after creation nor will there be further maintenance on this product.
Process_Date:2026
Back to Top
Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method:Point
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type:Point
Point_and_Vector_Object_Count:1324842079147
Back to Top
Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Planar:
Grid_Coordinate_System:
Grid_Coordinate_System_Name:State Plane Coordinate System 1983
State_Plane_Coordinate_System:
SPCS_Zone_Identifier:3701
Lambert_Conformal_Conic:
Standard_Parallel:40.8833333333
Standard_Parallel:41.95
Longitude_of_Central_Meridian:-77
Latitude_of_Projection_Origin:40.1666666667
False_Easting:1968500
False_Northing:0.0
Planar_Coordinate_Information:
Planar_Coordinate_Encoding_Method:coordinate pair
Coordinate_Representation:
Abscissa_Resolution:0.001
Ordinate_Resolution:0.001
Planar_Distance_Units:Foot US
Geodetic_Model:
Horizontal_Datum_Name:North American Datum of 1983 (2011)
Ellipsoid_Name:Geodetic Reference System 80
Semi-major_Axis:6378137.0
Denominator_of_Flattening_Ratio:298.257222101
Vertical_Coordinate_System_Definition:
Altitude_System_Definition:
Altitude_Datum_Name:NAVD88 Geoid 18
Altitude_Resolution:0.001
Altitude_Distance_Units:Foot US
Altitude_Encoding_Method:Explicit elevation coordinate included with horizontal coordinates
Back to Top
Distribution_Information:
Distributor:
Contact_Information:
Contact_Person_Primary:
Contact_Organization:Pennsylvania Spatial Data Access (PASDA)
Contact_Address:
Address_Type:mailing address
Address:
115 Land and Water research building
City:University Park
State_or_Province:Pennsylvania
Postal_Code:16802
Country:United States
Contact_Voice_Telephone:814-865-8792
Contact_Electronic_Mail_Address:pasda@psu.edu
Resource_Description:Downloadable Data
Distribution_Liability:
The USER shall indemnify, save harmless, and, if requested, defend those parties involved with the development and distribution of this data, their officers, agents, and employees from and against any suits, claims, or actions for injury, death, or property damage arising out of the use of or any defect in the FILES or any accompanying documentation. Those parties involved with the development and distribution excluded any and all implied warranties, including warranties or merchantability and fitness for a particular purpose and makes no warranty or representation, either express or implied, with respect to the FILES or accompanying documentation, including its quality, performance, merchantability, or fitness for a particular purpose. The FILES and documentation are provided "as is" and the USER assumes the entire risk as to its quality and performance. Those parties involved with the development and distribution of this data will not be liable for any direct, indirect, special, incidental, or consequential damages arising out of the use or inability to use the FILES or any accompanying documentation.
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Transfer_Size:0.006
Back to Top
Metadata_Reference_Information:
Metadata_Date:20260917
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization:NV5 Geospatial
Contact_Address:
Address_Type:mailing and physical
Address:
523 Wellington Way
City:Lexington
State_or_Province:KY
Postal_Code:40503
Country:USA
Contact_Voice_Telephone:859-277-8700
Contact_Facsimile_Telephone:859-277-8901
Hours_of_Service:Monday through Friday 8:00 AM to 5:00 PM (Eastern Time)
Metadata_Standard_Name:FGDC Content Standard for Digital Geospatial Metadata
Metadata_Standard_Version:FGDC-STD-001-1998
Metadata_Access_Constraints:None.
Metadata_Use_Constraints:
None.
Metadata_Security_Information:
Metadata_Security_Classification_System:None.
Metadata_Security_Classification:Unclassified
Metadata_Security_Handling_Description:
NONE
Metadata_Extensions:
Online_Linkage: None.
Profile_Name:None.
Back to Top