Panu Lahtinen
Panu Lahtinen
The calibration is what is loaded from the files (given implicitely in the `.load()` call), so I think that's fine. The standard name might need updating. Though I'm not sure...
Typically the calibration *is* loaded from the files as per-channel calibration coefficient attributes. With modifier you can't use the calibration coefficients stored within the files, as those are accessible only...
I approve
I'll do some more refactoring to `_reduce_data()`.
Yes, I think getting completely rid of the images from the repo requires rewriting the git history on force-pushing.
#2670 was about EUMeTrain RGBs, not the newer WMO definitions.
`oblique_toa_bidirectional_reflectance` is my candidate as the standard name in https://github.com/orgs/cf-convention/discussions/429#discussioncomment-14616050
The `oblique_reflectance` was my suggestion as the CF standard name for the non-SZA corrected TOA reflectance. The other suggestions tried to explain everything and so are ver,y very, very long....
So if we had the `enhancement` functionality available we could do this? ```yaml geo_color: compositor: !!python/name:satpy.composites.fill.DayNightCompositor lim_low: 78 lim_high: 88 standard_name: geo_color_day_night_blend name: geo_color enhancement: noop prerequisites: - true_color -...
The actual crash was caused by something else. The error message coming from the first engine to be tested just confused me. The actual cause is mystery, but it wasn't...