2019 FEMA Lidar: 19 County MI

Dates of collection for Luce and Schoolcraft counties.

Dates of collection for Alpena and Montmorency counties.

Dates of collection for Antrim and Ostego counties.

Dates of collection for Dickinson, Iron, and Menominee counties.

Additional dates of collection for Houghton, Keweenaw, and Ontonagon Counties

Dates of collection for Houghton, Keweenaw, and Ontonagon Counties

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. Change to an orthometric vertical datum is one of the many options.

Bulk download of data files in LAZ format, based on a horizontal datum/projection of NAD83 (2011) State Plane Michigan Central (FIPS 2112) and North (FIPS 2111) International Feet, and a vertical datum of NAVD88 (GEOID12B) in International feet. This url links to the USGS copy of the files, from which the Entwine Point Tile files originated. These have not been reviewed by OCM and the link is provided here for convenience.

The Data Access Viewer (DAV) allows a user to search for and download elevation, imagery, and land cover data for the coastal U.S. and its territories. The data, hosted by the NOAA Office for Coastal Management, can be customized and requested for free download through a checkout interface. An email provides a link to the customized data, while the original data set is available through a link within the viewer.

Lidar reports are available by county from the USGS rockyweb https site.

Hydro breaklines are available by county from the USGS rockyweb https site.

This data source was used (along with airborne GNSS/IMU data) to georeference the lidar point cloud data.

The following steps describe the Raw Data Processing and Calibration process: 1) Technicians processed the raw data to LAS format flight lines using the ABGNSS/IMU solution. 2) Technicians use TerraSolid TerraMatch to calculate initial calibration adjustment angles by mission and/or block. This is accomplished by identifying ground and above ground feature observations between flight-lines and calculating the offsets. The technician then analyzed the results and made any necessary additional adjustment until it is acceptable. 3) Once the angle calculation was completed the adjusted settings were applied to all of the flight-lines of the mission and/or block and checked for consistency. The technicians utilized commercial and proprietary software packages to analyze how well flight-line overlaps match and adjusted as necessary until the results met the project specifications. 4) The technicians checked and corrected the vertical misalignment of all flight-lines and also the matching between data and ground truth. The relative accuracy was less than or equal to 6 cm RMSEz within individual swaths and less than or equal to 8 cm RMSDz or within swath overlap (between adjacent swaths). 5) The technicians ran a final vertical accuracy check of the calibrated point cloud against the surveyed check points after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level (Required Accuracy) was met. Point classification was performed according to USGS Lidar Base Specification 1.3, and breaklines were collected for water features. Bare earth DEMs were exported from the classified point cloud using collected breaklines for hydroflattening.

LAS Point Classification: The point classification is performed as described below. The bare-earth surface is manually reviewed to ensure correct classification on the Class 2 (Ground) points. After the bare-earth surface is edited and QC'd, it is then used to generate all hydro-breaklines through heads-up digitization. All ground (ASPRS Class 2) lidar data inside of the Lake Pond and River Pond hydro flattening breaklines were then classified to water (ASPRS Class 9) using LP360 functionality. A buffer of 2 feet was also used around each hydro-flattened feature to classify these ground (ASPRS Class 2) points to Ignored ground (ASPRS Class 20). All Lake Pond Island and River Stream Island features were checked to ensure that the ground (ASPRS Class 2) points were reclassified to the correct classification after the automated classification was completed. All overlap data was processed through automated functionality provided by TerraScan to classify the overlapping flight-line data to approved classes by USGS. The overlap data was classified using standard LAS overlap bit. These classes were created through automated processes only and were not verified for classification accuracy. All data was manually reviewed and any remaining artifacts removed using functionality provided by TerraScan and TerraModeler. Global Mapper is used as a final check of the bare-earth dataset. GeoCue was then used to create the deliverable industry-standard LAS files for the Classified Point Cloud Data. LAStools, LP360 and TerraScan software was used to perform statistical analysis of the classes in the LAS files, on a per tile level to verify classification metrics and full LAS header information.

Data for Alcona, Oscoda, Cheboygan, Chippewa, Gogebic, Crawford & Kalkaska counties was downloaded from the USGS Rocky ftp site in NAD83(2011) Michigan North & Central State Plane (Int ft) coordinates with vertical feet NAVD88 (Geoid12b) elevations. Data were converted to geographic coordinates, from vertical feet to meters, and to ellipsoid heights (using Geoid 12b) for ingest in the NOAA Digital Coast Data Access Viewer.

The observed classes process to the Data Access Viewer are: 1 = unclassified, 2 = ground, 7 = low noise, 9 = water, 17 = bridge deck, 18 = high noise, 20 = ignored ground near breakline

Data for Alpena, Antrim, Dickinson, Iron, Luce, Menominee, Montmorency, Ostego, and Schoolcraft counties were downloaded from the USGS Rocky ftp site in NAD83(2011) Michigan North & Central State Plane (Int ft) coordinates with vertical feet NAVD88 (Geoid12b) elevations. Data were converted to geographic coordinates, from vertical feet to meters, and to ellipsoid heights (using Geoid 12b) for ingest in the NOAA Digital Coast Data Access Viewer.

The observed classes processed to the Data Access Viewer are: 1 = unclassified, 2 = ground, 7 = low noise, 9 = water, 17 = bridge deck, 18 = high noise, 20 = ignored ground near breakline

Data for Houghton, Keweenaw, and Ontonagon counties were downloaded from the USGS Rocky ftp site in NAD83(2011) Michigan North State Plane (Int ft) coordinates with vertical feet NAVD88 (Geoid12b) elevations. Data were converted to geographic coordinates, from vertical feet to meters, and to ellipsoid heights (using Geoid 12b) for ingest in the NOAA Digital Coast Data Access Viewer.

The observed classes processed to the Data Access Viewer are: 1 = unclassified, 2 = ground, 7 = low noise, 9 = water, 17 = bridge deck, 18 = high noise, 20 = ignored ground near breakline