Overview

Every NYISO location that carries a price, as three columns: location_id, name, and kind. 773 rows — generator (758), zone (15). This is the dimension the NYISO 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 NYISO, location_id is the numeric PTID and name is the human-readable zone or generator name. Join on location_id; report 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.

Use with MCP

This table is readable two ways, over the same guarded boundary. Over HTTP: POST /api/v1/datasets/nyiso_locations/query, described in the API reference. Or from an MCP client: connect a market below, then use search_data or describe_data to load its query contract before calling query_data.

Schema3

Column
Type
location_idLowCardinality(String)
nameLowCardinality(String)
kindLowCardinality(String)

Sample rows

location_idnamekind
-23651HQ_DAM_TRANS_STRIKEgenerator
-24062N.E._DAM_TRANS_STRIKEgenerator
-24063O.H._DAM_TRANS_STRIKEgenerator
-24065PJM_DAM_TRANS_STRIKEgenerator
23512ARTHUR_KILL_2generator
23513ARTHUR_KILL_3generator
23514ALLEGHENY___COGENgenerator
23515BROOKLYN_NAVY_YARDgenerator
23516ASTORIA___3generator
23517ASTORIA___4generator
23518ASTORIA___5generator
23519POLETTI____generator
23520ARTHUR KILL_GT_1generator
23522WADING RIVER_IC_1generator
23523ASTORIA_GT_1generator
23524EAST RIVER___7generator
23526BOWLINE___1generator
23527ADK_NYS___DAMgenerator
23528NEG_PENN_ALLEGHNYgenerator
23530INDIAN POINT___2generator
23531INDIAN POINT___3generator
23532RUSSELL___2generator
23533RAVENSWOOD___1generator
23534RAVENSWOOD___2generator
23535RAVENSWOOD___3generator

Coverage

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