MISO Price Locations

Every MISO location that carries a price, as three columns: location_id, name, and kind.

Infrastructure data

Download data

Native record

one row per priced location and kind

slow-moving dimension, refreshed every 6 hours publication cadence

Evidence

Reference data

Stable context used to interpret other datasets

Time basis

Point-in-time records

UTC · static reference

Overview

325 rows — generator (274), interface (22), zone (21), hub (8). This is the dimension the MISO 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 MISO, name equals location_id (the node name, e.g. ALTE.1ROCKGEN). MISO publishes no pricing-node registry, so this dimension is assembled from grid.entities rather than from a MISO feed. It covers MISO's hub and zone roll-up, which is coarser than a full nodal set. The same three columns exist for every market, so the equivalent question in another ISO is the same query against that ISO's table.

Query contract

Treat (location_id, kind) as the row identity. This is a current dimension snapshot, not a history: it describes the locations that exist now and carries no validity dates.

Analysis rules

Counting rows by kind describes the market's current location inventory. It does not describe how many locations were priced on some past date.
Join fact tables on location_id, and add kind to the join when the fact table also carries kind — the pair, not the id alone, is the identity.

Interpretation

A location existing here does not mean it has a price in any particular interval; check the price table for that.
kind is a classification of the priced object, not of the physical equipment behind it, and carries no capacity, voltage, or geography. Location geography lives in grid.entities.

Schema3

Column

Type

location_idLowCardinality(String)

nameLowCardinality(String)

kindLowCardinality(String)

Sample data

location_id	name	kind
AECI	AECI	interface
ALTE.1ROCKGEN	ALTE.1ROCKGEN	generator
ALTE.COLUMBAL1	ALTE.COLUMBAL1	generator
ALTE.COLUMBAL2	ALTE.COLUMBAL2	generator
ALTE.EDGG5G5	ALTE.EDGG5G5	generator
ALTE.ROCKGEN2	ALTE.ROCKGEN2	generator
ALTE.ROCKGEN3	ALTE.ROCKGEN3	generator
ALTW.ALTW	ALTW.ALTW	zone
ALTW.BRLGTN5	ALTW.BRLGTN5	generator
ALTW.JOUNEALS4	ALTW.JOUNEALS4	generator
ALTW.LANSIN4	ALTW.LANSIN4	generator
ALTW.LEDYARD	ALTW.LEDYARD	zone
ALTW.OTTUMW1	ALTW.OTTUMW1	generator
AMIL.ALSEYCTG1	AMIL.ALSEYCTG1	generator
AMIL.BALDWI51	AMIL.BALDWI51	generator
AMIL.BALDWI52	AMIL.BALDWI52	generator
AMIL.BWSS_BF	AMIL.BWSS_BF	generator
AMIL.BWSS_SF	AMIL.BWSS_SF	generator
AMIL.CLINTO51	AMIL.CLINTO51	generator
AMIL.COSF_BF	AMIL.COSF_BF	generator
AMIL.COSF_SF	AMIL.COSF_SF	generator
AMIL.EDWARDS2	AMIL.EDWARDS2	generator
AMIL.EDWARDS3	AMIL.EDWARDS3	generator
AMIL.NEWTON21	AMIL.NEWTON21	generator
AMIL.PPI	AMIL.PPI	generator

Coverage

No time-indexed data — coverage isn’t applicable to this dataset.

Related infrastructure data

Related infrastructure data
Dataset	Description
Live System SnapshotMISO · 1-minute snapshots	The compact public MISO dashboard snapshot, retaining each publisher title and raw string value for demand, capacity, and interchange headlines. Prefer the typed live_load, live_capacity, and live_grid_metrics tables for calculations.
MISO Interconnection QueueMISO · daily snapshot	MISO's public generator interconnection queue, including project identity, developer, county and state, proposed point of interconnection, transmission owner, technology, requested capacity, status, and negotiated or actual completion dates where published. 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.
CAISO Interconnection QueueCAISO · monthly snapshot	CAISO's public generation interconnection queue, combining active, completed, and withdrawn projects with the proposed point of interconnection, technology, requested capacity, status, and completion dates. Each posting is a snapshot: current totals must use one latest snapshot, and requested queue MW is not operating capacity, available transmission headroom, or evidence that a project will be built.
CAISO Price LocationsCAISO · slow-moving dimension, refreshed every 6 hours	Every CAISO location that carries a price, as three columns: location_id, name, and kind. 26,632 rows — node (26,048), interface (578), zone (6). This is the dimension the CAISO 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 CAISO, name equals location_id (the pnode name). The same three columns exist for every market, so the equivalent question in another ISO is the same query against that ISO's table.