-
Notifications
You must be signed in to change notification settings - Fork 303
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
[Question] Sun Zenith Correction #2781
Comments
Hi @akasom89, indeed, the rationale behind the sun zenith correction is to account for the variation of the incident illumination due to the sun elevation, i.e. making the computed reflectance independent of the illumination condition of the acquired pixel. By dividing with the cosine of the solar zenith angle, you normalise (compensate/cancel out) the effect of the reduced illumination due to the Sun not being at the zenith (directly overhead) of the acquired pixel. |
Thanks @ameraner for your detailed answer. I understand and agree. But based on the formula of converting radiance to reflectance, we have a cos(sun_zenith) in the denominator already. So I was wondering if we are applying that again or not!? |
Satpy does not generally apply the There are one or two exceptions, though. I think the VIIRS reader has SZA correction built-in, but that's due to the underlying data rather than a choice made in Satpy. |
Thanks a lot @simonrp84 for your answer. So it is now clear to me. |
I'll close this issue as answered then, but feel free to add new comments if you need further clarifications! |
I tried to figure out what is the main purpose behind Sun Zenith Correction. I took a look over the paper link (for EffectiveSolarPathLengthCorrector) in the docs.
Is this because we assumed a PPL (plain-parallel) model for atmospheric correction or anything else?
Or that is just to compensate variant incident solar irradiance?
(Because we should have applied cos of sza while converting radiances to reflectance. why is the logic behind doing that again?)
More details is greatly appreciated!
The text was updated successfully, but these errors were encountered: