Resource Handling in H2I

[elenya-grant]

Resource Handling: Functionality and Feature Dreams

• ability to handle various "models" or sources of resource data that may have different inputs (Open-Meteo, NREL developer network, NASA Power, user-customized data, etc)
• ability to specify different resource years across resource types (ex: solar resource for 2024 and wind resource for 2013)
• ability to specify different resource locations across resource types (ex: solar resource at different location than wind resource)
• ability to handle different simulation lengths (multi-year, one-year, sub-year)
• ability to handle different simulation time-steps (perhaps may require downsampling or upsampling)
• time information tied to resource data
• resource data rolled to a consistent timezone
• resource data could be:
  • provided by user as a dictionary
  • provided by user as a filepath
  • loaded from a user-provided directory, where a file within that directory matches has a filename that matches some auto-generated filename
  • not provided by user, has to be downloaded from API using user-provided "config" type inputs.
  • not provided by user, has to be pulled from some dataset (more specific to NREL uses)
• NREL developer network API calls: by default, download all resource data attributes for a site. This would look like downloading wind resource data for all available hub-heights which can be filtered within a wind farm performance model.

Proposed solution

Alternatives considered

Additional context

[elenya-grant]

Some of these have been addressed with the resource models in H2I. The remaining capabilities/functionality that has not yet been addressed are:

• Different locations (PR Enable multiple site functionality #434)
• Different simulation lengths (multi-year or sub 1-year)
• Ability to handle different simulation time-steps (perhaps may require downsampling or upsampling)
• resource data rolled to a consistent timezone (this is somewhat handled by shared default behavior where most resource data is downloaded in UTC)
• NASA Power for resource data
• Pulling resource data from NREL datasets hosted on HPC
• User provided dictionary (this is possible but may not be tested)