Data Management Plan
GUID: gov.noaa.nmfs.inport:47886 | 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
Data produced for the Florida Fish and Wildlife Conservation Commission's Florida Marine Research Institute (FMRI) in partnership with the South Florida Water Management District (SFWMD). This data set consists of digital data describing the seagrass, unvegetated bottom, open water, algal beds, oysters, and apparent shoreline for the Southwest Florida Seagrass project area,which consists of Pine Island Sound, Matlacha Pass, San Carlos Bay, the lower Caloosahatchee River, and Estero Bay, in 1999. The data set includes an ArcInfo coverage that was digitized from 1:24000 scale natural color aerial photographs that were photogrammetrically georeferenced utilizing GPS ground control points. Data was stereoscopically photointerpreted and digitized using a Zeiss P3 analytical stereoplotter. The seagrass beds and additional categories were classified according to the FDOT Florida Land Use, Cover and Forms Classification System (FLUCCS). Minimum mapping unit (mmu) for all classes was 0.25 acres. A Photointerpretation Key was developed to aid in the classification of collected data. Ground truthing was performed during the photointerpretation phase to ensure classification accuracy and consistency of PI. Digital files were created in Microstation design file format (.dgn). 1999 SWIM Seagrass data was translated from ARC/Info to .dgn format and was referenced as collateral tie information during the compilation process. These data were collected under a cooperative mapping program between the U.S. Geological Survey (USGS), the National Oceanic and Atmospheric Administration Office for Coastal Management (NOAA\OCM), and the Apalachicola National Estuarine Research Reserve (NERR). The primary objectives of this program were to collect marine geophysical data to develop a suite of seafloor maps to better define the extent of oyster habitats, the overall seafloor geology of the bay and provide updated information for management of this resource. In addition to their value for management of the bay's oyster resources, the maps also provide a geologic framework for scientific research and the public.
Original contact information:
Contact Org: NOAA Office for Coastal Management
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):
- 1999-12-01 00:00:00 - Aerial photography data collection. Conventional color film was flown under conditions conducive to mapping submerged habitats. This includes consideration of tidal stage, sun glint, cloud cover, water clarity, and phenology of submersed vegetation. The photography was reviewed for suitability and accepted as the primary data source for the benthic mapping.
- 2000-05-01 00:00:00 - Photointerpretation: From 20000201 to 20000501 data was stereoscopically photointerpreted and digitized from 1:24000 scale natural color aerial photography using a Zeiss P3 analytical stereoplotter. The seagrass beds and additional categories were classified according to the FDOT Florida Land Use, Cover and Forms Classification System (FLUCCS). Minimum mapping unit (mmu) for all classes was 0.25 acres. Ground truthing was performed during the photointerpretation phase to ensure classification accuracy and consistency of PI. Digital files were created in Microstation design file format (.dgn).
- 2000-05-01 00:00:00 - ARC/INFO validation: Microstation .dgn files were imported to ARC/Info to perform automated validation routines. Quality control checks for digital data consisted of unlabeled, multi-labeled and contiguous polygon errors as well as dangles and sliver polygons. Polygon topology was created and label errors and node errors were run in ARC/Info. Coverage characteristics were adhered to, as specified by the contract (tolerances, projection definition, PAT items etc.).
- 2001-11-05 00:00:00 - Field validation from 20011031-20011105 of final products. Following completion of the final benthic habitat map, staff from the NOAA Office for Coastal Management, FMRI, and the Southwest Florida Water Management District conducted a field thematic validation trip to the area to test the accuracy of the map product. A set of random points were generated for field evaluation in ERDAS Imagine. The vector coverage was converted into a classified raster based on thematic polygon values. Fifty stratified random points were generated from each class (continuous SAV, patchy SAV, Oyster, and bare bottom). These points were used to guide the field team. However conditions in the field including 20+ mph winds and extremely shallow water depths prevented the team from visiting the majority of the randomly selected points. Only ten percent of the field points (15 of 166) were from the random point set. Field methods used to validate the 1999 benthic coverage consisted of navigating to the random points using a live GPS link through a field PC. The field party segmented the study area into three zones based on water bodies and access. The zones were: Matlacha Sound, Pine Island Sound, and Estero Bay. The team navigated into these sounds, observing sites along one side and then left the area observing sites on the opposite side. Wind direction and exposure also influenced this process. In addition to navigating to pre-selected points whenever possible, the team would add points. An effort was made to add these points in areas where many polygons were located together. This was done to maximize the number of polygons that could be visited and also address the most complex areas. Upon arriving at a point, or polygon in the case of an added point, the team would deploy the Towed Underwater Video camera and cross into the polygon in a transect fashion. This transect was started such that some video observation of the area outside the polygon boundary could be made. As the transect was traveled, several observations were made along track to confirm the presence or absence of a given habitat. Once a determination could be made about the accuracy of the polygon in that area, the transect was stopped. Agreement between map observations and field observations exceeded 70%. Part of the difference between the two observations was the time elapsed between the time of the aerial photography and the seasonality differences between the two dates.
- 2012-03-28 00:00:00 - Original AGRA Baymont FLUCCS classes were cross-walked into the Florida System for Classifying Habitats in Estuarine and Marine Environments (SCHEME). All surficial geology classes translated smoothly into SCHEME. No information or data records were lost during this process. Geoform attributes not captured in the SCHEME hierarchy have been added as modifiers (ex. tidal inlet).
- 2015-01-01 00:00:00 - The data were converted from a single ESRI polygon shapefile classified according to the System for Classifying Habitats in Estuarine and Marine Environments (SCHEME) to the Coastal and Marine Ecological Classification Standard (CMECS) 2012 format (which can be found at https://coast.noaa.gov/digitalcoast/tools/cmecs-crosswalk) which produces separate geoform, biotic, and biotic feature layers from the original input benthic habitat dataset. This biotic feature layer contains CMECS biotic component attributes where an "Equal" or "Nearly Equal" SCHEME value was present in the original data. Polygons for which no biotic information was present have been removed. No other changes to the original polygon boundaries or any other alterations of the original SCHEME data were made during this process.
(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)
- 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.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.