DVRPC 2015 LiDAR


Identification_Information:
Citation:
Citation_Information:
Originator:Delaware Valley Regional Planning Commission
Publication_Date:2016
Title:
DVRPC 2015 LiDAR
Geospatial_Data_Presentation_Form:Lidar point cloud
Description:
Abstract:
Geographic Extent: Delaware Valley, covering approximately 3260 square miles over the Philadelphia Metro area, comprised of of 8 contiguous counties located in the states of Pennsylvania and New Jersey. Dataset Description: Delaware Valley 2015 LiDAR project called for the Planning, Acquisition, processing and derivative products of LIDAR data to be collected at a nominal pulse spacing (NPS) of 0.7 meter. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base LIDAR Specification, Version 1.2. The data was developed based on a horizontal projection/datum of UTM Zone 18, NAD83 (2011), meters and vertical datum of NAVD1988 (GEOID12A), meters. LiDAR data was delivered in RAW flight line swath format, processed to create Classified LAS 1.4 Files formatted to 25 individual 1500 meter X 1500 meter tiles for the pilot (3752 individual 1500 meter X 1500 meter tiles for the entire project area), Bare Earth DEMs tiled to the same 1500 meter X 1500 meter tile schema, and Breaklines in Esri shapefile format. Ground Conditions: LiDAR was collected in spring of 2015, 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, Quantum Spatial established 76 calibration control points in order to calibrate the LIDAR to known ground locations established throughout the Delaware Valley project area. The accuracy of the data was checked with 91 NVA points and 70 VVA points (161 total QC checkpoints).
Purpose:
Classified LAS files are used to show the manually reviewed bare earth surface. This allows the user to create Breaklines and Raster DEMs. The purpose of these lidar data was to produce high accuracy 3D hydro-flattened Digital Elevation Model (DEM) with a 1-meter cell size. These raw lidar point cloud data were used to create classified lidar LAS files, 3D breaklines, and hydro-flattened DEMs as necessary.
Supplemental_Information:
			    USGS Contract: G10PC00026  Task Order Number: G15PD00316
			    CONTRACTOR: Quantum Spatial
			    Lidar data were acquired and calibrated by Quantum Spatial.
			    All follow-on processing was completed by the prime contractor.
			
Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date:20150412
Ending_Date:20151125
Currentness_Reference:
ground condition
Status:
Progress:Complete
Maintenance_and_Update_Frequency:None planned
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate:-75.7114343254321
East_Bounding_Coordinate:-74.3752046076557
North_Bounding_Coordinate:40.610171463261
South_Bounding_Coordinate:39.502118241734
Keywords:
Theme:
Theme_Keyword_Thesaurus:None
Theme_Keyword:Elevation data
Theme_Keyword:Lidar
Theme_Keyword:Hydrology
Place:
Place_Keyword_Thesaurus:None
Place_Keyword:Delaware Valley
Place_Keyword:New Jersey
Place_Keyword:Burlington County
Place_Keyword:Camden County
Place_Keyword:Gloucester County
Place_Keyword:Mercer County
Place_Keyword:Pennsylvania
Place_Keyword:Bucks County
Place_Keyword:Delaware County
Place_Keyword:Mercer County
Place_Keyword:Philadelphia Coutny
Access_Constraints:No restrictions apply to this 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 its limitations. Acknowledgement of the U.S. Geological Survey would be appreciated for products derived from these data.
Point_of_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization:Quantum Spatial, Data Acquisition Department
Contact_Person:Tobin Guthrie
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:tguthrie@quantumspatial.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 Version 8; TerraScan Version 15; TerraModeler Version 15; GeoCue Version 2014.1.21.1; ESRI ArcGIS 10.2; Global Mapper 16; Leica Cloud Pro 1.2; Windows 7 Operating System \\psihq_nx3200\Projects\26236_DVRPC_LiDAR\ 24.1 GB and \\Matrix\LIDAR\26236_DVRPC\ 5.09 TB
Back to Top
Data_Quality_Information:
Logical_Consistency_Report:
Data cover the entire area specified for this project.
Completeness_Report:
			These raw 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 Nonvegetated Vertical Accuracy specifications.
		
Positional_Accuracy:
Vertical_Positional_Accuracy:
Vertical_Positional_Accuracy_Report:
					The specifications require that only raw Nonvegetated Vertical Accuracy (NVA) be computed for raw lidar point cloud swath files. The raw NVA was tested with 91 independent survey points distributed throughout the project area and located in open terrain. These checkpoints were not used in the calibration or post-processing of the lidar point cloud data. Specifications for this project require that the raw NVA be 19.6 cm or better AccuracyZ at 95 percent confidence level.
					The specifications require that Nonvegetated Vertical Accuracy (NVA) be computed for DEM files. The NVA was tested with 91 independent survey points distributed throughout the project area and located in open terrain. These checkpoints were not used in the calibration or post-processing of the lidar point cloud data. Specifications for this project require that the NVA be 19.6 cm or better AccuracyZ at 95 percent confidence level.
					The specifications require that Vegetated Vertical Accuracy (VVA) be computed for DEM files. The VVA was tested with 70 independent survey points distributed throughout the project area and located in vegetated terrain. These checkpoints were not used in the calibration or post-processing of the lidar point cloud data. Specifications for this project require that the VVA be 29.4 cm or better at the 95th percentile.
				
Quantitative_Vertical_Positional_Accuracy_Assessment:
Vertical_Positional_Accuracy_Value:0.085
Vertical_Positional_Accuracy_Explanation:
						The raw NVA was tested using 91 independent survey points located in open terrain. The surveyed checkpoints were distributed throughout the project area and surveyed using GNSS procedures and methodologies that provide reliable and consistent results to meet the project's accuracy requirements. Please see the "Survey Accuracy Requirements" and "Field Methodology" sections in the Survey Report for more information. Elevations from the unclassified lidar surface were measured for the x,y location of each check point. Elevations interpolated from the unclassified lidar surface were then compared to the elevation values of the surveyed control. The RMSEz was computed to be 0.04 meters and AccuracyZ to be 0.085 meters. This meets the required AccuracyZ value of 19.6 cm raw 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 National Digital Elevation Program (NDEP)/ASPRS Guidelines.
					
Quantitative_Vertical_Positional_Accuracy_Assessment:
Vertical_Positional_Accuracy_Value:0.081
Vertical_Positional_Accuracy_Explanation:
						The NVA was tested using 91 independent survey points located in open terrain. The surveyed checkpoints were distributed throughout the project area and surveyed using GNSS procedures and methodologies that provide reliable and consistent results to meet the project's accuracy requirements. Please see the "Survey Accuracy Requirements" and "Field Methodology" sections in the Survey Report for more information. Elevations from the DEM surface were measured for the x,y location of each check point. Elevations interpolated from the DEM surface were then compared to the elevation values of the surveyed control. The RMSEz was computed to be 0.041 meters and AccuracyZ to be 0.081 meters. This meets the required AccuracyZ value of 19.6 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 National Digital Elevation Program (NDEP)/ASPRS Guidelines.
					
Quantitative_Vertical_Positional_Accuracy_Assessment:
Vertical_Positional_Accuracy_Value:0.263
Vertical_Positional_Accuracy_Explanation:
						The VVA was tested using 70 independent survey points located in vegetated terrain. The surveyed checkpoints were distributed throughout the project area and surveyed using GNSS procedures and methodologies that provide reliable and consistent results to meet the project's accuracy requirements. Please see the "Survey Accuracy Requirements" and "Field Methodology" sections in the Survey Report for more information. Elevations from the DEM surface were measured for the x,y location of each check point. Elevations interpolated from the DEM surface were then compared to the elevation values of the surveyed control. The VVA was computed to be 0.263 meters. This meets the required value of 29.4 cm VVA at 95th percentile level using the 95th percentile of the absolute value of all vertical errors in all combined vegetation classes as defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASPRS Guidelines.
					
Lineage:
Source_Information:
Source_Citation:
Citation_Information:
Originator:Quantum Spatial
Publication_Date:2015
Title:
Control Survey Report: Delaware Valley Ortho and Lidar Task Order
Geospatial_Data_Presentation_Form:vector digital data and tabular data
Publication_Information:
Publication_Place:Lexington, KY
Publisher:Quantum Spatial
Type_of_Source_Media:CD-ROM
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date:2015
Source_Currentness_Reference:
ground condition
Source_Citation_Abbreviation:
DE_Valley_2015_LiDAR_ctrl
Source_Contribution:
This data source was used (along with the airborne GPS/IMU Data) to aid in the georeferencing of the lidar point cloud data.
Source_Information:
Source_Citation:
Citation_Information:
Originator:Quantum Spatial
Publication_Date:2015
Title:
Lidar RAW Data for Delaware Valley 2015
Geospatial_Data_Presentation_Form:lidar data
Publication_Information:
Publication_Place:Quantum Spatial
Publisher:2015
Type_of_Source_Media:online
Source_Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date:20150412
Ending_Date:20151125
Source_Currentness_Reference:
ground condition
Source_Citation_Abbreviation:
DE_Valley_2015_LiDAR_Data
Source_Contribution:
This data source was used to populate the lidar point cloud data.
Process_Step:
Process_Description:
			Lidar Pre-Processing: Airborne GPS and IMU data were merged to develop a Single Best Estimate (SBET) of the lidar system trajectory for each lift. Lidar ranging data were initially calibrated using previous best parameters for this instrument and aircraft. Relative calibration was evaluated using advanced plane-matching analysis and parameter corrections derived. This was repeated iteratively until residual errors between overlapping swaths, across all project lifts, was reduced to 2 cm or less. Data were then block adjusted to match surveyed calibration control. Raw data NVA were checked using independently surveyed checkpoints. Swath overage points were identified and tagged within each swath file.
Source_Used_Citation_Abbreviation:
DE_Valley_2015_LiDAR_gnd_ctrl
Process_Date:2015
Source_Produced_Citation_Abbreviation:
LiDAR datasets with USGS classifications
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization:Quantum Spatial
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)
Contact Instructions:
If unable to reach the contact by telephone, please send an email. You should get a response within 24 hours.
Process_Step:
Process_Description:
			Lidar Post-Processing: The calibrated and controlled lidar swaths 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. 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 area.
			All classification tags are stored in the original swath files.
			After completion of classification and final QC approval, the NVA and VVA for the project are calculated. Sample areas for each land cover type present in the project area were extracted and forwarded to the client, along with the results of the accuracy tests. Upon acceptance, the complete classified lidar swath files were delivered to the client.
Source_Used_Citation_Abbreviation:
DE_Valley_2015_LiDAR_ctrl
Source_Used_Citation_Abbreviation:
DE_Valley_2015_LiDAR_Data
Process_Date:2015
Source_Produced_Citation_Abbreviation:
DE_Valley_2015_LiDAR_Data
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization:Quantum Spatial
Contact_Person:Paul Bishop
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:pbishop@quantumspatial.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.
Process_Step:
Process_Description:
			Classified LAS Processing: 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 1 meter was also used around each hydro-flattened feature to classify these ground (ASPRS Class 2) points to Ignored ground (ASPRS Class 10).  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 bridge decks were classified to Class 17.
			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 identified using the Overlap Flag, per LAS 1.4 specifications.
			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.  Quantum Spatial 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.
Source_Used_Citation_Abbreviation:
DE_Valley_2015_LiDAR_ctrl
Source_Used_Citation_Abbreviation:
DE_Valley_2015_LiDAR_Data
Process_Date:2015
Source_Produced_Citation_Abbreviation:
Classified LAS
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization:Quantum Spatial
Contact_Person:Paul Bishop
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:pbishop@quantumspatial.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.
Process_Step:
Process_Description:
			        Hydro Flattened Breakline Processing: 
			        Class 2 LiDAR was used to create a bare earth surface model.  The surface model was then used to heads-up digitize 2D breaklines of inland streams and rivers with a 30 meter nominal width and Inland Ponds and Lakes of 2 acres or greater surface area.
			        Elevation values were assigned to all Inland Ponds and Lakes, Inland Pond and Lake Islands, Inland Stream and River Islands, using TerraModeler functionality.
			        Elevation values were assigned to all Inland streams and rivers using Quantum Spatial proprietary software.
			        All ground (ASPRS Class 2) LiDAR data inside of the collected inland 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.  These points were moved from ground (ASPRS Class 2) to Ignored Ground (ASPRS Class 10).
			        The breakline files were then translated to ESRI File-Geodatabase format using ESRI conversion tools.
Source_Used_Citation_Abbreviation:
DE_Valley_2015_LiDAR_ctrl
Source_Used_Citation_Abbreviation:
DE_Valley_2015_LiDAR_Data
Process_Date:2015
Source_Produced_Citation_Abbreviation:
Hydro Flattened Breaklines
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization:Quantum Spatial
Contact_Person:Paul Bishop
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:pbishop@quantumspatial.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.
Process_Step:
Process_Description:
			        Hydro Flattened Raster DEM Process: 
			        Class 2 LiDAR in conjunction with the hydro breaklines were used to create a 1 meter Raster DEM.  Using automated scripting routines within ArcMap, an ERDAS Imagine IMG file was created for each tile.  Each surface is reviewed using Global Mapper to check for any surface anomalies or incorrect elevations found within the surface. 
				
Source_Used_Citation_Abbreviation:
DE_Valley_2015_LiDAR_ctrl
Source_Used_Citation_Abbreviation:
DE_Valley_2015_LiDAR_Data
Process_Date:2015
Source_Produced_Citation_Abbreviation:
Hydro Flattened Raster DEMs
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization:Quantum Spatial
Contact_Person:Paul Bishop
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:pbishop@quantumspatial.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.
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
Back to Top
Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Planar:
Grid_Coordinate_System:
Grid_Coordinate_System_Name:Universal Transverse Mercator
Universal_Transverse_Mercator:
UTM_Zone_Number:18
Transverse_Mercator:
Scale_Factor_at_Central_Meridian:0.9996
Longitude_of_Central_Meridian:-75.0
Latitude_of_Projection_Origin:0.0
False_Easting:500000.0
False_Northing:0.0
Planar_Coordinate_Information:
Planar_Coordinate_Encoding_Method:coordinate pair
Coordinate_Representation:
Abscissa_Resolution:0.01
Ordinate_Resolution:0.01
Planar_Distance_Units:meter
Geodetic_Model:
Horizontal_Datum_Name:North American Datum of 1983 (2011)
Ellipsoid_Name:Geodetic Reference System 80
Semi-major_Axis:6378137
Denominator_of_Flattening_Ratio:298.257222101
Vertical_Coordinate_System_Definition:
Altitude_System_Definition:
Altitude_Datum_Name:North American Vertical Datum of 1988 (Geoid 12A)
Altitude_Resolution:0.01
Altitude_Distance_Units:meters
Altitude_Encoding_Method:Explicit elevation coordinate included with horizontal coordinates
Back to Top
Metadata_Reference_Information:
Metadata_Date:20160506
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization:Quantum Spatial
Contact_Person:Sarah Zibart
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:szibart@quantumspatial.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.
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
Back to Top