<?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>49832</catalog-item-id>
      <title>2003 NCFMP Lidar: NC Statewide Phase 2</title>
      <short-name>nc2003_phase2_m5010_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>2016-03-11</publication-date>
      <abstract>Airborne LIDAR terrain mapping data acquired January through March 2003.  Point data (XYZ) in ASCII format. Horizontal datum NAD83(1995) North Carolina State Plane feet. Vertical datum NAVD88 US Survey Feet. These data may represent a single geographic tile of a larger, county/sub-county data set. As such, the map extent indicated in the Spatial_Domain element is representative of the larger data set and not an individual tile. The data are organized in 10,000 ft x 10,000 ft tiles using the NC Bureau of Land Records Management (LRMP) standards.  Specific information about individual data tiles is included in the data delivery index.  LAS tiles were received at NOAA OCM.</abstract>
      <purpose>These data were collected and derived by the North Carolina Floodplain Mapping Program as part of its effort to modernize FEMA Flood Insurance Rate Maps (FIRM) statewide. Although created for specific use in the engineering aspects of floodplain delineation, the data were also developed to address the elevation data requirements of the broader geospatial data user community. The North Carolina Floodplain Mapping Program was established in response to the extensive damage caused by Hurricane Floyd in 1999.</purpose>
      <notes>10476</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/5010/supplemental/nc2003_ncfmp_phase2_m5010.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>Contour</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>ESRI</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Flood</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Floodplain</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Shapefile</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>None Planned</maintenance-frequency>
      <entity-attribute-overview>Files in LAZ format (Unclassified, class 1 only)</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 NC Floodplain Mapping Program, EarthData, the NOAA 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="679357" in-effect="Yes">
         <support-role-type>Data Steward</support-role-type>
         <from-date>2016-03-11</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="679359" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2016-03-11</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="679360" in-effect="Yes">
         <support-role-type>Metadata Contact</support-role-type>
         <from-date>2016-03-11</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="679358" in-effect="Yes">
         <support-role-type>Point of Contact</support-role-type>
         <from-date>2016-03-11</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="1137650">
         <geographic-areas>
            <geographic-area cc-id="1137652">
               <west-bound>-82.296</west-bound>
               <east-bound>-76.56061</east-bound>
               <north-bound>36.58547</north-bound>
               <south-bound>34.87411</south-bound>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1137651">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2003-01-03</start-date-time>
               <end-date-time>2003-03-23</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=5010;</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 that 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 sets were created with the highest consideration of accuracy and data integrity.  However, as with all other geospatial data sets, users must take into consideration the consequences of using the data for specific applications, business processes, decisions, and map display. For example, surface conditions may have changed in some areas since the initial data was captured. A full metadata record is provided to help the user understand the date, map scale and accuracy standard applied in the collection and data development process. The data should not be used without full review and comprehension of the metadata.  acknowledgement of the North Carolina Floodplain Mapping Program is appreciated when using the data set. Data further derived from this data set should be fully documented using the federal metadata standard and listed via the NC Geospatial Data Clearinghouse.</data-use-constraints>
   </access-information>
   <distribution-information>
      <distribution cc-id="741599">
         <download-url>https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=5010</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="741600">
         <download-url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/5010/index.html</download-url>
         <file-name>Bulk Download</file-name>
         <description>Simple download of data files.</description>
      </distribution>
   </distribution-information>
   <urls>
      <url cc-id="741604">
         <url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/5010/supplemental/nc2003_ncfmp_phase2_m5010.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 North Carolina Statewide Lidar Phase 2 collection.</description>
      </url>
      <url cc-id="741603">
         <url>https://coast.noaa.gov</url>
         <url-type>Online Resource</url-type>
      </url>
      <url cc-id="741602">
         <url>https://coast.noaa.gov/dataviewer</url>
         <url-type>Online Resource</url-type>
      </url>
   </urls>
   <activity-logs>
      <activity-log cc-id="679425">
         <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="679424">
         <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="718405">
         <activity-date-time>2018-02-08</activity-date-time>
         <description>Partial upload of Positional Accuracy fields only.</description>
      </activity-log>
      <activity-log cc-id="741601">
         <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>LIDAR full returns were compared with NCGS QA/QC checkpoints using only single and final returns per pulse. A vertical bias was aquired after airport calibration based on this comparison. For the NC Floodplain Mapping Program, the vertical accuracy for coastal counties is less than or equal to 20 cm
RMSE.  For mainland counties, the vertical accuracy of the elevation data is less than or equal to 25 cm RMSE. | Quantitative Value: less than 20 cm | Quantitative Test Explanation: RMSE (cm) of bare earth LIDAR points compared with independent checkpoints</accuracy>
      <horizontal-positional-accuracy>LIDAR full return mass points were compared with surveyed elevations provided by independent contractors to theNCGS.
More information about the Quality Control reports is available through NCFMP.
Numerous internal quality assurance/quality control steps taken to ensure the quality of the LIDAR terrain data to meet the bare earth requirements and RMSE accuracy standards in the NC Floodplain Mapping Program.
Step 1.  Preprocessing
Step 2.  Post-Automated Editing QC (Data Evaluation)
Step 3.  QC Check of Tiles
Step 4.  Manual Editing (Hillshade Checks / Peer Review)
Step 5.  QC and Tile Edge Matching
Step 6.  Final EarthData QC
Step 7.  Comparisons of Independent Field Survey Data with LIDAR Data; Quantitative Value: 2 meters, Test that produced the value: RMSE (m) of bare earth LIDAR points compared with independent checkpoints</horizontal-positional-accuracy>
      <vertical-positional-accuracy>LIDAR full return mass points were compared with surveyed elevations provided by independent contractors to the NCGS.  A vertical bias was acquired after airport calibration based on this comparison.
For the NC Floodplain Mapping Program, the vertical accuracy for coastal counties is less than or equal to 20 cm RMSE.  For mainland counties, the vertical accuracy of the elevation data is less than or equal to 25 cm RMSE.
Numerous internal quality assurance/quality control steps were taken to ensure the quality of the LIDAR terrain data to meet the bare earth requirements and RMSE accuracy standards in the NC Floodplain Mapping Program.
Step 1.  Preprocessing
Step 2.  Post-Automated Editing QC (Data Evaluation)
Step 3.  QC Check of Tiles
Step 4.  Manual Editing (Hillshade Checks / Peer Review)
Step 5.  QC and Tile Edge Matching
Step 6.  Final EarthData QC
Step 7.  Comparisons of Independent Field Survey Data with LIDAR Data; Quantitative Value: 0.20 meters, Test that produced the value: RMSE (m) of bare earth LIDAR points compared with independent checkpoints</vertical-positional-accuracy>
      <completeness-report>The full return mass points contain voids where insufficient energy was reflected from the surface to generate a valid return from the terrain.  Voids in the full return mass points tend to occur in water bodies.  Wet sand and certain types of vegetation can also cause voids or anomalous elevations.</completeness-report>
      <conceptual-consistency>Data was vertically adjusted based on RMSE and mean difference from control report</conceptual-consistency>
   </data-quality>
   <lineage>
      <lineage-process-steps>
         <lineage-process-step cc-id="1137645">
            <sequence-number>1</sequence-number>
            <description>All data collection flights were initialized and finalized during periods of GPS Position Dilution of Precision greater than 4.  GPS data quality was  evaluated post-flight to ensure sufficient quality for LIDAR data requirements and integration.  GPS base maximum allowable distance between stations was established such that no more than a 50 mile radius occurred between occupations.  Swath width of terrain covered in a single flightline at an altitude of 10,000 feet AMT was approximately 3,173 meters.  Field of View for the Leica GeoSystems Aeroscan system used was 55 degrees project wide, or approximately 27.5 degrees from nadir with a maximum of 5 returns collected for each pulse.  Nominal post spacing for finalized Bare Earth product was 2 meters. An average of 10-20 rapid static GPS survey collected ground control points were established per base airport project wide to detect and correct horizontal and vertical bias. Typically, 3 or more flightlines of LIDAR returns were collected for each airport lift, one of which being  bi-directional for use in optimizing instrument boresight angles to account for aircraft pitch, yaw and roll.  All post process collection quality assurance is achieved aided by airport cross and bi-directional flightlines, entire lift cross flightlines, and the use of surveyed ground control points.</description>
            <process-date-time>2003-12-22T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1137646">
            <sequence-number>2</sequence-number>
            <description>- Checking for coverage and anomalies 
- Airport calibration
- Production flightline calibration
- Removal of blunders</description>
            <process-date-time>2003-12-22T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1137647">
            <sequence-number>3</sequence-number>
            <description>Tiling, Automated filtering for point classification, Manual editing to classify points, Quality control</description>
            <process-date-time>2003-12-22T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1137648">
            <sequence-number>4</sequence-number>
            <description>The methods used to develop these data for the North Carolina Floodplain Mapping Program are documented in LIDAR Bare Earth Mass Points and Breaklines Technical Document.</description>
            <process-date-time>2006-04-26T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1137649">
            <sequence-number>5</sequence-number>
            <description>The lidar point data were received by the NOAA Office for Coastal Management from USGS CLICK.  The data were LAS format, horizontal datum NAD83 North Carolina State Plane (3200) feet, vertical datum NAVD88 US Survey Feet and contained elevation, intensity measurements and classifications. OCM performed the following processing for data storage and Digital Coast provisioning purposes:
1. The data were converted from State Plane coordinates to geographic coordinates in decimal degrees.
2. The data were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid03.</description>
            <process-date-time>2016-02-26T00:00:00</process-date-time>
         </lineage-process-step>
      </lineage-process-steps>
   </lineage>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:49832</guid>
      <metadata-record-created-by pers-id="19064">Anne Ball</metadata-record-created-by>
      <metadata-record-created>2017-11-15T15:22:36</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>
