Jump to content
GMS, SMS, and WMS User Forum

Chris Smemoe

WMS Development Team
  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by Chris Smemoe

  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. Kevin, I recommend contacting Aquaveo tech support about this issue with the exact steps you're using to duplicate this problem. Chris
  5. 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
  6. 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
  7. 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
  8. 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
  9. 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
  10. 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
  11. 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.
  12. 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
  13. 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
  14. 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
  15. 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
  16. 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
  17. 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
  18. 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
  19. 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
  20. David, You can have multiple GSSHA coverages and multiple GSSHA models in your WMS project. I'd recommend duplicating your existing GSSHA model (just right-click on your GSSHA model). Then duplicate your GSSHA coverage and delete any depression polygons in this coverage. Then assign the GSSHA coverage with the deleted polygons to your model. You should be able to run cleandam with the coverage/model containing the deleted polygons and it should not include any depression cells in your cleandam run (all the cells should be filled). Let me know if you have any other problems. Chris
  21. Joel, Here's a message from the GSSHA developer, Chuck Downer: It's pretty hard to say why he is not getting any ET. If he is in perpetual event mode, there is going to be little or no ET because ET will not occur in a cell that has any rainfall in it. So if he has some period that has constant rain, then the ET is going to be close to zero, and I can see no reason why that is not correct. Also, if his soil moistures were very low for some reason, below wilting point, he would get no ET. Other than that, it's hard to say based on the input. He can capture the effects of a perched water table, more or less, by using the multi-layer G&A model, and can specify the layer depths and the vertical hydraulic conductivity of the layers. If he puts a low permeability layer in there, the water will perch above, it won't move laterally of course. From the sounds of it, he probably wants to do this. If he uses GAR his SOIL_LAYER_DEPTH should be less than the impermeable layer depth, the top layer depth is typically a calibration parameter, as is the soil layer depth. If you use MLGA, you don't have to worry with these. Hope this helps, Chris
  22. Joel, I answered a question in another post. The answer to this question is that it's hard to answer without seeing your model. You can make sure you have good starting values for all the evapotranspiration parameters in your model. I'd recommend the GSSHA course or contacting tech support with your model as I described in your other post. Let me know if you have any other questions. Chris
  23. Joel, I don't have an immediate answer to your question off the top of my head. I'd recommend contacting tech support to see if they can help you with your specific questions. Their contact information is here: https://www.aquaveo.com/technical-support If you could provide a copy of your model to tech support and explain the specific problem you're having, that would be best. With specific engineering-related questions, consulting is available at an additional charge. There are 2 good resources for answering GSSHA-specific questions. The first is the GSSHA wiki, located at https://gsshawiki.com Also notice on the GSSHA wiki web site that a training course is being offered next month in Alabama. This 2-day course is offered free of charge if there are still seats available. You would need to provide your own time, lodging, and transportation to the course. I think this is a great opportunity to discuss any problems you have with the GSSHA developers and to get to know them. Contact information for the course is on gsshawiki.com. This would be a good use of your time and you would get to know other people using GSSHA for their projects. Let me know if you have any other questions, Chris
  24. David, The .dep file just has water depth solution values for each of the cells for each output time step. I don't know that the file format is documented anywhere, but maybe I can try to track something down if you need me to. The important values you would use if you were reading this file are the number of cells in the model, which is in the "ND" card at the top of the file, the name of the dataset (NAME card), whether each cell is active/inactive (these values do not change for each time step), and the solution values for each cell (these values DO change for each time step). It's just a text file, so you can open the file in a text editor and look at it to see what I'm talking about. The active/inactive and the solution values are for each cell (based on the cell ID) and you cannot determine the actual location with just this file. The values are listed in the .dep file in the order of the cell ID's. If you have the location of the center of the upper left cell of your grid and you know the number of rows and columns in your grid, you can determine the location of the center of any other cell from the cell ID. The cells are numbered starting from the upper left corner of the grid. Let me know if you have any other questions. Chris
  25. David, I looked at the documentation for gages in WMS and I'm afraid it's not very helpful. There are 2 types of gages in WMS: Rain gages and monitoring gages. You can convert a shapefile to rain gages in a "Rain Gage" coverage but there's no way to directly convert a shapefile to monitoring gages. However, there is a monitoring gage file format that you can import into WMS in the Gages dialog. Here's a sample file: GAGE BEGGAG NAM Gage1 LOC 1.000000 1.000000 0.000000 DIR 0.000000 1.000000 0.000000 COL 0 0 255 BEGGAG NAM Gage2 LOC 10.000000 10.000000 0.000000 DIR 0.000000 1.000000 0.000000 COL 0 0 255 BEGGAG NAM Gage3 LOC 20.000000 20.000000 0.000000 DIR 0.000000 1.000000 0.000000 COL 0 0 255 The "BEGGAG" line tells WMS to create a new gage. The "NAM" line is the name of the gage and the "LOC" line is the X Y Z location of the gage. You could just export the XYZ points from a shapefile to a text file and modify the file to include the necessary lines to import as a gage file. The only thing you might want to change in this file (besides the location and name) is the "COL" card. This is the Red, Green, and Blue color for the gage. The "DIR" isn't really used in WMS. To import this file, just go to the 2D grid module and select Data | Gages from the menus. It's also accessible from the "Select Monitoring Gage" tool. Select import from the Gages dialog and read your file. You could also just create a bunch of new gages in the Gages dialog and copy/paste your XYZ values into the dialog spreadsheet. Let me know if I can help with anything else. Chris
  • Create New...