gold_organization_name_mappings
How reported operator names resolve to organizations. 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.
Access tier: public_aggregate
Public. These rows are the public layer: aggregate series and reference records such as companies, formations and rig counts. Where a page publishes them you can read them on the website, and a free account can export the aggregate series behind a view (10 a month).
Primary key: normalized_name, region
Region codes: organizations
Columns
| Column | Type | Nullable | Description |
|---|---|---|---|
normalized_name |
string | no | Reported operator name after lookup normalization: uppercased, whitespace collapsed, the ampersand written as AND, trailing legal suffixes (INC, LLC, CO, ...) stripped, and a trailing period, comma or hyphen removed. Other punctuation from the source name is kept. |
region |
string | no | Region the mapping applies in (a region code such as `tx`), or `*` for a mapping valid across all regions. |
raw_example |
string | yes | One example of a raw reported string behind this normalized name. |
organization_id |
string | no | The organization this name resolves to. |
source |
string | no | How the mapping was created: `seed` = curated starting set, `enrichment` = automated research pipeline, `correction` = fix applied after the fact.
Values: seed · enrichment · correction. |
is_auto |
boolean | yes | True when the mapping was produced by automated name matching rather than curation. |
created_date |
date | yes | Date the mapping was added. |
How these numbers are built is on methodology; the machine twin of this page is data-dictionary.json.