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

RE: H+1 obs appearing in H+0 file (fwd)


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

---------- Forwarded message ----------
Date: Tue, 29 Feb 2000 14:32:57 -0500
From: Dan Vietor <address@hidden>
To: 'Kevin Tyle' <address@hidden>, address@hidden
Subject: RE: H+1 obs appearing in H+0 file

> I've noticed that hourly METAR observations for
> many sites seem to appear in two separate hourly files,
> at least for those receiving via NOAAPORT.  Example:
> ...
> It appears that many of the METARs that come in their own individual
> bulletin are for hour H+1 but appear in file H+0.

This is standard procedure.  Many of the early reports, say 1852Z for
19Z, come in initially in the product with a time stamp of 18xxZ.  The
LDM then places these reports in the 18Z file and not the 19Z as it
should be.  NWS has been doing this since the very beginning so handling
this isn't new.  Luckily, most of these early reports get duplicated in
a 1900Z report such as a SAUS80 product that comes out shortly after the
top of the hour.

So to get all the possible METARs, you must decode more than one hour of
data.

________________________________________________________
Daniel Vietor               Mail: address@hidden
Unisys Corp                 Title: Engineer/Meteorologist
221 Gale Lane               Phone: 610-444-2407
Kennett Square PA 19348     Fax: 610-444-2420