What West Virginia oil and gas data does EnergyNetWatch cover?
The current listed datasets are Production, Permits/status where available, Operator coverage. Coverage depth and source timing vary by record family.
West Virginia is a live gas-focused coverage state in the current app and API state set.
The coverage table summarizes state availability and dataset parity. State sources publish different record types on different schedules, so permit coverage, production coverage, and workflow depth are listed separately. Read the coverage methodology.
Gas-focused state with H6A production loaded through the 2025 Q4 workbook, including monthly fields through December 2025.
| Status | Full |
|---|---|
| Permits | Live |
| Production | Live |
| Coverage parity | Permits + production |
Refresh cadence follows state source availability.
The current West Virginia coverage page lists each dataset separately so production, permits, wells, maps, and other records are not presented as if they have identical depth or timing.
These are the current workflows supported by the listed West Virginia source coverage. The record type and latest available source date should stay visible when results move into a map, export, report, alert, or API integration.
Use this page to confirm which West Virginia record families are represented and where the source caveats apply.
See the oil and gas data use cases for operator monitoring, territory planning, sales intelligence, maps, exports, and alerts.
Review the commercial oil and gas data API when the supported West Virginia records need to feed a dashboard, CRM, monitor, or internal application.
The current listed datasets are Production, Permits/status where available, Operator coverage. Coverage depth and source timing vary by record family.
Refresh cadence follows state source availability. Recurring source refresh; depth is stronger for gas production and operator context than for every workflow.
API availability depends on the dataset, account, endpoint family, and current state coverage. The commercial API page and public reference describe the supported integration path.