2010 U.S. Geological Survey (USGS) Topographic LiDAR: Mobile Bay, AL

OCM Partners
Data Set (DS) | ID: 50114 | Published / External
Created: 2017-11-15   |   Last Modified: 2022-08-09

Parent: Lidar - partner (no harvest)
Project (PRJ) | ID: 49401

ID: 50114
Data Set (DS)

* Discovery
• First Pass
» Metadata Rubric

Item Identification

* » Title 2010 U.S. Geological Survey (USGS) Topographic LiDAR: Mobile Bay, AL
Short Name usgs2010_MobileBay_AL_lidar_m1426_metadata
* Status Completed
Creation Date  
Revision Date  
• Publication Date 2013-01
* » Abstract

USGS Contract: G10PC00026

Task Order Number: G10PD00578

LiDAR was collected at a nominal pulse spacing of 2.0 meters for a 700 square mile area to

the east of Mobile Bay, either not previously surveyed using LiDAR sensors or where the collected

data was poor, while no snow was on the ground and rivers were at or below normal levels.

The goal of the NGOM LiDAR project in the post-Katrina environment is to provide scientific

knowledge and tools required to make optimal decisions about land resource use, management

practices, and future development in the northern Gulf of Mexico coastal zone. This regional

LiDAR elevation mapping data will be used for modeling, predicting landscape change, promoting

restoration of ecosystems, and mitigating risks associated with anthropomorphic and natural hazards.
* Purpose

Classified LAS files are used to show the manually reviewed bare earth surface. Any additional

classification is provided via automated macro functionality from proprietary Photo Science TerraScan macros.

These additional classifications include Class 4 - Medium Vegetation and Class 5 - High Vegeation. This

allows the user to create Intensity Images, Break Lines, Raster DEM, and Triangular Irregular Networks.
Notes

10758
Other Citation Details
• Supplemental Information

The third-party QA report for this data set may be accessed at:

https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/1426/supplemental/usgs2010_MobileBay_AL_LidarReport.doc

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

https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/1426/supplemental/usgs2010_MobileBay_AL_footprint.kmz
DOI (Digital Object Identifier)  
DOI Registration Authority  
DOI Issue Date  

Keywords

Theme Keywords

Thesaurus Keyword
ISO 19115 Topic Category elevation
   
   
   

Temporal Keywords

Thesaurus Keyword
   
   
   

* Spatial Keywords

Thesaurus Keyword
   
   
   

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 As Needed
Maintenance Note
» Data Presentation Form las
• Entity Attribute Overview

LiDAR points in LAS 1.2 format
Entity Attribute Detail Citation

none
Entity Attribute Detail URL  
Distribution Liability

Any conclusions drawn from the analysis of this information are not the responsibility

of Photo Science, USGS, the Office for Coastal Management or its partners.
Data Set Credit Photo Science, Inc. flew the LiDAR and processed the data.

Support Roles

» At least one Distributor Org, one Metadata Contact, one Point of Contact, and one Data Steward should be listed.
* » Support Role Data Steward
* » Date Effective From 2013-01
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 2013-01
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 2013-01
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 2013-01
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 -87.915552
* » E° Bound -87.503212
* » N° Bound 30.856364
* » S° Bound 30.28702
* » Description

Extent Group 1 / Vertical Extent

EPSG Code
Vertical Minimum
Vertical Maximum

Extent Group 1 / Time Frame 1

* » Time Frame Type Range
* » Start 2010-02-20
End 2010-02-25
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
Dimension Type
Size
Resolution
Resolution Units
Resolution Type
Description

Axis Dimension
Dimension Type
Size
Resolution
Resolution Units
Resolution Type
Description

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
Horizontal Encoding Method
Latitude Resolution
Longitude Resolution
Coordinate X Resolution
Coordinate Y Resolution
Row Resolution
Column Resolution
Horizontal Units
Distance Resolution
Distance Units
Bearing Resolution
Bearing Units
Reference Direction
Reference Meridian

Vertical Resolution
Vertical Encoding Method
Vertical Resolution
Vertical Units

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/#/lidar/search/where:ID=1426

;
• » Data Access Constraints

None
• Data Use Constraints

Users should be aware that temporal changes may have occurred since this data set was collected

and some parts of this data may no longer represent actual surface conditions. Users should not use

this data for critical applications without a full awareness of its limitations. These data

depict the heights at the time of the survey and are only accurate for that time.
Metadata Access Constraints
Metadata Use Constraints

Distribution Information

Start Date  
» Download URL https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=1426
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/1426/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

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/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 https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/1426/supplemental/usgs2010_MobileBay_AL_footprint.kmz
Name Browse Graphic
URL Type Browse Graphic
File Resource Format kmz
Description

This graphic shows the lidar coverage for Baldwin and Escambia Counties in Alabama.
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

MicroStation Version 8; TerraScan Version 10; Optech DASHMap 4.1801; TerraModeler Version 10;

GeoCue Version 6.1.21.4; ESRI ArcGIS 9.3; QT Modeler v 7.0.3; Windows XP Operating System

Data Quality

Representativeness
Accuracy

The project area requires LiDAR to be collected on average of 2.0 meter point spacing

or better and vertical accuracy of 15 centimeters RMSE or better to support 2' contour

generation when combined with breaklines.
Analytical Accuracy
Horizontal Positional Accuracy
Vertical Positional Accuracy

Classified LAS files were tested by Photo Science for both vertical and horizontal

accuracy. All data is seamless from one tile to the next, no gaps or no data areas.

The vertical unit of the data file is in decimal feet with 2-decimal point precision.

; Quantitative Value: 0.0013 meters, Test that produced the value: RMSE in meters
Quantitation Limits
Bias
Comparability
Completeness Measure
Precision
Analytical Precision
Field Precision
Sensitivity
Detection Limit
Completeness Report

Datasets contain complete coverage of tiles.
Conceptual Consistency

Classified LAS files were tested by Photo Science for both vertical and horizontal accuracy.

All data is seamless from one tile to the next, no gaps or no data areas.
» 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 LiDAR
Contact Role Type  
Contact Type  
Contact Name  
Publish Date 2010-01-01
Extent Type Range
Extent Start Date/Time 2010-02-20
Extent End Date/Time 2010-04-28
Scale Denominator  
Citation URL  
Citation URL Name  
Citation URL Description
Source Contribution

LiDAR points were used to produce the deliverables. | Source Geospatial Form: digital data | Type of Source Media: hard drive
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

Applanix software was used in the post processing of the

airborne GPS and inertial data that is critical to the positioning

and orientation of the sensor during all flights. POSPac MMS provides

the smoothed best estimate of trajectory (SBET) that is necessary

for Optech's post processor to develop the point cloud from the

LiDAR missions. The point cloud is the mathematical three dimensional

collection of all returns from all laser pulses as determined from

the aerial mission. At this point this data is ready for analysis,

classification, and filtering to generate a bare earth surface model

in which the above ground features are removed from the data set.

The point cloud was manipulated within the Optech software; GeoCue,

TerraScan, and TerraModeler software was used for the automated

data classification, manual cleanup, and bare earth generation from

this data. Project specific macros were used to classify the ground

and to remove the side overlap between parallel flight lines.

All data was manually reviewed and any remaining artifacts removed

using functionality provided by TerraScan and TerraModeler.

All Class 2 LiDAR data inside of the collected breaklines were then classified to Class 9

using TerraScan macro functionality. A buffer of 1 meter was also used around each hydro flattened

feature.

The breakline files were then translated to ESRI Shapefile format using ESRI conversion tools.

Data was then run through additional macros to ensure deliverable classification

levels matching LAS ASPRS Classification structure. GeoCue functionality was then

used to ensure correct LAS Version. In house software was used as a final

QA/QC check to provide LAS Analysis of the delivered tiles.
Process Date/Time 2010-01-01 00:00:00
Process Contact  
Phone (Voice)  
Email Address  
Source LiDAR
Process Step Number 2
» Description

The NOAA Office for Coastal Management (OCM) received topographic files in LAS format. The files contained lidar

elevation and intensity measurements. The data were received in UTM Zone 16 (NAD83) coordinates

and were vertically referenced to NAVD88 using the Geoid09 model. The vertical units of the data were

meters. OCM performed the following processing for data storage and Digital Coast provisioning purposes:

1. The topographic las files were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid09.

2. The horizontal coordinate system was converted from UTM (meters) to Geographic (decimal degrees).
Process Date/Time 2012-12-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  
Identifier  
Identifier  
Identifier
Docucomp UUID
Description

Mounted Instruments
Identifier  
Identifier  
Identifier  
Identifier
Docucomp UUID
Description

Mounted Instruments
Identifier  
Identifier  
Identifier  

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 50114
Metadata Record Created By Anne Ball
Metadata Record Created 2017-11-15 15:24+0000
Metadata Record Last Modified By SysAdmin InPortAdmin
» Metadata Record Last Modified 2022-08-09 17:11+0000
Metadata Record Published 2022-03-16
Owner Org OCMP
Metadata Publication Status Published Externally
Do Not Publish? N
Metadata Workflow State Published / External
Metadata Last Review Date 2022-03-16
Metadata Review Frequency 1 Year
Metadata Next Review Date 2023-03-16
Tags