Jump to content
GMS, SMS, and WMS User Forum

Chris Smemoe

WMS Development Team
  • Content Count

  • Joined

  • Last visited

  • Days Won


Chris Smemoe last won the day on March 1 2011

Chris Smemoe had the most liked content!

Community Reputation

1 Neutral


About Chris Smemoe

  • Rank
    WMS Development Team Leader

Profile Information

  • Gender
  • Location
    Provo, UT

Recent Profile Visitors

20,105 profile views
  1. 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
  2. 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
  3. 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
  4. 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
  5. 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
  6. 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
  7. 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.
  8. 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
  9. 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
  10. 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
  11. Conrad, I think you can do what you need using the culvert option in GSSHA. I've never tried to model what you are doing using the GSSHA storm drain coverage/pipes with a GSSHA coverage and stream arcs. You may be able to get something working, but I'm not sure what would happen with the multiple stream networks you would have in the GSSHA coverage. Hope this helps somehow, Chris
  12. Chenxi, The problem is probably related to a conversion problem between meters and feet. It sounds like your data is being interpreted as meters and then being converted to feet inside of WMS for some reason. I'm not sure what the cause is, but it could be an issue with the projection (.prj) file associated with your ascii grid file. I'd recommend converting everything to the same XYZ units and making sure you display projection has vertical units of meters as well. Let me know if you have other questions. Chris
  13. Sepideh, There are a couple of commands that might help you remove triangles that are not needed. One is the filter command. This command removes vertices on your TIN based on a filtering angle based on normal vectors to adjacent triangles to a vertex. This command can be accessed by right-clicking on the TIN and selecting Filter. You enter a filtering angle for this command. The documentation for this command is located here. The other command that might help with your TIN is the option to select and delete extra triangles on the edges of your TIN. To select triangles on the edges of your TIN, select the "Select Triangles" tool and hold down the CTRL key while dragging a line. Any triangle that intersects that line will be selected. This is useful for selecting and deleting triangles you don't want to include in your triangulation, such as those triangles outside the boundary of your raster data. Let me know if you need anything else, Chris
  14. David, That's a good question, and I don't fully understand the answer right now. I do know that it is only used for tile drains and doesn't apply if you're modeling normal underground drain pipes (storm sewers). I talked to the original programmer (Nawa) about it and understood the answer at one point, but the complete answer has left my mind. I asked Chuck Downer, the writer of GSSHA about it and here's what he says: "It has to do with the assumed shape of the curve for the water surface flowing into the pipes, assuming you are doing drains. It doesn't actually add pipes. It comes from the two pipe drain models that in GSSHA, Cooke and DrainMod. Those are computations for the pipes only. Those methods are described in that report. Since GSSHA is integrated the ground water surface is being computed, so I guess you don't really need this in GSSHA but we'd have to re-derive a formula. These are standard formulas. I don't know how sensitive the model is to the parameter. It might not matter a lot. I don't think you can put zero. I'd say if there is some pipe spacing in the fields just use that. Typically there is. Otherwise, probably make it on the larger side." I found a Technical Release paper describing this "L" parameter in some detail here: https://www.researchgate.net/publication/268076111_Modeling_Subsurface_Storm_and_Tile_Drain_Systems_in_GSSHA_with_SUPERLINK (This may be the same paper you were referring to above) So my understanding is that you would put your pipes in the GSSHA Storm Drain coverage where they actually exist and then enter an approximate spacing of the pipes in this "Drain spacing" field. Chris
  15. Chenxi, You need polygons in your branch coverage (as well as your segment coverage), so you need to get the build polygons command working before you can map segments to branches. Try cleaning all the arcs in your branch coverage (Feature Objects | Clean) before building polygons and see if that fixes your problem. Also make sure you don't have any duplicate arcs by dragging a box around your entire branch coverage and deleting any arcs that are not needed to define the boundary of the water body. If these steps don't fix the problem, I'd recommend sending your files to the Aquaveo tech support team if possible and let them have a look at the issue and see if they can figure out the problem. Let me know if you have any additional questions. Chris
  • Create New...