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

Re: TIGGE data sets

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: Re: TIGGE data sets
  • Date: Mon, 11 Sep 2006 10:45:40 -0600
Good morning Brent,
Great timing as I'm back from Ocean City, MD this morning!

Yes, go ahead and point the WOC ensembles to GRIB2 rather than GRIB1.

All CONDUIT ensemble data is still being sent from the TGSV32 server.
Once the WOC is inserting GRIB2, I will create a transition time
schedule for the top level
relays to switch their feeds of ensembles from tgsv32 to WOC.

One note is that the NCAR TIGGE group has a direct  feed to the WOC, so
they
will start getting those GRIB2 products immediately via that route
(which is good I assume).

Once we have the CONDUIT feed transitioned to the GRIB2, we can schedule
a removal of the ensemble posting to tgsv32 (widdling our way off of
tgsv32).

Thanks,

Steve


On Mon, 2006-09-11 at 07:13 -0400, Brent A. Gordon wrote:
> Hi Steve,
> 
> We have the GRIB2 version of the ensemble data at the WOC now.  I was
> wondering if I could point CONDUIT to those data now instead of the
> GRIB1 versions?  Is anyone pulling the ensembles from the WOC system?
> 
> Thanks,
> 
> Brent
-- 
Steve Chiswell <address@hidden>
Unidata