Is your feature request related to a problem? Please describe.
Sometimes platform_name and/or sensor attributes are missing in DataArrays returned by readers (e.g. #2993)
Ideally the platform_name and sensor attributes would align with the names from https://space.oscar.wmo.int/(satellites/instruments). An open question might be how to handle possible renaming e.g. when switching from commissioning to operational setup (e.g. currently space oscar is listing MTG-I1 which will be renamed to Meteosat-12).
Should readers also have these values as properties like in the FCI reader currently?
Describe any changes to existing user workflow
Should not directly affect useres
Feature Request
Is your feature request related to a problem? Please describe. Sometimes
platform_nameand/orsensorattributes are missing inDataArraysreturned by readers (e.g. #2993)Describe the solution you'd like Every reader should put
platform_nameandsensoras attributes inDataArrays. Some readers (e.g. FCI even have properties regarding these values see: https://github.com/pytroll/satpy/blob/c2149175d2256e09ea0f61505a151e5625a80d87/satpy/readers/fci_l2_nc.py#L43-L51)platform_nameandsensorattributes would align with the names from https://space.oscar.wmo.int/(satellites/instruments). An open question might be how to handle possible renaming e.g. when switching from commissioning to operational setup (e.g. currently space oscar is listing MTG-I1 which will be renamed to Meteosat-12).Describe any changes to existing user workflow Should not directly affect useres