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: > The period in which I had problems was between 2019-07-18 at 09:00 > till 2019-07-19 at 18:00 (UTC). It would be useful to get information this specific with your original inquiry. re: > When I listed the images Band 1 for FD was available but I could not > retrieve it. Bands 2 and 4 I had no problems with. re: Since we don't keep images this old on our server (goeswest.unidata.ucar.edu), we can't comment about potential problems with any individual image or band. The best I can offer is the following: - the indicated signal strength on our GOES-15 ingest was nominal throughout the period you have indicated - our ingest logs show that there were ingest problems on three occasions during this period Here are the periods that had more than an occasional error: 20190718 08:59:00 - 20190718 09:34:02 20190721 20:53:45 - 20190721 20:54:05 20190722 00:41:49 - 20190722 00:42:00 Our ingest logs do not indicate any serious (non-occasional) errors outside of these periods. The cause of the ingest problems can not be pinpointed from the log files we have. It is likely, however, that some of the problems were caused from electrical activity associated with large thunderstorms that were in the area. re: > Since 2019-07-19 at 18:00 (UTC), everything is back to normal. OK. > Please note that I am not saying that the problem was yours. I am > just trying to find out what the problem was. OK. Comment: - since our main focus is ingest of the primary U.S. operational satellites (GOES-16 (East) and GOES-17 (West)), we are spending less time on our GOES-15 and GOES-14 (this satellite is turned on by NOAA occasionally for testing) activities Given this, it would be a wise for you to consider transitioning from use of GOES-15 to GOES-17 data. 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: LWG-608505 Department: Support McIDAS Priority: Normal Status: Closed =================== NOTE: All email exchanges with 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.