Jump to content
GMS, SMS, and WMS User Forum


  • Content Count

  • Joined

  • Last visited

Everything posted by calberts

  1. Rob, I don’t believe SMS 12.3 has the capability of converting to raster, someone correct me if I’m mistaken. I do happen to know that functionality was added to 13.0. In 13.0 you first convert the mesh to a scatter set by right-clicking on it and converting to scatter and then you right click on the scatter set and convert it to a raster. You can set the desired resolution and it will save out a geotiff. If you haven’t done so already, you could evaluate SMS 13.0 with a free trial and check it out. Or I’d also suggest looking into renewing your maintenance since 13.0 comes with some other useful features like improved LiDAR processing. calberts
  2. Donald is right, you may have better luck with using the source arc redistribution for those bends in the channel. See the following wiki for more details: Source Arc Redistribution The problematic elements are likely the tight group of skewed elements I've circled in the image below: The other elements that are flagged could also be improved (and will be with source arc redistribution), but I wouldn't expect them to be the problem. -calberts
  3. Is this for a line or point type obstruction? In general, for both types of obstructions you can set the height by changing the Z value(s) associated with the line or point . The thickness attribute that is assigned to it then is measured vertically upwards from that elevation. Cody
  4. Thanks for sharing the .srhhydro file, I believe Aquaveo has fixed this issue in SMS 12.3. As a workaround in SMS 12.2 try the following: 1. Export the simulation (Just choose "Export SRH-2D" and not "Save, Export, and Launch SRH-2D") 2. Open the .srhhydro file in a text editor and modify the last 5 lines to match the following lines: LinkNodestrings 1 1 2LinkFlowType 1 CONSTANTLinkConstantFlow 1 70 ENLinkLagtimeMethod 1 SpecLinkSpecifiedLagtime 1 3600 3. Save the changes to the .srhhydro file in the text editor. 5. Launch the simulation (Just choose "Launch SRH-2D" and not "Save, Export, and Launch SRH-2D") With these changes SRH should be good to run. Let us know if it still has issues. -Cody
  5. Typically when SRHPre asks for “on screen input” it means that a required variable for the structure has not been provided. This usually means that something went wrong exporting the simulation and the variable was not written to the .srhhydro file or It was written in an incorrect format. Could you include a screenshot or copy of the text in the .srhhydro file? Also, what version of SMS are you using? -Cody
  6. JKM, As you are to the point of running the model and already have a mesh created, the scatter set won't have any influence on the model since the elevations from the scatter were a piece of the mesh building process. The main thing you would want to verify is that if the scatter set does have problems, those problems have not been transferred to the mesh. If you review your mesh and all looks good, then the -999 values for the WSEs likely are caused by something else. You could review the materials coverage to make sure you have materials polygons covering the entire extents of the mesh and that those polygons have a material type other than "unassigned" that have been assigned to them. Aside from the materials, the only other thing I can think of is that the model possibly needs to be ran for a longer duration of time? Let us know! -Cody
  7. calberts


    B. Horrocks, The .img file that comes with the .rrd file you downloaded is supported by WMS and can be loaded in. However, due to the size of the file you will run into a snag when converting the .img to a native land use grid that WMS can use for computations. If you can crop the raster down to your area of interest using an exterior GIS program, that would be necessary. This is assuming you want to use the NLCD 2011 data. If the land use in the area you are working in hasn't changed much since 2006, WMS can download a cropped subset of the NLCD 2006 data by using the web services. I'd recommend using the Get Data From Map button and selecting it from the list of web services that pop up. In the near future WMS 11.0 will be released to a beta version. In that version the same capability described for the NLCD 2006 data will apply to the NLCD 2011 data, which will make it much easier to use the 2011 data. -Cody
  8. Fahad, Currently, SMS only allows the specification of materials for TUFLOW as polygons. It is possible that there may be a way to manually modify in the input files after SMS has written them which will allow you to use a raster file. So you may want to post this question on the TUFLOW user forum as well and see what suggestions you get from them. https://www.tuflow.com/forum/ -Cody
  9. Isaac, If I'm not mistaken, that may just be another way to tell SRH that you want to use a restart file. I have never done it that way, but from the manual it appears that you want to do either "IREST=0" for no restart file or "IREST=1" to use a restart file. You would then have a file alongside the simulation .DAT file which matches the casename of the .DAT file but has an "_RST.dat" at the end of it. Below is a snippet from page 91 of the SRH Manual Either way it seems like this is just an alternate way to specify that you want to use a restart file. Let us know if it works. I still think that the restart file should have the sediment info included in it, so let us know if it does not appear to have such. -Cody
  10. I do work for Aquaveo. Thanks for letting me know.
  11. Thanks for checking that. SRH-2D will interpret the geometry in SI units if the horizontal projection unit is in meters. So what I believe is happening is that SRH is interpreting the ~330 ft mesh elevations as 330 meters and the TW values are much much higher than the 330 ft values in the HY8 table. I would recommend making your horizontal and vertical units consistent by using the "Reproject All" function to convert all your horizontal units to feet or all your vertical units to meters, whichever one fits the situation. After doing that you should be ok to run SRH and even raise your timestep back up. -Cody
  12. One thing I notice is that the reported Max TW in the error message is 108.21 and the culvert definition inverts are defined as ~330. This is roughly about the conversion of meters to feet. Is there a chance that your mesh projection and display projection are set to meters for the vertical unit?
  13. I am glad you are seeing better results. For best results, when creating your domain coverage you should create it within the areas you have elevation data (TIN or Raster). If there are areas where you slightly go outside of the TIN edge there is an option to "Extrapolate" elevations for areas outside of the elevation data using an IDW interpolation. That is found in the "Scatter Options" when you are assigning a scatter data set for the mesh generator polygons. Please keep in mind, that is an extrapolation of data and that if large portions of the domain coverage are outside of the TIN or areas of interest are outside of the TIN this will not be a good representation of those areas. You can view the number of elements by selecting "File | Get info" and then clicking on the "Mesh module" tab. I do not currently have any document to share on the time step. In the future there will be a guidance document available online that will have more information about selecting a time step. Typically most models use a time step between 1 and 5 seconds. There are cases where lower or even higher time steps may be used but you should always review the 2D results as well as any structure output data files (if applicable) to make sure everything is hydraulically stable. -Cody
  14. Isaac, Restart files should include information about sediment transport. If you are not seeing that behavior, let us know what version of SMS you are running SRH-2D with and we can perform some additional tests to ensure that everything is working in the current release of SRH-2D and SMS. -Cody
  15. Shahidul, Which version of SMS are you using? I ran the simulation with SMS 12.3 and it is giving results consistent with the input parameters. -Cody
  16. In addition to Donald's comment, an additional method would be to switch to the scatter module, and select Interpolate to Map. This will interpolate elevations from the active scatter set to the nodes and vertices of arcs in the active map coverage. -Cody
  17. Hi, It is hard to say what may be causing the issue you are describing. You might investigate why the boundaries are irregular, but I would not expect those to be the cause of all output values being zero. Could you also give us a screenshot of the model in plan view with your BC coverage displayed? One thing you may want to check is that your materials polygons all are set the way you want them, if a materials polygon is left as the default of "Unassigned" or if there are areas of the mesh which do not have materials polygons covering them, then those elements will be inactive for the run. -Cody
  18. Hi Phillip, For now in SMS 12.3 and previous versions, the ascending order of the IDs for the monitor lines will match the ascending order of the file name index values in the LNn.dat files. In the next major version release (SMS 13.0) the arc ID will match the file name index values, making it easier to correspond the two. -Cody
  19. You are right, the 1D overtopping as well as the computed 2D pressure flows would be for all flow traveling in the direction of the culvert flows. Your parking lot flow traveling perpendicular to the structure would not be represented how you would want it to be with a pressure flow structure. -Cody
  20. The elevations of the 2D elements should represent the elevation of the channel beneath the bridge deck. The parameters specified in the structure will define the deck low/high chord elevations. -Cody
  21. Phillip, 2D pressure flow areas are actually different than culverts by nature. They actually don't deactivate the elements between the structure faces but rather act as a ceiling through which water can pass under, all the while keeping the 2D computations continuous while adding pressure flow computations to the region. There is an optional 1D component to the 2D pressure flow structures for computing overtopping which uses weir equations. This 1D component will not deactivate elements through the structure. -Cody
  22. Hi Phillip, You are right, the elements between the culvert faces are disabled and act as a barrier to flow. Another option for you would be to instead use a "Link" type structure which would not disable elements between the faces of the structure. Within the Link setup parameters you can specify a rating curve as the inflow type. Outside of SMS, if you open the HY8 file within the HY8 program and then go to the crossing properties, there is an option to view the rating curve data if you supply the discharge and tailwater data to the crossing definition. This method can work well as long as you can reasonably represent the hydraulic conditions around the culvert with a simple rating curve. An example of where this method would not work well is if the hydraulic conditions were tidally controlled. -Cody
  23. Hi Shahidul, The full sediment transport capabilities were not fully supported in SMS until the release of SMS 12.2. To access that coverage type, you would need to be using SMS 12.2 or 12.3. https://www.xmswiki.com/wiki/SMS:What's_New_in_SMS_12.2#SRH-2D -Cody
  24. Shahidul, You can set the projection by selecting "Transverse Mercator" as the projection and then entering the projection information that you have listed (see below). The datum you have listed does not appear to be in the library list of datums. In that case, there could possibly be one in the library that is a close match to your datum or you could define your own datum by selecting "Add Datum" and setting the datum parameters. -Cody
  25. Hi, It definitely looks like there is a projection issue with one of the pieces of data. Whenever I have similar issues, the first step I take is to locate which of the two is actually in the correct location. The easiest way to do this is to load in a dynamic map to provide a reference for where things are located. To load in a dynamic map, select "Add online maps" from the "Web" menu and choose "World Imagery" or "World Street map". SMS will display a dynamic map that updates when you pan around and zoom into the display. After you have located which one is correct, double check the specified projection on the one that is wrong by right clicking on it and checking the object projection. If the object projection of the object in the incorrect location seems correct, then more investigation is needed from the source of that data. Sometimes there are conversion factors such as a shift or scaling that must be applied, speaking to the surveyor or person that generated the data can sometimes clear that up. If after investigating the source of the data doesn't resolve the issue, then a trial and error process of manually shifting the data by applying either scale factors or X and Y shifts will be required. Most projections parameter fields that you can adjust within the projection (see below). -Cody
  • Create New...