Data Management Plan
GUID: gov.noaa.nmfs.inport:49896 | 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 lidar data set was collected along the Rogue River Greenway and Recreation Corridor, between TouVelle State Park and downtown
Grants Pass in portions of Jackson and Josephine Counties, Oregon. This data set covers approximately 28,000 acres
and was collected on May 30 and 31, 2007. The lidar data are multiple return and are classified as unclassified and bare earth.
Sky Research, Inc. collected the LiDAR and created this data set for Oregon Parks and Recreation Department.
Original contact information:
Contact Name: Brady Callahan
Contact Org: Oregon Parks and Recreation
Phone: 503-986-0783
Email: brady.callahan@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:
- 2007-01-01 00:00:00 - Sky Research acquired elevation data using an ALTM 3100 airborne LiDAR system at an average altitude of 1000 meters and a laser repetition rate of 71 kHz (71,000 measurements per second). The following were the LiDAR Data Acquisition Parameters: Scan width: 317 m, Scan Overlap: 50 percent, Scan Frequency: 50 Hz, Scan Angle: plus or minus 13 degrees, Average spot spacing: 0.54 m, Vertical accuracy: 10 cm, Horizontal Accuracy: 33 cm. During the data acquisition, the sensor operator observed the real-time LiDAR swath coverage to assure full coverage for the survey area. The operator also monitored the in-flight Position Dilution of Precision (PDOP) and GPS satellite coverage. If tolerance thresholds of either were exceeded, data acquisition activities were put on hold until acceptable conditions resumed. After the data acquisition flight, data from GPS base stations were checked against in-flight GPS data for concurrence. Once data quality assessments were completed, all data (image and ancillary) were transferred to a centralized location for pre-processing and quality control analysis.
- 2007-01-01 00:00:00 - After acquisition, the data were processed and analyzed, and the draft data was uploaded to the RVCOG interactive mapping site (IMS). Final data delivery and reporting concluded in August 2007.
- 2011-12-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 the Lambert Conformal Conic projection and NAVD88 Geoid 03 vertical datum. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The data were converted from Lambert Conformal Conic coordinates to geographic coordinates. 2. The data were converted from NAVD88 (orthometric) heights in feet to GRS80 (ellipsoid) heights in meters using Geoid 03. 3. The data were filtered to remove outliers. 4. The LAS data were sorted by latitude and the headers were updated.
(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/1120/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
The data set is dynamically generated based on user-specified parameters.
;
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.