PDQ Lease Summary (master)

PDQ Lease Summary (master) joins to Statewide Production Data — Oil on District number = District and Lease number = Lease number — many rows here share a single row there.

has a production summary

From the lease to the first and last cycles PDQ holds production for, which is the cheapest way to tell a lease that stopped reporting from one that never did. 4,619 of 5,000 sampled leases match -- the same set the cycle join finds, because both tables are built from the same PDQ lease universe. Expect more than one row back. The summary is keyed on the lease AND its operator and field, so a lease that changed hands or produces from two fields has a row for each: 121,660 of PDQ's lease keys carry one row, 79,812 carry two and 61,043 three, and the tail runs further. Restrict to oil_gas_code = 'O'. These two columns are different types — one is text, the other an integer — so a direct equality is rejected by Postgres. Cast the text side to integer, which also disposes of any leading zeros; casting the integer to text would not, because '000123' and 123 are not equal as text.

PDQ Lease Summary (master) joins to Oil Ledger — Leases on District name = District and Lease number = Lease number — one row here matches one row there.

has a production summary

From the lease record to the first and last cycles PDQ holds production for, which is the cheapest way to tell a dead lease from a live one. 3,754 of 5,000 sampled leases match as the columns stand; the missing quarter is the four lettered districts. Restrict PDQ to oil_gas_code = 'O'. These two columns are different types — one is text, the other an integer — so a direct equality is rejected by Postgres. Cast the text side to integer, which also disposes of any leading zeros; casting the integer to text would not, because '000123' and 123 are not equal as text.

PDQ Lease Summary (master) joins to Statewide Production Data — Gas on District number = District and Lease number = Gas RRC ID — many rows here share a single row there.

has a production summary

The first and last cycles PDQ holds gas production for. 4,775 of 5,000 sampled wells match, and more than one row can come back: the summary is keyed on the well AND its operator and field, so a well that changed hands has a row for each. Restrict to oil_gas_code = 'G'. These two columns are different types — one is text, the other an integer — so a direct equality is rejected by Postgres. Cast the text side to integer, which also disposes of any leading zeros; casting the integer to text would not, because '000123' and 123 are not equal as text.

PDQ Lease Summary (master) joins to Historical Ledger — Statewide Oil on District number = District and Lease number = Lease number — many rows here share a single row there.

has a production summary

From the lease to the first and last cycles PDQ holds production for, which is the cheapest way to tell a lease that stopped reporting from one that never did. 158,539 of 158,566 match. Expect more than one row back: the summary is keyed on the lease AND its operator and field, so a lease that changed hands or produces from two fields has a row for each -- and over 378 months most of these leases have. Restrict to oil_gas_code = 'O'. These two columns are different types — one is text, the other an integer — so a direct equality is rejected by Postgres. Cast the text side to integer, which also disposes of any leading zeros; casting the integer to text would not, because '000123' and 123 are not equal as text.

PDQ Lease Summary (master) joins to Historical Ledger — Statewide Gas on District number = District and Lease number = Gas RRC ID — many rows here share a single row there.

has a production summary

The first and last cycles PDQ holds gas production for. 219,355 of 219,384 wells match, and more than one row can come back: the summary is keyed on the well AND its operator and field, so a well that changed hands over thirty-one years has a row for each. Restrict to oil_gas_code = 'G'. These two columns are different types — one is text, the other an integer — so a direct equality is rejected by Postgres. Cast the text side to integer, which also disposes of any leading zeros; casting the integer to text would not, because '000123' and 123 are not equal as text.

PDQ Lease Summary (master) joins to Statewide Oil Well Database on District number and Lease number — rows can match many rows in both directions.

produced on the lease

From the well to what its lease actually produced, so a tested potential and an allowable can be read beside the volumes. 293,045 of the 293,069 wells match, but the summary carries one row per lease per operator and field, so the 293,045 wells produce 1,068,412 pairs -- aggregate, or pick the operator you mean. Restrict the PDQ side to oil_gas_code = 'O'; gas wells carry their RRC ID in the same lease_no column. These two columns are different types — one is text, the other an integer — so a direct equality is rejected by Postgres. Cast the text side to integer, which also disposes of any leading zeros; casting the integer to text would not, because '000123' and 123 are not equal as text.

PDQ Lease Summary (master) joins to Statewide Gas Well Database on District number = District number and Lease number = Gas RRC ID — rows can match many rows in both directions.

produced as the lease

The gas tape's route to reported production: PDQ keys a gas well's summary on the same statewide RRC ID. 138,870 of the 138,901 wells match, over 510,890 pairs, because the summary repeats a lease per operator and field. Restrict the PDQ side to oil_gas_code = 'G'. These two columns are different types — one is text, the other an integer — so a direct equality is rejected by Postgres. Cast the text side to integer, which also disposes of any leading zeros; casting the integer to text would not, because '000123' and 123 are not equal as text.