Data Management Plan
GUID: gov.noaa.nmfs.inport:49902 | 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
The Oregon Department of Geology & Mineral Industries (DOGAMI) contracted with Watershed Sciences, Inc. to collect high
resolution topographic LiDAR data for Lake Billy Chinook (from the resevoir edge to the surrounding canyon rim). The
total area of this collection, including a 50 meter project buffer, is approximately 46 square miles (29,228 acres).
This LiDAR data set was collected on August 14th and 15th, 2008 and encompasses a portion of Jefferson County. This data
set consists of bare earth, water and unclassified points. There are approximately 7.8 points per square meter over terrestrial surfaces.
In some areas of heavy vegetation or forest cover, there may be relatively few ground points in the LiDAR data. Elevation values for
open water surfaces are not valid elevation values because few LiDAR points are returned from water surfaces. LiDAR intensity values
were also collected.
Original contact information:
Contact Name: Ian Madin
Contact Org: DOGAMI
Phone: 971-673-1542
Email: ian.madin@dogami.state.or.us
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:
- 2008-01-01 00:00:00 - Resolve kinematic corrections for aircraft position data using kinematic aircraft GPS and static ground GPS data. Software: Waypoint GPS v.7.60
- 2008-01-01 00:00:00 - Develop a smoothed best estimate of trajectory (SBET) file that blends post-processed aircraft position with attitude data (sensor heading, position, and attitude are calculated throughout the survey). Software: IPAS v.1.4
- 2008-01-01 00:00:00 - Calculate laser point position by associating SBET position to each laser point return time, scan angle, intensity, etc. Create raw laser point cloud data for the entire survey in *.las (ASPRS v1.1) format. Software: ALS Post Processing Software
- 2008-01-01 00:00:00 - Import raw laser points into subset bins (less than 500 MB, to accommodate file size constraints in processing software). Perform manual relative accuracy calibration and filter for pits/birds. Classify ground points for individual flight lines (to be used for relative accuracy testing and calibration). Software: TerraScan v.7.012
- 2008-01-01 00:00:00 - Test relative accuracy using ground classified points per each flight line. Perform automated line-to-line calibrations for system attitude parameters (pitch, roll, heading), mirror flex (scale) and GPS/IMU drift. Perform calibrations on ground classified points from paired flight lines. Every flight line is used for relative accuracy calibration. Software: TerraMatch v.7.004
- 2008-01-01 00:00:00 - Import position and attitude data. Classify ground and non-ground points. Assess statistical absolute accuracy via direct comparisons of ground classified points to ground RTK survey data. Convert data to orthometric elevations (NAVD88) by applying a Geoid03 correction. Create ground model as a triangulated surface and export as ArcInfo ASCII grids at the specified pixel resolution. Software: TerraScan v.7.012, ArcMap v9.2
- 2013-08-01 00:00:00 - The NOAA Office for Coastal Management (OCM) received the files in las format. The files contained LiDAR elevation and intensity measurements. The data were in Oregon State Plane North (NAD83), International Feet coordinates and NAVD88 (Geoid03) vertical datum. OCM performed the following processing to the data to make it available within the Digital Coast: 1. The data were converted from Oregon State Plane North (NAD83), International Feet coordinates to geographic coordinates. 2. The data were converted from NAVD88 (orthometric) heights to GRS80 (ellipsoid) heights using Geoid03. 3. The vertical units of the data were converted from International feet to 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.6. Type(s) of data
- 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/2543/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=2543
;
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.