Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:49900 | 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
Watershed Sciences, Inc. (WS) collected Light Detection and Ranging (LiDAR) data for the USDA
Forest Service on September 17, 2007. The project covers an 8-mile reach of the
Powder River in northeast Oregon, downstream of the town of Sumpter. The extent of
requested LiDAR area totals over 3,146 acres; the map below shows the extent of the
LiDAR area to be delivered, covering nearly 3,208 acres. The delivered acreage for the study area is
greater than the original amount due to buffering of the original AOI and flight planning
optimization.
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:
- 2007-09-17 00:00:00 - Acquisition. The LiDAR survey utilized a Leica ALS50 Phase II mounted in Cessna Caravan 208B. The full survey was conducted September 17, 2007. The Leica ALS50 Phase II system was set to acquire =105,000 laser pulses per second (i.e. 105 kHz pulse rate) and flown at 800 meters above ground level (AGL), capturing a scan angle of plus\minus 14o from nadir2. These settings are developed to yield points with an average native density of =8 points per square meter over terrestrial surfaces. The native pulse density is the number of pulses emitted by the LiDAR system. Some types of surfaces (i.e., dense vegetation or water) may return fewer pulses than the laser originally emitted. Therefore, the delivered density can be less than the native density and lightly variable according to distributions of terrain, land cover and water bodies.
- 1. Resolve kinematic corrections for aircraft position data using kinematic aircraft GPS and static ground GPS data. 2. Develop a smoothed best estimate of trajectory (SBET) file that blends the post-processed aircraft position with altitude. 3. Calculate laser point position by associating the SBET position to each laser point return time, scan angle, intensity, etc. Creates raw laser point cloud data for the entire survey in *.las. 4. Import raw laser points into manageable blocks (less than 500 mb) to perform manual relative accuracy calibration and filter for pits/birds. Ground points are then classified for individual flights lines (to be used for relative accuracy testing and calibration). 5. Using ground classification points per each flight line, the relative accuracy is tested. Automated line-to-line calibrations are then performed for system attitude parameters (pitch, roll, heading), mirror flex (scale) and GPS/IMU drift. Calibrations are performed on ground classified points from paired flights lines. Every flight line is used for relative accuracy calibration. 6. Position and attitude data are imported. Resulting data are classified as ground and non-ground points. Statistical absolute accuracy is assessed via direct comparisons of ground classified points to ground RTK survey data. Data are then converted to orthometric elevations (NAVD88) by applying a Geoid03 correction. Ground models are created as a triangulated surface and exported as ArcInfo ASCII grids at a 1-meter pixel resolution.
- 2013-11-20 00:00:00 - The NOAA Office for Coastal Management (OCM) downloaded topographic files in LAZ format from the Puget Sound Lidar Consortium's (PSLC) website. The files contained lidar easting, northing, elevation, intensity, return number, class, scan angle and GPS time measurements; the data was received in UTM Zone 11 (in meters) and vertical coordinates were referenced to NAVD88 in meters using the Geoid03 model. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The All-Return LAZ files were checked for bad elevations 2. The laz files were converted from a Projected Coordinate System (UTM Zone 11) to a Geographic Coordinate system (NAD83) 3. The laz files were then converted to ellipsoidal vertical units in meters.
(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.amazonaws.com/laz/geoid18/2606/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=2606
;
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.