Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:48376 | Published / External
This is an outdated version of the NOAA Data Management Plan template. InPort now supports a dedicated Data Management Plan Catalog Item type, which is up-to-date with the latest NOAA DMP template. The ability to generate Data Management Plans from Data Sets will be discontinued in a future release. Please see the Data Management Plan Help Guide to learn more.
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
This metadata describes the Digital Elevation Model (DEM) 1 meter products derived from the airborne LiDAR data collected in August of 2015 for the Pelekane Watershed on the big island of Hawaii. The point cloud dataset was acquired with an Optech Orion M300 Airborne LiDAR Terrain Mapper with a nominal point spacing of 0.33 m. The DEM for this delivery was made from airborne LiDAR in LP360. A triangulated irregular network (TIN) was generated based on the LiDAR ground information (Using the tenderloin part of the point cloud only), and was later converted in a 1-meter raster file (DEM). Horizontal positions are referenced to UTM Zone 5 North (NAD83 PA11). Vertical elevations are in an orthometric datum derived from applying Geoid12b to NAD83(2011) ellipsoid heights and are in meters.
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.
4. Resources
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):
Process Steps:
- This point cloud dataset was acquired with an Optech Orion M300 Airborne LiDAR Terrain Mapper with a nominal point spacing of 0.33 m. The spatial reference is the UTM Zone 5 North with NAD83 (PA11) as horizontal datum. The vertical datum is GRS80. Units are in meters. This point cloud data classified as follows: Class 0: Untouched, Class 1: Unclassified, Class 2: Ground, Class 3: Low Vegetation, Class 4: Medium Vegetation, Class 5: High Vegetation, Class 6: Building, Class 7: Low point, Class 9: Water, Class 17: Bridge Deck, Class 18: High Noise. The overlap and keypoint flags are also set. The data were acquired in the summer of 2015.
- The DEM for this delivery was made from airborne LiDAR in LP360. A triangulated irregular network (TIN) was generated based on the LiDAR ground information (Using the tenderloin part of the point cloud only), and was later converted in a 1-meter raster file (DEM). The general tiling scheme for the DEM grids is made of cells of 3'000 x 3'000 m. The DEM grids are saved in the Envi DAT floating point raster format. The elevations are in meters.
- 2017-07-24 00:00:00 - The NOAA Office for Coastal Management (OCM) received 11 files in .dat format from TetraTech. The bare earth raster files were at a 1 m grid spacing. The data were in UTM Zone 5 (NAD83 PA11) and ellipsoid elevations in meters. OCM did the following for Digital Coast storage and provisioning purposes: 1. Converted the .dat format files to .img format using Global Mapper 18 2. Converted the files from ellipsoid heights to orthometric heights by applying the NGS Geoid12b model. (Citation: DEM tiles in .dat format)
(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.
Missing/invalid information:
- 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.
None
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.
https://noaa-nos-coastal-lidar-pds.s3.us-east-1.amazonaws.com/dem/HI_Pelekane_DEM_2015_5192/index.html
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
This data can be obtained on-line at the following URL: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=5192
;
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.