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

20040701: Level II Nexrad Feed (cont.)

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: 20040701: Level II Nexrad Feed (cont.)
  • Date: Thu, 01 Jul 2004 08:35:10 -0600
>From: Adam Taylor <address@hidden>
>Organization: ULM
>Keywords: 200406301714.i5UHENWb016674 IDD Level II

Adam,

re: how many NEXRADs are you intending to get

>One, is this right?
>
>request  CRAFT  "/p......"   bigbird.tamu.edu

No.  The headers on the Level II data are significantly different from
the headers on the Level III products.  Here are a couple of examples
from a notifyme on bigbird:

Jul 01 14:29:09 notifyme[29747]: f44161e7832125dc9693f05977ff7ceb    19885 
20040701142909.374   CRAFT 149009  L2-BZIP2/KOAX/20040701142743/149/9
Jul 01 14:29:10 notifyme[29747]: 19319e766fb19fafdd3f8c3710ad815f    20340 
20040701142909.569   CRAFT 146017  L2-BZIP2/KTLH/20040701142639/146/17

So, your request for a single station would look something like:

request CRAFT   "L2-BZIP2/KTLH" bigbird.tamu.edu

This example assumes that you wanted to request the data from KTLH, of course.

>Second,  Bigbird is not allowing me to connect.  I get a 
>RPC: Unable to receive; errno = Connection reset by peer

My ldmd.conf typo.  It is allowing you now:

Jul 01 14:28:44 bigbird tornado(feed)[29644]: topo:  tornado.geos.ulm.edu CRAFT 

>I know that the second error may be beacuse the request line may be incorrect.

Nope, it was a typo.

>Thanks

No worries.

>Adam Taylor
>Computing Center
>University of Louisiana at Monroe

Cheers,

Tom
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publically available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.