You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The wind resource file reader lib_windfile.cpp requires time zone and elevation data that is not used by the wind power model.
Elevation data does not appear to be used in any wind power model calculations, but may be required for SAM UI calculations -- need to investigate the elevation requirement. If it is only a UI requirement, handle missing data in UI when it applies instead of in SSC. (Elevation not included in WIND Toolkit wtk-download data.)
No need to require lat/lon data: The only potential use of lat/lon data in a wind file would be for hybrid systems to verify that the wind and solar wind files are for the same location, but this is not something we plan to have the hybrid models check or enforce. (Solar models need lat/lon for sun position calculations that are not needed for wind power model.)
Describe the bug
The wind resource file reader
lib_windfile.cpp
requires time zone and elevation data that is not used by the wind power model.Elevation data does not appear to be used in any wind power model calculations, but may be required for SAM UI calculations -- need to investigate the elevation requirement. If it is only a UI requirement, handle missing data in UI when it applies instead of in SSC. (Elevation not included in WIND Toolkit
wtk-download
data.)No need to require lat/lon data: The only potential use of lat/lon data in a wind file would be for hybrid systems to verify that the wind and solar wind files are for the same location, but this is not something we plan to have the hybrid models check or enforce. (Solar models need lat/lon for sun position calculations that are not needed for wind power model.)
Files for testing with missing elevation, timezone, and lat/lon data: wtk-download-default-no-elevation.zip
Operating System and Version
The text was updated successfully, but these errors were encountered: