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 Dave, Sorry for the silence today... when it rains, it pours (sigh). re: > Ok so here is where I am at. Clobbering everything in ldmd.conf, except for > NEXRAD2 and > NEXRAD3 gives me both data sets just fine. Slowly adding more datasets to > the ldmd.conf > file get me to a point where the NEXRAD2 data stops coming in. Sounds like a > bandwidth > issue to me. Does it sound like that to you? I looked at the latencies for the feeds you are requesting from idd.unidata.ucar.edu earlier today (after restarting the LDM on the idd.unidata.ucar.edu cluster node that you have been feeding from, and then got waylaid with another IDD-related problem), and came to the conclusion that there is some sort of network issue closer to Millersville than to Boulder. The test you relate above pretty much confirms this view. Again, I apologize for the slow response! 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: HFB-541734 Department: Support IDD Priority: Normal Status: Closed