Texas RRC District Code Conversion: Why File Values 07-14 Need a Crosswalk

Direct answer for mineral owners

Use a Texas RRC district conversion only when the exact data dictionary for the file supplies it. Store the incoming 01-14 value as text, preserve it unchanged, place the translated label in a separate field, and retain the dictionary, version or access date, conversion status, and exception note. Do not treat reserved 8B as currently accepted or apply the T-1-specific 6E/06 rule outside that guide.

Key takeaways for mineral owners

• The field-information and tight-sands dictionaries map numeric table values 01-14 to district labels, but the mapping is source-specific.
• Eight rows are not identity conversions: 07→6E, 08→7B, 09→7C, 10→08, 11→8A, 12→8B, 13→09, and 14→10.
• The dictionaries mark 8B reserved for future use, and the W-10/G-10 accepted-code list omits it.
• Store raw and translated codes as text so leading zeroes and letters survive imports and exports.
• The T-1 guide permits 06 or 6E for a narrow East Texas oil-field reporting context; it is not a global rewrite rule.

Source-scoped conversion, not a property conclusion. This page explains how selected Texas Railroad Commission data dictionaries translate district values. It does not identify a county, field boundary, well, lease, tract, unit, owner, title interest, royalty account, production result, reserve, private value, offer, buyer action, or transaction outcome. MRX provides educational information and resources only and does not buy mineral rights.

The direct answer is: convert a Texas RRC file district value only when the exact data dictionary for that file authorizes the conversion. Keep the incoming value unchanged in a raw-text field. Put the translated district label in a second text field. Record the dictionary, version or access date, conversion status, and any exception in adjacent columns.

This matters because two official RRC data dictionaries use table values 01 through 14, while the matching operational district labels can contain different digits or letters. A blind identity import would turn 07 into district 07 instead of 6E, for example. A global replacement rule is also unsafe: another RRC file, form, screen, or EDI guide may define its field differently.

The source-scoped district conversion

The RRC Oil and Gas Field Information data dictionary supplies a field-table conversion, and the RRC Tight Sands Gas Leases data dictionary independently supplies the same district-column conversion. In those two documented contexts, use this crosswalk:

Raw table or file value	Translated district label	Conversion status	Import note
01	01	Identity	Preserve both as two-character text
02	02	Identity	Preserve both as two-character text
03	03	Identity	Preserve both as two-character text
04	04	Identity	Preserve both as two-character text
05	05	Identity	Preserve both as two-character text
06	06	Identity	Do not silently substitute 6E
07	6E	Changed	Letter-bearing translated label
08	7B	Changed	Letter-bearing translated label
09	7C	Changed	Letter-bearing translated label
10	08	Changed	Leading zero required in translated label
11	8A	Changed	Letter-bearing translated label
12	8B	Reserved	Retain the dictionary note; do not call it currently accepted
13	09	Changed	Leading zero required in translated label
14	10	Changed	Numeric-looking but not an identity conversion

This is not a statement that every RRC system stores district values this way. It is a controlled translation for the two named dictionary contexts. Before applying it to another data source, locate that source’s own field definition and accepted-value list.

Why values 07-14 cannot pass through unchanged

Values 01 through 06 happen to equal their translated labels in these dictionaries. That pattern ends at 07. Eight later rows are non-identity mappings, including letter-bearing outputs and outputs that begin with zero.

That creates two predictable import failures. First, a pipeline that assumes raw = district will store the wrong label for all eight changed rows. Second, a spreadsheet or database that coerces either side to a number can discard a leading zero and cannot represent labels such as 6E, 7B, 7C, or 8A as a reliable district code.

The current RRC Oil and Gas Counties and Districts page visibly uses alphanumeric labels including 7B, 7C, and 8A. That supports the output format. It does not make the page a universal translation dictionary, and it does not authorize a private-property conclusion from a district label.

Preserve raw and translated values in separate fields

An auditable import keeps the source value and the interpretation separate. A minimal row should include:

Field	Entry rule	Why retain it
district_raw	Copy the incoming value exactly as delivered	Preserves the source record and makes reprocessing possible
district_translated	Apply only the attached source dictionary	Separates interpretation from the original bytes
district_dictionary	Store exact document name or controlled identifier	Shows which rule authorized the translation
dictionary_version	Record stated version; otherwise use access date	Prevents an undated rule from appearing timeless
conversion_status	identity, changed, reserved, unmapped, or error	Makes exceptions machine-reviewable
exception_note	Explain reserved, invalid, blank, or out-of-scope values	Prevents silent fallback behavior
validated_at	Date, time, and timezone of the check	Distinguishes validation time from a record effective date

Do not overwrite district_raw after conversion. If a source dictionary changes, the retained raw value lets a reviewer rerun the translation and compare results without reconstructing the original import.

Store every code as text

The RRC W-10/G-10 EDI specification defines District Code as Varchar (2) and lists two-character accepted values that include numeric-looking and alphanumeric labels. A text type protects both kinds.

Use a two-character string or a more descriptive text field with a separate length check. Do not use integer conversion, scientific-notation detection, arithmetic comparison, or automatic whitespace cleanup that can change the source. At minimum, validate that:

• the raw value is exactly what the file supplied;
• a numeric-looking code retains its leading zero;
• letters retain their original case unless the source explicitly defines normalization;
• the translated field is populated only after a matching dictionary row is found; and
• an unknown or blank code becomes unmapped or error, not a guessed district.

For the broader distinction among district code, county code, field number, field name, and page-specific FIPS labels, use Texas RRC District, County, and Field Codes: A Source-Label Crosswalk. Article 299 owns those non-equivalence rules. This page owns only district-value translation for a documented file context.

Keep 8B in the reserved lane

Both conversion tables label 8B reserved for future use. The reviewed W-10/G-10 accepted-code list does not include it. Those facts support a narrow import rule: a raw value of 12 can be translated to a dictionary output of 8B, but the resulting row must remain reserved rather than accepted.

Do not delete the row, silently map it to another district, or treat the word “future” as proof that activation has occurred. A current filing, API, or downstream workflow needs its own current accepted-value authority. If a later source activates 8B, record that source and effective context instead of rewriting the historical dictionary.

Keep the T-1 6E/06 exception attached to its guide

The RRC T-1 EDI User Guide distinguishes normal alphanumeric district designations from a special numeric district field. It also states, in its reporting context, that 6E refers to the East Texas oil field in district 06 and that oil production for that field may be reported using either 06 or 6E.

That is a guide-specific exception, not permission to replace every 06 with 6E or every 6E with 06. Preserve the form or EDI transaction, field name, guide version, and rule that allowed the submitted value. In the conversion table above, raw 06 remains translated 06; raw 07 translates to 6E because that is what the two named dictionaries specify.

A deterministic conversion and checksum workflow

A controlled pipeline can make the decision reproducible:

1. Fingerprint the incoming file and its exact data dictionary before transformation.
2. Read the district column as text and preserve the raw value byte-for-byte where practical.
3. Match the dictionary by source name, table name, field name, and version or access date.
4. Look up the raw value without numeric coercion.
5. Write the translated value to a separate field and assign identity, changed, reserved, unmapped, or error.
6. Retain the source-row number or stable record reference without publishing sensitive owner identifiers.
7. Count each status and compare the total to the input-row count.
8. Export an exception file for every reserved, unmapped, blank, malformed, or duplicate source row.
9. Fingerprint the transformed output and store the validation timestamp and reviewer or process identity.

The most useful reconciliation equation is simple:

input rows = identity + changed + reserved + unmapped + error

If the totals do not match, stop the import. Do not hide the difference in a catch-all district, discard rows, or force values through the nearest-looking code.

This workflow validates the translation process. It does not validate a field boundary, well, lease, tract, title chain, production record, royalty statement, reserve estimate, or mineral value.

What a converted district code does not prove

A successfully translated district label does not independently establish:

• that a county, field, well, lease, tract, unit, or deed belongs to the same private asset;
• field or reservoir boundaries, acreage allocation, geology, or engineering conclusions;
• mineral ownership, title quality, authority, royalty entitlement, or payment responsibility;
• production completeness, forecast, reserves, decline, or future development;
• tax treatment, appraisal result, private value, offer quality, or buyer qualification; or
• that two records describe the same interest because their district labels match.

For a query-specific record of inputs and outputs, use the Texas RRC G-10/W-10 Well Status Report Query Retrieval Provenance Worksheet. For broader search organization, use How to Build a Texas Mineral Production Record Locator Sheet. Neither job is replaced by this file-conversion crosswalk.

Controlled source record

Five official source objects were retrieved on August 31, 2026 and retained as 1,481,362 controlled bytes.

Source object	Bytes	SHA-256 prefix	Bounded role
RRC Oil and Gas Field Information data dictionary	74,568	b140a481947d	Field-table values 01-14, translated labels, and reserved 8B
RRC Tight Sands Gas Leases data dictionary	257,787	0e076c614bc5	Independent district-column conversion and reserved 8B
RRC T-1 EDI User Guide	508,413	73288045aa6c	Normal alphanumeric and special numeric fields plus the guide-specific 6E/06 note
RRC W-10/G-10 EDI specification	573,262	0453ec94b9d3	Varchar (2) field and accepted-code list omitting reserved 8B
RRC Oil and Gas Counties and Districts	67,332	eb438c443e17	Current public display of alphanumeric district labels

Claim ledger and stop conditions

Claim ID	Supported statement	Allowed evidence label	Stop condition
C300-01	Two RRC dictionaries supply the same 01-14 source-scoped conversion	RRC-DISTRICT-DICTIONARY	Do not apply the table to another source without its own definition
C300-02	Eight rows from 07 through 14 are not identity conversions	RRC-DISTRICT-MAPPING	Do not pass changed rows through unchanged or guess an unmapped value
C300-03	The dictionaries mark 8B reserved for future use	RRC-RESERVED-CODE	Do not call 8B currently accepted without current source-specific authority
C300-04	The W-10/G-10 field is Varchar (2) and accepts alphanumeric labels	RRC-DISTRICT-TYPE	Do not coerce the code to a number or strip leading zeroes
C300-05	The T-1 guide permits 06 or 6E in a narrow East Texas oil-field reporting context	RRC-T1-EXCEPTION	Do not globalize the exception across files, fields, forms, or districts
C300-06	Current RRC pages visibly use alphanumeric district labels	RRC-CURRENT-LABEL	Do not infer county, field, asset, ownership, production, or value relationships

Research scope and review boundaries

Before using a conversion in an owner-specific workflow, verify the exact source file, table, field name, dictionary, version or access date, raw value, translated value, conversion status, exception note, and downstream accepted-value authority. Questions about field boundaries, wells, leases, geology, engineering, title, tax, accounting, production, valuation, or a transaction belong with the responsible official source and qualified advisers.

Sources reviewed for this article

• Texas RRC: Oil and Gas Field Information data dictionary
• Texas RRC: Tight Sands Gas Leases data dictionary
• Texas RRC: T-1 EDI User Guide
• Texas RRC: W-10/G-10 EDI specifications
• Texas RRC: Oil and Gas Counties and Districts

Related mineral-rights research guides

• Texas Mineral Rights Guide
• Texas RRC District, County, and Field Codes: A Source-Label Crosswalk
• Texas RRC G-10/W-10 Well Status Report Query Retrieval Provenance Worksheet
• How to Build a Texas Mineral Production Record Locator Sheet

Educational information only. This article explains source-scoped regulatory data conversion and evidence boundaries. It is not legal, title, land, tax, appraisal, accounting, engineering, geological, investment, or financial advice; it is not a field delineation, property match, ownership opinion, production conclusion, valuation, offer, or transaction recommendation. Verify owner-specific facts with the responsible office and qualified advisers. MRX provides educational information and resources only and does not buy mineral rights.

Frequently asked questions

Why do Texas RRC file values 07 through 14 need a crosswalk?

In the two documented data-dictionary contexts, those table values do not equal the displayed district labels. For example, 07 translates to 6E and 10 translates to 08. Use the exact dictionary supplied with the file.

Should a data import overwrite the raw Texas RRC district value?

No. Preserve the incoming value unchanged and write the translated label to a separate field. Retain the source dictionary, version or access date, status, and any exception note so the conversion can be audited.

Is 8B a currently accepted Texas RRC filing code?

The two conversion tables mark 8B reserved for future use, while the reviewed W-10/G-10 accepted-code list omits it. Do not describe it as currently accepted without current source-specific authority.

Are Texas RRC district codes numeric or text?

Treat them as text. The W-10/G-10 specification defines District Code as Varchar (2), and valid labels can contain leading zeroes or letters, including 6E, 7B, 7C, and 8A.

Can 06 and 6E always be used interchangeably?

No. The reviewed T-1 guide permits either code for a narrow East Texas oil-field reporting situation. Keep that exception attached to the guide and filing context that states it.

Sources reviewed for this article

• Texas RRC Oil and Gas Field Information data dictionary (accessed 2026-08-31)
• Texas RRC Tight Sands Gas Leases data dictionary (accessed 2026-08-31)
• Texas RRC T-1 EDI User Guide (accessed 2026-08-31)
• Texas RRC W-10/G-10 EDI specifications (accessed 2026-08-31)
• Texas RRC Oil and Gas Counties and Districts (accessed 2026-08-31)