Alternative datasets for RES time-series generation (NSRDB, Solcast)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 614
- Forks
- 459
- Avg merge
- 4d 14h
- Merged PRs (30d)
- 6
Description
The datasests ERA5 and SARAH which we're currently using do have some limitations, see e.g. #285 .
Recently some newer datasets came to be which might do a better job in those regards:
- NSRDB (National Solar Radiation DataBase by NREL): The PSM model is extending in geographical coverage. METEOSAT PSM v3 for Europe is available.
- Solcast a commercial dataset but with free access options for public researchers and they might be open for a request for use by us.
Both datasets combine satellite data with other datasources and promise high spatial and temporal resolution. The number of available historic years however is limited.
Potentially of interest for @martavp .
Links
- Yang, D., and Bright, J.M. (2020). Worldwide validation of 8 satellite-derived and reanalysis solar radiation products: A preliminary evaluation and overall metrics for hourly data over 27 years. Solar Energy 210, 3–19.
- Bright, J.M. (2019). Solcast: Validation of a satellite-derived solar irradiance dataset. Solar Energy 189, 435–449.9
- Solcast sales comparison: https://solcast.com/historical-and-tmy/comparisons/
- Related
atliteissue: https://github.com/PyPSA/atlite/issues/213
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how the current ERA5 and SARAH datasets are used for time-series generation, then read issue #285 and the related atlite issue #213. Done would require evaluating NSRDB and Solcast coverage, access constraints, and historical availability, followed by a decided integration plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data, data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100