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

20010521: CMC GEM data

Eric,

CMC GEM model data is not a data set that is currently available via IDD.
At this time, we only have preliminary contacts with the CMC as far as setting
up the LDM on their end to provide the data. The data is not on NOAAPORT.

Steve Chiswell
Unidata User Support


>From: Eric Nelson <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200105212351.f4LNpep17821

>
>Anne,
>
>I'll forward your message on to the rest of the people who help run things
>here.  As far as getting information disseminated, I'm not surprised to
>hear that often it doesn't reach the people who need to know.  I'm not
>sure what the case is for other sites, but the person listed as the
>primary contact is not the person who actually maintains the various
>components of our system on a day to day basis.  In reality, the primary
>contact does very little administration of ldm and data related matters.  
>
>On an unrelated note, I wrote to support@unidata... on May 7 about how to
>gain access to GEM gridded data via ldm and have not recieved any type of
>reply.
>
>Have a good evening.
>Eric.
>
>On Mon, 21 May 2001, Anne Wilson wrote:
>
>> Eric,
>> 
>> >From the beginning of the availability of the radar data we've planned
>> on propagating only the NEXRAD (aka NNEXRAD) feed using a separate
>> topology, keeping the FNEXRAD feed flowing along the usual routes.  See
>> the fourth paragraph of
>> http://www.unidata.ucar.edu/packages/ldm/receivingRadar.html.  There
>> were also notices emailed to that effect.
>> 
>> But, you're not the only one that didn't get the message.  I've
>> discovered how difficult it is to convey information to a large group of
>> busy people.  We tried really hard to keep people informed while not
>> spamming them with too much information - a tricky balancing act that
>> always seems to fail somewhere along the line.  Oh well...
>> 
>> In theory, Pete should allow the FNEXRAD feed for you.  In practise,
>> people seem to be getting FNEXRAD from wherever.  It's a low volume feed
>> - you might as well do what works best for you.  
>> 
>> The only possible problem I can think of is that your failover script
>> will only provide automatic failover for your primary feed.  Currently,
>> you'd have to failover manually if your NEXRAD feed goes down.  (And,
>> even then it's only detected if the host actually dies, which was not
>> the case today.)  So, if FNEXRAD is really important to you I'd ask Pete
>> to feed it to you simply to increase the chances that you'll get it
>> regularly.
>> 
>> Anne
>> 
>> "In theory, theory and practise are the same.  In practise, they're
>> not."
>> -- 
>> ***************************************************
>> Anne Wilson                  UCAR Unidata Program            
>> address@hidden                      P.O. Box 3000
>>                                        Boulder, CO  80307
>> ----------------------------------------------------
>> Unidata WWW server       http://www.unidata.ucar.edu/
>> ****************************************************
>> 
>
>_______________________________________________________________________
>Eric Nelson                        College of Dupage Meteorology Dept.
>NWP WXP Graphics/Forecaster              http://weather.cod.edu/
>Lab:(630) 942-2590                      address@hidden    
>Desk:(630) 942-2188                     address@hidden
>
>"I love deadlines.  I especially like the whooshing sound they make as
>they go flying by."     --Douglas Adams
>_______________________________________________________________________
>
>