PDQ Well Completion Directory

PDQ Well Completion Directory joins to Statewide Oil Well Database on Well root number = Wlroot key — one row here matches one row there.

is PDQ's well completion

The one join that gets an API number out of this tape. PDQ's well_root_no is the same RRC internal well id as WL-ROOT-KEY, zero-padded to eight characters, and it resolves for 293,022 of the 293,069 oil wells -- one PDQ completion each, never more. The row it lands on carries api_county_code and api_unique_no, the county name, and PDQ's own district/lease/well key. 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 Well Completion Directory joins to Statewide Gas Well Database on Well root number = Wlroot key — one row here matches one row there.

is PDQ's well completion

The same bridge for the gas tape: 138,869 of the 138,901 gas wells resolve to exactly one PDQ well completion, which is where the API number and the county are. The two tapes share no root keys, so a key that matches here does not match the oil tape. 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 Well Completion Directory joins to PDQ Regulatory Lease Directory on Oil gas code and District number and Lease number — many rows here share a single row there.

is produced by the wells

The wells that make up a lease. Texas reports oil production by lease, so this is as close as the production data gets to a well — it tells you which wells are on the lease, not what each one made.

PDQ Well Completion Directory joins to Statewide API Data (dBase) on API county code = API county and API unique number = API unique — rows can match many rows in both directions.

is carried on the schedule as

The way to get from an API number to a lease WITH its district and schedule, which the map alone cannot give you: PDQ's well completion table carries the API halves alongside oil_gas_code, district_no and lease_no. 819,086 of PDQ's 820,005 completions have an entry in the map, and 998,442 of the map's 1,556,119 entries reach a completion — the rest are bores that were never carried on a proration schedule.

PDQ Well Completion 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 well whose completion is

From the gas id to PDQ's completion record and its API number. 219,205 of the 219,384 wells match, and exactly one row comes back for each, because a gas 'lease' in PDQ IS one well. The oil edge is the same join and one-to-many. 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 Well Completion 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 well whose completion is

From the gas id to PDQ's completion record and its API number. 4,988 of 5,000 sampled wells match, and exactly one row comes back for each: all 231,690 gas keys in PDQ's completion directory carry a single row, because a gas 'lease' there IS one well. The oil edge above is the same join and one-to-many, because an oil lease has several. 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 Well Completion Directory joins to Historical Ledger — Statewide Oil on District number = District and Lease number = Lease number — many rows here share a single row there.

is the lease whose completions are

The hop that gets a historical lease an API number, which no part of LAD001 carries: PDQ's completions for the lease. 157,875 of the 158,566 leases match. It stops at the lease -- the oil tape has no well number to take it further, and unlike the gas tape it has no well-database key either. 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 Well Completion Directory joins to Statewide Production Data — Oil on District number = District and Lease number = Lease number — many rows here share a single row there.

is the lease whose completions are

The hop that gets a production lease an API number, which no part of PDA001 carries: PDQ's completions for the lease. 4,827 of 5,000 sampled leases match. It stops at the lease -- the tape has no well number to take it 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 Well Completion Directory joins to Oil Ledger — Wells on District name = District and Lease number = Lease number — rows can match many rows in both directions.

is on the lease whose completions are

From a scheduled well to the API-numbered completions PDQ carries for its lease -- the hop that gets an oil ledger well an API number, which no ledger tape holds. 3,752 of 5,000 sampled wells match at lease level as the columns stand, and all 5,000 once the district's leading zero is stripped. It stops at the lease deliberately. Adding the well number matches every one of 5,000 sampled wells, but only after trimming: the ledger right-justifies the well number in six bytes and PDQ does not. 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 Well Completion Directory joins to Oil Detail Well on District name = District and Lease number = Lease number — rows can match many rows in both directions.

is on the lease whose completions are

The same hop for the wells inside multi-well units: from the detail tape to PDQ's completions for the lease, which carry the API number. 3,015 of 5,000 sampled detail wells match as the columns stand and all 5,000 once the district's leading zero is stripped -- the detail tape is two thirds District 08 and 8A, so the spelling costs it more than it costs the ledger. 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.