Welcome

Welcome to the RTMA/URMA VLab community!

The purpose of this community is to facilitate feedback and discussion on the RTMA/URMA system. 

Meeting notes are available under the Google Drive Folder linked above.

To learn more about our next upgrade, see the asset publication below.

Use the System Overview to learn more about the system in general.

Use the forum to ask questions about the system and join the discussion with other users and the development team. 

Note that there are two forums: one for precipitation issues and one for all other variables.

You can post to the precip issues forum by sending an email to qpe.rtma.urma.feedback.vlab@noaa.gov.  For all other issues, you can post by sending an email to rtma.feedback.vlab@noaa.gov.  Please note that you must have a user account to post to the forum.  If you do not have an account, please contact matthew.t.morris@noaa.gov.

We recently added the ability for NWS Regional or WFO personnel to request that stations be removed from the analysis.  To access this, click on the "Station Reject Lists and Requests" tab.

There has been recent interest in knowing exact station locations, especially those of METAR sites.  Our METAR information table is under the "METAR Location Info" tab.

Users may also be interested in the National Blend of Models VLab community.

We appreciate any feedback on how this page or community could be improved.  You can submit such feedback via the above email handle or forum.

 

What's New

December 2017 Implementation Summary

Document

Overview of upgrade scheduled for December 2017. Note that this was originally scheduled for October 2017, but has been pushed back due to technical issues.

Forums

Back

RTMA/URMA Terrain Gradient Issue in Temperature Analysis along Wasatch Front / Great Salt Lake

DC
David Church, modified 6 Days ago.

RTMA/URMA Terrain Gradient Issue in Temperature Analysis along Wasatch Front / Great Salt Lake

Youngling Posts: 10 Join Date: 1/8/14 Recent Posts

Lately we've noticed some higher temperature forecasts from the NBM along the benches (transitions between the mountains and valleys), than in the valley floors. I was able to trace this back to the RTMA and URMA analysis which is impacting the bias correction in the NBM. This also seems to happen at some pixels along the boundary of the Great Salt Lake lake shore as well. The issue is fairly ubiquitous at these transition zones in elevation, and does not appear to be limited to any specific observation site issues. The other odd thing is that I actually can't explain how the RMTA and URMA are arriving at the final analysis values. Using the KML files available to see how the obs are impacting the RTMA analysis, the final analysis values for the offending pixels in the KML file are actually reasonable values, but they don't actually match what I'm seeing the gridded RTMA and URMA. Furthermore, it appears the RTMA is too warm at these locations, but the URMA is even warmer at these locations, like the error magnifies between the RTMA and URMA. I've attached some examples are specific points, but the issue is far more widespread than just these pixels. The issue also shows up any day, and seem independent of how warm/cool the day is, we just happened to notice this on the warmer days as this has downstream impacts to the NBM and thus HeatRisk forecasts as well.

MM
Matthew Morris, modified 5 Days ago.

RE: RTMA/URMA Terrain Gradient Issue in Temperature Analysis along Wasatch Front / Great Salt Lake

Youngling Posts: 170 Join Date: 12/6/17 Recent Posts
Hi David,

Thanks for sharing this case with us.  We are looking into it and will follow-up once we know more, likely early next week.

Matt

On Tue, Jun 24, 2025 at 3:21 PM VLab Notifications <VLab.Notifications@noaa.gov> wrote:

Lately we've noticed some higher temperature forecasts from the NBM along the benches (transitions between the mountains and valleys), than in the valley floors. I was able to trace this back to the RTMA and URMA analysis which is impacting the bias correction in the NBM. This also seems to happen at some pixels along the boundary of the Great Salt Lake lake shore as well. The issue is fairly ubiquitous at these transition zones in elevation, and does not appear to be limited to any specific observation site issues. The other odd thing is that I actually can't explain how the RMTA and URMA are arriving at the final analysis values. Using the KML files available to see how the obs are impacting the RTMA analysis, the final analysis values for the offending pixels in the KML file are actually reasonable values, but they don't actually match what I'm seeing the gridded RTMA and URMA. Furthermore, it appears the RTMA is too warm at these locations, but the URMA is even warmer at these locations, like the error magnifies between the RTMA and URMA. I've attached some examples are specific points, but the issue is far more widespread than just these pixels. The issue also shows up any day, and seem independent of how warm/cool the day is, we just happened to notice this on the warmer days as this has downstream impacts to the NBM and thus HeatRisk forecasts as well.


--
David Church RTMA/URMA Discussion Group Virtual Lab Forum https://vlab.noaa.gov/web/715073/discussions-forums-/-/message_boards/view_message/45549960VLab.Notifications@noaa.gov


--
Matthew Morris
SAIC at NOAA/NWS/NCEP/EMC
5830 University Research Ct., Rm. 2038
College Park, MD 20740
301-683-3758

Bookmarks

Bookmarks
  • 2011 RTMA Paper (Weather and Forecasting)

    The most recent peer-reviewed paper on the RTMA. Published in Weather and Forecasting in 2011.
    7 Visits
  • Public RTMA/URMA Viewer

    Another viewer of the current RTMA/URMA, with an archive going back 24 hours. This version is open to the public, but does not contain information about the (many) restricted obs used.
    54 Visits
  • RAP downscaling conference preprint (23rd IIPS)

    This link is to a presentation from the (then) RUC group on how the downscaling process works. Although we now use the RAP, HRRR, and NAM, the logic of the downscaling code is mostly unchanged from this point.
    2 Visits