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
Is your feature request related to a problem? Please describe.
pvgis is the easiest weather data to retrieve b/c no credentials required, but it always returns data in UTC, which then needs to be adjusted to local timezone, causing the year to not start at midnight.
Describe the solution you'd like
This is some boilerplate that I use everytime I pull pvgis, so rather than clogging up my codebase, I thought it would be easier if it were upstream. Basically:
if february is a leap year, change it to 1990
rotate the dataframe by the desired utc offset (note, don't shift the index)
Is your feature request related to a problem? Please describe.
pvgis is the easiest weather data to retrieve b/c no credentials required, but it always returns data in UTC, which then needs to be adjusted to local timezone, causing the year to not start at midnight.
Describe the solution you'd like
This is some boilerplate that I use everytime I pull pvgis, so rather than clogging up my codebase, I thought it would be easier if it were upstream. Basically:
Tested in this Google Colab notebook
test_coerce_pvgis.ipynb
Describe alternatives you've considered
keep doing this manually in my code.
Additional context
This was discussed here #1528 (comment)
The text was updated successfully, but these errors were encountered: