Naches River, Yakima, WA, LiDAR Acquisition

Metadata also available as - [Questions & Answers] - [Parseable text] - [XML]

Metadata:


Identification_Information:
Citation:
Citation_Information:
Originator: Quantum Spatial, Inc. (formerly Aerometric, Inc.)
Publication_Date: 20140210
Title: Naches River, Yakima, WA, LiDAR Acquisition
Geospatial_Data_Presentation_Form: Lidar point cloud
Description:
Abstract:
Task Order: W912EF-12-D-0007 EC04 issued by the U.S. Army Corps of Engineers, Seattle District This dataset is LiDAR point cloud data and derivative models of the Naches River, Hwy 410 to mouth of Yakima River, from Naches confluence to Parker Bridge, approximately 32 square miles.
This dataset consists of LiDAR point cloud LAS swath files and tiles. Each LAS file contains LiDAR point information which has been calibrated, controlled, and classified. Each file represents a separate swath or tile of LiDAR.
Quantum Spatial Project No: 1130916
Lidar_Information:
Lidar_Collection_Information:
Lidar_Specification: USGS NGP Base Specification v1
Lidar_Sensor: Leica ALS60 sensor SN6105
Lidar_Maximum_Returns: 4
Lidar_Pulse_Spacing: 0.5
Lidar_Density: 4.06
Lidar_Flight_Height: 900
Lidar_Flight_Speed: 105
Lidar_Scan_Angle: 30
Lidar_Scan_Frequency: 61.1
Lidar_Pulse_Rate: 105.9
Lidar_Pulse_Duration: 4
Lidar_Pulse_Width: NA
Lidar_Central_Wavelength: 1064
Lidar_Multiple_Pulses_In_Air: 0
Lidar_Beam_Divergence: 0.15
Lidar_Swath_Width: 482.31
Lidar_Swath_Overlap: 20
Lidar_Coordinate_Reference_System_Name: NAD_1983_2011_StatePlane_Washington_South_FIPS_4602_Ft_US
Lidar_Geoid: National Geodetic Survey (NGS) Geoid09
Lidar_Accuracy_Information:
Lidar_Calculated_Horizontal_Accuracy: 0.1
Lidar_Raw_Fundamental_Vertical_Accuracy: NA
Lidar_LAS_Information:
Lidar_LAS_Version: 1.2
Lidar_LAS_Point_Record_Format: 1
Lidar_LAS_Witheld_Point_Identifier:
Withheld (ignore) points were identified in these files using the standard LAS Withheld bit
Lidar_LAS_Overage_Point_Identifier:
Swath "overage" points were identified in these files by adding 16 to the standard classification values.
Lidar_LAS_Radiometric_Resolution: 8-bit
Lidar_LAS_Classification:
Lidar_LAS_Class_Code: 0
Lidar_LAS_Class_Description: Never Processed
Lidar_LAS_Classification:
Lidar_LAS_Class_Code: 1
Lidar_LAS_Class_Description: Undetermined/Unclassified
Lidar_LAS_Classification:
Lidar_LAS_Class_Code: 2
Lidar_LAS_Class_Description: Bare-earth
Lidar_LAS_Classification:
Lidar_LAS_Class_Code: 7
Lidar_LAS_Class_Description: All noise
Lidar_LAS_Classification:
Lidar_LAS_Class_Code: 9
Lidar_LAS_Class_Description: Water
Lidar_LAS_Classification:
Lidar_LAS_Class_Code: 10
Lidar_LAS_Class_Description: Ignored ground
Lidar_LAS_Classification:
Lidar_LAS_Class_Code: 15
Lidar_LAS_Class_Description: Bridge
Purpose:
The purpose of these LiDAR data is to produce a high accuracy models of the Naches and Yakima Rivers for Rogers Surveying, Inc. in accordance with requirements outlined in the Task Order Agreement. Rogers Surveying Inc. requires the LiDAR data to aid in analysis of Yakima County’s hydraulic and geomorphic investigation of region.
The raw LiDAR point cloud data is used to create surface models as requested; classified LiDAR LAS files, XYZ files, bare-earth Digital Elevation Models (DEM), Intensity raster of first return, First return DEMs, breaklines shapefiles, one foot contours and two foot contours.
Supplemental_Information:
Task Order number: W912EF-12-D-0007 EC04
U.S. Army Corps of Engineers, Seattle District
Rodgers Surveying, Inc.
Quantum Spatial, Inc.
Time_Period_of_Content:
Time_Period_Information:
Multiple_Dates/Times:
Single_Date/Time:
Calendar_Date: 20131114
Single_Date/Time:
Calendar_Date: 20131115
Single_Date/Time:
Calendar_Date: 20131119
Single_Date/Time:
Calendar_Date: 20131120
Single_Date/Time:
Calendar_Date: 20140131
Currentness_Reference: ground condition
Status:
Progress: complete
Maintenance_and_Update_Frequency: unknown
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -120.789
East_Bounding_Coordinate: -120.434
North_Bounding_Coordinate: 46.750
South_Bounding_Coordinate: 46.500
Keywords:
Theme:
Theme_Keyword_Thesaurus: None
Theme_Keyword: Elevation data
Theme_Keyword: LiDAR
Theme_Keyword: LAS
Theme_Keyword: Bare Earth
Theme_Keyword: First Return
Theme_Keyword: DTM
Theme_Keyword: Breakline
Theme_Keyword: Contour
Theme_Keyword: Intensity Raster
Place:
Place_Keyword_Thesaurus: None
Place_Keyword: Washington
Place_Keyword: Yakima County
Place_Keyword: Naches
Place_Keyword: Yakima
Place_Keyword: Union Gap
Place_Keyword: Parker
Access_Constraints: No restrictions apply to accessing 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.
Point_of_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Quantum Spatial, Inc.
Contact_Person: Chris Guy
Contact_Address:
Address_Type: mailing and physical
Address: 4020 Technology Parkway
City: Sheboygan
State_or_Province: WI
Postal_Code: 53083
Country: USA
Contact_Voice_Telephone: 920-457-3631
Contact_Facsimile_Telephone: 920-457-0410
Contact_Electronic_Mail_Address: cguy@quantumspatial.com
Hours_of_Service: Monday through Friday 8:00 AM to 4:00 PM (Central Time)
Native_Data_Set_Environment:
ALS Post Processor 2.75 Build#25; GeoCue Version 13.1.45.1; Windows XP Operating System

Data_Quality_Information:
Logical_Consistency_Report: Data cover the entire area specified for this project.
Completeness_Report:
These data files include all data points collected. No points have been removed or excluded. The raw point cloud is of good quality and data passes Fundamental Vertical Accuracy specifications.
Positional_Accuracy:
Vertical_Positional_Accuracy:
Vertical_Positional_Accuracy_Report:
Project specifications require that vertical accuracy, as RMSE, of LiDAR data be less than 0.090 meters in open terrain. Vertical accuracy is determined by comparison of LiDAR data and ground survey point elevations. Differences are calculated to establish an RSME.
Quantitative_Vertical_Positional_Accuracy_Assessment:
Vertical_Positional_Accuracy_Value: 0.0686 meters RSME
Vertical_Positional_Accuracy_Explanation:
The RMSE was tested using ground survey points provided by Rogers Surveying. The check points were compared to a TIN surface of LiDAR points. Differences in elevations are calculated to determine an RSME. The vertical accuracy meets the requirement of RMSE less than 0.09 meters.
Lineage:
Source_Information:
Source_Citation:
Citation_Information:
Originator: Rogers Surveying, Inc
Publication_Date: 201311
Title: Ground Survey Control, Naches River, WA
Geospatial_Data_Presentation_Form: vector digital data and tabular data
Publication_Information:
Publication_Place: Rogers Surveying, Inc.
Publisher: Rogers Surveying, Inc.
Other_Citation_Details: None
Online_Linkage: none
Type_of_Source_Media: disk
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 201311
Source_Currentness_Reference: ground condition
Source_Citation_Abbreviation: Rogers_lidar_gnd_survey
Source_Contribution:
This data source is used (along with the airborne GPS/IMU data) to index the LiDAR point cloud data. Additional survey data may be used to assess vertical accuracy of LiDAR point data or models derived form LiDAR point data.
Source_Information:
Source_Citation:
Citation_Information:
Originator: Quantum Spatial, Inc.
Publication_Date: 20140210
Title: LiDAR Acquisition Naches River, WA
Geospatial_Data_Presentation_Form: point cloud
Publication_Information:
Publication_Place: Quantum Spatial, Inc.
Publisher: Quantum Spatial, Inc.
Other_Citation_Details: None
Online_Linkage: none
Type_of_Source_Media: disk
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 20131120
Source_Currentness_Reference: ground condition
Source_Citation_Abbreviation: QSI_LiDAR_Acquire
Source_Contribution:
This data source is used to acquire and record airborne LiDAR point set and GPS and IMU data.
Source_Information:
Source_Citation:
Citation_Information:
Originator: Quantum Spatial, Inc.
Publication_Date: 20140210
Title: Lidar Processing, Naches River, WA
Geospatial_Data_Presentation_Form: point cloud
Publication_Information:
Publication_Place: Quantum Spatial, Inc.
Publisher: Quantum Spatial, Inc.
Other_Citation_Details: None
Online_Linkage: none
Type_of_Source_Media: disk
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 201401
Source_Currentness_Reference: ground condition
Source_Citation_Abbreviation: QSI_Lidar_Proc_Class
Source_Contribution:
This data source is to process the LiDAR data set; indexing, classification, producing hydro breaklines and producing requested surface models.
Process_Step:
Process_Description:
Ground based survey points were collected to be compared as check points with airborne data points. These measurements were recorded and provided to Quantum Spatial for use in establishment of the LiDAR data set to ground elevations (indexing). Additional ground survey points may be made to provide for vertical accuracy assessment of LiDAR data or derivative models.
Source_Used_Citation_Abbreviation: Rogers_lidar_gnd_survey
Process_Date: 201311
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Rogers Surveying, Inc.
Contact_Person: John Baalman
Contact_Address:
Address_Type: mailing and physical
Address: 1455 Columbia Park Trail Suite 201
City: Richland
State_or_Province: WA
Postal_Code: 99352
Country: USA
Contact_Voice_Telephone: 509-783-4141
Contact_Electronic_Mail_Address: jbaalman@rogerssurveying.com
Hours_of_Service: Monday through Friday 8:00 AM to 4:00 PM (PST)
Process_Step:
Process_Description:
Airborne LiDAR collection survey is conducted using fixed wing aircraft equipped with a LiDAR scanning system following specifications of the flight plan. The system includes a differential GPS unit and inertial measurement system that provide data to aide in assembly of single best estimate trajectory files.
Additional specifications for scanning laser rangefinder, GPS and IMU: See accompanying document:
ALS60_ProductSpecs_en.pdf
Nominal on-ground beam diameter: 0.21 meters 1/e2 Minimum separation between detected returns from a single pulse: 3.5 meters Laser output power: Confidential per the manufacturer Minimum return power to produce a return: Confidential per the manufacturer Frequency of GPS sampling: 1 Hz Frquency of IMU sampling: 200 Hz Nominal single-swath pulse density: 0.5 meters Nominal aggregate pulse density: 4.06 /square meter Identity of reference survey monuments:
Name and coordinates:
SB1118 SELAH RESET N463748.698 W1203308.435
SB1069 CLUB N463542.564 W1202554.448
Nature of vertical control: RTK Trimble, TRM57971, ARP Height 1.616 meters
Source_Used_Citation_Abbreviation: QSI_LiDAR_Acquire
Process_Date: 20131120
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Quantum Spatial, Inc.
Contact_Person: Chris Guy
Contact_Address:
Address_Type: mailing and physical
Address: 4020 Technology Parkway
City: Sheboygan
State_or_Province: WI
Postal_Code: 53083
Country: USA
Contact_Voice_Telephone: 1-920-457-3631
Contact_Facsimile_Telephone: 1-920-457-0410
Contact_Electronic_Mail_Address: cguy@quantumspatial.com
Hours_of_Service: Monday through Friday 8:00 AM to 4:00 PM (Central Time)
Process_Step:
Process_Description:
Collected data alignment is established per flightline resolving for aircraft attitude and position utilizing in-flight GPS and IMU data. Swath data is saved in LAS format where points are differentiated by discreet time, position, return value, intensity, etc. Relative accuracy of swath strips is checked. Data is arranged into a tile layout and point classification routines are accomplished. Classified points are inspected, manually reclassed where necessary and breaklines added. Derivative data products and quality assessments are produced.
1. Automatic surface 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.
2. Each tile is reviewed for accuracy and consistency of the macro ground classification.
3. As automatic processing and the testing of LiDAR is complete technicians review the generated bare-earth surface data to ensure that proper classification was achieved as part of a Quality Control process. Point classification follows the standard established by The American Society for Photogrammetry and Remote Sensing (ASPRS) for LAS data:
Code 1 Processed, but unclassified / non-ground
Code 2 Bare Earth / Ground
Code 7 Noise / Low Points
Code 9 Water
Code 10 Ignored Ground (Breakline proximity)
Code 15 Withheld
4. Linework is created of water bodies and drainage. A routine is used to drape line work following monotonic elevation change of drainage.
5. LAS data and breaklines are processed to derive various surface model types.
6. Bare earth DEM files are generated from classified LAS data and output as hydro flattened models according to the tile layout scheme.
Using LP360 the DEMs are generated in an ASCII format on a per tile basis with neighboring tile information available to minimize seams between tiles and with hydro breaklines in place to delineate surface water. These DEM are reviewed using GlobalMapper for adherence and completeness to the data and tile layout used during the creation process.
The DEMs are converted to ESRI Grid format and checked in ArcMap.
7. First Return DEM files are generated from first return information of point data.
Using LP360 the DEMs are generated in an ASCII format on a per tile basis, reviewed using GlobalMapper for adherence and completeness to the data and tile layout used during the creation process, then converted to ESRI Grid format and checked in ArcMap.
8. Intensity raster First Return DEM files are generated from only the first return record of the LAS points. They are saved as geo-tiff grayscale files on a per tile basis.
9. One and two foot contours are produced from a set of ground points which are thinned to reduce "noise" and used as Contour Key points. Hydro breaklines and a boundary are included.
Contours are generated on one foot intervals and on two foot intervals then output to ESRI shapefiles.
Source_Used_Citation_Abbreviation: QSI_Lidar_Proc_Class
Process_Date: 201401
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Quantum Spatial, Inc.
Contact_Person: Chris Guy
Contact_Address:
Address_Type: mailing and physical
Address: 4020 Technology Parkway
City: Sheboygan
State_or_Province: WI
Postal_Code: 53083
Country: USA
Contact_Voice_Telephone: 1-920-457-3631
Contact_Facsimile_Telephone: 1-920-457-0410
Contact_Electronic_Mail_Address: cguy@quantumspatial.com
Hours_of_Service: Monday through Friday 8:00 AM to 4:00 PM (Central Time)

Spatial_Data_Organization_Information:
Indirect_Spatial_Reference:
Bare Earth ASCII files and Classified LAS files are on a per tile basis following the 1/100th USGS 7.5 minute quadrangle
Bare Earth Digital Elevation Models (DEM), First Return Models (DEM), one foot and two foot contour ESRI shapefiles and Intensity raster images are on a per tile basis following the 1/4th USGS 7.5 minute quadrangle
Direct_Spatial_Reference_Method: Point
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: 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: 4602
Lambert_Conformal_Conic:
Standard_Parallel: 45.83333
Longitude_of_Central_Meridian: 120.5
Latitude_of_Projection_Origin: 45.33333
False_Easting: 1640416.66666
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: survey feet
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
Altitude_Resolution: 0.01
Altitude_Distance_Units: survey feet
Altitude_Encoding_Method:
Explicit elevation coordinate included with horizontal coordinates

Distribution_Information:
Distributor:
Contact_Information:
Contact_Person_Primary:
Contact_Person: John Baalman
Contact_Organization: Rogers Surveying, Inc.
Contact_Position: unknown
Contact_Address:
Address_Type: mailing and physical address
Address: 1455 Columbia Park Trail
City: Richland
State_or_Province: WA
Postal_Code: 99352
Country: USA
Contact_Voice_Telephone: 509-783-4141
Contact_Electronic_Mail_Address: jbaalman@rogerssurveying.com
Resource_Description:
Distribution of this data is the discretion Olsson Associates, Inc. or the U.S. Army Corps of Engineers.
Distribution_Liability:
In no event shall the creators, custodians, or distributors of these data be liable for any damages arising out of its use, or from the inability of the customer to use these data for their intended application.

Metadata_Reference_Information:
Metadata_Date: 20140207
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Quantum Spatial, Inc.
Contact_Person: Chris Guy
Contact_Address:
Address_Type: mailing and physical
Address: 4020 Technology Parkway
City: Sheboygan
State_or_Province: WI
Postal_Code: 53083
Country: USA
Contact_Voice_Telephone: 1-920-457-3631
Contact_Facsimile_Telephone: 1-920-457-0410
Contact_Electronic_Mail_Address: cguy@quantumspatial.com
Hours_of_Service: Monday through Friday 8:00 AM to 4:00 PM (Central 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

Generated by mp version 2.9.26 on Mon Feb 10 06:06:20 2014