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
Critical habitat in the Caribbean Sea area includes the waters adjacent to Sandy Point, St. Croix from the 100 fathom curve shoreward to the level of mean high tide.Critical habitat in the Pacific Ocean areas includes marine waters to a depth of 80 meters from the ocean surface and is delineated along the shoreline at the line of extreme low water, except in the case of estuaries and bays where COLREGS lines (defined at 33 CFR part 80) are used as the shoreward boundary. The seaward boundary of the nearshore Washington/Oregon area (from Cape Flattery south to Cape Blanco) is defined along the 2,000 meter isobath. The seaward boundary of the nearshore California area (from Point Arena south to Point Arguello) is defined along the 3,000 meter isobath.
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):
- 2005-07-12 00:00:00 - Detailed shoreline for St. Croix from NOAA digital vector chart was created, then the 100 fathom curve was created by conducting heads-up digitizing of the contour from NOAA chart 25641_1 using ESRI's ArcGIS software. The accuracy of this data set is dependent upon the accuracy of the shoreline and bathymetric data used in the creation process.
- 2006-03-21 00:00:00 - Land area was erased from the buffer area using ET Geowizards. The source of land area used to erase was from the NCCOS project for coral and seafloor mapping.
- 2012-01-26 00:00:00 - Data created for Pacific Ocean 2012. Polygons mapped to add critical habitat for leatherback sea turtles along the west coast (Washington, Oregon, California).
- 2021-04-26 00:00:00 - Merged 2 datasets. During standardization, geometry was not edited for the Caribbean Sea polygon. Geometry was edited for the Pacific Ocean polygons. Attributes were edited. Metadata was edited and populated using the final rule/CFR and the sources: SeaTurtleLeatherback_19790323 (GCS_WGS_84 wkid 4326) and Final_LeatherbackCH.shp (NAD_1983_California_Teale_Albers). Geoprocessing steps: - Projected 2012 Pacific Ocean version Final_LeatherbackCH.shp (NAD_1983_California_Teale_Albers) to WGS84. - Exploded multipart polygon to populate separate attributes for WA/OR polygon and CA polygon. - Deleted 2 very tiny polygons that appeared after explosion, only 2 large polygons remained. - Merged with Caribbean Sea polygon (SeaTurtleLeatherback_19790323) to create the standardized feature class SeaTurtleLeatherback_20120126 (GCS_WGS_84 wkid 4326) using the National Critical Habitat Geodatabase processing protocol. - Migrated fields: none - Dropped fields: FID, NAME, SHAPE_Leng, SHAPE_Area - Caribbean Sea feature class deprecated (SeaTurtleLeatherback_19790323_archived). **Data history - for reference** See final rule map Figure 1 - Geographical Areas Occupied by the species (January 26, 2012, 77 FR 4188). The CFR text describes areas 1 and 7, but the CFR map does not show those boundaries. CFR text (i) matches area 1, (ii) matches area 7. CFR map shows areas 1 and 7 combined into a single polygon (i.e., the 200 meter isobath no longer existed, only the 3,000 meter isobath existed).
(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)
- 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.
St Petersburg, FL
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.