Re: [ldm-users] The end of NOAAport/SBN

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>I know Ryan said he is not interested in changing minds on the
      intent of NOAAPort, but I would just say as someone who was in the
      NWS field when all this started, NOAAPort was definitely always
      intended to serve both internal and external users of NOAA data. </p>
    <div class="moz-cite-prefix">On 9/3/2026 5:20 PM, Ryan May wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAC2L33ACOnMaYgcB9eXZuj2V2Un-TbRWTsUUwTfOa-LdfVpgQA@xxxxxxxxxxxxxx">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">Hi Mike,
        <div><br>
        </div>
        <div>I would counter with this sentence from the NOAAPORT page
          on <a href="http://weather.gov"; moz-do-not-send="true">weather.gov</a>
          (<a href="https://www.weather.gov/noaaport/";
            moz-do-not-send="true" 
class="moz-txt-link-freetext">https://www.weather.gov/noaaport/</a>):</div>
        <div><br>
        </div>
        <div>"The Advanced Weather Interactive Processing System (AWIPS)
          Satellite Broadcast Network (SBN) system provides a one-way
          broadcast of NOAA environmental data and information in
          near-real time to NOAA and <b>external users</b>." (emphasis
          mine)</div>
        <div><br>
        </div>
        <div>I'd also cite the numerous public Service Change Notices
          regarding NOAAPORT over the years. That said, we may
          fundamentally disagree and that's fine. I'm not interested in
          changing minds on that. </div>
        <div><br>
        </div>
        <div>What really matters to me is what happens over the next
          year. I think there is an opportunity to build out a
          terrestrial version of NOAAPORT akin to previous projects like
          CRAFT and CONDUIT; to me it's the current tight timeline that
          makes things...tense. I look forward to Unidata working with a
          variety of partners to ensure our community is not adversely
          affected by these changes and continues to readily access the
          incredibly valuable data that NOAA creates and disseminates.</div>
        <div><br>
        </div>
        <div>Ryan</div>
        <div><br>
        </div>
      </div>
      <br>
      <div class="gmail_quote gmail_quote_container">
        <div dir="ltr" class="gmail_attr">On Thu, Sep 3, 2026 at 3:11 PM
          Mike Zuranski &lt;<a href="mailto:mike@xxxxxxxxxxxxxxxxxxx";
            moz-do-not-send="true" 
class="moz-txt-link-freetext">mike@xxxxxxxxxxxxxxxxxxx</a>&gt;
          wrote:<br>
        </div>
        <blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid 
rgb(204,204,204);padding-left:1ex">
          <div dir="ltr">
            <div dir="ltr">
              <div>Hi Ryan,</div>
              <br>
              <div class="gmail_quote">
                <div dir="ltr" class="gmail_attr">On Thu, Sep 3, 2026 at
                  3:33 PM Ryan May &lt;<a href="mailto:rmay@xxxxxxxx";
                    target="_blank" moz-do-not-send="true"
                    class="moz-txt-link-freetext">rmay@xxxxxxxx</a>&gt;
                  wrote:<br>
                </div>
                <blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid 
rgb(204,204,204);padding-left:1ex">
                  <div dir="ltr">
                    <div dir="ltr">
                      <div>...it is very unsettling due to the lack of
                        clarity about how the NWS intends to replace the
                        open, realtime data distribution afforded by
                        NOAAPORT. </div>
                    </div>
                  </div>
                </blockquote>
                <div><br>
                </div>
                <div>Bare with me as there is a modest amount of
                  hand-waving coming up... </div>
                <div><br>
                </div>
                <div>I see this sentiment come up here and there, and
                  say what you want about lack of clarity with
                  actionable statements, you'll get no argument from me
                  that those could improve.  But what I think people are
                  missing is NOAAPort was never truly designed to serve
                  anyone outside of NOAA.  It is a service by NOAA, for
                  NOAA, that we were lucky enough to be able to tap into
                  because it was clear-air transmission.  But "luck" is
                  the wrong word...  The work Unidata and other parties
                  laid out decades ago and have maintained since was to
                  bridge that service for Academia and others so not
                  everyone had to get a giant dish in their yards... but
                  technically that's all anyone would need for NOAAPort
                  is the right kind of ear; that is the key element that
                  is changing.  NOAAPort was always a private network,
                  one technically available to all others but barred for
                  most.</div>
                <div><br>
                </div>
                <div>AWIPS is moving to the cloud, the data is already
                  there and with far superior internet now compared to
                  the '90s NOAA no longer needs that data feed to be in
                  the clear-air for themselves.  Cutting partner access
                  to data feeds was never intended nor desired, just a
                  result of no longer being transmitted in the clear. 
                  Now while NOAA has maintained/improved the SBN tech
                  for their own offices &amp; needs over the years,
                  there was never any obligation for NOAA to make its
                  replacement clear-air and available to anyone with
                  only the right hardware.  So now we can't simply
                  listen in like we could before, but it's still a
                  private network just with hard access restrictions due
                  to being on a public internet.  </div>
                <div><br>
                </div>
                <div>The way I personally read the big picture here is
                  Unidata had a seat at the head of the table when the
                  SBN/NOAAPort paradigm was established; it took a lot
                  of effort, conversations, collaborations but the
                  result was a widely available robust network of data
                  coming from a NOAA feed, through the bridges that
                  Unidata has made and maintains, out to academia and
                  beyond.  Now that NOAA will fully replace their
                  previous network with one of a different design those
                  bridges will need to be rebuilt.  But it was never an
                  obligation for NOAA to maintain those bridges to our
                  communities, that is traditionally where Unidata came
                  in.  </div>
                <div><br>
                </div>
                <div><br>
                </div>
                <div>All of that is to say the following:  I don't
                  believe the NWS intends to replace this real-time push
                  network that we have gotten used to beyond their own
                  needs.  It was never really open in the first place,
                  and it is Unidata's bridges and on-ramps that made it
                  available to us at all.  It will be up to us to build
                  and design new bridges, new on-ramps and new workflows
                  for ourselves... with NWS/NOAA's help of course.  But
                  waiting will be a death sentence.</div>
                <div><br>
                </div>
                <div> </div>
                <blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid 
rgb(204,204,204);padding-left:1ex">
                  <div dir="ltr">
                    <div dir="ltr">
                      <div>This will certainly be discussed during
                        Unidata's Community Advisory Committee (CAC)
                        meeting next week.  We're also happy to
                        partner with others as we all try to smoothly
                        migrate to a post-NOAAPORT world.</div>
                    </div>
                  </div>
                </blockquote>
                <div><br>
                </div>
                <div>I would like to request if you could get a
                  representative from NODD to join the CAC meetings
                  moving forward.  I know it's likely too short notice
                  for that this fall, but between more and more data
                  sets moving to under their control, and other
                  opportunities that could come from their inclusion
                  here, I think it would be very helpful if that's
                  possible.</div>
                <div> </div>
                <div>Best,</div>
                <div>-Mike</div>
                <div><br>
                </div>
                <div><br>
                </div>
                <blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid 
rgb(204,204,204);padding-left:1ex">
                  <div dir="ltr">
                    <div dir="ltr">
                      <div>Cheers,</div>
                      <div><br>
                      </div>
                      <div>Ryan</div>
                    </div>
                    <div><br>
                    </div>
                    <div>-------</div>
                    <div>Dr. Ryan May<br>
                    </div>
                    <div>Deputy Director</div>
                    <div>NSF Unidata</div>
                    <div>Boulder, CO</div>
                    <div><br>
                    </div>
                    <div class="gmail_quote">
                      <div dir="ltr" class="gmail_attr">On Tue, Sep 1,
                        2026 at 3:20 PM Sebenste, Gilbert &lt;<a
                          href="mailto:sebensteg@xxxxxxx";
                          target="_blank" moz-do-not-send="true"
                          
class="moz-txt-link-freetext">sebensteg@xxxxxxx</a>&gt;
                        wrote:<br>
                      </div>
                      <blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid 
rgb(204,204,204);padding-left:1ex">
                        <div>
                          <div lang="EN-US">
                            <div>
                              <p class="MsoNormal">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 <a
                                  href="http://weather.cod.edu";
                                  target="_blank" 
moz-do-not-send="true">weather.cod.edu</a>
                                website? How will it affect all of you?<br>
                                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?<br>
                                <br>
                                I have so many questions….<br>
                                <br>
                                NOUS41 KWBC 011655 PNSWSH<br>
                                <br>
                                Public Information Statement 26-63 <br>
                                National Weather Service Headquarters
                                Silver Spring MD <br>
                                1255 PM EDT Tue Sep 1 2026 <br>
                                To: <br>
                                <br>
                                From:     <br>
                                <br>
                                Subscribers: -NOAA Weather Wire Service
                                -Emergency Managers Weather Information
                                Network -NOAAPort Other NWS Partners and
                                Employees
                                <br>
                                <br>
                                George Jungbluth, Director  Mission,
                                Systems and Technology <br>
                                <br>
                                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.
                                <br>
                                <br>
                                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. 
                                <br>
                                <br>
                                NOAAPORT users are encouraged to provide
                                feedback via this feedback form <a
href="https://www.surveymonkey.com/r/NOAAPortSBN2026"; target="_blank"
                                  moz-do-not-send="true"
                                  
class="moz-txt-link-freetext">https://www.surveymonkey.com/r/NOAAPortSBN2026</a>
 
                                by September 21, 2026. While the
                                feedback form is preferred, users can
                                also send comments and questions to: <a
                                  href="mailto:nws.webfeedback@xxxxxxxx";
                                  target="_blank" moz-do-not-send="true"
                                  
class="moz-txt-link-freetext">nws.webfeedback@xxxxxxxx</a> 
                                <br>
                                <br>
                                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: <br>
                                <br>
                                <a
href="https://www.weather.gov/notification/"; target="_blank"
                                  moz-do-not-send="true"
                                  
class="moz-txt-link-freetext">https://www.weather.gov/notification/</a> 
                                <br>
                                <br>
                                NNNN</p>
                              <p class="MsoNormal"> </p>
                              <p class="MsoNormal"><span
                                  style="font-size:11pt">Gilbert
                                  Sebenste</span></p>
                              <p class="MsoNormal"><span
                                  style="font-size:11pt">Meteorology
                                  Support Analyst<br>
                                  <br>
                                </span></p>
                              <p class="MsoNormal"><span
                                  style="font-size:11pt"><img
                                    width="358" height="61"
style="width: 3.7291in; height: 0.6354in;"
id="m_-6584419502259494778m_-7251463896405182709m_2332311447329552464m_-143203142267129826Picture_x0020_1"
src="cid:part1.FhriIa6f.Qa6LEV0W@balancedweather.com" 
class=""><span></span></span></p>
                              <p class="MsoNormal"> </p>
                            </div>
                          </div>
_________________________________________________________<br>
                          NOTE: All exchanges posted to NSF Unidata
                          maintained email lists are<br>
                          made publicly available through the web. Users
                          who post to any of the<br>
                          lists we maintain are reminded to remove any
                          personal information that<br>
                          they do not want to be made public.<br>
                          <br>
                          NSF Unidata ldm-users Mailing List<br>
                          (<a href="mailto:ldm-users@xxxxxxxxxxxxxxxx";
                            target="_blank" moz-do-not-send="true"
                            
class="moz-txt-link-freetext">ldm-users@xxxxxxxxxxxxxxxx</a>)<br>
                          For list information, to unsubscribe, or
                          change your membership options,<br>
                          visit: <a
href="https://mailinglists.unidata.ucar.edu/listinfo/ldm-users/";
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true"
                            
class="moz-txt-link-freetext">https://mailinglists.unidata.ucar.edu/listinfo/ldm-users/</a><br>
                        </div>
                      </blockquote>
                    </div>
                    <div><br>
                    </div>
                  </div>
_________________________________________________________<br>
                  NOTE: All exchanges posted to NSF Unidata maintained
                  email lists are<br>
                  made publicly available through the web. Users who
                  post to any of the<br>
                  lists we maintain are reminded to remove any personal
                  information that<br>
                  they do not want to be made public.<br>
                  <br>
                  NSF Unidata ldm-users Mailing List<br>
                  (<a href="mailto:ldm-users@xxxxxxxxxxxxxxxx";
                    target="_blank" moz-do-not-send="true"
                    
class="moz-txt-link-freetext">ldm-users@xxxxxxxxxxxxxxxx</a>)<br>
                  For list information, to unsubscribe, or change your
                  membership options,<br>
                  visit: <a
href="https://mailinglists.unidata.ucar.edu/listinfo/ldm-users/";
                    rel="noreferrer" target="_blank"
                    moz-do-not-send="true" 
class="moz-txt-link-freetext">https://mailinglists.unidata.ucar.edu/listinfo/ldm-users/</a><br>
                </blockquote>
              </div>
            </div>
          </div>
        </blockquote>
      </div>
      <br>
      <fieldset class="moz-mime-attachment-header"></fieldset>
      <pre wrap="" 
class="moz-quote-pre">_________________________________________________________
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
(<a class="moz-txt-link-abbreviated" 
href="mailto:ldm-users@xxxxxxxxxxxxxxxx";>ldm-users@xxxxxxxxxxxxxxxx</a>)
For list information, to unsubscribe, or change your membership options,
visit: <a class="moz-txt-link-freetext" 
href="https://mailinglists.unidata.ucar.edu/listinfo/ldm-users/";>https://mailinglists.unidata.ucar.edu/listinfo/ldm-users/</a>
</pre>
    </blockquote>
  </body>
</html>

PNG image