<?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>49823</catalog-item-id>
      <title>2012 NRCS-USGS Tupelo, MS Lidar Survey</title>
      <short-name>ms2012_usgs_nrcs_tupelo_m2559_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-06</publication-date>
      <abstract>LiDAR data is a remotely sensed high resolution elevation data collected by an airborne
platform. The LiDAR sensor uses a combination of laser range finding, GPS positioning,
and inertial measurement technologies. The LiDAR systems collect data point clouds that
are used to produce highly detailed Digital Elevation Models (DEMs) of the earth's terrain,
man-made structures and vegetation. The task required the LiDAR data to be collected at a
nominal pulse spacing (NPS) of 1.0 meter. The final products include first, last, and at
least one intermediate return LAS, full classified LAS and one (1) meter pixel raster DEMs
of the bare-earth surface in ERDAS IMG Format. The LiDAR data was acquired from February 07,
2012 to March 05, 2012.

Original contact information: 
   Contact Org: USGS/NGTOC
   Phone: (573) 308-654</abstract>
      <purpose>This task order consisted of LiDAR data acquisition and processing for the USGS. The
task required the LiDAR data to be collected at a nominal pulse spacing (NPS) of 1.0 meter.
The LiDAR data was collected to meet the National Standard for Spatial Database Accuracy
(NSSDA) accuracy standards. The LiDAR data was provided in 1,500 meters x 1,500 meters
tiles in the UTM projection. The LiDAR tile file name was derived from the southwest corner
of each tile. The tiles are named based on the US National Grid.</purpose>
      <notes>10467</notes>
      <supplemental-information>A lidar report from the vendor for this data set may be viewed here:
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2559/supplemental/ms2012_usgs_nrcs_tupelo.pdf
A footprint of this data set may be viewed in Google Earth at:
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2559/supplemental/ms2012_usgs_nrcs_tupelo.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>LAZ</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>As Needed</maintenance-frequency>
      <data-presentation-form>laz</data-presentation-form>
      <entity-attribute-overview>LiDAR points in LAZ format</entity-attribute-overview>
      <entity-attribute-detail-citation>none</entity-attribute-detail-citation>
      <distribution-liability>Any conclusions drawn from the analysis of this information are not the responsibility
of USGS, NRCS, Woolpert, Inc., NOAA, the Office for Coastal Management or its partners.</distribution-liability>
   </data-set-information>
   <entity-attribute-information partial-listing="No" total-count="0"/>
   <support-roles>
      <support-role cc-id="678853" in-effect="Yes">
         <support-role-type>Data Steward</support-role-type>
         <from-date>2013-09-06</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="678855" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2013-09-06</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="678856" in-effect="Yes">
         <support-role-type>Metadata Contact</support-role-type>
         <from-date>2013-09-06</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="678854" in-effect="Yes">
         <support-role-type>Point of Contact</support-role-type>
         <from-date>2013-09-06</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="1134571">
         <geographic-areas>
            <geographic-area cc-id="1134586">
               <west-bound>-89.174071</west-bound>
               <east-bound>-88.28357</east-bound>
               <north-bound>34.596635</north-bound>
               <south-bound>32.683739</south-bound>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1134572">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2012-02-07</start-date-time>
            </time-frame>
            <time-frame cc-id="1134573">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2012-02-08</start-date-time>
            </time-frame>
            <time-frame cc-id="1134574">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2012-02-09</start-date-time>
            </time-frame>
            <time-frame cc-id="1134575">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2012-02-11</start-date-time>
            </time-frame>
            <time-frame cc-id="1134576">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2012-02-12</start-date-time>
            </time-frame>
            <time-frame cc-id="1134577">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2012-02-15</start-date-time>
            </time-frame>
            <time-frame cc-id="1134578">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2012-02-17</start-date-time>
            </time-frame>
            <time-frame cc-id="1134579">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2012-02-24</start-date-time>
            </time-frame>
            <time-frame cc-id="1134580">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2012-02-25</start-date-time>
            </time-frame>
            <time-frame cc-id="1134581">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2012-02-26</start-date-time>
            </time-frame>
            <time-frame cc-id="1134582">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2012-02-29</start-date-time>
            </time-frame>
            <time-frame cc-id="1134583">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2012-03-03</start-date-time>
            </time-frame>
            <time-frame cc-id="1134584">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2012-03-04</start-date-time>
            </time-frame>
            <time-frame cc-id="1134585">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2012-03-05</start-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=2559
;</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. These data
depict the heights at the time of the survey and are only accurate for that time.</data-use-constraints>
   </access-information>
   <distribution-information>
      <distribution cc-id="741543">
         <download-url>https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2559</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="741544">
         <download-url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2559/index.html</download-url>
         <file-name>Bulk Download</file-name>
         <description>Simple download of data files.</description>
      </distribution>
   </distribution-information>
   <urls>
      <url cc-id="741548">
         <url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2559/supplemental/ms2012_usgs_nrcs_tupelo.kmz</url>
         <name>Browse Graphic</name>
         <url-type>Browse Graphic</url-type>
         <file-resource-format>kmz</file-resource-format>
         <description>This graphic shows the lidar coverage for the Tupelo, Mississippi
USGS-NRCS lidar survey collected in 2012.</description>
      </url>
      <url cc-id="741547">
         <url>https://coast.noaa.gov</url>
         <url-type>Online Resource</url-type>
      </url>
      <url cc-id="741546">
         <url>https://coast.noaa.gov/dataviewer</url>
         <url-type>Online Resource</url-type>
      </url>
   </urls>
   <activity-logs>
      <activity-log cc-id="678901">
         <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="678900">
         <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="718394">
         <activity-date-time>2018-02-08</activity-date-time>
         <description>Partial upload of Positional Accuracy fields only.</description>
      </activity-log>
      <activity-log cc-id="741545">
         <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>
   <technical-environment>
      <description>Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 3</description>
   </technical-environment>
   <data-quality>
      <horizontal-positional-accuracy>Horizontal accuracy is +/- 3.8-foot (115 cm) at the 95%
confidence level. LiDAR system calibration is available in the project report.</horizontal-positional-accuracy>
      <vertical-positional-accuracy>LAS data covering the Tupelo, MS 1m NPS Lidar Task Order was compared to survey control points to determine the FVA of the LAS Swath and of the Bare-Earth DEM. In addition, this LAS data was compared to supplemental points from categories: Bare Earth Open Terrain, Urban, Tall Weeds/Crops, Brush Lands and Trees, and Forested Fully Grown. 

LAS Swath Fundamental Vertical Accuracy (FVA)
Tested 0.16 meters fundamental vertical accuracy at 95 percent confidence level in open terrain using RMSE(z) x 1.9600

Supplemental Vertical Accuracy (SVA)
Bare Earth/Open Terrain Land Cover Classification Supplemental Vertical Accuracy (SVA) Tested 0.101 meters supplemental vertical accuracy at the 95th percentile in Bare Earth/Open Terrain. Tested against the DEM.
Brush Lands and Trees Land Cover Classification Supplemental Vertical Accuracy (SVA) Tested 0.322 meters supplemental vertical accuracy at the 95th percentile in Brush Lands and Trees. Tested against the DEM.
Forested and Fully Grown Land Cover Classification Supplemental Vertical Accuracy (SVA) Tested 0.128 meters supplemental vertical accuracy at the 95th percentile in Forested and Fully Grown. Tested against the DEM.
Tall Weeds/Crops Land Cover Classification Supplemental Vertical Accuracy (SVA) Tested 0.265 meters supplemental vertical accuracy at the 95th percentile in Tall Weeds/Crops. Tested against the DEM.
Urban Land Cover Classification Supplemental Vertical Accuracy (SVA) Tested 0.081 meters supplemental vertical accuracy at the 95th percentile in Urban. Tested against the DEM.

Consolidated Vertical Accuracy (CVA)
Tested 0.200 meters consolidated vertical accuracy at the 95th percentile level, derived according to ASPRS Guidelines for Vertical Accuracy Reporting for LiDAR Data. Tested against the DEM.</vertical-positional-accuracy>
      <completeness-measure>Cloud Cover: 0</completeness-measure>
      <completeness-report>Complete</completeness-report>
      <conceptual-consistency>This data is visually inspected by Woolpert, Inc.</conceptual-consistency>
   </data-quality>
   <lineage>
      <lineage-process-steps>
         <lineage-process-step cc-id="1134566">
            <sequence-number>1</sequence-number>
            <description>Using Leica ALS60(LiDAR) system, 233 flight lines of high density data, at a nominal pulse
spacing (NPS) of 1 meter, were collected for the NRCS Tupelo, MS (approximately 3,697
square miles). Data Acquisition Height = 6,500 feet AGL - Aircraft Speed = 130 Knots.
Multiple returns were recorded for each laser pulse along with an intensity value for
each return. A total of fourteen (14) missions were flown during a period of February 07,
2012 through March 05, 2012. Two airborne global positioning system (GPS) base stations
were used in support of the LiDAR data acquisition. 18 ground control points were
surveyed through static methods. The geoid used to reduce satellite derived elevations
to orthometric heights was Geoid09. Data for the task order is referenced to the UTM Zone
16N, North American Datum of 1983 (NAD83), and NAVD88, in Meters. Airborne GPS data was
differentially processed and integrated with the post processed IMU data to derive a
smoothed best estimate of trajectory (SBET). The SBET was used to reduce the LiDAR slant range
measurements to a raw reflective surface for each flight line. The coverage was classified to
extract a bare earth digital elevation model (DEM) and separate last returns. In addition to the
LAS deliverables, one layer of coverage was delivered in the IMG Format: bare-earth.</description>
            <process-date-time>2012-02-07T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1134567">
            <sequence-number>2</sequence-number>
            <description>The ALS60 calibration and system performance is verified on a periodic basis
using Woolpert's calibration range. The calibration range consists of a large building and
runway. The edges of the building and control points along the runway have been located
using conventional survey methods. Inertial measurement unit (IMU) misalignment angles
and horizontal accuracy are calculated by comparing the position of the building edges
between opposing flight lines. The scanner scale factor and vertical accuracy is
calculated through comparison of LiDAR data against control points along the runway.
Field calibration is performed on all flight lines to refine the IMU misalignment angles.
IMU misalignment angles are calculated from the relative displacement of features within
the overlap region of adjacent (and opposing) flight lines. The raw LiDAR data is reduced
using the refined misalignment angles.</description>
            <process-date-time>2011-01-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1134568">
            <sequence-number>3</sequence-number>
            <description>Once the data acquisition and GPS processing phases are complete, the LiDAR
data was processed immediately to verify the coverage had no voids. The GPS and IMU data was
post processed using differential and Kalman filter algorithms to derive a best estimate of
trajectory. The quality of the solution was verified to be consistent with the accuracy
requirements of the project.</description>
            <process-date-time>2012-02-08T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1134569">
            <sequence-number>4</sequence-number>
            <description>The individual flight lines were inspected to ensure the systematic
and residual errors have been identified and removed. Then, the flight lines were compared
to adjacent flight lines for any mismatches to obtain a homogenous coverage throughout the
project area. The point cloud underwent a classification process to determine bare-earth points
and non-ground points utilizing "first and only" as well as "last of many" LiDAR returns. This
process determined Default (Class 1), Ground (Class 2), Noise (Class 7), Water (Class 9),
Ignored Ground (Class 10), Overlap Default (Class 17), and Overlap Ground (Class 18). The
bare-earth (Class 2 - Ground) LiDAR points underwent a manual QA/QC step to verify that
artifacts have been removed from the bare-earth surface. The surveyed ground control
points are used to perform the accuracy checks and statistical analysis of the LiDAR dataset.</description>
            <process-date-time>2012-05-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1134570">
            <sequence-number>5</sequence-number>
            <description>The NOAA Office for Coastal Management (OCM) received topographic files in .LAZ format. The files contained
lidar elevation and intensity measurements. The data were received in UTM Zone 16 N (meters) and NAVD88
vertical datum (meters). OCM performed the following processing for data storage and Digital Coast
provisioning purposes:
1. The topographic laz files were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid09.
2. The topographic laz files were transformed from UTM Zone 16N to a Geographic Coordinate system (NAD83).
3. The topographic laz files were cleaned of high and low error points and variable length records (vlr) were removed.
4. The topographic las files' horizontal units were converted from meters to decimal degrees.</description>
            <process-date-time>2013-09-05T00:00:00</process-date-time>
         </lineage-process-step>
      </lineage-process-steps>
   </lineage>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:49823</guid>
      <metadata-record-created-by pers-id="19064">Anne Ball</metadata-record-created-by>
      <metadata-record-created>2017-11-15T15:22:32</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>
      <best-available-metadata>No</best-available-metadata>
      <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>
