<?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>49819</catalog-item-id>
      <title>2009-2010 USACE Vicksburg District Lidar: Mississippi River Delta</title>
      <short-name>ms2009_2010_usace_msriverdelta_phase1_m2564_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>
      <publication-date>2013-09-19</publication-date>
      <abstract>LiDAR collected at 1.0 points per square meter (1.0m GSD) for the entire portion of the Mississippi River Delta in the Vicksburg District.  This area was flown during snow free and leaf-off conditions.</abstract>
      <purpose>Classified LAS files are used to show the manually reviewed bare earth surface.  Any additional classification is provided via automated macro functionality from proprietary Photo Science TerraScan macros.  These additional classifications include Class 4 - Medium Vegetation and Class 5 - High Vegeation.  This allows the user to create Intensity Images, Break Lines, Raster DEM, and Triangular Irregular Networks.</purpose>
      <notes>10463</notes>
      <supplemental-information>A footprint of this data set may be viewed in Google Earth at:
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2564/supplemental/ms2009_2010_usace_msriverdelta_phase1.KMZ</supplemental-information>
   </item-identification>
   <keywords>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus>ISO 19115 Topic Category</thesaurus>
         <keyword>elevation</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>ASCII</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Contours</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Light Detection and Ranging</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>TIN</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>
      <maintenance-frequency>Unknown</maintenance-frequency>
      <distribution-liability>Any conclusions drawn from the analysis of this information are not the responsibility of the USACE,
Photo Science Inc (a Quantum Solution company), the Office for Coastal Management or its partners.</distribution-liability>
      <data-set-credit>Photo Science, Inc. flew and processed the LiDAR data on behalf of the Vicksburg District of the USACE.</data-set-credit>
   </data-set-information>
   <entity-attribute-information partial-listing="No" total-count="0"/>
   <support-roles>
      <support-role cc-id="678632" in-effect="Yes">
         <support-role-type>Data Steward</support-role-type>
         <from-date>2013-09-19</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="678634" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2013-09-19</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="678635" in-effect="Yes">
         <support-role-type>Metadata Contact</support-role-type>
         <from-date>2013-09-19</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="678633" in-effect="Yes">
         <support-role-type>Point of Contact</support-role-type>
         <from-date>2013-09-19</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="1134670">
         <geographic-areas>
            <geographic-area cc-id="1134672">
               <west-bound>-91.247151</west-bound>
               <east-bound>-89.726308</east-bound>
               <north-bound>35.080157</north-bound>
               <south-bound>32.301454</south-bound>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1134671">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2009-02-19</start-date-time>
               <end-date-time>2010-08-02</end-date-time>
            </time-frame>
         </time-frames>
      </extent>
   </extents>
   <spatial-information>
      <spatial-representation>
         <representations-used>
            <vector>Yes</vector>
         </representations-used>
      </spatial-representation>
   </spatial-information>
   <access-information>
      <security-class>Unclassified</security-class>
      <data-access-procedure>This data can be obtained on-line at the following URL:
https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2564
This data set is dynamically generated based on user-specified parameters.
;</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="741520">
         <download-url>https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2564</download-url>
         <file-name>Customized Download</file-name>
         <description>Create custom data files by choosing data area, product type, map projection, file format, datum, etc.</description>
      </distribution>
      <distribution cc-id="741521">
         <download-url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2564/index.html</download-url>
         <file-name>Bulk Download</file-name>
         <description>Simple download of data files.</description>
      </distribution>
   </distribution-information>
   <urls>
      <url cc-id="741524">
         <url>https://coast.noaa.gov</url>
         <url-type>Online Resource</url-type>
      </url>
      <url cc-id="741523">
         <url>https://coast.noaa.gov/dataviewer</url>
         <url-type>Online Resource</url-type>
      </url>
   </urls>
   <activity-logs>
      <activity-log cc-id="678675">
         <activity-date-time>2016-05-23</activity-date-time>
         <description>Date that the source FGDC record was last modified.</description>
      </activity-log>
      <activity-log cc-id="678674">
         <activity-date-time>2017-11-14</activity-date-time>
         <description>Converted from FGDC Content Standards for Digital Geospatial Metadata (version FGDC-STD-001-1998) using 'fgdc_to_inport_xml.pl' script. Contact Tyler Christensen (NOS) for details.</description>
      </activity-log>
      <activity-log cc-id="718390">
         <activity-date-time>2018-02-08</activity-date-time>
         <description>Partial upload of Positional Accuracy fields only.</description>
      </activity-log>
      <activity-log cc-id="741522">
         <activity-date-time>2018-03-13</activity-date-time>
         <description>Partial upload to move data access links to Distribution Info.</description>
      </activity-log>
   </activity-logs>
   <data-quality>
      <accuracy>The project area requires LiDAR to be collected on average of 1.0 meter point spacing or better and vertical accuracy of 15.0 centimeters RMSE or better to support 2' contour generation when combined with breaklines.</accuracy>
      <horizontal-positional-accuracy>Not provided.</horizontal-positional-accuracy>
      <vertical-positional-accuracy>Classified LAS files were tested by both Photo Science for both vertical and horizontal accuracy.  All data are seamless from one tile to the next, no gaps or no-data areas exists. The vertical unit of the data file is in survey feet with 2-decimal point precision.; Quantitative Value: 0.09 meters, Test that produced the value: RMSE in Meters</vertical-positional-accuracy>
      <completeness-report>Datasets contain complete coverage of tiles.</completeness-report>
      <conceptual-consistency>Classified LAS files were tested by both Photo Science for both vertical and horizontal accuracy.  All data are seamless from one tile to the next, no gaps or no-data areas exists.</conceptual-consistency>
   </data-quality>
   <lineage>
      <lineage-sources>
         <lineage-source cc-id="1134667">
            <citation-title>LiDAR</citation-title>
            <publish-date>2010-01-01</publish-date>
            <extent-type>Range</extent-type>
            <extent-start-date-time>2009-02-19</extent-start-date-time>
            <extent-end-date-time>2010-08-02</extent-end-date-time>
            <source-contribution>LiDAR points were used to produce the deliverables. | Source Geospatial Form: digital data | Type of Source Media: hard drive</source-contribution>
         </lineage-source>
      </lineage-sources>
      <lineage-process-steps>
         <lineage-process-step cc-id="1134668">
            <sequence-number>1</sequence-number>
            <description>Applanix software was used in the post processing of the airborne GPS and inertial
data that is critical to the positioning and  orientation of the sensor during all
flights.  POSPac MMS provides the smoothed best estimate of trajectory (SBET) that
is necessary for Optech's post processor to develop the point cloud from the LiDAR
missions.  The point cloud is the mathematical three dimensional collection of all
returns from all laser pulses as determined from the aerial mission.  At this point
this data is ready for analysis, classification, and filtering to generate a bare
earth surface model in which the above ground features are removed from the data
set.  The point cloud was manipulated within the Optech or Leica software; GeoCue,
TerraScan, and TerraModeler software was used for the automated data classification,
manual cleanup, and bare earth generation from this data.  Project specific macros
were used to classify the ground and to remove the side overlap between parallel
flight lines.

All data was manually reviewed and any remaining artifacts removed using
functionality provided by TerraScan and TerraModeler.

Class 2 LIDAR was used to create a bare earth surface model.  The surface model
was then used to heads-up digitize 2D breaklines of inland streams and rivers
with a 30 foot nominal width and Inland Ponds and Lakes of 0.25 acres or greater.

Elevation values were assigned to all Inland Ponds and Lakes using TerraModeler
functionality.

Elevation values were assigned to all Inland streams and rivers using Photo Science
proprietary software.

All Class 2 LIDAR data inside of the collected breaklines were then classified to
Class 9 using TerraScan macro functionality.

The breakline files were then translated to ESRI Shapefile and ARC Generate format
using ESRI conversion tools.

Breaklines were used to reclassify lakes, ponds, and inland drains.

Data was then run through additional macros to ensure deliverable classification
levels matching LAS ASPRS Classification structure.  GeoCue functionality was then
used to ensure correct LAS Version.  In house software was used as a final QA/QC
check to provide LAS Analysis of the delivered tiles.

Buffered LAS files were created in GeoCue to provide overedge to the DEM creation.
These tiles were then run through automated scripting within ArcMap and were combined
with the Hydro Flattened Breaklines to create the 5' DEM.  Final DEM tiles were
clipped to the tile boundary in order to provide a seamless dataset.

A manual QA review of the tiles was completed in ArcMap to ensure full coverage with
no gaps or slivers within the project area.</description>
            <process-date-time>2010-01-01T00:00:00</process-date-time>
            <source-citation cc-id="1134667">LiDAR</source-citation>
         </lineage-process-step>
         <lineage-process-step cc-id="1134669">
            <sequence-number>2</sequence-number>
            <description>The NOAA Office for Coastal Management (OCM) received the files in laz format. The files contained LiDAR
elevation and intensity measurements. The data were in Mississippi State Plane West (2301, feet) coordinates and NAVD88 (Geoid03) vertical datum (feet).
OCM performed the following processing for data storage and Digital Coast provisioning purposes:
1. The data were converted from State Plane (2301) coordinates to geographic coordinates.
2. The data were converted from NAVD88 (orthometric) heights to GRS80 (ellipsoid) heights using Geoid03.
3. The data were cleaned of bad elevations above 150 m and below 0 m, assumed to be errors points/noise.
4. The data were sorted by time and zipped to laz format.</description>
            <process-date-time>2013-09-19T00:00:00</process-date-time>
         </lineage-process-step>
      </lineage-process-steps>
   </lineage>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:49819</guid>
      <metadata-record-created-by pers-id="19064">Anne Ball</metadata-record-created-by>
      <metadata-record-created>2017-11-15T15:22:31</metadata-record-created>
      <metadata-record-last-modified-by pers-id="0">SysAdmin InPortAdmin</metadata-record-last-modified-by>
      <metadata-record-last-modified>2022-08-09T17:11:36</metadata-record-last-modified>
      <record-published>2022-03-16</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>2022-03-16</metadata-last-review-date>
      <metadata-review-frequency>1 Year</metadata-review-frequency>
      <metadata-next-review-date>2023-03-16</metadata-next-review-date>
   </catalog-details>
</inport-metadata>
