Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:61289 | 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 metadata is summer 2016. These maps are developed utilizing high resolution National Agriculture Imagery Program (NAIP) imagery, and can be used to track changes in the landscape through time. The C-CAP program will use addtional image sources such as leaf off or tide controlled low tide imagery if it is available. This trend information gives important feedback to managers on the success or failure of management policies and programs and aid in developing a scientific understanding of the Earth system and its response to natural and human-induced changes. This understanding allows for the prediction of impacts due to these changes and the assessment of their cumulative effects, helping coastal resource managers make more informed regional decisions. NOAA C-CAP is a contributing member to the Multi-Resolution Land Characteristics consortium and C-CAP products are included as the coastal expression of land cover within the National Land Cover Database.
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:
- 2020-08-01 00:00:00 - This dataset was created by NOAA's Ocean Service, Office for Coastal Management (OCM). 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. Impervious Surface refinement: To create an impervious surface class with more spatial detail, 2012 impervious surface data (http://cteco.uconn.edu/projects/ms4/impervious2012.htm) from the UConn Center for Land Use Education and Research (CLEAR) was incorporated into the land cover map. Updates from the random forest classification were isolated and retained through a series of spectral and contextual threshold models. Forest refinement: Forest features from the initial classification were refined using 2016 lidar data (http://cteco.uconn.edu/data/flight2016/index.htm) collected through The Capitol Region Council of Governments. Point clouds were processed into normalized digital surface models to clean up the boundaries between forest, grass and shrub features. Water Refinement: Commission and omission errors associated with the Water class were addressed through manual interpretation and clean up in ERDAS Imagine. Once the review and edits were complete, the refined Water class was incorporated back into the land cover data set.
- 2020-08-01 00:00:00 - Water Refinement: Commission and omission errors associated with the Water class were addressed through manual interpretation and clean up in ERDAS Imagine. Once the review and edits were complete, the refined Water class was incorporated back into the land cover data set. Unconsolidated Shore: Unconsolidated substrate features were extracted primarily through unsupervised classification and manual editing in ERDAS Imagine. This process relied on tide contolled imagery collected by National Geodetic Survey (NGS). Once these features were inserted into the land cover additional object based algorithms were applied to clean up the results. Agriculture: Cultivated land and Pasture/Hay features were mapped from the grassland and bare categories using a Convolutional Neural Network (CNN). The CNN was training using existing high resolution C-CAP data and NAIP imagery available in the region. Predictions made by the CNN were post-processed and inserted into the land cover which was finalized through internal QA and manual editing. Wetlands: Wetlands were derived through a modeling process which used ancillary data such as Soils (SSURGO), the National Wetlands Inventory (NWI) and topographic derivatives. 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. Open Space Developed: Managed grasses and other low lying vegetation associated with development were derived from the grassland category of the draft 2016 land cover through intersections with ancillary vector-based land use data as well as analysis of impervious surface coverage within those land use polygons. Herbaceous land cover areas that intersected select features from the OpenStreetMap landuse and points of interest layers were converted to Open Space Developed. Additionally, parcel features from CoreLogic parcel data were used along with relative area and adjacency thresholds of the impervious surface class to further map the Open Space Developed class. Manual edits were performed to fine tune the classifications.
(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.