Data Management Plan
GUID: gov.noaa.nmfs.inport:58224 | Published / External
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 bare earth hydro flattened digital elevation model (DEM) represents the earth's surface with all vegetation and human-made structures removed and hydro flattening performed within the OLC John Day 3DEP 2017 defined project area. Bare Earth Hydro Flattened DEMs were derived from LiDAR data using TIN processing of the ground point returns. The DEM grid cell size is 1 meter. The data were developed based on the UTM 11N projection; horizontal datum of NAD83 (2011), meters and vertical datum of NAVD88 Geoid 12B, meters. See Process Steps for derivation of raster data sets.
In addition to these bare earth Digital Elevation Model (DEM) data, the lidar point data that these DEM data were created from and the breakline data are also available. These data are available for download at the link 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.
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:
- 2017-07-10 00:00:00 - Acquisition. LiDAR data acquisition was conducted from 20170614 to 20170709. The survey utilized a Leica ALS80 sensor mounted in a Cessna Caravan. 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.
- 2017-07-10 00:00:00 - Processing. 1. TRAJECTORY: Aircraft trajectory (position and attitude) were calculated based on on-board GPS and IMU data with post-processing refinement through coincident static GPS collection. 2. POST-PROCESSING: Laser point return coordinates (x,y,z) were computed using sensor-specific post processing software, combining LiDAR return range and intensity information with aircraft trajectory information. 3. INITIAL QAQC: The post-processed LiDAR files were assembled into flight lines and reviewed for gaps and consistency, as well as systematic noise. 4. CALIBRATION: Custom algorithms evaluated individual swaths for misalignments based on IMU configuration as well as aircraft attitude variability. Offsets were resolved through surface and linear matching algorithms that minimize variability in elevation and slope. Descriptive statistics, thresholds, and specifications providing transparency for data calibration are discussed in the accompanying Data Report. 5. GROUND MODELING: Ground classified point cloud was generated through proprietary data processing tools, with settings and thresholds appropriate to landscape and vegetation condition. 6. ARTIFACT FILTRATION: Noise and processing artifacts were filtered using post-processing software and proprietary quality control methods. 7. ACCURACY ASSESSMENT: Vertical accuracy for the LiDAR dataset was assessed against reserved Quality Assurance Points (QAPs) distributed throughout the study area and not used during calibration processes. See the accompanying Data Report for methodology, descriptive statistics, and relevant standards and reporting language. 8. DATA PRODUCT: LiDAR points classified as 'ground' were output as a digital elevation model (DEM). 9. Hydro Flattening Breakline Processing: Class 2 LiDAR was used to create a bare earth surface model. E-Cognition utilized rasters created within Bentley Microstation to auto-generate breaklines of inland streams and rivers with a 100 foot nominal width and Inland Ponds of 2 acres or greater surface area. Breaklines for Lakes with surface area greater than 2 acres were generated using heads-up digitization. Elevation values were assigned to all Inland Ponds and Lakes within ESRI ArcMap; Inland Pond and Lake Islands, Inland Stream and River Islands were assigned elevation values from within ESRI ArcMap. All ground (ASPRS Class 2) LiDAR data inside of the collected inland breaklines were then classified to water (ASPRS Class 9) using TerraScan macro functionality. A buffer of 2.1 meter was also used around each hydro-flattened stream. These points were moved from ground (ASPRS Class 2) to Ignored Ground (ASPRS Class 10). The breakline files were then translated to ESRI File-Geodatabase format using ESRI conversion tools.
- 2019-11-13 00:00:00 - The NOAA Office for Coastal Management (OCM) received 5472 hydro-flattened bare earth DEM files in Arc Grid format from DOGAMI. The data were in UTM Zone 11, NAD83 (2011), meters, coordinates and NAVD88 (Geoid12B) elevations in meters. The EPSG codes (Horizontal - 6340, Vertical - 5703), were assigned. The data were converted to GeoTIFF format for ingest into the Digital Coast Data Access Viewer and to adhere to the Open Data Policy.
(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/OLC_John_Day_DEM_2017_8922/index.html
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.