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 data represents the extent of the nation's coastal zone, as defined by the individual states and territories under the Coastal Zone Management Act of 1972 (CZMA). The CZMA was established to preserve, protect, develop, and where possible, to restore or enhance the resources of the nation's coastal zone. The zone generally extends seaward to the boundary of the Submerged Lands Act. The zone extends inland from the shorelines only to the extent necessary to control shorelands that have a direct and significant impact on coastal waters. Lands held in trust by the Federal Government have been included in this boundary unless otherwise noted, as accurately representing these could be erroneous. State jurisdiction extends to 3nm, except for Texas, Puerto Rico and Florida’s Gulf coast extends to 9nm. Great Lakes states have jurisdiction to the international boundary with Canada. CZMA applies in EEZ through federal consistency. This boundary is unofficial. For precise, regulatory boundaries, please contact the state or territorial coastal program office.
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-07-01 00:00:00 - To account for federal consistency rules, added geography to account for 200NM Exclusive Economic Zone (EEZ) boundary: 1. Using the National Environmental Policy Act boundary which has the EEZ represented, union data to CZMA data created in above processing step. 2. Explode features from multipart to singlepart. 3. Copy all EEZ features adjoining the CZMA boundary (around Atlantic, Gulf of Mexico, Puerto Rico, and Hawaii) into CZMA data. 4. Add "Notes" field. 5. For Notes field for EEZ features, calculate fields to add this note: "Applies to Exclusive Economic Zone through federal consistency pursuant to NOAA's CZMA regulations at 15 C.F.R. Part 930." 6. Display geometry for CZMA features as a solid fill with no outline, display geometry for the EEZ features as an empty fill with a solid outline. Create layer file. 7. Check geometry and project data into WGS 1984 Auxiliary Sphere
- 2018-06-01 00:00:00 - 1) Download data from each state source 2) Project all shapefiles into NAD 83 and import into a file geodatabase 3) The following state coastal zones include the entire state: Delaware, Florida, Hawaii and Rhode Island 4) The following state coastal zones include a 3 nautical mile buffer: CNMI, Guam, USVI (the download files for American Samoa and Hawaii include this in the download) 5) Puerto Rico’s coastal zone includes a 9 nautical mile buffer 6) For all other states, merge into a single feature class 7) Union this feature class with no gaps allowed and review all features to delete any slivers in the data and merge overlapping areas 8) For features on the east coast, west coast and Gulf of Mexico extend the areas to the accompanying SLA boundary and clip any area beyond 9) For features on the Great Lakes, extend the areas to the USA/Canada border and clip any area beyond 10) Merge all feature classes into a single layer and explode any multipart features 11) Delete all superfluous fields 12) 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.
- 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.
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.