ISO-NE Price Locations

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

One row per: one row per priced location and kind; Slow-moving dimension, refreshed every 6 hours cadence
Evidence: Reference data; Stable context used to interpret other datasets
Time basis: Point-in-time records; UTC · static reference

Overview

1,213 rows — node (1,177), aggregate (20), zone (8), interface (7), hub (1). This is the dimension the ISO-NE 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 ISO-NE, location_id is the numeric location id and name is ISO-NE's own location name (e.g. .Z.CONNECTICUT). Join on location_id; report name. ISO-NE's price feed is the registry here, so a location appears in this dimension exactly when it has been priced. 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

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.ISO-NE MCP API reference
HTTP endpoint: POST /api/v1/datasets/isone_locations/query
Full history: Delivered to Snowflake, Databricks or your own storage on a schedule by Data services.
More coverage

Schema

3 columns

Column	Type
`location_id`	`LowCardinality(String)`
`name`	`LowCardinality(String)`
`kind`	`LowCardinality(String)`

Sample data

location_id	name	kind
10033	LD.BURTT_RD13.2	node
10034	LD.TUNNEL 69	node
10037	LD.POWERSVL115	node
10038	LD.GREATBAY34.5	node
10039	LD.PORTSMTH34.5	node
1005	UN.DIGHTON 115 DIGH	node
10178	LD.DEBLOIS 34.5	node
1030	UN.FALMOUTH25 OAKB	node
1031	UN.FALMOUTH25 WTIS	node
1032	UN.BPT_ENER16 BHCC	node
10341	LD.BEVERLY 13.2	node
10344	LD.GOLDN_RK23	node
10347	UN.KENDALL 13.8KND1	node
10348	UN.KENDALL 13.8KND2	node
10349	UN.KENDALL 13.8KND3	node
10424	UN.BERLN_NH22 BERP	node
10426	LD.TORRNGTN13.2	node
10472	LD.ROLF_AVE13.8	node
10474	LD.DEXTR_RI13.8	node
10494	LD.TAFTS_CR34.5	node
10512	LD.CHALLENG34.5	node
10556	LD.ELLIS_AV14.4	node
10571	LD.OAK_ST 23	node
10602	LD.RAYNHAM 13.8	node
10603	LD.WESTFORD13.2	node

Coverage

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

Related data

Related infrastructure data
Dataset	Description
ISO-NE Interconnection QueueISONE · daily snapshot	ISO New England's public interconnection queue, including project identity, location, transmission owner, technology, requested capacity, milestone status, and withdrawal date 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.
Morning ReportISONE · ISO-NE source publication	ISO-NE's published Morning Report source feed. This catalog page exposes the physical schema, coverage, and latest source rows without inventing a normalized grain for publisher-shaped snapshot fields. Use the documented key and event time when comparing revisions or vintages.
Schedule2 VAR ProgramISONE · ISO-NE source publication	ISO-NE's published Schedule2 VAR Program source feed. This catalog page exposes the physical schema, coverage, and latest source rows without inventing a normalized grain for publisher-shaped snapshot fields. Use the documented key and event time when comparing revisions or vintages.
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.