Skip to content
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

[ENH] download and use horizon data to affect sky diffuse and far shading #1290

Open
mikofski opened this issue Aug 25, 2021 · 4 comments
Open

Comments

@mikofski
Copy link
Member

Problem statement

  1. most satellite data (CPR, SGIS, PSM3, ...) doesn't include effects of horizon, this info is downloaded separately, but pvlib doesnt' currently have any iotools for horizon download. Some sources for horizon data are pvgis and meteonorm, but make sure to follow the correct conventions. Also it's possible that horizon data can be derived from GIS elevation data like USGS or SRTM.
  2. once horizon data is obtained in the format {azimuth, elevation} then it can be applied to (a) reduce the sky dome of isotropic diffuse sky irradiance by integrating the ratio of the solid angles and (b) account for "far shading" or shade that affects the entire PV array uniformly, eg like the sun being partially obscured by a very distant (typically >30-km) mountain,

Describe the solution you'd like

  1. add pvgis horizon download to iotools
  2. complete Calculating horizon profiles and associated shading losses #758 which given a horizon profile (azimuth, elevation) calculates the effect on diffuse sky
  3. ditto for far shading

Describe alternatives you've considered
require users to account for horizon effects in the satellite data separately. pvgis already offers this option, but afaik, psm3 does not. Not sure about cpr or sgis

Additional context

@UGuntupalli
Copy link

@mikofski - Has someone done a PR for this ? If not, I can take a stab at it, if you want to mentor

@cwhanse
Copy link
Member

cwhanse commented Feb 8, 2022

#1395 is the most recent work. I haven't gotten far enough to see if #1395 supercedes #1295. #1395 has picked up some, but not all of the code in #758 which is stalled and unlikely to move ahead.

@bgpierc
Copy link
Contributor

bgpierc commented Feb 8, 2022

#1395 doesn't include #1295 but will work along side it. This would give us three methods to calculate horizon: locally using the horizon module as well as downloading preprocessed results from pvgis (implemented in #1395) or the method from #1295 in the iotools module

@UGuntupalli
Copy link

UGuntupalli commented Feb 10, 2022

@bgpierc - I am willing to take a stab at it this weekend, can you please do me a favor and guide me to what is the ask here, the issues are a little confusing to catch up on because of my lack of familiarity with pvlib and what has already been done and what needs to be achieved

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

No branches or pull requests

4 participants