Resource Node → Unit Mapping

ERCOT's weekly registration crosswalk between resource nodes and registered generation units.

Infrastructure data

Download data

Native record

event_time x resource_node x unit_name

weekly (snapshot) publication cadence

Evidence

Observed market data

Published observations from the named source

Time basis

Point-in-time records

UTC · event_time

Overview

It can establish the published node-to-unit relationship for a particular snapshot. It does not establish dispatch, ownership, substation topology, constraint exposure, or the cause of a nodal price move. This table is listed in the public catalog but is not exposed to agent SQL until its snapshot and identity semantics are fully contracted. The source is ERCOT report NP4-160-SG.

Query contract

Preserve one canonical row per (event_time, resource_node, unit_name) before aggregating.

Analysis rules

Group only after preserving the declared grain: event_time, resource_node, unit_name.

Schema7

Column

Type

event_timeDateTime64(6, 'UTC')

resource_nodeLowCardinality(String)

unit_nameLowCardinality(String)

emil_idNullable(String)

doc_idNullable(Int64)

ingested_atDateTime64(6, 'UTC')

unit_substationNullable(String)

Sample data

event_time	resource_node	unit_name	emil_id	doc_id	ingested_at	unit_substation
2026-09-16 00:00:00.000000	ZIER_SLR_ALL	PV1	NP4-160-SG	1275076044	2026-09-21 08:00:23.377986	ZIER_SLR
2026-09-16 00:00:00.000000	ZIER_SLR_ALL	ESR1	NP4-160-SG	1275076044	2026-09-21 08:00:23.377986	ZIER_SLR
2026-09-16 00:00:00.000000	Z5_DGR1_RN	DGR1	NP4-160-SG	1275076044	2026-09-21 08:00:23.377986	Z5
2026-09-16 00:00:00.000000	Z0_DGR2_RN	ESR1	NP4-160-SG	1275076044	2026-09-21 08:00:23.377986	Z0
2026-09-16 00:00:00.000000	Z0_DGR2_RN	DGR2	NP4-160-SG	1275076044	2026-09-21 08:00:23.377986	Z0
2026-09-16 00:00:00.000000	Z0_DGR1_RN	DGR1	NP4-160-SG	1275076044	2026-09-21 08:00:23.377986	Z0
2026-09-16 00:00:00.000000	YNG_WND_ALL	UNIT3	NP4-160-SG	1275076044	2026-09-21 08:00:23.377986	YNG_WND
2026-09-16 00:00:00.000000	YNG_WND_ALL	UNIT2	NP4-160-SG	1275076044	2026-09-21 08:00:23.377986	YNG_WND
2026-09-16 00:00:00.000000	YNG_WND_ALL	UNIT1	NP4-160-SG	1275076044	2026-09-21 08:00:23.377986	YNG_WND
2026-09-16 00:00:00.000000	YCAT_WND_RN	UNIT2	NP4-160-SG	1275076044	2026-09-21 08:00:23.377986	YCAT_WND
2026-09-16 00:00:00.000000	YCAT_WND_RN	UNIT1	NP4-160-SG	1275076044	2026-09-21 08:00:23.377986	YCAT_WND
2026-09-16 00:00:00.000000	YAPN_SLR_RN	PV2	NP4-160-SG	1275076044	2026-09-21 08:00:23.377986	YAPN_SLR
2026-09-16 00:00:00.000000	YAPN_SLR_RN	PV1	NP4-160-SG	1275076044	2026-09-21 08:00:23.377986	YAPN_SLR
2026-09-16 00:00:00.000000	X443ESRN	ESR1	NP4-160-SG	1275076044	2026-09-21 08:00:23.377986	X4
2026-09-16 00:00:00.000000	X1_DGR_RN	DGR1	NP4-160-SG	1275076044	2026-09-21 08:00:23.377986	X1
2026-09-16 00:00:00.000000	W_PECO_UNIT1	UNIT1	NP4-160-SG	1275076044	2026-09-21 08:00:23.377986	W_PECOS
2026-09-16 00:00:00.000000	W_HRL_ESR_RN	ESR1	NP4-160-SG	1275076044	2026-09-21 08:00:23.377986	W_HARLIN
2026-09-16 00:00:00.000000	WZRD_ESS_RN	ESR1	NP4-160-SG	1275076044	2026-09-21 08:00:23.377986	WZRD_ESS
2026-09-16 00:00:00.000000	WR_RN	ESR1	NP4-160-SG	1275076044	2026-09-21 08:00:23.377986	WR
2026-09-16 00:00:00.000000	WRSBES_BESS1	ESR1	NP4-160-SG	1275076044	2026-09-21 08:00:23.377986	WORSHAM
2026-09-16 00:00:00.000000	WOV_BESS_RN	ESR1	NP4-160-SG	1275076044	2026-09-21 08:00:23.377986	WOVER
2026-09-16 00:00:00.000000	WOODWRD2_RN	WOODWRD2	NP4-160-SG	1275076044	2026-09-21 08:00:23.377986	WOODWRD2
2026-09-16 00:00:00.000000	WOODWRD1_RN	WOODWRD1	NP4-160-SG	1275076044	2026-09-21 08:00:23.377986	WOODWRD1
2026-09-16 00:00:00.000000	WND_WHITNEY	WHITNEY2	NP4-160-SG	1275076044	2026-09-21 08:00:23.377986	WND
2026-09-16 00:00:00.000000	WND_WHITNEY	WHITNEY1	NP4-160-SG	1275076044	2026-09-21 08:00:23.377986	WND

Coverage

11.8% complete112 gap days15 days with data

Show coverage history

Coverage: 11.8%Days with data: 15Gaps: 112

2026

gaplessmore

Related infrastructure data

Related infrastructure data
Dataset	Description
ERCOT Interconnection QueueERCOT · monthly snapshot	ERCOT's public large-generation interconnection queue, with project identity, developer, proposed point of interconnection, transmission owner, technology, requested MW, queue status, and proposed or actual completion dates. Each posting is a snapshot, so current project claims must use the latest snapshot rather than count every vintage. Queue inclusion and proposed dates do not establish available transmission headroom, study outcome, approval, construction probability, or an operating asset. The official source is ERCOT's GIS Report.
ERCOT Price LocationsERCOT · slow-moving dimension, refreshed every 6 hours	Every ERCOT location that carries a price, as three columns: location_id, name, and kind. 20,456 rows — bus (19,329), node (1,100), weather_zone (8), zone (8), hub (7), interface (4). This is the dimension the ERCOT price, and where applicable constraint, tables join to, and it is the one place a location's type is decided: resolve "which hubs exist", "is this a zone or a node", or "give me the readable name for this id" here rather than inferring a type from a name prefix. For ERCOT, name equals location_id — the settlement-point name is the identifier. The key is (location_id, kind), not location_id alone: 161 ERCOT names exist as both a settlement point and an electrical bus, and those are separately priced objects. Filter on kind when a name could be either. The same three columns exist for every market, so the equivalent question in another ISO is the same query against that ISO's table.
BPA Anemometer TowersBPA · daily	BPA's anemometer towers with coordinates, elevation and sensor heights, active and retired.
BPA Interconnection QueueBPA · daily snapshot	BPA's public large-generator interconnection queue, with requested capacity, technology, county and state, proposed point of interconnection, BPA's status, and agreed in-service dates. Each posting is a snapshot: current totals must use one latest snapshot, and requested queue MW is not operating capacity, available transmission headroom, completed study work, or evidence that a project will be built. BPA runs line and load requests as a separate queue, held in interconnection_queue.bpat_load.