<?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>49681</catalog-item-id>
      <title>2003 Southwest Florida Water Management District (SWFWMD) LiDAR: Marion County</title>
      <short-name>fl2003_swfwmd_marionco_m2546_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-12-30</publication-date>
      <abstract>Merrick and Company produced one foot contours, spot elevations, and obscured areas for
the Southwest Florida Water Management District.

Original contact information: 
   Contact Name: Diana Burdick
   Contact Org: Southwest Florida Water Management District
   Title: GIS Analyst
   Phone: 352-540-6018
   Email: Diana.Burdick@swfwmd.state.fl.us</abstract>
      <purpose>Developed to support the DISTRICT's regulatory, land management and acquisition,
planning, engineering, and habitat restoration projects</purpose>
      <notes>10325</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/2546/supplemental/fl2003_swfwmd_marioncounty.kmz</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>Surface</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Terrain</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 Merrick, SWFWMD, NOAA, the Office for Coastal Management or its partners.</distribution-liability>
      <data-set-credit>Acknowledgement of the Southwest Florida Water Management District would be appreciated in products derived from these data.</data-set-credit>
   </data-set-information>
   <entity-attribute-information partial-listing="No" total-count="0"/>
   <support-roles>
      <support-role cc-id="672387" in-effect="Yes">
         <support-role-type>Data Steward</support-role-type>
         <from-date>2013-12-30</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="672389" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2013-12-30</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="672390" in-effect="Yes">
         <support-role-type>Metadata Contact</support-role-type>
         <from-date>2013-12-30</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="672388" in-effect="Yes">
         <support-role-type>Point of Contact</support-role-type>
         <from-date>2013-12-30</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>Publication Date</currentness-reference>
      <extent cc-id="1134415">
         <geographic-areas>
            <geographic-area cc-id="1134418">
               <west-bound>-82.545499</west-bound>
               <east-bound>-81.629324</east-bound>
               <north-bound>29.52831</north-bound>
               <south-bound>28.954762</south-bound>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1134416">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2003-03-26</start-date-time>
            </time-frame>
            <time-frame cc-id="1134417">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2003-04-17</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/#/lidar/search/where:ID=2546
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="740715">
         <download-url>https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2546</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="740716">
         <download-url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2546/index.html</download-url>
         <file-name>Bulk Download</file-name>
         <description>Simple download of data files.</description>
      </distribution>
   </distribution-information>
   <urls>
      <url cc-id="740720">
         <url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2546/supplemental/fl2003_swfwmd_marioncounty.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 SWFWMD Topography Survey of Marion County in Florida.</description>
      </url>
      <url cc-id="740719">
         <url>https://coast.noaa.gov</url>
         <url-type>Online Resource</url-type>
      </url>
      <url cc-id="740718">
         <url>https://coast.noaa.gov/dataviewer</url>
         <url-type>Online Resource</url-type>
      </url>
   </urls>
   <activity-logs>
      <activity-log cc-id="672407">
         <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="672406">
         <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="718230">
         <activity-date-time>2018-02-08</activity-date-time>
         <description>Partial upload of Positional Accuracy fields only.</description>
      </activity-log>
      <activity-log cc-id="740717">
         <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>
      <horizontal-positional-accuracy>The coverage features horizontal positional accuracy and the assurance of that
accuracy depend, in part, on the accuracy of the data inputs to the coverage and the tolerances of the coverage itself.
The input is the photogrammetrically compiled vectors in Microstation design files (.dgn). The coverage model is
created from an Arc Macro Language (AML) routine that follows the database design for precision, fuzzy tolerance,
dangle tolerance, weed tolerance, grain tolerance, and projection parameters.
; Quantitative Value: 0.762 meters, Test that produced the value: Horizontal accuracy was tested by comparing the raw contours from each flightline against adjoining flightlines at specific points.</horizontal-positional-accuracy>
      <vertical-positional-accuracy>RMSE for Z = 0.23 feet. The vertical positional accuracy of the data is verified by a control report
that matches known ground control points against LIDAR acquired points. The contours are derived from a digital terrain model that
meets FEMA Accuracy Standards for better than 0.6 feet vertical accuracy.
; Quantitative Value: 0.07 meters, Test that produced the value: 
The vertical positional accuracy of the data is
verified by a control report that matches known ground control points against LIDAR
acquired points. The contours are derived from a digital terrain model that meets
FEMA Accuracy Standards for better than 0.6 feet vertical accuracy.</vertical-positional-accuracy>
      <completeness-report>complete</completeness-report>
      <conceptual-consistency>none</conceptual-consistency>
   </data-quality>
   <lineage>
      <lineage-sources>
         <lineage-source cc-id="1134412">
            <citation-title>Ground Control</citation-title>
            <publish-date>2003-05-28</publish-date>
            <extent-type>Discrete</extent-type>
            <extent-start-date-time>2003-05-28</extent-start-date-time>
            <source-contribution>Survey data for aerotriangulation and data quality control. | Source Geospatial Form: model | Type of Source Media: HDD</source-contribution>
         </lineage-source>
      </lineage-sources>
      <lineage-process-steps>
         <lineage-process-step cc-id="1134413">
            <sequence-number>1</sequence-number>
            <description>LIDAR data was collected using Merrick's ALS40 sensor. The data was field-verified for complete coverage of
the project area. 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. The surface was then normalized into a digital surface model (DSM). Final data extraction
for the client's keypoint (statistically significant points) and canopy-building files were then
generated. Using orthophotography, planimetric features were compiled as breaklines to supplement
the LIDAR data. The LIDAR digital surface model was then processed with the breaklines, and contour
lines were interpolated. The contours were exported from Merrick's MARS software into Microstation.
The contour data was checked for spikes and holes, and then imported into Arc/Info coverages for
building topology, coding contour types, and creating annotation.

Ground control collected 20030724 through 20040424.</description>
            <process-date-time>2004-04-24T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1134414">
            <sequence-number>2</sequence-number>
            <description>The NOAA Office for Coastal Management (OCM) received the files in las format. The files contained lidar elevation and intensity
measurements. The data were in Florida State Plane West 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 FL State Plane West coordinates to geographic coordinates.
2. The data were converted from NAVD88 (orthometric) heights in feet to GRS80 (ellipsoid) heights in meters using Geoid 03.
3. The LAS data were sorted by latitude and the headers were updated.
4. Class 8 was moved to class 2 in accordance to the NOAA DAV classification scheme.</description>
            <process-date-time>2012-08-20T00:00:00</process-date-time>
         </lineage-process-step>
      </lineage-process-steps>
   </lineage>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:49681</guid>
      <metadata-record-created-by pers-id="19064">Anne Ball</metadata-record-created-by>
      <metadata-record-created>2017-11-15T15:21:36</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>
