LiDAR Project for Tenmile and Fifteenmile Creeks, Idaho

Metadata:

• Identification_Information
• Data_Quality_Information
• Spatial_Reference_Information
• Entity_and_Attribute_Information
• Distribution_Information
• Metadata_Reference_Information

Identification_Information:

Citation:

Citation_Information:

Originator: Horizons, Inc.

Publication_Date: 20040528

Title: 10-15 Mile Creek, Idaho

Edition: One

Publication_Information:

Publication_Place: Boise, Idaho

Publisher: Bureau of Reclamation, Snake River Area Office

Other_Citation_Details: None

Online_Linkage: Unknown

Description:

Abstract:

Horizons, Inc. was contracted by Bureau of Reclamation Boise to provide detailed high-accuracy data for hydraulic analysis and soil classification projects by the Bureau and the NRCS. The project emcompassed an area of approximately 150 square miles. LiDAR acquisition was obtained on December 9, 2003 at 8000' AMT by subcontractor EarthData Aviation. The Navajo Chieftain (tail number N62912) was equipped with an LH System ALS40 LiDAR system including an inertial measuring unit (IMU) and a dual frequency airborne GPS receiver. LiDAR data was collected with a 2.0 to 2.2 meter nominal post spacing, 25 percent field of view and a 30 percent overlap. Ground control survey was conducted by subcontractor DJ&A of Missoula, MT. LiDAR data processing included processing of the raw LiDAR data through a minimum block algorithm to classify points as bare-earth or non-bare earth. Points were edited in 2D using imagery, intensity of the LiDAR reflection and tin-editing software to ensure accuracy of the automated feature classification. Final delivery included Acquisition/Processing Report, Flight Map, Raw LiDAR data, Intensity Image, Bare Earth DEM and First Return DEM.

Purpose:

The data will be used to provide high-accuracy data for hydraulic analysis and soil classification projects.

Supplemental_Information:

The raw LIDAR point files were delivered in a proprietary binary format along with an ASCII translator. The point files were delivered to the project boundary and tiled into approximately 1 million point files. Each point contained Ground X -- Easting or "X" value for each LIDAR point; Ground Y -- Northing or "Y" value for each LIDAR point; Ground Z -- Elevation or "Z" value for each LIDAR point; Plane X -- Easting or "X" value for the aircraft at the time the point was fired ;Plane Y -- Northing or "Y" value for the aircraft at the time the point was fired; Plane Z -- Elevation or "Z" value for the aircraft at the time the point was fired; GPS Time -- GPS Time that the pulse was received; Scan Angle -- Angle of the scanner mirror at the time the instrument was fired; Roll Angle -- Roll (Omega) angle of the aircraft at the time the instrument was fired; Pitch Angle -- Pitch (Phi) angle of the aircraft at the time the instrument was fired; Heading Angle -- Heading (Kappa) angle of the aircraft at the time the instrument was fired; Intensity -- Intensity of the reflective surface based on amount of pulse returned; AGC Value -- Automatic Gain Control setting (Iris opening value) based on intensity of past returns; Return Number -- Value for the sequence for which a return was detected from a single pulse; GPS Week -- GPS week designation for the time of data acquisition; Classification -- Description given to each point based on the surface that reflected the pulse; Point Layer -- Point layer further describes the relationship of returns within a single laser a point with a return number of (1) could be further classified as "First and Only" or "First of Many"; Geoid Height -- Elevation difference between the ellipsoid and geoid heights. First Return Digital Elevation A tin using the Raw first return LIDAR data was generated in ArcView. A First Return Digital Elevation Model was delivered in ESRI float grid format using a two A tin using the Surface Bare Earth LiDAR data was generated in Arc View. A Bare Earth Digital Elevation Model was delivered in ESRI float grid format using a two meter During LiDAR acquistion an 8 bit intensity or surface reflectivity value is collected for each LiDAR point with a value ranging from 0 to 255. An image of the reflectivity surface was produced by generating a raster grid over the raw first return points and giving each pixel a value equal to the average of the LIDAR point intensity values that fell within it. A nearest neighbor interpolation was performed to give empty cells intensity values. A geotiff format black and white image of the LIDAR reflective surface was the resultant product. All project deliverables were submitted in two coordinate systems – UTM and IDTM (specifics described above). The projection of the project boundary from UTM to IDTM (or vice versa) introduces a slight rotation. A tile layout for each projection system was developed to ensure tile layouts in a north-south and east-west format. Each tile was sized to be 4572 meters x Tiles were named the same in both projection systems but, due to the projection rotation, will not cover the same area within the project boundary and will not contain the same number of raw LIDAR points.)

Time_Period_of_Content:

Time_Period_Information:

Range_of_Dates/Times:

Beginning_Date: 20031209

Ending_Date: 20031209

Currentness_Reference: Ground Condition

Status:

Progress: Complete

Maintenance_and_Update_Frequency: None planned

Spatial_Domain:

Bounding_Coordinates:

West_Bounding_Coordinate: -116.60449

East_Bounding_Coordinate: -116.13135

North_Bounding_Coordinate: 43.71194

South_Bounding_Coordinate: 43.44582

Keywords:

Theme:

Theme_Keyword_Thesaurus: None

Theme_Keyword: LiDAR Acquisition

Theme_Keyword: Digital Elevation Model

Theme_Keyword: None

Place:

Place_Keyword_Thesaurus: None

Place_Keyword: 10-15 Mile Creek

Place_Keyword: Idaho

Access_Constraints: Unknown

Use_Constraints: Unknown

Point_of_Contact:

Contact_Information:

Contact_Organization_Primary:

Contact_Organization: Bureau of Reclamation, Snake River Area Office

Contact_Person: Donna Fornshell

Contact_Position: GIS Specialist

Contact_Address:

Address_Type: mailing and physical address

Address: 230 Collins Road

City: Boise

State_or_Province: Idaho

Postal_Code: 83702-4520

Country: United States

Contact_Voice_Telephone: 208-383-2214

Contact_Facsimile_Telephone: 208-383-2237

Contact_Electronic_Mail_Address: dfornshell@pn.usbr.gov

Hours_of_Service: Unknown

Native_Data_Set_Environment:

LiDAR acquisition was done by Earthdata Aviation, LiDAR data processing and DEM production was done by Horizons, Inc. personnel in Rapid City, South Dakota using proprietary software.

Data_Quality_Information:

Attribute_Accuracy:

Attribute_Accuracy_Report:

All GPS phase data was post processed with continuous kinematic survey techniques using "On the Fly" (OTF) integer ambiguity resolution. The GPS data was processed with forward and reverse processing algorithms. The results from each process, using the data collected at the airport, were combined to yield a single fixed integer phase differential solution of the aircraft trajectory. Plots of altitude and the forward and reverse GPS solution residuals are attached. In the portion of the flight over the project area, the small differences between the trajectories of the forward and reverse solutions (less than +/- 3 cm in the horizontal and less than +/- 5 cm in the vertical) indicate a valid solution with ambiguities correctly fixed to integer values. Extensive comparisons were made of vertical and horizontal positional differences between points common to two or more LiDAR flight lines. This was done for the airport bore-site testing area and the project area. All comparisons were found to be well within project specifications. Vertical Bias Correction. LiDAR ground points were compared to independently surveyed and positioned ground points at both the airport bore-sight area and the project area. Comparisons to the project control points as well as the airport points indicated a vertical bias of 41.5 cm. All LiDAR points were lowered by this amount. Comparisons to on-site control points yielded the following 09 December 2003 Vertical Accuracy 3.2 cm RMSE Standard Deviation 3.1 cm Mean Difference 1.2 cm Number of Points in Sample 11 The comparison with the kinematic survey at the airport 09 December 2003 Vertical Accuracy 5.9 cm RMSE Standard Deviation 3.4 cm Mean Difference 4.9 cm Number of Points in Sample 84

Logical_Consistency_Report: None

Completeness_Report: None

Positional_Accuracy:

Horizontal_Positional_Accuracy:

Horizontal_Positional_Accuracy_Report:

The estimated horizontal error for nadir and FOV edge is 0.23 meters.

Vertical_Positional_Accuracy:

Vertical_Positional_Accuracy_Report:

3.2cm Z - RMS

Lineage:

Source_Information:

Source_Citation:

Citation_Information:

Originator: Horizons, Inc.

Publication_Date: 20030528

Title: 10-15 Mile Creek, Idaho

Source_Scale_Denominator: 8000 amt

Type_of_Source_Media: none

Source_Time_Period_of_Content:

Time_Period_Information:

Range_of_Dates/Times:

Beginning_Date: 20031209

Ending_Date: 20031209

Source_Currentness_Reference: Ground Condition

Source_Citation_Abbreviation: None

Source_Contribution: None

Process_Step:

Process_Description:

AeroScan LiDAR timed reflection data and the IMU SBET files were processed together using LiDAR processing software. The data set for each flight line was checked for data gaps between overlapping flightlines, and tension/compression areas (areas where data points are more or less dense that the average project specified post spacing). LiDAR data was collected for bi- and cross- directional flight lines over an airport prior to acquisition of the project area. Comparative analysis of the data produced a preliminary omega,phi,kappa correction. LiDAR data was processed and evaluated until angles met project specifications. All flight lines (airport and project) were checked and verified for vertical accuracy of 15 cm. An intensity raster for each flight line was generated and verified that intensity was recorded for each LiDAR point. Static survey ground control points at the airport were compared to the LiDAR data set and the LiDAR data was vertically biased down to the ground. Lidar data in overlap areas of project flight lines was removed. The raw LiDAR data set was processed through a minimum block mean algorithm and points were classified as either bare earth or non-bare earth. User developed macros that factor mean terrain angle and height from the ground were used to determine bare earth point classification. A 2D edit (surfacing) process ensures the accuracy of the automated feature classification. Imagery, intensity of the LiDAR reflection and tin-editing software were combined to assess points.

Source_Used_Citation_Abbreviation: None

Process_Date: 20040609

Source_Produced_Citation_Abbreviation: None

Process_Contact:

Contact_Information:

Contact_Person_Primary:

Contact_Person: Mary Bosworth

Contact_Organization: Horizons Inc.

Contact_Position: Project Manager

Contact_Address:

Address_Type: mailing and physical address

Address: 3600 Jet Drive

City: Rapid City

State_or_Province: South Dakota

Postal_Code: 57703

Country: United States

Contact_Voice_Telephone: 605-343-0280

Contact_Facsimile_Telephone: 605-343-0305

Contact_Electronic_Mail_Address: bosworth@horizonsinc.com

Hours_of_Service: 8am-5pm Mountain Time

Spatial_Reference_Information:

Horizontal_Coordinate_System_Definition:

Planar:

Grid_Coordinate_System:

Grid_Coordinate_System_Name: Universal Transverse Mercator

Universal_Transverse_Mercator:

UTM_Zone_Number: 11

Transverse_Mercator:

Scale_Factor_at_Central_Meridian: 0.9996

Longitude_of_Central_Meridian: -116.000000

Latitude_of_Projection_Origin: +00.000000

False_Easting: 500000.0000

False_Northing: 0.0000

Planar_Coordinate_Information:

Planar_Coordinate_Encoding_Method: coordinate pair

Coordinate_Representation:

Abscissa_Resolution: 0.1

Ordinate_Resolution: 0.1

Planar_Distance_Units: Meters

Geodetic_Model:

Horizontal_Datum_Name: North American Datum of 1983

Ellipsoid_Name: GRS 80

Semi-major_Axis: 6378137.00000

Denominator_of_Flattening_Ratio: 298.26

Entity_and_Attribute_Information:

Overview_Description:

Entity_and_Attribute_Overview:

Raw Binary LIDAR Files (*.IBN). The raw LIDAR point files were delivered in a proprietary binary format along with an ASCII translator. The point files were delivered to the project boundary and tiled into approximately 1 million point files. Each point contained Ground X -- Easting or "X" value for each LIDAR point Ground Y -- Northing or "Y" value for each LIDAR point Ground Z -- Elevation or "Z" value for each LIDAR point Plane X -- Easting or "X" value for the aircraft at the time the point was fired Plane Y -- Northing or "Y" value for the aircraft at the time the point was fired Plane Z -- Elevation or "Z" value for the aircraft at the time the point was fired GPS Time -- GPS Time that the pulse was received Scan Angle -- Angle of the scanner mirror at the time the instrument was fired Roll Angle -- Roll (Omega) angle of the aircraft at the time the instrument was fired Pitch Angle -- Pitch (Phi) angle of the aircraft at the time the instrument was fired Heading Angle -- Heading (Kappa) angle of the aircraft at the time the instrument was fired Intensity -- Intensity of the reflective surface based on amount of pulse returned AGC Value -- Automatic Gain Control setting (Iris opening value) based on intensity of past returns Return Number -- Value for the sequence for which a return was detected from a single pulse GPS Week -- GPS week designation for the time of data acquisition Classification -- Description given to each point based on the surface that reflected the pulse Point Layer -- Point layer further describes the relationship a point with a return number of (1) could be further classified as "First and Only" or "First of Many" Geoid Height - Elevation difference between the ellipsoid and geoid heights First Return Digital Elevation Model. A tin using the Raw first return LIDAR data was generated in ArcView. A First Return Digital Elevation Model was delivered in ESRI float grid format using a two meter spacing. First Return Digital Elevation Model. A tin using the Surface Bare Earth LiDAR data was generated in Arc View. A Bare Earth Digital Elevation Model was delivered in ESRI float grid format using a two meter spacing. LIDAR Intensity Image. During LiDAR acquistion an 8 bit intensity or surface reflectivity value is collected for each LiDAR point with a value ranging from 0 to 255. An image of the reflectivity surface was produced by generating a raster grid over the raw first return points and giving each pixel a value equal to the average of the LIDAR point intensity values that fell within it. A nearest neighbor interpolation was performed to give empty cells intensity values. A geotiff format black and white image of the LIDAR reflective surface was the resultant product. Note Regarding Data Tiling. All project deliverables were submitted in two coordinate systems - UTM and IDTM (specifics described above). The projection of the project boundary from UTM to IDTM (or vice versa) introduces a slight rotation. A tile layout for each projection system was developed to ensure tile layouts in a north-south and east-west format. Each tile was sized to be 4572 meters x Tiles were named the same in both projection systems but, due to the projection rotation, will not cover the same area within the project boundary and will not contain the same number of raw LIDAR points.)

Entity_and_Attribute_Detail_Citation: None

Distribution_Information:

Distributor:

Contact_Information:

Contact_Organization_Primary:

Contact_Organization: Bureau of Reclamation, Snake River Area Office

Contact_Person: Donna Fornshell

Contact_Position: GIS Specialist

Contact_Address:

Address_Type: mailing and physical address

Address: 230 Collins Road

City: Boise

State_or_Province: Idaho

Postal_Code: 83702-4520

Country: United States

Contact_Voice_Telephone: 208-383-2214

Contact_Facsimile_Telephone: 208-383-2237

Contact_Electronic_Mail_Address: dfornshell@pn.usbr.gov

Hours_of_Service: Unknown

Resource_Description: 10-15 Mile Creek, Idaho

Distribution_Liability: Unknown

Metadata_Reference_Information:

Metadata_Date: 20030528

Metadata_Review_Date: 20030528

Metadata_Contact:

Contact_Information:

Contact_Organization_Primary:

Contact_Organization: Horizons, Inc.

Contact_Person: Mary Bosworth

Contact_Position: Project Manager

Contact_Address:

Address_Type: Mailing and physical address

Address: 3600 Jet Drive

City: Rapid City

State_or_Province: South Dakota

Postal_Code: 57703

Country: United States

Contact_Voice_Telephone: 605-343-0280

Contact_Facsimile_Telephone: 605-343-0305

Contact_Electronic_Mail_Address: bosworth@horizonsinc.com

Hours_of_Service: 8am-5pm Mountain Time

Metadata_Standard_Name: FGDC CSDGM

Metadata_Standard_Version: FGDC-STD-001-1998