<?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>49674</catalog-item-id>
      <title>2007 Florida Division of Emergency Management (FDEM) Lidar Project: Coastal Jefferson County</title>
      <short-name>fdem2007_jefferson_m555_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>2008-05-05</publication-date>
      <abstract>This Light Detection and Ranging (LiDAR) LAS dataset is a topographic survey conducted for a coalition of GIS practitioners,
including the Florida Division of Emergency Management (FDEM), Florida Water Management Districts, Florida Fish and Wildlife
Conservation Commission, Florida Department of Environmental Protection, Army Corps of Engineers Jacksonville District, and
other state and federal agencies. The goal for this project is to use the LiDAR data as new elevation inputs for updated SLOSH
data grids. The ultimate result is the update of the Regional Hurricane Evacuation Studies (RHES) for the state. The State of Florida
Division of Emergency Management LiDAR Survey was collected under the guidance of a Professional Mapper/Surveyor.

Data were collected for 185 square miles in the coastal (southern) part of Jefferson County, Florida from July 18 - 20, 2007. This is a
classified lidar data set. The data are classified: 1 = Unclassified, 2 = Ground (Bare Earth), 7 = Noise and 9 = Water. The FDEM Baseline
Specifications required a maximum post spacing of 4 feet, however, the PDS (Program and Data Solutions) team required a much higher point
density of its subcontractors in order to increase the probability of penetrating dense foliage during the mandated summer acquisition;
with nominal post spacing of 0.7 meters per flight line and 50% sidelap between flight lines, the average point density is 4 points per
square meter.

Original contact information: 
   Contact Org: Florida DEM
   Phone: 850-413-9907
   Email: gis@dca.state.fl.us</abstract>
      <purpose>The LiDAR topographic mapping survey is to support the Florida Division of Emergency Management (FDEM) development and maintenance
of Regional Hurricane Evacuations Studies (RHES), which include vulnerability assessments, and to assist disaster response
personnel in understanding the threats to Florida's citizens and visitors. Additional intended uses for this survey are growth
management, map modernization/floodplain mapping, natural lands stewardship, and homeland security planning.</purpose>
      <notes>10318</notes>
      <supplemental-information>A complete description of this dataset is available in the Minimum Technical Standard (MTS report) "Final Report of Specific Purpose
LiDAR Survey - LiDAR-Generated Breaklines and Contours" submitted to Florida Division of Emergency Management.
This report may be accessed at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/555/supplemental/Jefferson_County_FL_LiDAR_Survey_Report.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/555/supplemental/FDEM_Lidar_Jefferson_County_South.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>
      <distribution-liability>Any conclusions drawn from the analysis of this information are not the responsibility of FDEM, the Office for Coastal Management
or its partners.</distribution-liability>
   </data-set-information>
   <entity-attribute-information partial-listing="No" total-count="1">
      <entity>
         <item-identification>
            <catalog-item-id>50217</catalog-item-id>
            <title>LAS</title>
            <short-name>LAS</short-name>
            <metadata-workflow-state ccs-id="9">Published / External</metadata-workflow-state>
            <status>Completed</status>
            <abstract>Lidar point cloud LAS 1.1 format | Description Source: "Florida GIS - Baseline Specifications for Orthophotography and LiDAR v1.2"</abstract>
            <notes>Converted from FGDC using 'fgdc_to_inport_xml_entity.pl' script.</notes>
         </item-identification>
      </entity>
   </entity-attribute-information>
   <support-roles>
      <support-role cc-id="672163" in-effect="Yes">
         <support-role-type>Data Steward</support-role-type>
         <from-date>2008-05-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="672165" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2008-05-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="672166" in-effect="Yes">
         <support-role-type>Metadata Contact</support-role-type>
         <from-date>2008-05-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="672164" in-effect="Yes">
         <support-role-type>Point of Contact</support-role-type>
         <from-date>2008-05-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="1138936">
         <geographic-areas>
            <geographic-area cc-id="1138938">
               <west-bound>-84.084223</west-bound>
               <east-bound>-83.829313</east-bound>
               <north-bound>30.374197</north-bound>
               <south-bound>30.081871</south-bound>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1138937">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2007-07-18</start-date-time>
               <end-date-time>2007-07-20</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;</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.</data-use-constraints>
   </access-information>
   <distribution-information>
      <distribution cc-id="740680">
         <download-url>https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=555</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="740681">
         <download-url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/555/index.html</download-url>
         <file-name>Bulk Download</file-name>
         <description>Simple download of data files.</description>
      </distribution>
   </distribution-information>
   <urls>
      <url cc-id="740684">
         <url>https://coast.noaa.gov</url>
         <url-type>Online Resource</url-type>
      </url>
      <url cc-id="740683">
         <url>https://coast.noaa.gov/dataviewer</url>
         <url-type>Online Resource</url-type>
      </url>
   </urls>
   <activity-logs>
      <activity-log cc-id="672179">
         <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="672178">
         <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="718222">
         <activity-date-time>2018-02-08</activity-date-time>
         <description>Partial upload of Positional Accuracy fields only.</description>
      </activity-log>
      <activity-log cc-id="740682">
         <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>Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.2.5.1450</description>
   </technical-environment>
   <data-quality>
      <horizontal-positional-accuracy>Lidar source compiled to meet 1 m horizontal accuracy.; Quantitative Value: 1 meters, Test that produced the value: 
The PDS team does not perform independent horizontal accuracy testing on the LiDAR. LiDAR vendors perform calibrations on the LiDAR
sensor and compare data to adjoining flight lines to ensure LiDAR meets the 1 meter horizontal accuracy standard at the 95% confidence
level.</horizontal-positional-accuracy>
      <vertical-positional-accuracy>The LiDAR is required to meet 0.60 feet (0.18 m) Fundamental Vertical Accuracy (FVA) and 1.19 feet (0.36 m) Consolidated Vertical Accuracy (CVA).; Quantitative Value: 0.15 meters, Test that produced the value: 
Based on the vertical accuracy testing conducted by PDS, using NSSDA and FEMA methodology, vertical accuracy at the 95% confidence
level (called Accuracyz) is computed by the formula RMSEz x 1.9600. The dataset for Jefferson County, Florida satisfies the criteria:
Countywide lidar dataset tested 0.48 ft (0.15 m) FVA at 95% confidence level in open terrain, based on open terrain RMSEz (0.24 ft) x 1.9600.
Countywide lidar dataset tested 0.51 ft (0.16 m) CVA at 95% confidence level in all land cover categories combined, based on consolidated
RMSEz (0.26 ft) x 1.9600.</vertical-positional-accuracy>
      <completeness-report>A visual qualitative assessment was performed in the source Lidar dataset. Small intensity anomalies corresponding to false depressions
in the ground data were found in 0.43 sq. miles of the data. While these intensity anomalies and false depressions impacted a
small geographic extent of the data, do not render the data unusable and are within the acceptable percentage of vertical errors allowed by
the project specifications, these anomalies could still visually be seen in the data. To effectively remove the false depressions from
the bare-earth data, ground points representing the false depression were reclassified from class 2 to class 7 and good ground points were
reclassified from class 1 to class 2 when present in overlap data.</completeness-report>
      <conceptual-consistency>Data covers the tile scheme provided for the county.</conceptual-consistency>
   </data-quality>
   <lineage>
      <lineage-sources>
         <lineage-source cc-id="1138931">
            <citation-title>Lidar</citation-title>
            <publish-date>2008-05-01</publish-date>
            <extent-type>Range</extent-type>
            <extent-start-date-time>2007-07-18</extent-start-date-time>
            <extent-end-date-time>2007-07-20</extent-end-date-time>
            <source-contribution>LiDAR dataset was used to create intensity stereopairs for 3D breakline compilation and for contour generation. | Source Geospatial Form: vector digital data | Type of Source Media: online</source-contribution>
         </lineage-source>
      </lineage-sources>
      <lineage-process-steps>
         <lineage-process-step cc-id="1138932">
            <sequence-number>1</sequence-number>
            <description>The ABGPS, IMU, and raw Optech ALTM 2050 LiDAR data are integrated into the REALM Survey Suite OPTECH post processor software.
The resultant file is in a LAS binary file format. The LAS file version 1.1 formats can be easily transferred from one file format
to another. It is a binary file format that maintains information specific to the LiDAR data (return#, intensity value, xyz, etc.).
The resultant points are produced in the geodetic coordinates referenced to the NAD83 horizontal datum and GRS80 vertical datum.
The date and time for each flight line can be determined using the Julian date and time. The Julian date is a continuous count of
days and fractions since noon Universal Time on January 1, 4713 BCE on the Julian calendar.</description>
            <process-date-time>2008-01-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1138933">
            <sequence-number>2</sequence-number>
            <description>The unedited data are classified to facilitate the application of the appropriate feature extraction filters. A combination of
proprietary filters are applied as appropriate for the production of bare earth digital terrain models (dtms). Interactive editing
methods are applied to those areas where it is inappropriate or impossible to use the feature extraction filters, based upon the
design criteria and/or limitations of the relevant filters. These same feature extraction filters are used to produce elevation
height surfaces. The LiDAR mass points were delivered in American Society for Photogrammetry and Remote Sensing LAS 1.1 format.
The header file for each dataset is complete as define by the LAS 1.1 specification. In addition the following fields are
included:  Flight Date Julian, Year, and Class. The LAS files do not include overlap.
The data was classified as follows:
Class 1 = Unclassified. This class includes vegetation, buildings, noise etc.
Class 2 = Ground
Class 7 = Noise
Class 9 = Water</description>
            <process-date-time>2008-01-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1138934">
            <sequence-number>3</sequence-number>
            <description>Conversion from Geodetic coordinates, NAD83 into State Plane coordinates (U.S. Survey Feet) NAD83 HARN and conversion from ellipsoid
heights (meters) into orthometric heights (U.S. Survey Feet).</description>
            <process-date-time>2008-01-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1138935">
            <sequence-number>4</sequence-number>
            <description>The NOAA Office for Coastal Management (OCM) received files in LAS format. The files contained LiDAR intensity and elevation measurements.
OCM performed the following processing on the data to make it available within Digital Coast:
1. The data were converted from State Plane Florida North coordinates to geographic coordinates.
2. The data were converted from NAVD88 heights to ellipsoid heights using Geoid03.
3. The LAS header fields were sorted by latitude and updated.</description>
            <process-date-time>2010-10-01T00:00:00</process-date-time>
         </lineage-process-step>
      </lineage-process-steps>
   </lineage>
   <child-items>
      <child-item>
         <catalog-item-id>50217</catalog-item-id>
         <catalog-item-type>Entity</catalog-item-type>
         <title>LAS</title>
      </child-item>
   </child-items>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:49674</guid>
      <metadata-record-created-by pers-id="19064">Anne Ball</metadata-record-created-by>
      <metadata-record-created>2017-11-15T15:21:33</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>
