ISO Table View Alternate Views: Get Data, FAQ, ISO Rubric, DOI Rubric, CSW, HTML, Components, XML

Metadata Identifier: gov.noaa.csc.maps:2010_USACE_AL_FL_m1064

Aggregation Info | Bands | Citations | Constraints | Coverage Descriptions | Dimensions | Extents | Formats | Geographic Bounding Box
Georectified Information | Georeferenceable Information | Identifiers | Instruments | Mediums | OnlineResources | Operations
Platforms | Process Steps | Range Elements | Reference Systems | Responsible Parties | Series | Sources | Spatial Grids | Temporal Extents

MD_DataIdentification

Count Component Title Abstract
1 2010 US Army Corps of Engineers (USACE) Joint Airborne Lidar Bathymetry Technical Center of Expertise (JALBTCX) Topobathy Lidar: Alabama Coast and Florida Gulf Coast These files contain topographic and bathymetric lidar data collected by the HawkEye system along the coast of Alabama and the gulf coast of Florida. The data were collected January - March 2010. The area of coverage includes the coastline in Baldwin and Mobile Counties in Alabama and the following Florida counties: Bay, Escambia, Franklin, Gulf, Okaloosa, Santa Rosa, and Walton. HawkEye integrates topographic and bathymetric lidar sensors with a digital camera on a single remote sensing platform for use in coastal mapping and charting activities. The topographic lidar sensor has a pulse repetition rate of 64 kHZ at 1064 nm (red wavelength). The bathymetric lidar sensor has a pulse repetition rate of 4 kHz at 532 nm (green wavelength). Native lidar data is not generally in a format accessible to most GIS systems. Specialized in-house and commercial software packages are used to process the native lidar data into 3-D positions that can be imported into GIS software for visualization and further analysis. The data were provided to NOAA CSC in decimal degrees of latitude and longitude, referenced to the NAD83 ellipsoid and in meters. The National Geodetic Survey's (NGS) GEOID03 model was used to transform the vertical positions from ellipsoid to orthometric heights referenced to the North American Vertical Datum of 1988 (NAVD88). The format of the file was LAS version 1.0. For data storage and Digital Coast provisioning purposes, NOAA CSC converted the orthometric heights (NAVD88) back to ellipsoidal heights using GEOID03.
Top

SV_Identification

none found
Top

CI_Citation

Count Component Title Date Citation Identifier
1 2010 US Army Corps of Engineers (USACE) Joint Airborne Lidar Bathymetry Technical Center of Expertise (JALBTCX) Topobathy Lidar: Alabama Coast and Florida Gulf Coast
  • 2011-09-01
3 None
    1 North American Datum 1983
    • 2007-01-19
    Top

    CI_Series

    none found
    Top

    CI_ResponsibleParty

    Count Component Individual Organization Position Email Role Linkage
    1 resourceProvider http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:crs:EPSG::4269
    1 BLOM Aerofilms Data Production Manager info@blomaerofilms.com processor
    1 NOAA CSC (originator) DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce csc.info@noaa.gov originator
    1 NOAA CSC (publisher) DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce csc.info@noaa.gov publisher
    1 NOAA CSC(distributor) DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce csc.info@noaa.gov distributor
    1 NOAA CSC (processor) DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce csc.info@noaa.gov processor
    1 EPSG Registry European Petroleum Survey Group publisher http://www.epsg-registry.org/
    1 Mike Sutherland(author) Mike Sutherland DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce mike.sutherland@noaa.gov author
    1 Mike Sutherland Mike Sutherland DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce mike.sutherland@noaa.gov distributor
    1 Pamela Grothe DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce processor
    1 JALBTCX (originator) US Army Corps of Engineers (USACE) Joint Airborne Lidar Bathymetry Technical Center of eXpertise (JALBTCX) Data Production Manager JALBTCX@usace.army.mil originator
    1 JALBTCX (pointOfContact) US Army Corps of Engineers (USACE) Joint Airborne Lidar Bathymetry Technical Center of eXpertise (JALBTCX) Data Production Manager JALBTCX@usace.army.mil pointOfContact
    Top

    CI_OnlineResource

    Count Component Linkage Name Description Function
    1 http://www.epsg-registry.org/ European Petroleum Survey Group Geodetic Parameter Registry Registry that accesses the EPSG Geodetic Parameter Dataset, which is a structured dataset of Coordinate Reference Systems and Coordinate Transformations. search
    1 http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:crs:EPSG::4269 NAD83 Link to Geographic Markup Language (GML) description of reference system. information
    Top

    MD_Identifier or RS_Identifier

    Count Component Code
    1 Ellipsoid in Meters
    1 urn:ogc:def:crs:EPSG::4269
    Top

    EX_Extent

    Bounding Box Temporal Extent
    Count Component Description West East North South Start End
    1 -88.356612 -84.331479 30.404759 29.586813 2010-01-01 2010-03-01
    Top

    EX_GeographicBoundingBox

    Count Component West East North South
    1 -88.356612 -84.331479 30.404759 29.586813
    Top

    EX_TemporalExtent

    Count Component Start End
    1 2010-01-01 2010-03-01
    Top

    MD_Format

    Count Component Name Version specification
    1 LAZ
    Top

    MD_Medium

    none found
    Top

    MD_Constraints

    Count Component Use Limitation
    1 Lidar Use Limitation These data depict the elevations at the time of the survey and are only accurate for that time. 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. Any conclusions drawn from analysis of this information are not the responsibility of NOAA or any of its partners. These data are NOT to be used for navigational purposes.
    Top

    MD_ReferenceSystem

    Count Component Code Authority Title
    1 Ellipsoid Ellipsoid in Meters
    1 NAD83 urn:ogc:def:crs:EPSG::4269 North American Datum 1983
    Top

    MD_GridSpatialRepresentation

    none found
    Top

    MD_Georeferenceable or MI_Georeferenceable

    none found
    Top

    MD_Georectified or MI_Georectified

    none found
    Top

    MD_Dimension

    none found
    Top

    MD_CoverageDescription or MI_CoverageDescription

    none found
    Top

    MD_Band or MI_Band

    none found
    Top

    MI_RangeElementDescription

    none found
    Top

    MD_AggregateInformation

    none found
    Top

    LE_Source or LI_Source

    none found
    Top

    LE_ProcessStep or LI_ProcessStep

    Count Component DateTime Description
    1 These data were collected using the Hawk Eye system. It is owned by BlomUK and operated through contract. The system collects topographic lidar data at 64 kHz, bathymetric lidar data at 4 kHz and RGB imagery covering the LiDAR area. Aircraft position, velocity and acceleration information are collected through a combination of IRS and GPS system (POS AV 410). All raw data streams are transferred to the office for downloading and processing in Coastal Survey Studio software. Aircraft position data are processed using Applanix software and the results are combined with the lidar data to produce 3-D positions for each lidar shot. Upon inspection and QC/QC in the software packages TerraSolid and Fledermaus, anomalous data are flagged as invalid. Especially designed HawkEye tool then converts all valid data from ellipsoid to orthometric height based on NGS GEOID03 model and exports topographic data as a series of ASCII files with a single file per flightline per 5 km box. The flightline ASCII files are imported into TerraScan <v10> module within Microstation <V8i>. The data are thinned to eliminate duplicate points. A customized classification macro is used to distinguish ground points (2) and unclassified points (1). The classification results are QC'd and any misclassified points are manually edited.
    1 2011-09-01T00:00:00 The NOAA Coastal Services Center (CSC) received unclassified bathymetric files in ASCII format and classified (ASPRS classifications of 1 (unclassified) and 2 (ground)) topographic files in las format. The files contained LiDAR intensity and elevation measurements. CSC performed the following processing on the data for data storage and Digital Coast provisioning purposes: 1. The bathymetric lidar points were converted from ASCII format to las format. 2. All data were converted from NAVD88 heights to ellipsoid heights using GEOID03. 3. The bathymetric lidar data points were classified according to the ASPRS LAS 1.2 classification scheme as 11 (bathymetry). 4. The LAS header fields were sorted by latitude and updated.
    1 2011-09-22T00:00:00 The NOAA National Geophysical Data Center (NGDC) received lidar data files via ftp transfer from the NOAA Coastal Services Center. The data are currently being served via NOAA CSC Digital Coast at http://www.csc.noaa.gov/digitalcoast/. The data can be used to re-populate the system. The data are archived in LAS or LAZ format. The LAS format is an industry standard for LiDAR data developed by the American Society of Photogrammetry and Remote Sensing (ASPRS); LAZ is a loseless compressed version of LAS developed by Martin Isenburg (http://www.laszip.org/). The data are exclusively in geographic coordinates (either NAD83 or ITRF94). The data are referenced vertically to the ellipsoid (either GRS80 or ITRF94), allowing for the ability to apply the most up to date geoid model when transforming to orthometric heights.
    Top

    MI_Operation

    none found
    Top

    MI_Platform

    none found
    Top

    MI_Instrument

    none found
    Top