[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20000321: FYI, NCDC

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.

  • Subject: 20000321: FYI, NCDC
  • Date: Tue, 21 Mar 2000 14:52:32 -0700
------- Forwarded Message

>To: Joan Brundage <address@hidden>,
>To: "Amenda Stanley" <address@hidden>
>cc: address@hidden,
>cc: Unidata Support <address@hidden>
>From: address@hidden
>Subject: ACQ-SERVR
>Organization: .
>Keywords: 200003212017.NAA28283



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