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. The project area extends from the river's mouth to RM 145 below the Bonneville Dam and from the Columbia River to the historic floodplain boundary. This dataset was developed through a collaboration between the Lower Columbia River Estuary Partnership and the NOAA Office for Coastal Management.
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-07-16 00:00:00 - This dataset was created by Sanborn (www.sanborn.com)and NOAA OCM. This version of the classification is the High Resolution Land Cover (2009-era) for the Lower Columbia River. Summary: This section outlines the classification procedure for the Lower Columbia River High Resolution C-CAP. This product was developed through a partnership between the Lower Columbia River Estuary Partnership (LCREP) and the NOAA Office for Coastal Management. The development process occurred in 2 phases. During Phase 1, Sanborn Solutions created a land cover dataset for the lower Columbia River estuary with an emphasis on estuarine and freshwater vegetation and habitats using classification scheme developed specifically for the needs of LCREP. NOAA OCM provided technical assistance and quality assurance services to LCREP and Sanborn. During Phase 2, NOAA OCM took LCREP's final product and retrofitted for addition to the high resolution C-CAP product line. The product was derived from high resolution 4 band digital imagery in combination with LiDAR elevation data. In addition to the primary data sources, many supporting datasets such as archived Landsat imagery, the NWI and a Hydrologic Influence Layer, were used to enhance the classification. The mapping methodology employed an object oriented (image segmentation) approach. Phase 1: The land cover data was generated via object oriented classification. Field data collection was performed by SWCA Environmental Consultants. Image objects (segments) formed the base unit for field data collection and analysis. Sanborn performed an initial automated classification using Classification and Regression Tree (CART) analysis. Additional modeling was performed at the segment level using eCognition. Features that could not be captured successfully through CART or Spatial Models were addressed through manual editing. The final MMU was 0.25 acres. Attributes for the LCREP product are as follows: 10 Coniferous Upland Forest; 11 Deciduous Upland Forest; 21 Coniferous Wetland Forest; 22 Deciduous wetland forest; 40 Upland Shrub-Scrub; 41 Wetland Shrub-Scrub; 50 Upland Herbaceous; 51 Wetland herbaceous; 60 Aquatic Bed; 70 Agriculture; 71 Tree farms; 80 Bare; 81 Mud; 82 Sand; 84 Rock; 90 Urban Impervious; 91 Open Space Developed; 93 Water Phase 2: NOAA OCM utilized the source imagery and the LCREP product to create a High Resolution C-CAP dataset. This involved several steps. 1)Impervious surfaces and Open Spaced Developed were remapped to finer minimum mapping unit (MMU). This involved resegmenting to a finer scale and applying threshold models. The impervious MMU was refined to 0.05 acres. 2)LCREP classes were crosswalked and/or consolidated to C-CAP classes. 3) Modeling in eCognition and Manual edits were applied to LCREP categories that did not exhibit a direct crosswalk. The map maintains a 0.25 acre MMU for non-impervious classes. Attributes for the final C-CAP 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
- 2010-07-16 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.3. Is this a one-time data collection, or an ongoing series of measurements?
- 1.4. Actual or planned temporal coverage of the data
- 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.