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 points representing airports, archaeological sites, beaches, facilities, heliports and platforms found in in coastal Louisiana and the lower Mississippi river. Location specific type and source information are stored in relational data tables (described below) designed to be used in conjunction with this spatial data layer. ESI data characterize the marine and coastal environments and wildlife by their sensitivity to spilled oil. The ESI data include information for three main components: shoreline habitats, sensitive biological resources, and human-use resources.
This data set comprises a portion of the ESI data for Louisiana and the lower Mississippi River. The entirety of the ESI Human-Use data layers consists of: PARKS-MANAGED AREAS Polygons; POLITICAL-JURISDICTIONAL Points; RESOURCE MANAGEMENT Polygons, Points; SOCECON Points.
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 geographic extent includes the entire coastal Louisiana and Lower Mississippi River ESI study area. The spatial extent of individual layers or feature classes may vary.
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):
- 2014-05-01 00:00:00 - The following refers to the entirety of the ESI SOCECON data layers consisting of: PARKS-MANAGED AREAS Polygons; POLITICAL-JURISDICTIONAL Points; RESOURCE MANAGEMENT Polygons, Points; SOCECON Points. Sources of data include digital datasets provided by the Federal Aviation Administration (FAA), U.S. Army Corps of Engineers (USACE), Louisiana Department of Transportation and Development (LDOTD), Louisiana Oil Spill Coordinator's Office (LOSCO), Louisiana Department of Culture, Recreation and Tourism (LCRT), and the Louisiana Department of Health and Hospitals (LDHH). Airport / Heliport - Information on the locations of airports and heliports was downloaded from the National Transportation Atlas Databases maintained by the FAA. Archaeological Site - Presence of archaeological sites within a 30-second grid cell were provided by LCRT. Point locations depicted in the database mark the center of a grid cell containing an archaeological site, and may or may not coincide with the actual location of the site. Boat Ramps and Marinas - Locations of boat ramps and marinas were provided by LOSCO. Marinas were defined as any facility with fuel or a store. All other points were mapped as boat ramps. Additional boat ramps were digitized based on USACE navigation maps of the Mississippi River. Ports and commercial docks were mapped as facilities in the database. Shallow and deep draft port locations were obtained from LDOTD and locations of waterfront commercial and industrial facilities with docks were downloaded from the National Transportation Atlas Database. Ferry - Locations of ferry crossings were provided by LDOTD. Ferry landings are shown as points. The actual routes are not depicted. Lock and Dam - Locations of locks and dams were downloaded from the National Transportation Atlas Database. These data were compiled by the USACE. Water Intake - Locations of drinking water intakes were provided by the LDHH. Additional locations were digitized from the USACE 2007 navigation atlas. For locations digitized based on USACE 2007 atlas, Google Earth was used to guide the digitization. The above digital and/or hardcopy sources were compiled by the project biologist to create the SOCECON data layer. 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. 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 SOCECON 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.