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

[LDM #WMK-256465]: 'Not a WMO format message' error

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: [LDM #WMK-256465]: 'Not a WMO format message' error
  • Date: Thu, 16 Aug 2012 11:07:20 -0600
Becky,

> I'm sorry if the horse is already dead, but we're getting some amount of
> push-back from some folks, so I'm just trying to understand as much as I
> can...
> 
> What makes pqing recognize that it's a new piece of data and therefore
> it doesn't have to be added to the same bufr as the last chunk of data?
> Is it the WMO header?

pqing(1) reads bytes until it sees the WMO start-of-message character sequence 
SOH CR CR LF. It then shifts everything from that point on to the beginning of 
the buffer and reads bytes until it sees the WMO end-of-message character 
sequence (CR CR LF ETX) or until end-of-file (whichever comes first). While 
this is happening, the buffer is expanded, as necessary, to accommodate more 
data. Once the end-of-message or file is seen, everything in the buffer up to 
that point is the WMO message, which is then converted into an LDM data-product 
and inserted into the product-queue.

The problem with the files in question is that they don't contain a WMO 
start-of-message character sequence. Information on the format of a WMO message 
can be found at http://www.nws.noaa.gov/tg/head.html.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: WMK-256465
Department: Support LDM
Priority: Normal
Status: Closed