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 feature class resides within the SOCECON Feature Data Set of the Great Lakes - Straits of Mackinac 2019 ESI geodatabase. It contains vector polygons representing political/jurisdictional areas for the Great Lakes - Straits of Mackinac study area. The study area includes the Straits of Mackinac, nearby portions of Lake Michigan and Lake Huron, and adjacent lands and waters in northern Michigan.
This data set contains information about the following resources: POLYGONS- Army Corps of Engineers divisions, Coast Guard sectors, cities, counties, Federal Emergency Management Association regions, and tribal lands.
Object specific Type and Source information are stored in the related data tables, SOC_DAT and SOURCES (described below). These are stand-alone tables within the Geodatabase, designed to be used in conjunction with these spatial data layers.
This data set is a portion of the ESI data for Great Lakes - Straits of Mackinac study area. As a whole, the ESI data characterize the marine and coastal environments and wildlife by their sensitivity to spilled oil, and 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.
Bounding box for the Straits of Mackinac area of interest in northern Michigan.
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):
Sources and Process Steps cited below in this metadata record include those used for two distinct areas of the Great Lakes: the Straits of Mackinac in northern Michigan, and the St. Clair / Detroit River System in southeastern Michigan. This is because these two study areas were initially combined into a single ArcGIS geodatabase, before being separated for publication. Some sources may pertain to both study areas, while others may pertain to one study area and not the other. As a final procedural step to prepare the geodatabases for publication, the spatial data data corresponding to each respective area were clipped in ArcGIS according to the two distinct geographic study areas.
- 2019-09-23 00:00:00 - Information on Political/Jurisdictional features within the GL_Mackinac_StClair_Detroit_River 2019 ESI study region were acquired from multiple sources. Political/Jurisdictional features are represented as polygons and include: Army Corps of Engineers divisions (ACE), Coast Guard sectors (CG), cities (CI), counties (CO), Federal Emergency Management Association regions (FEMA), and tribal lands (TL).
- 2019-09-23 00:00:00 - This data was developed as a POLITICAL_POLY feature class within the GL_Mackinac_StClair_Detroit_River 2019 ESI, following ESI Guidelines. Additional data are contained in the joined table SOC_DAT using HUNUM as a unique ID, and in SOURCES using SOURCE_ID as a unique ID. Depending on the type of source data, three general approaches are used for compiling the data layer: 1) information gathered during initial interviews and from hardcopy sources are compiled onto U.S. Geological Survey 1:50,000 topographic quadrangles and digitized; 2) hardcopy maps are digitized at their source scale; 3) digital data layers are evaluated and used "as is" or integrated with the hardcopy data sources. See the Lineage section for additional information on the type of source data for this data layer. The ESI, biology, and human-use data are compiled into the standard ESI digital data format. A second set of interviews with participating resource experts are conducted to review the compiled data. If necessary, edits to the POLITICAL_POLY data layer are made based on the recommendations of the resource experts, and final hardcopy maps and digital data are created.
- 2019-09-23 00:00:00 - The main data sources that were used to depict human-use resources for the POLITICAL_POLY data layer were: 1) Federal Emergency Management Association (FEMA) 2) Great Lakes Aquatic Habitat Framework (GLAHF) and the Great Lakes Commission 3) Michigan Geographic Framework (MGF) 4) U.S. Department of Commerce, U.S. Census Bureau, Geography Division of the U.S. Environmental Protection Agency (USEPA), Region 5. All data provided were digital vector polygon datasets.
- 2019-09-30 00:00:00 - Sources and Process Steps cited above in this metadata record include those used for two distinct areas of the Great Lakes: the Straits of Mackinac in northern Michigan, and the St. Clair / Detroit River System in southeastern Michigan. This is because these two study areas were initially combined into a single ArcGIS geodatabase, before being separated for publication. Some sources may pertain to both study areas, while others may pertain to one study area and not the other. As a final procedural step to prepare the geodatabases for publication, the spatial data data corresponding to each respective area were clipped in ArcGIS according to the two distinct geographic study areas.
(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.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.
Data can be accessed by downloading the zipped ArcGIS geodatabase from the Download URL (see Distribution Information). Questions can be directed to the ESI Program Manager (Point Of Contact).
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.