Minnesota Metro Region LiDAR Acquisition (8pts/m^2 for the Greater Minneapolis Area and Maple Grove)
Metadata also available as
Metadata:
- Identification_Information
- Data_Quality_Information
- Spatial_Reference_Information
- Entity_and_Attribute_Information
- Distribution_Information
- Metadata_Reference_Information
- Identification_Information:
-
- Citation:
-
- Citation_Information:
-
- Originator: Minnesota Department of Natural Resources
- Publication_Date: 20120000
- Title:
- Minnesota Metro Region LiDAR Acquisition (8pts/m^2 for the Greater Minneapolis Area and Maple Grove)
- Geospatial_Data_Presentation_Form: remote-sensing image
- Publication_Information:
-
- Publication_Place: Minnesota Department of Natural Resources
- Publisher: Minnesota Department of Natural Resources
- Online_Linkage: <http://www.dnr.state.mn.us/index.html>
- Description:
-
- Abstract:
- Fugro Horizons collected LiDAR with the FLI-MAP sensor for the Greater Minneapolis area and the city of Maple Grove. The LiDAR sensor settings included acquisition at 2,100' AMT, 130 knots, 60% sidelap, 200kHz, 60% degree field of View, 2,424ft swath to attain an approximate 8 points per square meter. This sensor was also equipped with an inertial measuring unit (IMU) and a dual frequency airborne GPS receiver. These settings were used to meet or exceed the following accuracy specification in flat areas with minimal egetation 17.64cm ACCz 95% (9.0cm RMSEz) 24.5cm ACCz 95% (12.5cm RMSEz) 24.5cm ACCz 95% (12.5cm RMSEz) Deliverables for the LiDAR are in UTM15N NAD83/HARN NAVD88 Geiod09 meters *******DELIVERABLE OVERVIEW***** Each geodatabase is named for its respective USGS quarter-quarter quad name. Every geodatabase contains a feature dataset called "terrain_data". The terrain_data feature dataset contains up to two feature classes; Bare_Earth_Points and Hydro_Breaklines (when applicable). The Bare-Earth_Points feature class is comprised of MultipointZ shapefiles extracted from the Ground and KeyPoint LAS files. Both the Bare_Earth_Points and Hydro-Breaklines have been clipped to the USGS quarter-quarter quad extent. Each geodatabase also contains a DEM. The DEM was created from a terrain using Bare-Earth multipoint PointZ and hydro-breaklines. The Terrain was then converted to a Raster DEM using a 1-meter cell-size, then clipped to an adjusted, quarter-quarter quad minimum-bounding- rectangle and buffered an additional 50 meters. The naming convention for all DEMs is "DEM01". LAS files are clipped to the provided USGS quarter-quarter quad. 1 - unclassified 2 - ground 3 - low veg 4 - med. veg 5 - high veg 6 - building 7 - noise 8 - keypoint 9 - water 10 - water edge (withheld / ignored ground) 11 - Scan edge (unreliable points near the extreme edge of swath) 12 - Overlap (NOT USED) 14 - bridge Water edges were created using proprietary processes to create an accurate 3D representation of water features. Further hands-on evaluations are performed to ensure compliance with USGS V13 regarding Hydro-Flattening. Once the waterbodies are finalized, LAS bare-earth points within the extents of the water polygons are classified to Class 9 (Water). Bare-earth points within 1-meter of the water polygons are re-classified to Class 10 (Ignored Class). ACQUISITION DATES LiDAR Block MN-SP - 11-2-11 to 11-11-11 LiDAR Block Maple Grove 11-11-2011
- Purpose:
- The mission of the Minnesota Department of Natural Resources (DNR) is to work with citizens to conserve and manage the state's natural resources, to provide outdoor recreation opportunities, and to provide for commercial uses of natural resources in a way that creates a sustainable quality of life. One of the products of this effort is 1.5m average post spacing LiDAR and its derivatives.
- Supplemental_Information:
- The Minnesota Department of Natural Resources works to integrate and sustain the interdependent values of a healthy environment, a sustainable economy, and livable communities. DNR’s integrated resource management strategy shares stewardship responsibility with citizens and partners to manage for multiple interests. DNR protects the state’s natural heritage by conserving the diversity of natural lands, waters, and fish and wildlife that provide the foundation for Minnesota’s recreational and natural resource-based economy (M.S. 84, M.S. 97A). DNR manages natural lands such as forests, wetlands, and native prairies; maintains healthy populations of fish and wildlife; and protects rare plant and animal communities throughout the state. DNR manages the state’s water resources, sustaining healthy waterways and ground water resources. DNR provides access to enrich public outdoor recreational opportunities, such as hunting, fishing, wildlife-watching, camping, skiing, hiking, biking, motorized recreation, and conservation education through a state outdoor recreation system that includes parks, trails, wildlife management areas, scientific and natural areas, water trails, and other facilities (M.S. 86A). DNR supports natural resource-based economies, managing state forest lands for multiple forest values (M.S. 89), ensuring the maximum long-term economic return from school trust lands (M.S. 127A), and providing other economic opportunities in a manner consistent with sound natural resource conservation and management principles.
- Time_Period_of_Content:
-
- Time_Period_Information:
-
- Range_of_Dates/Times:
-
- Beginning_Date: 20111102
- Ending_Date: 20111115
- Currentness_Reference: Publication Date
- Status:
-
- Progress: Complete
- Maintenance_and_Update_Frequency: Irregular
- Spatial_Domain:
-
- Bounding_Coordinates:
-
- West_Bounding_Coordinate: +094.714600
- East_Bounding_Coordinate: +092.120234
- North_Bounding_Coordinate: +46.395540
- South_Bounding_Coordinate: +44.211950
- Keywords:
-
- Theme:
-
- Theme_Keyword_Thesaurus: None
- Theme_Keyword: LiDAR Acquisition
- Theme_Keyword: LiDAR
- Theme_Keyword: Minnesota Metro Region LiDAR Acquisition
- Theme_Keyword: Minnesota Department of Natural Resources
- Theme_Keyword: LiDAR 8pts/m^2
- Place:
-
- Place_Keyword_Thesaurus: Geographic Names Information System
- Place_Keyword: Minnesota
- Place_Keyword: MN
- Place_Keyword: Greater Minneapolis Area
- Place_Keyword: Maple Grove
- Access_Constraints: There are no limitations for access.
- Use_Constraints:
- None other than Minnesota Department of Natural Resources and supporting partners ask to be credited in any derived products or services.
- Point_of_Contact:
-
- Contact_Information:
-
- Contact_Organization_Primary:
-
- Contact_Organization: Minnesota Department of Natural Resources
- Contact_Address:
-
- Address_Type: mailing and physical address
- Address:
- DNR Central Office 500 Lafayette Road
- City: St. Paul
- State_or_Province: MN
- Postal_Code: 55155-4040
- Country: USA
- Contact_Voice_Telephone: (651) 296-6157
- Contact_TDD/TTY_Telephone: (651) 296-5484
- Contact_Electronic_Mail_Address: info.dnr@state.mn.us
- Hours_of_Service: 8am to 5pm Central Time
- Contact_Instructions: <http://www.dnr.state.mn.us/index.html>
- Browse_Graphic:
-
- Browse_Graphic_File_Name: None
- Browse_Graphic_File_Description: None
- Browse_Graphic_File_Type: None
- Data_Quality_Information:
-
- Attribute_Accuracy:
-
- Attribute_Accuracy_Report:
- 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 and in project area, were combined to yield a single fixed integer phase differential solution of the aircraft trajectory. The differences between the forward to reverse solution within the project area were within project specifications, indicating a valid and accurate solution. An IMU was used to record precise changes in position and orientation of the LIDAR scanner at a rate of 200 Hz. All IMU data was processed post flight with a filter to integrate inertial measurements and precise phase differential GPS positions. The resulting solution contains geodetic position, omega, phi, kappa, and time for subsequent merging with the laser ranging information.
- Logical_Consistency_Report:
- All deliverables were quality checked by MN DNR and passed.
- Completeness_Report: Complete
- Positional_Accuracy:
-
- Horizontal_Positional_Accuracy:
-
- Horizontal_Positional_Accuracy_Report: Meets or exceeds horizontal accuracy of 0.6m RMSE.
- Vertical_Positional_Accuracy:
-
- Vertical_Positional_Accuracy_Report:
- Vertical Accuracy of the lidar data will be assessed and reported in accordance with the guidelines developed by the NDEP and subsequently adopted by the ASPRS. The complete guidelines may be found in Section 1.5 of the //www.ndep.gov/NDEP_Elevation_Guidelines_Ver1_ 10May2004.pdf Vertical accuracy requirements using the NDEP/ASPRS 17.64cm ACCz 95% (9.0cm RMSEz) 24.5cm ACCz 95% (12.5cm RMSEz) 24.5cm ACCz 95% (12.5cm RMSEz)
- Lineage:
-
- Source_Information:
-
- Source_Citation:
-
- Citation_Information:
-
- Originator: Minnesota Department of Natural Resources
- Publication_Date: 20120000
- Publication_Time: Unknown
- Title: <http://www.dnr.state.mn.us/>
- Geospatial_Data_Presentation_Form: remote-sensing image
- Online_Linkage: <http://www.dnr.state.mn.us/>
- Type_of_Source_Media: Digital copy
- Source_Time_Period_of_Content:
-
- Time_Period_Information:
-
- Range_of_Dates/Times:
-
- Beginning_Date: 20111102
- Ending_Date: 20111115
- Source_Currentness_Reference: Publication Date
- Source_Citation_Abbreviation: Georectifed LiDAR data sets
- Source_Contribution: Digital Georectifed LiDAR.
- Process_Step:
-
- Process_Description:
- The data set for each flight line was checked for project area coverage, data gaps between overlapping flight lines, and tension/compression areas (areas where data points are more or less dense that the average project specified post spacing). Using an iterative process that involves analyzing raster difference calculations the omega, phi, kappa angle corrections for the LiDAR instrument were determined. Corrections were applied to the LiDAR data set. Extensive comparisons were made of vertical and horizontal positional differences between points common to two or more LiDAR flight lines. An intensity raster for each flight line was generated and verified that intensity was recorded for each LiDAR point. LiDAR ground points were compared to independently surveyed and positioned ground control points in the project area. Based on the results of these comparisons, the LiDAR data was vertically biased to the ground. (1) PRE-PROCESSING STAGE LiDAR, GPS and IMU data are processed together using LiDAR processing software. The LiDAR data set for each flight line is checked for project area coverage and LiDAR post spacing is checked to ensure it meets project specifications. The LiDAR collected at the calibration area is used to correct the rotational, atmospheric, and vertical elevation differences that are inherent to LiDAR data. Intensity raster is generated to verify that intensity was recorded for each LiDAR point. LiDAR data is transformed to the specified project coordinate system. By utilizing the ground survey data collected at the calibration site and project area, the LiDAR data is vertically biased to the ground. Comparisons between the biased LiDAR data and ground survey data within the project area are evaluated and a final RMSE value is generated to ensure the data meets project specifications.
- Process_Date: 20110000
- Spatial_Reference_Information:
-
- Horizontal_Coordinate_System_Definition:
-
- Planar:
-
- Grid_Coordinate_System:
-
- Grid_Coordinate_System_Name: Universal Transverse Mercator
- Universal_Transverse_Mercator:
-
- UTM_Zone_Number: 15
- Transverse_Mercator:
-
- Scale_Factor_at_Central_Meridian: 0.9996
- Longitude_of_Central_Meridian: +093.000000
- Latitude_of_Projection_Origin: 0.0
- False_Easting: 500000
- False_Northing: 0.0
- Planar_Coordinate_Information:
-
- Planar_Coordinate_Encoding_Method: row and column
- Coordinate_Representation:
-
- Abscissa_Resolution: .001
- Ordinate_Resolution: .001
- Planar_Distance_Units: Meters
- Geodetic_Model:
-
- Horizontal_Datum_Name: North American Datum of 1983/HARN adjustment
- Ellipsoid_Name: Geodetic Reference System 80 (GRS 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 Geoid09
- Altitude_Resolution: .001
- Altitude_Distance_Units: Meters
- Altitude_Encoding_Method: Implicit coordinate
- Depth_System_Definition:
-
- Depth_Datum_Name: No correction
- Depth_Resolution: .001
- Depth_Distance_Units: Meters
- Depth_Encoding_Method: Implicit coordinate
- Entity_and_Attribute_Information:
-
- Overview_Description:
-
- Entity_and_Attribute_Overview:
- 8pts/m^2 LiDAR post spacing acquisition and processing for Minnesota Department of Natural Resources and supporting partners.
- Entity_and_Attribute_Detail_Citation: None
- Distribution_Information:
-
- Distributor:
-
- Contact_Information:
-
- Contact_Organization_Primary:
-
- Contact_Organization: TBD
- Contact_Address:
-
- Address_Type: mailing and physical address
- Address: TBD
- City: TBD
- State_or_Province: TBD
- Postal_Code: TBD
- Country: USA
- Contact_Voice_Telephone: TBD
- Hours_of_Service: 8am to 5pm Central Time
- Contact_Instructions: TBD
- Distribution_Liability:
- In no event shall the creators, custodians, or distributors of this information be liable for any damages arising out of its use (or the inability to use it).
- Metadata_Reference_Information:
-
- Metadata_Date: 20120000
- Metadata_Contact:
-
- Contact_Information:
-
- Contact_Organization_Primary:
-
- Contact_Organization: Minnesota Department of Natural Resources
- Contact_Address:
-
- Address_Type: mailing and physical address
- Address:
- DNR Central Office 500 Lafayette Road
- City: St. Paul
- State_or_Province: MN
- Postal_Code: 55155-4040
- Country: USA
- Contact_Voice_Telephone: (651) 296-6157
- Contact_TDD/TTY_Telephone: (651) 296-5484
- Hours_of_Service: 8am to 5pm Central Time
- Contact_Instructions: info.dnr@state.mn.us
- Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata
- Metadata_Standard_Version: FGDC-STD-001-1998
Generated by mp version 2.9.0 on Tue Feb 12 15:24:34 2013