Jump to content
GMS, SMS, and WMS User Forum

Chris Smemoe

WMS Development Team
  • Posts

  • Joined

  • Last visited

  • Days Won


Chris Smemoe last won the day on March 1 2011

Chris Smemoe had the most liked content!

1 Follower

About Chris Smemoe

Profile Information

  • Gender
  • Location
    Provo, UT

Recent Profile Visitors

21,082 profile views

Chris Smemoe's Achievements


Newbie (1/14)



  1. David, Sorry about the problems you're having. I haven't heard of this issue. If you are able to get a set of files to duplicate this problem and send your files and information to support@aquaveo.com, we could make sure any issues get fixed and get an update out. Chris
  2. I'd recommend making a rain gage coverage and add points to that coverage. In each point's attributes, you can assign the rain gage data to each location. You would normally assign a rainfall amount for a particular storm from the IDF curves along with some kind of rainfall distribution. All this information can be assigned in the point attributes in the rain gage coverage. If your rain gage coverage is defined and you have a watershed that you've delineated in WMS, WMS computes the gage weights for each sub-basin in your watershed when you compute the basin data. Chris
  3. Fsanti1 I think the solution cell water depth will correspond to the water surface elevation you specify in the overland boundary condition and this water depth will be applied in each of the GSSHA overland flow model time steps to adjacent cells. This option is useful for coastal storm surge or levee break modeling. I have not personally looked at the code to guarantee that the water depth at the cell is kept at that boundary condition throughout the simulation though. Also, to answer the second part of your question, I do not know how GSSHA interpolates between water surface elevation values. My suggestion is to experiment with GSSHA and try to determine what it does with your water surface elevation values and then you can interpolate the water surface elevation values yourself as needed. Chris
  4. Greeting Mr. Smemoe,

     Do you think you can help me with my question in the following topic:

    Thanks in advance

  5. Kevin, I recommend contacting Aquaveo tech support about this issue with the exact steps you're using to duplicate this problem. Chris
  6. Dan, Which version of WMS 11.0 are you using? Are you using the most recent update (Built around May 3rd)? To convert to a land use grid, WMS is looking for a raster with a single band of data that has a color palette. I don't think the values have to be 8-bit, but they usually are if there's a color palette. If you have a way to export a color palette from ArcGIS with your .tif file, WMS should recognize this as something that can be converted to a Land Use Grid. Chris
  7. AvilaY, Those 2 messages are normal if you have modified the WMS-computed basin boundaries. They show up because WMS follows the flow directions on your DEM to compute the maximum flow distance and the maximum basin length. If basin edges are encountered while following the flow directions, you get this error because the flow directions will usually intersect the basin boundary if you have modified the basin boundaries from the boundaries WMS-computed boundaries (WMS uses the original flow directions and accumulations to compute the boundary to begin with, so if you change the boundaries, you'll almost always get this error message). It's probably not a big issue for what you're doing since WMS should still be able to find an approximate flow distance and max basin length if you need those values for computing the Time of Concentration or another watershed parameter. You might want to keep an eye on these parameters that WMS computes though to see that the values look reasonable. Hope this helps, Chris
  8. The junction length is the length of the stream located downstream from the junction. It's measured from the junction to the next downstream outlet (junction) point. Hope this helps, Chris
  9. Thomas, EPA-SWMM support has not been dropped from WMS, but the tutorial is not available online for various reasons. You should be able to request the tutorial by contacting tech support directly or by going to the WMS tutorials page on xmswiki.com. WMS is useful for pulling data into WMS and converting the data to a schematic that can be used to export a SWMM model. It's also useful for running hydrology and linking hydrology results to a SWMM model as described in the tutorial. It does not have a full interface to EPA-SWMM (you can't enter all the SWMM time series information in WMS, for example) and SWMM cannot be run directly from WMS. You export an EPA-SWMM .inp file from WMS and then read this file into SWMM. Then you can finish setting up your model in SWMM. SWMM has an interface that's fairly easy to use once you have your basic model schematic set up. Let me know if I can help with anything else. Chris
  10. Sorry it's taken so long to answer this. The main channel length depends on the length of your stream in the watershed or sub-basin where the calculation is made. So if your stream arc is longer in this basin, your main channel length will be longer. It's the same with the 10/85 channel slope calculation. This calculation depends on your stream location and length. Since the 10/85 calculation depends on 2 points along your stream, this calculation may not be as accurate as something like the average stream slope. Hopefully that's helpful, let me know if I can help with anything else, Chris
  11. The WMS software developers are excited to announce that the beta version of WMS (11.0) is available for download! The final version will be available sometime in the next couple of weeks.  A detailed list of the new features available in WMS 11.0 is located on the following web site: https://www.xmswiki.com/wiki/WMS:What's_new_in_WMS_version_11.0 Enjoy! Chris
  12. I just noticed your response. There are a couple of things you can do to get a better result. One is to increase the number of cross sections in your model so you have more data points and get better interpolation when you do the floodplain delineation. The other thing you should always do is to add additional solution points by interpolating between the existing solution points along the river of interest and add additional solution points along each of the cross sections in your model.
  13. Yacob, Sorry it took so long to respond to this problem. The problem with Cleandam is that it does not always automatically fix all the "digital dams" in your elevation grid. However, cleandam does a good job of fixing most of the digital dams. Your easiest option is probably to fix what cleandam gave you by manually adjusting the elevations of the cell with the problem in WMS until the digital dam goes away. There is an ""official" gsshawiki.com help page that describes the process and problems with the cleandam program in WMS. The page is located here. I will mention that this page is a little outdated because it mentions that there are options to "tweak digital dams" and to "smooth grid (TOPAZ)" in the GSSHA menu. These menu options no longer exist. I should probably update the page to describe the process of using TOPAZ (or TauDEM) to smooth the grid if you desire to do this. It is a lengthy process that I won't describe here. If you do decide to run TOPAZ, I can provide the steps, but realize that the result might not necessarily be what you want as described on the gsshawiki.com help page linked above. Chris
  14. WMS is looking for something like the following lines in your .out file: RVR MILE MAX FLOW MAX ELEV MAX DEPTH TIME(HR) TIME(HR) TIME(HR) FLOOD FROM DAM (CFS) (FT-MSL) (FT) MAX DEPTH FLOOD DEFLOOD DEPTH(FT) ******** ******** ******** ******** ******** ******** ******** ******** .00 1214514. 5331.49 97.20 2.00 .00 .00 10.00 1.02 989023. 5331.49 109.32 2.07 .00 .00 10.00 2.57 952856. 5331.49 116.03 2.18 .00 .00 10.00 4.48 943327. 5299.28 125.07 2.23 .00 .00 10.00 8.83 933894. 4927.86 68.22 2.37 .37 5.44 10.00 10.35 924555. 4805.21 25.51 2.97 1.18 5.76 10.00 11.55 915310. 4736.06 20.70 3.00 1.25 5.76 10.00 12.24 906157. 4709.49 20.14 3.03 1.43 5.59 10.00 Your .out file has the following lines with a warning: RVR MILE MAX FLOW MAX ELEV MAX DEPTH TIME(HR) TIME(HR) TIME(HR) FLOOD FROM DAM (CFS) (FT-MSL) (FT) MAX DEPTH FLOOD DEFLOOD DEPTH(FT) ******** ******** ******** ******** ******** ******** ******** ******** CANNOT CONVERGE ON A TAILWATER DEPTH WHICH IS LESS THAN THE HEADWATER DEPTH EVEN WITH 90% SUBMERGENCE (Q= 1465.1 HW= 2.08 Y= 1.60 ) SUGGEST YOU INCREASE SLOPE OR MODIFIY CROSS SECTION .00 1440. 5479.86 2.06 2.00 .00 .00 10.00 16.91 78. 5173.31 2.68 69.72 .00 .00 10.00 You should be able to remove the 3 lines between the headers and the start of the first number in your .out file so you have the following text and it should read into WMS fine: RVR MILE MAX FLOW MAX ELEV MAX DEPTH TIME(HR) TIME(HR) TIME(HR) FLOOD FROM DAM (CFS) (FT-MSL) (FT) MAX DEPTH FLOOD DEFLOOD DEPTH(FT) ******** ******** ******** ******** ******** ******** ******** ******** .00 1440. 5479.86 2.06 2.00 .00 .00 10.00 16.91 78. 5173.31 2.68 69.72 .00 .00 10.00 I'd also recommend adding additional cross sections to your model so you have more computed flood depth values along your centerline. Adding additional cross sections might fix the warning in your .out file. Let me know if I can help with anything else. Chris
  15. I am not sure why you would be getting this message, though I can only guess. Make sure you have permissions to write to the directory where you're saving the TOPAZ output files. Also make sure the directory exists. If these are both true, there may be a problem with your WMS installation. You could try re-installing or repairing your installation. Let me know if you need anything else, Chris
  • Create New...