<?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>49732</catalog-item-id>
      <title>2013 Georgia Department of Natural Resources (GADNR) Topographic Lidar: Barrow, Clarke, Madison and Oglethorpe Counties</title>
      <short-name>ga2013_gadnr_barrowclarkemadisonoglethorpe_m2617_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>2014-02</publication-date>
      <abstract>NOAA Contract:  EA133C11CQ0009
NOAA Task Order Number:  T0013
The PS FY13 GA DNR Elevation Data Task Order involves collecting and delivering topographic elevation point data derived from multiple return light detection and ranging (LiDAR) measurements in 4 counties in Georgia.  The Statement of Work (SOW) was developed by the National Oceanic and Atmospheric Administration's (NOAA) Office for Coastal Management (referred to as the Center) in partnership with the Georgia Department of Natural Resources (GADNR) Environmental Protection Division (EPD).  The counties included are Barrow,Clarke, Madison and Oglethorpe.  The data collected for these 4 counties will exhibit Hydro Flattened DEMs for inclusion into the National Elevation Dataset (NED). The purpose of the data is for use in coastal management decision making, including applications such as floodplain mapping and water rights management.
LiDAR was collected at 1.0 points per square meter (1.0m GSD) for Barrow, Clarke, Madison and Oglethorpe Counties.This area was flown during snow free and leaf-off conditions.</abstract>
      <purpose>Lifts are planned to meet project specifications and are flown under cloud-free conditions in order to collect LIDAR points at an average of 1.0 meter point spacing.This allows the user to create Intensity Images, Break Lines, Hydro Flattened DEMs and fully Classified LiDAR LAS files.</purpose>
      <notes>10377</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/2617/supplemental/ga2013_gadnr_barrow_clarke_madison_oglethorpe_m2617.kmz</supplemental-information>
   </item-identification>
   <keywords>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus>ISO 19115 Topic Category</thesaurus>
         <keyword>elevation</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>las</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 Photo Science, GADNR, NOAA, the Office for Coastal Management or its partners.</distribution-liability>
      <data-set-credit>Photo Science, Inc. acquired and post-processed the LiDAR for Barrow, Clarke, Madison and Oglethorpe Counties.</data-set-credit>
   </data-set-information>
   <entity-attribute-information partial-listing="No" total-count="0"/>
   <support-roles>
      <support-role cc-id="674562" in-effect="Yes">
         <support-role-type>Data Steward</support-role-type>
         <from-date>2014-02</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="674564" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2014-02</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="674565" in-effect="Yes">
         <support-role-type>Metadata Contact</support-role-type>
         <from-date>2014-02</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="674563" in-effect="Yes">
         <support-role-type>Point of Contact</support-role-type>
         <from-date>2014-02</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="1135117">
         <geographic-areas>
            <geographic-area cc-id="1135119">
               <west-bound>-83.880586</west-bound>
               <east-bound>-82.767975</east-bound>
               <north-bound>34.283061</north-bound>
               <south-bound>33.680598</south-bound>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1135118">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2013-01-22</start-date-time>
               <end-date-time>2013-02-15</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=2617;</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="741019">
         <download-url>https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2617</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="741020">
         <download-url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2617/index.html</download-url>
         <file-name>Bulk Download</file-name>
         <description>Simple download of data files.</description>
      </distribution>
   </distribution-information>
   <urls>
      <url cc-id="741024">
         <url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2617/supplemental/ga2013_gadnr_barrow_clarke_madison_oglethorpe_m2617.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 Barrow, Clarke, Madison and Oglethorpe Counties in Georgia.</description>
      </url>
      <url cc-id="741023">
         <url>https://coast.noaa.gov</url>
         <url-type>Online Resource</url-type>
      </url>
      <url cc-id="741022">
         <url>https://coast.noaa.gov/dataviewer</url>
         <url-type>Online Resource</url-type>
      </url>
   </urls>
   <activity-logs>
      <activity-log cc-id="674583">
         <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="674582">
         <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="718289">
         <activity-date-time>2018-02-08</activity-date-time>
         <description>Partial upload of Positional Accuracy fields only.</description>
      </activity-log>
      <activity-log cc-id="741021">
         <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>MicroStation Version 8; TerraScan Version 13; TerraModeler Version 13; GeoCue Version 2012.1.27.5; ESRI ArcGIS 10.1;Global Mapper Version 14.1; ALS Post Processor 2.75 Build #25; DashMap Version 5.2000; Windows 7 Operating System</description>
   </technical-environment>
   <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>The LiDAR data was compiled to meet a 1 meter horizontal accuracy. The calibration of the LiDAR sensor itself and the calibration process of the data produced by this sensor ensure that this accuracy is met.; Quantitative Value: 1.0 meters, Test that produced the value: Value stated in meters</horizontal-positional-accuracy>
      <vertical-positional-accuracy>The classified LiDAR data was tested by Photo Science, Inc. for vertical accuracy.  Photo Science collected a total of 51 ground control points for use in verifying the vertical accuracy of the classified LiDAR data in Barrow, Clarke, Madison and Oglethorpe Counties.  These points were tested against the classified LiDAR data and a vertical adjustment was made to the classified LiDAR for each county in order to obtain a higher level of accuracy. All data are seamless from one tile to the next, no gaps or no data areas.  The vertical unit of the data file is in meters.; Quantitative Value: 0.06 meters, Test that produced the value: RMSE in meters of classified LiDAR</vertical-positional-accuracy>
      <completeness-report>Datasets contain complete coverage of tiles.</completeness-report>
      <conceptual-consistency>Deliverables were tested by Photo Science, Inc. for vertical accuracy.  All data are seamless from one tile to the next, no gaps or no data areas.</conceptual-consistency>
   </data-quality>
   <lineage>
      <lineage-sources>
         <lineage-source cc-id="1135114">
            <citation-title>LiDAR</citation-title>
            <publish-date>2013-01-01</publish-date>
            <extent-type>Range</extent-type>
            <extent-start-date-time>2013-01-22</extent-start-date-time>
            <extent-end-date-time>2013-02-15</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="1135115">
            <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 the 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.  Inland Ponds and Lakes of 2 acres or greater were also collected.
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 falling inside of the collected breaklines were then classified to Class 9 and Class 2 LIDAR data falling within a proximity of three feet will be classified to Class 10 using TerraScan macro functionality.
The breakline files were translated to ESRI Shapefile format using ESRI conversion tools.
Data was then run through additional macros to ensure deliverable classification levels matching LAS ASPRS Classification structure.  GeoCue functionality was 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.
Tiles were run through automated scripting within ArcMap and were combined with the Hydro Flattened Breaklines to create the 4' 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 and Global Mapper to ensure full coverage with no gaps or slivers within the project area.</description>
            <process-date-time>2013-01-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1135116">
            <sequence-number>2</sequence-number>
            <description>The NOAA Office for Coastal Management (OCM) received the topographic lidar files in LAS format from Photo Science. The files contained lidar elevation measurements and additional information. The data for Barrow and Clarke Counties were received in Georgia State Plane West Zone 1002, NAD83 coordinates. The data for Madison and Oglethorpe were received in Georgia State Plane East Zone 1001, NAD83 coordinates. Both sets of data were vertically referenced to NAVD88 using the Geoid09 model. The vertical units of the data were feet. OCM performed the following processing for data storage and Digital Coast provisioning purposes:1. The topographic las files were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid09.2. The topographic las files were converted from a Projected Coordinate System (State Plane) to a Geographic Coordinate System (NAD83).3. The topographic las files' vertical units were converted from feet to meters.4. The topographic las files' horizontal units were converted from feet to decimal degrees.</description>
            <process-date-time>2014-01-01T00:00:00</process-date-time>
         </lineage-process-step>
      </lineage-process-steps>
   </lineage>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:49732</guid>
      <metadata-record-created-by pers-id="19064">Anne Ball</metadata-record-created-by>
      <metadata-record-created>2017-11-15T15:21:56</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>
