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 set consists of land cover derived from high resolution imagery and was analyzed according to the Coastal Change Analysis Program (C-CAP) protocol to determine land cover. This data set utilized 32
three-band ADS40 scenes. These full scenes were not sufficient to replace cloud obscured areas within the base imagery. Additional imagery was used for classifying obsucred areas. All scenes were processed to detect C-CAP land cover features on St Thomas, U.S. Virgin Islands.
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):
- 2010-05-24 00:00:00 - This dataset was created by Sanborn (www.sanborn.com). This version of the classification is the High Resolution Land Cover (2007-era) for the Island of St Thomas, United States Virgin Islands. This section outlines the classification procedure for St Thomas, United States Virgin Islands High Resolution C-CAP. ADS40 imagery and the 2003-era C-CAP classification were used in producing this land cover product. The mapping approach utilized a boundary summary and refinement procedure developed by Sanborn to leverage the 2003-era classification. A calibration visit was conducted and training data was collected for classification. Non impervious features were mapped using a 0.5 acre minimum mapping unit (MMU). Pre-processing steps: The ADS40 was provided to Sanborn as a geo-referenced product. Sanborn perfomed a quality control on the imagery to check for pixel dropouts and other image issues. Individual image tiles were combined to create a single mosaic for the entire island. In conjunction with the ADS40 mosaic, Sanborn used Quickbird collected from 2002-2005 and LiDAR collected in 2007 for the island. Field-Collected Data: Training data was collected in the field between May 31th and June 5th, 2009. Land cover observations were recorded by analysts. The referenced dataset went through a QA/QC procedure to ensure it met accuracy standards. Classification: Segmentation - Image segmentation was completed at multiple scales using the multispectral (2.4 m) imagery in order to group like spectral and textural objects within the imagery. For consistency, the associated impervious data set was incorporated into the segmentation layer as a boundary delimiter. Segments can share boundaries of an impervious surface, but can never overlap an impervious surface. Automated Classification - Logical rulesets and thresholding based on the spectral properties of the imagery, and ancillary data, and the early date classification were used to generate a mask of potential change. The change mask was incorporated into the early date classification to create the 2007 classification. Automated Classification Refinement - Models are built to refine or reclassify land cover areas by utilizing the wealth of attribute information linked to each segment within Definiens. Classification Edits - As with any automated or semi-automated land cover classification there are often inconsistencies in the land cover map. The final step before map finalization was to remove inaccuracies through manual segment labeling as interpreted by an analyst. Map Finalization - Sanborn used independent reviewer's comments to further refine the land cover map. Attributes for this product are as follows: 0 Background 1 Unclassified 2 Impervious 3 4 5 Developed, Open Space 6 Cultivated Crops 7 Pasture/Hay 8 Grassland/Herbaceous 9 Deciduous Forest 10 Evergreen Forest 11 Mixed Forest 12 Scrub/Shrub 13 Palustrine Forested Wetland 14 Palustrine Scrub/Shrub Wetland 15 Palustrine Emergent Wetland 16 Estuarine Forested Wetland 17 Estuarine Scrub/Shrub Wetland 18 Estuarine Emergent Wetland 19 Unconsolidated Shore 20 Bare Land 21 Open Water 22 Palustrine Aquatic Bed 23 Estuarine Aquatic Bed 24 Tundra 25 Snow/Ice
- 2010-05-24 00:00:00 - Metadata imported
(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.