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 contains the 2005-era and 2007-era classifications of
St. John, United States Virgin Islands and can be used to analyze change.
This data set utilized 14 full or partial ADS40 scenes
which were analyzed according to the Coastal Change Analysis Program (C-CAP)
protocol to determine land cover.
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 - Process_Description This dataset was created by Sanborn. This dataset contains the classifications of 2005-era imagery and 2007- era imagery. It is used for change analysis between these years. The attributes include a from-to change description category. There are 481 classes corresponding to the 481 possible from-to change combinations. In this section of the metadata, the 2005-era classification procedure is described, then the 2007-era change detection classification procedure is described. Finally in the post-processing section, the process of combining the maps to generate a spatial matrix of change is discussed. Early Date (2005-era) Classification: This section outlines the classification procedure for the U.S. Virgin Islands C-CAP product. The IKONOS image tiles utilized for this project were provided by GeoEye as orthorectifed, georeferenced products and were consistent with the quoted 1:12000 spatial accuracy. In conjunction with the IKONOS, Sanborn used LiDAR collected in 2007 for the island. 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. 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. Image segments are classified using a decision tree classifier in See5 software and an iterative nearest neighbor classifier in Definiens software. Nearest neighbor training data is collected through field observations, and analyst photo interpretation/selection. Models are built to refine or reclassify land cover areas by utilizing the wealth of attribute information linked to each segment within Definiens. 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. Sanborn used independent reviewer's comments to further refine the land cover map.
- 2010-05-24 00:00:00 - 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 Ancillary Datasets: Non-IKONOS image datasets used are LiDAR (2 foot point spacing density), DCM (Digital Canopy Model derived from LiDAR), slope, aspect, NWI, NLCD, field-collected points, photo-interpreted points. QA/QC Process: There were several QA/QC steps involved in the creation of this product. There was an internal QA/QC. This was done by viewing the classification frame-by-frame along with the IKONOS imagery, the classification, and high resolution reference imagery. NOAA staff completed a similar review and provided both general and point comments. Late Date (2007-era) Classification: 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 image for the entire island. The early date (2005-era) classification was created first using satellite data because at the time it was the most recent, cloud free imagery available. The late date (2007-era) ADS40 became available shortly after the early date classification was completed. The ADS40 imagery was found to have ortho-rectification accuracy. The 2005-era classifications and imagery were geo-rectified to co-register with the ADS40 imagery. Change Detection: Once the images were aligned, the next step was to determine the areas of change between the 2005-era and 2007-era data. Since the 2005-era classification was already complete, it is only necessary to classify the areas of change to create a 2007-era classification of the same specifications. The 2007 ADS40 imagery was segmented with the 2005 land cover classification as a hard boundary delimter. Logical rulesets and thresholding based on the spectral properties of the imagery 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 draft late date classification. This map was further revised with rulesets and thresholding. The final step before map finalization was to remove inaccuracies through manual segment labeling as interpreted by an analyst. Sanborn used independent reviewer's comments to further refine the land cover map. Post-Processing Steps: A GIS matrix algorithm was run with 2005 and 2007 datasets as inputs. The algorithm generates a from-to file where each combination is uniquely labeled from 1 to 481.
- 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.