Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:79752 | Published / External
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. For more information, consult the help guides on the new Data Management Plan as well as how to convert this Legacy DMP to the new format.
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 through time. High resolution C-CAP products are developed utilizing high resolution aerial imagery, along with lidar and various available ancillary information, and can be used to track changes in the landscape through time. This is a full-scheme C-CAP land cover product, which includes up to 20 land cover classes, including impervious surfaces, agricultural areas, tree/shrub canopy, water, and wetlands. These high-resolution C-CAP land cover products enable local mapping and analyses for several applications, including water quality and stormwater management, land use planning and community development, risk assessment, natural resource management, and other community-level activities. This dataset represents land cover for the timeframe of 2021 for the Northeast Region of Ohio.
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:
- 2026-04-28 00:00:00 - This dataset was created as part of NOAA's Coastal Change Analysis Program (C-CAP), which is housed within the National Ocean Service, Office for Coastal Management (OCM). Contractor work was performed through NOAAâs Coastal Geospatial Services Contract (CGSC) vehicle. Initial Classification Initial 1m spatial resolution feature extraction for Impervious, Water, and Canopy (tree and scrub/shrub) mapping was conducted by Ecopia AI (https://www.ecopiatech.com/) using a proprietary feature recognition technology. This involves taking each image and classifying the pixels based on spectral and spatial properties, based on training examples and analyst refinement. Refined Classification The refinement of initial mapping layers, including the additional of up to 20 standard C-CAP categories of land cover feature types was conducted by NV5 (https://www.nv5.com/). Refinement specifics were broken down into a series of stages, and the specifics of each are discussed below. Impervious Surface Refinement: Commission and omission errors associated with the Impervious class were addressed through manual interpretation and clean up using OpenStreetMap road, building, and railroad layers as reference. Once the review and edits were complete, the refined Impervious class was incorporated back into the land cover data set. Water Refinement: Commission and omission errors associated with the Water class were addressed through a combination of modeling, expert rulesets, and manual interpretation. Once the review and edits were complete, the refined Water class was incorporated back into the land cover data set. Canopy Surface Refinement: Commission and omission errors associated with the Canopy class were addressed through manual interpretation and clean up. Once the review and edits were complete, the refined Canopy class was incorporated back into the land cover data set. Agriculture and Open Space Developed: Cultivated land, Pasture/Hay, and Open Space Developed features were derived from the grassland class of the initial land cover product using a combination of deep learning and image segmentation approaches. Predictions from a Convolutional Neural Network were summarized by image objects generated for grassland regions withing the AOI. Commission and omission errors associated with these categories were addressed through manual review and editing. Once the review and edits were complete, the new classes were incorporated into the land cover data set. Wetlands: Wetlands were derived through a modeling process which used ancillary data such as Soils (SSURGO), the National Wetlands Inventory (NWI), and topographic derivatives (derived from USGS OPR data). 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. Grass and Bare: Grass and Bare classifications were extracted from regions within the AOI not covered by the Ecopia AI Impervious, Water, and Canopy layer. This was accomplished through a combination of image segmentation, expert rulesets, and manual editing. Once the review and edits were complete, Bare and Grass features were incorporated into the land cover data set. Attributes for this product are as follows: 0 Background 1 Unclassified 2 Developed Impervious 3 4 Developed Impervious under Tree Canopy 5 Developed, Open Space 6 Cultivated Crops 7 Pasture/Hay 8 Grassland/Herbaceous 9 10 11 Upland Tree (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
(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.
