2017 Lidar: Wayne County, MI
Data Set (DS) | OCM Partners (OCMP)GUID: gov.noaa.nmfs.inport:58939 | Updated: December 8, 2023 | Published / External
Summary
Short Citation
OCM Partners, 2024: 2017 Lidar: Wayne County, MI, https://www.fisheries.noaa.gov/inport/item/58939.
Full Citation Examples
This metadata record describes the Classified Point Cloud (LAS) for the 2017 Michigan LiDAR project covering approximately 612 square miles, covering Wayne County.
The NOAA Office for Coastal Management (OCM) downloaded this data set from this USGS site:
ftp://rockyftp.cr.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/USGS_LPC_MI_WayneCo_2017_LAS_2018/
These files were processed to the Data Access Viewer (DAV) and https. The total number of files downloaded and processed was 2901.
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 this product has 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. Change to an orthometric vertical datum is one of the many options.
-
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. They will be in an orthometric datum.
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.
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
https://coast.noaa.gov
Metadata Contact
NOAA Office for Coastal Management (NOAA/OCM)
coastal.info@noaa.gov
(843) 740-1202
https://coast.noaa.gov
Extents
-83.54826° W,
-82.865575° E,
42.44696° N,
42.02154° S
2017-04-12 - 2017-04-23
Item Identification
Title: | 2017 Lidar: Wayne County, MI |
---|---|
Short Name: | mi2017_wayne_m9034_metadata |
Status: | Completed |
Creation Date: | 2020-02-27 |
Publication Date: | 2017 |
Abstract: |
This metadata record describes the Classified Point Cloud (LAS) for the 2017 Michigan LiDAR project covering approximately 612 square miles, covering Wayne County. The NOAA Office for Coastal Management (OCM) downloaded this data set from this USGS site: ftp://rockyftp.cr.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/USGS_LPC_MI_WayneCo_2017_LAS_2018/ These files were processed to the Data Access Viewer (DAV) and https. The total number of files downloaded and processed was 2901. 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 this product has 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 (Geoid12B) 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.67", "ldrdens" : "2.2", "ldranps" : "0.67", "ldradens" : "2.2", "ldrfltht" : "2345", "ldrfltsp" : "130", "ldrscana" : "38", "ldrscanr" : "47.3", "ldrpulsr" : "235", "ldrpulsd" : "10", "ldrpulsw" : "0.53", "ldrwavel" : "1064", "ldrmpia" : "1", "ldrbmdiv" : "0.3", "ldrswatw" : "1615", "ldrswato" : "30", "ldrcrs" : "NAD_1983_2011_StatePlane_Michigan_South_FIPS_2113_Ft_Intl", "ldrgeoid" : "NGS Geoid12B" }, "ldraccur" : {
"ldrchacc" : "0", "rawnva" : "0.13", "rawnvan" : "185", "clsnva" : "0.13", "clsnvan" : "185", "clsvva" : "0.20", "clsvvan" : "132" }, "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" : "16", "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
|
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
|
UNCONTROLLED | |
None | Continent > North America > United States Of America > Michigan > Wayne County |
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: | Model (digital) |
Entity Attribute Detail Citation: |
USGS Base Specification 1.2, QL2 meeting 19.6 cm NVA |
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, USGS, NOAA, the Office for Coastal Management or its partners. |
Data Set Credit: | State of Michigan (SOM) |
Support Roles
Data Steward
Date Effective From: | 2020 |
---|---|
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
Date Effective From: | 2020 |
---|---|
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
Date Effective From: | 2020 |
---|---|
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
Date Effective From: | 2020 |
---|---|
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
W° Bound: | -83.54826 | |
---|---|---|
E° Bound: | -82.865575 | |
N° Bound: | 42.44696 | |
S° Bound: | 42.02154 |
Extent Group 1 / Time Frame 1
Time Frame Type: | Range |
---|---|
Start: | 2017-04-12 |
End: | 2017-04-23 |
Spatial Information
Spatial Representation
Representations Used
Grid: | No |
---|---|
Vector: | Yes |
Text / Table: | No |
TIN: | No |
Stereo Model: | No |
Video: | No |
Reference Systems
Reference System 1
Coordinate Reference System |
|||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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
Start Date: | 2020-02-27 |
---|---|
End Date: | Present |
Download URL: | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9034 |
Distributor: | NOAA Office for Coastal Management (NOAA/OCM) (2020 - Present) |
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. Change to an orthometric vertical datum is one of the many options. |
File Type (Deprecated): | Zip |
Compression: | Zip |
Distribution 2
Start Date: | 2020-02-27 |
---|---|
End Date: | Present |
Download URL: | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9034/index.html |
Distributor: | NOAA Office for Coastal Management (NOAA/OCM) (2020 - Present) |
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. They will be in an orthometric datum. |
File Type (Deprecated): | LAZ |
Distribution Format: | LAS/LAZ - LASer |
Compression: | Zip |
URLs
URL 1
URL: | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9034/supplemental/mi2017_wayne_m9034.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
URL: | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9034/breaklines/index.html |
---|---|
Name: | Breaklines |
URL Type: |
Online Resource
|
Description: |
Link to data set breaklines. |
Technical Environment
Description: |
Microsoft Windows 7; ESRI ArcCatalog 9.3.1.1850 |
---|
Data Quality
Horizontal Positional Accuracy: |
Horizontal positional accuracy for Wayne 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. 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 12 county control area. 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 185 independent survey check points located in flat terrain types within the 12 county area. The survey checkpoints were distributed throughout the block area. The 185 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 surface were then compared to the elevation values of the surveyed control. The RMSEz was computed to be 0.066m. 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. The NVA was tested using 185 independent survey check points located in bare earth terrain types within the 12 county area. The 185 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 RMSEz was computed to be 0.066m, or 0.13m @ 95 percent confidence level 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 132 independent survey check points located in various vegetation terrain types within the 12 county area. The 132 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 RMSEz was computed to be 0.104m, or 0.20m @ 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 Non-Vegetated and Vegetated Vertical Accuracy specifications. |
Conceptual Consistency: |
LiDAR data is collected within the project area and processed. After all of the deliverables were created, the dataset was verified against control. The control points were compared to the following counties and reported as one accuracy assessment: Tuscola, Huron, Sanilac, St. Clair, Macomb, Oakland, Jackson, Washtenaw, Wayne, Hillsdale, Lenawee, Monroe. |
Data Management
Have Resources for Management of these Data Been Identified?: | Yes |
---|---|
Approximate Percentage of Budget for these Data Devoted to Data Management: | Unknown |
Do these Data Comply with the Data Access Directive?: | Yes |
Actual or Planned Long-Term Data Archive Location: | NCEI-CO |
How Will the Data Be Protected from Accidental or Malicious Modification or Deletion Prior to Receipt by the Archive?: |
Data is backed up to tape and to cloud storage. |
Lineage
Sources
Classified lidar
Contact Role Type: | Originator |
---|---|
Contact Type: | Organization |
Contact Name: | Sanborn Map Company Inc. |
Extent Type: | Discrete |
Extent Start Date/Time: | 2017 |
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
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: | 2017 |
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
Contact Role Type: | Originator |
---|---|
Contact Type: | Organization |
Contact Name: | Sanborn Map Company Inc. |
Extent Type: | Discrete |
Extent Start Date/Time: | 2017 |
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
Contact Role Type: | Originator |
---|---|
Contact Type: | Organization |
Contact Name: | Sanborn Map Company Inc. |
Extent Type: | Discrete |
Extent Start Date/Time: | 2017 |
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
Contact Role Type: | Originator |
---|---|
Contact Type: | Organization |
Contact Name: | Sanborn Map Company Inc. |
Extent Type: | Discrete |
Extent Start Date/Time: | 2017 |
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
Contact Role Type: | Originator |
---|---|
Contact Type: | Organization |
Contact Name: | State of Michigan |
Extent Type: | Discrete |
Extent Start Date/Time: | 2017 |
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
Description: |
At selected locations throughout the site, accurate GPS coordinates and elevations are surveyed and the points are marked with targets. |
---|---|
Process Date/Time: | 2017-01-01 00:00:00 |
Process Step 2
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: | 2017-01-01 00:00:00 |
Process Step 3
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: | 2017-01-01 00:00:00 |
Process Step 4
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: | 2017-01-01 00:00:00 |
Process Step 5
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: | 2017-01-01 00:00:00 |
Process Step 6
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: | 2017-01-01 00:00:00 |
Process Step 7
Description: |
The NOAA Office for Coastal Management (OCM) downloaded this data set from this USGS site: ftp://rockyftp.cr.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/USGS_LPC_MI_WayneCo_2017_LAS_2018/ The total number of files downloaded and processed was 2901. The data were in MI State Plane South (2113) (NAD83 2011) coordinates and NAVD88 (Geoid12B) elevations in international 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. An internal OCM script was run to check the number of points by classification and by flight ID and the gps and intensity ranges. 2. Internal OCM scripts were run on the laz files to convert from orthometric (NAVD88) elevations to ellipsoid elevations using the Geoid12B model, to convert from MI State Plane South (2113) (NAD83 2011) coordinates in international feet to geographic coordinates, to convert vertical units from 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: | 2020-02-27 00:00:00 |
Process Contact: | Office for Coastal Management (OCM) |
Catalog Details
Catalog Item ID: | 58939 |
---|---|
GUID: | gov.noaa.nmfs.inport:58939 |
Metadata Record Created By: | Rebecca Mataosky |
Metadata Record Created: | 2020-02-27 14:25+0000 |
Metadata Record Last Modified By: | Rebecca Mataosky |
Metadata Record Last Modified: | 2023-12-08 15:23+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 |