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:
Oil and Gas Wells
1.2. Summary description of the data:

This dataset contains surface locations of oil and gas wells located in the waters surrounding the United States and associated territories. This feature class is intended for use with the accompanying table titled Oil and Gas Wells (Table). It was necessary to separate the data into an feature class and table because some wells have more than one well record associated with it, each identified by a unique API (American Petroleum Institute) number. These diverging paper trails are often due to co-leasee relationships between multiple operators. Because one geospatial point feature can represent multiple wells, the accompanying table should be joined to this feature in a one-to-many relationship to ensure all data is displayed correctly and completely.These data were retrieved from many different State and Federal Government sources, and there was great diversity of attribution, quality and recency among the sources. This resulting dataset represents the best possible effort to create a temporally relevant data collection with a unified schema appropriate for the intended audience. All users are encouraged to visit the source agencies websites listed in the attributes for the most updated and complete records on individual wells and specific areas of interest. It may also be helpful to consult the lineage section of this document for additional information on each data source.

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?
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.
Edit
1.4. Actual or planned temporal coverage of the data:
2018-06-06
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: -178.292438, E: -67.20884, N: 71.853904, S: 25.947026
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-06-04 05:00:00 - Use the Find Identical Tool and visual comparison of the resulting records' API numbers to eliminate duplicate well records.
  • 2018-06-15 07:00:00 - Add State attribute to the OilGasWells feature class. Using the FederalAndStateWaters feature class, assigned the appropriate labels.
  • 2018-06-04 06:00:00 - Export attribute table to stand-alone table. Call it OilGasWells_Table.
  • 2018-06-04 03:00:00 - Utilize source code definitions and crosswalks described below to populate final attributes as needed. "Source" attribute crosswalk (Final domain ..... Source domains) Permanently abandoned ..... Permanently abandoned, Plugged and abandonded, Junked and abandoned Temporarily abandoned ..... Temporarily abandoned, Temporarily abandoned (oil and gas shows), Temporarily abandoned (old well worked over) Application for permit to drill ..... Application for permit to drill, Permitted, New Drilling active ..... Drilling active, Active Drilling suspended ..... Drilling suspended, Suspended well, Temporarily inactive, Idle Cancelled ..... Cancelled, Permit expired Shut In ..... Shut in, Shut in (dry hole), Shut in (productive) Dry and abandoned ..... Dry and abandoned, Dry and plugged Other ..... Buried, Unknown, Orphan well, Water (no product specified) Production ..... Producing, Active producing, Oil/Gas multiple producer, Oil/Gas producer, Active *in CA DOC sourced data* Worked over ..... Dry and abandoned (well worked over), Gas/Oil producer (old well worked over), Junked and abandoned (old well worked over), Old well worked over, Well worked over, Conversion to oil/gas Injection ..... Active injection Borehole complete ..... Borehole complete, Reverted to single completion Borehole sidetracked ..... Borehole sidetracked, Plugged back, Approved sidetrack ..... Approved sidetrack Bypass ..... Bypass Core test well ..... Core test well "Type" attribute crosswalk (Final domain ..... Source domains) Exploratory ..... Exploratory, Wildcat discovery Relief ..... Relief Development ..... Development, Development well oil/gas, Successful outpost extension, Oil, Gas, Unknown product, No product specified, Dry gas, Liquid gas Core test ..... Core test Stratigraphic test ..... S *in BSEE/BOEM sourced data" Cancelled ..... Cancelled Dry hole ..... Dry hole, Wildcat dry, Development well dry Other ..... Water disposal, Gas disposal, Gas storage, Suspended well Non operation ..... Non operation Service ..... Service, S *in non-BSEE/BOEM sourced data*, Pressure maintenance, Cyclic steam, Steam flood, Water flood, Water source, Air injector
  • 2018-06-04 02:00:00 - Delete superfluous attributes (such as depth, permit date, soil type, etc.) from all layers. Add attributes as need to match desired final schema.
  • 2018-06-04 01:00:00 - Remove all features located on land (clip to shoreline established in FederalAndStateWaters) from files sourced from state agencies. Also delete well records with "bad data" or "unable to locate" in attribution.
  • 2018-06-04 00:00:00 - Project all layers into WGS_1984_World_Mercator.
  • 2018-06-04 05:00:00 - Again using the Find Identical Tool, assign geographically coincident well records the same Match_ID number.
  • 2018-06-04 04:00:00 - Merge all layers together. Call the new file OilGasWells.
  • 2018-06-04 07:00:00 - Delete all attributes from OilGasWells feature class. Use Delete Identical tool to find and delete records with duplicate Match_ID numbers.
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)
  • 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