49800
2010 USGS Lidar: Southeastern Michigan (Hillsdale, Jackson, Lenawee Counties)
mi2010_usgs_southeastern_m3692_metadata
Data Set
Published / External
49401
Lidar - partner (no harvest)
Project
Completed
2011-02-04
TASK NAME: Lake Erie LiDAR Priority Area 1
LiDAR Data Acquisition and Processing Production Task- Jackson, Hillsdale, and Lenawee Counties
USGS Contract No. G10PC00057
Task Order No: G10PD02054
Woolpert ORDER NUMBER: 70398
CONTRACTOR: Woolpert, Inc.
LiDAR data is a remotely sensed high resolution elevation data collected by an airborne platform. The LiDAR sensor uses a combination of laser range finding, GPS positioning, and inertial measurment technologies. The LiDAR systems collect data point clouds that are used to produce highly detailed Digital Elevation Models (DEMs) of the earth's terrain, man-made structures, and vegetation. The task required the LiDAR data to be collected at a resolution of 0.44 points per square meter (PPSM). The final products include first, last, and at least one intermediate return LAS, full classified LAS and a bare earth model in separate files.
This task order consisted of LiDAR data acquisition and processing for Jackson, Hillsdale, and Lenawee Counties in southeastern Michigan. The task order area of interest encompasses approximately 2,093 square miles. The task required the LiDAR data to be collected at a resolution of 0.44 points per square meter (PPSM). The LiDAR data was collected to meet a vertical accuracy requirement of 15.0 cm (0.49 ft) RMSE, or better, so that when combined with breaklines, the data adequately supports the generation of two (2) foot FEMA compliant contours. The final LiDAR data was delivered as 1,500m x 1,500m tiles, aligned to even 1,500m coordinates.
10445
A footprint of this data set may be viewed in Google Earth at:
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/3692/supplemental/mi2010_usgs_southeastern_m3692.kmz
A report for this dataset is available at:
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/3692/supplemental/mi2010_usgs_southeastern_m3692_surveyreport.pdf
Theme
ISO 19115 Topic Category
elevation
Theme
Great Lakes
Theme
USGS
Temporal
2010
Temporal
November
Office for Coastal Management
Charleston
SC
Data Set
As Needed
Map (digital)
Lidar points in LAZ format (Classes 1,2,6,7,9,10,12)
none
Any conclusions drawn from the analysis of this information are not the responsibility of USGS, NOAA, the Office for Coastal Management or its partners.
Data Steward
2011-02-04
Organization
NOAA Office for Coastal Management
NOAA/OCM
coastal.info@noaa.gov
2234 South Hobson Ave
Charleston
SC
29405-2413
(843) 740-1202
https://coast.noaa.gov
NOAA Office for Coastal Management Home Page
Online Resource
Distributor
2011-02-04
Organization
NOAA Office for Coastal Management
NOAA/OCM
coastal.info@noaa.gov
2234 South Hobson Ave
Charleston
SC
29405-2413
(843) 740-1202
https://coast.noaa.gov
NOAA Office for Coastal Management Home Page
Online Resource
Metadata Contact
2011-02-04
Organization
NOAA Office for Coastal Management
NOAA/OCM
coastal.info@noaa.gov
2234 South Hobson Ave
Charleston
SC
29405-2413
(843) 740-1202
https://coast.noaa.gov
NOAA Office for Coastal Management Home Page
Online Resource
Point of Contact
2011-02-04
Organization
NOAA Office for Coastal Management
NOAA/OCM
coastal.info@noaa.gov
2234 South Hobson Ave
Charleston
SC
29405-2413
(843) 740-1202
https://coast.noaa.gov
NOAA Office for Coastal Management Home Page
Online Resource
Ground Condition
-84.836293
-83.750877
42.430187
41.683064
Discrete
2010-11-19
Discrete
2010-11-20
Discrete
2010-11-20
Discrete
2010-11-28
Discrete
2010-11-28
Yes
3
Point
No
Row
500
Column
500
Vertical
1
Unclassified
This data can be obtained on-line at the following URL:
https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=3692;
None
Users should be aware that temporal changes may have occurred since this data set was collected and some parts of this data may no longer represent actual surface conditions. Users should not use this data for critical applications without a full awareness of its limitations. These data depict the heights at the time of the survey and are only accurate for that time.
https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=3692
Customized Download
Create custom data files by choosing data area, product type, map projection, file format, datum, etc.
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/3692/index.html
Bulk Download
Simple download of data files.
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/3692/supplemental/mi2010_usgs_southeastern_m3692.kmz
Browse Graphic
Browse Graphic
kmz
This graphic shows the coverage of the 2012 USACE Lake Michigan lidar in Wisconsin and on the upper peninsula of Michigan.
https://coast.noaa.gov
Online Resource
https://coast.noaa.gov/dataviewer
Online Resource
2016-05-23
Date that the source FGDC record was last modified.
2017-11-14
Converted from FGDC Content Standards for Digital Geospatial Metadata (version FGDC-STD-001-1998) using 'fgdc_to_inport_xml.pl' script. Contact Tyler Christensen (NOS) for details.
2018-02-08
Partial upload of Positional Accuracy fields only.
2018-03-13
Partial upload to move data access links to Distribution Info.
The LiDAR collected for this task order was collected at a vertical accuracy of 15.0 cm (0.49 ft) Root Mean Squared (RMSE), or better, so that when combined with breaklines, it will adequately support the generation of two (2) foot FEMA compliant contours. | Quantitative Value: 15.0 cm (0.49 ft) RMSE | Quantitative Test Explanation: Points measured will produce an error less than 15.0 cm (0.49 ft) RMSE.
Horizontal accuracy is +/- 1.158 meters at the 95% confidence level using RMSE(r) x 1.9600 as defined by the FGDC Geospatial Positional Accuracy Standards, Part 3: NSSDA.; Quantitative Value: 1.158 meters, Test that produced the value: +/- 115.8 cm, 2 sigma
The LiDAR data vertical accuracy RMSE is 7.0 cm (0.22 ft).
The data collected under this Task Order meets the National Standard for Spatial Database Accuracy (NSSDA) accuracy standards. The NSSDA standards specify that vertical accuracy be reported at the 95 percent confidence level for data tested by an independent source of higher accuracy. (http://www.fgdc.gov/standards/projects/FGDC-standards-projects/accuracy/part3/index_html).
The Fundamental Vertical Accuracy (FVA) of the TIN: 13.72 cm (0.45 ft) at a 95% confidence level, derived according to NSSDA, i.e., based on RMSE of 18.5 cm in the "open terrain" land cover category.
; Quantitative Value: 0.07 meters, Test that produced the value: +/- 7 cm, 2 sigma
Cloud Cover: 0
The LIDAR data is visually inspected for completeness to ensure that are no gaps between flight lines.
All formatted data are validated using commercial GIS software to ensure proper formatting and loading prior to delivery.
1
Using a LH Systems ALS50 Light Detection And Ranging (LiDAR) system, 83 flight lines of high density data, one and one half point per square meter, were collected over Jackson, Hillsdale, and Lenawee counties in Michigan (approximately 2,093 square miles). Multiple returns were recorded for each laser pulse along with an intensity value for each return. A total of five missions were flown over a 3 day period: November 19, 2010, November 20, 2010, and November 28, 2010. A minimum of two airborne global positioning system (GPS) base stations were used in support of the LiDAR data acquisition. 28 ground control points were surveyed through static methods. The geoid used to reduce satellite derived elevations to orthometric heights was Geoid09. All data for the task order is referenced to UTM 16N for the area within its zone and UTM 17N for the area within its zone, NAD83, NAVD88, in meters. Data located in tiles along the UTM zone border was processed in both UTM 16N and UTM 17N. Airborne GPS data was differentially processed and integrated with the post processed IMU data to derive a smoothed best estimate of trajectory (SBET). The SBET was used to reduce the LiDAR slant range measurements to a raw reflective surface for each flight line. The coverage was classified to extract a bare earth digital elevation model (DEM) and separate last returns. In addition to the LAS deliverables, one layer of coverage were delivered in the ArcINFO ArcGrid binary format: bare-earth. System Parameters: - Type of Scanner = LH Systems ALS50 - Data Acquisition Height = 7,800-feet AGL - Scanner Field of View = 40 degrees - Scan Frequency = 35.3 Hertz - Pulse Repetition Rate - 99.0 Kilohertz - Aircraft Speed = 130 Knots - Swath Width = 5,678-feet - Number of Returns Per Pulse = Maximum of 4 - Distance Between Flight Lines = 3,943-feet
2011-02-04T00:00:00
2
The ALS50 calibration and system performance is verified on a periodic basis using Woolpert's calibration range. The calibration range consists of a large building and runway. The edges of the building and control points along the runway have been located using conventional survey methods. Inertial measurement unit (IMU) misalignment angles and horizontal accuracy are calculated by comparing the position of the building edges between opposing flight lines. The scanner scale factor and vertical accuracy is calculated through comparison of LiDAR data against control points along the runway. Field calibration is performed on all flight lines to refine the IMU misalignment angles. IMU misalignment angles are calculated from the relative displacement of features within the overlap region of adjacent (and opposing) flight lines. The raw LiDAR data is reduced using the refined misalignment angles.
2010-11-18T00:00:00
3
Once the data acquisition and GPS processing phases are complete, the LiDAR data was processed immediately to verify the coverage had no voids. The GPS and IMU data was post processed using differential and Kalman filter algorithms to derive a best estimate of trajectory. The quality of the solution was verified to be consistent with the accuracy requirements of the project.
2010-11-19T00:00:00
4
The individual flight lines were inspected to ensure the systematic and residual errors have been identified and removed. Then, the flight lines were compared to adjacent flight lines for any mismatches to obtain a homogenous coverage throughout the project area. The point cloud underwent a classification process to determine bare-earth points and non-ground points utilizing "first and only" as well as "last of many" LiDAR returns. This process determined bare-earth points (Class 2), Noise (Class 7), Water (Class 9) Ignored ground (Class 10) and unclassified data (Class 1). The bare-earth (Class 2 - Ground) LiDAR points underwent a manual QA/QC step to verify that artifacts have been removed from the bare-earth surface. The surveyed ground control points are used to perform the accuracy checks and statistical analysis of the LiDAR dataset.
2010-11-19T00:00:00
5
Breaklines defining lakes, greater than two acres, and double-line streams, wider than 30.5 meters (100 feet), were compiled using digital photogrammetric techniques as part of the hydrographic flattening process and provided as ESRI Polyline Z and Polygon Z shape files. Breaklines defining water bodies and streams were compiled for this task order. The breaklines were used to perform the hydrologic flattening of water bodies, and gradient hydrologic flattening of double line streams. Lakes, reservoirs and ponds, at a nominal minimum size of two (2) acres or greater, were compiled as closed polygons. The closed water bodies were collected at a constant elevation. Rivers and streams, at a nominal minimum width of 30.5 meters (100 feet), were compiled in the direction of flow with both sides of the stream maintaining an equal gradient elevation. The hydrologic flattening of the LiDAR data was performed for inclusion in the National Elevation Dataset (NED).
2011-02-04T00:00:00
6
The NOAA Office for Coastal Management (OCM) received the topographic files in LAS format from USACE. The files contained lidar easting, northing, elevation, intensity, return number, etc. The data was received in Geographic Coordinates (decimal degrees). OCM performed the following processing for data storage and Digital Coast provisioning purposes:
1. A datum shift was performed for all tiles found in UTM Zone 17N and shifted to UTM Zone 16N in order to eliminate duplicate points and tiles.
2014-09-16T00:00:00
gov.noaa.nmfs.inport:49800
Anne Ball
2017-11-15T15:22:23
SysAdmin InPortAdmin
2022-08-09T17:11:36
2022-03-16
OCM Partners
OCMP
1002
Public
No
2022-03-16
1 Year
2023-03-16