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
Dewberry collected 1000 square miles of lidar data in Pasco County, Florida. The nominal pulse spacing for this project was 1 point every 0.35 meters or a nominal pulse density of 8 points per square meter. Dewberrry used proprietary procedures to classify the LAS according to project specifications: 1-Unclassified, 2-Ground, 6-Building Rooftops, 7-Low Noise, 9-Water, 17- Bridge Decks, 18-High Noise. Geometrically unreliable points, ground points within 2 feet of breaklines, and ground points within 3 feet of buiding rooftops have been identified with the Withheld Flag. Overage points have been identified with the Overlap Flag. The lidar data were combined with 3D breaklines compiled by Dewberry to create hydro-enforced bare-earth DEMs. The data were tiled according to the Florida Statewide Lidar Index tiling scheme with each tile covering an area of 5,000 feet by 5,000 ft.
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):
The NOAA Office for Coastal Management (OCM) downloaded the DEM .img file from the Southwest Florida Water Management District (SWFWMD).
- 2018-03-01 00:00:00 - Class 2, ground, lidar points are exported from the LAS files into an Arc Geodatabase (GDB) in multipoint format. The 3D breaklines, water bodies, hydrographic features, and islands are imported into the same GDB. 2D building footprints are buffered by 3 feet and the highest ground elevation within the buffered footprint is applied to the entire footprint. The 3D building footprints are then imported into the same GDB as the multipoints and other 3D breaklines. An ESRI Terrain is generated from these inputs. The surface type of each input is as follows: Ground Multipoint: Masspoints Water bodies: Hard Replace Hydrographic feature : Hard Line Islands : Hard Line Building Footprint: Hard Replace The ESRI Terrain is converted to a raster. The raster is created using linear interpolation with a 2.5 foot cell size. The DEM is reviewed with hillshades in both ArcGIS and Global Mapper. Hillshades allow the analyst to view the DEMs in 3D and to more efficiently locate and identify potential issues. Analysts review the DEM for missed lidar classification issues, incorrect breakline elevations, incorrect hydro-flattening or hydro-enforcement, and artifacts that are introduced during the raster creation process. The corrected and final DEM is clipped to individual tiles. Dewberry uses a proprietary tool that clips the DEM to each tile located within the final Tile Grid, names the clipped DEM to the Tile Grid Cell name, and verifies that final extents are correct. All individual tiles are loaded into Global Mapper for the last review. During this last review, an analsyt checks to ensure full, complete coverage, no issues along tile boundaries, tiles seamlessly edge-match, and that there are no remaining processing artifacts in the dataset.
- 2022-03-21 00:00:00 - The NOAA Office for Coastal Management (OCM) downloaded 1 raster DEM file in .img format from the Southwest Florida Water Management District (SWFWMD). The data were in Florida State Plane West NAD83(2011), US survey feet coordinates and NAVD88 (Geoid12B) elevations in feet. The bare earth raster file was at a 2.5 feet grid spacing. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. Used internal an script to assign the EPSG codes (Horizontal EPSG: 6443 and Vertical EPSG: 6360) and convert the .img file to GeoTiff format. 2. Copied the file 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.