Storm Sewer & Flood Modeling
Welcome to the Innovyze Stormwater, Sewer, and Flood modeling feedback page.
370 results found
-
Merge pond and storage nodes and increase their functionality
Pond nodes:
- allow variable infiltration at different levels (up to 3 different rates)
- allow variable perimeter with level i.e. plan area through which side infiltration can occurs can vary
- no porosity functionStorage nodes:
- 1 porosity value (which only works below ground, above ground it is assumed to be 100%)
- fixed perimeter for infiltration i.e. assumes cylindrical shape for infiltration (despite the plan area changing with level)
- fixed infiltration rate (no change with height)It is not possible to model both porosity and a change in infiltration with height.
I propose that pond and…
9 votes -
Correct calculation of volume within storage node when using porosity
Currently when a porosity value is applied to a storage node, the porosity is only applied for storage array entries which are below ground level. Storage array entries above ground level are assumed to have a porosity of 100%. Between the highest storage array level value below ground and the lowest storage array level value above ground the porosity is assumed to increase linearly between the value you applied and 100%. i.e. the storage is assumed to be conical.
This should be corrected. The porosity value applied should be applied to the whole storage array both above and below ground.…5 votesCould you provide a practical example of porosity above ground?
-
Allow the user to choose the flood type of pond or storage nodes
Allow the user to choose the flood type of pond or storage nodes from a drop down as is the case for manholes. As opposed to the current state where the flood type depends on the relationship between the highest level entry in the storage array and the ground level of the node.
From help file: "Storage nodes or ponds can flood. If the highest level entry is below ground level, the pond is considered to have a roof at that level and is therefore sealed. If the highest level entry is equal to the ground level then any water…
7 votes -
Drain to 2D line source from subcatchment
The current function allows rainfall runoff to be given to a node, link, multiple links and 2D point source, but not to 2D line source. We are modelling rivers with 2D meshes, but thinking to represent rainfall runoff with subcatchments, as it is more flexible. However, applying rainfall runoff to a 2D point source can mean that lots of water goes into a single mesh, which is not inappropriate in most cases. So, could you please enhance ICM so that we can drain to 2D line source?
5 votes -
Include a Rainfall Generator Using Environment Canada Data
Similar to the ARR and NOAA 14 storm generators, build one that could utilize Environment Canada data with common distribution types.
6 votes -
Allow all objects (nodes, subcatchments etc) to be included within the ‘gauge’ objects used in the run window
In a simulation run window the user has the choice to use a selection list of 'gauged' objects. This is useful so as to provide the results of some objects more frequently, or to only save the results from some objects and not others, in order to keep simulation data sizes down. Currently only links can be 'gauged' objects. It would be beneficial to allow all objects to be 'gauged' as currently to save the results for 1 node requires saving all objects in the model.
(In addition, the 2D Zone is by far the most data hungry object, so…
6 votes -
Urban (or modified) ReFH rainfall inputs
ICM currently supports the use of ReFH And ReFH2 parameters. However, it does not support the Urban (or modified) ReFH rainfall that is more commonly used in urban environments. Please could ICM introduce the ability to use Urban ReFH parameters in their system.
3 votes -
Overhaul to the Hyperlinks system to allow attached data to be transportable
ICM and Infoasset databases offer a system that allow hyperlinked documents to be connected to the database. Primarily this to allow survey, as laid and other background data to be available to the user and is a powerful function that if used correctly would allow databases to become much easier / quicker to check, improving quality and confidence. Currently the models are abstract representations of the systems, and to check detail requires arduous library time retracing other people's steps. Having the data bundled with the model is a significant improvement.
However, two practical problems arise, since many different organizations work…
11 votes -
Call the 'Total storage calculation' function from a ruby script and write the output into a csv-file
It would be a great feature to call the 'Total storage calculation' function from a ruby script and write the output into a csv-file.
If it is not possible to call the build-In function from ruby, it would also help to call the 'storage calculation function' from InfoWorks ICM UI for a set of nodes (maybe from a selection list) and write the output directly to csv-file(s).
2 votes -
1 vote
-
Improve ground infiltration simulation parameters.
Could we have a 'Node level affects groundwater infiltration' for the soil store please?
This simulation parameter was introduced to InfoWorks ICM recently to limit infiltration from the ground store to the model. Could this be extended to limit flows from the soil store as well?
As often when are using models for design purposes, infiltration can become excessive in design events compared to verification. Therefore we have to manually reduce soil store inflow, often requiring new limiting discharge orifices and nodes at each subcatchment with GI applied. Thanks19 votes -
Add a result grid window for cross sections
Currently there is not a grid results window to show all cross sections. Would be helpful to have one. Also would be good if the grid window can show geometric elements of each cross section, such as bank levels, flow area, wetted perimeter, hydraulic radius, critical depth, etc.
9 votes -
Transportabele database (.icmt) containing an earlier version of the commited network without losing the commit history
For the moment we can only 'branch' an earlier version from the commit history interface or 'copy' this earlier version.
- the branch can't be disconnected from the 'mother' network
- the copy looses the commit history
It would be nice to deliver a .icmt file that contains only the earlier version of a network we are working on including the commit history and detached from the original network, so no branch.8 votes -
Rename Pages in Observed vs Predicted Graphs to Flow Monitor/ Depth Monitor nos
Provide way to rename Pages on Observed vs Predicted Graphs to Flow Monitor/ Depth Monitor nos. If there are considerable nos of FM/ DMs, an individual has to go through page nos to find out which FM is checked/verified. Facility to rename the pages to relevant FM/DM would help quick viewing of graphs.
8 votes -
Attach Model documentation to Db
be able to attach documents, model user guide, MBV etc so key documentation in one place. Similar to InfoAsset
1 voteI think this is a duplicate idea.
-
blockage
Applying pipe blockage is a standard required in Australia and the functionality in ICM to do this is not user friendly (using blockage links). A simple % pipe blockage in the conduit properties should really be an option. This is particular the case for cross drainage and also orifice and pipes leaving detention basins (where a pit isnt used)
12 votes -
More gems available ICM Exchange that allow for a better user interface (shoes, tk, RubyFX, etc.)
I would like more gems to be available within ICM Exchange that allow for a better end-user experience with ICM Exchange (not command line prompts). The specific gems I would reccomend are shoes, tk, and RubyFX - or any other gems that have applications for user interface
1 vote -
8 votes
-
Zoom graphs on either axis
Many software suites allow the option to zoom in on both y and x axes on their graphs. However, ICM only allows zooming on the x-axis which often takes away the ability to see trends for lower or higher conditions. I am aware that it is possible to change the y-axis range in properties, but that is not desired since it requires changing the range numerous times as you pan through the data. This is a major caveat which sometimes changes our choice of modeling software, especially for systems which require heavy calibration and data visualization.
14 votes -
RTC Debugging Interface and Support
It would be really useful to have a debugging module for the RTC components in InfoWorks ICM so that one can go step by step through a simulation to display in simulation RTC values-things like variable values (e.g. timers), range/logic values, active/deactivate rules and so on to make isolating RTC schemes simpler. This would be kind of like a debugging module for computer programming in languages such as VBA or C++ or perhaps another grid view. I also find that there are a lot of RTC concepts that we find our by trial and error and it would be useful…
5 votes
