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 Matthew, re: > I wanted to contact you regarding the GOES-16 lightning data on > lead.unidata.ucar.edu > under the ADDE dataset RTGOESR. There doesn’t seem to be much in the way of > data there > as of late. Is there an issue on this machine or is the data not available at > this point? I see GLM netCDF files in the directory that the ADDE server entries are pointing at being updated every 20 seconds as expected, and 'ncdump's do not show any problems with the files. My impression is, therefore, that we are serving everything that we are receiving from our GOES-16 downlink. I also checked the same things on the other server that we maintain that has all GOES-16 products and serves the ABI image and GLM lightning products, atm.ucar.edu, and I see the same thing there - no apparent problem with receipt of GLM files every 20 seconds and viable files. re: > Thanks for having a look! No worries. Quick questions: - which GLM products are you looking at? - which version of McIDAS are you using to look at them? 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: DVA-616382 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.