<?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>49728</catalog-item-id>
      <title>2010 ARC Dekalb County Georgia Lidar</title>
      <short-name>ga2010_arc_dekalbcounty_m2527_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>2012-08-13</publication-date>
      <abstract>This metadata record describes the DTM comprised of classified aerial lidar elevation points, photogrammetrically compiled breaklines and the derived TIN for Dekalb County, GA
Original contact information: 
   Contact Name: Stacy Grear
   Contact Org: Dekalb County GIS Department
   Title: Acting Director
   Phone: 404-371-3619
   Email: scgrear@dekalbcountyga.gov will change to scgrear@dekalbcountyga.gov on July 1, 2010</abstract>
      <purpose>The lidar DEM data was collected for the Dekalb County, GA area.  All lidar returns were classified using the default classes of Terrascan processing software for Unclassified Points (class 1), Ground points (class 2), Water points (class 9), Overlap points (class 12).  The lidar ground points are supplemented with photogrammmetrically compiled breaklines from digital imagery collected during the same project time frame as the lidar.  The ground class points, often refered to as "bald earth" are then used as an input to proprietary and publicly available processing software to generate a Triangulated Irregular Network (TIN) model.  Classified lidar DEMs and derived TIN models are useful for a variety of applications, such as aiding in contour generation, development of digital surface models, 3D modeling, flood plane mapping, viewshed analysis and the production of orthophotos.</purpose>
      <notes>10373</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/2527/supplemental/ga2010_dekalbcounty.KMZ
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/2527/supplemental/ga2010_dekalbcounty_QC_Report.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>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Triangulated Irregular Network</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>mapping</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>Unknown</maintenance-frequency>
      <data-presentation-form>Point and vector digital data</data-presentation-form>
      <entity-attribute-overview>LiDAR points in LAS 1.2 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 Kucera International, ARC, USGS, NOAA, the Office for Coastal Management or its partners.</distribution-liability>
      <data-set-credit>Please credit the Deklab County GIS Department Puget with support from the Atlanta Regional Commission with this data.</data-set-credit>
   </data-set-information>
   <entity-attribute-information partial-listing="No" total-count="0"/>
   <support-roles>
      <support-role cc-id="674411" in-effect="Yes">
         <support-role-type>Data Steward</support-role-type>
         <from-date>2012-08-13</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="674413" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2012-08-13</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="674414" in-effect="Yes">
         <support-role-type>Metadata Contact</support-role-type>
         <from-date>2012-08-13</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="674412" in-effect="Yes">
         <support-role-type>Point of Contact</support-role-type>
         <from-date>2012-08-13</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="1134279">
         <geographic-areas>
            <geographic-area cc-id="1134282">
               <west-bound>-84.35091417</west-bound>
               <east-bound>-84.02334971</east-bound>
               <north-bound>33.97061816</north-bound>
               <south-bound>33.61447836</south-bound>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1134280">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2010-01-02</start-date-time>
            </time-frame>
            <time-frame cc-id="1134281">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2010-01-03</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
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>
   </access-information>
   <distribution-information>
      <distribution cc-id="740995">
         <download-url>https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2527</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="740996">
         <download-url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2527/index.html</download-url>
         <file-name>Bulk Download</file-name>
         <description>Simple download of data files.</description>
      </distribution>
   </distribution-information>
   <urls>
      <url cc-id="741000">
         <url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2527/supplemental/ga2010_dekalbcounty.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 Dekalb County Lidar Survey in Georgia.</description>
      </url>
      <url cc-id="740999">
         <url>https://coast.noaa.gov</url>
         <url-type>Online Resource</url-type>
      </url>
      <url cc-id="740998">
         <url>https://coast.noaa.gov/dataviewer</url>
         <url-type>Online Resource</url-type>
      </url>
   </urls>
   <activity-logs>
      <activity-log cc-id="674431">
         <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="674430">
         <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="718285">
         <activity-date-time>2018-02-08</activity-date-time>
         <description>Partial upload of Positional Accuracy fields only.</description>
      </activity-log>
      <activity-log cc-id="740997">
         <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>Attribute accuracy is tested in the LiDAR processing stage.  After classification of the LiDAR data, the 'bald earth' point class is compared to ground control collected within the project area.</accuracy>
      <horizontal-positional-accuracy>Horizontal positional accuracy for LiDAR is dependent upon the quality of the GPS/INS solution, sensor calibration and ground conditions at the time of data capture.  The standard system results for horizontal accuracy are less than 1 meter.; Quantitative Value: 1 meters, Test that produced the value: This value is computed by comparing ground control to an intensity based image derived from the classified LiDAR data and represents the RMSE of residuals on controls within the project area.</horizontal-positional-accuracy>
      <vertical-positional-accuracy>Vertical positional accuracy for LiDAR is dependent upon the quality of the GPS/INS solution, sensor calibration and ground conditions at the time of data capture.  The vertical accuracy for this project was tested with a resultant RMSE of 0.057 meter (0.188 feet).; Quantitative Value: 0.057 meters, Test that produced the value: This value is computed by comparing ground control elevation to the classified LiDAR ground surface and represents the RMSE of residuals on controls within the project area.  Units = meters.</vertical-positional-accuracy>
      <completeness-report>LiDAR data is collected for the project area.  Post processing of the simultaneously acquired GPS/INS is performed and applied to the laser returns to output a point cloud in the specified project coordinate system and datums.  The point cloud data is then subjected to automated classification routines to assign all points in the point cloud to ground, water, overlap and unclassified point classes.  Anomalous laser returns that occur infrequently are removed entirely from the data set.  The ground class points are then compared to surveyed ground control to develop an accuracy measure of the laser terrain data.</completeness-report>
      <conceptual-consistency>LiDAR data is collected within the project area, processed and verified against control.</conceptual-consistency>
   </data-quality>
   <lineage>
      <lineage-sources>
         <lineage-source cc-id="1134264">
            <citation-title>Aerial Digital Imagery</citation-title>
            <extent-type>Discrete</extent-type>
            <extent-start-date-time>2010-02-18</extent-start-date-time>
            <source-contribution>New digital aerial imagery and GPS/IMU data was recorded for the defined project area. | Source Geospatial Form: Remote sensing image | Type of Source Media: disc</source-contribution>
         </lineage-source>
         <lineage-source cc-id="1134265">
            <citation-title>Ground control</citation-title>
            <publish-date>2010-01-01</publish-date>
            <extent-type>Discrete</extent-type>
            <extent-start-date-time>2010</extent-start-date-time>
            <source-contribution>Targeted ground control is used to create a digital control file and control report as well as QC check of LiDAR accuracy.  Predefined points (NGS when available) within the project area are targeted. | Source Geospatial Form: tabular digital data | Type of Source Media: disc</source-contribution>
         </lineage-source>
         <lineage-source cc-id="1134266">
            <citation-title>LiDAR Data</citation-title>
            <extent-type>Discrete</extent-type>
            <extent-start-date-time>2010-01-02</extent-start-date-time>
            <source-contribution>Aerial LiDAR and GPS/IMU data was recorded for the defined project area. | Source Geospatial Form: Remote sensing image | Type of Source Media: disc</source-contribution>
         </lineage-source>
         <lineage-source cc-id="1134267">
            <citation-title>Triangulated Irregular Network</citation-title>
            <publish-date>2010-01-01</publish-date>
            <extent-type>Discrete</extent-type>
            <extent-start-date-time>2010</extent-start-date-time>
            <source-contribution>Using the lidar elevation points and compiled breaklines as inputs, a Triangulated Irregular Network (TIN) is generated using ESRI ArcGIS software. | Source Geospatial Form: Vector digital data | Type of Source Media: disc</source-contribution>
         </lineage-source>
      </lineage-sources>
      <lineage-process-steps>
         <lineage-process-step cc-id="1134268">
            <sequence-number>1</sequence-number>
            <description>At selected locations throughout the site, accurate GPS coordinates and elevations are surveyed and the points are marked with targets.</description>
            <process-date-time>2010-01-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1134269">
            <sequence-number>10</sequence-number>
            <description>The Traingulated Irregular Network is generate with ESRI ArcGIS software.</description>
            <process-date-time>2010-01-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1134270">
            <sequence-number>11</sequence-number>
            <description>The NOAA Office for Coastal Management (OCM) received topographic files in LAS format. The files contained lidar
elevation and intensity measurements. The data were received in projected Georgia State Plane West Zone 1002 coordinates
and were vertically referenced to NAVD88. The vertical units of the data were feet. OCM performed the following processing
for data storage and Digital Coast provisioning purposes:
1. The LAS files were processed through a lastools program known as LASGround, where an algorithm further processes any unclassified points to the ground class, ignoring pre-exisint ground points.
2. All files were then horizontally shifted from the projected GA_W (1002) state place coordinates (in feet) to geographic NAD83 coordinates (decimal degrees)
3. All files were then vertically shifted from from orthometric NAVD88 heights (feet) to ellipsoidal NAD83 (meters) using GEOID09 (assumed based on processing date)</description>
            <process-date-time>2013-08-09T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1134271">
            <sequence-number>2</sequence-number>
            <description>New LiDAR data is captured for the project area using a Leica ALS60 LiDAR instrument in conjunction with a POSAV Applanix GPS/INS system mounted within a Piper Navajo twin engine airplane.</description>
            <process-date-time>2010-01-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1134272">
            <sequence-number>3</sequence-number>
            <description>New aerial digital imagery with airborne GPS/IMU data is acquired for the project area.</description>
            <process-date-time>2010-01-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1134273">
            <sequence-number>4</sequence-number>
            <description>The airborne GPS data is processed in Terratec TerraPos software and then combined with the IMU data in Applanix PosPAC software to determine the LiDAR sensor's angle and orientation in the terrain (project) coordinate system and datums during the survey.  The same GPS/IMU processing is performed for the digital imagery to define the orientation parameters of the images to be used in stereo compilation of terrain breaklines.</description>
            <process-date-time>2010-01-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1134274">
            <sequence-number>5</sequence-number>
            <description>LiDAR data is processed using the GPS/INS solution.  Data is classified to produce:
Class 1:  unclassified points
Class 2:  ground points
Class 9:  water points
Class 12:  overlap points</description>
            <process-date-time>2010-01-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1134275">
            <sequence-number>6</sequence-number>
            <description>The ground class of the processed lidar data is then compared to the ground control and elevation differences between the lidar surface and surveyed elevation are recorded in tabular form.  Vertical accuracy statistices are then developed to produce vertical RMSE and overall accuracy estimates and reports.</description>
            <process-date-time>2010-01-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1134276">
            <sequence-number>7</sequence-number>
            <description>Photogrammetrically compiled breaklines are compiled to supplement the lidar ground points.</description>
            <process-date-time>2010-01-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1134277">
            <sequence-number>8</sequence-number>
            <description>Water polygons are buffered to remove any lidar points within the polygon to flatten these surfaces.</description>
            <process-date-time>2010-01-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1134278">
            <sequence-number>9</sequence-number>
            <description>Breaklines are buffered to remove lidar surface points on or near the breakline.</description>
            <process-date-time>2010-01-01T00:00:00</process-date-time>
         </lineage-process-step>
      </lineage-process-steps>
   </lineage>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:49728</guid>
      <metadata-record-created-by pers-id="19064">Anne Ball</metadata-record-created-by>
      <metadata-record-created>2017-11-15T15:21:54</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>
