Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:55020 | Published / External
This is an outdated version of the NOAA Data Management Plan template. InPort now supports a dedicated Data Management Plan Catalog Item type, which is up-to-date with the latest NOAA DMP template. The ability to generate Data Management Plans from Data Sets will be discontinued in a future release. Please see the Data Management Plan Help Guide to learn more.
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 point data for: access sites, airports, archaeological sites, boat ramps, coast guard stations, ferries, heliports, historical sites, marinas, recreational fishing, and water intakes; and vector lines for roads and state boundaries in Delaware, New Jersey, and Pennsylvania.
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: SOCECON Lines, Points, and MGT 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 Delaware Bay (Delaware, New Jersey, Pennsylvania) 2014 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.
4. Resources
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):
Process Steps:
- 2014-03-01 00:00:00 - 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: Pennsylvania Fish and Boat Commission (PFBC), New Jersey Department of Environmental Protection (NJDEP) Division of Fish and Wildlife (F&W) Bureaus of Marine Fisheries and Shellfisheries (BMF & BSF), Federal Aviation Administration (FAA), Delaware Department of Natural Resources and Environmental Control (DNREC), Delaware River and Bay Authority (DRBA), United States Coast Guard (USCG), NJDEP, Natural and Historic Resources Historic Preservation Office (HPO), Delaware State Historic Preservation Office, and the National Park Service (NPS).
- 2014-03-01 00:00:00 - Access Sites: Access site data was provided by NJDEP and indicates beach and river access locations. Airports/Heliports: Information on the locations of airports and heliports was downloaded from the National Transportation Atlas Databases maintained by the FAA. Archaeological/Historic sites: National Park Service (NPS) National Register of Historic Places data (2007) was used for all three states to depict historic sites. Delaware archaeological/historic sites: DE archaeological and historic site data was provided by the DE Division of Historical and Cultural Affairs. Four data sets were provided for inclusion in the ESI: DE National Historic Landmarks, DE State Historic Register Districts, DE National Register dataset, and DE National Historic Properties. All archaeological site points from the pre-processed data sets were buffered and offset prior to plotting in the ESI to protect the sensitivity of the resources. New Jersey Archaeological/Historic sites: NJ archaeological and historic site data was provided by NJDEP Natural and Historic Resources Historic Preservation Office (HPO). NJ HPO provided a nj_stgrd layer, which included one added attribute from the version available at DEP's downloads page. The site_status field in the data set as provided, which is the NAME field in the ESI, indicates National Register eligibility status of the site(s) within the grid determining whether sites are one of three statuses: listed, eligible, or identified. 'Listed' sites are included in the NJ or National Registers of historic places; 'eligible' sites have been determined eligible for inclusion through federal or state processes as administered by the HPO; 'identified' sites have been identified through cultural resource survey or other documentation on file at the HPO. The centroid point of each grid cell was used for data display purposes in the ESI. Please note: This atlas was developed using NJDEP GIS digital data for archaeological and historic sites, but this secondary product has not been verified by NJDEP and is not state-authorized. Boat Ramps: Boat ramp location data was provided by NJDEP, PFBC, DNREC and NJ SeaGrant Consortium. Coast Guard: USCG locations are located in all 3 states. Location data was provided by the USCG. Ferries: Three ferries occur in the Area of Interest (AOI): Cape May - Lewes Ferry (between NJ and DE), Fort Mott - Fort Delaware Ferry (between NJ and DE), and the Riverlink Ferry (between NJ and PA). Ferry data was provided by the Delaware River and Bay Authority. Marinas: Marina location data was provided by PFBC, DNREC, and NJ SeaGrant Consortium. Recreational Fishing: Recreational fishing locations were provided by NJDEP DFW Bureau of Marine Fisheries and DNREC. Water Intake: Locations of drinking water intakes were provided by the DNREC.
- 2014-03-01 00:00:00 - 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:45,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 SOCECON data layer 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.
Missing/invalid information:
- 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.
None
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.