Re: [ldm-users] SCN 24-54: noaaport channel updates 10 June, shall I be worried?

Hi Daryl & fellow LDMers,

That SCN most certainly raised my eyebrows when it came in.  As you clearly
do, I've got some questions about this too.

I'm going to inquire deeper into what this means, the implications, and
what users (not to mention us at the UPC) should do to adjust if anything.
I'll share what I learn when I hear back.

May we live in interesting times,
-Mike


*Mike Zuranski*
Data Engineer II
NSF Unidata Program Center
University Corporation for Atmospheric Research


On Wed, Jun 5, 2024 at 7:53 AM Stonie Cooper <cooper@xxxxxxxx> wrote:

> The unfortunate answer is it's unknown. Mike is on it as I'm in Iowa City
> at a NOAA CAP/RISA meeting this week.
>
> 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 Pawnee, The Omaha, and The Otoe.
>
> ---------- Forwarded message ---------
> From: Herzmann, Daryl E [AGRON] <akrherz@xxxxxxxxxxx>
> Date: Wed, Jun 5, 2024, 07:26
> Subject: [ldm-users] SCN 24-54: noaaport channel updates 10 June, shall I
> be worried?
> To: ldm-users@xxxxxxxxxxxxxxxx <ldm-users@xxxxxxxxxxxxxxxx>
>
>
> Howdy LDM Users/Unidata,
>
> The SCN below looks scary and impactful to the IDD with products changing
> feedtypes.  Can any of the fine folks here / Unidata put my mind at ease?
>
> thanks!
> daryl
>
> NOUS41 KWBC 042030 AAA
> PNSWSH
>
> Service Change Notice 24-54 Updated
> National Weather Service Headquarters Silver Spring MD
> 430 PM EDT Tue Jun 4 2024
>
> To:      Subscribers:
>          -NOAA Weather Wire Service (NWWS)
>          -Emergency Managers Weather Information Network (EMWIN)
>          -NOAAPort
>          Other NWS Partners, Users and Employees
>
> From:    David Michaud
>          Director, NWS Office of Central Processing
>
> Subject: Updated: Change to NOAAPort / Satellite Broadcast Network
> (SBN)
>          Channel Alignment, Effective June 10, 2024
>
> Updated to change the implementation date from on or about 1200
> Coordinated Universal Time (UTC) June 10, 2024, to on or about 1200
> Coordinated Universal Time (UTC) July 15, 2024, and to add
> information on
> a recommended configuration setting.
>
> Effective June 10, 2024, the NWS recommends that all users ensure
> their
> requests from NOAAPort / SBN utilize the feed type of ANY rather than
> specific feed types such as HDS and NGRID. The implementation date
> has
> been delayed to allow users time to make these changes. After this
> change
> patterns could be duplicated so users should cross-check and make
> sure
> there are no duplicates.
>
> An example of a request to change is for CONUS MOS products.
>
> Before:
>
> NGRID|IDS|DDPLUS ^(FOUS[1-589].) (....) (..)(..)(..)
>
> After:
>
> ANY   ^(FOUS[1-589].) (....) (..)(..)(..)
>
> >From the original SCN 24-54:
> The NWS has studied the existing NOAAPort/SBN/NWWS channel alignment,
> bandwidth usage, prioritization, and delay times. This study
> identified
> that reorganizing the data on the various channels will improve the
> timeliness of distributed products.
>
> The first of three changes to the existing NOAAPort/SBN/NWWS channels
> is
> to migrate all grib, grib2, and bufr formatted data from the NMC
> channel
> to the NMC2 channel.
>
> The following is a list of World Meteorological Organization (WMO)
> Headers
> that will move: (Channel: NMC | Priority: 0 | Bandwidth: 20 | Port:
> 1201 |
> PID: 101) to (Channel: NMC2 | Priority: 5 | Bandwidth: 30 | Port:
> 1203 |
> PID: 103):
>
> ^(AT....) ^(DT....) ^(ES....) ^(FT....) ^(GT....) ^(HH....)
> ^(HR....) ^(HT....) ^(HU....) ^(HV....) ^(IU....) ^(JS....)
> ^(JU....) ^(LA....) ^(LE....) ^(LH....) ^(LP....) ^(LR....)
> ^(LT....) ^(LU....) ^(LV....) ^(MA....) ^(ME....) ^(ME....)
> ^(MH....) ^(MP....) ^(MP....) ^(MR....) ^(OE....) ^(PE....)
> ^(RD....) ^(RE....) ^(RH....) ^(SL....) ^(SV....) ^(YA....)
> ^(YB....) ^(YC....) ^(YD....) ^(YE....) ^(YF....) ^(YG....)
> ^(YH....) ^(YI....) ^(YJ....) ^(YK....) ^(YL....) ^(YM....)
> ^(YN....) ^(YO....) ^(YP....) ^(YQ....) ^(YR....) ^(YS....)
> ^(YT....) ^(YU....) ^(YV....) ^(YW....) ^(YX....) ^(YY....)
> ^(YZ....) ^(ZA....) ^(ZB....) ^(ZC....) ^(ZD....) ^(ZE....)
> ^(ZF....) ^(ZG....) ^(ZH....) ^(ZO....) ^(ZP....) ^(ZQ....)
> ^(ZR....) ^(ZS....) ^(ZT....) ^(ZU....) ^(ZV....) ^(ZW....)
> ^(ZX....) ^(ZY....) ^(ZZ....)
>
> This data is expected to move on or about 1200 Coordinated Universal
> Time
> (UTC) July 15, 2024. If a Critical Weather Day has been issued, this
> change will be postponed until 1200 UTC on the next non-Critical
> Weather
> Day.
>
> No change is expected to the data feed at the receiver. If no issues
> are
> experienced, the configuration will remain in place. If any issues
> are
> identified, the changes will be evaluated, and a new implementation
> date
> will be determined.
>
> We encourage all NOAAPort/SBN/NWWS users to closely monitor this
> Service
> Change Notice (SCN) during the transition period for updated
> information.
> If you have any questions or concerns, please contact the focal
> points
> below:
>
> Paul Kirkwood
> NOAA/NWS Southern Region Headquarters
> Email: paul.kirkwood@xxxxxxxx
>
> Andy Just
> NOAA/NWS Office of Central Processing
> Email: andy.just@xxxxxxxx
>
> James Glenn
> NOAA/NWS Office of Central Processing
> Email: james.glenn@xxxxxxxx
>
> National Service Change Notices are online at:
>
> https://www.weather.gov/notification
> _______________________________________________
> NOTE: All exchanges posted to Unidata maintained email lists are
> recorded in the Unidata inquiry tracking system and made publicly
> available through the web.  Users who post to any of the lists we
> maintain are reminded to remove any personal information that they
> do not want to be made public.
>
>
> ldm-users mailing list
> ldm-users@xxxxxxxxxxxxxxxx
> For list information or to unsubscribe,  visit:
> https://www.unidata.ucar.edu/mailing_lists/
>
  • 2024 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the ldm-users archives: