Re: missing SPECI reports and the db file entries

hiya,

i did a quick grep of the last 3 days for reports that have ".... SPECI"
as the first part. the only station that came up was:

2004091718_sao.wmo:SBBE SPECI  ...

is this the only station or are there other?  this is not the standard
format of according to the WMO 306  on codes.  unidata has been trying to
deprecate pqsurf processing because it's a fragile piece of code and it
really shouldn't be part of the ldm because it's a decoder. With that
being said, is there some other filter to replace the pqsurf code? thus
eliminating pqsurf.conf and the pqsurf queue. i would like to open a
discussion to find out the available options and the main reasons for
using pqsurf.

thanks,
robb...


On Mon, 20 Sep 2004, Kevin R. Tyle wrote:

> I have noticed this too; it appears to be a bug in the way METARs
> are displayed when read from a METAR file that is in the gdbm database
> format.  I have never investigated it further, but have typically
> fallen back to using "flatmetar" which reads from METARs written
> in ASCII format.  You sacrifice a bit of speed, but make up for
> it in the completeness of the data.
>
> ______________________________________________________________________
> Kevin Tyle, Systems Administrator               **********************
> Dept. of Earth & Atmospheric Sciences           address@hidden
> University at Albany, ES-235                    518-442-4578 (voice)
> 1400 Washington Avenue                          518-442-5825 (fax)
> Albany, NY 12222                                **********************
> ______________________________________________________________________
>
> On Mon, 20 Sep 2004, Neil R. Smith wrote:
>
> > All,
> > It was pointed out to me recently that our weather program(v4.10) was
> > not printing out all SPECI special reports that are available in the
> > bulletins.
> >
> > While looking at both a text and dbfile output from pqsurf, where both
> > pqsurf.conf entries have the same header request, and comparing with
> > output from weather queries, it seems that reports that are preceded
> > with a line that looks like xxxxSPECI, where xxxx is the 4-character
> > station id, are not output by METAR, METARDECODE, or METARFULLDECODE,
> > whereas those preceded with just a simple line that has only the
> > characters SPECI are output by these weather commands.
> >
> > Is this a known issue with weather, or is it a problem with the DBFILE
> > action in the LDM, or perhaps a bad header request entry in pqsurf.conf?
> >
> > Is there a known solution?
> >
> > (I can't find a way to search the weatherbud mailing list at unidata, so
> > I don't know if this has been treated before.)
> >
> > Our pqsurf ldmd.conf entry looks like
> >
> > exec    "pqsurf -p ^S(A....|P....|XUS8.|XUS91) -Q /que/pqsurf.pq
> > /unidata/ldm/etc/pqsurf.conf"
> >
> > Our pqsurf.conf looks like
> >
> > WMO     ^metar (....) ([0-3][0-9])([0-2][0-9])
> >         DBFILE  /data/ddplus/db_metar/(\2:yy)(\2:mm)\2\3.METAR_DB \1
> >
> > WMO     ^speci (....) ([0-3][0-9])([0-2][0-9])
> >         DBFILE  /data/ddplus/db_metar/(\2:yy)(\2:mm)\2\3.METAR_DB \1
> >
> > Thanks,
> > -Neil
> > --
> > Neil R. Smith, Comp. Sys. Mngr.             address@hidden
> > Dept. Atmospheric Sci., Texas A&M Univ.     979/845-6272 FAX:979/862-4466
> >
> >
>

===============================================================================
Robb Kambic                                Unidata Program Center
Software Engineer III                      Univ. Corp for Atmospheric Research
address@hidden             WWW: http://www.unidata.ucar.edu/
===============================================================================