Static map view
Shows where a route, point, or facility sits. Useful for orientation, but often separated from source tables.
EnergyNetWatch
Midstream infrastructure data for pipeline permits, GIS routes, and source records
Turn midstream permits, GIS route evidence, and facility records into review-ready infrastructure workflows.
EnergyNetWatch connects pipeline permits, GIS route evidence, facility records, operators, counties, source dates, and public-record context so teams can move from a map signal to a record they can review, qualify, export, monitor, or access through API workflows.
Visual proof
Data fields
What midstream infrastructure data includes
EnergyNetWatch is useful when infrastructure records become structured enough to review, filter, export, monitor, and explain. These fields turn a map layer into a working dataset.
| Data field | Example value | Why it is useful |
|---|---|---|
| Source family | Texas RRC T-4 pipeline permit | Separates pipeline permit records from drilling permits, facility records, production records, and federal docket signals. |
| Operator / applicant | Firebird Energy II LLC | Gives commercial, operating, and account ownership context. |
| Asset type | Pipeline | Helps separate pipeline signals from wells, tank batteries, plants, compressor stations, and other facilities. |
| Commodity | Natural gas | Helps teams separate gas gathering, crude, liquids, and other route contexts. |
| Source date | 2026-04-15 | Anchors the record to the source timeline instead of only the platform observation date. |
| Date basis | Source record | Clarifies whether the date comes from the public source, a platform observation, or another derived layer. |
| GIS match status | Route matched | Shows whether a permit row has been connected to route evidence. |
| Route segment count | 13 segments | Gives a quick measure of mapped route evidence for the selected record. |
| Diameter range | 4.5-10.75 inches | Helps qualify whether the line looks like small gathering, larger transport, or another infrastructure profile. |
| Counties | Midland and Upton counties | Supports county, basin, sales-territory, and nearby activity review. |
| Coordinates | 31.5618, -102.2057 | Lets analysts connect the record to map context and nearby records. |
| Status confidence | Known | Helps users understand whether the row is clean enough for follow-up or needs source review. |
Data field
Source family
Example value
Texas RRC T-4 pipeline permit
Why it is useful
Separates pipeline permit records from drilling permits, facility records, production records, and federal docket signals.
Data field
Operator / applicant
Example value
Firebird Energy II LLC
Why it is useful
Gives commercial, operating, and account ownership context.
Data field
Asset type
Example value
Pipeline
Why it is useful
Helps separate pipeline signals from wells, tank batteries, plants, compressor stations, and other facilities.
Data field
Commodity
Example value
Natural gas
Why it is useful
Helps teams separate gas gathering, crude, liquids, and other route contexts.
Data field
Source date
Example value
2026-04-15
Why it is useful
Anchors the record to the source timeline instead of only the platform observation date.
Data field
Date basis
Example value
Source record
Why it is useful
Clarifies whether the date comes from the public source, a platform observation, or another derived layer.
Data field
GIS match status
Example value
Route matched
Why it is useful
Shows whether a permit row has been connected to route evidence.
Data field
Route segment count
Example value
13 segments
Why it is useful
Gives a quick measure of mapped route evidence for the selected record.
Data field
Diameter range
Example value
4.5-10.75 inches
Why it is useful
Helps qualify whether the line looks like small gathering, larger transport, or another infrastructure profile.
Data field
Counties
Example value
Midland and Upton counties
Why it is useful
Supports county, basin, sales-territory, and nearby activity review.
Data field
Coordinates
Example value
31.5618, -102.2057
Why it is useful
Lets analysts connect the record to map context and nearby records.
Data field
Status confidence
Example value
Known
Why it is useful
Helps users understand whether the row is clean enough for follow-up or needs source review.
Example records
Route-matched pipeline permit examples
These public-record examples show how raw Texas T-4 pipeline permit rows become more useful when connected to GIS route evidence and operator context.
| Permit / record | Operator | Counties | Commodity / class | GIS route evidence | Practical use |
|---|---|---|---|---|---|
| Firebird Energy II example | Firebird Energy II LLC | Midland, Upton | Natural gas / private pipeline | Route matched; 13 segments; 4.5-10.75 in. | Review gas infrastructure signal by operator, county, source date, and matched route context. |
| T-4 permit 10740 | Civitas Permian Operating, LLC | Glasscock, Howard | Gas / private pipeline | 15 segments; 4.5-16 in.; Foster/Tubb gas gathering | Connect a T-4 route lead to nearby permits, reported spuds, wells, and production context. |
| T-4 permit 10748 | Enterprise Products Operating LLC | Martin, Midland | Gas / private pipeline | 26 segments; 4.5-16 in.; Nail Ranch | Track a midstream operator signal in core Permian counties with route evidence. |
| T-4 permit 10765 | Diamondback E&P LLC | Midland | Gas / private pipeline | 14 segments; 4.5 in.; Buchanan Ranch Residue | Read operator-linked infrastructure context alongside Diamondback drilling and well activity. |
| T-4 permit 10766 | Plains Pipeline L.P. | Culberson, Loving, Winkler | Liquid / common carrier | 43 segments; 4.5-16 in.; Alpha Gathering | Review multi-county liquid infrastructure across Delaware Basin counties. |
Permit / record
Firebird Energy II example
Operator
Firebird Energy II LLC
Counties
Midland, Upton
Commodity / class
Natural gas / private pipeline
GIS route evidence
Route matched; 13 segments; 4.5-10.75 in.
Practical use
Review gas infrastructure signal by operator, county, source date, and matched route context.
Permit / record
T-4 permit 10740
Operator
Civitas Permian Operating, LLC
Counties
Glasscock, Howard
Commodity / class
Gas / private pipeline
GIS route evidence
15 segments; 4.5-16 in.; Foster/Tubb gas gathering
Practical use
Connect a T-4 route lead to nearby permits, reported spuds, wells, and production context.
Permit / record
T-4 permit 10748
Operator
Enterprise Products Operating LLC
Counties
Martin, Midland
Commodity / class
Gas / private pipeline
GIS route evidence
26 segments; 4.5-16 in.; Nail Ranch
Practical use
Track a midstream operator signal in core Permian counties with route evidence.
Permit / record
T-4 permit 10765
Operator
Diamondback E&P LLC
Counties
Midland
Commodity / class
Gas / private pipeline
GIS route evidence
14 segments; 4.5 in.; Buchanan Ranch Residue
Practical use
Read operator-linked infrastructure context alongside Diamondback drilling and well activity.
Permit / record
T-4 permit 10766
Operator
Plains Pipeline L.P.
Counties
Culberson, Loving, Winkler
Commodity / class
Liquid / common carrier
GIS route evidence
43 segments; 4.5-16 in.; Alpha Gathering
Practical use
Review multi-county liquid infrastructure across Delaware Basin counties.
These are source-level infrastructure leads. A route match does not automatically prove in-service status, final construction, economics, or commercial exposure. It gives the team a better starting point than a flat permit list.
Workflow
Permit -> map -> GIS evidence -> review
The map is the starting point. The report should show what source record supports the lead and what a team can check next.
| Workflow step | EnergyNetWatch data layer | What the user can do |
|---|---|---|
| Find the source record | T-4 permit, facility record, gas plant record, or docket signal | Identify the operator, source family, location, and date basis. |
| Match to map context | GIS route, project point, county, coordinate, or facility location | See where the infrastructure signal sits and what area it affects. |
| Qualify the record | GIS match status, route segments, diameter, commodity, confidence, facility type | Separate strong leads from rows that still need source review. |
| Connect nearby activity | Wells, drilling permits, reported spuds, production, facility records | Understand whether the infrastructure signal sits near active upstream or facility activity. |
| Move to action | Export, saved workflow, alert, API access, account review | Turn a map signal into a repeatable review process. |
Workflow step
Find the source record
EnergyNetWatch data layer
T-4 permit, facility record, gas plant record, or docket signal
What the user can do
Identify the operator, source family, location, and date basis.
Workflow step
Match to map context
EnergyNetWatch data layer
GIS route, project point, county, coordinate, or facility location
What the user can do
See where the infrastructure signal sits and what area it affects.
Workflow step
Qualify the record
EnergyNetWatch data layer
GIS match status, route segments, diameter, commodity, confidence, facility type
What the user can do
Separate strong leads from rows that still need source review.
Workflow step
Connect nearby activity
EnergyNetWatch data layer
Wells, drilling permits, reported spuds, production, facility records
What the user can do
Understand whether the infrastructure signal sits near active upstream or facility activity.
Workflow step
Move to action
EnergyNetWatch data layer
Export, saved workflow, alert, API access, account review
What the user can do
Turn a map signal into a repeatable review process.
Snapshot examples
Sample current snapshot metrics
Public examples reviewed in May 2026. Counts below are snapshot examples from cited EnergyNetWatch public-record workflows, not universal live totals or all-state parity claims. Source coverage and refresh timing vary by dataset.
| Snapshot metric | Public example | What it means |
|---|---|---|
| Texas RRC T-4 pipeline permit records in a project-signal snapshot | 88 | T-4 rows available for midstream permit review in that snapshot. |
| Route-matched T-4 records in the detail pass | 78 of 88 | Shows how many T-4 rows had a direct route match in loaded RRC pipeline GIS at that review point. |
| Texas RRC R-3 gas plant records | 524 | Adds gas plant and processing context where source records are available. |
| FERC CP docket signals | 1,655 | Adds federal certificate, compressor, storage, and interstate project context. |
| Total project-signal rows | 2,267 | Source-level infrastructure records across the current public-record families in the cited snapshot. |
| Texas TCEQ facility records | 36,112 | Broader Texas facility-record coverage used for infrastructure account and source-date workflows. |
| Chase-ready Texas infrastructure records | 23,627 | Rows with enough source detail to support follow-up in the reviewed snapshot. |
Snapshot metric
Texas RRC T-4 pipeline permit records in a project-signal snapshot
Public example
88
What it means
T-4 rows available for midstream permit review in that snapshot.
Snapshot metric
Route-matched T-4 records in the detail pass
Public example
78 of 88
What it means
Shows how many T-4 rows had a direct route match in loaded RRC pipeline GIS at that review point.
Snapshot metric
Texas RRC R-3 gas plant records
Public example
524
What it means
Adds gas plant and processing context where source records are available.
Snapshot metric
FERC CP docket signals
Public example
1,655
What it means
Adds federal certificate, compressor, storage, and interstate project context.
Snapshot metric
Total project-signal rows
Public example
2,267
What it means
Source-level infrastructure records across the current public-record families in the cited snapshot.
Snapshot metric
Texas TCEQ facility records
Public example
36,112
What it means
Broader Texas facility-record coverage used for infrastructure account and source-date workflows.
Snapshot metric
Chase-ready Texas infrastructure records
Public example
23,627
What it means
Rows with enough source detail to support follow-up in the reviewed snapshot.
Use cases
What teams can do with this data
| Team | Useful data | Practical question it helps answer |
|---|---|---|
| Midstream business development | T-4 permits, route matches, counties, operators, commodity, diameter | Which operators and counties show source-backed infrastructure signals worth reviewing? |
| Oilfield services and equipment | Facility records, source dates, facility types, nearby wells and permits | Where might gathering, compression, water, power, or field-service demand be forming? |
| Operators | Nearby permits, wells, production, facility records, source dates | What infrastructure context sits around current development areas? |
| Analysts and consultants | Source family, date basis, operator identity, route evidence, caveats | Which public records support the market or operator story? |
| Data and API teams | Structured fields, exports, source metadata, route evidence | Which records can be pulled into a repeatable data workflow? |
Team
Midstream business development
Useful data
T-4 permits, route matches, counties, operators, commodity, diameter
Practical question it helps answer
Which operators and counties show source-backed infrastructure signals worth reviewing?
Team
Oilfield services and equipment
Useful data
Facility records, source dates, facility types, nearby wells and permits
Practical question it helps answer
Where might gathering, compression, water, power, or field-service demand be forming?
Team
Operators
Useful data
Nearby permits, wells, production, facility records, source dates
Practical question it helps answer
What infrastructure context sits around current development areas?
Team
Analysts and consultants
Useful data
Source family, date basis, operator identity, route evidence, caveats
Practical question it helps answer
Which public records support the market or operator story?
Team
Data and API teams
Useful data
Structured fields, exports, source metadata, route evidence
Practical question it helps answer
Which records can be pulled into a repeatable data workflow?
Static map vs workflow
What EnergyNetWatch adds beyond a static map
EnergyNetWatch workflow
Connects map context to permit, facility, source-date, operator, county, confidence, exports, alerts, and API workflows.
Featured reading
Midstream and infrastructure reads
Texas RRC T-4 Pipeline Permits: Map Context To GIS Route Evidence
Specific Firebird example showing map context, T-4 permit data, GIS route evidence, source date, and record workflow.
Texas T-4 Pipeline Permits: How Midstream Infrastructure Leads Work
Deeper methodology page explaining T-4 permits, route matching, a Civitas example, and nearby activity review.
Texas Infrastructure Records: Chase-Ready Oil And Gas Leads
Facility-record workflow showing source dates, facility types, operator/county context, and chase-ready quality.
EnergyNetWatch Developers
API access path for teams that need governed data workflows instead of manual screenshots or one-off exports.
FAQ
Midstream infrastructure data FAQ
What is midstream infrastructure data?
Midstream infrastructure data includes pipeline permits, pipeline GIS route context, gas plant records, facility records, federal docket signals, operators, counties, source dates, commodities, diameter ranges, and related public-record fields used to review infrastructure activity.
What is pipeline GIS data?
Pipeline GIS data is geographic route or point context for pipeline infrastructure. It helps show where a route or asset sits and becomes more useful when connected to source records such as Texas RRC T-4 pipeline permits, facility records, or other public infrastructure signals.
What is a Texas RRC T-4 pipeline permit?
A Texas RRC T-4 pipeline permit is a Texas pipeline permit record. It can identify operator, commodity, classification, location context, and pipeline attributes depending on the source record and related filings.
What does GIS route matching add?
GIS route matching connects a source record to route evidence. That can add matched route segments, diameter range, commodity context, counties, system/operator context, and route-confidence information where the source data supports it.
Does route matched mean the pipeline is in service?
No. A route-matched infrastructure record should be read as a source-backed lead. In-service status, construction status, lifecycle history, and economics require additional source review.
Can EnergyNetWatch provide exports, alerts, or API access?
EnergyNetWatch is built around source-aware workflows, including maps, record review, exports, alerts, saved workflows, and API access where product coverage and customer access support them.
Need current midstream records?
Review current route context, infrastructure records, maps, exports, alerts, and API access paths.
Request EnergyNetWatch access