Search Help Show/Hide Menu
Summary
Item Identification
Keywords
Physical Location
Data Set Info
Support Roles
Extents
Access Info
Distribution Info
URLs
Tech Environment
Data Quality
Lineage
Catalog Details

Summary

Browse graphic

Short Citation
OCM Partners, 2024: 2016 FEMA Michigan Lidar: Part 1 (Muskegon County), https://www.fisheries.noaa.gov/inport/item/56271.
Full Citation Examples

Abstract

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. All systems consist of geodetic GPS positioning, orientation derived from high-end inertial sensors and highly-accurate lasers. The sensor is mounted inside an aircraft and emits rapid pulses of light, through an opening in the fuselage, that are used to determine distances between the plane and terrain below. The Leica ALS70-HP was used to collect data for the survey campaign. The LiDAR systems are calibrated by conducting flight passes over a known ground surface before and after each LiDAR mission. During final data processing, the calibration parameters are inserted into post-processing software.

The NOAA Office for Coastal Management (OCM) downloaded the Muskegon County portion of this data set from this USGS site:

ftp://rockyftp.cr.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/USGS_LPC_MI_Muskegon_2015_LAS_2018/ and processed the data to the Data Access Viewer (DAV) and https.

Muskegon County: 2509 laz files covering approximately 527 square miles.

Hydro breaklines are also available. These data are available for download at the link provided in the URL section of this metadata record. Please note that these products have not been reviewed by the NOAA Office for Coastal Management (OCM) and any conclusions drawn from the analysis of this information are not the responsibility of NOAA or OCM.

Distribution Information

  • Create custom data files by choosing data area, product type, map projection, file format, datum, etc. A new metadata will be produced to reflect your request using this record as a base.

  • LAS/LAZ - LASer

    Bulk download of data files in LAZ format, geographic coordinates, orthometric heights. Note that the vertical datum (hence elevations) of the files here are different than described in this document.

Access Constraints:

None

Use Constraints:

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.

Controlled Theme Keywords

COASTAL ELEVATION, elevation, TERRAIN ELEVATION

Child Items

No Child Items for this record.

Contact Information

Point of Contact
NOAA Office for Coastal Management (NOAA/OCM)
coastal.info@noaa.gov
(843) 740-1202

Metadata Contact
NOAA Office for Coastal Management (NOAA/OCM)
coastal.info@noaa.gov
(843) 740-1202

Extents

Geographic Area 1

-86.4603° W, -85.79142° E, 43.468881° N, 43.114456° S

Time Frame 1
2016-04-14 - 2016-04-16

Item Identification

Title: 2016 FEMA Michigan Lidar: Part 1 (Muskegon County)
Short Name: mi2016_fema_m8731_metadata.xml
Status: Completed
Publication Date: 2016
Abstract:

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. All systems consist of geodetic GPS positioning, orientation derived from high-end inertial sensors and highly-accurate lasers. The sensor is mounted inside an aircraft and emits rapid pulses of light, through an opening in the fuselage, that are used to determine distances between the plane and terrain below. The Leica ALS70-HP was used to collect data for the survey campaign. The LiDAR systems are calibrated by conducting flight passes over a known ground surface before and after each LiDAR mission. During final data processing, the calibration parameters are inserted into post-processing software.

The NOAA Office for Coastal Management (OCM) downloaded the Muskegon County portion of this data set from this USGS site:

ftp://rockyftp.cr.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/USGS_LPC_MI_Muskegon_2015_LAS_2018/ and processed the data to the Data Access Viewer (DAV) and https.

Muskegon County: 2509 laz files covering approximately 527 square miles.

Hydro breaklines are also available. These data are available for download at the link provided in the URL section of this metadata record. Please note that these products have not been reviewed by the NOAA Office for Coastal Management (OCM) and any conclusions drawn from the analysis of this information are not the responsibility of NOAA or OCM.

Purpose:

To acquire detailed surface elevation data for use in conservation planning, design, research, floodplain mapping, dam safety assessments, and hydrologic modeling. LAS data products are suitable for 1 foot contour generation. USGS LiDAR Base Specification 1.2, QL2. 19.6 cm NVA.

Supplemental Information:

Project Projection, Datums and Units. Projection - State Plane Michigan 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 FVA",

"ldrsens" : "Leica ALS70",

"ldrmaxnr" : "4",

"ldrnps" : "0.65",

"ldrdens" : "1.67",

"ldradens" : "2.2",

"ldranps" : "0.71",

"ldrfltht" : "2250",

"ldrfltsp" : "135",

"ldrscana" : "32",

"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_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" : "1",

"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"

}

}}

Keywords

Theme Keywords

Thesaurus Keyword
Global Change Master Directory (GCMD) Science Keywords
EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION
Global Change Master Directory (GCMD) Science Keywords
EARTH SCIENCE > OCEANS > COASTAL PROCESSES > COASTAL ELEVATION
ISO 19115 Topic Category
elevation
UNCONTROLLED
MI ALS70
MI Bare Earth
MI Contour
MI Digital Elevation Model (DEM)
MI Digital Surface Model (DSM)
MI Digital Terrain Model (DTM)
MI First Return
MI Grid
MI ground points
MI IMG
MI Intensity return
MI LAS
MI LiDAR
MI mapping
MI Overlap points
MI point cloud
MI Unclassified points
MI Water points
None beach
None erosion

Spatial Keywords

Thesaurus Keyword
Global Change Master Directory (GCMD) Location Keywords
CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > MICHIGAN
Global Change Master Directory (GCMD) Location Keywords
VERTICAL LOCATION > LAND SURFACE

Instrument Keywords

Thesaurus Keyword
Global Change Master Directory (GCMD) Instrument Keywords
LIDAR > Light Detection and Ranging

Platform Keywords

Thesaurus Keyword
Global Change Master Directory (GCMD) Platform Keywords
Airplane > Airplane

Physical Location

Organization: Office for Coastal Management
City: Charleston
State/Province: SC

Data Set Information

Data Set Scope Code: Data Set
Data Set Type: Elevation
Maintenance Frequency: Unknown
Data Presentation Form: Point cloud (Digital)
Entity Attribute Detail Citation:

USGS Base Specification 1.2, QL2 meeting 19.6 cm FVA

Distribution Liability:

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 the State of Michigan, NOAA, the Office for Coastal Management, or its partners.

Data Set Credit: State of Michigan (SOM)

Support Roles

Data Steward

CC ID: 839635
Date Effective From: 2019
Date Effective To:
Contact (Organization): NOAA Office for Coastal Management (NOAA/OCM)
Address: 2234 South Hobson Ave
Charleston, SC 29405-2413
Email Address: coastal.info@noaa.gov
Phone: (843) 740-1202
URL: https://coast.noaa.gov

Distributor

CC ID: 839636
Date Effective From: 2019
Date Effective To:
Contact (Organization): NOAA Office for Coastal Management (NOAA/OCM)
Address: 2234 South Hobson Ave
Charleston, SC 29405-2413
Email Address: coastal.info@noaa.gov
Phone: (843) 740-1202
URL: https://coast.noaa.gov

Metadata Contact

CC ID: 839637
Date Effective From: 2019
Date Effective To:
Contact (Organization): NOAA Office for Coastal Management (NOAA/OCM)
Address: 2234 South Hobson Ave
Charleston, SC 29405-2413
Email Address: coastal.info@noaa.gov
Phone: (843) 740-1202
URL: https://coast.noaa.gov

Point of Contact

CC ID: 839638
Date Effective From: 2019
Date Effective To:
Contact (Organization): NOAA Office for Coastal Management (NOAA/OCM)
Address: 2234 South Hobson Ave
Charleston, SC 29405-2413
Email Address: coastal.info@noaa.gov
Phone: (843) 740-1202
URL: https://coast.noaa.gov

Extents

Currentness Reference: Ground Condition

Extent Group 1

Extent Group 1 / Geographic Area 1

CC ID: 1142249
W° Bound: -86.4603
E° Bound: -85.79142
N° Bound: 43.468881
S° Bound: 43.114456

Extent Group 1 / Time Frame 1

CC ID: 1142248
Time Frame Type: Range
Start: 2016-04-14
End: 2016-04-16

Access Information

Security Class: Unclassified
Data Access Procedure:

Data is available online for bulk and custom downloads.

Data Access Constraints:

None

Data Use Constraints:

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.

Distribution Information

Distribution 1

CC ID: 839642
Start Date: 2018
End Date: Present
Download URL: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=8731
Distributor:
File Name: Customized Download
Description:

Create custom data files by choosing data area, product type, map projection, file format, datum, etc. A new metadata will be produced to reflect your request using this record as a base.

Compression: Zip

Distribution 2

CC ID: 839643
Start Date: 2018
End Date: Present
Download URL: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/8731/index.html
Distributor:
File Name: Bulk Download
Description:

Bulk download of data files in LAZ format, geographic coordinates, orthometric heights. Note that the vertical datum (hence elevations) of the files here are different than described in this document.

File Type (Deprecated): LAZ
Distribution Format: LAS/LAZ - LASer
Compression: Zip

URLs

URL 1

CC ID: 839632
URL: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/8731/supplemental/mi2016_fema_m8731.kmz
Name: Browse graphic
URL Type:
Browse Graphic
File Resource Format: KML
Description:

This graphic displays the footprint for this lidar data set.

URL 2

CC ID: 839633
URL: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/8731/supplemental/Final_Report_Michigan_LiDAR_Spring_2016.docx
Name: Dataset report
URL Type:
Online Resource
File Resource Format: PDF
Description:

Link to data set report.

URL 3

CC ID: 839687
URL: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/8731/breaklines/index.html
URL Type:
Online Resource
Description:

Link to the data set breaklines.

Technical Environment

Description:

Microsoft Windows 7; ESRI ArcCatalog 9.3.1.1850

Data Quality

Horizontal Positional Accuracy:

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.

Vertical Positional Accuracy:

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 FVA be 19.6 cm or better @ 95 percent confidence level.

Raw NVA

0.070m RMSE, or 0.137m NVA @ 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 RMSE was computed to be 0.070 m. AccuracyZ has been tested to meet 10 cm Nonvegetated Vertical Accuracy at 95 Percent confidence level using RMSE(z) x 1.9600 as defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASPRS Guidelines.

NVA

0.070m RMSE, or 0.156m NVA @ 95th Percentile

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.156m @ 95th Percentile defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASRPS Guidelines.

VVA

0.078m RMSE, or 0.169m VVA @ 95th Percentile

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.

Completeness Report:

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.

Conceptual Consistency:

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.

Lineage

Sources

Classified lidar

CC ID: 1142234
Contact Role Type: Originator
Contact Type: Organization
Contact Name: Sanborn Map Company Inc.
Extent Type: Discrete
Extent Start Date/Time: 2016
Scale Denominator: 1200
Source Contribution:

The classified lidar point cloud is used to derive various data products such as, but not limited to, bare earth gridded DEM, triangulated irregular networks (TIN), contours, digital surface models (DSM). The output format is fully compliant LAS v1.4, Point Record Format 6

Ground control

CC ID: 1142235
Contact Role Type: Originator
Contact Type: Organization
Contact Name: Sanborn Map Company Inc.
Publish Date: 2010-01-01
Extent Type: Discrete
Extent Start Date/Time: 2016
Source Contribution:

Targeted ground control is used to create a digital control file and control report as well as QC check of LiDAR accuracy. Predefined points (NGS when available) within the project area are targeted.

LiDAR Data

CC ID: 1142236
Contact Role Type: Originator
Contact Type: Organization
Contact Name: Sanborn Map Company Inc.
Extent Type: Discrete
Extent Start Date/Time: 2016
Source Contribution:

Aerial LiDAR and GPS/IMU data are recorded for the defined project area at an altitude, flight speed, scanner swath width and scanner pulse frequency to achieve the design goals of the project.

Post processed GPS/INS

CC ID: 1142237
Contact Role Type: Originator
Contact Type: Organization
Contact Name: Sanborn Map Company Inc.
Extent Type: Discrete
Extent Start Date/Time: 2016
Scale Denominator: 1200
Source Contribution:

Post processed GPS/INS is applied to the lidar point data to georeference each point in the project coordinate system

Post processed lidar

CC ID: 1142238
Contact Role Type: Originator
Contact Type: Organization
Contact Name: Sanborn Map Company Inc.
Extent Type: Discrete
Extent Start Date/Time: 2016
Scale Denominator: 1200
Source Contribution:

The post processed lidar data has been projected and oriented in the specified coordinate system as an un-classified point cloud.

Tile Definition

CC ID: 1142239
Contact Role Type: Originator
Contact Type: Organization
Contact Name: State of Michigan
Extent Type: Discrete
Extent Start Date/Time: 2016
Scale Denominator: 1200
Source Contribution:

The tile definition defines discreet non-overlapping rectangular areas used as cut lines to break up the large classified lidar dataset into smaller, more manageable data tiles. Each tile is 2500ft by 2500ft in dimension.

Process Steps

Process Step 1

CC ID: 1142240
Description:

At selected locations throughout the site, accurate GPS coordinates and elevations are surveyed and the points are marked with targets.

Process Date/Time: 2016-01-01 00:00:00

Process Step 2

CC ID: 1142241
Description:

New LiDAR data is captured for the project area using a Leica ALS70 LiDAR instrument an integrated IPAS20 GPS/INS system mounted within a Aero Commander twin engine airplane.

Process Date/Time: 2016-01-01 00:00:00

Process Step 3

CC ID: 1142242
Description:

The airborne GPS data is post-processed in Inertial Explorer software and LEICA CloudPro software to determine the LiDAR sensor's angle and orientation in the terrain (project) coordinate system and datums during the survey.

Process Date/Time: 2016-01-01 00:00:00

Process Step 4

CC ID: 1142243
Description:

The post processed GPS/INS solution is applied to the raw lidar data to orient and project the data points into the project area reference system as an unclassified point cloud.

Process Date/Time: 2016-01-01 00:00:00

Process Step 5

CC ID: 1142244
Description:

The georeferenced lidar data is then classified and edited in Terrasolid Terrascan software. Data is classified to produce: Class 1: unclassified, Class 2: ground, Class 7: low point, Class 9: water, Class 10: ignored ground, Class 11: withheld.

Process Date/Time: 2016-01-01 00:00:00

Process Step 6

CC ID: 1142245
Description:

The classified lidar data is exported as 2500 X 2500 foot tiles in the LAS format with any or all classes required to produce derivative products.

Process Date/Time: 2016-01-01 00:00:00

Process Step 7

CC ID: 1142246
Description:

For Muskegon County, the NOAA Office for Coastal Management (OCM) downloaded 2509 laz files from this USGS site: ftp://rockyftp.cr.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/USGS_LPC_MI_Muskegon_2015_LAS_2018/. The data were in State Plane Michigan South NAD83 2011 coordinates (international feet) and NAVD88 (Geoid12A) elevations in feet. The data were classified as: 1 - Unclassified, 2 - Ground, 7 - Low Noise, 9 - Water, 10 - Ignored Ground, 17 - Bridge Decks, 18 - High Noise. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). Classes available on the DAV are: 1, 2, 7, 9, 10, 17, 18.

OCM performed the following processing on the data for Digital Coast storage and provisioning purposes:

1. The LAStools software scripts lasinfo and lasvalidate were run on the laz files to check for errors.

2. An internal OCM script was run to check the number of points by classification and by flight ID and the gps and intensity ranges.

3. Internal OCM scripts were run on the laz files to convert from orthometric (NAVD88) elevations to ellipsoid elevations using the Geoid 12A model, to convert from State Plane Michigan South NAD83 2011coordinates in international feet to geographic coordinates, to convert from vertical elevations in feet to meters, to assign the geokeys, to sort the data by gps time and zip the data to database and to http.

Process Date/Time: 2019-05-09 00:00:00
Process Contact: Office for Coastal Management (OCM)

Catalog Details

Catalog Item ID: 56271
GUID: gov.noaa.nmfs.inport:56271
Metadata Record Created By: Rebecca Mataosky
Metadata Record Created: 2019-05-10 09:29+0000
Metadata Record Last Modified By: Rebecca Mataosky
Metadata Record Last Modified: 2023-12-08 16:01+0000
Metadata Record Published: 2022-03-16
Owner Org: OCMP
Metadata Publication Status: Published Externally
Do Not Publish?: N
Metadata Last Review Date: 2022-03-16
Metadata Review Frequency: 1 Year
Metadata Next Review Date: 2023-03-16