2007 Florida Division of Emergency Management (FDEM) Lidar Project: Eastern Indian River County
OCM Partners
Data Set
(DS)
| ID: 49673
| Published / External
Created: 2017-11-15
|
Last Modified: 2022-08-09
Project (PRJ) | ID: 49401
ID: 49673
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2007 Florida Division of Emergency Management (FDEM) Lidar Project: Eastern Indian River County |
---|---|
Short Name | fdem2007_indian_river_m539_metadata |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2008 |
* » 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 255 square miles in the eastern portion of Indian River County, Florida from August 24 - 28, 2007. This is a classified lidar data set. The data are classified: 1 = Unclassified, 2 = Ground (Bare Earth), 7 = Noise, 9 = Water and 12 = Overlap. The data was collected at a maximum post spacing of 4 feet in unobscured areas for random point data. Original contact information: Contact Org: Florida DEM Phone: 850-413-9907 Email: gis@dca.state.fl.us |
* 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. |
Notes |
10317 |
Other Citation Details | |
• Supplemental Information |
A complete description of this data set is available in the Minimum Technical Standard (MTS report) "Minimum Technical Standards, Vol.2 Final Report of Lidar Mapping, Indian River County, Florida" and in "Minimum Technical Standards, Vol. 1 Final Report of Lidar Control and QA/QC Checkpoint Survey, Indian River County, Florida." These reports may be accessed at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/539/supplemental A footprint of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/539/supplementalFDEM_Lidar_Indian_River_County.kmz |
DOI (Digital Object Identifier) | |
DOI Registration Authority | |
DOI Issue Date |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
ISO 19115 Topic Category | elevation |
None | Contours |
None | Hydrology |
None | Photogrammetry |
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 and Attribute information designed in accordance to FDEM Baseline Specifications 1.2 (Attachment 3) |
Entity Attribute Detail Citation |
Entity and Attribute information designed in accordance to FDEM Baseline Specifications 1.2 (Attachment 3) |
Entity Attribute Detail URL | |
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. |
Data Set Credit |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2008 |
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 | 2008 |
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 | 2008 |
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 | 2008 |
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 | Ground Condition |
---|
Extent Group 1
Extent Description |
---|
Extent Group 1 / Geographic Area 1
* » W° Bound | -80.61717 |
---|---|
* » E° Bound | -80.30907 |
* » N° Bound | 27.867889 |
* » S° Bound | 27.550789 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Range |
---|---|
* » Start | 2007-08-24 |
End | 2007-08-28 |
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 |
|||||||||||||
|
|||||||||||||
Axis Dimension |
|||||||||||||
|
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 |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Vertical Resolution |
|||||||||||||||||||||||||||||
|
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; |
• » 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=539 |
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/539/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 | |
---|---|
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 |
Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 9.2.2.1350 |
---|
Data Quality
Representativeness | |
---|---|
Accuracy | |
Analytical Accuracy | |
Horizontal Positional Accuracy |
Per contract specification, the horizontal accuracy requirement is to meet or exceed a 3.8-foot (1.15 m) horizontal accuracy at the 95% confidence level using RMSE(r) x 1.7308 as defined by the FGDC Geospatial Positional Accuracy Standards, Part 3: NSSDA. Please refer to the two reports that accompany this data set for more detailed information. These reports may be accessed at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/539/supplemental/index.html |
Vertical Positional Accuracy |
0.3-feet (9.14 cm) tested RMSE for unobscured ground points. The accuracy assessment was performed using a standard method to compute the root mean square error (RMSE) based on a comparison of ground control points and filtered LiDAR data points. Filtered LiDAR data has had vegetation and cultural features removed and by analysis represents bare earth elevations. The RMSE figure was used to compute the vertical National Standard for Spatial Data Accuracy (NSSDA). The Brush Lands and Low Trees and the Forested Areas Fully Covered by Trees landcover types exceed the recommended maximum values for RMSEz and 95% CI. Brush Lands and Low Trees exceed the recommended accuracies by 0.07 feet and 0.14 feet, respectively. Forested Areas Fully Covered by Trees type exceeds the recommended accuracies by 0.31 feet and 0.61 feet, respectively. This indicates that there is a greater degree of misclassification of lidar points within these landcover types than within the Bare Earth and Low Grass and Urban Areas landcover types. It is important that users of the data be aware of the potential accuracy limitations within the Forested Areas Fully Covered by Trees and to a lesser degree for the Brush Lands and Low Trees. Please refer to the two reports that accompany this data set for more detailed information. These reports may be accessed at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/539/supplemental/index.html |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure | |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
Completeness Report |
This feature class represents the complete set of data for 284 tiles within Indian River County. |
Conceptual Consistency |
The LiDAR DTM was developed in accordance with the Baseline Specifications 1.2. The DTM is intended to support 2-foot contours, and the vertical accuracy of ground points in unobscured areas is not to exceed 0.6-feet RMSE. |
» 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 | State of Florida Division of Emergency Management LiDAR Project Survey |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | 2008-03-27 |
Extent Type | Discrete |
Extent Start Date/Time | 2008-03-27 |
Extent End Date/Time | |
Scale Denominator | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Source Contribution |
The LiDAR Project Survey was acquired for the Florida Division of Emergency Management and processed by Woolpert Inc. To collect the breaklines the LiDAR data was used as the main source data set in addition to orthophotography. Orthophoto imagery was from new imagery collected and developed by the Woolpert Team. All imagery for Indian River County is dated 2007 with a 0.5 foot pixel resolution. | Source Geospatial Form: vector digital data | Type of Source Media: disc |
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 was collected within portions of Indian River County. System Parameters/Flight Plan: The LiDAR system acquisition parameters were developed based on a maximum average ground sample distance of 4 feet. Two Leica ALS50 sensors were used for acquisition. Acquisition specifications for the two sensors were as follows: Sensor 19 Field of View (full angle) - 29 degrees Nominal flight altitude (AMSL) - 3999.30 feet Airspeed - 54.02 meters/sec Laser pulse rate - 75,000 Hz Nominal swath width (on ground) - 2068.58 feet Maximum cross track point spacing - 3.91 feet Maximum along track point spacing - 3.94 feet Average point spacing - 2.21 feet Flight line spacing - 1544.95 feet Side overlap - 25.31%. Sensor 59 Field of View (full angle) - 29 degrees Nominal flight altitude (AMSL) - 3999.30 feet Airspeed - 60.70 meters/sec Laser pulse rate - 84,400 Hz Nominal swath width (on ground) - 2068.58 feet Maximum cross track point spacing - 3.94 feet Maximum along track point spacing - 3.91 feet Average point spacing - 2.21 feet Flight line spacing - 1413.72 feet Side overlap - 31.66%. LiDAR System Calibration: Prior to the LiDAR acquisition, the system underwent a calibration to verify the operational accuracy and misalignment angles. Boresight calibrations were performed for each LiDAR system at the beginning and end of each flight mission. LiDAR Data Acquisition: LiDAR data acquisition only occurred when the sky was sufficiently clear of clouds, smoke, and atmospheric haze. The LiDAR data was processed immediately after the acquisition to verify the coverage had no voids. GPS/Inertial Measurement Unit (IMU) Post Processing: The GPS and IMU data was post processed using differential and Kalman filter algorithms to derive a best estimate of trajectory. The quality of the solution was verified to be consistent with the accuracy requirements of the project. LiDAR Processing and Classification: The LiDAR data was post processed and verified to be consistent with the project requirements in terms of post spacing and absence of artifacts. The point cloud underwent classification to determine bare-earth points (class 2), noise points (class 7), water returns (class 9), and unclassified data (class 1). Class 12 contains LiDAR points removed from the overlap region between adjacent flight lines. |
Process Date/Time | 2009-01-05 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 2 |
---|---|
» 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 East 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. |
Process Date/Time | 2010-06-01 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 | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
FAQs
Date | |
---|---|
Author | |
Question | |
Answer |
Related Items
Item Type | Relationship Type | Title |
---|---|---|
Catalog Details
Catalog Item ID | 49673 |
---|---|
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 |
---|