Search Help Show/Hide Menu

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.

URL of higher-level DM Plan (if any) as submitted to DM Plan Repository:
Always left blank

1. General Description of Data to be Managed

1.1. Name of the Data, data collection Project, or data-producing Program:
NY/NJ Metro Area, Hudson River, and South Long Island 2016 ESI SOCECON Polygons, Lines, Points
1.2. Summary description of the data:

This data set contains vector polygons depicting locations of historical sites; vector lines representing pipeline, road, and rail route features; and vector points representing airports, archaeological sites, abandoned vessels, beaches, bridges, campgrounds, EPA Risk Management Plan (RMP) facilities, historical sites, landfills, oil facilities, renewable energy sites, and surfing 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.

Taken From: Item Identification | Abstract
Notes: Only a maximum of 4000 characters will be included.
1.3. Is this a one-time data collection, or an ongoing series of measurements?
One-time data collection
Taken From: Extents / Time Frames | Time Frame Type
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.
1.4. Actual or planned temporal coverage of the data:
2014 to 2016
Taken From: Extents | Time Frame - Start, Time Frame - End
Notes: All time frames from all extent groups are included.
1.5. Actual or planned geographic coverage of the data:
W: -74.595, E: -71.7215, N: 42.8226, S: 39.9993
Taken From: Extents | Geographic Area Bounds, Geographic Area Description
Notes: All geographic areas from all extent groups are included.
1.6. Type(s) of data:
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)
Map (digital)
1.7. Data collection method(s):
(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.)
No information found
1.8. If data are from a NOAA Observing System of Record, indicate name of system:
Always left blank due to field exemption
1.8.1. If data are from another observing system, please specify:
Always left blank due to field exemption

2. Point of Contact for this Data Management Plan (author or maintainer)

2.1. Name:
ESI Program Manager
Taken From: Support Roles (Metadata Contact) | Person
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.
2.2. Title:
Metadata Contact
Always listed as "Metadata Contact"
2.3. Affiliation or facility:
Taken From: Support Roles (Metadata Contact) | Organization
Notes: The name of the Organization of the most recent Support Role of type "Metadata Contact" is used. This field is required if applicable.
2.4. E-mail address:
orr.esi@noaa.gov
Notes: The email address is taken from the address listed for the Person assigned as the Metadata Contact in Support Roles.
2.5. Phone number:
No information found
Notes: The phone number is taken from the number listed for the Person assigned as the Metadata Contact in Support Roles. If the phone number is missing or incorrect, please contact your Librarian to update the Person record.

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.

3.1. Name:
ESI Program Manager
Taken From: Support Roles (Data Steward) | Person
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.
3.2. Position Title:
Data Steward
Always listed as "Data Steward"

4. Resources

Programs must identify resources within their own budget for managing the data they produce.

4.1. Have resources for management of these data been identified?
No information found
4.2. Approximate percentage of the budget for these data devoted to data management (specify percentage or "unknown"):
No information found

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.

5.1. Processing workflow of the data from collection or acquisition to making it publicly accessible
(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 SOCECONPT 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 SOCECONPT data layer 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 layer are made based on the recommendations of the resource experts, and final hardcopy maps and digital data are created.
  • Process steps 4 and 5 describe the mapping of all polygon features 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. 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 MGT 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. 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 polygon data layers are made based on the recommendations of the resource experts, and final hardcopy maps and digital data are created.
5.1.1. If data at different stages of the workflow, or products derived from these data, are subject to a separate data management plan, provide reference to other plan:
Always left blank
5.2. Quality control procedures employed
(describe or provide URL of description):
No information found

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.

6.1. Does metadata comply with EDMC Data Documentation directive?
No
Notes: All required DMP fields must be populated and valid to comply with the directive.
6.1.1. If metadata are non-existent or non-compliant, please explain:

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?
Notes: Required DMP fields that are not populated or invalid are listed here.
6.2. Name of organization or facility providing metadata hosting:
NMFS Office of Science and Technology
Always listed as "NMFS Office of Science and Technology"
6.2.1. If service is needed for metadata hosting, please indicate:
Always left blank
6.3. URL of metadata folder or data catalog, if known:
Always listed as the URL to the InPort Data Set record
6.4. Process for producing and maintaining metadata
(describe or provide URL of description):
Metadata produced and maintained in accordance with the NOAA Data Documentation Procedural Directive: https://nosc.noaa.gov/EDMC/DAARWG/docs/EDMC_PD-Data_Documentation_v1.pdf
Always listed with the above statement

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.

7.1. Do these data comply with the Data Access directive?
No information found
7.1.1. If the data are not to be made available to the public at all, or with limitations, has a Waiver (Appendix A of Data Access directive) been filed?
No information found
7.1.2. If there are limitations to public data access, describe how data are protected from unauthorized access or disclosure:

None

7.2. Name of organization of facility providing data access:
Office of Response and Restoration (ORR)
Taken From: Support Roles (Distributor) | Organization
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.
7.2.1. If data hosting service is needed, please indicate:
Taken From: Data Management | If data hosting service is needed, please indicate
Notes: This field is required if a Distributor has not been specified.
7.2.2. URL of data access service, if known:
Taken From: Distribution Info | Download URL
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
7.3. Data access methods or services offered:

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).

7.4. Approximate delay between data collection and dissemination:
No information found
7.4.1. If delay is longer than latency of automated processing, indicate under what authority data access is delayed:

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.

8.1. Actual or planned long-term data archive location:
(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)
No information found
8.1.1. If World Data Center or Other, specify:
Taken From: Data Management | Actual or planned long-term data archive location
Notes: This field is required if archive location is World Data Center or Other.
8.1.2. If To Be Determined, Unable to Archive or No Archiving Intended, explain:
Taken From: Data Management | If To Be Determined, Unable to Archive or No Archiving Intended, explain
Notes: This field is required if archive location is To Be Determined, Unable to Archive, or No Archiving Intended.
8.2. Data storage facility prior to being sent to an archive facility (if any):
Office of Response and Restoration - Seattle, WA
Taken From: Physical Location | Organization, City, State, Location Description
Notes: Physical Location Organization, City and State are required, or a Location Description is required.
8.3. Approximate delay between data collection and submission to an archive facility:
No information found
8.4. How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?
Discuss data back-up, disaster recovery/contingency planning, and off-site data storage relevant to the data collection
No information found

9. Additional Line Office or Staff Office Questions

Line and Staff Offices may extend this template by inserting additional questions in this section.

Always left blank