Re: Still more metar2nc problems

• To: "Bryan G. White" <bgwhite@xxxxxxxxxxxx>
• Subject: Re: Still more metar2nc problems
• From: Robb Kambic <rkambic@xxxxxxxxxxxxxxxx>
• Date: Fri, 11 Feb 2000 10:01:11 -0700 (MST)

Bryan,

I did another version of the metar2nc decoder to enter the reports in the
correct files according to date. I used your raw test data from the
command line and all the reports where put into the correct files except
reports that the time was different than the bulletin time by 30 hours.
The command line:

% metar2nc metar.cdl 0002 < testData

The 0002 represent the year and month of the raw data.

Let me know if you find any problems because I want to make a official
release soon.

On Fri, 4 Feb 2000, Bryan G. White wrote:

Robb,

The metar2nc worked with the 2345z-2359z data if metar2nc was being used in the 
pqact.conf file of ldm.  This gets around my imediate need, but still would be nice if it 
would work "correctly" with ascii/raw files.

Thank you for your help

Bryan

> > Bryan, > > I made some fixes to the perl decoders that should solve all the problems.

> Would you want to test it on your machine?  The modified decoders are in

> the UPC anonymous ftp decoders directory. > > ascii2nc buoy2nc metar2nc sao2nc syn2nc ua2nc ldmConnect > > The reason you might have been missing some of the reports is that they

> were put into the wrong file.

> > Let me know how this works out. > > Robb... > > > > On Mon, 31 Jan 2000, Bryan G. White wrote: > > > Rob, > > > > I've got a Y2k problem and a I don't know what problem with metar2nc > > > > 1) Around 0z every day I get files created with "000" as the year....

> >     ie. 000013123_metar.nc.  Must be the dreaded perl "2000 = 000" bug I've

> > been squashing in some of my programs. It only does this after 0z with > > data that has a time stamp before ~2345z. > > > > I think the problem is around line #1558 with formating of the year > > variable. > > > > 2) I can't get the ~23:45-23:59 hour obs to decode. It's vanishing in thin

> >     air.  I don't know what is going on.  I manually decode a file that
> >     has a 23:50 ob, but it isn't in the *metar_nc file.  The file has obs 
from
> >     before 0z and after 0z.  It does decode the after 0z obs.

> > > > It does however show up int the rawmetars.*.nc file. > > > > > > Bryan > > > > ==============================================================================

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

> >

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