2016 USACE NCMP Topobathy Lidar: Florida East Coast fl2016_usace_ncmp_fl_east_cst_m5185_metadata eng Dataset DOD/USARMY/USACE/SAM/MOBILE/OPJ/JALBTCX > Joint Airborne Lidar Bathymetry Technical Center of Expertise, Mobile District, South Atlantic Division, U.S. Army Corps of Engineers, U.S. Army, U.S. Department of Defense EARTH SCIENCE > HUMAN DIMENSIONS > ENVIRONMENTAL GOVERNANCE/MANAGEMENT > LAND MANAGEMENT > LAND USE CLASSES EARTH SCIENCE > LAND SURFACE > GEOMORPHIC LANDFORMS/PROCESSES > COASTAL LANDFORMS EARTH SCIENCE > LAND SURFACE > GEOMORPHIC LANDFORMS/PROCESSES > COASTAL PROCESSES EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION EARTH SCIENCE > OCEANS > BATHYMETRY/SEAFLOOR TOPOGRAPHY > BATHYMETRY EARTH SCIENCE > OCEANS > BATHYMETRY/SEAFLOOR TOPOGRAPHY > SEAFLOOR TOPOGRAPHY EARTH SCIENCE > OCEANS > COASTAL PROCESSES > COASTAL ELEVATION elevation imageryBaseMapsEarthCover oceans VERTICAL LOCATION > LAND SURFACE VERTICAL LOCATION > SEA FLOOR LIDAR > Light Detection and Ranging Geographic Information > LiDAR EARTH SCIENCE > Land Surface > Topography> Terrain Elevation EARTH SCIENCE > Oceans > Bathymetry/Seafloor Topography > Bathymetry Spatial Data Branch United States Army CoRIS IWG-OCM National Coastal Mapping Program (NCMP) U.S. Army Corps of Engineers (USACE) 2016 July June May COUNTRY/TERRITORY > United States of America > Florida OCEAN BASIN > Atlantic Ocean > North Atlantic Ocean > Florida Florida United States These files contain classified topo/bathy lidar data. Data are classified as 1 (valid non-ground topographic data), 2 (valid ground topographic data), and 29 (valid bathymetric data). Classes 1 and 2 are defined in accordance with the American Society for Photogrammetry and Remote Sensing (ASPRS) classification standards. These data were collected by the Coastal Zone Mapping and Imaging Lidar (CZMIL) system. CZMIL integrates a lidar sensor with simultaneous topographic and bathymetric capabilities, a digital camera and a hyperspectral imager on a single remote sensing platform for use in coastal mapping and charting activities. Native lidar data is not generally in a format accessible to most Geographic Information Systems (GIS). Specialized in-house and commercial software packages are used to process the native lidar data into 3-dimensional positions that can be imported into GIS software for visualization and further analysis. The 3-D position data are sub-divided into a series of LAS files, which are tiled into quarter-quads or 5 km boxes. In addition to the lidar point data, topobathy bare earth Digital Elevation Models (DEMs), at a 1 meter grid spacing, created from the lidar point data are also available. These data are available for download here: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=6196 DEMs that were created from all classes of points (1, 2, 29) at a 1 meter grid size are available by request via email at: coastal.info@noaa.gov. These products have not been reviewed by the NOAA Office for Coastal Management (OCM) and any conclusions drawn from the analysis of this information are not the responsibility of NOAA or OCM. Original contact information: Contact Org: JALBTCX Title: Data Production Manager Phone: 228-252-1131 Email: JALBTCX@usace.army.mil OCM Partners OCM Partners https://www.fisheries.noaa.gov/inport/item/49722 https://www.fisheries.noaa.gov/inport/item/49401 northlimit=30.766599; eastlimit=-80.008543; southlimit=25.657031; westlimit=-81.466334; start=2016-05-19; end=2016-07-20; None. These data have been developed from the best available sources. Although efforts have been made to ensure that the data are accurate and reliable, errors and variable conditions originating from physical sources used to develop the data may be reflected in the data supplied. Users must be aware of these conditions and bear responsibility for the appropriate use of the information with respect to possible errors, scale, resolution, rectification, positional accuracy, development methodology, time period, environmental and climatic conditions and other circumstances specific to these data. The user is responsible for understanding the accuracy limitations of the data provided herein. The burden for determining fitness for use lies entirely with the user. The user should refer to the accompanying metadata notes for a description of the data and data development procedures. 2016-12-15