Open gerritholl opened 4 years ago
How could this be addressed in a maintainable way? Move the composites that are currently in seviri.yaml
to a new nwcsaf-geo.yaml
thus providing for ABI, AHI, and FCI in addition to SEVIRI? Would we need to include them into each of abi.yaml
, ahi.yaml
, and fci.yaml
for Satpy to find them there?
Feature Request
Is your feature request related to a problem? Please describe.
I'd like to use the NWCSAF composites defined in
visir.yaml
andseviri.yaml
when reading anwcsaf-geo
file produced with ABI data. This fails for most composites, because the prerequisites as defined invisir.yaml
are not met for geostationary data, and the composites defined inseviri.yaml
are not used when data are coming from ABI, AHI, or FCI.When reading a NWCSAF-GEO file produced with ABI:
When reading one produced with SEVIRI:
Describe the solution you'd like
I'd like that composites such as
cloud_optical_thickness
can be used for any NWCSAF-GEO data, regardless of what geostationary imager was used to produce the data.Describe any changes to existing user workflow
None.
Additional context
Those composites were apparently first added in #41. Reading NWCSAF-GEO from ABI has been correctly possible since #1111 was closed in #1113.