2014 MiSAIL Lidar DEM: Van Buren County (MI)
OCM Partners
Data Set
(DS)
| ID: 52310
| Published / External
Created: 2018-03-30
|
Last Modified: 2024-01-10
Project (PRJ) | ID: 49404
ID: 52310
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2014 MiSAIL Lidar DEM: Van Buren County (MI) |
---|---|
Short Name | mi2014_van_buren_dem_m8515_metadata |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2015 |
* » Abstract |
This metadata record describes the hydro-flattened bare earth digital elevation model (DEM) derived from the classified LiDAR data for the 2014 Michigan LiDAR project covering approximately 623 square miles, in which its extents cover Van Buren County. The NOAA Office for Coastal Management (OCM) downloaded the MI_13Co-VanBurrenCo_2015 Digital Elevation Model (DEM) files from this USGS site: ftp://rockyftp.cr.usgs.gov/vdelivery/Datasets/Staged/Elevation/OPR/ and processed the data to the Data Access Viewer (DAV) and https. In addition to these bare earth Digital Elevation Model (DEM) data, the lidar point data that these DEMs were created from, are also available. These data are available for custom download at the link provided in the URL section of this metadata record. 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 and bare earth DEM data products are suitable for 1 foot contour generation. USGS LiDAR Base Specification 1.0, QL2. 18.13 cm FVA. |
Notes | |
Other Citation Details | |
• Supplemental Information |
The following are the USGS lidar fields in JSON: { "ldraccur" : { "ldrchacc" : "1.0", "rawfva" : "0.161", "clsfva" : "0.131", "clscva" : "0.192", "clssvas" : { "svalctyp" : "Urban", "svavalue" : "0.159" }, "clssvas" : { "svalctyp" : "LowVeg", "svavalue" : "0.215" }, "clssvas" : { "svalctyp" : "MedVeg", "svavalue" : "0.192" }, "clssvas" : { "svalctyp" : "HighVeg", "svavalue" : "0.196" } }} |
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 |
None | ALS70 |
None | Bare Earth |
None | beach |
None | DEM |
None | erosion |
None | Grid |
None | IMG |
None | mapping |
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 | Model (digital) |
• Entity Attribute Overview | |
Entity Attribute Detail Citation |
FEMA Specification Version QL2 meeting 9.25cm 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 | 2018 |
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 | 2018 |
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 | 2018 |
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 | 2018 |
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.363315 |
---|---|
* » E° Bound | -85.76266 |
* » N° Bound | 42.426066 |
* » S° Bound | 42.069443 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Range |
---|---|
* » Start | 2014-12-07 |
End | 2014-12-23 |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Spatial Information
Spatial Resolution
Angular Distance | |
---|---|
Angular Distance Units | |
Horizontal Distance | 3.0 |
Horizontal Distance Units | Foot |
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 | EPSG:8228 | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Horizontal Resolution |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Vertical Resolution |
|||||||||||||||||||||||||||||
|
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 custom and bulk 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=8515 |
Distributor | NOAA Office for Coastal Management (NOAA/OCM) (2018 - Present) |
File Name | Customized Download |
Description |
Create custom data files. |
File Date/Time | |
File Type (Deprecated) | Zip |
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.us-east-1.amazonaws.com/dem/MI_Van_Buren_DEM_2014_8515/index.html |
Distributor | NOAA Office for Coastal Management (NOAA/OCM) (2018 - Present) |
File Name | Bulk Download |
Description |
Bulk download of data files. |
File Date/Time | |
File Type (Deprecated) | GeoTIFF |
Distribution Format | GeoTIFF |
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 |
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 |
Archive Information
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
URLs
URL | https://coast.noaa.gov/ |
---|---|
Name | NOAA's Office for Coastal Management (OCM) website |
URL Type | Online Resource |
File Resource Format | HTML |
Description |
Information on the NOAA Office for Coastal Management (OCM) |
URL | https://coast.noaa.gov/dataviewer/ |
---|---|
Name | NOAA's Office for Coastal Management (OCM) Data Access Viewer (DAV) |
URL Type | Online Resource |
File Resource Format | HTML |
Description |
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. |
URL | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12b/8514/supplemental/mi2014_van_buren_m8514.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/geoid12b/8514/breaklines/ |
---|---|
Name | |
URL Type | Online Resource |
File Resource Format | |
Description |
Hydro breaklines |
URL | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=8514 |
---|---|
Name | |
URL Type | Online Resource |
File Resource Format | |
Description |
Link to custom download the lidar point data from which these raster Digital Elevation Model (DEM) data were created. |
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 Van Buren LiDAR 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 FVA, SVA, and CVA were computed. The vertical accuracy was tested with independent survey check points located in various terrain types within Van Buren County. 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 9.25 cm (18.13 cm or better @ 95 percent confidence level) 0.067m RMSE, or 0.131m FVA @ 95 percent Confidence Interval The FVA was tested using 38 independent survey check points located in flat terrain types within Area 5. The survey checkpoints were distributed throughout the block area. The 38 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.067 m. AccuracyZ has been tested to meet 9.25 cm Fundamental 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)/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 5 areas. Area 5 includes Allegan, Berrien, and Van Buren. Accuracy results are reported for Area 5. |
» 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 | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | Discrete |
Extent Start Date/Time | 2015 |
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.2 or v1.3, Point Record Format 1 |
Citation Title | Ground control |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | 2010-01-01 |
Extent Type | Discrete |
Extent Start Date/Time | 2015 |
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 | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | Discrete |
Extent Start Date/Time | 2015 |
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 | Originator |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Scale Denominator | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Source Contribution |
Citation Title | Post processed GPS/INS |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | Discrete |
Extent Start Date/Time | 2015 |
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 | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | Discrete |
Extent Start Date/Time | 2015 |
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 | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | Discrete |
Extent Start Date/Time | 2015 |
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 | 2015-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 ALS80 w/MPiA LiDAR instrument an integrated IPAS20 GPS/INS system mounted within a Aero Commander twin engine airplane. |
Process Date/Time | 2015-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 Intertial 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 | 2015-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 | 2015-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 | 2015-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 6 |
---|---|
» Description |
The bare earth points of the processed lidar data are then output to a DEM tile format. The DEM is compared to the ground control and elevation differences between the surface and surveyed elevation are recorded in tabular form. Vertical accuracy statistics are then developed to produce vertical RMSE and overall accuracy estimates and reports. |
Process Date/Time | 2015-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 7 |
---|---|
» Description |
The NOAA Office for Coastal Management (OCM) downloaded the MI_13Co-VanBurrenCo_2015 Digital Elevation Model (DEM) files from this USGS site: ftp://rockyftp.cr.usgs.gov/vdelivery/Datasets/Staged/Elevation/OPR/ The NOAA Office for Coastal Management (OCM) downloaded 2945 raster files from the USGS rockyftp site. The data were in MI State Plane South coordinates and NAVD88 (Geoid12A) elevations in feet. The bare earth raster files were at a 3 ft grid spacing. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. Converted the raster files from img format to cloud optimized geotiff format. |
Process Date/Time | 2023-07-03 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 | 52310 |
---|---|
Metadata Record Created By | Rebecca Mataosky |
Metadata Record Created | 2018-03-30 16:01+0000 |
Metadata Record Last Modified By | Kirk Waters |
» Metadata Record Last Modified | 2024-01-10 19:01+0000 |
Metadata Record Published | 2024-01-10 |
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 |
---|