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 feature classes HYDROL and HYDROP contain vector lines and polygons representing the coastal shoreline and hydrography used in the creation of the Environmental Sensitivity Index (ESI) for Great Lakes - St. Clair / Detroit River System - 2019 ESI Geodatabase. The HYDROP (hydrography polygons) layer delineates the shoreline, and identifies areas as either Land or Water. The HYDROL (hydrography lines) layer includes features that are not captured in the HYDROP data layer, such as breakwaters, fenders, groins, jetties, and piers.
The study area includes a small portion of southern Lake Huron at its outlet, the St. Clair River (which flows out of Lake Huron), Lake St. Clair, the Detroit River (which flows into Lake Erie), a small portion of western Lake Erie, and adjacent lands and waters in southeastern Michigan.
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 St. Clair - Detroit River System area of interest in southeastern 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. 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 - The HYDROL dataset was derived from the National Shoreline composite (2011) and verified using ESRI Basemap World Imagery (2010-2017) as well as Google Earth imagery (2014-2018). Piers and docks were trimmed/extended to match the shoreline if this was implied; however, structures such as groins, jetties, fenders, and breakwaters that appeared to extend inland of the shoreline were left as is.
- 2019-09-23 00:00:00 - The land and water polygons in the area of interest (RPI 2018-2019) for the HYDROP dataset were derived primarily from digital coastline data originating from the integration of the National Oceanic and Atmospheric Administration (NOAA) Continually Updated Shoreline Product (CUSP, 2006-2007) and National Shoreline composite (2011); the U.S. Geological Survey (USGS) high resolution National Hydrography Dataset (NHD, 2011-2016); the U.S. Fish and Wildlife Service (USFWS) National Wetlands Inventory (NWI) dataset (1975-2013); the Ontario Ministry of Natural Resources dataset (1998-2018) and manual digitization at 1:4,000 from BING Bird’s Eye and Aerial imagery (2012-2019), ESRI Basemap World Imagery (2010-2017), and Google Earth aerial imagery (2014-2018). The most recent shoreline was utilized where available. Additional sources used to verify ESI classification and identify land and water polygons included: U.S. Army Corps of Engineers Oblique Imagery (2012), Marinas.com (2018, Marinas only), and Land Use 2010 from Agriculture and Agri-Food Canada.
- 2019-09-23 00:00:00 - Depending on the type of source data, four general approaches are used for compiling these data layers: 1) hardcopy maps are digitized at their source scale; 2) digital data layers are evaluated and used "as is" or integrated with the other data sources; 3) overflight classifications are digitized from the scanned and registered hardcopy field maps; and/or 4) classifications are interpreted from oblique gps referenced photography or video taken during the overflights. After the initial shoreline classification, these data are edgematched and checked for logical consistency errors. Review maps are plotted at 1:50,000 scale for verification of polygonal and linear attributes. 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 HYDROL and HYDROP data layers are made based on the recommendations of the resource experts, and final hardcopy maps and digital data are created.
- 2020-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. 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.