Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:57099 | Published / External
This is an outdated version of the NOAA Data Management Plan template. InPort now supports a dedicated Data Management Plan Catalog Item type, which is up-to-date with the latest NOAA DMP template. The ability to generate Data Management Plans from Data Sets will be discontinued in a future release. Please see the Data Management Plan Help Guide to learn more.
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
The NOAA Coastal Change Analysis Program (C-CAP) produces national standardized land cover and change products for the coastal regions of the U.S. C-CAP products inventory coastal intertidal areas, wetlands, and adjacent uplands with the goal of monitoring changes in these habitats. The timeframe for this data is 2015, 2016, or 2017 (depending on the exact date of imagery used). These maps are developed through the automated classification of high resolution National Agriculture Imagery Program (NAIP) imagery, available Lidar digital elevation data, and assorted ancillary information.
While produced as part of the Coastal Change Analysis Program (C-CAP), these products should not be compared directly to past dates of 30-meter C-CAP to identify change, as there will be vast differences caused by the different methods and the classes mapped.
These data should be considered to be BETA-level or draft products. They are based on 1-meter land cover mapping that were entirely automated and the relationship of those data to existing wetlands data. As such, there may be issues that result from the different vintages of these products, as well as the errors included in each. While not perfect, the data should provide an example of what level of detail would be possible through such higher-resolution mapping.
These data are not jurisdictional or intended for use in litigation. NOAA does not assume liability for any damages or misrepresentations caused by inaccuracies in the data, or as a result of the data used on a particular system. NOAA makes no warranty, expressed or implied, nor does the fact of distribution constitute such a warranty.
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:
- 2018-11-01 00:00:00 - This dataset was created by NOAA's Ocean Service, Office for Coastal Management (OCM). Process_Description: This dataset was created by the NOAA National Ocean Service (NOS), Office for Coastal Management (OCM). It was based on a 6 category land cover that was produced using a random forest classifier and Geographic Object-Based Image Analysis (GEOBIA) processing framework. That classification was performed by EarthDefine LLC (under contract to NOAA OCM), as part of NOAA’s Coastal Change Analysis Program (C-CAP) efforts. This classification is based on high resolution National Agriculture Imagery Program (NAIP) imagery, available Lidar digital elevation data, and assorted ancillary information. The resulting land cover was then combined with U.S. Fish and Wildlife Servie’s (USFWS) National Wetland Inventory (NWI) data, using a logic based rule set. The final classification includes up to 15 categories. Random Forest Classification: The initial 1m spatial resolution 6 class high resolution land cover product was developed using a Geographic Object-Based Image Analysis (GEOBIA) processing framework. This involves taking each image to be classified and grouping the pixels based on spectral and spatial properties into regions of homogeneity called objects. The resulting objects are the primary units for analysis. Additionally, these objects introduce additional spectral, shape, textural and contextual information into the mapping process and are utilized as independent variables in a supervised classification. Each object is labeled using a Random Forest Classifier which is ensemble version of a Decision Tree. Training data for the initial 6 classes (Herbaceous, Bare, Impervious, Water, Forest and Shrub) were generated through photo interpretation. The resulting Random Forest model was applied to the input data sets to create the initial automated map. Resampling: The resulting 1-meter land cover was then resampled to a 10-meter raster. This was done using a 10x10 focal pixel window to compute the percent value for each land cover type in the 100 pixel neighborhood around each target pixel, and subsequently performing a nearest neighbor resampling of the resulting values. Land cover was then assembled based on the land cover category that represented the largest overall percentage of the output 10-meter cell (i.e. the majority cover type), except where values of impervious exceeded 20% in which case Impervious Developed would be forced into the classification (even if not the majority for that cell). Wetlands: Wetlands were derived through a modeling process which used the National Wetlands Inventory (NWI), exported to a 10-meter raster grid to a classification that matched the wetland categories typically included within C-CAP land cover products. A logic based rule set was then applied. This rule set accounted for changes in condition of wetland features, since the NWI mapping occurred. This was based on how those features were mapped in the 6 category land cover described above, as compared to the NWI class. Forest, shrub and grassland objects within the initial land cover that exhibited hydric characteristics based on the input ancillary layers were designated to their appropriate wetland category. The process relied mainly on the NWI to determine palustrine and estuarine distinctions.
(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.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.