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 the location of Danger Zones and Restricted Areas within coastal and marine waters, as outlined by the Code of Federal Regulations (CFR) and the Raster Navigational Charts (RNC). The CFR defines a Danger Zone as, "A defined water area (or areas) used for target practice, bombing, rocket firing or other especially hazardous operations, normally for the armed forces. The danger zones may be closed to the public on a full-time or intermittent basis, as stated in the regulations." The CFR defines a Restricted Area as, "A defined water area for the purpose of prohibiting or limiting public access to the area. Restricted areas generally provide security for Government property and/or protection to the public from the risks of damage or injury arising from the Government's use of that area." Other features in this dataset include: Danger Area, Missile Testing Area, Naval Operations Area, Prohibited Area, Restricted Airspace, Test Area, and Torpedo Testing Area. Authoritative information relating to these data may be found in Title 33, Chapter II of the CFR (Part 334).
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):
- 2014-01-01 00:00:00 - 1. Acquired list of Danger Zones and Restricted Areas (DZRAs) from the CFR (Title 33, Chapter 2, Volume 3, Section 334). 2. Created labeled points in ArcMap (XY tool) based on CFR coordinates. Converted these points (graphics) to features, per CFR feature (DRAWING...CONVERT GRAPHICS TO FEATURES). 3. If points projected in NAD83 appeared to be off significantly compared to the RNCs, the points were projected to determine the intended coordinate system. (The CFR did not explicitly provide the datum, but for a couple features.) 4. For features in which no coordinate system could be identified, Global Mapper was used to project the points in the intended coordinate system, and export them as NAD83. This yielded results that placed the coordinates in significantly closer proximity to that of the charted feature. (It was determined to be a bug with Esri's NADCON transformation.) 5. Created a new polygon feature class to generate geometry from the points. 6. Added necessary fields to feature class (populated as necessary during creation of features). 7. Within the new polygon feature class, used a) point features (coordinates) generated, b) CFR language, c) Raster Nautical Charts (RNCs), and d) shorelines to create geometry. 8. Populated any remaining attributes after geometry was completed. 9. Created metadata. 10. Cross-referenced RNCs to check geometry and reconciled any differences between CFR and RNC where necessary.
- 2015-06-01 00:00:00 - 1. Acquired current national geometry from internal directory. 2. Created new geometry for select features, derived from the Code of Federal Regulations (2014), the Raster Navigational Charts, and data provided by NASA for areas off the coast of Virginia. Features were created using language and coordinates from the CFR or geometry from the RNC, then made coincident with the shoreline. The two areas provided by NASA were not made coincident with the shoreline. 3. Populated attribute fields for new features.
- 2016-01-01 00:00:00 - 1. Acquired latest version of the Danger Zone and Restricted Areas from MarineCadastre.gov data registry. 2. Acquired the latest version (2015) of the Code of Federal Regulations (CFR). 3. Based on differences between the 2012 and 2015 Code of Federal Regulations, created geometry for new features and removed expired features. New features were made coincident with the NOAA 1:80,000 shoreline. 4. Populated attribute fields for new and existing features, based on 2015 CFR.
- 2017-01-01 00:00:00 - 1. Acquired latest version of the Danger Zone and Restricted Areas from the MarineCadastre.gov data registry. 2. Acquired the latest version (2017) of the Code of Federal Regulations (CFR). 3. Performed a 1:1 inspection of every feature in the published data set, with those features found on the Raster Nautical Charts. For features that varied noticeably from the nautical charts, language and coordinates from the latest CFR (2017) were used to confirm if the geometry was correct. For the few that were noted as deviating from both the RNC features and CFR descriptions, new geometry was created to update the data set. Also, geometry for new features found in the RNCs or 2017 CFR was created and added to the data set. Attributes were updated accordingly. 4. Changed symbology to more closely resemble the Raster Navigational Charts.
- 2022-10-01 00:00:00 - 1. Acquired latest version of the Danger Zone and Restricted Areas from the MarineCadastre.gov data registry. 2. Acquired the latest version (2022) of the Code of Federal Regulations (CFR). 3. Performed a 1:1 inspection of every feature in the published data set, with those features found in the CFR, to confirm which features should be removed or added. 4. The geometry for some circular features in the previous data set were corrected and Repair Geometry was run. 5. Attributes were updated accordingly and special characters were removed.
(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)
- 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.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.