Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:55812 | 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 lines depicting shipping lanes; and vector points depicting access sites, anchorages, boat ramps, diving sites, ferries, lock and dam sites, marinas, and ports in the New York/New Jersey Metro Area, Hudson River, and South Long Island regions.
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 - Process steps 1 and 2 describe the process used to map all points within the 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. The main sources of data used to depict human-use resources for this data layer were publicly-available digital data supplemented with expert knowledge. Abandoned vessel data originated from the National Oceanic and Atmospheric Administration (NOAA) Office of Coast Survey Automated Wrecks and Obstructions Information System. Access locations were compiled using New York State Department of Environmental Conservation (NYSDEC) digital data and Quantum Spatial, Inc. (QSI) generated points. Airport locations were acquired from Federal Aviation Administration Aeronautical Information Services. NYSDEC and Rutgers Agricultural Experiment Station provided information on aquaculture sites. Archeological sites were provided by Hudsonia LTD and New Jersey Department of Environmental Protection. NOAA.s Coastal Services Center provided data for artificial reefs. Beach locations were compiled by QSI using aerial imagery and data from United States Geological Survey Geographic Names Information System. Boat ramp locations were mapped using digital data from NYSDEC, New York State Office of Parks, Recreation & Historic Preservation, New York State Office of Cyber Security (NYSOCS), and National Park Service. The NYSOCS also provided state campground data. Coast Guard unit locations were acquired from the U.S. Coast Guard (USCG) Operation Systems Center and U.S. Department of Commerce, Census Bureau, Geographic Products Branch. Diving and surfing sites were acquired from EcoTrust as part of the Mid-Atlantic Coastal and Ocean Recreation Study. The New Jersey Department of State and New York City Department of City Planning provided ferry terminal data. U.S. Environmental Protection Agency (USEPA) Facility locations represent facilities that are required to maintain a risk management plan, because they use/store regulated substances exceeding an EPA-specified threshold quantity. 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. Landfill sites were compiled from Energy Justice and NYSDEC tabular data. Lock and Dam data were acquired from NYSDEC.s Inventory of Dams. Marina data were provided by the Hudson River Boat and Yacht Club Association, the Mohawk Hudson Council of Yacht Clubs, and Peter Cunningham. Additional probable marina locations were mapped by QSI using Google Earth imagery. NYSDEC and United States Energy Information Administration provided locations of major oil facilities.
- 2015-11-01 00:00:00 - Port locations were obtained from NOAAS.s Coastal Services Center, National Atlas, and NYC Department of City Planning. Recreational fishing sites came from NYSDEC. NOAA.s Office for Coastal Management provided data for renewable energy. Repeated measurement site (RMS) locations for marine observation sites and tide gauges were obtained through NOAA's National Data Buoy Center, and the Center for Operational Oceanographic Products and Services. Mussel Watch program RMS locations were obtained from the NOAA Chemical Impacts Team. An oyster restoration site was provided by New York/New Jersey Baykeeper. Streamflow gage locations were obtained from the USGS. NYSDEC Bureau of Water Resources Management provided water intake locations and were supplemented with expert knowledge. Water intakes in New Jersey were mapped as polygons and were not included in this feature class. The above digital and expert knowledge sources were compiled by the project biologist to create the SOCECON point data layers. 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. 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 point data layers are made based on the recommendations of the resource experts, and final hardcopy maps and digital data are created.
- Process step 3 describes the process used to map all lines within the 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. The main sources of data used to depict human-use resources for this data layer were publicly-available digital data sets. Bridge locations were mapped using the National Atlas of the United States Major Roads and supplemented by Quantum Spatial, Inc. (QSI) using ESRI aerial imagery. Pipeline data were acquired from the United States Energy Information Administration. Rail routes were acquired from the National Atlas. Shipping Lanes were mapped using the National Waterway Network provided by the United States Army Corps of Engineers. The above digital sources were compiled by the project biologist to create the SOCECONL data layer. 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. 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 line 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.
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.