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

Metadata Identifier: gov.noaa.csc.maps:usgs2010_AtchafalayaBasinLouisiana_m1433

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 U.S. Geological Survey Topographic LiDAR: Atchafalaya Basin, Louisiana The Light Detection and Ranging (LiDAR) dataset is a survey of the Atchafalaya Basin in south-central Louisiana. The entire survey area encompasses 981 square miles. The LiDAR point cloud was flown at a nominal post spacing of 1.0 meters for unobscured areas. The LiDAR data is in compliance with the U.S. Geological Survey National Geospatial Program Guidelines and Base Specifications, Version 13-ILMF 2010. The Flightlines were acquired by Northrop Grumman, 3001 Operating Unit, which required 10 subsequent missions between December 2, 2010, and December 7, 2010. Northrop Grumman classified the data into the following ASPRS compliant classes: Class 1: Processed, but unclassified Class 2: Bare Earth Ground Class 3: Low Vegetation Class 4: Medium Vegetation (also used for manual classification of vegetation returns) Class 5: High Vegetation Class 6: Buildings and man-made structures Class 7: Noise (low or high, manually identified) Class 9: Water Class 10: Ignored Ground (Breakline Proximity) Class 13: Withheld (outliers, blunders, etc.)
Top

SV_Identification

none found
Top

CI_Citation

Count Component Title Date Citation Identifier
1 2010 U.S. Geological Survey Topographic LiDAR: Atchafalaya Basin, Louisiana
  • 2013-01-01
2 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 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 DOI/USGS, United States Geological Survey, U.S. Department of the Interior originator
    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 Mike Sutherland (processor) Mike Sutherland DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce mike.sutherland@noaa.gov processor
    1 Northrop Grumman, 3001 Operating Unit Northrop Grumman, 3001 Operating Unit LiDAR Department Jochen.Floesser@ngc.com processor
    1 Patrick Emmett United States Geological Survey, National Geospatial Technical Operations Center (NGTOC) USGS NGTOC pemmett@usgs.gov 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 -91.880079 -91.156365 30.558588 29.670848 2010-12-02 2010-12-07
    Top

    EX_GeographicBoundingBox

    Count Component West East North South
    1 -91.880079 -91.156365 30.558588 29.670848
    Top

    EX_TemporalExtent

    Count Component Start End
    1 2010-12-02 2010-12-07
    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 2010-12-01T00:00:00 The ABGPS, inertial measurement unit (IMU), and raw scans are collected during the LiDAR aerial survey. The ABGPS monitors the xyz position of the sensor and the IMU monitors the orientation. During the aerial survey, laser pulses reflected from features on the ground surface are detected by the receiver optics and collected by the data logger. GPS locations are based on data collected by receivers on the aircraft and base stations on the ground. The ground base stations are placed no more than 40 km radius from the flight survey area.
    1 2010-12-01T00:00:00 The ABGPS, IMU, and raw scans are integrated using proprietary software developed by Optech and delivered with the Optech ALTM 213 System. The resultant file is in a LAS binary file format. The LAS version 1.2 file format can be easily transferred from one file format to another. It is a binary file format that maintains information specific to the LiDAR data (return number, intensity value, xyz, etc.). The resultant points are produced in the NAD83 UTM Zone 15 coordinate system, with units in meters and referenced to the NAVD88 datum. The LiDAR mass points were processed in American Society for Photogrammetry and Remote Sensing LAS 1.2 format. The header file for each dataset is complete as defined by the LAS 1.2 specification. The datasets were divided into a 1500 meters by 1500 meters tiling scheme. The tiles are contiguous, do not overlap, and are suitable for seamless topographic data mosaics that include no "no data" areas. The names of the tiles include alphabetic column and numeric row designations and all files utilize the LAS file extension.
    1 2011-01-01T00:00:00 The unedited data are classified to facilitate the application of the appropriate feature extraction filters. A combination of proprietary filters are applied as appropriate for the production of bare earth models (DEMs). Interactive editing methods are applied to those areas where it is inappropriate or impossible to use the feature extraction filters, based upon the design criteria and/or limitations of the relevant filters. These same feature extraction filters are used to produce elevation height surfaces.
    1 2013-01-01T00:00:00 The NOAA Coastal Services Center (CSC) received topographic files in LAS format. The files contained lidar elevation and intensity measurements. The data were received in NAD83 UTM Zone 15 Coordinates and were vertically referenced to NAVD88 using the Geoid09 model. The vertical units of the data were meters. CSC 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 topographic las files were converted from UTM Zone 15 (meters) to Geographic coordinates (decimal degrees). 3. ASPRS Class 11 (Withheld) was changed to Class 13 (Withheld). 4. The data were converted to LAZ format.
    1 2013-04-25T00: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