2016 FEMA Lidar: Michigan - Part 1

This metadata supports the data entry in the NOAA Digital Coast Data Access Viewer (DAV). For this data set, the DAV is leveraging the Entwine Point Tiles (EPT) hosted by USGS on Amazon Web Services.

The State of Michigan (DTMB) contracted with Sanborn to provide LiDAR mapping services for 10 counties in the State of Michigan. These counties include Clare, Lake, Mecosta, Missaukee, Montcalm, Muskegon, Newaygo, Osceola, Roscommon, and Wexford. Utilizing multi-return systems, Light Detection and Ranging (LiDAR) data in the form of 3-dimensional positions of a dense set of mass points was collected for the 10 counties in April and May of 2016. LAS data products are suitable for 1 foot contour generation. USGS LiDAR Base Specification 1.2, QL2. 19.6 cm NVA.

Clare County: data covers approximately 575 square miles

Lake County: data covers approximately 573 square miles

Mecosta County: data covers approximately 571 square miles

Missaukee County: data covers approximately 574 square miles

Montcalm County: data covers approximately 721 square miles

Muskegon County: This county is available from a different data set, see the links in the URL section of this metadata record for the metadata and custom download.

Newaygo County: data covers approximately 826 square miles

Osceola County: data covers approximately 573 square miles

Roscommon County: data covers approximately 580 square miles

Wexford County: data covers approximately 575 square miles

The purpose of this data set is the acquisition and production of high resolution elevation data for the State of Michigan. This LiDAR operation was designed to create high resolution data sets that will establish an authoritative source for elevation information for the State of Michigan to create detailed surface elevation data for use in conservation planning, design, research, floodplain mapping, dam safety assessments, and hydrologic modeling.

Project Projection, Datums and Units. Projection - State Plane Michigan Central and South. Horizontal datum - North American Datum of 1983 (NAD83 (2011)). Vertical datum - North American Vertical Datum of 1988 (NAVD88) using the latest geoid (Geoid12a) for converting ellipsoidal heights to orthometric heights. Units - intl feet

The following are the USGS lidar fields in JSON:

{

"ldrinfo" : {

"ldrspec" : "USGS Base Specification 1.2, QL2 meeting 19.6cm NVA",

"ldrsens" : "Leica ALS70",

"ldrmaxnr" : "4",

"ldrnps" : "0.65",

"ldrdens" : "1.67",

"ldradens" : "2.2",

"ldranps" : "0.71",

"ldrfltht" : "2250",

"ldrfltsp" : "135",

"ldrscana" : "20",

"ldrscanr" : "64",

"ldrpulsr" : "167",

"ldrpulsd" : "10",

"ldrpulsw" : "3",

"ldrwavel" : "1064",

"ldrmpia" : "1",

"ldrbmdiv" : "0.3",

"ldrswatw" : "1222",

"ldrswato" : "30",

"ldrcrs" : "NAD_1983_2011_State_Plane_Michigan_Central_2112_Ft_Intl" and

"NAD_1983_2011_State_Plane_Michigan_South_2113_Ft_Intl",

"ldrgeoid" : "NGS Geoid12a"

},

"ldraccur" : {

"ldrchacc" : "0.196",

"rawnva" : "0.137",

"rawnvan" : "183",

"clsnva" : "0.156",

"clsnvan" : "183",

"clsvva" : "0.169",

"clsvvan" : "211"

},

"lasinfo" : {

"lasver" : "1.4",

"lasprf" : "6",

"laswheld" : "Withheld points were identified in these files with the withheld flag",

"lasolap" : "Overlap points were identified in these files with the overlap flag",

"lasintr" : "10",

"lasclass" : {

"clascode" : "1",

"clasitem" : "Unclassified"

},

"lasclass" : {

"clascode" : "2",

"clasitem" : "Bare earth"

},

"lasclass" : {

"clascode" : "7",

"clasitem" : "Noise"

},

"lasclass" : {

"clascode" : "9",

"clasitem" : "Water"

},

"lasclass" : {

"clascode" : "10",

"clasitem" : "Ignored Ground (Breakline Proximity)"

},

"lasclass" : {

"clascode" : "17",

"clasitem" : "Bridges"

},

"lasclass" : {

"clascode" : "18",

"clasitem" : "High Noise"

}

}}

USGS Base Specification 1.2, QL2 meeting 19.6 cm NVA

The State of Michigan Geographic Information Systems digital data have been tested and their documentation carefully reviewed. However, the State of Michigan and its representatives make no warranty or representation, either expressed or implied, with respect to the digital data and their documentation, their quality, performance, merchantability, or fitness for a particular purpose. The digital data are distributed on "as is" basis, and the user assumes all risk to their quality, the results obtained from their use, and the performance of the data. In no event will the State of Michigan or its representatives be liable for any direct, indirect, special, incidental or consequential damages resulting from and defect in the State of Michigan or in their documentation. This disclaimer of warranty is exclusive and in lieu of all others, oral or written, express or implied. No agent or employee is authorized to make any modification, extension, or addition to this warranty.

Any conclusions drawn from the analysis of this information are not the responsibility of NOAA, the Office for Coastal Management or its partners.

Data is available online for bulk and custom downloads.

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.

Microsoft Windows 7; ESRI ArcCatalog 9.3.1.1850

Horizontal positional accuracy for the 10 counties is dependent upon the quality of the GPS/INS solution, sensor calibration and ground conditions at the time of data capture. The standard system results for horizontal accuracy meet or exceed the project specified 1.0 meter RMSE. For the 10 counties, this value is computed by comparing ground control to a DEM derived from the classified LiDAR data and represents the RMSE of residuals on controls within the project area.

For the DEM data derived from the classified point cloud, the NVA and VVA were computed. The vertical accuracy was tested with independent survey check points located in various terrain types within the 10 counties. These check points were not used in the calibration or post processing of the lidar point cloud data. The survey check points were distributed throughout the block area. Specifications for this project require that the NVA be 19.6 cm or better @ 95 percent confidence level. The raw NVA was tested using 183 independent survey check points located in flat terrain types within the 10 counties. The survey checkpoints were distributed throughout the block area. The 183 independent check points were surveyed using static GPS base stations collecting point location for 20 minute intervals. Elevations were measured for the x,y,z location of each check point. Elevations interpolated from the DEM surface were then compared to the elevation values of the surveyed control.

The NVA was tested using 183 independent survey check points located in bare earth terrain types within the 10 counties. The 183 independent check points contained all NVA points and were surveyed using static GPS base stations collecting point location for 20 minute intervals. Elevations were measured for the x,y,z location of each check point. Elevations interpolated from the DEM surface were then compared to the elevation values of the surveyed control. The RMSE was computed to be 0.070m, or 0.137m @ 95th Confidence Interval defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASRPS Guidelines.

The VVA was tested using 211 independent survey check points located in various vegetation terrain types within the 10 counties. The 211 independent check points were surveyed using static GPS base stations collecting point location for 20 minute intervals. Elevations were measured for the x,y,z location of each check point. Elevations interpolated from the DEM surface were then compared to the elevation values of the surveyed control. The RMSE was computed to be 0.078m, or 0.169m @ 95th Percentile defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASRPS Guidelines.

LiDAR data is collected for the project area. Post processing of the simultaneously acquired GPS/INS is performed and applied to the laser returns to output a point cloud in the specified project coordinate system and datums. The point cloud data is then subjected to automated classification routines to assign all points in the point cloud to ground, water, overlap and unclassified point classes. Anomalous laser returns that occur infrequently are removed entirely from the data set. Once clean bare earth points are established, DEMs are created using bare earth points and hydro features. The DEM surface is then compared to the survey checkpoints. These accuracies must pass the Fundamental Vertical Accuracy, Supplemental Vertical Accuracy, and Consolidated Vertical Accuracy specifications.

LiDAR data is collected within the project area and processed. After the DEMs were created, the dataset was verified against control. Control was collected in 10 adjoining counties in Michigan. These counties include: Clare, Lake, Mecosta, Missaukee, Montcalm, Muskegon, Newaygo, Osceola, Roscommon, and Wexford. Accuracy is reported for all 10 counties combined.

Data is backed up to tape and to cloud storage.

The 2016 FEMA Michigan Part 1 lidar was ingested into the Data Access Viewer for custom product generation by leveraging USGS hosted Entwine Point Tiles.