<?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>49988</catalog-item-id>
      <title>2010 ARRA Lidar: Hampton County (SC)</title>
      <short-name>sc2010_arra_hampton_m4803_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>2011-05</publication-date>
      <abstract>Provide high density LiDAR elevation data map of Hampton County, SC. Provide Bare Earth DEM (vegetation removal) of Hampton County, SC.</abstract>
      <purpose>This LIDAR operation was designed to provide a high density set of masspoints within the defined areas. The data sets are suitable for the development of contours for use in hydraulic/hydrologic model development, and for assessing environmental impacts.Typical uses for the data set include: FEMA Flood Plain Map Modernization. DFIRM map updates. Watersheds and other hydro studies per FEMA specifications. County Mapping projects which include several uses, in addition to Flood mitigation assessment. Mapping projects that include accuracy verification, reporting and meta data.</purpose>
      <notes>10632</notes>
      <supplemental-information>The lidar report for this data set may be viewed at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4803/supplemental/sc2010_arra_hampton_m4803_lidarreport.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/4803/supplemental/sc2010_arra_hampton_m4803.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>Surface</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Terrain</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-note>None planned</maintenance-note>
      <entity-attribute-overview>LAS 1.2</entity-attribute-overview>
      <entity-attribute-detail-citation>See process steps within this metadata record for specific methodology</entity-attribute-detail-citation>
      <distribution-liability>Any conclusions drawn from the analysis of this information are not the responsibility of Sanborn, SC DNR, USGS, 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="685958" in-effect="Yes">
         <support-role-type>Data Steward</support-role-type>
         <from-date>2011-05</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="685960" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2011-05</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="685961" in-effect="Yes">
         <support-role-type>Metadata Contact</support-role-type>
         <from-date>2011-05</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="685959" in-effect="Yes">
         <support-role-type>Point of Contact</support-role-type>
         <from-date>2011-05</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="1136483">
         <geographic-areas>
            <geographic-area cc-id="1136485">
               <west-bound>-81.82115324</west-bound>
               <east-bound>-81.43860006</east-bound>
               <north-bound>33.0276575</north-bound>
               <south-bound>32.5463144</south-bound>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1136484">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2010-03-20</start-date-time>
               <end-date-time>2010-03-24</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=4803
The 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. These data depict the heights at the time of the survey and are only accurate for that time</data-use-constraints>
      <metadata-use-constraints>This dataset is not valid without the signed and sealed copy of the Florida Minimum Technical Standards Report
of Specific Purpose Survey dated 4/31/2008. Please refer to this document for user constraints.</metadata-use-constraints>
   </access-information>
   <distribution-information>
      <distribution cc-id="742464">
         <download-url>https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=4803</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="742465">
         <download-url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4803/index.html</download-url>
         <file-name>Bulk Download</file-name>
         <description>Simple download of data files.</description>
      </distribution>
   </distribution-information>
   <urls>
      <url cc-id="742469">
         <url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4803/supplemental/sc2010_arra_hampton_m4803.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 2010 ARRA lidar for Hampton County, SC.</description>
      </url>
      <url cc-id="742468">
         <url>https://coast.noaa.gov</url>
         <url-type>Online Resource</url-type>
      </url>
      <url cc-id="742467">
         <url>https://coast.noaa.gov/dataviewer</url>
         <url-type>Online Resource</url-type>
      </url>
   </urls>
   <activity-logs>
      <activity-log cc-id="685977">
         <activity-date-time>2017-04-04</activity-date-time>
         <description>Date that the source FGDC record was last modified.</description>
      </activity-log>
      <activity-log cc-id="685976">
         <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="718589">
         <activity-date-time>2018-02-08</activity-date-time>
         <description>Partial upload of Positional Accuracy fields only.</description>
      </activity-log>
      <activity-log cc-id="742466">
         <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 flight missions were typically four or five hours in duration including runway calibration flights flown at the beginning and the end of each mission. During the data collection, the operator recorded information on log sheets which includes weather conditions, LiDAR operation parameters, and flight line statistics. Near the end of the mission GPS ambiguities are again resolved by flying within ten kilometers of the base stations, to aid in post-processing.</accuracy>
      <horizontal-positional-accuracy>Federal Emergency Management Administration (FEMA) LiDAR Specifications; Quantitative Value: 1.00 meters, Test that produced the value: Processing accuracies and requirements</horizontal-positional-accuracy>
      <vertical-positional-accuracy>Federal Emergency Management Administration (FEMA) LiDAR Specifications; 15 cm RMSE; Quantitative Value: 0.099 meters, Test that produced the value: The LiDAR data was evaluated using a collection of 6 NGS benchmarks. For Hampton County, the standard deviation is 0.353 feet and the root mean squared is 0.324 feet (9.9 cm). The LiDAR data was compared to each of these benchmarks yielding much better results than was required for the project.</vertical-positional-accuracy>
      <completeness-report>Complete</completeness-report>
      <conceptual-consistency>A minimum of two GPS base stations were set for the Hampton County project, which is within the project area or within the required baseline specifications of the project.
Pre-flight checks such as cleaning the sensor head glass are performed. A four minute INS initialization is conducted on the ground, with the engines running, prior to flight, to establish fine-alignment of the INS. GPS ambiguities are resolved by flying within ten kilometers of the base stations.</conceptual-consistency>
   </data-quality>
   <lineage>
      <lineage-process-steps>
         <lineage-process-step cc-id="1136478">
            <sequence-number>1</sequence-number>
            <description>Data Collection: 
Using an Optech Light Detection And Ranging (LiDAR) system, 103 flight lines of standard density (1.4 meter ground sample distance) data were collected over areas in Hampton, SC (approximately 395 square miles). Multiple returns were recorded for each laser pulse along with an intensity value for each return. The data acquisition occurred in 6 missions between March 14, 2010 , and March 20, 2010. During the LIDAR campaign, the LMSI field crew conducted a GPS field survey to establish final coordinates of the ground base stations for final processing of the base-remote GPS solutions</description>
            <process-date-time>2010-03-20T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1136479">
            <sequence-number>2</sequence-number>
            <description>Airborne GPS Processing: 
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 overlap between flight lines was removed to provide a homogeneous coverage, and the coverage was classified to extract a bare earth digital elevation model (DEM). Airborne GPS is differentially processed using the GrafNAV V7.50 software by Waypoint Consulting of Calgary, Alberta, Canada. The PDOP and distance separation is as follows: The classification and quality control (QC) of LiDAR data is carried out using TerraScan software by Terrasolid Limited of Helsinki, Finland.</description>
            <process-date-time>2010-04-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1136480">
            <sequence-number>3</sequence-number>
            <description>IMU data Processing: 
IMU data provides information concerning roll, pitch and yaw of collection platform during collection event. IMU information allows the pulse vector to be properly placed in 3D space allowing the distance from the aircraft reference point to be properly positioned on the elevation model surface. The IMU data is processed using the PosPac V4.2 software by Applanix Corporation of Richmond Hill, Ontario, Canada. The reflective surface is derived using the ALS Post Processor software by Leica Geosystems GIS &amp; Mapping Division of Atlanta, Georgia.</description>
            <process-date-time>2010-04-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1136481">
            <sequence-number>4</sequence-number>
            <description>LIDAR Point Classification:
The classification and quality control (QC) of LiDAR data is carried out using TerraScan software by Terrasolid Limited of Helsinki, Finland.</description>
            <process-date-time>2010-05-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1136482">
            <sequence-number>5</sequence-number>
            <description>The NOAA Office for Coastal Management (OCM) received the files in laz format from USGS via an FTP online repository. The files contained lidar elevation and intensity measurements. The data were in State Plane Zone 3900 (South Carolina, NAD83) in feet, NAVD88 (orthometric) heights in feet. OCM performed the following processing for data storage and Digital Coast provisioning purposes:
1. The LAS files were converted from SPCS coordinates to geographic coordinates.
2. Erroneous elevations were removed.
3. The LAS files were converted from NAVD88 (orthometric) heights in meters to GRS80 (ellipsoid) heights in meters using Geoid 03.
4. The LAS data were sorted by latitude and the headers were updated.</description>
            <process-date-time>2015-04-17T00:00:00</process-date-time>
         </lineage-process-step>
      </lineage-process-steps>
   </lineage>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:49988</guid>
      <metadata-record-created-by pers-id="19064">Anne Ball</metadata-record-created-by>
      <metadata-record-created>2017-11-15T15:23:35</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:37</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>
