2003 Southwest Florida Water Management District (SWFWMD) LiDAR: Marion County

OCM Partners
Data Set (DS) | ID: 49681 | Published / External
Created: 2017-11-15   |   Last Modified: 2022-08-09

Parent: Lidar - partner (no harvest)
Project (PRJ) | ID: 49401

ID: 49681
Data Set (DS)

* Discovery
• First Pass
» Metadata Rubric

Item Identification

* » Title 2003 Southwest Florida Water Management District (SWFWMD) LiDAR: Marion County
Short Name fl2003_swfwmd_marionco_m2546_metadata
* Status Completed
Creation Date  
Revision Date  
• Publication Date 2013-12-30
* » 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
* Purpose

Developed to support the DISTRICT's regulatory, land management and acquisition,

planning, engineering, and habitat restoration projects
Notes

10325
Other Citation Details
• 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
DOI (Digital Object Identifier)  
DOI Registration Authority  
DOI Issue Date  

Keywords

Theme Keywords

Thesaurus Keyword
ISO 19115 Topic Category elevation
None Surface
None Terrain
   
   
   

Temporal Keywords

Thesaurus Keyword
   
   
   

* Spatial Keywords

Thesaurus Keyword
   
   
   

Stratum Keywords

Thesaurus Keyword
   
   
   

Instrument Keywords

Thesaurus Keyword
   
   
   

Platform Keywords

Thesaurus Keyword
   
   
   

Physical Location

• » Organization Office for Coastal Management
• » City Charleston
• » State/Province SC
• Country  
• » Location Description

Data Set Information

* Data Set Scope Code Data Set
• Data Set Type  
• Maintenance Frequency As Needed
Maintenance Note
» Data Presentation Form  
• Entity Attribute Overview
Entity Attribute Detail Citation
Entity Attribute Detail URL  
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.
Data Set Credit Acknowledgement of the Southwest Florida Water Management District would be appreciated in products derived from these data.

Support Roles

» At least one Distributor Org, one Metadata Contact, one Point of Contact, and one Data Steward should be listed.
* » Support Role Data Steward
* » Date Effective From 2013-12-30
Date Effective To
Organization NOAA Office for Coastal Management (NOAA/OCM)
Address 2234 South Hobson Ave
Charleston, SC 29405-2413
Email Address coastal.info@noaa.gov
Phone (843) 740-1202
Fax  
Mobile  
URL https://coast.noaa.gov
Business Hours  
Contact Instructions
* » Support Role Distributor
* » Date Effective From 2013-12-30
Date Effective To
Organization NOAA Office for Coastal Management (NOAA/OCM)
Address 2234 South Hobson Ave
Charleston, SC 29405-2413
Email Address coastal.info@noaa.gov
Phone (843) 740-1202
Fax  
Mobile  
URL https://coast.noaa.gov
Business Hours  
Contact Instructions
* » Support Role Metadata Contact
* » Date Effective From 2013-12-30
Date Effective To
Organization NOAA Office for Coastal Management (NOAA/OCM)
Address 2234 South Hobson Ave
Charleston, SC 29405-2413
Email Address coastal.info@noaa.gov
Phone (843) 740-1202
Fax  
Mobile  
URL https://coast.noaa.gov
Business Hours  
Contact Instructions
* » Support Role Point of Contact
* » Date Effective From 2013-12-30
Date Effective To
Organization NOAA Office for Coastal Management (NOAA/OCM)
Address 2234 South Hobson Ave
Charleston, SC 29405-2413
Email Address coastal.info@noaa.gov
Phone (843) 740-1202
Fax  
Mobile  
URL https://coast.noaa.gov
Business Hours  
Contact Instructions
* » Support Role
* » Date Effective From
Date Effective To
* » Contact
* Contact Instructions
* » Support Role
* » Date Effective From
Date Effective To
* » Contact
* Contact Instructions
* » Support Role
* » Date Effective From
Date Effective To
* » Contact
* Contact Instructions

Extents

Currentness Reference Publication Date

Extent Group 1

Extent Description

Extent Group 1 / Geographic Area 1

* » W° Bound -82.545499
* » E° Bound -81.629324
* » N° Bound 29.52831
* » S° Bound 28.954762
* » Description

Extent Group 1 / Vertical Extent

EPSG Code
Vertical Minimum
Vertical Maximum

Extent Group 1 / Time Frame 1

* » Time Frame Type Discrete
* » Start 2003-03-26
End  
Alternate Start As Of Info  
Alternate End As Of Info  
Description

Extent Group 1 / Time Frame 2

* » Time Frame Type Discrete
* » Start 2003-04-17
End  
Alternate Start As Of Info  
Alternate End As Of Info  
Description

Spatial Information

Spatial Resolution

Angular Distance  
Angular Distance Units  
Horizontal Distance  
Horizontal Distance Units  
Vertical Distance  
Vertical Distance Units  
Equivalent Scale Denominator  
Level of Detail Description

Spatial Representation

Grid Representation Used?  
Vector Representation Used? Yes
Text / Table Representation Used?  
TIN Representation Used?  
Stereo Model Representation Used?  
Video Representation Used?  

Grid Representation

Dimension Count
Cell Geometry
Transformation Parameter Available?  

Axis Dimension
Dimension Type
Size
Resolution
Resolution Units
Resolution Type
Description

Axis Dimension
Dimension Type
Size
Resolution
Resolution Units
Resolution Type
Description

Vector Representation

Topology Level
Complex Object Present?  
Complex Object Count
Composite Object Present?  
Composite Object Count
Curve Object Present?  
Curve Object Count
Point Object Present?  
Point Object Count
Solid Object Present?  
Solid Object Count
Surface Object Present?  
Surface Object Count

Reference Systems

Reference System

EPSG Code

Horizontal Resolution
Horizontal Encoding Method
Latitude Resolution
Longitude Resolution
Coordinate X Resolution
Coordinate Y Resolution
Row Resolution
Column Resolution
Horizontal Units
Distance Resolution
Distance Units
Bearing Resolution
Bearing Units
Reference Direction
Reference Meridian

Vertical Resolution
Vertical Encoding Method
Vertical Resolution
Vertical Units

Access Information

* » Security Class Unclassified
* Security Classification System
Security Handling Description
• Data Access Policy
» 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 Constraints

None
• 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.
Metadata Access Constraints
Metadata Use Constraints

Distribution Information

Start Date  
» Download URL https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2546
Distributor
File Name Customized Download
Description

Create custom data files by choosing data area, product type, map projection, file format, datum, etc.
File Date/Time  
File Type  
File Size  
Application Version  
Compression  
Review Status  
Start Date  
» Download URL https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2546/index.html
Distributor
File Name Bulk Download
Description

Simple download of data files.
File Date/Time  
File Type  
File Size  
Application Version  
Compression  
Review Status  
Start Date
End Date
» Download URL
Distributor
File Name
Description
File Date/Time
File Type
FGDC Content Type
File Size
Application Version
Compression
Review Status
Start Date
End Date
» Download URL
Distributor
File Name
Description
File Date/Time
File Type
FGDC Content Type
File Size
Application Version
Compression
Review Status
Start Date
End Date
» Download URL
Distributor
File Name
Description
File Date/Time
File Type
FGDC Content Type
File Size
Application Version
Compression
Review Status

URLs

URL https://coast.noaa.gov/dataviewer
Name  
URL Type Online Resource
File Resource Format  
Description
URL https://coast.noaa.gov
Name  
URL Type Online Resource
File Resource Format  
Description
URL https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2546/supplemental/fl2003_swfwmd_marioncounty.kmz
Name Browse Graphic
URL Type Browse Graphic
File Resource Format kmz
Description

This graphic shows the lidar coverage for the SWFWMD Topography Survey of Marion County in Florida.
URL
Name
URL Type
File Resource Format
Description
URL
Name
URL Type
File Resource Format
Description
URL
Name
URL Type
File Resource Format
Description

Activity Log

Activity Time 2016-05-23
Activity Type  
Responsible Party  
Description

Date that the source FGDC record was last modified.
Activity Time 2017-11-14
Activity Type  
Responsible Party  
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.
Activity Time 2018-02-08
Activity Type  
Responsible Party  
Description

Partial upload of Positional Accuracy fields only.
Activity Time 2018-03-13
Activity Type  
Responsible Party  
Description

Partial upload to move data access links to Distribution Info.
Activity Time
Activity Type
Responsible Party
Description
Activity Time
Activity Type
Responsible Party
Description
Activity Time
Activity Type
Responsible Party
Description

Issues

Issue Date
Author
Issue
Issue Date
Author
Issue
Issue Date
Author
Issue

Technical Environment

Description  
 

Data Quality

Representativeness
Accuracy
Analytical Accuracy
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.
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.
Quantitation Limits
Bias
Comparability
Completeness Measure
Precision
Analytical Precision
Field Precision
Sensitivity
Detection Limit
Completeness Report

complete
Conceptual Consistency

none
» Quality Control Procedures Employed

Data Management

» Have Resources for Management of these Data Been Identified?  
» Approximate Percentage of Budget for these Data Devoted to Data Management  
» Do these Data Comply with the Data Access Directive?  
» Is Access to the Data Limited Based on an Approved Waiver?  
» If Distributor (Data Hosting Service) is Needed, Please Indicate  
» Approximate Delay Between Data Collection and Dissemination  
» If Delay is Longer than Latency of Automated Processing, Indicate Under What Authority Data Access is Delayed  
 
» Actual or Planned Long-Term Data Archive Location  
» If World Data Center or Other, Specify  
» If To Be Determined, Unable to Archive, or No Archiving Intended, Explain  
 
» Approximate Delay Between Data Collection and Archiving  
» How Will the Data Be Protected from Accidental or Malicious Modification or Deletion Prior to Receipt by the Archive?  
 

Lineage

» Lineage Statement

Sources

Citation Title Ground Control
Contact Role Type  
Contact Type  
Contact Name  
Publish Date 2003-05-28
Extent Type Discrete
Extent Start Date/Time 2003-05-28
Extent End Date/Time  
Scale Denominator  
Citation URL  
Citation URL Name  
Citation URL Description
Source Contribution

Survey data for aerotriangulation and data quality control. | Source Geospatial Form: model | Type of Source Media: HDD
Citation Title
Contact Role Type
Contact Type
Contact Name
Publish Date
Extent Type
Extent Start Date/Time
Extent End Date/Time
Citation URL
Citation URL Name
Citation URL Description
Scale Denominator
Citation Title
Contact Role Type
Contact Type
Contact Name
Publish Date
Extent Type
Extent Start Date/Time
Extent End Date/Time
Citation URL
Citation URL Name
Citation URL Description
Scale Denominator
Citation Title
Contact Role Type
Contact Type
Contact Name
Publish Date
Extent Type
Extent Start Date/Time
Extent End Date/Time
Citation URL
Citation URL Name
Citation URL Description
Scale Denominator

Process Steps

Process Step Number 1
» 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.
Process Date/Time 2004-04-24 00:00:00
Process Contact  
Phone (Voice)  
Email Address  
Source  
Process Step Number 2
» 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.
Process Date/Time 2012-08-20 00:00:00
Process Contact  
Phone (Voice)  
Email Address  
Source  
Process Step Number
» Description
Process Date/Time
Process Contact
Phone (Voice)
Email Address
Source
Process Step Number
» Description
Process Date/Time
Process Contact
Phone (Voice)
Email Address
Source
Process Step Number
» Description
Process Date/Time
Process Contact
Phone (Voice)
Email Address
Source

Acquisition Information

Instruments

Instrument Unavailable Reason  
Identifier
Docucomp UUID
Instrument / Gear
Instrument Type
Description
Identifier
Docucomp UUID
Instrument / Gear
Instrument Type
Description
Identifier
Docucomp UUID
Instrument / Gear
Instrument Type
Description

Platforms

Platform Unavailable Reason  
Identifier
Docucomp UUID
Description

Mounted Instruments
Identifier  
Identifier  
Identifier  
Identifier
Docucomp UUID
Description

Mounted Instruments
Identifier  
Identifier  
Identifier  
Identifier
Docucomp UUID
Description

Mounted Instruments
Identifier  
Identifier  
Identifier  

FAQs

Date
Author
Question
Answer

Child Items

Rubric scores updated every 15m

Score Type Title
     
     
     

Related Items

Item Type Relationship Type Title
     
     
     

Catalog Details

Catalog Item ID 49681
Metadata Record Created By Anne Ball
Metadata Record Created 2017-11-15 15:21+0000
Metadata Record Last Modified By SysAdmin InPortAdmin
» Metadata Record Last Modified 2022-08-09 17:11+0000
Metadata Record Published 2022-03-16
Owner Org OCMP
Metadata Publication Status Published Externally
Do Not Publish? N
Metadata Workflow State Published / External
Metadata Last Review Date 2022-03-16
Metadata Review Frequency 1 Year
Metadata Next Review Date 2023-03-16
Tags