Data Management Plan
GUID: gov.noaa.nmfs.inport:25853 | Published / External
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 the critical habitat for Johnson's Seagrass as designated by Federal Register Vol. 65, No. 66, Wednesday, April 5, 2000, Rules and Regulations.
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.
4. Resources
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):
Process Steps:
- 2011/2012 edits to shapefile: (a) Indian River north Sebastian Inlet: I recreated the polygon according to eCFR 50 CFR 226.213 in 2007. (b) Indian River south Sebastian Inlet: OK (c) Indian River Lagoon - Fort Pierce inlet: OK (d) Indian River Lagoon - St. Lucie Inlet: I included the ICW in the shapefile, and created one solid polygon. I also redigitized the eastern side along the shoreline using Bing Maps as a background in ArcMap. (e) Hobe Sound: The coordinate in the FR is suppose to be at SR 708, but looking at Bing Maps, it is to the south. I edited the shapefile to continue north to SR 708. I also made one big poly that does not depict the ICW exclusion. The polygon shorelines were also edited to follow the Bing Maps background. (f) Jupiter Inlet: I digitized a boundary that followed the shoreline (again, employing heads-up digitizing techniques using Bing Maps). (g) Lake Worth: the original shapefile had a 4 vertice polygon that approximated the shoreline on the south side. I digitized the shoreline along the south side using Bing Maps as a guide. (h) Lake Worth Lagoon - Boynton Inlet: I edited the polygon to go all the way to the coordinates (the shape file does not exclude the ICW). I also redigitized the western edge to follow the Bing Maps shoreline. (i) Lake Wyman: The original shapefile excluded the ICW, so I redigitized the polygon to extend to the published coordinates. This unit did not follow the shoreline on the eastern side, so I redigitized it to follow the Bing Maps shoreline. (j) A portion of Northern Biscayne Bay, FL: I received a new Biscayne Bay Aquatic Preserve boundary from Florida DEP, Bureau of Survey and Mapping, Division of State Lands (rev. 2010). The boundary is from Section 258.39 (11) Florida Statutes, and Section 258.397. They send me the exterior boundary for the AP. They said that the law for the boundary has not changed, but the boundary is more accurate now. If there are questions about specific sites within the boundary, contact the Title and Land Records Section of the Bureau of Survey and Mapping Division of State Lands (850)245-2788.
- 2003-11-14 00:00:00 - A point layer was created using the coordinates in the Federal Register. Those points were then used to digitize polygons. The polygons were then "clipped" to a detailed shoreline (cb24_det.e00) obtained from St. John's River Water Management District (SJRWMD). Following the clip operation, microstation design files of the ICW and Miami Harbor navigation channels were obtained from the US Army Corps of Engineers (USACE) and converted to shapefiles. The final ICW shapefile was created by using a 62.5ft buffer on either side of the centerline and editing that buffer file to match the widening areas in the vicinity of the critical habitat areas. The final Miami Harbor shapefile was created by digitizing a polygon over the channel edge line work in the design file. An Edit Clip was then performed to "punch a hole" through the Critical Habitat areas where they intersected the ICW and the Miami Harbor navigation channel, thus excluding the federally authorized navigation channels from the Critical Habitat areas. Finally, the data in the vicinity of Miami Harbor in Biscayne Bay were edited visually to correspond to the paper maps in the federal register document. Additionally, all data used were reprojected to match the detailed shoreline. (UTM Zone 17, NAD 83, HARN)
(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.
Missing/invalid information:
- 1.7. Data collection method(s)
- 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.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.
None
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.