<?xml version="1.0" encoding="UTF-8"?>
<inport-metadata xmlns:xs="http://www.w3.org/2001/XMLSchema"
                 version="1.11"
                 source="https://www.fisheries.noaa.gov">
   <item-identification>
      <catalog-item-id>72897</catalog-item-id>
      <title>2016 ADECA Lidar: 6 County (Bibb, Chilton, Coosa, Dallas, Hale, Perry), AL</title>
      <short-name>al2016_adeca_6county_m10127_metadata</short-name>
      <catalog-item-type>Data Set</catalog-item-type>
      <metadata-workflow-state ccs-id="9">Published / External</metadata-workflow-state>
      <parent-catalog-item-id>49401</parent-catalog-item-id>
      <parent-title>Lidar - partner (no harvest)</parent-title>
      <parent-catalog-item-type>Project</parent-catalog-item-type>
      <status>Completed</status>
      <creation-date>2016</creation-date>
      <abstract>Geographic Extent: This data set consists of the lidar point cloud, classified lidar, digital elevation model, and lidar intensity images which encompasses the six counties in the ADECA (AL Department of Economic and Community Affairs) portion of the 2016 Alabama AGIO/ADECA 12 County Lidar Area of Interest (AOI), The entire 12 county project covers approximately 22,909 square kilometers or 8845 square miles. The ADECA portion covers the following counties: Bibb, Chilton, Coosa, Dallas, Hale, and Perry.

Data set Description: This data set consists of lidar point cloud LAS swath files and tiled LAS files. Each LAS file contains lidar point information, which has been calibrated, controlled, and classified. Each file represents a separate swath of lidar.

Ground Conditions: water at normal levels; no unusual inundation; no snow; leaf off

How the Withheld Points are Identified:	Withheld (ignore) points were identified in the files using the standard LAS Withheld bit.

Class Code:1
Class Item:Unclassified
Class Code:2
Class Item:Ground
Class Code:7
Class Item:Low Noise
Class Code:9
Class Item:Water
Class Code:10
Class Item:Ignored Ground
Class Code:17
Class Item:Bridges
Class Code:18
Class Item:High Noise

This metadata supports the data entry in the NOAA Digital Coast Data Access Viewer (DAV). For this data set, the DAV is leveraging the Entwine Point Tiles (EPT) hosted by USGS on Amazon Web Services. 

</abstract>
      <purpose>The primary purpose of the lidar survey was to establish measurements of the bare earth surface, as well as top surface feature data for providing geometric inputs for modeling, other numerical modeling and economic related assessments.</purpose>
      <supplemental-information>All lidar data was acquired, calibrated, and used in the creation of lidar derived products by Atlantic.</supplemental-information>
   </item-identification>
   <keywords>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Science Keywords</thesaurus>
         <keyword identifier="74ed1690-968e-444c-8a31-7b8344a2aad3">EARTH SCIENCE &gt; LAND SURFACE &gt; TOPOGRAPHY &gt; TERRAIN ELEVATION</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus>ISO 19115 Topic Category</thesaurus>
         <keyword>elevation</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Spatial</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Location Keywords</thesaurus>
         <keyword identifier="753f915c-70d4-49e1-9bd5-83e75f461e30">CONTINENT &gt; NORTH AMERICA &gt; UNITED STATES OF AMERICA</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Spatial</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Location Keywords</thesaurus>
         <keyword identifier="9fe93f63-61b1-4232-bf5b-05703f803fce">CONTINENT &gt; NORTH AMERICA &gt; UNITED STATES OF AMERICA &gt; ALABAMA</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Spatial</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Location Keywords</thesaurus>
         <keyword identifier="90761f8d-6abe-499c-b711-acec394daa59">VERTICAL LOCATION &gt; LAND SURFACE</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Instrument</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Instrument Keywords</thesaurus>
         <keyword identifier="7166c458-f935-4bd9-a322-d92830cf0c33">LIDAR &gt; Light Detection and Ranging</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Platform</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Platform Keywords</thesaurus>
         <keyword identifier="8b7834c1-2c66-414e-a655-2298e7dcc479">Airplane &gt; Airplane</keyword>
      </keyword>
   </keywords>
   <physical-location>
      <organization>Office for Coastal Management</organization>
      <city>Charleston</city>
      <state-province>SC</state-province>
   </physical-location>
   <data-set-information>
      <data-set-scope-code>Data Set</data-set-scope-code>
      <data-set-type>Elevation</data-set-type>
      <maintenance-frequency>As Needed</maintenance-frequency>
      <data-presentation-form>Model (digital)</data-presentation-form>
      <entity-attribute-detail-citation>Lidar tiles and associated derived products for USGS</entity-attribute-detail-citation>
      <distribution-liability>The data represented is the result of data collection and processing per contract specifications and indicates the general existing conditions at the time of data collection. As such, it is only valid for its intended use, content, time, and accuracy specifications. The user is responsible for the results of any application of the data for other than its intended purpose.
Any conclusions drawn from the analysis of this information are not the responsibility of NOAA, the Office for Coastal Management or its partners.</distribution-liability>
      <data-set-credit>ADECA, Atlantic, USGS	</data-set-credit>
   </data-set-information>
   <entity-attribute-information partial-listing="No" total-count="0"/>
   <support-roles>
      <support-role cc-id="1339344" in-effect="Yes">
         <support-role-type>Data Steward</support-role-type>
         <from-date>2024</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>NOAA Office for Coastal Management</contact-name>
         <contact-noaa-acronym>NOAA/OCM</contact-noaa-acronym>
         <contact-email>coastal.info@noaa.gov</contact-email>
         <contact-address>2234 South Hobson Ave</contact-address>
         <contact-address-city>Charleston</contact-address-city>
         <contact-address-state>SC</contact-address-state>
         <contact-address-zip>29405-2413</contact-address-zip>
         <contact-phone-number>(843) 740-1202</contact-phone-number>
         <contact-url>https://coast.noaa.gov</contact-url>
         <contact-url-description>NOAA Office for Coastal Management Home Page</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
      <support-role cc-id="1339343" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2024</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>NOAA Office for Coastal Management</contact-name>
         <contact-noaa-acronym>NOAA/OCM</contact-noaa-acronym>
         <contact-email>coastal.info@noaa.gov</contact-email>
         <contact-address>2234 South Hobson Ave</contact-address>
         <contact-address-city>Charleston</contact-address-city>
         <contact-address-state>SC</contact-address-state>
         <contact-address-zip>29405-2413</contact-address-zip>
         <contact-phone-number>(843) 740-1202</contact-phone-number>
         <contact-url>https://coast.noaa.gov</contact-url>
         <contact-url-description>NOAA Office for Coastal Management Home Page</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
      <support-role cc-id="1339374" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2017</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>U.S. Geological Survey</contact-name>
         <contact-address>12201 Sunrise Valley Drive </contact-address>
         <contact-address-city>Reston</contact-address-city>
         <contact-address-state>VA</contact-address-state>
         <contact-address-zip>20191</contact-address-zip>
         <contact-address-country>USA</contact-address-country>
         <contact-url>https://usgs.gov</contact-url>
         <contact-url-name>USGS Home</contact-url-name>
         <contact-url-description>Home page for USGS</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
      <support-role cc-id="1339345" in-effect="Yes">
         <support-role-type>Metadata Contact</support-role-type>
         <from-date>2024</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>NOAA Office for Coastal Management</contact-name>
         <contact-noaa-acronym>NOAA/OCM</contact-noaa-acronym>
         <contact-email>coastal.info@noaa.gov</contact-email>
         <contact-address>2234 South Hobson Ave</contact-address>
         <contact-address-city>Charleston</contact-address-city>
         <contact-address-state>SC</contact-address-state>
         <contact-address-zip>29405-2413</contact-address-zip>
         <contact-phone-number>(843) 740-1202</contact-phone-number>
         <contact-url>https://coast.noaa.gov</contact-url>
         <contact-url-description>NOAA Office for Coastal Management Home Page</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
      <support-role cc-id="1339346" in-effect="Yes">
         <support-role-type>Point of Contact</support-role-type>
         <from-date>2024</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>NOAA Office for Coastal Management</contact-name>
         <contact-noaa-acronym>NOAA/OCM</contact-noaa-acronym>
         <contact-email>coastal.info@noaa.gov</contact-email>
         <contact-address>2234 South Hobson Ave</contact-address>
         <contact-address-city>Charleston</contact-address-city>
         <contact-address-state>SC</contact-address-state>
         <contact-address-zip>29405-2413</contact-address-zip>
         <contact-phone-number>(843) 740-1202</contact-phone-number>
         <contact-url>https://coast.noaa.gov</contact-url>
         <contact-url-description>NOAA Office for Coastal Management Home Page</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
   </support-roles>
   <extents>
      <currentness-reference>Ground Condition</currentness-reference>
      <extent cc-id="1339347">
         <geographic-areas>
            <geographic-area cc-id="1339349">
               <west-bound>-87.85</west-bound>
               <east-bound>-85.979111</east-bound>
               <north-bound>33.26</north-bound>
               <south-bound>32.039299</south-bound>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1339348">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2016-12-02</start-date-time>
               <end-date-time>2017-03-15</end-date-time>
            </time-frame>
         </time-frames>
      </extent>
   </extents>
   <spatial-information>
      <spatial-representation>
         <representations-used>
            <grid>No</grid>
            <vector>Yes</vector>
            <text-table>No</text-table>
            <tin>No</tin>
            <stereo-model>No</stereo-model>
            <video>No</video>
         </representations-used>
      </spatial-representation>
      <reference-systems>
         <reference-system>
            <coordinate-reference-system>
               <crs-type>Projected</crs-type>
               <epsg-code>EPSG:3857</epsg-code>
               <epsg-name>WGS 84 / Pseudo-Mercator</epsg-name>
               <datum-name>World Geodetic System 1984</datum-name>
               <ellipsoid>WGS 84</ellipsoid>
               <semimajor-axis>6378137</semimajor-axis>
               <flattening-ratio>298.257223563</flattening-ratio>
               <base-crs-name>WGS 84</base-crs-name>
               <projection-name>Popular Visualisation Pseudo-Mercator</projection-name>
               <conversion-method>Popular Visualisation Pseudo Mercator</conversion-method>
               <parameters>
                  <parameter>
                     <parameter-name>Latitude of natural origin</parameter-name>
                     <parameter-value>0° 0' 0" N</parameter-value>
                  </parameter>
                  <parameter>
                     <parameter-name>Longitude of natural origin</parameter-name>
                     <parameter-value>0° 0' 0" E</parameter-value>
                  </parameter>
                  <parameter>
                     <parameter-name>False easting</parameter-name>
                     <parameter-value>0</parameter-value>
                     <parameter-units>metre</parameter-units>
                  </parameter>
                  <parameter>
                     <parameter-name>False northing</parameter-name>
                     <parameter-value>0</parameter-value>
                     <parameter-units>metre</parameter-units>
                  </parameter>
               </parameters>
               <axes>
                  <axis>
                     <order>1</order>
                     <name>Easting</name>
                     <abbreviation>X</abbreviation>
                     <units>metre</units>
                     <orientation>east</orientation>
                  </axis>
                  <axis>
                     <order>2</order>
                     <name>Northing</name>
                     <abbreviation>Y</abbreviation>
                     <units>metre</units>
                     <orientation>north</orientation>
                  </axis>
               </axes>
            </coordinate-reference-system>
         </reference-system>
         <reference-system>
            <coordinate-reference-system>
               <crs-type>Vertical</crs-type>
               <epsg-code>EPSG:5703</epsg-code>
               <epsg-name>NAVD88 height</epsg-name>
               <datum-name>North American Vertical Datum 1988</datum-name>
               <axes>
                  <axis>
                     <order>1</order>
                     <name>Gravity-related height</name>
                     <abbreviation>H</abbreviation>
                     <units>metre</units>
                     <orientation>up</orientation>
                  </axis>
               </axes>
            </coordinate-reference-system>
         </reference-system>
      </reference-systems>
   </spatial-information>
   <access-information>
      <data-license-type>Custom</data-license-type>
      <security-class>Unclassified</security-class>
      <data-access-procedure>Data is available online for bulk and custom downloads.</data-access-procedure>
      <data-access-constraints>No restrictions apply to this data the data represented is the result of data collection and processing per contract specifications and indicates the general existing conditions at the time of the data collection. As such, it is only valid for its intended use, content, time, and accuracy specifications. The user is responsible for the results of any application of the data for other than its intended purpose.</data-access-constraints>
      <data-use-constraints>None, however, users should be aware that temporal changes may have occurred since this dataset was collected and that some parts of these data may no longer represent actual surface conditions. Users should not use these data for critical applications without a full awareness of the limitations of the data. Acknowledgement of USGS would be appreciated for products derived from these data. The data represented is the result of data collection and processing per contract specifications and indicates the general existing conditions at the time of the data collection. As such, it is only valid for its intended use, content, time, and accuracy specifications. The user is responsible for the results of any application of the data for other than its intended purpose.

</data-use-constraints>
   </access-information>
   <distribution-information>
      <distribution cc-id="1339350">
         <download-url>https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=10127/details/10127</download-url>
         <distributor cc-id="1339343">
            <from-date>2024</from-date>
            <contact-type>Organization</contact-type>
            <contact-name>NOAA Office for Coastal Management</contact-name>
         </distributor>
         <file-name>Customized Download</file-name>
         <description>Create custom data files by choosing data area, product type, map projection, file format, datum, etc. A new metadata will be produced to reflect your request using this record as a base. Change to an orthometric vertical datum is one of the many options.</description>
         <distribution-format>Not Applicable</distribution-format>
         <compression>Zip</compression>
      </distribution>
      <distribution cc-id="1339351">
         <download-url>https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/AL_ADECA_6_County_Lidar_2016_B16/</download-url>
         <distributor cc-id="1339374">
            <from-date>2017</from-date>
            <contact-type>Organization</contact-type>
            <contact-name>U.S. Geological Survey</contact-name>
         </distributor>
         <file-name>Bulk Download</file-name>
         <description>Bulk download of data files in LAZ format, UTM Zone 16N NAD83 (2011), meters coordinates and NAVD88 (Geoid12B) elevations in meters. </description>
         <distribution-format>LAS/LAZ - LASer</distribution-format>
         <compression>LAZ</compression>
      </distribution>
   </distribution-information>
   <urls>
      <url cc-id="1339341">
         <url>https://coast.noaa.gov/dataviewer/</url>
         <name>NOAA's Office for Coastal Management (OCM) Data Access Viewer (DAV)</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>HTML</file-resource-format>
         <description>The Data Access Viewer (DAV) allows a user to search for and download elevation, imagery, and land cover data for the coastal U.S. and its territories. The data, hosted by the NOAA Office for Coastal Management, can be customized and requested for free download through a checkout interface. An email provides a link to the customized data, while the original data set is available through a link within the viewer.</description>
      </url>
      <url cc-id="1339377">
         <url>https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/AL_ADECA_6_County_Lidar_2016_B16/</url>
         <name>USGS Additional Info</name>
         <url-type>Online Resource</url-type>
         <description>Link to the additional information available for this data set from the USGS. This information includes reports, tile index shapefiles, and hydro breaklines.</description>
      </url>
      <url cc-id="1339378">
         <url>https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/AL_ADECA_6_County_Lidar_2016_B16/AL_ADECA_B1_2016/reports/AL_ADECA%206%20County%20Lidar_2016_B16_Aerial_Lidar_Report.pdf</url>
         <name>Lidar Report</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>pdf</file-resource-format>
         <description>Link to the lidar report.</description>
      </url>
      <url cc-id="1339379">
         <url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_AL_ADECA_B1_2016_LAS_2019/ept.json</url>
         <name>USGS Entwine Point Tile (EPT) - AL_ADECA_B1</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>json</file-resource-format>
         <description>Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud.</description>
      </url>
      <url cc-id="1339380">
         <url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_AL_ADECA_B2_2016_LAS_2019/ept.json</url>
         <name>USGS Entwine Point Tile (EPT) - AL_ADECA_B2</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>json</file-resource-format>
         <description>Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud.</description>
      </url>
      <url cc-id="1339381">
         <url>https://usgs.entwine.io/data/view.html?r=[%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_AL_ADECA_B1_2016_LAS_2019/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_AL_ADECA_B2_2016_LAS_2019/ept.json%22]</url>
         <name>USGS 3D View</name>
         <url-type>Online Resource</url-type>
         <description>Link to view the point cloud (using the Entwine Point Tile (EPT) format) in the 3D Potree viewer.</description>
      </url>
   </urls>
   <technical-environment>
      <description>CloudPro 1.2.0 Build 85620; GeoCue Version 2014.1.21.2; Windows 7 Operating System
\\lidarsrv\GC_Warehouse_5\80658\30\*.las
184 GB</description>
   </technical-environment>
   <data-quality>
      <horizontal-positional-accuracy>Horizontal error in lidar derived elevation data is largely a function of positional error as derived from the Global Navigation Satellite System (GNSS), attitude (angular orientation) error (as derived from the INS) and flying altitude; and can be estimated based on these parameters. As described in Section 7.5 of the ASPRS Positional Accuracy Standards for Digital Geospatial Data the horizontal errors in lidar data are largely a function of GNSS positional error, INS angular error, and flying altitude. Therefore, lidar data collected with GNSS error of 8cm and the IMU error of 0.00427 degrees at an altitude of 2,000m; the expected radial horizontal positional error will be RMSEr = 29.0cm.</horizontal-positional-accuracy>
      <vertical-positional-accuracy>Vertical Accuracy of the point cloud and bare-earth lidar data was assessed and reported in accordance with the ASPRS Positional Accuracy Standards for Digital Geospatial Data;
Three hundred and ninety-five (395) surveyed points were measured for the purpose of assessing the accuracy of the lidar data. (227 NVA + 168 VVA). 
Required Vegetated Vertical Accuracy (VVA): 29.4cm. Required Non Vegetated Vertical Accuracy (NVA) : 19.6cm
This data set was tested to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 10.0 (cm) RMSEz Vertical Accuracy Class. 
Actual NVA accuracy of the bare-earth was found to be RMSEz = 6.5 cm, equating to +/- 12.8 cm at 95% confidence level. This data set was tested to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 10.0 (cm) RMSEz Vertical Accuracy Class.
Actual VVA accuracy was found to be RMSEz = 8.0 cm, equating to +/-14.6 cm at the 95th percentile.</vertical-positional-accuracy>
      <completeness-report>The raw LAS data files included all data points collected. No points have been removed or excluded. A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. The raw point cloud is of good quality and data passes Fundamental Vertical Accuracy specifications.Void areas (i.e., areas outside the project boundary but within the tiling scheme) are coded using a unique NODATA value. This value is identified in the appropriate location within the file header.</completeness-report>
      <conceptual-consistency>All lidar data and lidar derived data covers the entire 8845 square mile area of interest for the project AOI. All lidar point cloud tiles show no edge artifacts or mismatches from tile to tile. Void areas (i.e. areas outside the project boundary but within the tiling scheme) are coded using a unique NODATA value. This value is identified in the appropriate location within the file header. Data cover the entire area specified for this project.</conceptual-consistency>
   </data-quality>
   <data-management>
      <resources-identified>Yes</resources-identified>
      <resources-budget-percentage>Unknown</resources-budget-percentage>
      <data-access-directive-compliant>Yes</data-access-directive-compliant>
      <archive-location>NCEI-NC</archive-location>
      <data-protection-plan>Data is backed up to cloud storage.</data-protection-plan>
   </data-management>
   <lineage>
      <lineage-statement>The NOAA Office for Coastal Management (OCM) ingested references to the USGS Entwine Point Tiles (EPT) hosted on Amazon Web Services (AWS) into the Digital Coast Data Access Viewer (DAV). The DAV accesses the point cloud as it resides on AWS under the usgs-lidar-public-container.</lineage-statement>
      <lineage-sources>
         <lineage-source cc-id="1339382">
            <citation-title>USGS AWS Entwine Point Tile (EPT) - AL_ADECA_B1</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>USGS</contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <citation-url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_AL_ADECA_B1_2016_LAS_2019/ept.json</citation-url>
            <citation-url-name>USGS Entwine Point Tile (EPT)</citation-url-name>
         </lineage-source>
         <lineage-source cc-id="1339383">
            <citation-title>USGS AWS Entwine Point Tile (EPT) - AL_ADECA_B2</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>USGS</contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <citation-url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_AL_ADECA_B2_2016_LAS_2019/ept.json</citation-url>
            <citation-url-name>USGS Entwine Point Tile (EPT)</citation-url-name>
         </lineage-source>
      </lineage-sources>
      <lineage-process-steps>
         <lineage-process-step cc-id="1339329">
            <sequence-number>1</sequence-number>
            <description>Aerial Lidar Acquisition: Aerial data collection was acquired in thirty-eight (38) flight missions, using the ALS70 SN#7123/7225 at an altitude of 2300 meters AGL. During flight operations, the flight crew monitored weather and atmospheric conditions. Lidar missions were flown only when no condition existed below the sensor that would affect the collection of data.  The pilot constantly monitored the aircraft course, position, pitch, roll, and yaw of the aircraft.  The sensor operator monitored the sensor, the status of the GNSS constellations, and performed the first QC review during acquisition.  The flight crew constantly reviewed weather and cloud locations.  Data acquisition was completed on March 15, 2017.

Ground Control Survey: This GNSS survey consisted of twelve (12) contiguous Alabama counties which due to geographic proximity were combined into one Area of Interest (AOI) the five hundred twenty-four (524) checkpoints were subdivided into 3 main categories: NVA, VVA, and LCP. A survey crew mobilized to the AOI to perform the RTN –RTK survey to support the aerial LiDAR collection October 20th through November 19th 2016. The RTN –RTK survey consisted of independent GNSS observations on Non-Vegetated Vertical Accuracy, Vegetated Vertical Accuracy (NVA-VVA), and LiDAR Calibration Points (LCP).</description>
            <process-date-time>2017-03-15T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1339385">
            <sequence-number>10</sequence-number>
            <description>References to the entwine point tiles and data reports were ingested into the Digital Coast Data Access Viewer. No changes to the data were made at this point. The Data Access Viewer will access the point cloud as it resides on AWS under the usgs-lidar-public container.</description>
            <process-date-time>2024-06-07T00:00:00</process-date-time>
            <process-contact>
               <contact-type>Organization</contact-type>
               <contact-name>Office for Coastal Management</contact-name>
               <contact-noaa-acronym>OCM</contact-noaa-acronym>
               <contact-ror>https://ror.org/05v14bq57</contact-ror>
               <contact-address>2234 South Hobson Avenue</contact-address>
               <contact-address-city>Charleston</contact-address-city>
               <contact-address-state>SC</contact-address-state>
               <contact-address-zip>29405-2413</contact-address-zip>
               <contact-url>https://www.coast.noaa.gov/</contact-url>
            </process-contact>
         </lineage-process-step>
         <lineage-process-step cc-id="1339330">
            <sequence-number>2</sequence-number>
            <description>Lidar Pre-processing: Airborne GPS and IMU data were merged to develop a Smoothed Best Estimate Trajectory (SBET) of the lidar system for each lift. Lidar ranging data were initially calibrated using previous best parameters for this instrument and aircraft. Relative calibration was evaluated using advanced plane-matching analysis and parameter corrections derived. This process was repeated interactively until residual errors between overlapping swaths, across all project lifts, was reduced to 2 cm or less. Data were then block adjusted to match surveyed calibration control. Raw data NVA were checked using independently surveyed check points. Swath overage points were identified and tagged within each swath file</description>
            <process-date-time>2017-03-16T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1339331">
            <sequence-number>3</sequence-number>
            <description>Initial processing of the GPS data was processed using Inertial Explorer. The solution file was generated and CloudPro software was used to generate georeferenced laser returns which were then processed in strip form allowing for the QC of the overlap between strips (lines). The data from each line were combined and automated classification routines run to determine the initial surface model. This initial surface model was then verified to the surveyed test points.</description>
            <process-date-time>2017-03-18T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1339332">
            <sequence-number>4</sequence-number>
            <description>Lidar Post-Processing: The calibrated and controlled lidar swaths were processed using automatic point classification routines in TerraSolid software. These routines operate against the entire collection (all swaths, all lifts), eliminating character differences between files. Data were then distributed as virtual tiles to experienced Lidar analysts for localized automatic classification, manual editing, and peer-based QC checks. Supervisory QC monitoring of work in progress and completed editing ensured consistency of classification character and adherence to project requirements across the entire project. All classification tags are stored in the original swath files. After completion of classification and final QC approval, the NVA and VVA for the project are calculated. Sample areas for each land cover type present in the project were extracted and forwarded to the client, along with the results of the accuracy tests. Upon acceptance, the complete classified Lidar swath files were delivered to the client.</description>
            <process-date-time>2017-03-25T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1339333">
            <sequence-number>5</sequence-number>
            <description>Lidar Classification:  The calibrated Lidar data was run through automated classification routines and then manually checked and edited. The data was classified into the following classes:  1-unclassified*, 2-ground, 7-low noise, 9-water, 10-ignored ground, 17-bridges, and 18-high noise</description>
            <process-date-time>2017-04-05T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1339334">
            <sequence-number>6</sequence-number>
            <description>Lidar Intensity Imagery Creation: All lidar intensity imagery was created from the final calibrated and classified lidar point cloud. Intensity images were produced from all classified points and are posted to a 1 meter cell size. Intensity images were cut to match the tile index and have corresponding names to match tile names.</description>
            <process-date-time>2017-05-15T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1339335">
            <sequence-number>7</sequence-number>
            <description>Hydro line Collection: Hydro break lines were compiled using the lidar intensity data and surface terrain model of the entire project area. After the collection of hydro lines all features were validated for monotonicity and vertical variance, to ensure that no points were floating above ground. The hydro break lines were encoded into the lidar surface and used to hydro-enforce/flatten all significant water bodies. These final hydro lines were then used in the production of bare Earth digital models to hydro flatten significant water bodies.</description>
            <process-date-time>2017-06-15T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1339336">
            <sequence-number>8</sequence-number>
            <description>Bare-Earth DEM Creation: Bare-Earth digital elevation models (DEMs) were derived using the hydro break line and bare-earth (ground) lidar points, all DEMs were created with a grid spacing of 1 meter. The DEMs were cut to tiles of 1500 meters X 1500 meters index.</description>
            <process-date-time>2017-08-10T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1339384">
            <sequence-number>9</sequence-number>
            <description>Original point clouds in LAS/LAZ format were restructured as Entwine Point Tiles and stored on Amazon Web Services. The data were re-projected horizontally to WGS84 Web Mercator (EPSG 3857). Vertically, no changes were made to the vertical datum (NAVD88 GEOID12B; EPSG 5703).</description>
            <process-contact>
               <contact-type>Organization</contact-type>
               <contact-name>U.S. Geological Survey</contact-name>
               <contact-address>12201 Sunrise Valley Drive </contact-address>
               <contact-address-city>Reston</contact-address-city>
               <contact-address-state>VA</contact-address-state>
               <contact-address-zip>20191</contact-address-zip>
               <contact-address-country>USA</contact-address-country>
               <contact-url>https://usgs.gov</contact-url>
               <contact-url-name>USGS Home</contact-url-name>
               <contact-url-description>Home page for USGS</contact-url-description>
               <contact-url-function>Online Resource</contact-url-function>
            </process-contact>
         </lineage-process-step>
      </lineage-process-steps>
   </lineage>
   <related-items>
      <related-item>
         <catalog-item-id>78785</catalog-item-id>
         <catalog-item-type>Data Set</catalog-item-type>
         <title>2016 ADECA Lidar DEM: 6 County (Bibb, Chilton, Coosa, Dallas, Hale, Perry), AL</title>
         <relationship-type>Cross Reference</relationship-type>
      </related-item>
      <related-item>
         <catalog-item-id>78799</catalog-item-id>
         <catalog-item-type>Data Set</catalog-item-type>
         <title>2016 AGIO Lidar DEM: 6 County (Fayette, Franklin, Greene, Marion, Pickens, Sumter), AL</title>
         <relationship-type>Cross Reference</relationship-type>
      </related-item>
      <related-item>
         <catalog-item-id>72898</catalog-item-id>
         <catalog-item-type>Data Set</catalog-item-type>
         <title>2016 AGIO Lidar: 6 County (Fayette, Franklin, Greene, Marion, Pickens, Sumter), AL</title>
         <relationship-type>Cross Reference</relationship-type>
      </related-item>
   </related-items>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:72897</guid>
      <metadata-record-created-by pers-id="20143">Rebecca Mataosky</metadata-record-created-by>
      <metadata-record-created>2024-06-07T13:28:25</metadata-record-created>
      <metadata-record-last-modified-by pers-id="0">SysAdmin InPortAdmin</metadata-record-last-modified-by>
      <metadata-record-last-modified>2026-03-04T19:17:17</metadata-record-last-modified>
      <record-published>2024-06-07</record-published>
      <owner-organization>OCM Partners</owner-organization>
      <owner-organization-acronym>OCMP</owner-organization-acronym>
      <owner-organization-address/>
      <owner-organization-address-city/>
      <owner-organization-address-state/>
      <owner-organization-address-zip/>
      <owner-organization-address-country/>
      <owner-organization-phone/>
      <owner-organization-url/>
      <owner-organization-business-hours/>
      <owner-organization-group-id>1002</owner-organization-group-id>
      <publication-status>Public</publication-status>
      <limited-metadata-available>No</limited-metadata-available>
      <is-do-not-publish>No</is-do-not-publish>
      <metadata-last-review-date>2024-06-07</metadata-last-review-date>
      <metadata-review-frequency>1 Year</metadata-review-frequency>
      <metadata-next-review-date>2025-06-07</metadata-next-review-date>
   </catalog-details>
</inport-metadata>
