Here's the smoking gun from our logs, confirming that the errant bulletin
was flagged as a binary file with the feedtype set to HRS:
Mar 17 23:58:41 cascade pqact[11540] INFO: 3731 20090317235409.703
HDS 83649598 SAUS80 KWBC 180000
We split our pqact's into separate files according to the feedtype, so
I'll just add in a rule that will hopefully catch these strays the next
time this happens.
______________________________________________________________________
Kevin Tyle, Systems Administrator **********************
Dept. of Atmospheric & Environmental Sciences ktyle@xxxxxxxxxxxxxxxx
University at Albany, ES-235 518-442-4578 (voice)
1400 Washington Avenue 518-442-5825 (fax)
Albany, NY 12222 **********************
______________________________________________________________________
On Wed, 18 Mar 2009, akrherz@xxxxxxxxxxx wrote:
On Wed, 18 Mar 2009, Larry D. Oolman wrote:
On a whim I downloaded the 23Z hrs file from motherlode. I found the
missing report. The first metar has an errant character so the report was
interpreted as being binary and set the feedtype as HRS.
That is very interesting! So, I had better fix my various pqact files to be
sure to use WMO in the case of when a product shows up in the HRS feed...
As an aside, anybody else noticing an increase in the number of stray control
characters showing up in various text products? The ADMNCF has had it a
bunch lately. I have also noticed the "\'" string showing up in products too
:(
daryl
_______________________________________________
ldm-users mailing list
ldm-users@xxxxxxxxxxxxxxxx
For list information or to unsubscribe, visit:
http://www.unidata.ucar.edu/mailing_lists/
