<?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>49726</catalog-item-id>
      <title>2009 USGS Potato Creek Lidar Survey</title>
      <short-name>ga2009_usgs_potatocreek_m2530_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-08-12</publication-date>
      <abstract>LiDAR collected for the upper portion of the Flint River in central georgia. 237.6 sqmiles collected between May 1st and May 4th, 2009. The data contains 1 meter spaced pointscontaining classifications of unclassified (1), ground (2), noise (7) and water (9).Nominal spacing of points at 0.58 meters.
Original contact information: 
   Contact Org: AeroMetric, Inc
   Phone: 920-457-3631</abstract>
      <purpose>The purpose of this project was to produce highly detailed and accurate digitalelevation maps of a portion of the Potato Creek watershed in Georgia for use as amanagement tool and to make these data available to natural-resource managers andresearch scientists.</purpose>
      <notes>10371</notes>
      <supplemental-information>Potato Creek is a subset of the Flint River Watershed.A footprint of this data may be viewed in Google Earth at:https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2530/supplemental/ga2009_usgs_potatocreek.KMZA LiDAR Report from the vendor for this data set may be viewed here:https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2530/supplemental/ga2009_usgs_potatocreek_qareport.pdf</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>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>None Planned</maintenance-frequency>
      <distribution-liability>Any conclusions drawn from the analysis of this information are not the responsibilityof Aero-Metric, 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="674313" in-effect="Yes">
         <support-role-type>Data Steward</support-role-type>
         <from-date>2013-08-12</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="674315" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2013-08-12</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="674316" in-effect="Yes">
         <support-role-type>Metadata Contact</support-role-type>
         <from-date>2013-08-12</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="674314" in-effect="Yes">
         <support-role-type>Point of Contact</support-role-type>
         <from-date>2013-08-12</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="1134296">
         <geographic-areas>
            <geographic-area cc-id="1134298">
               <west-bound>-84.453547</west-bound>
               <east-bound>-84.160765</east-bound>
               <north-bound>33.250302</north-bound>
               <south-bound>32.782026</south-bound>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1134297">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2009-05-01</start-date-time>
               <end-date-time>2009-05-04</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=2530The 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 nolonger represent actual surface conditions. Users should not use this data for critical applications without a full awareness of itslimitations.</data-use-constraints>
   </access-information>
   <distribution-information>
      <distribution cc-id="740983">
         <download-url>https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2530</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="740984">
         <download-url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2530/index.html</download-url>
         <file-name>Bulk Download</file-name>
         <description>Simple download of data files.</description>
      </distribution>
   </distribution-information>
   <urls>
      <url cc-id="740988">
         <url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2530/supplemental/ga2009_usgs_potatocreek.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 topography of the Potato Creek LiDAR survey area in Georgia.</description>
      </url>
      <url cc-id="740987">
         <url>https://coast.noaa.gov</url>
         <url-type>Online Resource</url-type>
      </url>
      <url cc-id="740986">
         <url>https://coast.noaa.gov/dataviewer</url>
         <url-type>Online Resource</url-type>
      </url>
   </urls>
   <activity-logs>
      <activity-log cc-id="674336">
         <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="674335">
         <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="718283">
         <activity-date-time>2018-02-08</activity-date-time>
         <description>Partial upload of Positional Accuracy fields only.</description>
      </activity-log>
      <activity-log cc-id="740985">
         <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>none</accuracy>
      <horizontal-positional-accuracy>Based on relative spacing to control points.; Quantitative Value: 1.0 meters, Test that produced the value: Data tested to meet accuracy.</horizontal-positional-accuracy>
      <vertical-positional-accuracy>The accuracy assessment was performed using a standard method to compute the root mean square error (RMSE) based on a comparison of ground control points (GCP) and filtered LiDAR data points.; Quantitative Value: 0.08 meters, Test that produced the value: 8.66 cm calculated vertical accuracy. This value iscomputed by comparing ground control elevation to the classified LiDAR ground surface andrepresents the RMSE of residuals on controls within the project area.</vertical-positional-accuracy>
      <completeness-report>The LAS files were flown at a density sufficient to support a maximum final post spacing of 1 meter for unobscured areas.</completeness-report>
      <conceptual-consistency>The LAS files were flown at a density sufficient to support a maximum final post spacing of 1 meter for unobscured areas.</conceptual-consistency>
   </data-quality>
   <lineage>
      <lineage-sources>
         <lineage-source cc-id="1134293">
            <citation-title>Fulton County LiDAR Survey</citation-title>
            <publish-date>2009-05-26</publish-date>
            <extent-type>Range</extent-type>
            <extent-start-date-time>2009-05-05</extent-start-date-time>
            <extent-end-date-time>2009-05-26</extent-end-date-time>
            <source-contribution>The Potato Creek LiDAR Survey was acquired and processed by Aero-Metric, Inc. | Source Geospatial Form: Remote sensing image | Type of Source Media: digital tape media</source-contribution>
         </lineage-source>
      </lineage-sources>
      <lineage-process-steps>
         <lineage-process-step cc-id="1134294">
            <sequence-number>1</sequence-number>
            <description>1m hydro enforced Arc ASCII Grids were loaded into Global Mapper catalog for review. Upon review itwas found that 15 original grids had excess tinning during processing and data was lost. Those 15 gridswere replaced by Aero-Metric.The replaced grids also had voids and lines across tiles, requiring repair. Repairs were made at NGTOCusing the original .las files to correct the residual line and void problems. Elevations were then checkedthrougout project with DRGs and were found to be accurate. There are no other areas of concern.Grid files were exported to 1m Image files for delivery to the NED. Each final image tile is 8994x x 6518yand is 223.7 mb in size. Shapefile of the extent of Potato Creek has been provided. Final data appears tobe very good.</description>
            <process-date-time>2009-05-26T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1134295">
            <sequence-number>2</sequence-number>
            <description>The NOAA Office for Coastal Management (OCM) received the files in las format with only a qualityassurance report, no metadata accompanied the data. The files contained lidar elevation and intensitymeasurements. The data were in GA State Plane coordinates and NAVD88 (orthometric) heights in feet.OCM performed the following processing for data storage and Digital Coast provisioning purposes:1. The data were converted from GA State Plane coordinates to geographic coordinates.3. The data were converted from NAVD88 (orthometric) heights in feet to GRS80 (ellipsoid) heights in meters using Geoid 03.4. Attempts were made to find the water class (9) though data received had water reclassed tounclassed along with a number of ground points, therefore processing to pull out only water classes were thwarted.</description>
            <process-date-time>2013-08-12T00:00:00</process-date-time>
         </lineage-process-step>
      </lineage-process-steps>
   </lineage>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:49726</guid>
      <metadata-record-created-by pers-id="19064">Anne Ball</metadata-record-created-by>
      <metadata-record-created>2017-11-15T15:21:53</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>
