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 Donna, As Robb suggested, it may be time to find another upstream node. One that carries all the feedtypes you desire. I am thinking University of Oklahoma. Would you please do a traceroute stokes.metr.ou.edu from your machine and copy the results in a message to me to determine the viability of that path. They are currently getting all feetypes that you are interested in and have good top level connections. Let me know, -Jeff __________ Jeff Weber Unidata/NWS-COMET Case Study Library University Corp for Atmospheric Research address@hidden PH:303-497-8676 URL--http://www.unidata.ucar.edu/staff/jweber ________________________________________________ On Wed, 23 Feb 2000, Robb Kambic wrote: > Jeff, > > Can you handle this one, I don't know why Donna is not getting the data > she needs. This might be a time for us to find a new upstream site > for UKANS besides ORST. > > RObb... > > =============================================================================== > Robb Kambic Unidata Program Center > Software Engineer III Univ. Corp for Atmospheric Research > address@hidden WWW: http://www.unidata.ucar.edu/ > =============================================================================== > > ---------- Forwarded message ---------- > Date: Wed, 23 Feb 2000 10:46:15 -0700 > From: Unidata Support <address@hidden> > To: address@hidden > Subject: 20000223: IDD to Kansas > > > Robb, > > Iowa State does not appear to be receiving/requesting any > data except NLDN and DIFAX. UKans is apparently feeding > the Unidata stream from ORST. > > Chiz > > > LDMBINSTATS > ldm-5.0.6 homer.geol.iastate.edu 2000022316 NLDN 7 2072 + > 20000223163641 striker.atmos.albany.edu 0.00 0@0000 > ldm-5.0.6 homer.geol.iastate.edu 2000022316 DIFAX 11 1245019 + > 20000223163954 lightning.alden.com 0.00 0@0000 > ldm-5.0.6 homer.geol.iastate.edu 2000022315 NLDN 10 1932 + > 20000223155500 striker.atmos.albany.edu 0.00 0@0000 > ldm-5.0.6 homer.geol.iastate.edu 2000022315 DIFAX 13 1553514 + > 20000223154056 lightning.alden.com 0.00 0@0000 > LDMEND > TOPOLOGY > homer.geol.iastate.edu chinook.phsx.ukans.edu FSL2 > unknown unknown > TOPOEND > > > > ------- Forwarded Message > > >To: address@hidden > >cc: address@hidden > >From: address@hidden > >Subject: FSL profiler data > >Organization: . > >Keywords: 200002231630.JAA06185 > > We have set up our LDM to receive the netCDF profiler data from > FSL as opposed to the BUFR profiler data. However, we are still > not receiving any profiler data although we have both GEMPAK > and McIdas decoders set up. No log files exist for the profiler > data either. The only thing I can think of is that Iowa State > (our upstream feed) does not receive those data. That seems > amazing since I know there are research projects at Iowa State > which use profiler data. What steps do we need to take to receive > these data? > > Donna Tucker http://chinook.phsx.ukans.edu/tucker.html > address@hidden Department of Physics and Astronomy > (785) 864-4738 (new area code!) University of Kansas > (785) 864-5262 (fax) Lawrence, KS 66045-2151 > > > > > > ------- End of Forwarded Message > >