-
Notifications
You must be signed in to change notification settings - Fork 321
Open
Milestone
Description
(related to #3271 )
As of today, the "reflectance" calibration level refers to both sunz normalized and not normalised "reflectance" quantities. In order to correct the situation, we need to differentiate these two quantities, and we thus need to add a new "oblique_reflectance" calibration level to refer no the non-normalised quantity.
The objective here is to get a minimal working solution, without bells and whistles to start with.
We have identified a few things to discuss/work on:
- Need to add utilities for readers:
if data_id[“calibration”] == _obliquereflectance_name():
# do oblique-reflectance calibration
elif data_id[“calibration] == “reflectance”:
# do real-reflectance calibration- Update reader YAML files with new calibration names where necessary
- Add oblique reflectance calibration name to builtin Enum and any appropriate custom reader YAML definitions for calibration
- Satpy.config entry for using new calibration name for oblique-reflectance
- Do “sunz_corrected” modifiers update the calibration name? Can the Dependency Tree handle that?
- Would need to test:
scn.load([“C01”], modifiers=(“sunz_corrected”,))
scn.load([DataQuery(name=”C01”, calibration=”reflectance”, modifiers=(“sunz_corrected”,))]) (should this crash?)
scn.load([DataQuery(name=”C01”, calibration=”oblique_reflectance”, modifiers=(“sunz_corrected”,))])- Lazy workaround: Don’t update calibration in modifier(s)
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
No status
Status
No status