Data Management Plan
GUID: gov.noaa.nmfs.inport:56471 | 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
Wild Rice (Manoomin) plays an integral role in the ecosystems, culture, and economy of the Lake Superior region and it faces an existential threat from invasive species which compete for the same habitat and a variety of other factors. Six Areas of Interest (AOI) were identified as pilot sites and selected as the target AOI for this project.
1. Crooked Lake, Sucker Lake, and the Ontonagon River (CSO)
2. Eastern Upper Peninsula (EUP)
3. Fond du Lac (FDL)
4. Kakagon Sloughs and Bad River (KSBR)
5. St. Louis River Estuary (SLRE)
6. Upper St. Louis River (USLR)
Funding for this project was received via Great Lakes Restoration Initiative. For more information on the Initiative and Action Plan go to https://www.glri.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.
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):
- 2018-01-01 00:00:00 - The following section details the steps taken to pre-process the data. Processing Level 1a – Radiometric Correction 1. Dark Noise Removal Dark image data was acquired for every raw image at the end of every flight line by the sensor control software closing the shutter and recording 5 seconds of dark noise. To remove sensor noise the mean value of every line of the dark data was subtracted from the corresponding line of the raw data (dark noise removal or dark current removal). 2. Calibration from RAW data to radiance data using calibration file After the dark noise removal, the raw data was calibrated to radiance units using a sensor specific calibration file. Every spatial and spectral pixel is multiplied with the corresponding value in the calibration file. The calibration values for each pixel on the CCD are calculated using an integrating sphere in the laboratory. The radiance units are equal to (mW/cm^2*str*um)*1000.00. 3. Smile Correction Spectral smile is defined as changes in wavelength over the field of view (FOV). Smile correction was performed by proprietary algorithms. 4. Crosstrack Correction A crosstrack correction was performed using proprietary algorithm in order to normalize illumination in the across-track direction of each flight line. 5. Quality Control Quality control was accomplished using ASD measurements, established radiometric quality protocols and systematic manual evaluations. Applied Hyperspectral Imaging Services 25 25 Processing Level 1b – Atmospheric Correction 1. Atmospheric Correction The radiance units were converted to reflectance units using the ASD spectrometer measurements of uniform surfaces (parking lots, asphalt, sand and concrete) that were collected in the field. Multiple spectrometer measurements were taken at each site under clear conditions to ensure data quality. An “empirical line correction” method was used to calibrate every flight line to reflectance. After the correction an adaptive spectral filter was used to smooth the reflectance values and to eliminate outliers and spikes in the spectra. The reflectance units are equal to Reflectance*10000. 2. Quality Control Quality control was accomplished using ASD spectrometer measurements, established atmospheric correction quality protocols and systematic manual evaluations.
- 2018-01-01 00:00:00 - Processing Level 2 – Geometric Correction 1. Calculation of the sensor offset (Boresight correction) During the aerial acquisition, four special Boresight flight lines were flown to geometrically calibrate the sensor and GPS/INS. The Boresight parameters were calculated using four overlapping flight lines flown in a crosshair pattern. 15 to 20 Ground Control Points per flight line pair (GCPs) were identified and used to calculate geometric correction values for Roll (0.162353), Pitch (0.131388) and Yaw (0.166983). These values were then used as input parameters for the geometric correction process. 2. GPS/INS Data The GPS/INS Data was encoded and processed for the use in the georectification process 3. GLT files (Geographic Lookup Table) A GLT file contains the geographic location of every pixel in the unrectified reflectance data. A GLT file was generated for every flight line using the GPS/INS Data, the Boresight Correction parameters and a Digital Elevation Model (DEM) Processing Level 3 – Orthorectification Applied Hyperspectral Imaging Services 26 26 1. Georectification using GLT data The unrectified reflectance data was then Georectified into North American Datum of 1983 (NAD83) and projected into the Universal Transverse Mercator (UTM) coordinate system using the corresponding GLT file. A DEM was used to correct for surface elevation variation across the scene. 2. Mosaicking Individual flight lines for each AOI were combined into a single mosaic image which covered the entire AOI. This image was then masked to the AOI boundary and tiled according to the tiling scheme vectors included with this delivery. 3. Quality Control Geo-accuracy was checked and confirmed to meet pre-established quality standards by systematic comparison of specific geo-locations acquired in the field with a GPS unit and high resolution RGB imagery of known geo-accuracy.
(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.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.3. Data access methods or services offered
- 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.
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.
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.