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

[IDD #VAU-279996]: RE: [ldm-users] Upcoming Changes to NOAAPort/SBN Feeds - July 15th

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: [IDD #VAU-279996]: RE: [ldm-users] Upcoming Changes to NOAAPort/SBN Feeds - July 15th
  • Date: Thu, 18 Jul 2024 10:43:49 -0600
Greetings,

> Regarding the NOAAPort/SBN changes, if the main impact is likely to be 
> products now on HDS will be transferred to NGRID, why can’t we simply replace 
> all references to HDS with HDS|NGRID in our pattern/actions?

You could.  What we cannot guarantee is that there won't be overlaps with WMO 
headers such that some products may overwrite one another.  We think that's 
rather unlikely, but we wanted to highlight what the impacts could potentially 
be.  Another reason could be bandwidth...

Say you are currently REQUESTing HDS from us, using ".*" to capture everything 
on that feed.  That feed is comparatively small to NGRID in terms of the amount 
of data it carries.  If you change that REQUEST to HDS|NGRID and nothing else, 
well now you're getting everything on BOTH of those feeds.  If your site can 
handle that it shouldn't be much of a problem.  But if your site has bandwidth 
concerns this could lead to issues.

It's also worth mentioning that by making a change like REQUESTing a whole new 
feed, you may want to check in on your product queue after a little bit of time 
to see if you need to adjust its size or number of product slots, both can be 
done in the LDM's registry.

Long story short, you can absolutely replace HDS with HDS|NGRID, but there may 
be consequences so be aware.


> 
> You say that “in places within the LDM code the logic gets a little fuzzy.”  
> This leads me to ask (if I may) if Steve Emmerson and Tom Yoskas have retired 
> from Unidata.  I know they were getting close.
> 
> Thanks for your help

Both of those fine gentlemen have moved on to greener pastures, pretty sure 
it's a field of hops.  Stonie Cooper is the current LDM developer and with him 
you are in good hands.


Best,
-Mike

Ticket Details
===================
Ticket ID: VAU-279996
Department: Support IDD
Priority: Normal
Status: Closed
===================
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.