gold_well_transporter
Who moves and buys each well's production: one row per (well, product, role, counterparty, effective interval) linking wells to their gatherer, purchaser, or off-taker, with each counterparty's share of take where reported. Sourced from designation filings (Texas, Colorado, Louisiana) and realized off-take reports (New Mexico).
Access tier: portal
Portal. These rows are well-level or producing-unit-level data, or our modelled output at cohort or grid grain. They open with a Portal, Pro or Enterprise plan. The website shows aggregates built from them, never the rows.
Primary key: well_id, product, role, transporter_reg_id, effective_from
Region codes: co, la, nm, tx
Columns
| Column | Type | Nullable | Description |
|---|---|---|---|
well_id |
string | no | Join key to the well register (gold_wells): the well whose product this counterparty gathers, buys, or takes. Always populated. |
product |
string | no | The product stream, oil or gas (oil includes condensate). Part of the key, not an attribute: a well has distinct counterparties per stream.
Values: oil · gas. |
role |
string | no | The counterparty's role on this stream: gatherer = transports the product off-lease (physical takeaway); purchaser = the first buyer (marketing/credit); off_taker = the receiving counterparty where the source does not distinguish gatherer from purchaser. Texas designations split gatherer and purchaser (a company holding both roles appears as two rows); Colorado reports the hauler only (gatherer); New Mexico reports realized off-take (off_taker).
Values: gatherer · purchaser · off_taker. |
transporter_reg_id |
string | no | The counterparty's regulator-issued ID: Texas RRC operator number, New Mexico OGRID, Colorado COGIS entity number. Always present; part of the key. Opaque string; combine with the well's region to look it up in gold_organization_registrations. |
transporter_entity_id |
string | yes | The resolved company identifier for the counterparty (join to gold_organizations), the counterpart of operator_id on the well register. NULL until the counterparty is resolved; these are midstream and marketing companies (Energy Transfer, Enterprise, Plains, Targa), a different population than producers. |
transporter_name |
string | no | The counterparty's canonical display name (e.g. "ENERGY TRANSFER COMPANY", "EAGLE FORD GATHERING LLC"). Always present. |
effective_from |
date | no | Start of the counterparty's effective interval: the filed designation/effective date where the source files one (Texas, Colorado), or the first observed sale month where the source reports realized off-take without a filed date (New Mexico). For designations filed at lease level this is the filing's own start date, and it can be earlier than the well's arrival on the lease it was filed for. Part of the key. |
effective_to |
date | yes | End of the interval. NULL means currently effective. Derived from the next superseding designation (the day before it takes effect) for filed sources, and for lease-replicated designations, the end of the well's tenure on the filed lease, whichever comes first; the last observed sale month for realized off-take. |
percent_of_take |
float64 | yes | The counterparty's share of the well's product stream, 0-100: the one magnitude comparable across the different source types. Observed on the Texas designation filing; derived for New Mexico (the counterparty's received volume over the well's total sold in the interval); NULL for Colorado (a designation with no volume) and wherever the source reports no share. Multiply by the disposition table's sold volume for the absolute flow to a counterparty. |
origin |
string | no | How the relationship was observed: reported_offtake = the counterparty actually received the volume (realized off-take, New Mexico); reported_designation = a filed designation at well grain (Colorado); lease_designated = a designation filed at lease level and applied to each of the lease's wells (Texas). A designation can sit unused; a realized off-take is an accounting fact: a real trader distinction. Always populated.
Values: reported_offtake · reported_designation · lease_designated. |
How these numbers are built is on methodology; the machine twin of this page is data-dictionary.json.