Reference NOAA SCN24-54:
https://www.weather.gov/media/notification/pdf_2023_24/scn24-54_channel_realignment_to_sbn_aac.pdfFor reference as it applies to the WMO headers listed:
https://www.weather.gov/tg/tableOnly the following feedtypes are generated by the noaaportIngester:
HDS
IDS|DDPLUS
NEXRAD
NGRID
NIMAGE
NOTHER
The logic in the noaaportIngester source code is such that the product ID and feedtype assigned should not matter what SBN PID it comes in on; nothing should need changed. It is dependent upon the data types in the NOAAPort Transmission Header remaining assigned as indicated in the 1991 NOAAPort Transmission ICD. Thus, the broader feedtype arrangement as indicated in the SCN to be inclusive with using the “ANY” feedtype.
This is problematic for bandwidth-poor requesting instances. The following is specific to REQUEST entries, but the regular _expression_ and feedtype matched can be applied to pqact configurations as well. Use the following as a more refined approach. For the actual product designated, see the WMO reference above for lookup, or Google. Comments have been added to the side for known data types.
IDS|DDPLUS|HDS|NGRID ^AT
HDS|NGRID ^DT #GRID messages
HDS|NGRID ^ES
IDS|DDPLUS|HDS|NGRID ^FT #TAF Reports
HDS|NGRID ^((H[HRTUV])|(GT)) #GRIB1 messages
HDS|NGRID ^((J[SU])|(IU)) #BUFR
HDS|NGRID ^((L[AEHPRTUV])|(M[AEHPR])) #GRIB1 messages
HDS|NGRID ^OE #GRID messages
HDS|NGRID ^PE #Graphics
IDS|DDPLUS|HDS|NGRID ^((R[DEH])|(S[LV]))
HDS|NGRID ^((Y[A-Z])|(Z[A-HO-Z])) #GRIB1 messages
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 home of The Chahiksichahiks (Pawnee), The Umoⁿhoⁿ (Omaha), and The Jiwere (Otoe).