This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Hi, re: > Hi any update on Ticket ID: QWH-540341 (update of mcidas x to read MTG > METEOSAT data) After getting sidetracked by a variety of things (including a trip to Witney, England), I was able to concentrate on putting together a new McIDAS release that incorporates the changes UWisc/SSEC made in their v2023.1 release. I am in the process of finalizing the incorporation of the SSEC changes, and should be testing builds sometime next week. The Unidata distribution of McIDAS is a superset of SSEC's, and getting the make process to work with the different file/directory layout is quite finicky. By the way, I did not see anything comments in the SSEC list of changes made that relate to the serving/use of MTG data. I think I recall that they have developed a new ADDE server in Python that was written to support MTG imagery, but that is not part of their standard release, so I will need to assess what they have done and see if/how it can be incorporated in the Unidata release. I apologize for the delays in getting a new McIDAS release out! Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: RNS-517280 Department: Support McIDAS Priority: Normal Status: Open =================== NOTE: All email exchanges with NSF Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.