>
> We've known this for a while, that sometime around that date the Ratheon
> contract ends and likely so would NOAAPort. This is more of a reminder
> than anything else, but certainly a stark reminder that time is running out.
I think this official status is important, and should be discussed without
dismissal as "we've known," because it is very likely that some downstream
NOAAPort consumers don't actually know.
After that, turns out someone made a python package to parse that feed in
> real-time:
> https://github.com/bradsjm/nwws-oi-receiver
>
An archived repository at that. NWWS-OI via fiber has always been slower
and more disorganized than NOAAPort could ever be. That said, it currently
has the alerts until the NWS alerts actually start reaching WIS2 like our
EU counterparts.
I've started a test to determine latency deltas, missing products (+
additional products), and what a "NOAAPort" LDM feed might look like coming
from fiber. I'll have more information tomorrow after enough log data has
been collected and processed. My hope is that the latency isn't egregious
and that these products can be handled via `pqinsert` until which time
everyone has made their adjustments.
On Tue, Sep 1, 2026 at 3:50 PM Mike Zuranski <mike@xxxxxxxxxxxxxxxxxxx>
wrote:
> Hi Gilbert and all,
>
> We've known this for a while, that sometime around that date the Ratheon
> contract ends and likely so would NOAAPort. This is more of a reminder
> than anything else, but certainly a stark reminder that time is running out.
>
> To hopefully help answer some of your questions, take note of this subtle
> detail in that message:
>
> > The internet-based NWWS Open Interface (NWWS-OI) will continue to
> operate.
> That's right, there is a free NWWS push service online, and it will
> persist after NOAAPort goes dark. Here's how you register for an account:
> https://www.weather.gov/nwws/nwws_oi_request
>
> I was approved in under an hour, even during a CWD, but your mileage may
> vary.
>
> After that, turns out someone made a python package to parse that feed in
> real-time:
> https://github.com/bradsjm/nwws-oi-receiver
>
> I've been playing with this all afternoon, and while it doesn't replace
> the whole SBN of course it IS a free push service for critical text and WWA
> data. Even CAP messages which, if you haven't heard this one is going to
> officially replace VTEC soon enough as well. So here's my new data source
> for all that!
>
>
> Realistically though, this is going to be a rough ride for many. I really
> hope Unidata is cooking something up to solve this for our community at the
> very least, and I'm sure they're talking about this internally right now
> too. In a month or so are their governing committee meetings and fingers
> crossed we'll hear more actionable information from them soon after. They
> know how critical this is. In the meantime all I can say is hope for the
> best and plan for the worst; find alternate data sources, pipe lines or
> even workflows. We're all going to have to adapt in different ways
> somehow.
>
> -Mike
>
> On Tue, Sep 1, 2026 at 5:20 PM Sebenste, Gilbert <sebensteg@xxxxxxx>
> wrote:
>
>> If you haven’t heard, now you know. It says we are to wait for how the
>> information will be disseminated in the future. But what will that look
>> like? How will that impact me and our weather.cod.edu website? How will
>> it affect all of you?
>> How long will we have a parallel test to make sure that we can get the
>> data we need and process it locally? How can I plan when I literally do not
>> know what to plan for?
>>
>> I have so many questions….
>>
>> NOUS41 KWBC 011655 PNSWSH
>>
>> Public Information Statement 26-63
>> National Weather Service Headquarters Silver Spring MD
>> 1255 PM EDT Tue Sep 1 2026
>> To:
>>
>> From:
>>
>> Subscribers: -NOAA Weather Wire Service -Emergency Managers Weather
>> Information Network -NOAAPort Other NWS Partners and Employees
>>
>> George Jungbluth, Director Mission, Systems and Technology
>>
>> Subject: Soliciting initial comments, through September 21, 2026, on
>> planned retirement of the Satellite Broadcast Network (SBN)/NOAAPort and
>> NOAA Weather Wire Service (NWWS) Satellite as early as August 31, 2027.
>>
>> The NWS is modernizing its infrastructure and dissemination services by
>> transitioning to cloud-based services. This initiative will enhance
>> operational efficiency, increase reliability, and provide scalability for
>> future growth. As part of this modernization, the NWS will retire the
>> Satellite Broadcast Network (SBN), commonly referred to as NOAAPort.
>> Retirement of the SBN will also terminate the satellite-based NOAA Weather
>> Wire Service (NWWS), which uses SBN channel 201 to deliver data. The
>> internet-based NWWS Open Interface (NWWS-OI) will continue to operate. We
>> are assembling information about alternative data sources and will provide
>> it as soon as possible.
>>
>> NOAAPORT users are encouraged to provide feedback via this feedback form
>> https://www.surveymonkey.com/r/NOAAPortSBN2026 by September 21, 2026.
>> While the feedback form is preferred, users can also send comments and
>> questions to: nws.webfeedback@xxxxxxxx
>>
>> Stakeholder feedback will be used to help NWS plan the follow-on
>> dissemination systems to NOAAPort to ensure continuity of data and services
>> to users. The NWS will send an updated statement once the feedback is
>> processed and we have additional information to share. National Public
>> Information Statements are online at:
>>
>> https://www.weather.gov/notification/
>>
>> NNNN
>>
>>
>>
>> Gilbert Sebenste
>>
>> Meteorology Support Analyst
>>
>>
>> _________________________________________________________
>> NOTE: All exchanges posted to NSF Unidata maintained email lists are
>> 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.
>>
>> NSF Unidata ldm-users Mailing List
>> (ldm-users@xxxxxxxxxxxxxxxx)
>> For list information, to unsubscribe, or change your membership options,
>> visit: https://mailinglists.unidata.ucar.edu/listinfo/ldm-users/
>>
> _________________________________________________________
> NOTE: All exchanges posted to NSF Unidata maintained email lists are
> 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.
>
> NSF Unidata noaaport Mailing List
> (noaaport@xxxxxxxxxxxxxxxx)
> For list information, to unsubscribe, or change your membership options,
> visit: https://mailinglists.unidata.ucar.edu/listinfo/noaaport/
>
