Skip to main content

2024 Upgrades and Plans for Future

This document contains notes on recent upgrades to RSMS as well as changes planned for the short term. We will use these notes to prepare a list of changes for a new SOW.

2024 Upgrades​

  • Upgraded to the latest version of SQL Server Express, (v16)
  • Upgraded to the latest version of Windows Server (2022 version 21H2).
  • Upgraded to the latest version of IIS (10).
  • Upgraded to a more recent version of .NET (6.0), but we need to upgrade again...
  • Various dependencies in the dotnet code, i.e. NuGet packages:
    • Should we list the most important NuGet packages that got upgraded?
  • Dell changes?
  • Make RSMS more robust, related to river mile flipping for Ohio River.

Planned Upgrades​

  • Upgrade to the current LTS for .NET and ASP.NET (from v4.6.2 to ".NET Core" 8.0).
  • Add HTTPS certificate and configure the server.
  • Upgrade VM:
    • Current version of SQL Server Express is 2014 - v12, which loses support in 2024.
    • Current version of SQL Server Management Studio is 12, which loses support in 2024.
    • Current version of Windows Server is 2008 R2 Datacenter, which lost support on Jan 14, 2020.
    • Current version of IIS is 7.5, which lost support on Jan 14, 2020.
    • All NuGet packages will also be updated to the latest supported versions.
  • Read from HDF files or Flows DB instead of ".O" files.

HECRAS Community Model Upgrade​

The effort for upgrading RSMS after the model update will be separate.

Possible changes that will be made with the new model

  • Add cross sections to existing river.
  • Remove cross sections from an existing river.
  • Add a river.
  • Remove a river.
  • Split the model.
  • What version of HEC_RAS will be used?

Important Information that will need to be figured out

  • River Miles corresponding to the cross section. Hopefully the cross sections will be named with the river miles.
  • Lat Long for each cross section. Hopefully we will get a new shape file.
  • Constructing the RMI table.
    • Make a note on how the RMI table needs to be constructed.
      • Start with the Mainstem. Mouth to source
      • Tributary Rivers in order they appear on Ohio River. Mouth to source
        • Start with the farthest cross section from the mainstem and go towards it.

What files and tables to be modified.

  • River Basin Database
    • RiverLatLong
    • RivermileIndex
    • RiversXref
    • RSMSRiver
  • RMI file will need to be generated.

How to handle Rivers. We should create a table in the Spills database.

  • River
  • Farthest River mile.
  • Date for historical rainfall to Start.
  • If a lot of the tributaries get longer a second Farthest River Mile. New vs old based on the date.

Some Examples for new Table.

  • If they type in a river mile that for a tributary that we do not have. We can through a warning and set it to the Farthest River Mile.
  • If we have a new river like Green River that is not currently in the model but will be in the new Model we will not have historical flow for it. We can set a warning for it at the creation of the spill.
Last updated on by Jacob