[x] Is your feature request essential for your project?
Describe the workflow you want to enable
Currently, HIFLD grid building defines zones as a combination of state and interconnect, and leverages the demand profiles for usa_tamu to be able to roll up demand to these zones for testing. However, now that we have shapefiles representing balancing authority (BA) areas and sub-areas via #270, we can use these definitions to assign buses to BAs, and get BA-level hourly profiles either directly from EIA (via Form 930 data) or via a third-party source that performs data-correction on these data (e.g. https://zenodo.org/record/4116342). We may also want to define our zones as a combinations of BA & state, where the BA-level demand profiles are distributed to multiple states by the population-weighting of each bus; this step would increase the degree of assumptions/approximations, but could enable more detailed state-level policy studies.
Describe your proposed implementation, if applicable
We would create a new function which takes the substation/bus coordinates and a shapefile representing multiple BA geometries, and map each bus to exactly one BA area. If there's a bus that is in no geometries (there's a gap in the coverage) or multiple geometries (there's overlap in the coverage), we could map this bus to the nearest successfully-mapped bus. During HIFLD grid-building, we would call this function to assign buses to zones.
We would create a new function which retrieves EIA data via their API (https://www.eia.gov/opendata/qb.php?category=2123635 and sub-categories) for a given year, and call this function during HIFLD profile-building. Where necessary, the demand from EIA would be aggregated or split as necessary to match the zone set defined during grid-building.
:rocket:
Describe the workflow you want to enable
Currently, HIFLD grid building defines zones as a combination of state and interconnect, and leverages the demand profiles for
usa_tamu
to be able to roll up demand to these zones for testing. However, now that we have shapefiles representing balancing authority (BA) areas and sub-areas via #270, we can use these definitions to assign buses to BAs, and get BA-level hourly profiles either directly from EIA (via Form 930 data) or via a third-party source that performs data-correction on these data (e.g. https://zenodo.org/record/4116342). We may also want to define our zones as a combinations of BA & state, where the BA-level demand profiles are distributed to multiple states by the population-weighting of each bus; this step would increase the degree of assumptions/approximations, but could enable more detailed state-level policy studies.Describe your proposed implementation, if applicable