29 code sets

  • Drilling permit application type

    rrc.application_type

    What the operator asked permission to do. A single wellbore accumulates several of these over its life: an original DRILL, then a RE-ENTER or a PLUG-BACK years later. The pipeline that loads this data resolves the code on the way in, so the warehouse column holds the text below rather than the raw RRC code. Both are recorded here so the original filing can be read either way.

    15 values · used by 0 datasets

    • 01 DRILL
    • 02 DEEPEN-BELOW-CASING
    • 03 DEEPEN-WITHIN-CASING
    • 04 PLUG-BACK
    • 05 OTHER
    • 06 AMENDED-DRILL
    • See all 15 codes
  • Cement quantity unit

    rrc.cement_measurement

    The unit the casing record's cement amount is expressed in.

    3 values · used by 2 datasets

    • S Sacks
    • Y Cubic yards
    • F Feet
  • Casing type code

    rrc.completion_casing_type

    Which string of casing a completion casing row describes. The pipeline that loads this data resolves the code on the way in, so the warehouse column holds the text below rather than the raw RRC code. Both are recorded here so the original filing can be read either way.

    6 values · used by 0 datasets

    • 1 Conductor
    • 2 Surface
    • 3 Intermediate
    • 4 Conventional Production
    • 5 Tapered Production
    • 6 Other
  • Completion filing purpose

    rrc.completion_filing_purpose

    Why the G-1 or W-2 was filed. 'Well Record Only' matters: those filings carry no production test.

    7 values · used by 1 dataset

    • 1 Initial Potential
    • 2 Retest
    • 3 Reclass Oil to Gas
    • 4 Reclass Gas to Oil
    • 5 Reclass Injection to Producing
    • 6 Reclass Producing to Injection
    • See all 7 codes
  • Stimulation material and process code

    rrc.completion_material_process

    How the interval was treated. Code 2, Fracture, is the one people come here for: it is the closest thing RRC publishes to a frac flag. The pipeline that loads this data resolves the code on the way in, so the warehouse column holds the text below rather than the raw RRC code. Both are recorded here so the original filing can be read either way.

    6 values · used by 0 datasets

    • 1 Added with SWR 13. Acid
    • 2 Fracture
    • 3 Cement Squeeze
    • 4 Cast Iron Bridge Plug
    • 5 Retainer
    • 6 Other
  • Top-of-cement determination method

    rrc.completion_top_cement_determination

    How the operator established where the cement top is. This is the difference between a measured figure and an arithmetic one. The pipeline that loads this data resolves the code on the way in, so the warehouse column holds the text below rather than the raw RRC code. Both are recorded here so the original filing can be read either way.

    4 values · used by 0 datasets

    • 1 Calculation
    • 2 Temperature Survey
    • 3 Cement Evaluation Log
    • 4 Circulated
  • Completion type

    rrc.completion_type

    What physical work produced this completion.

    7 values · used by 1 dataset

    • 1 New Well
    • 2 Deepening
    • 3 Plug Back
    • 4 Sidetrack
    • 5 Horizontal
    • 6 Reentry
    • See all 7 codes
  • Completion well type

    rrc.completion_well_type

    Whether the completion is producing, shut in, or an injection well.

    4 values · used by 1 dataset

    • 1 Producing
    • 2 Shut-In Producer
    • 3 Active UIC
    • 4 Shut-In UIC
  • Texas county code

    rrc.county

    The three-digit county code RRC uses, which is also the county's FIPS code. `canonical_value` carries the full five-digit state plus county FIPS, so a county joins straight to Census geography. There are 254 Texas counties and 277 codes; the extras are offshore areas and administrative entries.

    277 values · used by 7 datasets

    • 001 Anderson
    • 003 Andrews
    • 005 Angelina
    • 007 Aransas
    • 009 Archer
    • 011 Armstrong
    • See all 277 codes
  • RRC district (printed designation)

    rrc.district

    The district as the Railroad Commission prints it: 01-06, 6E, 7B, 7C, 08, 8A, 09 and 10, plus 20 for statewide. This is what appears on permits, completions, ST-1 filings and inspection reports. It is not interchangeable with the internal district number. A column holding '11' means District 8A under the internal numbering and nothing at all under this one.

    14 values · used by 4 datasets

    • 01 District 01 — San Antonio
    • 02 District 02 — San Antonio
    • 03 District 03 — Houston
    • 04 District 04 — Corpus Christi
    • 05 District 05 — Kilgore
    • 06 District 06 — Kilgore
    • See all 14 codes
  • RRC district (internal number)

    rrc.district_number

    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.

    14 values · used by 15 datasets

    • 01 District 01 — San Antonio (internal 01)
    • 02 District 02 — San Antonio (internal 02)
    • 03 District 03 — Houston (internal 03)
    • 04 District 04 — Corpus Christi (internal 04)
    • 05 District 05 — Kilgore (internal 05)
    • 06 District 06 — Kilgore (internal 06)
    • See all 14 codes
  • Elevation reference point

    rrc.elevation_code

    The point the elevation was measured from. Depths in the same record are measured from this datum, so two wells are not comparable until you know which one each used.

    5 values · used by 2 datasets

    • GL Ground level
    • DF Derrick floor
    • KB Kelly bushing
    • RT Rotary table
    • GR Ground
  • H-15 inactive well test status

    rrc.h15_status

    Where a 25-year-plus inactive wellbore stands against its H-15 fluid-level or mechanical-integrity test requirement.

    9 values · used by 2 datasets

    • A Approved
    • C Compliant
    • D Delinquent
    • N Filed, not approved
    • P Pending
    • W W-3A extension
    • See all 9 codes
  • Horizontal well flag

    rrc.horizontal_flag

    A one-byte flag on the permit master. Only 'Y' means horizontal; anything else, including a blank, is treated as vertical. The pipeline that loads this data resolves the code on the way in, so the warehouse column holds the text below rather than the raw RRC code. Both are recorded here so the original filing can be read either way.

    2 values · used by 0 datasets

    • Y Horizontal
    • N Vertical
  • Coordinate datum code

    rrc.lat_lon_datum

    Which datum the coordinates on a completion packet were surveyed on. Ignoring this is worth up to about 200 metres of error in West Texas. The pipeline that loads this data resolves the code on the way in, so the warehouse column holds the text below rather than the raw RRC code. Both are recorded here so the original filing can be read either way.

    3 values · used by 0 datasets

    • 1 NAD27
    • 2 NAD83
    • 3 WGS84
  • Oil or gas schedule

    rrc.oil_gas_code

    Which schedule a lease is carried on. This is not decoration: an oil lease number and a gas lease number can be the same digits and mean different leases, so a lease key is only unique with this code and the district in it.

    2 values · used by 12 datasets

    • O Oil
    • G Gas
  • Oil or gas well type (completion packet)

    rrc.oil_gas_type_code

    Whether the completion packet describes a gas well or an oil well.

    2 values · used by 0 datasets

    • 1 Gas Well
    • 2 Oil Well
  • Open hole indicator

    rrc.open_hole_code

    Marks a producing interval that is open hole rather than perforated casing.

    1 value · used by 2 datasets

    • OH Open hole
  • Organization type

    rrc.organization_code

    The legal form the operator filed under. Codes 'H' and 'I' also appear in the warehouse but are not among the seven 88-level values ORA001 documents, so they are left unlabelled rather than guessed.

    7 values · used by 2 datasets

    • A Corporation
    • B Limited partnership
    • C Sole proprietor
    • D Partnership
    • E Trust
    • F Joint venture
    • See all 7 codes
  • P-5 organization status

    rrc.p5_status

    Whether an operator's Form P-5 organization report is current. An operator has to hold an active P-5 to be the operator of record on anything. The warehouse also contains 'H', 'R' and 'X' in this column. Those are not among the four 88-level values ORA001 documents for OROR-P-5-STATUS, so EZRRC does not guess at labels for them.

    4 values · used by 2 datasets

    • A Active
    • I Inactive
    • D Delinquent
    • S See remarks
  • Production method at test

    rrc.production_method

    How the well was being produced when the reported test was taken. The pipeline that loads this data resolves the code on the way in, so the warehouse column holds the text below rather than the raw RRC code. Both are recorded here so the original filing can be read either way.

    4 values · used by 0 datasets

    • 1 Flowed
    • 2 Lifted
    • 3 Pumped
    • 4 Jetted
  • UIC well class

    rrc.uic_class

    Which Underground Injection Control class the permit falls under.

    2 values · used by 1 dataset

    • 2 Injection / disposal well
    • 5 Storage, geothermal or brine well
  • UIC form status

    rrc.uic_form_status

    Whether the UIC form behind the permit record has been received and completed.

    3 values · used by 1 dataset

    • 0 Not received
    • I Incomplete
    • C Complete
  • Geothermal indicator

    rrc.uic_geothermal

    Whether the UIC record describes a geothermal well.

    2 values · used by 1 dataset

    • 0 Not geothermal
    • G Geothermal
  • UIC injection type (from 1995-06-01)

    rrc.uic_injection_type

    What is being injected and why, under the vocabulary in force from 1 June 1995. UIA010 also documents a superseded list used until 31 May 1995, in which 4 meant hydrocarbon storage, 5 meant gas storage and 6 meant miscellaneous. Records that predate the change carry the old meanings, so this code is not safe to interpret without a date.

    7 values · used by 1 dataset

    • 1 Disposal into a nonproductive zone
    • 2 Disposal into a productive zone
    • 3 Secondary or tertiary recovery
    • 4 Miscellaneous types
    • 5 R95 liquid storage — salt formation
    • 6 R96 gas storage — reservoir
    • See all 7 codes
  • Water or land location

    rrc.water_land_code

    Whether the wellbore sits on land, in a bay, in an inland waterway, or offshore.

    4 values · used by 1 dataset

    • L Land
    • B Bay / estuary
    • I Inland waterway
    • O Offshore
  • Century code

    rrc.wellbore_century_code

    WBA091 stores dates as separate century, year, month and day fields. This code says which century the two-digit year belongs to — the reason a raw read of the file produces wells completed in the year 19 and the year 20.

    4 values · used by 0 datasets

    • 0 No date
    • 1 1900s
    • 2 2000s
    • 3 2100s
  • Wellbore profile

    rrc.wellbore_profile

    The shape of the hole as declared on the completion packet. Anything outside 1-4 is written as 'Unknown'. The pipeline that loads this data resolves the code on the way in, so the warehouse column holds the text below rather than the raw RRC code. Both are recorded here so the original filing can be read either way.

    4 values · used by 0 datasets

    • 1 Horizontal
    • 2 Directional
    • 3 Vertical
    • 4 Sidetrack
  • Permit well code

    rrc.well_code

    What the permit says the well is for. This is the widest code list RRC uses and it goes well past oil and gas — uranium, cathodic protection, seismic shot holes and water supply wells all appear. The pipeline that loads this data resolves the code on the way in, so the warehouse column holds the text below rather than the raw RRC code. Both are recorded here so the original filing can be read either way.

    34 values · used by 0 datasets