Data Management Plan
GUID: gov.noaa.nmfs.inport:57756 | 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
Watershed Sciences, Inc. (WSI) collected airborne Thermal Infrared (TIR) imagery and Light Detection and Ranging (LiDAR) data for the Department of Geology and Mineral Industries (DOGAMI) in Malheur, Harney, and Lake Counties during March and April 2012. This is the final delivery encompassing the four remaining study areas of the DOGAMI TIR and LiDAR survey. The requested acreage for Christmas Valley (13,041 acres), Oregon Military (9,701 acres), Paulina Marsh (56,287 acres), and Baker Pass (44,846 acres) study areas were expanded to include a 100m buffer to ensure complete coverage around survey area boundaries. This expansion results in a total of 13,809 acres, 10,344 acres, 57,768 acres, and 46,194 acres of delivered TIR and LiDAR data, respectively (Figure 1). The TIR imagery provides an accurate data set for detecting and identifying surface expression of geothermal activity. LiDAR data was co-acquired with the TIR imagery and provides highly detailed topographic data for recognizing landforms associated with detected thermal features.
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.
Paulina MarshW: -120.773, E: -120.599, N: 43.047, S: 42.915
Summer LakeW: -120.677, E: -120.547, N: 43.334, S: 43.244
Christmas ValleyW: -120.39, E: -120.302, N: 43.325, S: 43.249
Oregon MilitaryW: -118.256, E: -118.075, N: 43.183, S: 43.013
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.
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):
Data were collected and processed by Watershed Sciences, Inc. for DOGAMI. NOAA/OCM received the data from DOGAMI for ingest in the Digital Coast Data Access Viewer.
- 2012-04-13 00:00:00 - Acquisition. The LiDAR survey utilized a Leica ALS60 sensor mounted in a Cessna Caravan.The Leica system was set to acquire 88,000 laser pulses per second (i.e., 88 kHz pulse rate) and was flown at 1,100 meters above ground level (AGL), capturing a scan angle of ±15o from nadir. With these flight parameters, the laser swath width was 598m and the laser pulse footprint was 26cm. These settings were developed to yield points with an average native pulse density of 4 pulses per square meter over terrestrial surfaces. All areas were surveyed with an opposing flight line side-lap of ≥50% (≥100% overlap) to reduce laser shadowing and increase surface laser painting. The Leica laser systems allow up to four range measurements (returns) per pulse, and all discernible laser returns were processed for the output dataset. To accurately solve for laser point position (geographic coordinates x, y, z), the positional coordinates of the airborne sensor and the attitude of the aircraft were recorded continuously throughout the LiDAR data collection mission. Aircraft position was measured twice per second (2 Hz) by an onboard differential GPS unit. Aircraft attitude was measured 200 times per second (200 Hz) as pitch, roll and yaw (heading) from an onboard inertial measurement unit (IMU). To allow for post-processing correction and calibration, aircraft/sensor position and attitude data are indexed by GPS time.
- 2012-06-01 00:00:00 - Processing. 1. Resolved kinematic corrections for aircraft position data using kinematic aircraft GPS and static ground GPS data. Software: Waypoint GPS v.8.10, Trimble Business Center 2.6 2. Developed a smoothed best estimate of trajectory (SBET) file that blends post-processed aircraft position with attitude data. Sensor head position and attitude were calculated throughout the survey. The SBET data were used extensively for laser point and thermal image processing. Software: IPAS TC v.3.1 3. Calculated laser point position by associating SBET position to each laser point return time, scan angle, intensity, etc. Created raw laser point cloud data for the entire survey in *.las (ASPRS v. 1.2) format. Data were then converted to orthometric elevations (NAVD88) by applying a Geoid03 correction. Software: ALS Post Processing Software v.2.74 4. Imported raw laser points into manageable blocks (less than 500 MB) to perform manual relative accuracy calibration and filter for pits/birds. Ground points were then classified for individual flight lines (to be used for relative accuracy testing and calibration). Software: TerraScan v.12.004 5. Using ground classified points per each flight line, the relative accuracy was tested. Automated line-to-line calibrations were then performed for system attitude parameters (pitch, roll, heading), mirror flex (scale) and GPS/IMU drift. Calibrations were performed on ground classified points from paired flight lines. Every flight line was used for relative accuracy calibration. Software: TerraMatch v.12.001 6. Position and attitude data were imported. Resulting data were classified as ground and non-ground points. Statistical absolute accuracy was assessed via direct comparisons of ground classified points. Software: TerraScan v.12.004, TerraModeler v.12.002 (Citation: Raw Lidar Data)
- 2012-09-01 00:00:00 - Bare Earth models were created as a triangulated surface and exported as ArcInfo ASCII grids at a 1 meter pixel resolution. Software: TerraScan v.12.004, TerraModeler v.12.002, ARCGIS10 (Citation: Processed Lidar Data)
- 2019-09-25 00:00:00 - The NOAA Office for Coastal Management (OCM) received the raster DEM files from DOGAMI in ArcGrid format. The data were in NAD83(CORS96) UTM 10 or 11 (Baker Pass only) meters coordinates and NAVD88 (Geoid03) vertical meters. OCM transformed the data to GeoTiff format to comply with the Open Data Policy and ingest into the Data Access Viewer. This metadata record was generated from the project report as no metadata record was received from DOGAMI. (Citation: DEM tiles)
(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.
- 1.6. Type(s) of data
- 1.7. Data collection method(s)
- 3.1. Responsible Party for Data Management
- 5.2. Quality control procedures employed
- 7.4. Approximate delay between data collection and dissemination
- 8.3. Approximate delay between data collection and submission to an archive facility
(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.
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.
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
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
Backup in Azure cloud
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.