Data Management Plan
GUID: gov.noaa.nmfs.inport:48088 | Published / External
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
These data were created as part of the National Oceanic and Atmospheric Administration Office for Coastal Management's efforts to create an online mapping viewer called the NOAA Lake Level Viewer. It depicts potential lake level rise and fall and its associated impacts on the nation's coastal areas. The purpose of the mapping viewer is to provide coastal managers and scientists with a preliminary look at lake level change, coastal flooding impacts, and exposed lakeshore. The viewer is a screening-level tool that uses nationally consistent data sets and analyses. Data and maps provided can be used at several scales to help gauge trends and prioritize actions for different scenarios. The NOAA Lake Level Viewer may be accessed at: https://coast.noaa.gov/llv.
This metadata record describes the Lake Michigan digital elevation model (DEM), which is a part of a series of DEMs produced for the National Oceanic and Atmospheric Administration Office for Coastal Management's Lake Level Viewer described above. This DEM includes the best available lidar, US Army Corps of Engineer dredge surveys, and National Park Service multibeam data known to exist at the time of DEM creation that met project specifications. This DEM includes data for Allegan, Antrim, Benzie, Berrien, Charlevoix, Delta, Emmet, Grand Traverse, Leelanau, Mackinac, Manistee, Mason, Menominee, Muskegon, Oceana, Ottawa, Schoolcraft, and Van Buren counties in Michigan; Lake, La Porte, and Porter Counties in Indiana, Cook and Lake Counties in Illinois, and Brown, Door, Kenosha, Kewaunee, Manitowoc, Marinette, Milwaukee, Oconto, Ozaukee, Racine, and Sheboygan Counties in Wisconsin.
The DEM was produced from the following lidar data sets:
1. 2016 NOAA Topobathy Lidar: Upper Lake Michigan Islands
2. 2015 FEMA Marinette County
3. 2013 Indiana Statewide Lidar Collection: Lake, La Porte, Tippecanoe, Newton, Jasper and Porter County Buy-Up
4. 2013 Muskegon County, Michigan Lidar Co-Op
5. 2013 USACE NCMP Topobathy Lidar: Lake Michigan North (MI)
6. 2012 USACE NCMP Topobathy Lidar: Lake Michigan (MI,WI)
7. 2012 USACE NCMP Topobathy Lidar: Lake Michigan (IL,IN,MI,WI)
8. 2010 Brown County Lidar
9. 2008 USACE NCMP Topobathy Lidar: Lake Michigan (IN)
10. 2008 USACE NCMP Topobathy Lidar: Lake Michigan (WI)
11. 2008 USACE NCMP Topobathy Lidar: Lake Michigan (IL)
12. 2008 USACE NCMP Topobathy Lidar: Lake Michigan (MI)
13. 2007 USACE NCMP Topobathy BE Lidar: Lake Michigan (MI) and Lake Erie (PA)
14. 2007 ARRA Lidar: Lake County (IL)
15. 2006 USACE NCMP Topobathy Lidar: Lake Michigan (IN), Lake Erie (OH,PA), Lake Huron (MI)
The DEM was produced from the following sonar data sets:
16. 2015 USACE Detroit District, Port Washington Harbor, WI
17. 2015 USACE Detroit District, South Haven Harbor, MI
18. 2015 USACE Detroit District, Washington Island (Detroit Harbor), WI
19. 2015 USACE Detroit District, Washington Island (Jackson Harbor), WI
20. 2015 USACE Detroit District, Grand Haven Harbor, MI
21. 2015 USACE Detroit District, Pentwater Harbor, MI
22. 2015 USACE Detroit District, Pensaukee Harbor, WI
23. 2015 USACE Detroit District, St. Joseph Harbor, MI
24. 2015 USACE Detroit District, Manistee Harbor, MI
25. 2015 USACE Detroit District, Green Bay Harbor, WI
26. 2015 USACE Detroit District, Saugatuck Harbor, MI
27. 2015 USACE Detroit District, Oconto Harbor, WI
28. 2015 USACE Detroit District, White Lake Harbor, MI
29. 2015 USACE Detroit District, Manistique Harbor, MI
30. 2014 USACE Detroit District, Milwaukee Harbor, WI
31. 2014 USACE Detroit District, Frankfort Harbor, MI
32. 2014 USACE Detroit District, St. Joseph Harbor, MI
33. 2014 USACE Detroit District, Holland Harbor, MI
34. 2014 USACE Chicago District, Burns Waterway Harbor, IN
35. 2014 USACE Chicago District, Burns Small Boat Harbor, IN
36. 2014 USACE Chicago District, Michigan City, IN
37. 2014 USACE Chicago District, Waukegan Harbor, IL
38. 2014 USACE Chicago District, Calumet River, IL
39. 2014 USACE Detroit District, Menominee Harbor, MI/WI
The DEM was produced from the following NPS multibeam sonar data sets:
40. 2011, National Park Service, Sleeping Bear Dunes National Lakeshore Multibeam Sonar
41. 2012, National Park Service, Sleeping Bear Dunes National Lakeshore Multibeam Sonar
The DEM is referenced vertically to the North American Vertical Datum of 1988 (NAVD88) with vertical units of meters and horizontally to the North American Datum of 1983 (NAD83). The resolution of the DEM is approximately 3 meters.
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):
- 2017-01-01 00:00:00 - The source elevation datasets listed above were identified, downloaded, edited, and finalized.
- 2017-01-01 00:00:00 - Source elevation data and their associated hydro-breaklines, where available, were downloaded. Data were then reviewed and edited to meet the project's requirements. The major requirements were delineating data extent for topography and bathymetry; removing areas less than 0.01 square kilometers; creating separate terrain datasets for topography and bathymetry; converting to rasters; and mosaicing the topography and bathymetry together for the final product. NOAA's VDatum datum conversion tool was used to convert geoids.
(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)
- 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.