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.
John,
I'm afraid I misled you in saying that the "same" feed-splitting
that you're doing for CONDUIT data could also be done for NEXRAD2
data.  *Exactly* the same trick can't be done because not all NEXRAD2
product-identifiers end with a numeral.  For example:
    L2-BZIP2/KHNX/20071226172702/615/45/E
    
The "/E" signifies the last set of radials of a horizontal
sweep.  I was thinking "similar" rather than "same".
You could try making the "/E" optional, e.g.,
    [05](/E)?$
    [16](/E)?$
    [27](/E)?$
    [38](/E)?$
    [49](/E)?$
Regards,
Steve Emmerson
Ticket Details
===================
Ticket ID: HMA-788722
Department: Support LDM
Priority: Normal
Status: On Hold