Data

All seven interconnection queues share one map

Official queue publications from ERCOT, CAISO, ISO-NE, MISO, NYISO, PJM, and SPP can be compared nationally, then opened as operator-specific county and project records.

#Interconnection#National grid#Map#Projects

The Interconnection queue layer combines every supported organized market without collapsing their sources or native records. County capacity, project counts, technologies, and normalized active, completed, and withdrawn statuses provide a national comparison; publication dates, operator names, queue IDs, and project histories remain market-specific.

Coverage is the seven organized US markets supported by Ask the Grid. Areas outside those footprints—including much of the Southeast and Arizona—require additional utility or balancing-authority sources before they can appear. Requested queue capacity is not a forecast of what will be built, and an operator status is not independent proof of commercial operation.

Compare the official queues nationally

The national layer shades counties by requested capacity and keeps counties shared by several market footprints intact. Opening one compares publication date, project count, active capacity, and total requested capacity for each operator side by side.

Project rows retain their native market and queue ID, so the next step always opens the correct operator record.

The National grid map showing queue capacity across seven markets and a county comparison for ERCOT, MISO, and SPP.
Shared counties preserve each operator's publication date and totals instead of collapsing them into the selected market.

Replay the publication that existed at the time

ERCOT's detailed workflow follows map time: move backward to the queue publication available then, between adjacent snapshots, or forward to active projects whose proposed completion date falls inside a chosen horizon. County totals keep that meaning beside the result.

The live ERCOT queue map showing Pecos County results beside the latest publication, completion-horizon, and technology controls.
The operator-specific view connects map time, delivery horizon, filters, provenance, and county results.

Inspect the native project history

Individual records preserve queue ID, developer, requested MW, technology, point of interconnection, status, proposed dates, and changes across official publications. County-centroid placement remains explicit because the source does not publish exact project geometry.

Big Watt Mustang queue project card with published status, dates, and county-centroid location qualification.
A county result opens the source queue record; a county centroid is not an exact project site.