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 vector lines and polygons representing the shoreline and coastal habitats of the Aleutian Islands classified according to the Environmental Sensitivity Index (ESI) classification system.This data set comprises a portion of the ESI data for Aleutians East Borough and Aleutians West Coastal Resource Service Area (CRSA). These data identify the marine and coastal environments and wildlife. The ESI data include information for three main components: shoreline habitats, sensitive biological resources, and human-use resources.
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):
- 2001-11-01 00:00:00 - The intertidal habitats of the Aleutians East Borough were mapped using the ESI shoreline ranking scheme below. A typical ESI survey employs a combination of observational scale. Overflights, existing aerial photos and 1:63,360 topographic maps are examined and parameters such as tidal regime, wave energy, and long-shore sediment transport are assessed. If necessary, modifications to the base shoreline are made at this time. Overflights are flown at altitudes ranging from 300 to 600 ft. and speeds of 80 knots during spring low tides. During a five-hour interval of time centered on the peak low tide, the coast is flown and categorized. Mapping within this time interval ensures proper delineation of tidal flats and allows the maximum amount of the intertidal zone to be exposed and evaluated. ESI classifications are recorded onto 1:63,360 U.S. Geological Survey (USGS) maps; small changes in the shoreline, such as inlet positions or new man-made structures, are noted. The final component is the ground verification of the overflight classification. Ideally, examples of each ESI category are surveyed on the ground. The maps compiled in the field are digitized by geographers, and the base shoreline is updated to reflect the observations made during the survey. For the Aleutians East atlas, the ESI shoreline types from the 1980 hardcopy ESI atlases of Bristol Bay and the southern Alaska Peninsula, were digitized and integrated with a newly acquired biological database. Intertidal habitats of the Aleutians West Coastal Resource Service Area (CRSA) were mapped using two systems: (1) the ESI shoreline ranking scheme, and (2) the Coastal Habitats shoreline ranking scheme. The shoreline of Unalaska Island was classified using the ESI ranking system during overflights conducted on 30 June-3 July 2000. In the case of Unalaska, ground-truthing locations included: the north shore of Beaver Inlet near Ugadaga bay; Summer Bay; Iliuliuk Bay; Dutch Harbor; the northern and eastern shores of Amaknak Island, and Captains Bay. The shorelines of all other islands in the Aleutians West CRSA, from Attu to Umnak, were mapped at a scale of 1:250,000 by the same coastal geologist using the more general Coastal Habitat classification system. Overflights of these islands were not conducted, hence the separate mapping scheme. While interest remains high in conducting traditional field-oriented ESI surveys for these islands, budget considerations and logistical factors such as fuel staging, a short field season, habitation, and helicopter availability must be addressed. The mapping done in the Coastal Habitat classification scheme is based on field experience gained in the Unalaska mapping effort, National Imaging and Mapping Agency (NIMA) 1:250,000 topographic maps, USGS bulletin series 1028 (1951-1971) and local expertise. These classifications are not field checked. The categories in the Coastal Habitat scheme are similar to those included in the previous Aleutians West CRSA Resource Inventory atlas. However, the Coastal Habitat scheme improves on the previous work in that individual beaches are mapped as distinct coastal habitats.
(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)
- 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.2. Name of organization of facility providing data access
- 7.2.1. If data hosting service is needed, please indicate
- 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.
Contact NOAA for distribution options (see Distributor). ESI data are processed into multiple formats to make them useful to a wider community of GIS/mapping users. Distribution formats include ARC export, MOSS and Shape files, and MARPLOT map folders. An ArcView ESI project and ESI_Viewer product are also included on the distribution CDs for ease of use of the ESI data. The database files are distributed both in the NOAA standard relational database format (see NOAA Technical Memorandum NOS ORCA 115) and in a simplified desktop flat file format. This metadata document includes information on both of these database formats.;
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.