gold_formation_name_mappings
How reported formation names resolve to registry units. 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.
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_raw_name, basin
Region codes: formations
Columns
| Column | Type | Nullable | Description |
|---|---|---|---|
normalized_raw_name |
string | no | Reported formation string after normalization. |
basin |
string | no | Basin the mapping applies in: the same basin vocabulary as gold_wells.basin. |
formation_id |
string | no | The registry unit this name resolves to (join to gold_formations). |
zone |
string | yes | Informal bench or landing-zone label anchored to the formation (for example an upper/lower bench), where the reported name carries one. |
confidence |
float64 | no | Mapping confidence, 0 to 1. |
source |
string | no | Where the mapping came from. |
How these numbers are built is on methodology; the machine twin of this page is data-dictionary.json.