Dear Martin,
Under EUMHD-3711 the problem was explained to OPS 2021/03/26 (see below). I have no answer so far.
Today I found some old decompressed GOMS2 files from 20190408 and from 20200525 in tmp directories
of two unused servers. I was able to image the data again and print out the "satellite_id". I compared with
GOMS3 data from 20210407 and all Prologue files had satellite_id = 19002. So there is no way to distinguish
GOMS2 from GOMS3 data (except for the file naming of course). I still think that this is a bug in the data.
In what reference are these IDs 19001 and 19002 (and maybe 19003) defined? I found the reference given in
the reader but just saw the "satellite_status" prologue data structure as used in the satpy Electro-L reader.
Best regards,
Ernst
P.S.
I will contact EUMETSAT OPS again and try to make myself understood ....
----------------------------------------------------------------------------------------------------------------------------------------------------
Re: EUMHD-3711 RE: Trial dissemination of Electro-L N3 MSU-GS data
Von
Ernst Lobsiger
An
EUMETSAT User Helpdesk
Datum
26.03.2021 14:34
Dear Debbie
Dear OPS
It appears that there is still a bug in the Prologue (?) data files.
The SatPy 'electrol-hrit' reader has used platform identification with:
...
satellite_status = np.dtype([("TagType", "<u4"),
("TagLength", "<u4"),
("SatelliteID", "<u8"),
("SatelliteName", "S256"),
("NominalLongitude", "<f8"),
("SatelliteCondition", "<u4"),
("TimeOffset", "<f8")])
...
SPACECRAFTS = {19001: "Electro-L N1",
19002: "Electro-L N2"}
...
satellite_id = self.prologue['SatelliteStatus']['SatelliteID']
self.platform_name = SPACECRAFTS[satellite_id]
...
When processing Electro-L N3 (GOMS3) files I notice that satellite_id
is set 19002 and platform_name "Electro-L N2" accordingly. So it seems
I have been successful making N3 images in part because the reader found
the old satellite_id 19002 that we have used for Electro-L N2 (GOMS2)
up to last summer. One of the main Satpy developers proposes EUMETSAT
should check the satellite_id for GOMS3 again and the 'electrol-hrit'
reader would then be updated accordingly. Please also check this thread:
https://groups.google.com/g/pytroll/c/2fjnngvdjlI
Best regards
Ernst