Data Management Plan
DMP Template v2.0.1 (2015-01-01)Please provide the following information, and submit to the NOAA DM Plan Repository.
Reference to Master DM Plan (if applicable)
As stated in Section IV, Requirement 1.3, DM Plans may be hierarchical. If this DM Plan inherits provisions from a higher-level DM Plan already submitted to the Repository, then this more-specific Plan only needs to provide information that differs from what was provided in the Master DM Plan.
1. General Description of Data to be Managed
Product: These are Digital Elevation Model (DEM) data for FL Panhandle as part of the required deliverables for the 2018 FL Panhandle Lidar project. Class 2 (ground) lidar points in conjunction with the hydro breaklines were used to create a 1 meter hydro-flattened Raster DEM. This delivery consists of 2859 tiles.
Geographic Extent: Bay, Calhoun, Covington, Decatur, Dixie, Escambia, Franklin, Gadsden, Geneva, Grady, Gulf, Holmes, Houston, Jackson, Jefferson, Lafayette, Leon, Liberty, Madison, Okaloosa, Santa Rosa, Seminole, Taylor, Thomas, Walton, Wakulla, Walton, and Washington counties, Florida, covering approximately 5,952 square miles.
Dataset Description: FL Panhandle 2018 Lidar project called for the Planning, Acquisition, processing and derivative products of lidar data to be collected at a nominal pulse spacing (NPS) of 0.7 meter. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 1.3. The data was developed based on a horizontal projection/datum of NAD83 (2011), Albers Equal Area, meters and vertical datum of NAVD88 (GEOID12B), meters. Lidar data was delivered as processed Classified LAS 1.4 files, formatted to 16,768 individual 1000 m x 1000 m tiles, as tiled Intensity Imagery, and as tiled bare earth DEMs; all tiled to the same 1000 m x 1000 m schema.
Ground Conditions: Lidar was collected in early 2018, while no snow was on the ground and rivers were at or below normal levels. In order to post process the lidar data to meet task order specifications and meet ASPRS vertical accuracy guidelines, Airborne Imaging used 30 control points (16 FL DOT FPRN stations, 5 NGS monuments, and 9 newly established base stations) to control the lidar acquistion and tie the lidar to known ground locations established throughout the FL Panhandle project area. Over 15,000 GNSS kinematic points were used by Airborne Imaging to verify accuracy of the calibarted lidar data. An additional full AOI will be tested with 262 independent accuracy checkpoints, 152 in Bare Earth and Urban landcovers (152 NVA points), 110 in Tall Grass and Brushland/Low Trees categories (110 VVA points), but interim accuracy of Block 1 was tested with 22 in Bare Earth and Urban landcovers (22 NVA points), 12 in Tall Grass and Brushland/Low Trees categories (12 VVA points), were used to assess the vertical accuracy of the Block 1 data. These checkpoints were not used to calibrate or post process the data.
In addition to these bare earth Digital Elevation Model (DEM) data, the lidar point data that these DEM data were created from, are also available. These data and the breaklines are available for download at the links provided in the URL section of this metadata record.
Notes: Only a maximum of 4000 characters will be included.
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.
Notes: All time frames from all extent groups are included.
Notes: All geographic areas from all extent groups are included.
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)
(e.g., satellite, airplane, unmanned aerial system, radar, weather station, moored buoy, research vessel, autonomous underwater vehicle, animal tagging, manual surveys, enforcement activities, numerical model, etc.)
2. Point of Contact for this Data Management Plan (author or maintainer)
Notes: The name of the Person of the most recent Support Role of type "Metadata Contact" is used. The support role must be in effect.
Notes: The name of the Organization of the most recent Support Role of type "Metadata Contact" is used. This field is required if applicable.
3. Responsible Party for Data Management
Program Managers, or their designee, shall be responsible for assuring the proper management of the data produced by their Program. Please indicate the responsible party below.
Notes: The name of the Person of the most recent Support Role of type "Data Steward" is used. The support role must be in effect.
Programs must identify resources within their own budget for managing the data they produce.
5. Data Lineage and Quality
NOAA has issued Information Quality Guidelines for ensuring and maximizing the quality, objectivity, utility, and integrity of information which it disseminates.
(describe or provide URL of description):
- 2018-07-15 00:00:00 - Hydro Flattened Raster DEM Process: Class 2 (ground) lidar points in conjunction with the hydro breaklines were used to create a 1 meter hydro-flattened Raster DEM. Using automated scripting routines within ArcMap, an ERDAS Imagine IMG file was created for each tile. Each surface is reviewed using Global Mapper to check for any surface anomalies or incorrect elevations found within the surface.
- 2019-12-16 00:00:00 - The NOAA Office for Coastal Management (OCM) received this data set from the Northwest Florida Water Management District (NWFWMD). The total number of files provided was 16,802. The data were in img format. The data were in US Albers (NAD83 (2011)) meters coordinates and NAVD88 (Geoid12B) elevations in meters. The bare earth raster files were at a 1 meter grid spacing. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. Used an internal script to assign the EPSG codes (Horiz - 6360, Vert - 5703) and convert from img to GeoTiff format. 2. Copied to the files to https.
(describe or provide URL of description):
6. Data Documentation
The EDMC Data Documentation Procedural Directive requires that NOAA data be well documented, specifies the use of ISO 19115 and related standards for documentation of new data, and provides links to resources and tools for metadata creation and validation.
- 1.7. Data collection method(s)
- 3.1. Responsible Party for Data Management
- 4.1. Have resources for management of these data been identified?
- 4.2. Approximate percentage of the budget for these data devoted to data management
- 5.2. Quality control procedures employed
- 7.1. Do these data comply with the Data Access directive?
- 7.1.1. If data are not available or has limitations, has a Waiver been filed?
- 7.1.2. If there are limitations to data access, describe how data are protected
- 7.4. Approximate delay between data collection and dissemination
- 8.1. Actual or planned long-term data archive location
- 8.3. Approximate delay between data collection and submission to an archive facility
- 8.4. How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?
(describe or provide URL of description):
7. Data Access
NAO 212-15 states that access to environmental data may only be restricted when distribution is explicitly limited by law, regulation, policy (such as those applicable to personally identifiable information or protected critical infrastructure information or proprietary trade information) or by security requirements. The EDMC Data Access Procedural Directive contains specific guidance, recommends the use of open-standard, interoperable, non-proprietary web services, provides information about resources and tools to enable data access, and includes a Waiver to be submitted to justify any approach other than full, unrestricted public access.
Notes: The name of the Organization of the most recent Support Role of type "Distributor" is used. The support role must be in effect. This information is not required if an approved access waiver exists for this data.
Notes: This field is required if a Distributor has not been specified.
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
Data is available online for bulk and custom downloads.
Notes: This field is required if applicable.
8. Data Preservation and Protection
The NOAA Procedure for Scientific Records Appraisal and Archive Approval describes how to identify, appraise and decide what scientific records are to be preserved in a NOAA archive.
(Specify NCEI-MD, NCEI-CO, NCEI-NC, NCEI-MS, World Data Center (WDC) facility, Other, To Be Determined, Unable to Archive, or No Archiving Intended)
Notes: This field is required if archive location is World Data Center or Other.
Notes: This field is required if archive location is To Be Determined, Unable to Archive, or No Archiving Intended.
Notes: Physical Location Organization, City and State are required, or a Location Description is required.
Discuss data back-up, disaster recovery/contingency planning, and off-site data storage relevant to the data collection
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.