<?xml version="1.0" encoding="UTF-8"?>
<metadata xmlns:dc="http://purl.org/dc/elements/1.1/"
          xmlns:dcterms="http://purl.org/dc/terms/"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <dc:title>2013 USACE NCMP Topobathy Lidar: Kauai (HI)</dc:title>
   <dcterms:alternative>hi2013_usace_ncmp_kauai_m5013_metadata</dcterms:alternative>
   <dc:language xsi:type="dcterms:ISO639-3">eng</dc:language>
   <dc:type xsi:type="dcterms:DCMIType">Dataset</dc:type>
   <dc:subject>DOD/USARMY/USACE/SAM/MOBILE/OPJ/JALBTCX &gt; 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</dc:subject>
   <dc:subject>EARTH SCIENCE &gt; HUMAN DIMENSIONS &gt; ENVIRONMENTAL GOVERNANCE/MANAGEMENT &gt; LAND MANAGEMENT &gt; LAND USE CLASSES</dc:subject>
   <dc:subject>EARTH SCIENCE &gt; LAND SURFACE &gt; GEOMORPHIC LANDFORMS/PROCESSES &gt; COASTAL LANDFORMS</dc:subject>
   <dc:subject>EARTH SCIENCE &gt; LAND SURFACE &gt; GEOMORPHIC LANDFORMS/PROCESSES &gt; COASTAL PROCESSES</dc:subject>
   <dc:subject>EARTH SCIENCE &gt; LAND SURFACE &gt; TOPOGRAPHY &gt; TERRAIN ELEVATION</dc:subject>
   <dc:subject>EARTH SCIENCE &gt; OCEANS &gt; BATHYMETRY/SEAFLOOR TOPOGRAPHY &gt; BATHYMETRY</dc:subject>
   <dc:subject>EARTH SCIENCE &gt; OCEANS &gt; BATHYMETRY/SEAFLOOR TOPOGRAPHY &gt; SEAFLOOR TOPOGRAPHY</dc:subject>
   <dc:subject>EARTH SCIENCE &gt; OCEANS &gt; COASTAL PROCESSES &gt; COASTAL ELEVATION</dc:subject>
   <dc:subject>elevation</dc:subject>
   <dc:subject>imageryBaseMapsEarthCover</dc:subject>
   <dc:subject>oceans</dc:subject>
   <dc:subject>VERTICAL LOCATION &gt; LAND SURFACE</dc:subject>
   <dc:subject>VERTICAL LOCATION &gt; SEA FLOOR</dc:subject>
   <dc:subject>LIDAR &gt; Light Detection and Ranging</dc:subject>
   <dc:subject>Geographic Information &gt; LiDAR</dc:subject>
   <dc:subject>EARTH SCIENCE &gt; Land Surface &gt; Topography&gt; Terrain Elevation</dc:subject>
   <dc:subject>EARTH SCIENCE &gt; Oceans &gt; Bathymetry/Seafloor Topography &gt; Bathymetry</dc:subject>
   <dc:subject>Spatial Data Branch</dc:subject>
   <dc:subject>United States Army</dc:subject>
   <dc:subject>CoRIS</dc:subject>
   <dc:subject>IWG-OCM</dc:subject>
   <dc:subject>National Coastal Mapping Program (NCMP)</dc:subject>
   <dc:subject>U.S. Army Corps of Engineers (USACE)</dc:subject>
   <dc:subject>October</dc:subject>
   <dc:subject>September</dc:subject>
   <dc:subject>COUNTRY/TERRITORY &gt; United States of America &gt; Hawaii &gt; Hawaii &gt; Kauai Island (22N159W0001)</dc:subject>
   <dc:subject>OCEAN BASIN &gt; Pacific Ocean &gt; Central Pacific Ocean &gt; Hawaiian Islands &gt; Kauai Island &gt; Kauai Island (22N159W0001)</dc:subject>
   <dc:subject>Hawaii</dc:subject>
   <dc:subject>Kauai</dc:subject>
   <dc:subject>United States</dc:subject>
   <dcterms:abstract>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 imagery 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. Horizontal positions, provided in decimal degrees of latitude and longitude, are referenced to the North American Datum of 1983 National Adjustment of 2011 (NAD83 PA11). Vertical positions are referenced to the (NAD83 PA11) ellipsoid and provided in meters. The 3-D position data are sub-divided into a series of LAS files, which are tiled into quarter-quads or 5km boxes. 

In addition to the lidar point data, Digital Elevation Models(DEMs), created from the lidar point data are also available. DEMs were created from all classes of points (1, 2, 29) at a 1 meter grid size and bare earth DEMs were created from the ground and bathymetric data classes (2, 29) at a 1 meter grid size. 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. The data are available upon request via email at: coastal.info@noaa.gov. Please provide the name of the data set and "DEM Request" in the subject line. 

The FTP versions of the LAZ files have GPS-derived orthometric heights. To adjust to the Local Mean Sea Level (LMSL) use the following value to correct the vertical heights: -0.827 m.
Original contact information: 
   Contact Org: JALBTCX
   Title: Data Production Manager
   Phone: 228-252-1131
   Email: JALBTCX@usace.army.mil</dcterms:abstract>
   <dc:publisher>OCM Partners</dc:publisher>
   <dc:creator>OCM Partners</dc:creator>
   <dc:identifier xsi:type="dcterms:URI">https://www.fisheries.noaa.gov/inport/item/49747</dc:identifier>
   <dcterms:isPartOf xsi:type="dcterms:URI">https://www.fisheries.noaa.gov/inport/item/49401</dcterms:isPartOf>
   <dcterms:spatial xsi:type="dcterms:Box">
            northlimit=22.243215;
            eastlimit=-159.276628;
            southlimit=21.855445;
            westlimit=-159.802141;
          </dcterms:spatial>
   <dcterms:temporal xsi:type="dcterms:Period">
              start=2013-09-26;
              end=2013-10-07;
            </dcterms:temporal>
   <dcterms:accessRights>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.</dcterms:accessRights>
   <dcterms:created xsi:type="dcterms:W3CDTF">2016-03-16</dcterms:created>
</metadata>
