PDQ Lease Production by Cycle

PDQ Lease Production by Cycle joins to Historical Ledger — Statewide Oil on District number = District and Lease number = Lease number — many rows here share a single row there.

produced, by month

The two long series side by side, and the reason to know which one you want. Both reach back to January 1993 and ALL 158,566 leases on this tape have PDQ cycles -- a clean 100%, the best rate in this family. Where both carry a figure they agree: in cycle 200506 the P-1 oil volume here is identical to lease_oil_prod_vol on all 69,283 leases reporting, and in 201506 on 83,454 of 83,479. Take PDQ when you want the lease NAME, the operator name and the field name, which this tape does not carry at all. Take this one for the allowable, the movable balance, the overproduction status and the dispositions broken out by code, none of which PDQ has. Restrict PDQ to oil_gas_code = 'O', and add the cycle to the join if you are joining month to month -- Historical Ledger -- Oil Lease Months carries cycle_yyyymm for exactly that, and without it both sides multiply by 378. 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 Production by Cycle joins to Historical Ledger — Statewide Gas on District number = District and Lease number = Gas RRC ID — many rows here share a single row there.

produced, by month

PDQ carries a gas well as a lease keyed on the same RRC id, so this is the oil join again and it scores the same way: all 219,384 wells on this tape have PDQ cycles. MIND THE WET AND THE DRY. This tape's production is the WET volume charged against the allowable; PDQ's lease_gas_prod_vol is the dry one. In cycle 202406, production minus the code-9 (separation and extraction loss) disposition equals PDQ's figure on 141,447 of the 141,466 wells both carry, where comparing the raw volumes matches only 111,614. In 200506 all 103,045 wells reporting match on the key. Restrict PDQ to oil_gas_code = 'G', and add the cycle if you are joining month to month -- Historical Ledger -- Gas Well Months carries cycle_yyyymm for exactly that. 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 Production by Cycle joins to Statewide Production Data — Oil on District number = District and Lease number = Lease number — many rows here share a single row there.

produced, by month

The join that puts the regulatory record beside the published volumes: what the lease was allowed to produce, and what PDQ says it produced. 4,619 of 5,000 sampled leases match; the missing 381 are leases on the production database that PDQ has no cycle for at all, usually because they have filed nothing in the window. Where both sides carry a figure they agree: in cycle 202506 the P-1 oil volume here is identical to lease_oil_prod_vol on 73,188 of the 73,271 leases matched. PDQ is the one to use for a long series; this tape is the one that is current, because PDQ's rows for 202606 onwards exist with every volume zero. Restrict PDQ to oil_gas_code = 'O': 122 of 5,000 sampled leases collide with a gas well of the same number in the same district. 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 Production by Cycle joins to Statewide Production Data — Gas on District number = District and Lease number = Gas RRC ID — many rows here share a single row there.

produced, by month

PDQ carries a gas well as a lease keyed on the same RRC id, so this is the same join as the oil one and scores the same way: 4,775 of 5,000 sampled wells match. Two figures here are worth crossing. lease_gas_prod_vol is the DRY volume, identical to dry_gas_mcf on 119,974 of the 120,106 wells matched in cycle 202506 -- not to gas_prod_mcf, which is wet. And lease_gas_allow is the allowable in full, where this tape's balancing_allow_amt keeps only its low five digits. Restrict PDQ to oil_gas_code = 'G': 76 of 5,000 sampled wells collide with an oil lease of the same number in the same district. 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 Production by Cycle joins to Oil Ledger — Leases on District name = District and Lease number = Lease number — many rows here share a single row there.

produced, by month

The join that puts the schedule beside the production: the allowable the ledger assigned against the volumes PDQ reports. Restrict the PDQ side to oil_gas_code = 'O' -- a gas well carries the same digits in the same lease_no column, and 298 of 5,000 sampled oil leases collide with one. 3,773 of 5,000 sampled leases match on the columns as they stand. The 1,227 that do not are every lease in 6E, 7B, 7C and 8A: the ledger writes 06E and PDQ writes 6E. Strip the leading zero and all 5,000 match. 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 Production by Cycle joins to Gas Ledger — Wells on District name = District and Lease number = Gas RRC ID — many rows here share a single row there.

produced, by month

The gas schedule beside the gas production: PDQ carries a gas well as a lease, keyed on the same six-digit RRC id. Restrict the PDQ side to oil_gas_code = 'G' -- 43 of 5,000 sampled wells collide with an oil lease of the same digits. 4,200 of 5,000 match on the columns as they stand and all 5,000 once the district's leading zero is stripped. 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 Production by Cycle joins to PDQ County Lease Production by Cycle on Oil gas code and District number and Lease number and Cycle year month — one row here matches many rows there.

is the county split of

A lease that crosses a county line has its production apportioned between counties. Summing the county split by lease double counts; use the lease cycle table for lease totals.

PDQ Lease Production by Cycle joins to PDQ Lease Summary (master) on Oil gas code and District number and Lease number — many rows here share a single row there.

summarises the monthly production

The summary gives a lease's first and last production cycle; the cycle table gives every month in between. Read the summary first if you are about to scan 76 million rows.