Ask the Grid

IEDR DER Hosting Capacity by Grid Section

Every record on NYSERDA IEDR's New York hosting-capacity map, one row per weekly snapshot: `asset_type` is `segment` (a line section of a radial feeder), `feeder`, or Con Ed's `network`, `network-area`, `network-structure` and `transformer`; `parent_id` links a segment to its feeder.

iedr.hosting_capacity_assetsNYSERDA IEDRInfrastructure data
Open in Data (opens in a new tab) Open on map
One row per
event_time x asset_id
Weekly snapshot cadence
Evidence
Observed market data
Published observations from the named source
Time basis
Point-in-time records
UTC · event_time

Overview

Each `*_max_hosting_capacity_mw` is the largest single project that could connect AT THAT POINT before upgrades, for generic DER, ESS charging, ESS discharging and EVSE. Points on a feeder share its capacity, so NEVER sum these values: count or rank locations instead (for example the share of a county's `segment` and `network-area` rows with `max_hosting_capacity_mw >= 1`). Utility methods differ: Central Hudson values stop at 6 MW and the rest at 10, Orange and Rockland publishes bands (0.99, 1.99, 2.99, 4.99), LIPA and Orange and Rockland publish no ESS values, and Con Ed `network` rows read like kW. Read one snapshot at a time: `event_time = (SELECT max(event_time) FROM iedr.hosting_capacity_assets)`.

Query contract
Preserve one canonical row per (event_time, asset_id) before aggregating.
Analysis rules
Group only after preserving the declared grain: event_time, asset_id.

Access

Plans
See available download and API access options. View pricing
Full history
Delivered to Snowflake, Databricks or your own storage on a schedule by Data services.
More coverage

Schema

Loading…

Sample data

Loading…

Coverage

Loading…