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
A bare earth digital elevation model (DEM) represents the earth's surface with all vegetation and human-made structures removed. The bare earth DEMs were derived from LiDAR data using triangulated irregular network (TIN) processing of the ground point returns. Hydro-flattened Bare Earth DEMs represent water bodies in a cartographically and aesthetically pleasing manner, and are not intended to accurately map water surface elevations. In a Hydro-flattened DEM, water surfaces are flat and level for lakes with a greater area than two acres, and gradated for rivers or other long impoundments (e.g., reservoirs) that are wider than 100 feet, and tidal areas. Any existing island larger than one acre was be delineated. Water surface edge elevations were at or below the immediately surrounding terrain. Each image corresponds to a 37,800-square-foot tile. Each pixel is 3 feet and represents an average elevation for that area. The specified coordinate system for this dataset is California State Plane Zone II (FIPS 0402), NAD83 (2011), with units in US Survey Feet for horizontal, and vertical units are NAVD88 (12A) US Survey Feet. The dataset encompasses all of Sonoma County and parts of Mendocino County. WSI collected the LiDAR and created this data set for the Sonoma County Vegetation Mapping and LiDAR Program.
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):
- 2014-02-19 00:00:00 - Acquisition. LiDAR data acquisition was started September 28, 2013 and was completed on November 26, 2013. The survey is utilizing a Leica ALS50 or ALS70 laser system mounted in a Piper Navajo PA-31-325 or Cessna Caravan 208B. Near nadir scan angles were used to increase penetration of vegetation to ground surfaces. Ground level GPS and aircraft IMU were collected during the flight.
- 2014-02-19 00:00:00 - Hydro-Flattening. The bare-earth DEMs were created by triangulating all ground classified points and inserting 3-D breaklines by utilizing Terra-Solid’s TerraScan and TerraModeler software. Any ground points within one meter of the breaklines were reclassified to “ignored-ground” (ASPRS code: 10) before triangulation. The highest-hit DEMs were generated from “ground” and “default” classified points. In instances where “water” classified points had the highest elevation value, the water surface elevation from the bare-earth raster were used.
- 2014-02-19 00:00:00 - LiDAR Data Processing. Flight lines and data were reviewed to ensure complete coverage of the study area and positional accuracy of the laser points. Laser point return coordinates were computed using ALS Post Processor software and IPAS Pro GPS/INS software, based on independent data from the LiDAR system, IMU, and aircraft. The raw LiDAR file was assembled into flight lines per return with each point having an associated x, y, and z coordinate. Visual inspection of swath to swath laser point consistencies within the study area were used to perform manual refinements of system alignment. Custom algorithms were designed to evaluate points between adjacent flight lines. Automated system alignment was computed based upon randomly selected swath to swath accuracy measurements that consider elevation, slope, and intensities. Specifically, refinement in the combination of system pitch, roll and yaw offset parameters optimize internal consistency. Noise (e.g., pits and birds) was filtered using ALS post-processing software, based on known elevation ranges and included the removal of any cycle slips. Using TerraScan and MicroStation, ground classifications utilized custom settings appropriate to the study area. The corrected and filtered return points were compared to the RTK ground survey points collected to verify the vertical and horizontal accuracies. Points were output as laser points, TINed and GRIDed surfaces.
- 2019-07-08 00:00:00 - NOAA Office for Coastal Management received the DEMs in imagine format with img and ige files. Data were converted to GeoTiff format with deflate compression using gdal_translate. Vertical georeferencing was also added. (Citation: Hydro-flattened DEMs)
(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 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.