NOAA Office for Coastal Management Coastal Inundation Digital Elevation Model: Miami (FL) WFO - Palm Beach, Broward, Miami-Dade, and Monroe (Keys) Counties
Office for Coastal Management
Data Set
(DS)
| ID: 48062
| Published / External
Created: 2017-11-14
|
Last Modified: 2023-05-30
Project (PRJ) | ID: 37230
ID: 48062
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | NOAA Office for Coastal Management Coastal Inundation Digital Elevation Model: Miami (FL) WFO - Palm Beach, Broward, Miami-Dade, and Monroe (Keys) Counties |
---|---|
Short Name | FL_MFL_2_metadata |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2012 |
* » Abstract |
This digital elevation model (DEM) is a part of a series of DEMs produced for the National Oceanic and Atmospheric Administration Office for Coastal Management's Sea Level Rise and Coastal Flooding Impacts Viewer. The DEMs created for this project were developed using the NOAA National Weather Service's Weather Forecast Office (WFO) boundaries. Because the WFO boundaries can cover large areas, the WFO DEM was divided into smaller DEMs to ensure more manageable file sizes. The Miami (FL) WFO DEM was split into two smaller DEMs. They are divided along county lines and are: 1. Miami (FL) WFO - Collier and Monroe (Mainland) Counties 2. Miami (FL) WFO - Palm Beach, Broward, Miami-Dade, and Monroe (Keys) Counties This metadata record describes the DEM for Miami (FL) WFO - Palm Beach, Broward, Miami-Dade, and Monroe (Keys) Counties. The DEM includes the best available lidar data known to exist at the time of DEM creation for the coastal areas of Palm Beach, Broward, Miami-Dade, and Monroe (Keys) counties, that met project specifications. The DEM is derived from LiDAR datasets collected for the Florida Department of Emergency Management (FDEM). LiDAR data for Monroe, Miami-Dade, Broward and Palm Beach counties was collected in 2007 and 2008. Hydrographic breaklines used in the creation of the DEM were obtained from FDEM and the South Florida Water Management District. The DEMs are hydro flattened such that water elevations are less than or equal to 0 meters. The DEM is referenced vertically to the North American Vertical Datum of 1988 (NAVD88) with vertical units of meters and horizontally to the North American Datum of 1983 (NAD83). The resolution of the DEM is approximately 5 meters. |
* Purpose |
The NOAA Office for Coastal Management has developed high-resolution digital elevation models (DEMs) for use in the Center's Sea Level Rise And Coastal Flooding Impacts internet mapping application. These DEMs serve as source datasets used to derive data to visualize the impacts of inundation resulting from sea level rise along the coastal United States and its territories. |
Notes |
10919 |
Other Citation Details | |
• Supplemental Information |
All datasets used to construct this DEM are publicly available via the NOAA Office for Coastal Management's Digital Coast (www.coast.noaa.gov/lidar). Further information regarding the constituent lidar datasets of this DEM can be accessed using the following url's: Monroe County (Blocks 1-7, 9-10): https://coast.noaa.gov/dataviewer/webfiles/metadata/fdem2007_blocks1_10_template.html Miami-Dade County (Blocks 2-6): https://coast.noaa.gov/dataviewer/webfiles/metadata/fdem2007_blocks1_10_template.html Broward County (Block 6): https://coast.noaa.gov/dataviewer/webfiles/metadata/fdem2007_blocks1_10_template.html Palm Beach County (Block 6-7): https://coast.noaa.gov/dataviewer/webfiles/metadata/fdem2007_blocks1_10_template.html Spatial_Reference_Information: Horizontal_Coordinate_System_Definition: Geographic: Latitude_Resolution: 0.0000001 Longitude_Resolution: 0.0000001 Geographic_Coordinate_Units: Decimal degrees Geodetic_Model: Horizontal_Datum_Name: North American Datum of 1983 Ellipsoid_Name: Geodetic Reference System 80 Semi-major_Axis: 6378137.000000 Denominator_of_Flattening_Ratio: 298.257222101 Vertical_Coordinate_System_Definition: Altitude_System_Definition: Altitude_Datum_Name: North American Vertical Datum of 1988 Altitude_Resolution: 0.001 Altitude_Distance_Units: meters Altitude_Encoding_Method: Explicit elevation coordinate included with horizontal coordinates |
DOI (Digital Object Identifier) | |
DOI Registration Authority | |
DOI Issue Date |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > LAND SURFACE > GEOMORPHIC LANDFORMS/PROCESSES > COASTAL PROCESSES > FLOODING |
Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > LAND SURFACE > GEOMORPHIC LANDFORMS/PROCESSES > COASTAL PROCESSES > SEA LEVEL CHANGES |
Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION > DIGITAL ELEVATION/TERRAIN MODEL (DEM) |
ISO 19115 Topic Category | elevation |
None | Bathymetry/Topography |
None | DEM |
None | Digital Elevation Model |
None | elevation |
None | flooding |
None | inundation |
None | lidar |
None | sea level rise |
None | topography |
Temporal Keywords
Thesaurus | Keyword |
---|---|
* Spatial Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Location Keywords | CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > FLORIDA |
None | Broward County |
None | Florida |
None | Miami-Dade County |
None | Monroe County |
None | Palm Beach County |
None | US |
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 | None Planned |
Maintenance Note | |
» Data Presentation Form | Image (digital) |
• 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 the Office for Coastal Management or its partners. |
Data Set Credit | Acknowledgment of the NOAA Office for Coastal Management as a data source would be appreciated in products developed from these data, and such acknowledgment as is standard for citation and legal practices for data source is expected. |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2012 |
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 | 2012 |
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 | 2012 |
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 | 2012 |
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 | -82.222033571 |
---|---|
* » E° Bound | -79.973248571 |
* » N° Bound | 26.9719578952 |
* » S° Bound | 24.3954378952 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Range |
---|---|
* » Start | 2007 |
End | 2008 |
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? | Yes |
---|---|
Vector Representation Used? | |
Text / Table Representation Used? | |
TIN Representation Used? | |
Stereo Model Representation Used? | |
Video Representation Used? |
Grid Representation
Dimension Count | 3 | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Cell Geometry | Area | ||||||||||||
Transformation Parameters Available? | No | ||||||||||||
Axis Dimension |
|||||||||||||
|
|||||||||||||
Axis Dimension |
|||||||||||||
|
|||||||||||||
Axis Dimension |
|||||||||||||
|
|||||||||||||
Axis Dimension |
|||||||||||||
|
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
Data License | |
---|---|
Data License URL | |
Data License Statement | |
* » Security Class | Unclassified |
* Security Classification System | |
Security Handling Description | |
• Data Access Policy | |
» Data Access Procedure | |
• » Data Access Constraints |
None |
• Data Use Constraints |
The dataset is provided "as is," without warranty to its performance, merchantable state, or fitness for any particular purpose. The entire risk associated with the results and performance of this dataset is assumed by the user. This dataset should be used strictly as a planning reference and not for navigation, permitting, or other legal purposes. |
Metadata Access Constraints | |
Metadata Use Constraints |
Distribution Information
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 |
Archive Information
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
URLs
URL | https://coast.noaa.gov/slr |
---|---|
Name | |
URL Type | Online Resource |
File Resource Format | |
Description |
URL | https://coast.noaa.gov/digitalcoast/tools/slr |
---|---|
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 | |
---|---|
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 DEM is derived from the source lidar data. Horizontal accuracy testing is not performed on the DEM. Lidar source data assumed to meet 1 meter horizontal accuracy. |
Vertical Positional Accuracy |
The DEM is derived from the source lidar data. Vertical accuracy is not tested on the DEM. Project specifications require all source lidar data used in constructing the DEM to meet FEMA Specifications for Flood Hazard Mapping. |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure | |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
Completeness Report |
A visual qualitative check was performed to ensure data completeness. All available lidar data known at the time of DEM creation that meets project specifications has been used to develop the DEM. Known data gaps may exist where lidar coverage was incomplete. |
Conceptual Consistency |
Data covers the project area, defined as the WFO boundary. Elevation data checked for anomalous elevation values outside expected range. |
» 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 | NOAA Office for Coastal Management lidar data holdings |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | NOAA Office for Coastal Management |
Publish Date | 2012-01-01 |
Extent Type | Range |
Extent Start Date/Time | 2007 |
Extent End Date/Time | 2008 |
Scale Denominator | |
Citation URL | https://coast.noaa.gov/dataviewer/ |
Citation URL Name | |
Citation URL Description | |
Source Contribution |
Lidar points covering portions of Monroe, Miami-Dade, Broward and Palm Beach Counties, Florida were used in developing the DEM. | Type of Source Media: online digital data |
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 |
1. Lidar source data and hydrographic breaklines were obtained and imported into an ESRI ArcGIS file geodatabase for each constituent county within the WFO boundary. Only ground classified lidar (Class 2) points were used to reflect a bare earth surface. Hydrographic features were assigned elevation values at or below 0 meters. An ESRI Terrain was then generated from these source data. 2. The ESRI Terrain was converted to a DEM (Erdas Imagine .img file format) with a cell size of 3 meters. The DEM was reviewed in Global Mapper for incorrect elevations and artifacts introduced from source inputs or during the raster creation process. Corrections were applied to the DEM and reprocessed for further review. 3. All DEMs for the entire study area (WFO) were loaded into Global Mapper for a final review. The constituent DEMs were then checked to ensure complete coverage within the study area and that no issues existed along the boundary between adjacent DEMs. Once it was determined all DEMs were seamlessly edge-matched and no other artifacts were present, the constituent DEMs were mosaiced together, resampled to 5m and reprojected to the NAD83 geographic coordinate system. |
Process Date/Time | 2011-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source | NOAA Office for Coastal Management lidar data holdings |
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 |
Child Items
Rubric scores updated every 15m
Score | Type | Title |
---|---|---|
Related Items
Item Type | Relationship Type | Title |
---|---|---|
Catalog Details
Catalog Item ID | 48062 |
---|---|
Metadata Record Created By | Anne Ball |
Metadata Record Created | 2017-11-14 14:15+0000 |
Metadata Record Last Modified By | SysAdmin InPortAdmin |
» Metadata Record Last Modified | 2023-05-30 18:09+0000 |
Metadata Record Published | 2018-02-08 |
Owner Org | OCM |
Metadata Publication Status | Published Externally |
Do Not Publish? | N |
Metadata Workflow State | Published / External |
Metadata Last Review Date | 2018-02-08 |
Metadata Review Frequency | 1 Year |
Metadata Next Review Date | 2019-02-08 |
Tags |
---|