OH Division of Oil & Gas Resources Management

Live

Ohio ODNR DOGRM — Marcellus + Utica operator side. ~242K wells (Eclipse, Encino, Ascent, EAP heavy). 4.6K horizontal wellheads + 4.3K lateral polylines + 1.2K well-pad polygons + 1K horizontal drilling units + 3K field polygons.

What is OH Division of Oil & Gas Resources Management?

Ohio ODNR Division of Oil & Gas Resources Management (DOGRM). Marcellus + Utica operator side — Eclipse Resources, Encino Energy, Ascent Resources Utica, EAP Ohio (Eclipse acquired). Probed 2026-05-02. Native server at `gis.ohiodnr.gov/arcgis/rest/services/DOG_Services` — 6 working layers consumed: Oilgas_Wells_public/0 (~242,071 — primary inventory, ALL O&G wells regardless of status), Oilgas_Wells_public/4 (~4,606 horizontal wellheads — Utica/Marcellus laterals), Oilgas_Wells_public/6 (~4,299 horizontal lateral polylines), WellPads/1 (~1,169 well-pad polygons), Unitization_DrillingUnits/1 (~1,007 horizontal drilling-unit polygons), Oilgas_Fields/0 (~2,971 field polygons w/ PROD_TYPE GAS=2262/OIL=702/CBM=7). upstream quirks (probed): **WL_CNTY column UPPERCASE** on wells (88 distinct counties — BELMONT 3,228 wells, CARROLL 3,922, ASHLAND 5,960, ALLEN 4,848); County stored Title Case on WellPads/1 (different casing — handler accommodates both). SLANT distinct codes V=236,357 (97.6%), H=4,679, D=858, O=177 — handler accepts code or descriptive substring. WL_STATUS_DESC has 15 distinct descriptive strings (top: Plugged and Abandoned=68,143, Producing=60,854, Final Restoration=39,053, Unknown status=26,821, Expired Permit=23,374, Well Drilled=10,809, Permit Expired=4,448, Storage Well=3,169, Orphan Well - Ready=2,326, Active Injection=400, Well Permitted=183) — handler matches via UPPER LIKE. Utica_Shale + Marcellus_Shale are 0/1 doubles surfaced as boolean utica/marcellus on output. OrphanWellProgramStatus has trailing whitespace variants ('Referred ', 'LOPTC ') — handler trims for comparison. maxRecordCount=1000 advertised AND enforced. Spec methods searchOilGasFields, searchHorizontalWells, searchDrillingUnits, searchWellPads all working; Oilgas_CoreSamples + NotificationAreas catalog-present but low-value for operator workflows (skipped). InspectorWellHead_Coords FeatureServer is internal-inspector data (skipped).

Available Tools

searchWells
ODNR DOGRM wells (~242K). Filter county, operator, status, wellType (V/H/D/O), uticaOnly/marcellusOnly, orphanOnly, township/formation.
searchHorizontalWells
Utica/Marcellus horizontal wellheads (~4.6K). Pass asLines=true for ~4.3K polyline laterals.
getWellByApi
Lookup single well by API_WELLNO (14-digit, e.g. 34013204000000).
searchWellPads
Well Pad polygons (~1.2K). Filter county/operator/status. County Title Case.
searchDrillingUnits
Horizontal Drilling Units (~1K polygons). Slim — only API_WELLNO + geometry.
searchOilGasFields
Field polygons (~3K). Filter prodType (OIL/GAS/CBM), fieldName, play (CLNN/BERE/PENN/etc.).
getServiceInfo
Schema + record counts for any of the 6 services.

Requirements

ENABLE_ENERGY_APIS
Set ENABLE_ENERGY_APIS=true to allow connector toggles.

Quick Setup Guide

Follow these steps to connect your AI agents to this connector

Set ENABLE_ENERGY_APIS=true for your deployment.

Open /mcp and turn on OH Division of Oil & Gas Resources Management with the energy switch.

Call the oh-dogrm MCP tool — start with method=searchWells or method=searchHorizontalWells.

Connect to Your AI Assistant

Choose your AI assistant below for specific setup instructions

Follow these steps to connect OH Division of Oil & Gas Resources Management to Claude:

Step 1: Open Claude Settings

Launch Claude → Click the profile button (bottom left) → Navigate to Settings

Step 2: Access Connectors

Scroll down to the Connectors tab → Navigate to the bottom → Click “Add Custom Connector”

Step 3: Name Your Connector

Enter any name you'd like for this connector

Step 4: Get the Connector URL

Step 5: Add the Connector

Paste the URL in the “Remote MCP Server URL” text box → Click Add

Step 6: Start Using

Your connector is now ready to use in Claude

Follow these steps to connect OH Division of Oil & Gas Resources Management to ChatGPT:

Step 1: Enable Developer Mode

Go to Settings → Connectors → Advanced → Enable Developer mode

Step 2: Create New Connector

Go back to Connectors page → Click “Create” (top right)

Step 3: Name Your Connector

Enter any name you'd like for this connector (descriptions are optional)

Step 4: Get the Connector URL

Step 5: Add the URL

Paste the URL in the “MCP Server URL” text box

Step 6: Set Authentication

Click the authentication dropdown → Select “No authentication” (PatchOps handles authentication internally)

Step 7: Create the Connector

Click “I understand and want to continue” checkbox → Press Create

Step 8: Using the Connector

Start a new chat → Click the + button (left of text box) → Open dropdown → Hover over three dots labeled “More” → Select your connector

Instructions for connecting OH Division of Oil & Gas Resources Management to GitHub Copilot:

Coming Soon

Detailed setup instructions for GitHub Copilot will be added here.

For other MCP-compatible platforms:

Step 1: Get the Connector URL

Step 2: Add to Configuration

Add this configuration to your MCP settings file. Replace the URL with your specific connector URL from the /mcp page:

"OH Division of Oil & Gas Resources Management-MCP": {
  "url": "https://patchops.ai/api/mcp/...",
  "type": "http"
}

Example Configuration

Here’s an example using PatchOps MCP:

"PatchOps-MCP": {
  "url": "https://patchops.ai/api/mcp/...",
  "type": "http"
}