California coverage

Full

California is selectable in the app and appears in the current state coverage base, with dataset-specific coverage depth.

Status

Full

Permits

Live

Production

Live

Coverage parity

Permits + production

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.

Meaningful oil state in the multi-state coverage base.

Coverage parity

Status	Full
Permits	Live
Production	Live
Coverage parity	Permits + production

Sources

California state sources

Refresh

Refresh cadence depends on the specific source and workflow.

California oil and gas datasets

The current California 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.

WellsProductionCoverage comparison

California oil and gas data workflows

These are the current workflows supported by the listed California 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.

Production coverageCoverage comparison

Known caveats

Permit depth and production depth are labeled separately.

Choose the right California data access path

Check coverage first

Use this page to confirm which California record families are represented and where the source caveats apply.

Build a working review

See the oil and gas data use cases for operator monitoring, territory planning, sales intelligence, maps, exports, and alerts.

Move records into another system

Review the commercial oil and gas data API when the supported California records need to feed a dashboard, CRM, monitor, or internal application.

Frequently asked questions

What California oil and gas data does EnergyNetWatch cover?

The current listed datasets are Wells, Production, Coverage comparison. Coverage depth and source timing vary by record family.

How current is the California data?

Refresh cadence depends on the specific source and workflow. Represented in the active state set; route-level freshness metadata still needs hardening.

Can California records be used through an API?

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.