Skip to content

Changes to PVGIS in version 5.2 #1415

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
AdamRJensen opened this issue Feb 27, 2022 · 8 comments · Fixed by #1502
Closed

Changes to PVGIS in version 5.2 #1415

AdamRJensen opened this issue Feb 27, 2022 · 8 comments · Fixed by #1502
Milestone

Comments

@AdamRJensen
Copy link
Member

AdamRJensen commented Feb 27, 2022

Describe the bug
PVGIS is releasing version 5.2 on March 1st, 2022. In the new version, the irradiance databases CMSAF and COSMO have been removed. Additionally, the ERA5 coverage has been extended to cover almost the entire globe and a new database, SARAH-2, has been added.

The full description can be found here.

The new default databases can be seen here:
image

Additional context
There is nothing that indicates any changes to the API, so the pvlib.iootools functions get_pvgis_tmy and get_pvgis_hourly should continue to work.

However, some of the test files used in test_pvgis.py are from the CMSAF database. Since those tests seem to be either based on local files or mock tests, I do not expect test failures. However, it would probably make sense to update the tests regardless.

@cwhanse
Copy link
Member

cwhanse commented Feb 28, 2022

@AdamRJensen do you know if the content of CMSAF and COSMO is migrating to the new database? Sorry that I'm not familiar with PVGIS.

@cwhanse
Copy link
Member

cwhanse commented Feb 28, 2022

@AdamRJensen do you know if the content of CMSAF and COSMO is migrating to the new database? Sorry that I'm not familiar with PVGIS.

I missed the link to the documentation in my quick read of your issue, the documentation answers my question. I agree it would make sense to replace the test files or (more simply) to add a note to the test code identifying the data source.

@AdamRJensen
Copy link
Member Author

AdamRJensen commented Mar 1, 2022

In order to use the new version 5.2 (which is still in beta), the URL needs to be updated, e.g.,:

data, input, meta = pvlib.iotools.get_pvgis_hourly(
    latitude=28.965734,
    longitude=117.147418,
    raddatabase='PVGIS-ERA5',
    url='https://re.jrc.ec.europa.eu/api/v5_2/',
)

I suspect this will only be necessary temporarily until the databases are considered stable and migrated to the default URL. The retired databases CMSAF and COSMO remain available through the default URL for now, though they will be removed in the future.

@kandersolar
Copy link
Member

Probably a good idea to scrub mentions of the retired databases from the docstring as well:

PVGIS provides access to a number of different solar radiation datasets,
including satellite-based (SARAH, CMSAF, and NSRDB PSM3) and re-analysis
products (ERA5 and COSMO). Each data source has a different geographical
coverage and time stamp convention, e.g., SARAH and CMSAF provide
instantaneous values, whereas values from ERA5 are averages for the hour.

@AdamRJensen thoughts on tagging this issue for 0.9.1?

@AdamRJensen
Copy link
Member Author

@kanderso-nrel what's the current timeline for 0.9.1? I'll be out of the office until April 5th fyi.

@kandersolar
Copy link
Member

what's the current timeline for 0.9.1

Don't think there really is a timeline. Next couple weeks maybe? Depends on how long it takes us to finish or defer the remaining things in #1424...

@kandersolar kandersolar added this to the 0.9.2 milestone Apr 14, 2022
@kandersolar kandersolar mentioned this issue Jun 1, 2022
8 tasks
@kandersolar
Copy link
Member

@AdamRJensen should we keep this open until we update the tests and docstrings?

@AdamRJensen AdamRJensen reopened this Jul 22, 2022
@AdamRJensen
Copy link
Member Author

@kanderso-nrel Sorry I got ahead of myself

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants