PDQ Field Directory
Queryable CSV
The field number to field name lookup, with class, discovery date and rules flags.
Get the data
Free. You will be asked to confirm an email address before the files are built — that is the only gate, and it is there so we can tell you when a large export is ready.
What this is
One of the sixteen delimited tables inside the monthly Production Data Query dump. RRC publishes the dump as a single archive; EZRRC publishes each table inside it separately so you can take the one you need instead of a 3.6 GB zip.
65,000 fields: number, name, district, class, wildcat flag, hydrogen sulphide flag, salt dome flag, offshore code, discovery dates and the derived rule type — separately for the oil and gas schedules, because the same field can be governed differently on each.
Nothing else in the production data spells a field name out.
What you can do with it
Turn eight-digit field numbers into names, find every field discovered in a given year, and identify sour or offshore fields.
Gotchas
Almost every attribute exists twice, prefixed o_ for the oil schedule and g_ for the gas schedule. They frequently differ.
A field number is not unique across districts.
Record layout
33 columns.
pdq_og_field_dw
33 columns
| # | Column | Type | RRC name | Meaning | Lookup |
|---|---|---|---|---|---|
| 1 |
field_no
key
join
|
text | — | The eight-digit RRC field number. The field's name is not in most files; join to the field directory to get it. | — |
| 2 |
field_name
|
text | — | Field name. | — |
| 3 |
district_no
join
|
text | — | RRC's INTERNAL district number, 01 to 14 plus 20 for statewide. This is not the district name the industry uses: internal 07 is District 6E, 08 is 7B, 09 is 7C, 10 is District 08, 11 is 8A, 13 is 09 and 14 is District 10. Join to the district directory rather than reading it as a label. | RRC district (internal number) |
| 4 |
district_name
|
text | — | RRC district as the industry writes it, e.g. 7B, 8A, 6E. | — |
| 5 |
field_class
|
text | — | A field is classified as an oil field, a gas field, or as both oil and gas. If a gas field is associated with an oil field, the oil and gas fields will usually have the same field number; they are indicated in this data item by the value "b". If a gas field is associated with an oil field, but the related oil field has a different field number, the data item "fl-assoc-oil-field number" will act as a pointer to the related oil field number. The actual process of classifying a field depends initially on the gas to oil ratio (GOR) of the first well but may also result from administrative hearings. However, as additional well discoveries provide more information about the field, the creation of a related field may become necessary. gas field value "G" oil field value "O" associated field value "B" (both oil and gas) Note: If the field is both oil and gas, and the fl- assoc-oil-field-number data item has a number greater than zeroes, then there exists at least one associated gas field with a field number that is different than its related oil field. | — |
| 6 |
field_h2s_flag
|
text | — | The values below indicates if hydrogen sulfide is present in the well. N - No hydrogen sulfide present Y - Hydrogen sulfide present E -Hydrogen sulfide present (but exempt from filing) The Railroad Commission must be knowledgeable of hydrogen sulfide presence. An operator submits to the Commission a Form H-9 (Certificate of Compliance Statewide Rule 36). | — |
| 7 |
field_manual_rev_flag
|
text | — | Indicates field rules require manual analysts review of the field rules. | — |
| 8 |
wildcat_flag
|
text | — | Denotes that there is no known zone of production for this field. Values = Y & N | — |
| 9 |
o_derived_rule_type_code
|
text | — | Series of codes derived from the field type and field location. | — |
| 10 |
g_derived_rule_type_code
|
text | — | Series of codes derived from the field type and field location. | — |
| 11 |
o_rescind_dt
|
date | — | The oil rule suspended date indicates in century, year, month and day format when the field rules were rescinded for a oil field. | — |
| 12 |
g_rescind_dt
|
text | — | The oil rule suspended date indicates in century, year, month and day format when the field rules were rescinded for an oil field. | — |
| 13 |
o_salt_dome_flag
|
text | — | Flag that indicates salt dome. A salt dome is a naturally occurring formation of salt which causes oil traps. The RRC determines whether a field should be classified as a salt dome on the basis of engineering and geologic evidence. If a field is classified as a salt dome, the statewide spacing rule does not apply to the field. | — |
| 14 |
g_salt_dome_flag
|
text | — | A salt dome is a naturally occurring formation of salt that causes oil traps. The RRC determines whether a field should be classified as a salt dome on the basis of engineering and geologic evidence. If a field is classified as a salt dome, the statewide spacing rule does not apply to the field. | — |
| 15 |
o_offshore_code
|
text | — | Surface location information. It takes values from the ew_county_lkup table for offshore counties when the surface location is 'offshore'. | — |
| 16 |
g_offshore_code
|
text | — | The offshore code indicates the geographic surface of a field using the location of the discovery well as a point of reference. The state of Texas offshore encompasses the area in the Gulf of Mexico from the coastline to three leagues (approx. 10 miles) out of the gulf. LAND VALUE "L" BAYS-ESTUARIES VALUE "B" STATE-OFFSHORE VALUE "SO" LAND-BAYS-ESTUARIES VALUE "LB" BAYS-ESTUARIES-OFFSHORE VALUE "BO" LAND-BAYS-ESTUARIES-OFFSHORE VALUE "AL" STATE-FEDERAL VALUE "SF" | — |
| 17 |
o_dont_permit
|
text | — | Flag that denotes if permit can be granted or not. | — |
| 18 |
g_dont_permit
|
text | — | Flag that denotes if permit can be granted or not. | — |
| 19 |
o_noa_man_rev_rule
|
text | — | Notice of Application Manual Review Rule. | — |
| 20 |
g_noa_man_rev_rule
|
text | — | Notice of Application Manual Review Rule. | — |
| 21 |
o_county_no
|
text | — | The county number (no.) is a 3-digit number: The Railroad Commission assigns a number to each onshore county; the American Petroleum Institute (API) assigns a number to each offshore county. | — |
| 22 |
g_county_no
|
text | — | The county number (no.) is based on 3-digit numbers: The Railroad Commission assigns a number to each onshore county; the American Petroleum Institute (API) assigns a number to each offshore county. The first 254 number of the code are odd, and indicate onshore counties only. The remaining 23 numbers are both odd and even, and indicate offshore counties. | — |
| 23 |
o_discovery_dt
|
date | — | The discovery date of the first well in the oil field; it is formatted in cc/yy format where cc=century, and yy=year, then further broken down into mm and dd format where mm=month and dd=day. | — |
| 24 |
g_discovery_dt
|
date | — | The discovery date of the first well in the gas field; it is formatted in cc/yy format where cc=century, and yy=year, then further broken down into mm and dd format where mm=month and dd=day. | — |
| 25 |
o_sched_remarks
|
text | — | Comments on the schedule table. | — |
| 26 |
g_sched_remarks
|
text | — | Remarks that print on the gas proration schedule. | — |
| 27 |
o_comments
|
text | — | Remarks. | — |
| 28 |
g_comments
|
text | — | Remarks for the field. | — |
| 29 |
create_by
|
text | — | User or process that created the row in RRC's system. | — |
| 30 |
create_dt
|
date | — | When the row was created in RRC's system. | — |
| 31 |
modify_by
|
text | — | User or process that last changed the row in RRC's system. | — |
| 32 |
modify_dt
|
date | — | When the row was last changed in RRC's system. | — |
| 33 |
ingested_at
|
timestamptz | — | When the upstream pipeline last wrote this row. Not an RRC field — it is EZRRC's provenance stamp, and it is what the freshness badge is measured against. | — |
Code lookups used here
Every coded column in this dataset resolves to a real lookup table, so
a well code of G can be read as what it actually means.
RRC district (internal number) 14 values
Read by district_no
RRC's internal sequential district numbering, 01 to 14 plus 20 for statewide. The production data, the UIC database and the high-cost gas certifications all use this. Internal 07 is District 6E, 08 is 7B, 09 is 7C, 10 is District 08, 11 is 8A, 13 is 09 and 14 is District 10. There is no internal 12.
| Code | Means |
|---|---|
01 |
District 01 — San Antonio (internal 01) Internal district number 01, which RRC prints as District 01 and administers from San Antonio. |
02 |
District 02 — San Antonio (internal 02) Internal district number 02, which RRC prints as District 02 and administers from San Antonio. |
03 |
District 03 — Houston (internal 03) Internal district number 03, which RRC prints as District 03 and administers from Houston. |
04 |
District 04 — Corpus Christi (internal 04) Internal district number 04, which RRC prints as District 04 and administers from Corpus Christi. |
05 |
District 05 — Kilgore (internal 05) Internal district number 05, which RRC prints as District 05 and administers from Kilgore. |
06 |
District 06 — Kilgore (internal 06) Internal district number 06, which RRC prints as District 06 and administers from Kilgore. |
07 |
District 6E — Kilgore (internal 07) Internal district number 07, which RRC prints as District 6E and administers from Kilgore. |
08 |
District 7B — Abilene (internal 08) Internal district number 08, which RRC prints as District 7B and administers from Abilene. |
09 |
District 7C — San Angelo (internal 09) Internal district number 09, which RRC prints as District 7C and administers from San Angelo. |
10 |
District 08 — Midland (internal 10) Internal district number 10, which RRC prints as District 08 and administers from Midland. |
11 |
District 8A — Midland (internal 11) Internal district number 11, which RRC prints as District 8A and administers from Midland. |
13 |
District 09 — Wichita Falls (internal 13) Internal district number 13, which RRC prints as District 09 and administers from Wichita Falls. |
14 |
District 10 — Pampa (internal 14) Internal district number 14, which RRC prints as District 10 and administers from Pampa. |
20 |
District 20 — State Wide (internal 20) Internal district number 20, which RRC prints as District 20 and administers from State Wide. |
Source: Generated from texas.pdq_gp_district.district_no
What this joins to
The Railroad Commission never states these keys anywhere in the files. They are the reason the data is hard to use, so here they are with the exact columns on both sides.
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-cycle.field_no = pdq-field-directory.field_no
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-lease-cycle.field_no = pdq-field-directory.field_no
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.
uic-database-ascii.field_no = pdq-field-directory.field_no
Where this comes from
- Published by
- Texas Railroad Commission — the original page
- Original format
- CSV Comma-separated text.
- Update cadence
- Updated once a month (Last Saturday each month, with the PDQ dump.)
- RRC download link
- GoAnywhere MFT
- Record layout manuals
- Our table
texas.pdq_og_field_dw
EZRRC is an independent mirror of public-domain data published by the Texas Railroad Commission. It is not affiliated with or endorsed by the RRC. For any legal or regulatory purpose, verify against the official RRC release.