ISO-NE Price Locations
Every ISO-NE location that carries a price, as three columns: location_id, name, and kind.
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
Analysis rules
Interpretation
Schema3
location_idLowCardinality(String)nameLowCardinality(String)kindLowCardinality(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 |
| 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 |
| 10683 | LD.BELL_RK 34.5 | node |
| 10684 | LD.JOHNSTON12.5 | node |
Coverage
No time-indexed data — coverage isn’t applicable to this dataset.