The product

Where a regulator distinguishes a filed application from an approved permit, wells enter at the filing; elsewhere they enter at approval. Carries identity, operators (the operator as the source records it, the operator we attribute where the winning evidence is not the well record, and the original driller; the current owner is computed from our merger history at read time, so an ownership change reaches every well without a rewrite), surface and bottom-hole location, key lifecycle dates (permit, spud, completion, first production, plugged), wellbore geometry (trajectory, depths, lateral length), formation, and status. Many attributes carry a paired _source column telling you where the value came from (reported by the source, measured from a directional survey, or derived). Regional columns add each jurisdiction's own subdivisions (county, district, municipal district, ...).

Key fields: well_id, well_name (served as name), reported_operator_entity, state_province, basin, trajectory, first_production_date, well_status · 146 fields in all · Full reference

The series runs from first production to the well's reporting frontier: alongside volumes exactly as reported, it includes reliably-inferred rows (interior gap fills, lease-to-well allocations, period-to-month splits), each labeled in record_origin so you can always filter to the raw reported subset. Where a well's operator filed nothing at all in a month, that month may be omitted rather than zero-filled. Volumes are monthly totals; per-day rates, cumulatives, and month counts are intentionally not stored. They derive from this table in one SQL expression (see the derived-fields section). Operator columns carry who filed each record, exactly as the source reported it, plus the operator we attribute where the source filed none; the owner at any date is computed from our merger history at read time, so an ownership correction reaches every month without a rewrite.

Key fields: well_id, date (served as month), year (in the bulk extracts and the change feed), oil_per_month (served as oil), gas_per_month (served as gas), water_per_month (served as water), producing_days, reported_operator (in the bulk extracts and the change feed) · 23 fields in all · Full reference

The monthly operator columns are in the bulk extracts; each well’s operator history is served at /oil-gas/v1/wells/{well_id}/operators.

Each unit carries its grain, jurisdiction, and operator. Volumes live in the monthly unit-production table; well-grain and unit-grain series are unified into one all-grain production surface.

Key fields: producing_unit_id, grain, name, country, region (served as state_province), parent_unit_id, operator, operator_id · 16 fields in all · Full reference

This is the companion of the well-grain production table for sources that report at coarser grain; the unit's name, grain, and jurisdiction live on the producing-units register. A volume is NULL when that stream isn't reported at this unit's grain (e.g. gas metered nationally while oil is per-facility): NULL means no series at this grain, never zero. This table is unified with well-grain production into one all-grain surface.

Key fields: producing_unit_id, date, period_days, oil_per_month, gas_per_month, water_per_month, producing_days, operator · 14 fields in all · Full reference

This is fluid going down the hole; produced water lives on the production table. NULL means not reported, never zero.

Key fields: well_id (in the route path), date (served as month), year (not served), water_injected, gas_injected, injection_type, record_origin · 7 fields in all · Full reference

NULL means the source didn't report that split; 0 is a reported zero. Each disposition column carries its own paired _origin column (reported at well grain vs allocated from lease-level filings). Together with monthly production this gives gross-to-marketed reconciliation and flaring intensity at well grain.

Key fields: well_id (in the route path), date (served as month), year (not served), gas_sold, gas_flared, gas_vented, gas_flared_vented, gas_reinjected · 19 fields in all · Full reference

This is the companion of the well-grain disposition table for sources that report at coarser grain: where the produced volume went, split into sold, flared, vented, reinjected, and fuel. The unit's name, grain, and jurisdiction live on the producing-units register; join monthly unit production for the produced denominator. NULL means the source didn't report that split; 0 is a reported zero. Each disposition column carries its own paired _origin column.

Key fields: producing_unit_id, date, gas_sold, gas_flared, gas_vented, gas_flared_vented, gas_reinjected, gas_lease_fuel · 18 fields in all · Full reference

Key fields: well_id, transfer_date, operator_from, operator_to, transfer_date_basis, effective_date, operator_from_id, operator_to_id · 8 fields in all · Full reference

Sourced from designation filings (Texas, Colorado, Louisiana) and realized off-take reports (New Mexico).

Key fields: well_id, product, role, transporter_reg_id, effective_from, transporter_entity_id, transporter_name, effective_to · 10 fields in all · Full reference

Most series today end at the calendar end, so a sum over a well's series is projected production through the series end, not ultimate recovery. oil_per_month and gas_per_month are expected values: additive across wells, so portfolio sums are portfolio forecasts. p10/p50/p90 bands appear where an uncertainty model backs them (petroleum convention: P10 optimistic).

Key fields: well_id (in the route path), forecast_month (served as month), year (not served), oil_per_month (served as oil), oil_per_month_p10 (held back), oil_per_month_p50 (held back), oil_per_month_p90 (held back), gas_per_month (served as gas) · 11 fields in all · Full reference

Scale a curve by a well's own peak to get that well's expected profile. The basin and region-analog curves are the ones that drive our new-well and total-supply projections; the two sub_region grains (model and descriptive) describe an area's own wells without feeding any projection. curve_grain, n_donors and is_extrapolated tell you the cohort grain, how many wells back the curve, and where the tail is extrapolated rather than donor-backed.

Key fields: curve_grain, stream, mop, norm_rate, norm_rate_p10, norm_rate_p90 · 18 fields in all · Full reference

Amendments update the permit's row (last_amended_date marks them) rather than creating duplicates. Carries the permitted well's identity and proposed location (including bottom-hole for horizontals), the operator at filing and today, and proposed depth, formation, and purpose. well_id is NULL until a well exists.

Key fields: permit_id, well_id, permit_number, country, state_province, state_province_code, well_name, permit_type · 70 fields in all · Full reference

A source that registers one physical completion under multiple registration identities carries one row per registration. Carries the completion date, the wellbore configuration produced by the event (formation, depths, lateral length, trajectory), and interval details. Plug-and-abandon events are not completions; they live on the well register (plugged_date).

Key fields: completion_id, well_id, completion_date, event_type, formation, lateral_length · 52 fields in all · Full reference

Carries treatment dates, total proppant and water volumes, fluid-system classification, and stage count. Where FracFocus and the state disagree, we keep the better value and say which source supplied it: each key measurement carries its own paired _source column (proppant_lbs_source, total_water_gal_source, frac_stages_source).

Key fields: frac_id, well_id, completion_id, frac_start_date, frac_end_date, total_water_gal, proppant_lbs, proppant_type · 16 fields in all · Full reference

Test rates are short-duration measurements; monthly production is the sustained record.

Key fields: test_id, well_id, test_date, test_type, oil_per_day, gas_per_day, water_per_day, gor · 33 fields in all · Full reference

Every filed reading is kept: planned (proposed) surveys as well as as-drilled, and superseded filings alongside the latest, so you can compare plan against actual. For the current as-drilled trajectory, filter is_proposed = false and is_latest_version = true. This is the table for accurate lateral placement, well spacing, and landing-zone work.

Key fields: station_id, well_id, completion_id, station_sequence, leg, leg_type, leg_sequence, md · 26 fields in all · Full reference

Parallel series from independent published sources, each at its native breakdown: the Baker Hughes weekly North America count, the Baker Hughes monthly international count by country, and Mexico's monthly regulator series. Series are never mixed or reconciled, so each row matches the figure its source publishes. Where a source does not break down an axis, that column carries `all`: aggregate only within one source and one period type.

Key fields: source, date, country, state_province_code, area, basin, environment, rig_purpose · 17 fields in all · Full reference

One row per stratigraphic unit (group, formation, member, or bed, plus broad age buckets where a source reports only a geological age), with its place in the hierarchy and stable links into public stratigraphic references. formation_id columns across our well, completion, and formation-top tables reference this registry, so a name like Wolfcamp means the same unit everywhere.

Key fields: formation_id, canonical_name, rank, parent_formation_id, strat_order_base, strat_order_top, strat_order_withheld_reason, macrostrat_strat_name_id · 13 fields in all · Full reference

Built from our formation-top picks; combine with directional surveys to determine where a wellbore landed.

Key fields: basin, formation, grid_lat, grid_lon, formation_id, predicted_tvdss, predicted_tvdss_stddev, isopach_ft · 9 fields in all · Full reference

Sourced from completion reports, well logs and scout tickets; this is the input data behind our gridded formation surfaces.

Key fields: well_id, formation, zone, formation_id, top_tvd, top_md, top_tvdss, top_tvd_source · 18 fields in all · Full reference

The same rock is reported under many names and spellings; each row maps one normalized reported name, within one basin, to its formation_id: the basin scope keeps same-named units in different basins apart. Apply it to your own data to get the same formation resolution we use.

Key fields: normalized_raw_name, basin, formation_id, zone, confidence, source · 6 fields in all · Full reference

One row per organization, deduplicated across regions and name variants; operator id columns across the well, production, and permit tables reference it by organization_id. Where a company was acquired, merged, or renamed, successor_id points to the organization that carries on.

Key fields: organization_id, name, short_name, organization_type, is_public, is_state_controlled, ticker, exchange · 15 fields in all · Full reference

One row per event with the organizations involved and the date it took effect. This drives ownership-over-time attribution: activity before the effective date stays with the original company, after it with the successor.

Key fields: event_id, event_type, effective_date, announced_date, source_org_id (served as source_organization_id), target_org_id (served as target_organization_id), description (held back), source · 9 fields in all · Full reference

When an asset transfer moves only part of a company's assets, this holds the frozen set of wells the deal covered as of its effective date. Most events apply to whole organizations and need no well list, so this table is small and may be empty.

Key fields: event_id, well_id, source · 3 fields in all · Full reference

Regulators publish the same company under many spellings; each row maps one normalized reported name, within one region, to its organization_id. This is the exact lookup our own attribution uses. Apply it to your raw data to get the same resolution.

Key fields: normalized_name, region, raw_example, organization_id, source (held back), is_auto (held back), created_date (held back) · 7 fields in all · Full reference

organization_id links to the company register once the operator is resolved. Where the company behind an ID was renamed, the ID carries one row per period instead (see valid_from / valid_to) so that filings made before and after the rename are attributed to the right company. Some IDs that were transferred to an acquiring company in the regulator's own records are split the same way. A few IDs created for a buyer at an acquisition, where the regulator recorded production from before it under the new ID, are split the same way.

Key fields: region, registration_id, registered_name, status, organization_id · 19 fields in all · Full reference