Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:55413 | 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 polygons depicting locations for aquaculture, essential habitats, and water intakes; and vector points depicting locations for aquaculture, artificial reefs, recreational fishing, repeated measurement sites, and water intakes found i in the New York/New Jersey Metro Area, Hudson River, and South Long Island regions.
Polygons in the SOCECON feature data set may overlap where an area is associated with more than one agency or feature type. As an example, multiple parks may fall within a county boundary, which may itself fall within a larger polygon depicting the jurisdiction of an Army Corps of Engineers region.
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 NY/NJ Metro Area, Hudson River, and South Long Island Human-Use data layers consists of: PARKS-MANAGED AREAS Polygons, Points; NAVIGATION-MARINE 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.
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:
- 2015-11-01 00:00:00 - The following describes the process used to map all human use data layers found within the SOCECON feature data set. 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 publically-available digital data sets supplemented with expert knowledge. Aquaculture locations were provided by the New York State Department of Environmental Conservation (NYSDEC) and New Jersey Department of Environmental Protection (NJDEP). The United States Army Corps of Engineers provided data for their jurisdictional boundaries. United States Coast Guard (USCG) jurisdictional boundaries were acquired from the USCG Operation Systems Center. County jurisdictional boundaries were acquired from the New York State Geographic Information System Program (NYSGIS) Office and the New Jersey Office of Information Technology (NJOIT). Environmental Protection Agency (EPA) Region data came from the EPA. Essential Habitat for fish was provided by the National Oceanic and Atmospheric Administration (NOAA) National Marine Fisheries Service Mid-Atlantic Essential Fish Habitat and New England Essential Fish Habitat. Audubon New York and New Jersey Audubon provided Important Bird Areas data. Multi-species essential habitat in New York was mapped using New York State Department of State's Significant Coastal Fish and Wildlife Habitat data. Federal Emergency Management Agency (FEMA) Regions were acquired by the FEMA Enterprise GIS Services. State managed shellfish areas were obtained from NJDEP and SeaPlan (Northeast Ocean Data). Historical sites came from the National Park Service (NPS), NJDEP, NJDOS, New York State Office of Cyber Security (NYSOCS), and New York State Office of Parks, Recreation, and Historic Preservation (NYSOPRHP). Military jurisdictional boundaries that fall under the responsibility of the Department of Defense came from the United States Census Bureau (Census Bureau), National Atlas, NJDEP, NYSOCS, and NOAA.s Office for Coastal Management. National Estuarine Research Reserve (NERR) boundary data for the Hudson River were provided by the NERR System. National Guard locations were mapped with data from the Census Bureau and the NYSOCS. Fire Island National Seashore and Gateway National Recreation Area were mapped using NPS data. The Nature Conservancy (TNC) properties and easements were provided by TNC. State boundaries were provided by NYSGIS and NJOIT. State park data were provided by NYSOCS and NYSOPRHP, USGS Protected Areas Database, and NOAA.s Office of National Marine Protected Areas Center. The Poospatuck and Shinnecock Reservations were mapped using Census Bureau data. Water Intake locations provided by NJDEP were offset and buffered as requested by New Jersey. United States Fish and Wildlife Service (USFWS) National Wildlife Refuge data were provided by the USFWS.
- 2015-11-01 00:00:00 - All polygons were edited to reflect the updated ESI shoreline. The above digital and/or hardcopy sources were compiled by the project biologist to create the data layers in the SOCECON feature dataset. Depending on the type of source data, two general approaches are used for compiling the data layer: 1) digital data layers are evaluated and used "as is" or integrated with the ESI base map features (ESIP, HYDROP, ESIL) 2) information gathered during initial interviews and from hardcopy sources are compiled and digitized using ESI base map features. See the Lineage section for additional information on the type of source data for this data layer. 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 layer within the SOCECON feature dataset were 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.