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 Christian, re: GFS 0.5 degree fields were incomplete until Boulder CONDUIT toplevel access was restored > Indeed, the data feed is ok now: I do receive the files completely now…!! Very good. re: > So it seems that there is something related, but it is strange that nobody > else seemed affected. Yes, it was very strange indeed. This is especially the case since LOTS of folks access the 0.5 deg GFS fields through the TDS server on thredds.ucar.edu and other server instances. re: > Some differences with me and other sites: ldm regex and alternate > feed site for conduit. I am unsure what you mean by 'ldm regex'. Do you mean your LDM REQUEST line(s)? re: > It would be nice to know exactly why this was happening! Yes, indeed. I have not been able to come up with any scenario that would explain the problem... 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: SIB-910423 Department: Support CONDUIT Priority: Normal Status: Closed