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

[LDM #LJY-425624]: NEXRAD Level II Feed

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: [LDM #LJY-425624]: NEXRAD Level II Feed
  • Date: Wed, 04 Jun 2008 13:20:15 -0600
Alan,

> So sorry....The columns are 1) Radar ID; 2) volume scan number
> (generated by the radar); 3) sequence number; 4) date and time of volume
> scan (when the scan began); 5) time it was received (local time); 6)
> either blank or an E to signify the end of the scan.
> 
> It's just an excerpt of the last few radial files.  The sequence number
> identifies the radial file from the first to the last.  All domestic
> radars start the sequences at 1, I have received a few from S. Korea
> that begin with 0.  When you do an ldmadmin watch, you will see
> something like:
> 
> Jun 04 17:27:19 pqutil INFO:     4411 20080604172718.712 NEXRAD2 698010
> L2-BZIP2/KESX/20080604172424/698/10
> Jun 04 17:27:19 pqutil INFO:    10210 20080604172718.708 NEXRAD2 449044
> L2-BZIP2/KUDX/20080604172142/449/44
> Jun 04 17:27:19 pqutil INFO:     8917 20080604172719.286 NEXRAD2 55002
> L2-BZIP2/KFSD/20080604172710/55/2
> Jun 04 17:27:19 pqutil INFO:     7807 20080604172719.289 NEXRAD2 249002
> L2-BZIP2/KLRX/20080604172710/249/2
> Jun 04 17:27:20 pqutil INFO:    21976 20080604172719.145 NEXRAD2 593016
> L2-BZIP2/KBUF/20080604172515/593/16
> Jun 04 17:27:20 pqutil INFO:    13514 20080604172719.670 NEXRAD2 175054
> L2-BZIP2/KSFX/20080604172350/175/54
> Jun 04 17:27:20 pqutil INFO:    14280 20080604172719.516 NEXRAD2 647016
> L2-BZIP2/KBGM/20080604172517/647/16
> Jun 04 17:27:20 pqutil INFO:     7861 20080604172719.853 NEXRAD2 507025
> L2-BZIP2/KAMA/20080604172008/507/25
> Jun 04 17:27:20 pqutil INFO:     6611 20080604172817.869 NEXRAD2 201029
> L2-BZIP2/KHNX/20080604171807/201/29/E
> Jun 04 17:27:20 pqutil INFO:     7651 20080604172720.363 NEXRAD2 389029
> L2-BZIP2/KTLX/20080604171742/389/29/E
> Jun 04 17:27:20 pqutil INFO:     6660 20080604172720.348 NEXRAD2 287034
> L2-BZIP2/KDIX/20080604172256/287/34
> Jun 04 17:27:20 pqutil INFO:    19050 20080604172817.933 NEXRAD2 202002
> L2-BZIP2/KHNX/20080604172817/202/1
> Jun 04 17:27:21 pqutil INFO:     8426 20080604172720.414 NEXRAD2 390002
> L2-BZIP2/KTLX/20080604172720/390/1
> 
> It's that last part that corresponds with my log:
> KESX/20080604172424/698/10 (i.e. 1) KESX; 2) 698; 3) 10; 4) 20080604172424)
> 
> One interesting point I have noticed, sometimes the first radial file
> might arrive slightly early or at the same time as the previous ended
> radial files.  The example above does show how very close it can be.
> That really isn't a big deal because they are separate volume scans.

Thanks.

Can you display the different-sized volume scans from NCDC and Boulder 
to see if they're truly different?

> You do realize that after you become more educated about this, I am
> going to hit you up for some configuration advice on how best to
> configure the LDM at the radar site and at the top tear sites.  I think
> we could use some tuning help especially with the Build 10 SuperRes
> deployment.

We'll be glad to help however we can.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: LJY-425624
Department: Support LDM
Priority: Normal
Status: On Hold