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:2009_USACE_Texas_m1063

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 2009 US Army Corps of Engineers (USACE) Joint Airborne Lidar Bathymetry Technical Center of Expertise (JALBTCX) Topographic Lidar: South Texas Coast This Light Detection and Ranging (LiDAR) classified (ASPRS LAS classifications) dataset is a topographic survey conducted for the West Texas Aerial Survey 2009 project. This data was produced for the US Army Corps of Engineers (USACE) Joint Airborne Lidar Bathymetry Technical Center of Expertise (JALBTCX). The LiDAR point cloud was flown at a density sufficient to support a maximum final post spacing of 1 point per meter. 3001 International Inc. acquired 81 flightlines between February 3, 2009 and April 23, 2009. The West Texas Aerial Survey 2009 was collected under the guidance of a Professional Mapper/Surveyor. The area of coverage includes portions of the coastline in the following counties: Aransas, Brazoria, Calhoun, Cameron, Kenedy, Kleberg, Matagorda, Nueces, San Patricio, and Willacy.
Top

SV_Identification

none found
Top

CI_Citation

Count Component Title Date Citation Identifier
1 2009 US Army Corps of Engineers (USACE) Joint Airborne Lidar Bathymetry Technical Center of Expertise (JALBTCX) Topographic Lidar: South Texas 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
    3 3001 International Inc. LiDAR Department lidar@3001inc.com processor
    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 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
    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 -97.403417 -95.277455 28.957342 25.951459 2009-02-03 2009-04-23
    Top

    EX_GeographicBoundingBox

    Count Component West East North South
    1 -97.403417 -95.277455 28.957342 25.951459
    Top

    EX_TemporalExtent

    Count Component Start End
    1 2009-02-03 2009-04-23
    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 2009-05-27T00:00:00 The ABGPS, IMU, and raw scans are integrated using proprietary software developed by Optech and delivered with the Optech ALTM Gemini System. The resultant file is in a LAS binary file format. The LAS file version 1.1 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#, intensity value, xyz, etc.). The resultant points are referenced to the Geographic NAD83 horizontal datum and NAVD88 vertical datum.
    1 2009-05-27T00:00:00 The data is subjected to rigorous QA/QC according to the 3001 Inc. Quality Control Plan and procedures. Very briefly, a series of quantitative and visual procedures are employed to validate the accuracy and consistency of the data. Ground control is established by 3001, Inc. and GPS-derived ground control points (GCPs) points in various areas of dominant and prescribed land cover. These points are coded according to landcover, surface material, and ground control suitability. A suitable number of points are selected for calculation of a statistically significant accuracy assessment as per the requirements of the National Standard for Spatial Data Accuracy. A spatial proximity analysis is used to select edited LiDAR data points within a specified distance of the relevant GCPs. A search radius decision rule is applied with consideration of terrain complexity, cumulative error, and adequate sample size. Accuracy validation and evaluation is accomplished using proprietary software to apply relevant statistical routines for calculation of Root Mean Square Error (RMSE) and the National Standard for Spatial Data Accuracy (NSSDA) according to Federal Geographic Data Committee (FGDC) specifications.
    1 2010-01-15T00:00:00 The Airborne Global Position System (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 of the aircraft. During the aerial survey laser pulses reflected from features on the surface and 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 20 km radius from the flight survey area.
    1 2010-09-01T00:00:00 Metadata imported.
    1 2011-09-01T00:00:00 The NOAA Coastal Services Center (CSC) received classified data (ASPRS LAS classifications) in las format. The files contained LiDAR intensity and elevation measurements. CSC performed the following processing for data storage and Digital Coast provisioning purposes: 1. The data were converted from NAVD88 heights to ellipsoid heights using Geoid03. 2. 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