<?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>72957</catalog-item-id>
      <title>2013 USGS Lidar: Jefferson County, AL</title>
      <short-name>al2013_jefferson_m10141_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>2013</creation-date>
      <publication-date>2014</publication-date>
      <abstract>LiDAR generated point cloud acquired in March 2013 for the entire area of Jefferson County, Alabama (1,124 Square Miles).

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>LIDAR data is remotely sensed high-resolution elevation data collected by an airborne collection platform. Using a combination of laser range finding, GPS positioning and inertial measurement technologies; LIDAR instruments are able to make highly detailed Digital Elevation Models (DEM) of the earth's terrain, man-made structures and vegetation.  LIDAR data is used for 3D visualization, elevation based analysis and for feature extraction.  This data was collected at a nominal point spacing to support flood plain analysis, hydrological modeling, and general land use planning.</purpose>
      <supplemental-information>The LiDAR survey was conducted between March 13th, 2013 and April 4, 2014.</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>None Available</entity-attribute-detail-citation>
      <distribution-liability>The data represent the results 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.
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>Atlantic, USGS</data-set-credit>
   </data-set-information>
   <entity-attribute-information partial-listing="No" total-count="0"/>
   <support-roles>
      <support-role cc-id="1339656" 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="1339655" 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="1339682" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2014</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="1339657" 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="1339658" 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="1339659">
         <geographic-areas>
            <geographic-area cc-id="1339667">
               <west-bound>-87.343173</west-bound>
               <east-bound>-86.515073</east-bound>
               <north-bound>33.843294</north-bound>
               <south-bound>33.245076</south-bound>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1339660">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2013-03-13</start-date-time>
            </time-frame>
            <time-frame cc-id="1339661">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2013-03-14</start-date-time>
            </time-frame>
            <time-frame cc-id="1339662">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2013-03-19</start-date-time>
            </time-frame>
            <time-frame cc-id="1339663">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2013-03-20</start-date-time>
            </time-frame>
            <time-frame cc-id="1339664">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2013-03-21</start-date-time>
            </time-frame>
            <time-frame cc-id="1339665">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2013-03-28</start-date-time>
            </time-frame>
            <time-frame cc-id="1339666">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2013-08-27</start-date-time>
            </time-frame>
         </time-frames>
      </extent>
   </extents>
   <spatial-information>
      <spatial-resolution>
         <horizontal-distance>.35</horizontal-distance>
         <horizontal-distance-units>Meter</horizontal-distance-units>
      </spatial-resolution>
      <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>None</data-access-constraints>
      <data-use-constraints>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.</data-use-constraints>
   </access-information>
   <distribution-information>
      <distribution cc-id="1339668">
         <download-url>https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=10141/details/10141</download-url>
         <distributor cc-id="1339655">
            <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="1339669">
         <download-url>https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/Jefferson_County_AL_LIDAR/AL_JeffersonCo_2013/LAZ/</download-url>
         <distributor cc-id="1339682">
            <from-date>2014</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, Alabama State Plane West, NAD83, US survey feet coordinates and NAVD88 (Geoid 12A) elevations in feet.</description>
         <distribution-format>LAS/LAZ - LASer</distribution-format>
         <compression>LAZ</compression>
      </distribution>
   </distribution-information>
   <urls>
      <url cc-id="1339653">
         <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="1339686">
         <url>https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/Jefferson_County_AL_LIDAR/AL_JeffersonCo_2013/</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 may include reports, tile index shapefiles, and hydro breaklines.</description>
      </url>
      <url cc-id="1339687">
         <url>https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/Jefferson_County_AL_LIDAR/AL_JeffersonCo_2013/reports/13145_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="1339688">
         <url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_AL_JeffersonCo_2013_LAS_2015/ept.json</url>
         <name>USGS Entwine Point Tile (EPT)</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="1339689">
         <url>https://usgs.entwine.io/data/view.html?r=%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_AL_JeffersonCo_2013_LAS_2015%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>Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog V. 10.1 build 3085</description>
   </technical-environment>
   <data-quality>
      <horizontal-positional-accuracy>LiDAR data horizontal accuracy is contracted to meet a 1.0 meter (RMSE) or better. Horizontal point accuracy is a function of angular origination of the pulse; IMU orientation; the scanner encoder and ranging function and will vary depending on the proposed point density selected for the collection. Statistically, the error is roughly 1/3 of the illuminated foot print on the ground and is a function of the beam divergences.</horizontal-positional-accuracy>
      <vertical-positional-accuracy>Vertical Accuracy for the Jefferson County LiDAR data was assessed and reported in accordance with guidelines developed by the National Digital Elevation Program (NDEP) and subsequently adopted by the American Society for Photogrammetry and Remote Sensing (ASPRS). Guidelines are listed below:
	Fundamental Vertical Accuracy (FVA)&lt;=24.5cm ACCz, 95% RMSEz (12.5 cm) 
	Consolidated Vertical Accuracy (CVA)&lt;=36.3cm ACCz, 95% RMSEz  (12.5 cm) 
	Supplemental Vertical Accuracy (SVA)&lt;=36.3cm ACCz, 95% RMSEz (12.5 cm)
Based on the vertical accuracy testing conducted by Atlantic using NDEP methodology, the dataset for Jefferson County, AL
Tested 0.19 cm FVA ; Fundamental Vertical Accuracy in Open Terrain at 95th percentile (RMSEz x 1.9600) or 8.4 cm RMSE, Spec=24.5 cm
Tested 0.24 cm CVA ; Consolidated Vertical Accuracy at 95th percentile (RMSEz x 1.9600), Spec=36.3 cm
Tested 0.22 cm SVA ; Supplemental Vertical Accuracy at 95th percentile (RMSEz x 1.9600), Spec=36.5 cm</vertical-positional-accuracy>
      <completeness-report>LIDAR raster data was visually inspected for completeness to ensure that any gaps between flight lines of required collection area. LIDAR is self-illuminating and has minimal cloud penetration capability. Water vapor in steam plumes or particulates in smoke may cause reflection of LIDAR signals and loss of elevation information beneath these plumes. Glass structures and roofs may appear transparent to the LIDAR signal and therefore may not register on the reflective surface.</completeness-report>
      <conceptual-consistency>Bare-earth processed data for this acquisition block comply with the following accuracy requirements for Artifact/Feature removal:  artifacts - 90%; outliers - 95%; vegetation - 95%; buildings - 98%.  All LAS formatted LIDAR data are validated using commercial GIS software to ensure proper formatting and loading before delivery. This validation procedure ensures that data on delivery media is in correct physical format and is readable.</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="1339690">
            <citation-title>USGS AWS Entwine Point Tile (EPT)</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_JeffersonCo_2013_LAS_2015/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="1339644">
            <sequence-number>1</sequence-number>
            <description>The ABGPS, IMU, and raw Leica ALS70HP LiDAR data are integrated into the IPAS post processor software. The resultant file is in a LAS binary file format. The LAS file version 1.2 formats 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 produced in the geodetic coordinates referenced to the WGS1984_UTM16N horizontal datum and Ellipsoid Height, Meters.</description>
            <process-date-time>2013-09-10T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1339645">
            <sequence-number>2</sequence-number>
            <description>The initial step of calibration is to verify availability and status of all needed GPS and Laser data against field notes and compile any data if not complete. Subsequently the mission points are output using Leica's ALS Post Processor, initially with default values from Leica or the last mission calibrated for the system. The initial point generation for each mission calibration is verified within Terrascan using a distance colored point cloud to identify errors. If a calibration error greater than specification is observed within the mission, the roll, pitch and scanner scale corrections that need to be applied are calculated. The missions with the new calibration values are output again and validated internally to ensure quality. Once validated each output mission is imported into the Geocue software package. Here a project level supplementary coverage check is carried out to ensure no data voids unreported by Field Operations are present.</description>
            <process-date-time>2013-09-15T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1339646">
            <sequence-number>3</sequence-number>
            <description>Conversion from Geodetic coordinates WGS_1984 into NAD_1883_2011_UTM16N, NAVD88 (Geoid12A) Orthometric height, meters, was done using GeoCue.</description>
            <process-date-time>2013-11-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1339647">
            <sequence-number>4</sequence-number>
            <description>The unedited data are classified to facilitate the application of the appropriate feature extraction filters. A combination of proprietary filters is applied as appropriate for the production of bare earth digital terrain models (dtms).  Interactive editing methods are applied to those areas where it is inappropriate or impossible to use the feature extraction filters, based upon the design criteria and/or limitations of the relevant filters. These same feature extraction filters are used to produce elevation height surfaces. The LiDAR mass points were delivered in American Society for Photogrammetry and Remote Sensing LAS 1.2 format.  The header file for each dataset is complete as define by the LAS 1.2 specification.  The data was classified as follows: Class 1 = Unclassified.  This class includes all non-ground classified points. Class 2 = Ground.  Class 7 = Low Points.  Class 9 = water.  Class 10 - breakline proximity.  Class 12 = Overlap.</description>
            <process-date-time>2013-12-02T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1339648">
            <sequence-number>5</sequence-number>
            <description>Dataset copied to delivery drive, and content reviewed.</description>
            <process-date-time>2014-03-03T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1339691">
            <sequence-number>6</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) and the vertical units were converted to meters (NAVD88 GEOID12A).</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-step cc-id="1339692">
            <sequence-number>7</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.

This is the EPT file being accessed:

https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_AL_JeffersonCo_2013_LAS_2015/ept.json</description>
            <process-date-time>2024-06-12T00: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-steps>
   </lineage>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:72957</guid>
      <metadata-record-created-by pers-id="20143">Rebecca Mataosky</metadata-record-created-by>
      <metadata-record-created>2024-06-12T19:38:08</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-12</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-12</metadata-last-review-date>
      <metadata-review-frequency>1 Year</metadata-review-frequency>
      <metadata-next-review-date>2025-06-12</metadata-next-review-date>
   </catalog-details>
</inport-metadata>
