PDQ Regulatory Lease Directory

PDQ Regulatory Lease Directory joins to Certificate of Authorization P-4 (Oil and Gas) on Oil gas code = Oil gas code and District number = District number and Lease number = Lease rrcid — one row here matches one row there.

is the lease in PDQ's directory

The strongest join on this tape, and the one that gets a lease NAME and a county onto a P-4. 548,047 of the 548,099 leases resolve to exactly one directory row, and every one of the directory's 548,047 rows resolves back -- the two files are the same population of leases seen from two sides. Both write RRC's INTERNAL district number, so no translation is needed here, unlike the proration ledgers below. Keep oil_gas_code in the join: PDQ carries oil leases and gas wells in one table on the same lease_no, and without it a lease matches the other schedule's row of the same digits. 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 Regulatory Lease Directory joins to PDQ Lease Production by Cycle on Oil gas code and District number and Lease number — one row here matches many rows there.

produced from the lease

Production rows carry a lease key and nothing else identifying. The regulatory lease directory is what turns that key into a lease name, an operator, a field number and a well number, and it is where the severance flag lives. Exact on all 5,000 sampled rows. The key is three columns, not one: the oil/gas code, the district and the lease number. Any two of them alone are ambiguous.

PDQ Regulatory Lease Directory joins to Historical Ledger — Statewide Gas on District number = District and Lease number = Gas RRC ID — one row here matches one row there.

is the regulatory lease

The gas well's name, its current operator and its field, none of which is on this tape. 219,356 of the 219,384 wells resolve. Restrict PDQ 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 Regulatory Lease Directory joins to Historical Ledger — Statewide Oil on District number = District and Lease number = Lease number — one row here matches one row there.

is the regulatory lease

The route from a lease number to its NAME, its current operator and its field -- none of which is anywhere on this tape. It is the first join most people need here and it is exact: all 158,566 leases resolve. 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 Regulatory Lease Directory joins to Statewide Production Data — Oil on District number = District and Lease number = Lease number — one row here matches one row there.

is the regulatory lease

The route from a lease number to its NAME, its operator and its field -- none of which is anywhere on this tape. It is the first join most people need here, and the cleanest: 4,998 of 5,000 sampled leases match. 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 Regulatory Lease Directory joins to Statewide Production Data — Gas on District number = District and Lease number = Gas RRC ID — one row here matches one row there.

is the regulatory lease

The gas well's name, operator and field, none of which is on this tape. 4,995 of 5,000 sampled wells match. Restrict PDQ 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 Regulatory Lease Directory joins to High Cost Gas on District number = District and Lease number = Lease number — one row here matches many rows there.

certifies the lease

The certification file and the production system agree on the district (both use the internal numbering) and on the zero-padded lease number, so those two columns join exactly — 4,998 of 5,000 sampled certifications find their lease. They do not agree on the oil/gas code: the certification file writes 'GAS' and the production system writes 'G', which is why that column is not part of the join. Every row here is gas. This is also the route to the field: the certification carries no field number, but the lease directory it lands on does.

PDQ Regulatory Lease Directory joins to Statewide Gas Well Database on District number = District number and Lease number = Gas RRC ID — one row here matches many rows there.

is the lease

PDQ carries a gas well as a lease keyed on its statewide RRC ID, so this well's gas_rrc_id is PDQ's lease_no. 138,870 of the 138,901 wells resolve, and the directory row carries the operator number and field number this tape does not. Restrict the PDQ side to oil_gas_code = 'G': without it the join returns 140,840 rows rather than 138,870, the extra 1,970 being oil leases that share their digits and district with a gas well. 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 Regulatory Lease Directory joins to Statewide Oil Well Database on District number and Lease number — one row here matches many rows there.

is on the lease

From the well to its lease's directory entry, which is where the operator number, the operator name, the field number and the lease name are -- none of which is on this tape. 293,049 of the 293,069 wells resolve, one lease each. Restrict the PDQ side to oil_gas_code = 'O'. Without it the join returns 311,664 rows instead of 293,049: a gas well ID and an oil lease number can be the same digits in the same district, and 18,615 of them are. Both sides write RRC's INTERNAL district number, so no translation is needed here -- unlike the W-10 and G-10 status files, which print the designation. 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 Regulatory Lease Directory joins to PDQ Lease Disposition by Cycle on Oil gas code and District number and Lease number — one row here matches many rows there.

disposed of production from the lease

The lease key resolved to a name, operator and field.

PDQ Regulatory Lease Directory joins to Horizontal Drilling Permits on District name = District and Oil gas code = Oil gas and Lease number = Validated lease number — one row here matches many rows there.

was completed on the lease

The bridge this dataset exists for: from a horizontal permit to the lease or gas well it was finally validated against, and so to everything PDQ knows about that lease's production. Nothing else RRC publishes says which permit became which lease. PDQ carries the printed district in district_name, so the join goes through that and never through district_no. The lease number needs a cast on the oil side and none on the gas side, because daf318 writes six characters for both schedules and PDQ does not: a gas well ID is six digits there, an oil lease number FIVE. As printed, 52,553 of 52,801 gas rows match and 0 of 88,280 oil rows do. Strip the leading zero and pad back to five — lpad(ltrim(validated_lease_no, '0'), 5, '0') — and the oil side goes to 87,816 of 88,280. Both measured over the whole table. Restrict to validated_carryover = false: on 32,429 records RRC's own program left another permit's data in the validated block, and those columns are null here for that reason.

PDQ Regulatory Lease Directory joins to Oil Ledger — Leases on District name = District and Lease number = Lease number — one row here matches one row there.

is the regulatory lease

The lease's entry in PDQ's regulatory directory, which carries its off-schedule and severance flags. 3,848 of 5,000 sampled leases match as the columns stand and all 5,000 once the district's leading zero is stripped; the operator number agrees on every one of them, which is what makes it the same lease rather than a collision. 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 Regulatory Lease Directory joins to Natural Gas Policy Act on District name = District and Lease number = Lease ID — one row here matches many rows there.

covers the gas well

From a GAS docket to the lease directory, on the printed district and the six-digit gas well ID. 148,806 of the 154,493 gas dockets that name a lease resolve, which is 96%. Restrict the PDQ side to oil_gas_code = 'G' if you want to be explicit, though the widths already do it: PDQ writes gas IDs six characters wide and oil lease numbers five, and 0 of the 154,493 gas dockets collide with an oil lease. An OIL docket needs its lease re-padded to five digits first and is not this join — see the dataset's gotchas. The join goes through district_name, not district_no: NGPA publishes the printed designation once the subscript is decoded, and PDQ's district_no is the internal number.

PDQ Regulatory Lease Directory joins to Gas Ledger — Wells on District name = District and Lease number = Gas RRC ID — one row here matches one row there.

is the regulatory lease

The gas well's entry in PDQ's regulatory directory, which carries its off-schedule and severance flags. 4,232 of 5,000 sampled wells match as the columns stand and all 5,000 with the district normalised. Restrict PDQ 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 Regulatory Lease Directory joins to PDQ Onshore Lease Summary on Oil gas code and District number and Lease number — one row here matches many rows there.

summarises the lease

The onshore lease summary's key, resolved to the lease directory.

PDQ Regulatory Lease Directory joins to Statewide API Data (dBase) on Lease number = Gas RRC ID — one row here matches many rows there.

is on the gas lease

The gas half of the map's lease column, resolved to the lease directory. 302,481 of the 306,668 gas entries match, and 289,503 of the 293,684 distinct gas well IDs. Safe without a district only because gas well IDs are effectively statewide: 102 of the 294,448 PDQ carries appear in more than one district. The width does the schedule restriction on its own — PDQ writes oil lease numbers five characters wide, so a six-character gas ID matches 0 non-gas rows. None of this holds for oil_lease_no, which is why there is no oil equivalent of this join; go through the well completion table instead.