Data Management Plan
GUID: gov.noaa.nmfs.inport:57239 | 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
These data represent an inventory of the national impacts of wind turbine interference with NEXRAD radar stations. This inventory was developed by the NOAA Radar Operations Center (ROC) to establish variable zones that delineate the possible impacts that wind turbines may have on radar operations. The inventory scheme includes four zones that take in to account terrain, distance, and the number of elevation angles impacted. ROC requests various degrees of consultation with the developer depending on the zone. No Build - No wind turbines permitted Mitigation Zone - Significant impacts likely Consultation Zone - Significant impacts possible Notification Zone - Impacts not likely
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:
- 2015-07-01 00:00:00 - 1) Original source data was provided by NOAA Radar Operations Center 2) Import 4 shapefiles into a file geodatabase 3) Project 4 feature classes into NAD83 4) Update attribute names to siteID and siteName 5) Add impactZone field to each feature class 6) Populate the fields so that GREEN = Notification Zone, YELLOW = Consultation Zone, ORANGE = Mitigation Zone and RED = No Build Zone 7) Dissolve each feature class based on siteID, siteName, and impactZone, unselecting multi-part features 8) Integrate each feature class at 1 foot tolerance to clean up most of the slivers in the data 9) Dissolve each feature class again based on siteID, siteName, and impactZone, unselecting multi-part features 10) Erase RED from ORANGE and Merge the new hollow ORANGE with RED 11) Union this new ORANGE-RED, and split and merge overlaps in the Mitigation Zone only 12) Erase the new ORANGE-RED from YELLOW and Merge the new hollow YELLOW with ORANGE-RED 13) Union this new YELLOW-ORANGE-RED, and split and merge overlaps in the Consultation Zone only 14) Erase the new YELLOW-ORANGE-RED from GREEN and Merge the new hollow GREEN with YELLOW-ORANGE-RED 15) Union this new GREEN-YELLOW-ORANGE-RED, and split and merge overlaps in the Notification Zone only 16) Delete from the No Build Zone features: Camp Humphreys, Kadena AB, Kunsan AB, Lajes AB and Langley Hill 17) Select by Attributes where siteID = 'PAHG', and populate so that all features have siteName = 'Kenai FAA (RDA1)' 18) Integrate new feature class at 20 feet tolerance to further clean up data slivers 19) Check geometry and project data into WGS 1984 Auxiliary Sphere
(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)
- 2.1. Point of Contact Name
- 2.4. Point of Contact Email
- 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.2. Name of organization of facility providing data access
- 7.2.1. If data hosting service is needed, please indicate
- 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.2. Data storage facility prior to being sent to an archive facility
- 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.
Charleston, SC
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.