<?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>49870</catalog-item-id>
      <title>2007 Northwest Florida Water Manangement District (NWFWMD) Lidar: 5 Counties (Jackson, Calhoun, Washington, Liberty, Holmes)</title>
      <short-name>nwfwmd2007_5counties_m579_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-01</publication-date>
      <abstract>LIDAR-derived binary (.las) files containing points classified as bare-earth and canopy (first return) were produced for the 2007/2008 Northwest
Florida Water Management District - 5 Counties (Calhoun, Washington, Jackson, Liberty, Holmes), Florida lidar mapping project. ESRI GRIDs of
bare earth points are also provided. The files were provided in a scheme of FDEM-derived 5,000 x 5,000 foot (1500 x 1500 meter) tiles. Horizontal
mapping units are in UTM meters, vertical mapping units are in U.S. survey feet. The total mapping area covers approximately 2102 square miles.

Original contact information: 
   Contact Name: Mr John Crowe
   Contact Org: Northwest Florida Water Management District
   Title: Associate Hydrologist, Division of Resource Management
   Phone: 850-539-5999
   Email: ron.bartel@nwfwmd.state.fl.us</abstract>
      <purpose>The purpose of the project is to produce accurate, high-resolution data for planning, analysis, and for use with other datasets. Merrick obtained
LiDAR data over approximately 2,102 square miles covering all or portions of 5-Counties in Florida. The LiDAR data has been processed to result in
a data set that is suitable for the future generation of 2-foot contours.

These data will be used to support FEMA's Map Modernization Program through the creation of high-resolution digital elevation models (DEMs).  These
DEMs support a variety of applications, including improved floodplain delineation, hydrologic and hydraulic modeling, hazard mapping as well as
other planning activities.</purpose>
      <notes>10514</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/579/supplemental/2007_NWFWMD_5_Counties_Lidar.kmz

The Lidar Mapping Report (including sensor information, collection parameters, etc.) for this data set may be viewed at:
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/579/supplemental/NWFWMD_5_Counties_Lidar_Mapping_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>bare earth</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>binary</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>canopy</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</data-presentation-form>
      <entity-attribute-overview>Lidar points are attributed with the following classifications:
1 - Unclassified
2 - Ground (bare earth)
Lidar intensity values range from 0-255. Lidar return values range from 1-3. Flight line numbers range from 1-19.</entity-attribute-overview>
      <entity-attribute-detail-citation>All deliverables meet specifications in contract.  LAS Files meet ASPRS Classification Standards.</entity-attribute-detail-citation>
      <distribution-liability>Any conclusions drawn from the analysis of this information are not the responsibility of NOAA, the Office for Coastal Management
or its partners.</distribution-liability>
      <data-set-credit>Merrick &amp; Company</data-set-credit>
   </data-set-information>
   <entity-attribute-information partial-listing="No" total-count="0"/>
   <support-roles>
      <support-role cc-id="681311" in-effect="Yes">
         <support-role-type>Data Steward</support-role-type>
         <from-date>2008-01</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="681313" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2008-01</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="681314" in-effect="Yes">
         <support-role-type>Metadata Contact</support-role-type>
         <from-date>2008-01</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="681312" in-effect="Yes">
         <support-role-type>Point of Contact</support-role-type>
         <from-date>2008-01</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="1139312">
         <geographic-areas>
            <geographic-area cc-id="1139314">
               <west-bound>-85.894507</west-bound>
               <east-bound>-84.828007</east-bound>
               <north-bound>31.006292</north-bound>
               <south-bound>30.193492</south-bound>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1139313">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2007-11-12</start-date-time>
               <end-date-time>2008-01-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
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.</data-use-constraints>
   </access-information>
   <distribution-information>
      <distribution cc-id="741810">
         <download-url>https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=579</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="741811">
         <download-url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/579/index.html</download-url>
         <file-name>Bulk Download</file-name>
         <description>Simple download of data files.</description>
      </distribution>
   </distribution-information>
   <urls>
      <url cc-id="741814">
         <url>https://coast.noaa.gov</url>
         <url-type>Online Resource</url-type>
      </url>
      <url cc-id="741813">
         <url>https://coast.noaa.gov/dataviewer</url>
         <url-type>Online Resource</url-type>
      </url>
   </urls>
   <activity-logs>
      <activity-log cc-id="681338">
         <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="681337">
         <activity-date-time>2017-11-14</activity-date-time>
         <description>Converted from FGDC Content Standard 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="718450">
         <activity-date-time>2018-02-08</activity-date-time>
         <description>Partial upload of Positional Accuracy fields only.</description>
      </activity-log>
      <activity-log cc-id="741812">
         <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); ArcGIS Desktop 9.1; ArcGIS Workstation 9.1; MARS 4.0</description>
   </technical-environment>
   <data-quality>
      <accuracy>Verification of attribute accuracy of LIDAR data involves the use of filtering techniques.  Auto-filtering uses algorithms to reclassify data in the
point cloud.  Hand-filtering involves the use of a technician working in a graphic environment to reclassify the erroneous points that may remain in
the LIDAR point cloud after auto filter.</accuracy>
      <horizontal-positional-accuracy>Horizontal accuracy is verified in three tests.  During boresighting, adjoining flightlines are view in profile and hard edged features are
observed and if necessary the flightlines are adjusted for good relative horizontal and vertical fit.  The second test for horizontal accuracy is
by comparing raw contours from each flightline against adjoining flightlines at specific points.  The final test is the vertical LIDAR control
report.</horizontal-positional-accuracy>
      <vertical-positional-accuracy>Survey control points were used to validate the accuracy of the LIDAR surface model after automatic and hand filtering. This surface exceeds the
NSSDA consolidated vertical accuracy specifications of 36.3 cm (1.19 ft) at the 95% confidence level.
; Quantitative Value: 0.15 meters, Test that produced the value: 
RMSEz (m) based upon comparison of 176 survey checkpoint z-values with those of a bare-earth generated surface model at same geographic location.</vertical-positional-accuracy>
      <completeness-report>This dataset contains classified returns of the LIDAR sensor.  The sensor data was verified in MARS software to ensure complete coverage.</completeness-report>
      <conceptual-consistency>Calibrations of the LIDAR flightline data are performed; this process is known as boresighting.  The flightlines are compared to evaluate both their

relative and absolute accuracies.</conceptual-consistency>
   </data-quality>
   <lineage>
      <lineage-sources>
         <lineage-source cc-id="1139308">
            <citation-title>Ground Control</citation-title>
            <publish-date>2007-03-17</publish-date>
            <extent-type>Discrete</extent-type>
            <extent-start-date-time>2007-11-12</extent-start-date-time>
            <source-contribution>GPS control network for LIDAR acquisition and processing. | Source Geospatial Form: spreadsheet | Type of Source Media: spreadsheet</source-contribution>
         </lineage-source>
         <lineage-source cc-id="1139309">
            <citation-title>LIDAR</citation-title>
            <publish-date>2007-03-17</publish-date>
            <extent-type>Range</extent-type>
            <extent-start-date-time>2007-11-12</extent-start-date-time>
            <extent-end-date-time>2008-01-20</extent-end-date-time>
            <source-contribution>LIDAR points form the basis of the DTM surface. | Source Geospatial Form: point digital data | Type of Source Media: digital data</source-contribution>
         </lineage-source>
      </lineage-sources>
      <lineage-process-steps>
         <lineage-process-step cc-id="1139310">
            <sequence-number>1</sequence-number>
            <description>LIDAR data was collected using Merrick's ALS50 Phase 2 sensor.  The raw data was verified in MARS software for complete coverage of the project
area, and boresighted to align the flightlines.  Raw data files were parsed into manageable client-specific tiles.  These tiles were then
processed through automated filtering that separates the data into different classification groups: error points, ground points,
and canopy/building points.  The data was next taken into a graphic environment to reclassify the erroneous points that may remain in the LIDAR
point cloud after auto filter.</description>
            <process-date-time>2007-06-11T00:00:00</process-date-time>
            <source-citation cc-id="1139309">LIDAR</source-citation>
         </lineage-process-step>
         <lineage-process-step cc-id="1139311">
            <sequence-number>2</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 for data storage purposes and Digital Coast provisioning:
1. The data were converted from projected UTM (NAD83, Zone 16) coordinates to geographic (NAD83) 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>2011-04-29T00:00:00</process-date-time>
            <source-citation cc-id="1139309">LIDAR</source-citation>
         </lineage-process-step>
      </lineage-process-steps>
   </lineage>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:49870</guid>
      <metadata-record-created-by pers-id="19064">Anne Ball</metadata-record-created-by>
      <metadata-record-created>2017-11-15T15:22:52</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:38</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>
