PDQ Field Directory

PDQ Field Directory joins to Oil & Gas Field Rules on Field number — one row here matches one row there.

is the field

The field rules to the production system's field directory, on the eight-digit field number, zero-padded identically on both sides. 65,826 of the 65,836 fields with rules are in the directory, and all 65,826 directory fields have a rules row — the ten that do not match are fields RRC has designated since the directory was last cut. From there the field's monthly production is one more join: 41,144 of the 65,836 fields have a row in the PDQ field cycle table.

PDQ Field Directory joins to Statewide Field Data on District number and Field number — one row here matches one row there.

is the same field as

The FL tape's field master and PDQ's field directory are the same 65,826 fields, district for district: every fl_field row finds exactly one PDQ row and every PDQ row finds exactly one fl_field row. Both write the district as the internal number, so that half needs no translation. Worth having in both directions. PDQ carries the field name, the wildcat flag and the derived rule type; the FL tape carries the rules themselves, the allocation formula, the allowables and the monthly production. 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 Field Directory joins to PDQ Field Production by Cycle on Field number — one row here matches many rows there.

totals the field

Field production is published against an eight-digit number and nothing else. The field directory is the only place the name, class, discovery date and wildcat flag live. Exact on all 5,000 sampled rows. A field that crosses a district boundary appears under more than one district, so sum across districts for a field total.

PDQ Field Directory joins to Oil & Gas Field Name & Numbers on Field number = Field number text — one row here matches one row there.

is the same field as

The published name list and the production system's own field directory are the same 65,826 fields exactly: every row here finds one PDQ row and every PDQ row finds one row here. Both write the number as eight zero-padded characters, so the comparison is made as printed with no cast. They agree completely on what they share, which is itself the finding: the field name is identical on all 65,826 rows and so is the printed district. What each adds is different. PDQ carries the wildcat flag, the H2S flag and the derived rule type, and a SEPARATE county number for the oil and the gas schedule; this file carries one county code, the multi-county flag and the OIL / GAS / O & G classification. On 65,815 of the 65,826 fields the county here matches at least one of PDQ's two (33,721 the oil one, 41,853 the gas one); the eleven that match neither are the statewide WILDCAT rows whose county code is 000.

PDQ Field Directory joins to Oil Ledger on Field number — one row here matches one row there.

is the field

The ledger's field number resolved to the field directory, which is where the field's name and class live. Measured over the whole table rather than a sample, because 33,939 rows can afford it: all 33,939 field records match a directory entry. District is deliberately not in the join, and it costs nothing to leave out. Field numbers are unique on this tape -- 33,939 numbers in 33,939 rows, none carried in two districts -- and the directory names the same district on every one of them, so adding it would neither narrow the join nor drop a row. Leaving it out also spares the reader the 06E-to-6E translation every other PDQ join here needs. 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 Field Directory joins to Gas Ledger on Field number — one row here matches one row there.

is the field

The gas ledger's field number resolved to the field directory for its name and class. All 5,000 sampled gas field records 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 Field Directory joins to Certificate of Authorization P-4 (Oil and Gas) on Field number — one row here matches many rows there.

is in the field

The lease's CURRENT field, resolved to a field name and its district. Every one of the 548,099 leases carries a field number -- no nulls, no zeros -- and 547,747 of them find a directory row, over 61,768 distinct fields. The field a lease was in at the time of an OLDER filing is info_field_no on p4_filing, which reaches the same directory: 48,048 of its 48,150 distinct values are in it. 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 Field Directory joins to PDQ Lease Production by Cycle on Field number — one row here matches many rows there.

produced from the field

The eight-digit field number resolved to a field name, class, discovery date and rules flags.

PDQ Field Directory joins to Gas Annual Report Field Table on District name = District and Field name = Field name — rows can match many rows in both directions.

is the field

The annual gas report has no field number, only a name, so this is the route to one. Matched on the printed district and the exact field name, 42,125 of the 42,138 annual rows find a directory entry — the thirteen that do not are the twelve 'DISTRICT TOTAL' rows and the one ' TEXAS TOTALS' row RRC writes into the field-name column. A name is not a key: a handful of districts carry two directory fields under one name, so 42,105 distinct district-and-name pairs produce 42,188 matched rows. Check the field number you get back before you build on it.

PDQ Field Directory joins to UIC Database (ASCII) on Field number — one row here matches many rows there.

injects into the field

The permitted injection field, resolved to a field name.