EUMHD-7805 MTG and EUMETCast
toggle quoted messageShow quoted text
Er, some of us - like me - have got to get moving on the use of other 'operating systems' or rather perhaps, rather, processing software
I received this information from Ops a couple of days ago regarding an enquiry I made recently as to MTG data formats and required processing software.
Lots of useful links in the email and further 'MTG operations' links at the bottom of the webpages of the links below and yet more MTG information links on those pages.
From: EUMETSAT User Helpdesk <OPS@...>
To: geojohnt@... <geojohnt@...>
Sent: Wed, 30 Nov 2022 12:41
Subject: EUMHD-7805 MTG and EUMETCast
Dear John Tellick,
Thank you for reaching out to us about this matter.
EUMETCast-Europe will stay the same in the foreseeable future, with only the planned evolutions on the transponder configurations on prime and backup satellites. You can read more about it here: https://eumetsatspace.atlassian.net/wiki/spaces/DSEC/pages/1827045377/EUMETCast+Europe+Future+Transponder+Evolution+Updated
On the other hand, the data format of the MTG-FCI data will be completely different than the current MSG-SEVIRI data, in terms of file format, compression, filenames, etc. The FCI test data can be used for assessment and gaining familiarity. More information can be found here: https://www.eumetsat.int/mtg-test-data
As can be expected, the existing MSG processing/visualization software wouldn't handle the MTG data. However, some software packages, like the mentioned PyTroll is known to be ready for MTG-FCI data. Some other manufacturers are also updating their software for the next generation of EUMETSAT satellites. There is a list of manufacturers available in our website: https://www.eumetsat.int/equipment-manufacturers
The PyTroll software is supposed to be working also on Windows operating system. The details and the documentation can be found at https://www.eumetsat.int/software and http://pytroll.github.io/
EUMETSAT User Service Helpdesk
From: geojohnt@... <geojohnt@...>
Sent: Tuesday 22 November 2022 15:07
To: EUMETSAT User Helpdesk <OPS@...>
Subject: MTD and EUMETCast.
WARNING: This email originated outside the organisation. Treat links and attachments with caution.
I'm thinking ahead but with the possible launch of E 10-B tomorrow - part of the new chain, I'm wondering when MTG data becomes operational next year if EUMETCast will remain in its currant transmission format.
Or, will there need to be a new transmission and/or data labelling format - requiring new processing/data compilation software.
You will be aware that there is a lot of talk on the MSG-1 Group at the moment about Satpy (which I know nothing about) but I think it runs on Linux.
It had been suggested by some earlier that this was the way to go for MTG data.
So will Linux be the preferred operating system and/or will Windows remain viable?
The email message you have received has been written by a EUMETSAT contractor, and although sent in good faith shall neither be binding nor construed as constituting a commitment by EUMETSAT, except where provided for in a written agreement or contract or if explicitly stated in the email. Please note that any opinions presented in this email are solely those of the contractor, working independently and not as an employee of EUMETSAT, and as such does not necessarily represent and share the views of EUMETSAT.
This message and any attachments are intended for the sole use of the addressee(s) and may contain confidential and privileged information. Any unauthorised use, disclosure, dissemination or distribution (in whole or in part) of its contents is not permitted. If you received this message in error, please notify the sender and delete it from your system.
I am not proffesional programator but I succeeded build software for MTG-I compressed and decompressed
data. Software run on windows platform read basic bands and create RGB compossite and GLM data read also.
I am sendding screenshot
Thank you for sharing Roman. Quite impressive.,toggle quoted messageShow quoted text
On 14 Dec 2022, at 16:35, Roman Zamiesal <msg1@...> wrote: