ISO Table View View Metadata As: Get Data, FAQ, HTML, 19139 XML
Assess Metadata For: Completeness, DOI Readiness, CSW Readiness, Components

Metadata Identifier: gov.noaa.csc.maps:2011_ARRA_LA_Region2_m1404

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 2011 U.S. Geological Survey (USGS) Topographic LiDAR: Louisiana Region 2 TASK NAME: Louisiana Region 2 LiDAR ARRA Task Order LiDAR Data Acquisition and Processing Production Task- Orleans, Plaquemines, St. Bernard, St. Tammany Parishes, and Hancock County (MS) USGS Contract No: G10PC00057 Task Order No: G10PD02781 Woolpert ORDER NUMBER: 70930 CONTRACTOR: Woolpert, Inc. LiDAR data is a remotely sensed high resolution elevation data collected by an airborne platform. The LiDAR sensor uses a combination of laser range finding, GPS positioning, and inertial measurement technologies. The LiDAR systems collect data point clouds that are used to produce highly detailed Digital Elevation Models (DEMs) of the earth's terrain, man-made structures, and vegetation. The task required the LiDAR data to be collected at a nominal pulse spacing (NPS) of 2.0 meters. The final products include first, last, and at least one intermediate return LAS, full classified LAS and a bare earth model in separate files.
Top

SV_Identification

none found
Top

CI_Citation

Count Component Title Date Citation Identifier
1 2011 U.S. Geological Survey (USGS) Topographic LiDAR: Louisiana Region 2
  • 2011-04-15
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/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce coastal.info@noaa.gov originator http://coast.noaa.gov
    1 NOAA CSC (publisher) DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce coastal.info@noaa.gov publisher http://coast.noaa.gov
    1 NOAA CSC(distributor) DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce coastal.info@noaa.gov distributor http://coast.noaa.gov
    1 NOAA CSC (processor) DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce coastal.info@noaa.gov processor http://coast.noaa.gov
    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 U.S. Geological Survey originator
    1 USGS (United States Geological Survey) NGTOC pointOfContact
    5 Woolpert, Inc. Geospatial Services processor
    Top

    CI_OnlineResource

    Count Component Linkage Name Description Function
    4 http://coast.noaa.gov
    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 -90.006583 -89.026134 30.258269 28.901380 2011-01-11 2011-03-01
    Top

    EX_GeographicBoundingBox

    Count Component West East North South
    1 -90.006583 -89.026134 30.258269 28.901380
    Top

    EX_TemporalExtent

    Count Component Start End
    1 2011-01-11 2011-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 2011-04-15T00:00:00 Using a LH Systems ALS50 Light Detection And Ranging (LiDAR) system, 160 flight lines of high density data, at a nominal pulse spacing (NPS) of 2.0 meters, were collected over approximately 7,301 square meters (2,819 square miles) of Orleans, Plaquemines, St. Bernard and St. Tammany Parishes in southeastern Louisiana. Multiple returns were recorded for each laser pulse along with an intensity value for each return. A total of sixteen missions were flown over a 12 day period: January 11 - 14, 2011, January 21, 2011, January 29, 2011, February 11 - 15, 2011, February 21, 2011, February 28, 2001, and March 1, 2011 . A minimum of two airborne global positioning system (GPS) base stations were used in support of the LiDAR data acquisition. 22 ground control points were surveyed through static methods. The geoid used to reduce satellite derived elevations to orthometric heights was Geoid09. All data for Region 2 is referenced to UTM 16N for the area within its zone, NAD83, NAVD88, in meters. Airborne GPS data was differentially processed and integrated with the post processed IMU data to derive a smoothed best estimate of trajectory (SBET). The SBET was used to reduce the LiDAR slant range measurements to a raw reflective surface for each flight line. The coverage was classified to extract a bare earth digital elevation model (DEM) and separate last returns. In addition to the LAS deliverables, one layer of coverage was delivered in the ArcINFO ArcGrid binary format 2m cell size: bare-earth. The ArcGrid data was created using ArcMap v93. software. System Parameters: - Type of Scanner = LH Systems ALS50 - Data Acquisition Height = 2,377-meters AGL - Scanner Field of View = 40 degrees - Scan Frequency = 36.7 Hertz - Pulse Repetition Rate = 99.0 Kilohertz - Aircraft Speed = 140 Knots - Swath Width = 1730-meters - Number of Returns Per Pulse = Maximum of 4 - Distance Between Flight Lines = 1212-meters.
    1 2011-04-15T00:00:00 The ALS50 calibration and system performance is verified on a periodic basis using Woolpert's calibration range. The calibration range consists of a large building and runway. The edges of the building and control points along the runway have been located using conventional survey methods. Inertial measurement unit (IMU) misalignment angles and horizontal accuracy are calculated by comparing the position of the building edges between opposing flight lines. The scanner scale factor and vertical accuracy is calculated through comparison of LiDAR data against control points along the runway. Field calibration is performed on all flight lines to refine the IMU misalignment angles. IMU misalignment angles are calculated from the relative displacement of features within the overlap region of adjacent (and opposing) flight lines. The raw LiDAR data is reduced using the refined misalignment angles.
    1 2011-04-15T00:00:00 Once the data acquisition and GPS processing phases are complete, the LiDAR data was processed immediately to verify the coverage had no voids. The GPS and IMU data was post processed using differential and Kalman filter algorithms to derive a best estimate of trajectory. The quality of the solution was verified to be consistent with the accuracy requirements of the project.
    1 2011-04-15T00:00:00 The individual flight lines were inspected to ensure the systematic and residual errors have been identified and removed. Then, the flight lines were compared to adjacent flight lines for any mismatches to obtain a homogenous coverage throughout the project area. The point cloud underwent a classification process to determine bare-earth points and non-ground points utilizing "first and only" as well as "last of many" LiDAR returns. This process determined bare-earth points (Class 2), Noise (Class 7), Water (Class 9) Ignored ground (Class 10) and unclassified data (Class 1). The bare-earth (Class 2 - Ground) LiDAR points underwent a manual QA/QC step to verify that artifacts have been removed from the bare-earth surface. The surveyed ground control points are used to perform the accuracy checks and statistical analysis of the LiDAR dataset.
    1 2011-04-15T00:00:00 Breaklines defining lakes, greater than two acres, and double-line streams, wider than 30.5 meters (100 feet), were compiled using digital photogrammetric techniques as part of the hydrographic flattening process and provided as ESRI Polyline Z and Polygon Z shape files. Breaklines defining water bodies and streams were compiled for this task order. The breaklines were used to perform the hydrologic flattening of water bodies, and gradient hydrologic flattening of double line streams. Lakes, reservoirs and ponds, at a nominal minimum size of two (2) acres or greater, were compiled as closed polygons. The closed water bodies were collected at a constant elevation. Rivers and streams, at a nominal minimum width of 30.5 meters (100 feet), were compiled in the direction of flow with both sides of the stream maintaining an equal gradient elevation. The draping of the polygons and double lines streams was performed using proprietary software developed by Woolpert. The hydrologic flattening of the LiDAR data was performed for inclusion in the National Elevation Dataset (NED).
    1 2012-10-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 UTM Zone 16 (NAD83) 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 data were converted to LAZ format.
    1 2013-01-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