LiDAR Project- Sussex and Warren Counties, New Jersey LiDAR Task Order G12PD00941
Metadata also available as
Metadata:
- Identification_Information:
-
- Citation:
-
- Citation_Information:
-
- Originator: AeroMetric, Inc.
- Publication_Date: 20130121
- Title:
-
LiDAR Project- Sussex and Warren Counties, New Jersey LiDAR Task Order G12PD00941
- Geospatial_Data_Presentation_Form:
-
tabular digital data
vector digital data
raster digital data
- Publication_Information:
-
- Publication_Place: Sheboygan, WI
- Publisher: AeroMetric
- Description:
-
- Abstract:
-
This task order is for planning, acquisition, processing, and derivative products of LiDAR data collected in the vicinity of Sussex and Warren Counties in the state of New Jersey. LiDAR data, and derivative products produced in compliance with this task order are part of the data to be processed under Contract number G10PC00025, Order number G12PD00941. Specifications listed below are based on the U.S. Geological Survey National Geospatial Program Base LiDAR Specification, Version 13.
- Purpose:
-
USGS has a requirement for derivative LiDAR products in Sussex and Warren counties and vicinity in New Jersey. The LiDAR data set was collected previously at a nominal pulse spacing (NPS) of 1.4 meters or less. The Sussex-Warren LiDAR processing project is to provide raw point cloud, classified points and bare-earth processed LiDAR data suitable for the project area. The project consisted of processing provided data, calibration, classification of LiDAR data, and creation of final deliverable products. Vertical accuracy was to achieve a RMSE Z of 12.5 cm (0.41 feet)or better in "open terrain" and Fundamental Vertical Accuracy (FVA) of 24.5 cm (0.80 ft) at 95% confidence level based on RSMEz x 1.960 in "open terrain" as defined by National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASPRS Guidelines. The accuracy of the LiDAR data as tested met or exceeded the vertical accuracy requirements, however, derived products may be less accurate in areas of dense vegetation due to a lesser number of points defining the bare-earth in such areas.
- Supplemental_Information:
-
The LiDAR data set was collected by Kucera International then processed by Robinson Aerial Surveys, Inc under specification for The Federal Emergency Management Agency (FEMA).
Metadata files pertinent to the origination of this dataset named, 34041C_Terrain_metadata.xml and 34027C_Terrain_metadata.xml, may accompany this metadata and derivative products and can provide information on the initial collection details.
- Time_Period_of_Content:
-
- Time_Period_Information:
-
- Single_Date/Time:
-
- Calendar_Date: 20090111
- Currentness_Reference: ground condition
- Status:
-
- Progress: Complete
- Maintenance_and_Update_Frequency: As needed
- Spatial_Domain:
-
- Bounding_Coordinates:
-
- West_Bounding_Coordinate: -75.20
- East_Bounding_Coordinate: -74.51
- North_Bounding_Coordinate: 41.385
- South_Bounding_Coordinate: 40.845
- Keywords:
-
- Theme:
-
- Theme_Keyword_Thesaurus: None
- Theme_Keyword: Light Detection and Ranging
- Theme_Keyword: LiDAR
- Theme_Keyword: Breaklines
- Theme_Keyword: Survey Control
- Theme_Keyword: DEM
- Theme_Keyword: Lift
- Theme_Keyword: LAS
- Theme_Keyword: Swath
- Place:
-
- Place_Keyword_Thesaurus: None
- Place_Keyword: US
- Place_Keyword: State
- Place_Keyword: New Jersey
- Place_Keyword: NJ
- Place_Keyword: Sussex County
- Place_Keyword: Warren County
- Access_Constraints: None.
- Use_Constraints:
-
None.
However, users should be aware that changes may have occurred since this data set was collected in 2008 and that some parts of this data may no longer represent actual surface conditions.
The LiDAR data also lacks discrete time stamps and the scan angle is equal to 0, this is because the original data was las v1.0 which did not store this information.
Users of this data in critical applications should have a full awareness of its limitations.
Acknowledgment of the U.S. Geological Survey would be appreciated for products derived from these data.
- Point_of_Contact:
-
- Contact_Information:
-
- Contact_Person_Primary:
-
- Contact_Person: Mike Duncan
- Contact_Organization: United States Geological Survey
- Contact_Position: National Geospatial Technical Operations Center
- Contact_Address:
-
- Address_Type: mailing
- Address: 1400 Independence Road
- City: Rolla
- State_or_Province: MO
- Postal_Code: 65401
- Country: USA
- Contact_Voice_Telephone: 573-308-3799
- Contact_TDD/TTY_Telephone: unknown
- Contact_Facsimile_Telephone: 573-308-3810
- Contact_Electronic_Mail_Address: jduncan@usgs.gov
- Hours_of_Service: unknown
- Contact_Instructions: none
- Data_Set_Credit: AeroMetric, Inc.
- Native_Data_Set_Environment:
-
Processing Programs and versions - TerraSolid TerraScan (version 012.019), TerraModeler (version 012.008) and TerraMatch (version 012.010), Intergraph MicroStation (version 08.05.02.70), and GeoCue (version 2012.1.27.4).
Viewing Program - GlobalMapper V13.00
- Data_Quality_Information:
-
- Attribute_Accuracy:
-
- Attribute_Accuracy_Report:
-
LiDAR data set for this area was collected by Kucera International in 2008 to meet FEMA LIDAR Specifications for Flood Hazard Mapping, Appendix 4B (The expected horizontal RMSE of the 1"=100' Class 1 standards is +/- 1.5'(per acquisition metadata). This data set was provided to Aerometric. Aerometric performed ground survey in the area to collect ground check points to be used in vertical accuracy assessment of the data set.
- Logical_Consistency_Report: None
- Completeness_Report: Complete
- Positional_Accuracy:
-
- Horizontal_Positional_Accuracy:
-
- Horizontal_Positional_Accuracy_Report:
-
Data was collected in 2008 to meet FEMA LIDAR Specifications for Flood Hazard Mapping, Appendix 4B. <http://www.fema.gov/plan/prevent/fhm/lidar_4b.shtm#4>. The measurements contained within the elevation of this feature class are compiled to meet the ASPRS Class 1 accuracy standards for 1"=100' maps.
- Vertical_Positional_Accuracy:
-
- Vertical_Positional_Accuracy_Report:
-
The vertical accuracy of the data has been tested to achieve a RSMEz of 12.5 cm (0.41 ft) or better in "open terrain". Also a Fundamental Vertical Accuracy (FVA) of 24.5 cm (0.80 ft) at 95% confidence level based on RSMEz x 1.960 in "open terrain" as defined by National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASPRS Guidelines. Further, the data meets a Consolidated Vertical Accuracy (CVA) of 36.3 cm (1.19 ft) at 95th Percentile and a target value for Supplemental Vertical Accuracy (SVA) of 36.3 cm (1.19 ft) at 95th Percentile.
The vertical accuracy assessment is conducted by comparing ground survey check point z values to TIN or processed DEM file z values by horizontal proximity. Differences in z values are calculated to express an RMSEz value.
- Quantitative_Vertical_Positional_Accuracy_Assessment:
-
- Vertical_Positional_Accuracy_Value: 4.8 cm (0.158 ft) RMSEz .
- Vertical_Positional_Accuracy_Explanation:
-
Tested RMSE of 4.8 cm (0.158 ft) in open terrain (20 check points) as tested against the TIN.
- Quantitative_Vertical_Positional_Accuracy_Assessment:
-
- Vertical_Positional_Accuracy_Value: 9.4 cm (0.309 ft) FVA.
- Vertical_Positional_Accuracy_Explanation:
-
Tested FVA of 9.4 cm (0.309 ft) at the 95% confidence level in open terrain (20 check points) as tested against the TIN.
- Quantitative_Vertical_Positional_Accuracy_Assessment:
-
- Vertical_Positional_Accuracy_Value: 7.8 cm (0.256 ft) RMSEz .
- Vertical_Positional_Accuracy_Explanation:
-
Tested RMSE of 7.8 cm (0.256 ft) in open terrain (20 check points) as tested against the DEM.
- Quantitative_Vertical_Positional_Accuracy_Assessment:
-
- Vertical_Positional_Accuracy_Value: 15.3 cm (0.503 ft) FVA.
- Vertical_Positional_Accuracy_Explanation:
-
Tested FVA of 15.3 cm (0.503 ft) at the 95% confidence level in open terrain (20 check points) as tested against the DEM.
- Quantitative_Vertical_Positional_Accuracy_Assessment:
-
- Vertical_Positional_Accuracy_Value: 15.3 cm (0.503 ft).
- Vertical_Positional_Accuracy_Explanation:
-
Tested 15.3 cm (0.503 ft) SVA at the 95th Percentile in the Urban category (25 check points) against the DEM.
- Quantitative_Vertical_Positional_Accuracy_Assessment:
-
- Vertical_Positional_Accuracy_Value: 15.5 cm (0.510 ft).
- Vertical_Positional_Accuracy_Explanation:
-
Tested 15.5 cm (0.510 ft) SVA at the 95th Percentile in the Tall Grass category (21 check points) against the DEM.
- Quantitative_Vertical_Positional_Accuracy_Assessment:
-
- Vertical_Positional_Accuracy_Value: 18.4 cm (0.605 ft).
- Vertical_Positional_Accuracy_Explanation:
-
Tested 18.4 cm (0.605 ft) SVA at the 95th Percentile in the Brush category (20 check points) against the DEM.
- Quantitative_Vertical_Positional_Accuracy_Assessment:
-
- Vertical_Positional_Accuracy_Value: 13.0 cm (0.427 ft).
- Vertical_Positional_Accuracy_Explanation:
-
Tested 13.0 cm (0.427 ft) SVA at the 95th Percentile in the Forested category (20 check points) against the DEM.
- Quantitative_Vertical_Positional_Accuracy_Assessment:
-
- Vertical_Positional_Accuracy_Value: 16.1 cm (0.528 ft).
- Vertical_Positional_Accuracy_Explanation:
-
Tested 16.1 cm (0.528 ft) CVA at the 95th Percentile in all ground categories (106 check points) against the DEM.
- Lineage:
-
- Source_Information:
-
- Source_Citation:
-
- Citation_Information:
-
- Originator: Robinson Aerial Surveys, Inc
- Publication_Date: 20090111
- Title: DCS Terrain Submission for Warren_County, NJ
- Edition: FEMA CASE 08-02-0998S
- Geospatial_Data_Presentation_Form: tabular digital data
- Type_of_Source_Media: disc
- Source_Time_Period_of_Content:
-
- Time_Period_Information:
-
- Single_Date/Time:
-
- Calendar_Date: 20090111
- Source_Currentness_Reference: publication date
- Source_Citation_Abbreviation: Robinson Aerial
- Source_Contribution:
-
Analyze LiDAR data set to provide terrain models and data representing the topography of the project area to specifications of FEMA Guidelines and Specifications, Appendix N.
Contracted to meet FEMA LIDAR Specifications for Flood Hazard Mapping, Appendix 4B. <http://www.fema.gov/plan/prevent/fhm/lidar_4b.shtm#4>. The measurements contained within the elevation of this feature class are compiled to meet the ASPRS Class 1 accuracy standards for 1"=100' maps.
- Source_Information:
-
- Source_Citation:
-
- Citation_Information:
-
- Originator: Kucera International
- Publication_Date: 200804
- Title: Airborne LiDAR Acquisition
- Type_of_Source_Media: disc
- Source_Time_Period_of_Content:
-
- Time_Period_Information:
-
- Range_of_Dates/Times:
-
- Beginning_Date: Unknown
- Ending_Date: Unknown
- Source_Currentness_Reference: ground condition
- Source_Citation_Abbreviation: Kucera International
- Source_Contribution:
-
Initial LiDAR collection was conducted by Kucera International in April 2008 with a Leica ALS50 airborne LiDAR system. Acquisition was made with a Nominal Point Spacing of 1.4 meters. Ground point classification was carried out using TerraScan software by Terrasolid Limited. In the filtering process raw data was classified as Ground or non-Ground, (Unclassified), and provided as LAS 1.0 data.
- Process_Step:
-
- Process_Description:
-
The LiDAR data set was provided to AeroMetric to process and produce the necessary derivatives.
Point Cloud Processing:
1. Horizontal Datum - North American Datum 1983 (NAD83)
2. Horizontal Coordinates - New Jersey State Plane - 2900 - feet.
3. Vertical Datum - North American Vertical Datum 1988 (NAVD88)
4. Geoid Model used to reduce satellite derived elevations to orthometric heights - NGS Geoid09.
LiDAR Processing:
1. Point Cloud data is imported to TerraScan in a Microstation V8 (V) CAD environment on a specified 5000 foot by 5000 foot tiling scheme.
2. Analyze the data for overall completeness and consistency. This is to ensure that there are no voids in the data.
3. Inspect for calibration errors in the dataset using the TerraMatch software. This is accomplished by sampling the data collected across all flight lines and classify the individual lines to ground class. The software will use the ground-classified lines to compute corrections (Heading, Pitch, Roll, and Scale).
4. Orientation corrections (i.e. Calibration corrections) are then applied (if needed) to the entire dataset.
5. Automatic ground classification is performed using algorithms with customized parameters to best fit the project area. Several areas of varying relief and planimetric features were inspected to verify the final ground surface.
6. AeroMetric, Inc. provided Quality Assurance and Quality Control (QA/QC) data for this project. AeroMetric captured QA/QC points in 'open terrain' land cover category that were used to test the accuracy of the LiDAR ground surface. TerraScan's Output Control Report (OCR) was used to compare the QA/QC data to the LiDAR data. This routine searches the LiDAR dataset by X and Y coordinate, finds the closest LiDAR point and compares the vertical (Z) values to the known data collected in the field. Based on the QA/QC data, a bias adjustment was determined, and the results were applied (if necessary) to the LiDAR data.
7. Once the LiDAR point cloud has been adjusted vertically to best fit the survey control points, a macro is run via TerraScan outputting each flightline swath separately. During this process all points are reclassified to class 0
8. Once the automatic processing and the testing of LiDAR is complete, AeroMetric meticulously reviews the generated bare-earth surface data to ensure that proper classification was achieved as part of a Quality Control process.
9. Each tile is reviewed for accuracy and consistency of the macro ground classification. During this phase, MicroStation is used to generate line work representing water bodies and rivers. Separate line work is also placed in instances where overpasses have blocked enough valid ground returns or water gave too few ground returns to reasonably portray the ground surface. A proprietary in-house software program is then run to drape the river line work in a flowing fashion. Contours are generated on the river breaklines to review monotonicity of the draped line work.
10. Final deliverables are generated and output to a client specified tiling scheme.
- Process_Date: 201210
- Cloud_Cover: Unknown
- Spatial_Data_Organization_Information:
-
- Direct_Spatial_Reference_Method: Point
- 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: 2900
- Transverse_Mercator:
-
- Scale_Factor_at_Central_Meridian: 0.9999
- Longitude_of_Central_Meridian: -74.5
- Latitude_of_Projection_Origin: 38.83333
- False_Easting: 492125.0
- False_Northing: 0
- Planar_Coordinate_Information:
-
- Planar_Coordinate_Encoding_Method: coordinate pair
- Coordinate_Representation:
-
- Abscissa_Resolution: 0.01
- Ordinate_Resolution: 0.01
- Planar_Distance_Units: Survey Feet
- Geodetic_Model:
-
- Horizontal_Datum_Name: North American Datum of 1983
- Ellipsoid_Name: Geoid 09
- 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
- Altitude_Resolution: 0.01
- Altitude_Distance_Units: Survey Feet
- Altitude_Encoding_Method:
-
Explicit elevation coordinate included with horizontal coordinates
- Entity_and_Attribute_Information:
-
- Detailed_Description:
-
- Entity_Type:
-
- Entity_Type_Label: Point Cloud
- Entity_Type_Definition: Points describing measured echo from ground surface
- Entity_Type_Definition_Source: LAS 1.2
- Detailed_Description:
-
- Entity_Type:
-
- Entity_Type_Label: Object ID
- Entity_Type_Definition: Internal feature number
- Entity_Type_Definition_Source: ERSI
- Detailed_Description:
-
- Entity_Type:
-
- Entity_Type_Label: Shape
- Entity_Type_Definition: Feature geometry
- Entity_Type_Definition_Source: ESRI
- Overview_Description:
-
- Entity_and_Attribute_Overview:
-
LiDAR data provides spatial representation of terrain features in horizontal and vertical dimensions relative to surrounding features and may be geo-referenced.
- Entity_and_Attribute_Detail_Citation: LiDAR data
- Metadata_Reference_Information:
-
- Metadata_Date: 20130118
- Metadata_Contact:
-
- Contact_Information:
-
- Contact_Organization_Primary:
-
- Contact_Organization: AeroMetric, Inc.
- Contact_Address:
-
- Address_Type: Mailing and physical address
- Address: 4020 Technology Parkway
- City: Sheboygan
- State_or_Province: WI
- Postal_Code: 53083-6049
- Country: US
- Contact_Voice_Telephone: 1-920-457-3631
- Contact_Facsimile_Telephone: 1-920-457-0410
- Contact_Electronic_Mail_Address: cguy@aerometric.com
- Hours_of_Service: Monday through Friday 8:00 AM to 5:00 PM (Central Time)
- Metadata_Standard_Name: FGDC Content Standard for Digital Geospatial Metadata
- Metadata_Standard_Version: FGDC-STD-001-1998
Generated by mp version 2.9.6 on Mon Jan 21 11:24:29 2013