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
This database shows the location of publicly owned treatment works, and other significant point source discharges to surface waters at or near the contiguous U.S. coastline. Three types of features are provided in this database; facility location, outfall pipes, and the outfall discharge point. Outfall pipes and discharge points may not be present for some facilities due to a lack of source data. A facility can be linked to its outfall pipe, discharge point and other National Pollution Discharge Elimination System records using the provided key field.
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):
- Subject matter experts from the NOAA National Centers for Coastal Ocean Science, and the NOAA Office for Coastal Management conducted two pilot studies to evaluate data sources and to inform the design of the proposed data product. These pilots were shared with peers to elicit input on the final data product design.
- Outfall Pipes: All data source that could contain a pipeline feature were reviewed, pipeline feature were aggregated, cleaned and flagged with a unique identifier (PGM_SYS_ID) of the coincident facility. Pipeline positions were verified when visible in orthoimagery. Visually verifiable features were retained and superseded any record originating from the ENC and RNC sources. Any ENC or RNC feature that exhibited a break, edge of data offset, or duplicate was edited manually in ArcGIS to repair or remove the error.
- 2021-01-01 00:00:00 - Facilities: Through visual inspection, facilities were removed from the source data if they were outside of the vicinity of the coast and the immediate navigable waterways. Duplicate facility records were removed. Facilities that could not be defined as Publicly Owned Treatment Works, or as another significant contributor were removed. Facility locations were adjusted when their location was clearly in error.
- Outfall: For each facility an attempt was made to identify the primary outfall location if it discharged into surface waters. Source data for an outfall location included examples such as; EPA FRS records, permits, NOAA RNC, and the end of an outfall pipeline. Generally only one outfall was mapped per facility. Each outfall point feature was flagged with an identifier (PGM_SYS_ID) that links it to the relevant facility and pipe.
- Quality control testing for completeness, accuracy, and representativeness was conducted by personnel not directly involved in the hands-on development and editing of the data.
- 2022-08-08 00:00:00 - An update was made to the MWRA outfall pipe location and the MWRA outfall location with the EPA FRS Registry Identifier = 110025247720. The source of the update was Raster Nautical Chart 13270, Edition 66, 2018-12-01, compiled at a scale ratio of 1 to 25,000. This supersedes the previous record which was sourced from Raster Nautical Chart 13267, Edition 37, 2019-09-01, compiled at a scale ratio of 1 to 80,000.
(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.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.
North 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.