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 state geographic location descriptions (GLDs). Section 307 of the Coastal Zone Management Act of 1972, called the "federal consistency" provision, provides states with review authority of federal actions in areas outside of the state coastal zone, which they otherwise would not have, for activities that may affect a state's coastal uses or resources. Federal license or permit, and federal financial assistance activities that are listed in state coastal management programs for an accompanying GLD are subject to state review. All listings and GLDs must be approved by NOAA.
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):
- 2017-01-01 00:00:00 - 1. Data sets for Oregon, Rhode Island, and New York provided by the respective state. These data sets were used as provided, except as noted below for Rhode Island. 2. For Connecticut: NMFS Statistical Areas: extracted the six respective areas from the "Statistical_Areas_2010_withNames" shapefile. Long Island Sound: Extracted the 12m bathy contour (40ft. equivalent) and manually closed the line (between 10m and 14m contours). Extracted the 6m bathy contour (20ft. equivalent) and manually closed the line (between 4m and 8m contours). Used RNCs to create these contours in far eastern Long Island Sound, where the LIS contours in the source data were not included. Off of Montauk Point (eastern point of Long Island), the 12m contour was extended to the New York-Rhode Island border by a line extending from the furthest point east of the 12m contour, to the New York-Connecticut boundary, following a bearing generally parallel to the New York state boundary that exists to the south of Long Island. Fishers Island Sound: the geometry (in New York waters) was extracted from the "NAMED_WATERBODY_POLY" shapefile. Byram River: the geometry (in New York waters) was extracted from the "pwl" shapefile, excluding Kirby Pond. Little Narraganset Bay: the geometry (in Rhode Island Waters) was extracted from the Connecticut state boundary and the Rhode Island shoreline. Connecticut River: used Massachusettss "CENSUS2010HYDRO_SHP" feature class and manually extracted the river (below the dam in Holyoke, MA). 3. For Delaware, acquired supporting maps illustrating the GLD, via email from Delaware CMP. Using these maps and textual descriptions, extracted the necessary offshore lease blocks for the federal waters portion of the GLD. Clipped the seaward extent of these lease blocks with the 24NM line. The remainder of the offshore alternative energy portions of the GLD (in state waters) were extracted using a combination of the Submerged Lands Act's seaward boundary, a national shoreline, the OCS Administrative Boundaries, and COLREGS demarcation lines. The segments of the Delaware River/Bay were constructed using a combination of official state boundaries, maintained channels in Delaware Bay, a boundary of the Delaware Bay (excluding tributaries) from the New Jersey Department of GIS, and the RNCs (i.e. Commodore Barry Bridge). The non-native shellfish segment in the Chesapeake Bay was extracted from a combination of official state boundaries, a national shoreline, and COLREGS demarcation lines. Used centerline of the navigation channel in Delaware Bay to establish the Delaware-New Jersey boundary necessary for the creation of the GLDs for both states. This was suggested by Delaware, since no official boundary between these states in Delaware Bay had ever been agreed upon. 4. For New Jersey, the segments of the Delaware River/Bay were constructed using a combination of official state boundaries, a national shoreline, and COLREGS demarcation lines. Used centerline of the navigation channel in Delaware Bay to establish the Delaware-New Jersey boundary necessary for the creation of the GLDs for both states. This was suggested by Delaware, since no official boundary between these states in Delaware Bay had ever been agreed upon. 5. For Pennsylvania, the boundary was constructed using a combination of official state boundaries, a state of Ohio shoreline, and Office for Coast Survey's US-Canada border. The western portion of the boundary was constructed using a line that was parallel to the Pennsylvania-Ohio border at the origin of the GLD's southeast boundary. 6. For Rhode Island, erased the Ocean SAMP boundary with the Submerged Lands Act (SLA) seaward boundary, as directed by the state CRMC office. 7. For Texas, the Western GOM and Central GOM "BOEM Oil and Gas Planning Areas" features were extracted. These constitute the limit of the Texas GLD, as confirmed by the Texas General Land Office. 8. Added fields and populated according to data dictionary
- 2019-06-13 00:00:00 - 1. Download amended Rhode Island shapefile from NROC and the national GLD layer from Marine Cadastre. 2. Merge amended GLD to the national data set and populate attributes based on information for the Rhode Island CRMC. 3. Update metadata.
- 2022-04-01 00:00:00 - 1. Modified field names to better reflect the content per field. 2. Modified the symbology to illustrate state jurisdiction per feature.
(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.