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.
------- Forwarded Message >To: address@hidden >cc: Joan Brundage <address@hidden>, >cc: "Amenda Stanley" <address@hidden>, >cc: address@hidden, >cc: Unidata Support <address@hidden>, >cc: address@hidden >From: "Amenda Stanley" <address@hidden> >Subject: Re: ACQ-SERVR >Organization: . >Keywords: 200003221824.LAA15780 Glenn, I'm not at all familiar with N-AWIPS/GARP, so I may not be of much help. Perhaps COMET staff could be of more help. In any case, the AWIPS software expects the CCB, so it is handled implicitly by AWIPS. The non-AWIPS software we run here at FSL handles either type of header. My suggestion to you is to set up some code that is run by LDM's pqact which does this work before passing the data on to the N-AWIPS/GARP code. This same kind of thing could be done to handle the GRIB problem Alan brought up a couple of weeks ago. By the way, I would strongly suggest that this kind of change to the data is not made upstream of your data archive system. My guess is that for the NOAAPORT data archive you'll want the data to be as unchanged as possible. Amenda ------------------------------------------------------------------ Amenda Stanley E-mail: address@hidden Forecast Systems Laboratory Fax: 303-497-7259 U.S. Department of Commerce Phone: 303-497-6964 325 Broadway Mail Code: R/FS2 Boulder, CO 80303-3328 ------------------------------------------------------------------ On Tue, 21 Mar 2000, Glenn Rutledge wrote: > > Joan, > We've hit a snag with the current implementation of Unidata's N-AWIPS/GARP. > > Regarding text data, it appears Unidata takes the NOAAPort feed and strips > the communications control block, adds: > cntl A (cr/cr/LF) then adds a 3 digit Sequence Number (just like the Family > of Services) the TEXT (cr/cr/LF) then a cntl C. > > The LDM process downstream, and eventually the N-AWIPS decoders can read > the data. > > How does FSL deal with this? How can NCDC overcome this? Can you look into > this? Thanks, Glenn > > ------- End of Forwarded Message