NYISO Price Locations

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

Infrastructure data NYISO market

Query with the agent

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

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.

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.

Access

Query from your own tools

Use the guarded HTTP endpoint directly, or connect an MCP client and load the dataset contract with describe_data before calling query_data.

NYISO MCP API reference

HTTP endpoint

POST /api/v1/datasets/nyiso_locations/query

Need the full history of this dataset in Snowflake, Databricks or your own storage? Data services delivers it on a schedule.

Schema3

Column

Type

location_idLowCardinality(String)

nameLowCardinality(String)

kindLowCardinality(String)

Sample data

location_id	name	kind
-23651	HQ_DAM_TRANS_STRIKE	generator
-24062	N.E._DAM_TRANS_STRIKE	generator
-24063	O.H._DAM_TRANS_STRIKE	generator
-24065	PJM_DAM_TRANS_STRIKE	generator
0	0	generator
23512	ARTHUR_KILL_2	generator
23513	ARTHUR_KILL_3	generator
23514	ALLEGHENY___COGEN	generator
23515	BROOKLYN_NAVY_YARD	generator
23516	ASTORIA___3	generator
23517	ASTORIA___4	generator
23518	ASTORIA___5	generator
23519	POLETTI____	generator
23520	ARTHUR KILL_GT_1	generator
23522	WADING RIVER_IC_1	generator
23523	ASTORIA_GT_1	generator
23524	EAST RIVER___7	generator
23526	BOWLINE___1	generator
23527	ADK_NYS___DAM	generator
23528	NEG_PENN_ALLEGHNY	generator
23530	INDIAN POINT___2	generator
23531	INDIAN POINT___3	generator
23532	RUSSELL___2	generator
23533	RAVENSWOOD___1	generator
23534	RAVENSWOOD___2	generator

Coverage

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

Related infrastructure data

Related infrastructure data
Dataset	Description
NYISO Interconnection QueueNYISO · irregular snapshot	NYISO's public interconnection queue across active, cluster-study, withdrawn, and in-service projects, including developer, location, transmission owner, technology, requested capacity, status, and proposed or actual 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.
Published generator reference CSVNYISO · Publisher snapshot	NYISO's Published generator reference CSV. Each row preserves a publisher record, workbook row, or report document with its source member and row index. Source timestamps, units, geographic scope, and revision qualifiers are retained in record_json; event_time is collection time; completed_at is when the entire document became available.
Published load reference CSVNYISO · Publisher snapshot	NYISO's Published load reference CSV. Each row preserves a publisher record, workbook row, or report document with its source member and row index. Source timestamps, units, geographic scope, and revision qualifiers are retained in record_json; event_time is collection time; completed_at is when the entire document became available.
Advanced MetersEIA · annual (report year)	EIA-861 advanced metering: AMR, AMI and other meter counts, AMI energy served and customer access, by utility and customer class. Advanced_Meters, one row per utility, state, balancing authority and customer class. customer_class is residential, commercial, industrial, transportation (direct_connected in the distributed generation tables) or EIA's own total, so summing classes without excluding total counts everything twice. event_time is 1 January of the report year. release is final or early_release: EIA posts an early release of a year in August and replaces it with the final file in the autumn, and the mirror keeps the newest row per key. A key cell EIA leaves blank is '' or 0, and duplicate_index numbers rows that still share a key, in workbook order.