Allow multiple lat/lon pairs for when GreenHEART hybrids are partially onshore and partially offshore
We have cases where we need to specify multiple lat/lon pairs for a single plant. The primary instance so far is when we have a portion of the plant offshore (e.g. wind) and a portion of the plant on shore (e.g. solar) and both are connected to a single substation or end use (e.g. electrolysis) as a single plant.
Proposed solution
I could see this being implemented on a per-technology basis or on an onshore/offshore basis. I think it will be more extensible if we make lat/lon an optional parameter for each of the technologies or, perhaps cleaner, allow the user to pass a list of lat/lon pairs in the same place lan/lon is currently provided and then we allow each technology to specify an index location into the lat/lon list provided so the appropriate resource is downloaded and used for each technology but we don't have lots of duplicate inputs.
Alternatives considered
Our current work around is to provide the lat/lon for one area and provide resource files for the tech that are not in the same area.
Additional context
This is relevant to the green steel reference plants.
Allow multiple lat/lon pairs for when GreenHEART hybrids are partially onshore and partially offshore
We have cases where we need to specify multiple lat/lon pairs for a single plant. The primary instance so far is when we have a portion of the plant offshore (e.g. wind) and a portion of the plant on shore (e.g. solar) and both are connected to a single substation or end use (e.g. electrolysis) as a single plant.
Proposed solution
I could see this being implemented on a per-technology basis or on an onshore/offshore basis. I think it will be more extensible if we make lat/lon an optional parameter for each of the technologies or, perhaps cleaner, allow the user to pass a list of lat/lon pairs in the same place lan/lon is currently provided and then we allow each technology to specify an index location into the lat/lon list provided so the appropriate resource is downloaded and used for each technology but we don't have lots of duplicate inputs.
Alternatives considered
Our current work around is to provide the lat/lon for one area and provide resource files for the tech that are not in the same area.
Additional context
This is relevant to the green steel reference plants.