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 geographic terms used within the Clean Water Act (CWA). The CWA establishes the basic structure for regulating the addition of pollutants (discharges) into waters of the United States, a three mile territorial sea, a 12 mile contiguous zone, and the ocean. The goal of the CWA is to restore and maintain the chemical, physical, and biological integrity of the Nation's waters. This data includes two component boundaries, which delineate the seaward extent of various parts of the CWA. The boundary of a three mile territorial sea and 12 mile contiguous zone are relevant to application of various discharge standards associated with vessels or other floating craft, that vary depending on operational status. As referenced within the CWA, these two boundaries are based on the 1958 Convention on the Territorial Sea and the Contiguous Zone, and not the contemporary extent of these respective boundaries. While the Exclusive Economic Zone (EEZ) is not specified with the CWA, it is denoted here for illustrative purposes. The CWA does not include inland waters because 1) it is difficult to properly identify the nationwide extent of all inland water bodies, and 2) there is current litigation with EPA of such water bodies falling under the jurisdiction of the CWA. When investigating geo-regulatory boundaries near the boundary edges, users should consult the most up-to-date applicable jurisdictional boundaries from all respective authoritative sources.
Date enacted: April 30, 1948
Codification: 33 U.S.C. Sec. 1251 et seq.
Authority: U.S. Environmental Protection Agency
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):
- 2016-01-01 00:00:00 - 1. Acquired national shoreline/s from authoritative sources (NOAA, BOEM, and NGA) to use as the inland extent of the Clean Water Act (CWA) boundary. 2. Acquired international borders (Canada and Mexico) from authoritative sources (OCS and USGS, respectively). 3. Acquired the seaward Clean Water Act line work (OCS 3nm line, Territorial Sea, Exclusive Economic Zone) from NOAA OCS and NOAA OCM. Acquired NOAA 3nm line work from OCS (via email) for entire nation and territories. The Territorial Sea was extracted from the OCS Maritime Boundaries and Limits data. The Exclusive Economic Zone was derived from the Energy Policy Act boundary via MarineCadatsre.gov. 4. Created a national polygon shoreline, using the various shoreline sources and international borders. This was used as the landward extent of the CWA boundary. (NOTE: in northeast Alaska, the BOEM shoreline and OCS international boundary did not intersect. Used the NGA shoreline to close the small gap between these two sources.) 5. The seaward extent of the CWA boundary was generated using three marine boundaries: OCS 3nm line, Territorial Sea, and EEZ. Special notes on generating these boundaries are as follows: 6. Small gaps in the line work for the Territorial Sea were corrected. These (six) gaps were located in Alaska and Louisiana, and were closed by creating a straight line between the two end nodes. 7. In a few places in Maine and Alaska, OCS 3nm line was extended, where it was needed to intersect with the EEZ and Territorial Sea. This was performed by extending the line parallel to the bearing of the line at its terminus. Generally, these extensions were very short - usually less than 5 feet. Similarly, the Territorial Sea line was extended offshore of Texas, where it did not extend far enough south to intersect the EEZ boundary. 8. Territorial Sea line was extended offshore of Washington state by following the line of the state's Coastal Zone Management Act boundary. In Washington state, the Territorial Sea line intentionally ends miles short of and does not intersect with the EEZ boundary. 9. Three small gaps (about 1-4nm in length) in the OCS 3nm line work were noted in southeast Alaska (all on the eastern side of chart 17320). These were manually closed using the BOEM Submerged Lands Act boundary. 10. Visually inspected boundary extents to make sure they were coincident to respective data source boundaries. 11. Combined all three component marine boundaries (i.e. OCS 3nm line, Territorial Sea, Exclusive Economic Zone) into one layer. 12. Added fields and populated according to data dictionary.
(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)
- 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.