Storm Sewer & Flood Modeling
Welcome to the Innovyze Stormwater, Sewer, and Flood modeling feedback page.
18 results found
-
Use tracers for water on mesh elements
Our clients are more and more trying to figure out if damage to a property is caused by water from the public area (which is the responsibility of the client) or from private areas (which is not). When rainfall on mesh can pick up a tracer (eg. from existing objects like infiltration zones or roughness zones) we think we'll be able to better help our clients.
18 votes -
I want Infoworks' "Export maxima to GIS" to include the below parameters to assist scour protection design within 2D Zone
- For shear-stress-based design 1.1 Max Shear Stress (in N/m2 with at least 1 digit after the decimal point) 1.2 Hydraulic Slope at Max Shear Stress (in percent with at least 3 digits after the decimal point)
- For velocity-based design 2.1. Max SPEED2D (already available. Good job, devlopment team!) 2.2. Hydraulic slope at max SPEED2D (in percent with at least 3 digits after the decimal point)
2 votes -
Import “initial conditions 2D” CSV files in batches .
At the moment I can only import initial conditions 2D” CSV files one by one. It would be helpful if I could import a batch of files in one go, like with CSV rainfall files.
2 votes -
Add 2D result labels for ICM mesh elements
I would like to display the 2D results (depth, elevation, velocity) at each individual GRID cell using labels.
This is currently available in XPSWMM, so I would like the same functionality in InfoWorks ICM as I would rather not have to export the data to GIS.9 votes -
2D worst case analysis
I would like to be able to analyse a number of simulations in terms of the worst flood depth per 2D mesh element. An integrated tool (along the lines of the already existing worst case grid output) would avoid the need to mess around in external GIS.
20 votesThank you for this idea addition, it is something we have been considering and building out plans for, if there are more specifics in terms of the exact outputs/comparisons you would like to see, please feel free to add so we can ensure these are captured.
-
Add sub-grid sampling functionality to the ICM 2D engine
And sub-grid sampling visualizations, please :)
2 votes -
Consistent SHP Export Data Fields for 2D mesh elements in ICM
A simulation result can be exported to SHP files by right clicking the icon and choosing the Export menu. When the result is exported for a specific timestamp, some underlying data fields are not exported such as the elevation and area of a 2D element. When we need such data fields, the maximum state should be exported.
We wanted to investigate the ground levels of 2D meshes in my model, and were a bit confused to find the data was not included, as the export was done for the peak of a rainfall. Contacting the support team, we learned that…3 votes -
Show water levels at Bridge Linear Structures
We would like to see the water levels at the bridge linear structures as it is important for us to be able to see the water levels with respect to the bridge openings and decks.
6 votes -
Triangles browser
Small triangles can slow down 2D simulations significantly. Currently, after creating a 2D mesh, I export the 2D mesh to a GIS software to check how many triangles I have below certain size and where they are. This helps me address the problem of small triangles efficiently. it would be helpful to have a similar functionality in ICM (i.e. triangles browser).
17 votes -
As a user, I would like the computing time to be reported as clock time rather than CPU time in XPSWMM 2D
I just noticed this when trying to run a test on model speed. This is with the “CPU” Extreme option and 4 CPUs selected. The clock time is about 16 minutes, but the elapsed time is showing at 58 (close to 16x4). I think the ET is counting CPU time, and not clock time. While CPU time is interesting, I think it would be better to report clock time if you’re going to label it “Elapsed Time”.
Perhaps a separate “CPU Time” line would be appropriate when using multiple CPUs.
==============================================================
| XPSWMM/XPSTORM Simulation Date and Time Summary |
==============================================================
…
1 vote -
Collapsing walls identified in the log file
Can we have the status of base linear structures included in the log file? I have a large model where I have lots of these and I need to interrogate each one in turn. It would be much easier if the log file (or, better still, a grid view) showed the status of each wall.
4 votes -
Apply RTC / observed values to Sluice Linear Structures
At the moment we cannot move sluice linear structures in 2D. We're wanting to model a river entirely in 2D but the river is subject to a series of barrages that would require control. Therefore it would be essential to apply RTC and observed settings to the gates.
7 votes -
Merge more than two polygon in one go
Merging polygons representing for instance mesh zones can help reducing the number of triangles, particularly small ones, and reduce simulation time. The version of ICM I am using can only merge two polygons at the time. I currently do the polygon merge as part of my data pre-processing before importing the data into ICM as I can merge more than two polygons at the time. However, it would be useful to be able merge several polygons in one go in ICM.
5 votes -
Include groundlevel as attribute in export network 2D mesh elements
When you export a model to shape for example, only the element id is included. You have to run a simulation (for a second) and then exporting maximum reveales the element ground level. It saves time to add the mesh element level to the export. Although easy to add in GIS, the element area is also a handy attribute
5 votes -
As a user, I would like to have warnings about the landuse polygon size that will greatly slow down the performance in XPSWMM.
Large number of land use polygons can greatly slow down the performance of XPSWMM, it can take up to 10 min to open and save a model. Ideally this issue should be fixed. Before that happens, if XPSWMM can warn the user for the large size of the landuse polygons, and provide links to ways to simplify the polygons or move landuse out as a reference layer, that will save the users lots of time.
1 vote -
Create preset 2D inflow equation
Similar to inlet capacity, have the ability to create 2D inflow equations relative to inlet size and control depending on weir or orifice curves. This will allow the user to increase or change 2D inflow control easier and more standardized.
2 votes -
Loading bars for large 2d TIN results.
Vissible loading progress for loading large or TIN modelling results.
2 votes -
Enable TIN Reference in Scenarios (Enable/Disable)
All other layers in XPSTORM/XPSWMM are able to be deactivated for different scenarios.
If you could allow for the Topography tins to be activated and deactivated (like Fill Areas, Elevation Shapes etc), this will allow for multiple scenarios (i.e. pre- and post-development) and minimise the complexities of trying to model two identical scenarios on two seperate models.
1 vote
