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

[LDM #NFA-100528]: SBN Channel Alignment Question

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 #NFA-100528]: SBN Channel Alignment Question
  • Date: Mon, 12 Aug 2024 12:58:17 -0500
Mike - you will not need to go to that level of effort.

Unless, Raytheon does something different with their RPM packaged LDM, there 
are only the following feedtypes generated by the noaaportIngester:

HDS
IDS|DDPLUS
NEXRAD
NGRID
NIMAGE
NOTHER

The reality is the logic in the code is such that the product ID and feedtype 
assigned should not matter what SBN PID it comes in on . . . so the fact is, 
probably nothing will need changed at all.  The notice is providing the worst 
case, which is the the primary contractor for the uplink changes the data type 
in the NOAAPort transmission header such that it is outside of the NOAAPort 
transmission ICD definitions.  The only two data types listed in the notice 
that I am unsure of, if things go worst case, is the WMO ^AT and WMO ^FT.  I 
believe they are both coded as either IDS|DDPLUS or HDS . . . 

On the NMC channel, that will be IDS|DDPLUS, NEXRAD, NGRID, and HDS . . . and 
of the products being moved, we know that NGRID will stay the same, and that 
the only other products are all feedtyped HDS.

Oddly enough, the first product in the list, WMO ^AT . . . is not defined.  I 
am almost sure it is BUFR, so it would be cast as HDS.  The WMO ^HR is a GRIB1, 
so it is currently HDS.  The WMO ^JU is BUFR.  The next two on the list are 
GRIB, but I believe - ironically - they are the SPC convective outlook grids, 
from your neighbors.

This all boils down to - except for the two conditions I indicated very early 
on - is for those products on the NMC channel that you were configuring for 
HDS, adding the pipe NGRID to make sure.  It would be certainly more 
restrictive than an "ANY".  On the two I mentioned, it is nice that they are 
pretty specific, so you could do an ANY ^AT and ANY ^FT, just to be safe.

Does that help?  I am coming out with a more information this week on the 
change.
-
Stonie Cooper, PhD
Software Engineer III
NSF Unidata Program Center
University Corporation for Atmospheric Research
I acknowledge that the land I live and work on is the traditional territory of 
The Pawnee, The Omaha, and The Otoe.

Ticket Details
===================
Ticket ID: NFA-100528
Department: Support LDM
Priority: Normal
Status: Open
===================
NOTE: All email exchanges with NSF Unidata User Support are recorded in the 
Unidata inquiry tracking system and then made publicly 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.