2004 Saginaw Bay, Lake Huron, Michigan Coastline LiDAR
Office for Coastal Management
Data Set
(DS)
| ID: 48193
| Published / External
Created: 2017-11-14
|
Last Modified: 2022-08-09
Project (PRJ) | ID: 37231
ID: 48193
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2004 Saginaw Bay, Lake Huron, Michigan Coastline LiDAR |
---|---|
Short Name | mi2004_m18_metadata |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2006-10-19 |
* » Abstract |
This metadata document describes the collection and processing of Light Detection and Ranging (LIDAR) data over an area along the coast of Saginaw Bay, Lake Huron, Michigan. Data was collected at a nominal two (2) meter post spacing between points. Two elevation data sets were compiled in this project, first surface returns, in which features that are above the ground, such as buildings, bridges, tree tops, etc. have not been eliminated and a Bare Earth Data set. Original contact information: Contact Org: NOAA Office for Coastal Management Phone: 843-740-1202 Email: coastal.info@noaa.gov |
* Purpose |
This LIDAR collected under this task order has been supplied to the NOAA, Office for Coastal Management (OCM) to support local Coastal Zone Managers in their decision-making processes. |
Notes |
10216 |
Other Citation Details | |
• Supplemental Information |
The 2004 Saginaw Bay, Michigan Lidar Data Validation Report may be viewed at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/18/supplemental/index.html |
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 > TOPOGRAPHICAL RELIEF MAPS |
Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > OCEANS > BATHYMETRY/SEAFLOOR TOPOGRAPHY > SEAFLOOR TOPOGRAPHY |
Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > OCEANS > COASTAL PROCESSES > COASTAL ELEVATION |
ISO 19115 Topic Category | elevation |
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 |
Stratum Keywords
Thesaurus | Keyword |
---|---|
Instrument Keywords
Thesaurus | Keyword |
---|---|
Platform Keywords
Thesaurus | Keyword |
---|---|
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 | |
• Maintenance Frequency | None Planned |
Maintenance Note | |
» Data Presentation Form | |
• Entity Attribute Overview | |
Entity Attribute Detail Citation | |
Entity Attribute Detail URL | |
Distribution Liability |
Any conclusions drawn from the analysis of this information are not the responsibility of NOAA, the Office for Coastal Management or its partners. |
Data Set Credit | EarthData International of Maryland, LLC 7320 Executive Way Frederick, MD 21704 1-301-948-8550 1-301963-2064 |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2006-10-19 |
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 | 2006-10-19 |
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 | 2006-10-19 |
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 | 2006-10-19 |
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 | -83.969892 |
---|---|
* » E° Bound | -82.946673 |
* » N° Bound | 44.345024 |
* » S° Bound | 43.551754 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Range |
---|---|
* » Start | 2004-04-27 |
End | 2004-05-04 |
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? | Yes |
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 |
This data can be obtained on-line at the following URL: https://coast.noaa.gov/dataviewer; |
• » 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 | |
---|---|
» Download URL | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=18 |
Distributor | |
File Name | Customized Download |
Description |
Create custom data files by choosing data area, product type, map projection, file format, datum, etc. |
File Date/Time | |
File Type (Deprecated) | |
Distribution Format | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
» Download URL | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/18/index.html |
Distributor | |
File Name | Bulk Download |
Description |
Simple download of data files. |
File Date/Time | |
File Type (Deprecated) | |
Distribution Format | |
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 |
URLs
URL | https://coast.noaa.gov/dataviewer |
---|---|
Name | |
URL Type | Online Resource |
File Resource Format | |
Description |
URL | https://coast.noaa.gov |
---|---|
Name | |
URL Type | Online Resource |
File Resource Format | |
Description |
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 | 2016-05-23 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Date that the source FGDC record was last modified. |
Activity Time | 2017-11-14 |
---|---|
Activity Type | |
Responsible Party | |
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 Time | 2018-02-08 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Partial upload of Positional Accuracy fields only. |
Activity Time | 2018-03-13 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Partial upload to move data access links to Distribution Info. |
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 |
|
---|
Data Quality
Representativeness | |
---|---|
Accuracy | |
Analytical Accuracy | |
Horizontal Positional Accuracy |
The horizontal accuracy of this lidar data was not assessed. The high vertical accuracy is indicative of good horizontal accuracy, though slight horizontal inaccuracies are difficult to detect using these check points because they were located in relatively flat terrain. |
Vertical Positional Accuracy |
Thirty check points collected on generally flat open terrain with a reported accuracy of 0.03 meters were compared to the lidar points. The Guidelines for Digital Elevation Data by NDEP recommends interpolation from a surface generated from a triangulated irregular network (TIN) derived from the lidar point data surrounding the check point for assessing the accuracy of mass points. This method was employed in this evaluation. Elevation values at the location of each of the 30 check points were interpolated from the triangulated bare earth point data. The vertical error at each check point location was calculated by subtracting the interpolated lidar elevation value from the check point elevation value. The 95th percentile error was used to calculate the overall accuracy of the lidar data because the errors were distributed non-parametrically. ; Quantitative Value: 0.26 meters, Test that produced the value: Tested 0.26 meter fundamental vertical accuracy at 95th percentile in open terrain. The fundamental vertical accuracy at the 95th percentile was calculated with the following equation: Vertical Accuracy = 95th percentile error. |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure |
Cloud Cover: 0 |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
Completeness Report |
None available |
Conceptual Consistency |
The data were evaluated to ensure no voids exist and the data covers the entire project area. |
» 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 | Ground Control Survey of Saginaw Bay, Michigan |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | 2004-09-27 |
Extent Type | Range |
Extent Start Date/Time | 2004-06-08 |
Extent End Date/Time | 2004-06-10 |
Scale Denominator | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Source Contribution |
Twenty-four (24) ground control points were established by Terrasurv, Inc. using GPS for vertical and horizontal coordinate values. Ground control references NAD83, NAVD88, Geoid99, in meters. An additional thirty (30) independent check ground control points were acquired by Terrasurv, Inc. and provided directly to NOAA, OCM to support an independent analysis of the accuracy of the Lidar data. | Source Geospatial Form: Model | Type of Source Media: Electronic mail system |
Citation Title | Saginaw Bay, Michigan LIDAR Scanning Project |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | 2004-09-27 |
Extent Type | Range |
Extent Start Date/Time | 2004-04-27 |
Extent End Date/Time | 2004-05-04 |
Scale Denominator | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Source Contribution |
The project area was flown using EarthData Aviation's Piper Navajo aircraft with tail number 62912. LIDAR data was captured using an ALS40 LIDAR system, including an inertial measuring unit (IMU) and a dual frequency GPS receiver. The acquisition was flown during the period of April 27 2004 through May 4, 2004. One ground based GPS receiver was in constant operation during each flight. During the data acquisition, all receivers collected phase data at an epoch rate of 1 Hz. All GPS phase data was post processed with continuous kinematic survey techniques using "On the Fly" (OTF) integer ambiguity resolution. The GPS data was processed with forward and reverse processing algorithms. The results from each process, using the data collected at the airport, were combined to yield a single fixed integer phase differential solution of the aircraft trajectory. | Source Geospatial Form: Model | Type of Source Media: CD-ROM |
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 |
EarthData has developed a unique method for processing LIDAR data. The algorithms for filtering data were utilized within EarthData's proprietary software and commercial software written by TerraSolid. This software suite of tools provides efficient processing for small to large-scale projects and has been incorporated into ISO 9001 compliant production work flows. POINT CLOUD The following is a step-by-step breakdown of the process utilized to produce the variably-spaced point cloud surface data set. 1. Processing of the LIDAR data begins with refinement of the initial boresight alignment parameters provided by EarthData Aviation in the LITES configuration file delivered with the raw data. The technician also verifies that there are no voids, and that the data covers the entire project area. Calibration is accomplished using the tri-directional flight lines over the project airport, which is generally flat and free of major obstructions, trees or brush. Two overlapping bi-directional lines are flown along the length of the runway, and the cross flight line is perpendicular to both. All three lines are examined to ensure that they agree, within expected system tolerances, in the overlapping areas. The technician will review flight lines and locate the areas that contained systematic errors or distortions that were introduced by the LIDAR sensor. 2. Systematic distortions highlighted in step 1 were removed and the data was re-inspected. Corrections and adjustments can involve the application of angular deflection or compensation for curvature of the ground surface that can be introduced by crossing from on type of land cover to another. 3. All flight lines are processed with the refined calibration parameters obtained thru steps 1 and 2. All flight line are examined to ensure that they agree, within expected system tolerances, in the overlapping areas (side lap). 4. The LIDAR data for each flight line was trimmed in batch for the removal of the overlap areas between flight lines. The data was checked against a control network to ensure that vertical requirements were maintained. Conversion to the client-specified datum and projections were then completed. The LIDAR flight line data sets were then segmented into adjoining tiles for batch processing and data management. 5. The data was then edited for Blunder removal. 6. The data was processed interactively by the operator using LIDAR editing tools. During this final phase the operator generated a TIN based on a desired thematic layer to evaluate the automated classification performed in step 5. This allowed the operator to quickly re-classify points from one layer to another and recreate the TIN surface to see the effects of edits. The use of geo-referenced images was toggled on or off to aid the operator in identifying problem areas. The data was also examined with an automated profiling tool to aid the operator in the reclassification. 7. The data was separated into (1) variably-spaced point cloud in LAS files. The files were written to PC readable CD-ROM. |
Process Date/Time | 2004-09-27 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 2 |
---|---|
» Description |
The NOAA Office for Coastal Management (OCM) received files in LAS format. The files contained lidar intensity and elevation measurements. OCM performed the following processing on the data to make it available within the Lidar Data Retrieval Tool (LDART): 1. The data were projected from UTM to geographic decimal degrees using the General Cartographic Transformation Package. 2. The las files were sorted by latitude and the las header fields were completed. |
Process Date/Time | 2005-01-05 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 3 |
---|---|
» Description |
For data management purposes, the Office for Coastal Management converted the data from NAVD88 elevations to ellipsoid elevations using Geoid 03. |
Process Date/Time | 2008-01-01 00:00:00 |
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 |
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 | 48193 |
---|---|
Metadata Record Created By | Anne Ball |
Metadata Record Created | 2017-11-14 14:19+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 | OCM |
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 |
---|