MISO Price Locations

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.

Download

Query it in SQL, download it, or read it with an API key. Download data

MCP

Connect an MCP client and load the contract with describe_data before calling query_data.MISO MCPAPI reference

HTTP endpoint

POST /api/v1/datasets/miso_locations/query

Full history

Delivered to Snowflake, Databricks or your own storage on a schedule by Data services.

More coverage

Request data coverage

This dataset has no time index, so it has no daily coverage.