2016 FEMA Michigan Lidar: Part 1 (Muskegon County)
OCM Partners
Data Set
(DS)
| ID: 56271
| Published / External
Created: 2019-05-10
|
Last Modified: 2023-12-08
Project (PRJ) | ID: 49401
ID: 56271
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2016 FEMA Michigan Lidar: Part 1 (Muskegon County) |
---|---|
Short Name | mi2016_fema_m8731_metadata.xml |
* Status | Completed |
Creation Date | |
Revision Date | |
• 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. |
Notes | |
Other Citation Details | |
• 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" } }} |
DOI (Digital Object Identifier) | |
DOI Registration Authority | |
DOI Issue Date |
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 |
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 |
Temporal Keywords
Thesaurus | Keyword |
---|---|
* 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 |
Stratum Keywords
Thesaurus | Keyword |
---|---|
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 |
• Country | |
• » Location Description |
Data Set Information
* Data Set Scope Code | Data Set |
---|---|
• Data Set Type | Elevation |
• Maintenance Frequency | Unknown |
Maintenance Note | |
» Data Presentation Form | Point cloud (Digital) |
• Entity Attribute Overview | |
Entity Attribute Detail Citation |
USGS Base Specification 1.2, QL2 meeting 19.6 cm FVA |
Entity Attribute Detail URL | |
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
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2019 |
Date Effective To | |
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 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | Distributor |
---|---|
* » Date Effective From | 2019 |
Date Effective To | |
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 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | Metadata Contact |
---|---|
* » Date Effective From | 2019 |
Date Effective To | |
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 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | Point of Contact |
---|---|
* » Date Effective From | 2019 |
Date Effective To | |
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 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
Extents
Currentness Reference | Ground Condition |
---|
Extent Group 1
Extent Description |
---|
Extent Group 1 / Geographic Area 1
* » W° Bound | -86.4603 |
---|---|
* » E° Bound | -85.79142 |
* » N° Bound | 43.468881 |
* » S° Bound | 43.114456 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Range |
---|---|
* » Start | 2016-04-14 |
End | 2016-04-16 |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Spatial Information
Spatial Resolution
Angular Distance | |
---|---|
Angular Distance Units | |
Horizontal Distance | |
Horizontal Distance Units | |
Vertical Distance | |
Vertical Distance Units | |
Equivalent Scale Denominator | |
Level of Detail Description |
|
Spatial Representation
Grid Representation Used? | |
---|---|
Vector Representation Used? | |
Text / Table Representation Used? | |
TIN Representation Used? | |
Stereo Model Representation Used? | |
Video Representation Used? |
Grid Representation
Dimension Count | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Cell Geometry | |||||||||||||
Transformation Parameter Available? | |||||||||||||
Axis Dimension |
|||||||||||||
|
|||||||||||||
Axis Dimension |
|||||||||||||
|
Vector Representation
Topology Level | |
---|---|
Complex Object Present? | |
Complex Object Count | |
Composite Object Present? | |
Composite Object Count | |
Curve Object Present? | |
Curve Object Count | |
Point Object Present? | |
Point Object Count | |
Solid Object Present? | |
Solid Object Count | |
Surface Object Present? | |
Surface Object Count |
Reference Systems
Reference System
EPSG Code | |||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Horizontal Resolution |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Vertical Resolution |
|||||||||||||||||||||||||||||
|
Access Information
Data License | |
---|---|
Data License URL | |
Data License Statement | |
* » Security Class | Unclassified |
* Security Classification System | |
Security Handling Description | |
• Data Access Policy | |
» 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. |
Metadata Access Constraints | |
Metadata Use Constraints |
Distribution Information
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. |
File Date/Time | |
File Type (Deprecated) | |
Distribution Format | |
File Size | |
Application Version | |
Compression | Zip |
Review Status |
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 Date/Time | |
File Type (Deprecated) | LAZ |
Distribution Format | LAS/LAZ - LASer |
File Size | |
Application Version | |
Compression | Zip |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
URLs
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 | 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 | |
Description |
Link to data set report. |
URL | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/8731/breaklines/index.html |
---|---|
Name | |
URL Type | Online Resource |
File Resource Format | |
Description |
Link to the data set breaklines. |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
Activity Log
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Issues
Issue Date | |
---|---|
Author | |
Issue |
Issue Date | |
---|---|
Author | |
Issue |
Issue Date | |
---|---|
Author | |
Issue |
Technical Environment
Description |
Microsoft Windows 7; ESRI ArcCatalog 9.3.1.1850 |
---|
Data Quality
Representativeness | |
---|---|
Accuracy | |
Analytical Accuracy | |
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. |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure | |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
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. |
» Quality Control Procedures Employed |
Data Management
» Have Resources for Management of these Data Been Identified? | |
---|---|
» Approximate Percentage of Budget for these Data Devoted to Data Management | |
» Do these Data Comply with the Data Access Directive? | |
» Is Access to the Data Limited Based on an Approved Waiver? | |
» If Distributor (Data Hosting Service) is Needed, Please Indicate | |
» Approximate Delay Between Data Collection and Dissemination | |
» If Delay is Longer than Latency of Automated Processing, Indicate Under What Authority Data Access is Delayed |
|
» Actual or Planned Long-Term Data Archive Location | |
» If World Data Center or Other, Specify | |
» If To Be Determined, Unable to Archive, or No Archiving Intended, Explain |
|
» Approximate Delay Between Data Collection and Archiving | |
» How Will the Data Be Protected from Accidental or Malicious Modification or Deletion Prior to Receipt by the Archive? |
|
Lineage
» Lineage Statement |
---|
Sources
Citation Title | Classified lidar |
---|---|
Contact Role Type | Originator |
Contact Type | Organization |
Contact Name | Sanborn Map Company Inc. |
Publish Date | |
Extent Type | Discrete |
Extent Start Date/Time | 2016 |
Extent End Date/Time | |
Scale Denominator | 1200 |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
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 |
Citation Title | 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 | 2016 |
Extent End Date/Time | |
Scale Denominator | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
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. |
Citation Title | LiDAR Data |
---|---|
Contact Role Type | Originator |
Contact Type | Organization |
Contact Name | Sanborn Map Company Inc. |
Publish Date | |
Extent Type | Discrete |
Extent Start Date/Time | 2016 |
Extent End Date/Time | |
Scale Denominator | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
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. |
Citation Title | Post processed GPS/INS |
---|---|
Contact Role Type | Originator |
Contact Type | Organization |
Contact Name | Sanborn Map Company Inc. |
Publish Date | |
Extent Type | Discrete |
Extent Start Date/Time | 2016 |
Extent End Date/Time | |
Scale Denominator | 1200 |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Source Contribution |
Post processed GPS/INS is applied to the lidar point data to georeference each point in the project coordinate system |
Citation Title | Post processed lidar |
---|---|
Contact Role Type | Originator |
Contact Type | Organization |
Contact Name | Sanborn Map Company Inc. |
Publish Date | |
Extent Type | Discrete |
Extent Start Date/Time | 2016 |
Extent End Date/Time | |
Scale Denominator | 1200 |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Source Contribution |
The post processed lidar data has been projected and oriented in the specified coordinate system as an un-classified point cloud. |
Citation Title | Tile Definition |
---|---|
Contact Role Type | Originator |
Contact Type | Organization |
Contact Name | State of Michigan |
Publish Date | |
Extent Type | Discrete |
Extent Start Date/Time | 2016 |
Extent End Date/Time | |
Scale Denominator | 1200 |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
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. |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Process Steps
Process Step Number | 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 | 2016-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 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 | 2016-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 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 | 2016-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 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 | 2016-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 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 | 2016-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 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 | 2016-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 7 |
---|---|
» 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) |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Acquisition Information
Instruments
Instrument Unavailable Reason |
---|
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Platforms
Platform Unavailable Reason |
---|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
FAQs
Date | |
---|---|
Author | |
Question | |
Answer |
Child Items
Rubric scores updated every 15m
Score | Type | Title |
---|---|---|
Related Items
Item Type | Relationship Type | Title |
---|---|---|
Catalog Details
Catalog Item ID | 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 Workflow State | Published / External |
Metadata Last Review Date | 2022-03-16 |
Metadata Review Frequency | 1 Year |
Metadata Next Review Date | 2023-03-16 |
Tags |
---|