Slide Menu
System Maintenance Notice, Monday, December 5, 2022 @ 1pm-5pm Eastern. The Operations Team will be performing system maintenance. During this scheduled downtime, InPort will not be available.
View All
Search Help Show/Hide Menu
Short Citation:
OCM Partners, 2022: Wayne and Washtenaw Counties 1.0 PPSM LiDAR, https://www.fisheries.noaa.gov/inport/item/49798.

Item Identification

Title: Wayne and Washtenaw Counties 1.0 PPSM LiDAR
Short Name: mi2009_usgs_wayne_washtenaw_m4809_metadata
Status: Completed
Publication Date: 2015-02-09
Abstract:

TASK NAME: Wayne and Washtenaw Counties 1.0 PPSM LiDAR

LiDAR Data Acquisition and Processing Production Task

USGS CONTRACT: 07CRCN0006

TASK ORDER NUMBER: G09PD00300

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 measurement 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. This data was collected at a resolution of one point per square meter. The final products include reflective surface, first, last, and at least one intermediate return, a bare earth model, and intensity data in separate files.

The reflective surface data represents the DEM created by the laser energy reflected from the first surface encountered by the laser pulse. Some energy may continue beyond this initial surface, to be reflected by a subsequent surface as represented by the last return data. Intensity information is captured from the reflective surface pulse and indicates the relative energy returned to the sensor, as compared to the energy transmitted. The intensity image is not calibrated or normalized but indicates differences in energy absorption due to the the interaction of the surface materials with laser energy, at the wavelength transmitted by the sensor. The bare earth model is created by identifying the returns that fall on the ground surface and by interpolating a surface between these points. In this manner, buildings and vegetation are removed from the bare earth model. This data set does not include bridges and overpasses in the bare earth model as the delineation point for these structures is not reliably discernible in the LiDAR data.

Purpose:

This task order consisted of LiDAR data acquisition and processing for Wayne and Washtenaw Counties in southeastern Michigan. The task order area of interest encompasses approximately 1324 square miles. The task required the LiDAR data to be collected at a minimum of one (1) point per square meter (1.0 meter GSD). The LiDAR data was collected to meet a vertical accuracy requirement of 18.0 cm (0.59 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 5,000' x 5,000' tiles, aligned to even 5,000' coordinates. The LAS files are comprised of the full class data.

Notes:

10442

Supplemental Information:

Reports for this project are available at:

https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4809/supplemental/mi2009_usgs_wayne_washtenaw_m4809_surveyreport.pdf https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4809/supplemental/mi2009_usgs_wayne_m4809_surveyreport.pdf

A footprint of this data set may be viewed in Google Earth at:

https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4809/supplemental/mi2009_usgs_wayne_washtenaw_m4809.kmz

Keywords

Theme Keywords

Thesaurus Keyword
ISO 19115 Topic Category
elevation
UNCONTROLLED
None Ground
None Terrain

Spatial Keywords

Thesaurus Keyword
UNCONTROLLED
Michigan Wayne and Washtenaw County

Physical Location

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

Data Set Information

Data Set Scope Code: Data Set
Maintenance Frequency: As Needed
Data Presentation Form: las
Entity Attribute Overview:

LAS 1.2 format (classes 1,2,8,9,12)

Entity Attribute Detail Citation:

none

Distribution Liability:

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

Support Roles

Data Steward

CC ID: 677665
Date Effective From: 2015-02-09
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: 677667
Date Effective From: 2015-02-09
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: 677668
Date Effective From: 2015-02-09
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: 677666
Date Effective From: 2015-02-09
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: 1136579
W° Bound: -84.158227
E° Bound: -82.859494
N° Bound: 42.473937
S° Bound: 42.011439

Extent Group 1 / Time Frame 1

CC ID: 1136573
Time Frame Type: Discrete
Start: 2009-04-16

Extent Group 1 / Time Frame 2

CC ID: 1136574
Time Frame Type: Discrete
Start: 2009-04-17

Extent Group 1 / Time Frame 3

CC ID: 1136575
Time Frame Type: Discrete
Start: 2009-04-18

Extent Group 1 / Time Frame 4

CC ID: 1136576
Time Frame Type: Discrete
Start: 2009-04-23

Extent Group 1 / Time Frame 5

CC ID: 1136577
Time Frame Type: Discrete
Start: 2009-04-24

Extent Group 1 / Time Frame 6

CC ID: 1136578
Time Frame Type: Discrete
Start: 2009-05-03

Spatial Information

Spatial Representation

Representations Used

Vector: Yes

Access Information

Security Class: Unclassified
Data Access Procedure:

This data can be obtained on-line at the following URL:

https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=4809

The data set is dynamically generated based on user-specified parameters.;

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. These data depict the heights at the time of the survey and are only accurate for that time.

Distribution Information

Distribution 1

CC ID: 741398
Download URL: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=4809
Distributor:
File Name: Customized Download
Description:

Create custom data files by choosing data area, product type, map projection, file format, datum, etc.

Distribution 2

CC ID: 741399
Download URL: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4809/index.html
Distributor:
File Name: Bulk Download
Description:

Simple download of data files.

URLs

URL 1

CC ID: 741401
URL: https://coast.noaa.gov/dataviewer
URL Type:
Online Resource

URL 2

CC ID: 741402
URL: https://coast.noaa.gov
URL Type:
Online Resource

URL 3

CC ID: 741403
URL: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4809/supplemental/mi2009_usgs_wayne_washtenaw_m4809.kmz
Name: Browse Graphic
URL Type:
Browse Graphic
File Resource Format: kmz
Description:

This graphic shows the lidar coverage for the 2009 USGS lidar collection of Wayne and Washtenaw Counties, Michigan.

Activity Log

Activity Log 1

CC ID: 677687
Activity Date/Time: 2016-05-23
Description:

Date that the source FGDC record was last modified.

Activity Log 2

CC ID: 677686
Activity Date/Time: 2017-11-14
Description:

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.

Activity Log 3

CC ID: 718368
Activity Date/Time: 2018-02-08
Description:

Partial upload of Positional Accuracy fields only.

Activity Log 4

CC ID: 741400
Activity Date/Time: 2018-03-13
Description:

Partial upload to move data access links to Distribution Info.

Data Quality

Accuracy:

The LiDAR collected for this task order was collected at a vertical accuracy of 18.0 cm (0.59 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: 18.0 cm (0.59 ft) RMSE | Quantitative Test Explanation: Points measured will produce an error less than 18.0 cm (0.59 ft) RMSE.

Horizontal Positional Accuracy:

Horizontal accuracy is +/- 1.158 meters at the 95% confidence level using RMSE(r) x 1.7308 as defined by the FGDC Geospatial Positional Accuracy Standards, Part 3: NSSDA.; Quantitative Value: 0.669 meters, Test that produced the value: 66.9 cm RMSE

Vertical Positional Accuracy:

The LiDAR data vertical accuracy RMSE is 8.84 cm.

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: 36.3 cm (1.19 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. This data set tested to 0.56 ft.

The Supplemental Vertical Accuracy (SVA) of the TIN: 36.3 cm (1.19 ft) at a 95% confidence level, derived according to American Society for Photogrammetry and Remote Sensing (ASPRS) Guidelines, Vertical Accuracy Reporting for LiDAR Data, i.e., based on the 95th percentile error in each of the individual other land cover categories. This criterion is a target value; larger errors in category could be offset by smaller errors in other categories so long as the overall consolidated vertical accuracy (CVA) is satisfied.This data set tested to 0.56 ft. for all categories.

The Consolidated Vertical Accuracy (CVA): 36.3 cm (1.19 ft) at a 95% confidence level, derived according to ASPRS Guidelines, Vertical Accuracy Reporting for LiDAR Data, i.e., based on the 95th percentile error in all land cover categories combined. This data set tested to 0.56 ft. for all categories.; Quantitative Value: 0.0884 meters, Test that produced the value: 8.84 cm RMSEz

Completeness Report:

The LIDAR data is visually inspected for completeness to ensure that are no gaps between flight lines.

Conceptual Consistency:

All formatted data are validated using commercial GIS software to ensure proper formatting and loading prior to delivery.

Lineage

Process Steps

Process Step 1

CC ID: 1136567
Description:

Using a LH Systems ALS50 Light Detection And Ranging (LiDAR) system, 135 flight lines of high density data, one point per square meter, were collected over Wayne and Washtenaw Counties (approximately 1,324 square miles). Multiple returns were recorded for each laser pulse along with an intensity value for each return. A total of six missions were flown over an 18 day period: April 16, 2009 through May 3, 2009. A minimum of two airborne global positioning system (GPS) base stations were used in support of the LiDAR data acquisition. The mean baseline length was 28 miles, with a maximum baseline length of 52 miles. In addition, 31 ground control points were surveyed through static methods. The geoid used to reduce satellite derived elevations to orthometric heights was Geoid03. All data for the task order is referenced to Michigan State Plane South Zone (2113), NAD83/2007, NAVD88, in international feet. 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. Four layers of coverage were delivered in the ArcINFO ArcGrid binary format: reflective surface, bare-earth, last return and intensity. System Parameters: - Type of Scanner = LH Systems ALS50 - Data Acquisition Height = 7,000-feet AGL - Scanner Field of View = 14 degrees - Scan Frequency = 65.3 Hertz - Pulse Repetition Rate - 114.6 Kilohertz - Aircraft Speed = 120 Knots - Swath Width = 1,719-feet - Number of Returns Per Pulse = Maximum of 4 - Distance Between Flight Lines = 1,289-feet

Process Date/Time: 2009-08-31 00:00:00

Process Step 2

CC ID: 1136568
Description:

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.

Process Date/Time: 2009-08-31 00:00:00

Process Step 3

CC ID: 1136569
Description:

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.

Process Date/Time: 2009-08-31 00:00:00

Process Step 4

CC ID: 1136570
Description:

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 homogeneous 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), model keypoints (Class 8), overlap (Class 12) 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.

Process Date/Time: 2009-08-31 00:00:00

Process Step 5

CC ID: 1136571
Description:

The NOAA Office for Coastal Management (OCM) received the files in laz format from USGS via an FTP online repository. The files contained lidar elevation and intensity measurements. The data were in State Plane MI 2113 South, NAVD88 (orthometric) international feet. OCM performed the following processing for data storage and Digital Coast provisioning purposes:

1. The data were converted from State Plane coordinates to geographic coordinates.

2. The data were converted from NAVD88 (orthometric) heights in international feet to GRS80 (ellipsoid) heights in meters using Geoid 03.

3. The LAS data were sorted by latitude and the headers were updated.

4. Erroneous elevations were removed.

Process Date/Time: 2015-01-20 00:00:00

Catalog Details

Catalog Item ID: 49798
GUID: gov.noaa.nmfs.inport:49798
Metadata Record Created By: Anne Ball
Metadata Record Created: 2017-11-15 15:22+0000
Metadata Record Last Modified By: SysAdmin InPortAdmin
Metadata Record Last Modified: 2022-08-09 17:11+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