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:
Pipelines
1.2. Summary description of the data:

This data set contains the locations of oil and gas pipelines in the Unites States Offshore Outer Continental Shelf. The areas found in Alaska were calculated NAD 1983 Alaska Albers Equal Area Conic. All data in the layer is projected into WGS 1984 World Mercator.

Taken From: Item Identification | Abstract
Notes: Only a maximum of 4000 characters will be included.
Edit
1.3. Is this a one-time data collection, or an ongoing series of measurements?
No information found
Taken From: Extents / Time Frames | Time Frame Type
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.
Edit
1.4. Actual or planned temporal coverage of the data:
No information found
Taken From: Extents | Time Frame - Start, Time Frame - End
Notes: All time frames from all extent groups are included.
Edit
1.5. Actual or planned geographic coverage of the data:
W: -152.15446, E: -68.811756, N: 70.490307, S: 25.39485
Taken From: Extents | Geographic Area Bounds, Geographic Area Description
Notes: All geographic areas from all extent groups are included.
Edit
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:
NOAA Office for Coastal Management (NOAA/OCM)
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.
Edit
2.2. Title:
Metadata Contact
Always listed as "Metadata Contact"
2.3. Affiliation or facility:
NOAA Office for Coastal Management (NOAA/OCM)
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.
Edit
2.4. E-mail address:
coastal.info@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:
(843) 740-1202
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:
No information found
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.
Edit
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:

  • 2018-05-24 00:00:00 - Project all source layers into WGS_1984_World_Mercator & erase any pipelines that fall on land using the USAStateTerritoriesAssociatedAreas feature class with the FederalAndStateWaters layer removed from it to assure pipelines falling in State Waters were captured. Each layer was named with "_project" after it was properly projected and the layers that had to have space erased had "_erase" after this step was completed.
  • 2018-05-25 00:00:00 - Cleaned up attributes to read more clearly. Set attribute alias.
  • 2018-05-24 00:00:00 - Create the Length attribute and utilize the calculate geometry function and calculate the length in meters. Select the Alaska data, export & project into Alaska Albers Equal Area & calculate the length in meters within this projection. Take the Alaska Equal Area length calculations for each attribute and replace them in the proper place in the Pipeline feature class. The calculations for the Alaska data will be from Albers Equal Area, but the layer and data are still projected into World_Mercator.
  • 2018-05-24 00:00:00 - Merged the BOEM_Pacific_Pipelines_2011-08 & ppl_arcs projected layers into one layer called BOEM_MC_Pipelines.
  • 2018-05-24 00:00:00 - Utilizing the select by location for all other layers individually NaturalGas_Pipelines_US_201804_project_erase , PetroleumProduct_Pipelines_US_201801_project_erase, ME_project_erase, mv_infra_pipeline_ln_project_erase , MS_Natural_Gas_Pipelines_project_erase , LAPipelinesfromTIMS_project_erase, Offshore_pipelines_project_erase select the attributes that intersect with the Pipelines feature class & export this data with a naming convention that ends in layername_Conflict & add this back to your map. Reselect the data that intersects the Pipelines using the Select by location and reverse the selection so that you have all of the pipelines that are not currently present in the Pipelines feature class, using the Editor copy the data into Pipelines feature class.
  • 2018-05-24 00:00:00 - Copy all data in the BOEM_MC_Pipelines dataset and save as a new Pipelines feature class. Starting with California, individually confirm Emmy_oil.shp , Emmy_oil_and_low_pressure_gas.shp , Emmy_water_and_high_pressure_gas.shp , Esther_gas.shp , Esther_oil.shp , Eva_gas.shp , Eva_oil.shp , Holly_gas.shp , Holly_oil.shp , Holly_Power_Cable.shp , & spps tent gas.shp attributes were not present in BOEM data and added to the Pipelines feature class using the Editor.
  • 2018-05-24 00:00:00 - Create Status_Descrpt & Prod_Descrpt attributes and fill in the information required using the Select by Attribute feature in the table to select for the status code or product code that is provided by BOEM/BSEE. https://www.data.bsee.gov/Main/HtmlPage.aspx?page=pipelineMastersFields#Prod%20Code
  • 2018-05-24 00:00:00 - Once the conflicting data has been edited & remove pipelines that already existed you will be left with pipelines to add to the Pipelines feature class, which can be completed with the Merge tool or utilizing the Editor tool. The Pipelines feature class now has all pipelines added into the attributes.
  • 2018-05-24 00:00:00 - Create attributes STATUS_CODE, PPL_SIZE_CODE, PROD_CODE, SDE_COMPANY for each layer and populate using the information available from each layer assuring that schema is matching to the BOEM/BSEE layers - https://www.data.bsee.gov/Main/HtmlPage.aspx?page=pipelineMastersFields#Prod%20Code . Turn off attributes in the fields tab that will not be needed moving forward for all 20 data layers/deleted empty attributes so that when exported only the important attributes move forward.
  • 2018-05-24 00:00:00 - The Pipelines feature class with now have all data that was not conflicting from all layers present. Go through each "layername_Conflicting" data set utilizing the Editor tool and remove any pipelines that you can confirm are already present in the Pipelines feature class. Utilize the STATUS_CODE, PPL_SIZE_CODE, PROD_CODE,& SDE_COMPANY attributes that you already filled out to see if the data is truly already present. If a pipeline did not have information available & a N/A was filled in it will not be possible to determine if this line has already been gathered so it should be left in.
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.3. Is this a one-time data collection, or an ongoing series of measurements?
  • 1.4. Actual or planned temporal coverage of the data
  • 1.7. Data collection method(s)
  • 3.1. Responsible Party for Data Management
  • 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.2. Name of organization of facility providing data access
  • 7.2.1. If data hosting service is needed, please indicate
  • 7.3. Data access methods or services offered
  • 7.4. Approximate delay between data collection and dissemination
  • 8.1. Actual or planned long-term data archive location
  • 8.2. Data storage facility prior to being sent to an archive facility
  • 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:
No information found.
7.2. Name of organization of facility providing data access:
No information found
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.
Edit
7.2.1. If data hosting service is needed, please indicate:
No information found
Taken From: Data Management | If data hosting service is needed, please indicate
Notes: This field is required if a Distributor has not been specified.
Edit
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.
Edit
7.3. Data access methods or services offered:
No information found
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.
Edit
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.
Edit
8.2. Data storage facility prior to being sent to an archive facility (if any):
Partial information found
North Charleston, SC
Taken From: Physical Location | Organization, City, State, Location Description
Notes: Physical Location Organization, City and State are required, or a Location Description is required.
Edit
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