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 polygons representing boundaries of historical sites and renewable energy sites; vector lines showing railway routes; and vector points showing locations of abandoned vessels, airports, beaches, EPA facilities, heliports, historical sites, renewable energy sites, wash overs, and waste disposal sites, in Georgia.
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. The entirety of the ESI Human-Use data layers consists of: PARKS-MANAGED AREAS Polygons, Points; NAVIGATION-MARINE Polygons, Points, Lines; POLITICAL-JURISDICTIONAL Polygons, Points; RESOURCE MANAGEMENT Polygons, Points; SOCECON Polygons, Points, Lines; and NATURAL HAZARD Polygons.
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.
This reflects the extent of all land and water features included in the overall Georgia ESI study region. The bounding box for this particular feature class may vary depending on occurrences identified and mapped.
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):
- 2015-06-01 00:00:00 - This description covers the mapping of all Socioeconomic features mapped as polygons: The mapping extent was dependent upon information availability and location of mapped coastal habitats and shorelines. Sources of data used to depict human-use resources in this data layer include digital datasets provided by the U.S. Army Corps of Engineers (USACE), U.S. Coast Guard (USCG), U.S. Fish and Wildlife Service (USFWS), NOAA, National Park Service (NPS), U.S. Census Bureau (USCB), Federal Emergency Management Agency (FEMA), U.S. Environmental Protection Agency (USEPA), The Nature Conservancy (TNC), National Estuarine Research Reserve System (NERR), Bureau of Ocean Energy Management (BOEM), and Georgia's Department of Natural Resources (GADNR) Coastal Resources Division. Critical Habitat - designated critical habitat was mapped for the piping plover, North Atlantic right whale, and loggerhead sea turtle with data downloaded from USFWS. Commercial fishing - Commercial fishing areas show where shad fishing is approved according to GADNR Coastal Resources Division. Fishery Area - Fishery areas provided by GADNR Coastal Resources Division represent recreational and commercial oyster harvest areas. Management Areas - management areas provided by GADNR Coastal Resources Division represent easements, wildlife management areas, and natural areas. Marine Sanctuary - The Gray's Reef National Marine Sanctuary (GRNMS) boundary was provided by NOAA\x92s National Marine Sanctuaries Program. National Estuarine Research Reserve (NERR) - Boundary data was provided by the Sapelo Island NERR System. National Park - Boundaries for the Cumberland Island National Seashore, Fort Frederica National Monument, and Fort Pulaski National Monument were used from the National Park boundaries dataset downloaded from http://Data.gov. Nature Conservancy - Boundaries of The Nature Conservancy (TNC) properties and easements were provided by TNC. Wildlife Refuges - USFWS National Wildlife Refuge (NWR) data were downloaded from the USFWS National Cadastral Data. Anchorage areas - anchorage areas provided by Marine Cadastre. All polygons were edited to reflect the updated ESI shoreline.
- 2015-06-01 00:00:00 - This description covers all socioeconomic features mapped as lines: The mapping extent was dependent upon information availability and location of mapped coastal habitats and shorelines. The main sources of data used to depict human-use resources for this data layer were digital data sets. Rail Route data were acquired from U.S. Department of Transportations's (USDOT) National Transportation Atlas Database. Shipping Lanes in US Waters data were provided by NOAA\x92s Coastal and Marine Spatial Planning office.
- 2015-06-01 00:00:00 - The following description relates to all socioeconomic data represented as points: The mapping extent was dependent upon information availability and location of mapped coastal habitats and shorelines. The main sources of data used to depict human-use resources for this data layer were digital data sets provided by the following agencies: U.S. Army Corps of Engineers (USACE), U.S. Coast Guard (USCG), U.S. Department of Transportation (USDOT), NOAA, Governors' South Atlantic Alliance (GSAA) coast and ocean portal, and Research Planning, Inc. Airports, heliports, ports, and marina data were acquired from USDOT's National Transportation Atlas Database. Known access and beach locations were compiled from NOAA's Office of Response and Restoration. Georgia Department of Natural Resources (GADNR) - Coastal Resources Division provided artificial reefs, marinas, recreational fishing, and repeated measurement sites. Governors' South Atlantic Alliance (GSAA) coast and ocean portal provided boat ramp data. USCG station and facility locations were derived from the USCG Units dataset hosted by http://sciencebase.gov. U.S. Environmental Protection Agency (USEPA) Facility (EPAF) locations represent facilities that maintain a risk management plan describing its hazards and prevention activities as required by the EPA Risk Management Plan Rule (RMP), facilities that manufacture, process, or use certain chemicals in amounts above established levels regulated by the EPA Toxic Release Inventory System (TRIS) program, facilities with permits from the National Pollutant Discharge Elimination System (NPDES), and facilities that the EPA has identified and monitors for storing certain quantities of oil (OIL). The data were provided by the USEPA to NOAA's Emergency Response Division. Historic sites were depicted from sites in the NPS National Register of Historic Places. Abandoned vessel data comes from NOAA's Office of Coast Survey Automated Wrecks and Obstructions Information System (AWOIS). Repeated measurement site (RMS) locations for marine observation sites and tide gauges were obtained through NOAA's National Data Buoy Center (NDBC), and the Center for Operational Oceanographic Products and Services (CO-OPS). Mussel Watch program RMS locations were obtained from the NOAA Chemical Impacts Team. Washover locations are represented by points that were generated by Research Planning, Inc. at a scale of 1:8,000. (A washover, or washover fan, is a relatively flat surface on the top of a barrier spit complex that slopes gently landward. It is usually created when water forced landward by breaking waves flows across the top of the barrier spit during high spring tides or storms. This process creates a flattened-off surface along which sand is transported across the top of the spit into the standing water (lagoon) or marsh landward of the spit. The resulting deposit usually has a fan-like shape.) Waste Disposal Sites were generated from Ocean Disposal Site areas to point features. Army National Guard and Air National Guard base locations were digitized as points from addresses matching and verified with Google Earth imagery by Research Planning, Inc.
- 2015-06-01 00:00:00 - The above digital and/or hardcopy sources were compiled by the project biologist to create the ESI Human Use data layers. 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:24,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 data layers are made based on the recommendations of the resource experts, and final hardcopy maps and digital data are created.
(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.