Skip to content
Developers
Get an API token

Operators and reference lists

Operators, operator contacts, the basin list, and data lineage.

View MarkdownOpen in Claude(opens in a new tab)

Views live in NOVI_DATA_ACCESS.NOVI_WELLS. Column descriptions are from the Wells data dictionary, release 26.4.3. Type is the data model’s logical type, and unit appears where the model declares one. For Snowflake column types, query NOVI_DATA_ACCESS.INFORMATION_SCHEMA.COLUMNS.

8 columns

A company that operates wells.

More about this view

One row per company. Its registrations, and the contact details filed with them, are operator_contact rows keyed by operator_id.

Key columns
  • OPERATOR_ID Surrogate key for the company, derived from name.
Joins to
Sample query
SELECT OPERATOR_ID, WEBSITE, TICKER, IS_PUBLIC, NAME
FROM NOVI_DATA_ACCESS.NOVI_WELLS.OPERATOR
LIMIT 10
Columns8
OPERATOR_IDinteger
Surrogate key for the company, derived from name.
WEBSITEstring
Operator website URL.
TICKERstring
Stock ticker symbol.
More

NULL when the company is not publicly traded or the ticker is unknown.

IS_PUBLICboolean
Whether the organization is a publicly traded company.
NAMEstring
The company's name, verbatim as the source gave it.
More

May contain trailing whitespace. Unique, and the value operator_id is derived from.

SOURCE_ID
Foreign key to source.source_id for data lineage.
CREATED_ATtimestamp
Timestamp the operator record was created.
UPDATED_ATtimestamp
Timestamp of the most recent update.
17 columns

How to reach an operator about a particular jurisdiction, and the registration that jurisdiction issued.

More about this view

A row is either a registration a regulator issued, or an operator's presence in a jurisdiction with no registration behind it; is_registered says which, and external_operator_id is empty on the second kind. Because the unregistered case is a row rather than an absence, a lookup from an operator to a jurisdiction distinguishes 'no registration exists' from 'not present here'.

Key columns
Sample query
SELECT OPERATOR_CONTACT_ID, OPERATOR_ID, EXTERNAL_OPERATOR_ID, COUNTRY, JURISDICTION_REPORTED
FROM NOVI_DATA_ACCESS.NOVI_WELLS.OPERATOR_CONTACT
LIMIT 10
Columns17
OPERATOR_CONTACT_ID
Surrogate key for this registration or presence.
OPERATOR_ID
Foreign key to operator.operator_id: the company this row belongs to.
More

Part of the natural key.

EXTERNAL_OPERATOR_ID
The registration identifier the regulator issued.
More

Absent where no registration exists; required where is_registered is true. Part of the natural key.

COUNTRY
ISO 3166-1 alpha-2 country of the jurisdiction in jurisdiction_reported.
More

Not the mailing country, which is not modelled. Part of the natural key.

JURISDICTION_REPORTED
The state or province that issued the registration, or in which the operator is evidenced.
More

Part of the natural key.

IS_REGISTERED
TRUE where a regulator issued this registration, FALSE where only activity in the jurisdiction attests to the operator's presence.
More

The two row kinds are different claims, 'this regulator issued this registration' versus 'this operator is evidenced here and no registration exists', and this column is what tells them apart; external_operator_id is empty on the second kind.

OPERATOR_REPORTED
The operator's name as this registration recorded it, or as the activity source reported it.
More

Filed spellings differ between a company's registrations, so this is the name on THIS row rather than the company's canonical name, which is operator.name.

ADDRESS
Mailing address, first line.
ADDRESS2
Mailing address, second line, suite, floor or unit.
CITY
Mailing address city.
ADDRESS_STATE
Mailing state or province.
More

Where post is sent, which may differ from jurisdiction_reported, the jurisdiction that licensed the operator.

POSTAL_CODE
Mailing postal code, a US ZIP or ZIP+4, or a Canadian postal code.
More

The mailing country is not modelled, so both forms are accepted and neither is tied to country, which is the licensing jurisdiction's country rather than the address's.

PHONE
Contact telephone number as reported.
EMERGENCY_PHONE
Emergency contact telephone number as reported.
SOURCE_ID
Foreign key to source.source_id for data lineage.
CREATED_AT
Timestamp the record was created.
UPDATED_AT
Timestamp of the most recent update.
3 columns

Reference list of basins and subbasins.

Joins to
Sample query
SELECT BASIN, SUBBASIN, SOURCE_ID
FROM NOVI_DATA_ACCESS.NOVI_WELLS.BASIN
LIMIT 10
Columns3
BASINstring
Name of the basin, e.g. "Permian"
SUBBASINstring
Name of the subbasin, e.g. "Midland"
SOURCE_ID
Foreign key to source.source_id for data lineage.
8 columns

Data lineage dimension.

More about this view

One row per (system, collection, source_file, source_path) lineage tuple, where source_file carries the upstream dataset name (e.g. 'US_Horizontals', 'US_Onshore', 'Canada'). Every base fact and dimension row carries a source_id resolving to exactly one row here, and rows from different datasets of the same upstream table receive distinct source_ids. ingested_at carries the date and time of the bulk export that last loaded this lineage tuple, so it moves with each export.

Sample query
SELECT SYSTEM, INGESTED_AT, COLLECTION, SOURCE_FILE, SOURCE_PATH
FROM NOVI_DATA_ACCESS.NOVI_WELLS.SOURCE
LIMIT 10
Columns8
SYSTEM
Originating system name (e.g., 'regulator', 'internal_ops').
INGESTED_AT
When the data was ingested into the platform.
COLLECTION
Source collection or dataset name within the originating system.
SOURCE_FILE
Upstream dataset name carrying the bulk-export provenance for this row (e.g. 'US_Horizontals', 'US_Onshore', 'Canada').
More

Names the dataset rather than a single file, because this schema's lineage is tracked per dataset.

SOURCE_PATH
Path or URI to the source data file or object.
SOURCE_ID
Deterministic integer hash of the canonical lineage payload.
More

Serves as both primary key and dedup key.

CREATED_AT
Timestamp the source record was created in this system.
UPDATED_AT
Timestamp of the most recent update to this source record.