Storm Sewer & Flood Modeling
Welcome to the Innovyze Stormwater, Sewer, and Flood modeling feedback page.
56 results found
-
Bridge section data updates
When a bridge section is changed then there are repeatable tasks for entering openings again, if this workflow could be improved that would be great.
8 votes -
Create selection list from level or inflow events
In some of our older or larger models the number of profiles in level or inflow events have grown to > 100. Through the time quite a number of these have become obsolete because of consecutive model updates (resulting in many log warnings), but it is a very painstaking task to check them all one by one. Therefore it would be a big help if there were a possibility to create a selection list from these events that contains all the profile IDs (and vice versa to create a new event with profiles based on an existing selection list).
3 votes -
Ground model inference rememebered
When object entries are updated from ground model, it would be good if the previously used settings could be remembered the next time the dialog is triggered.
5 votes -
RTC - New time range to allow "between 2 dates" every year
In a similar way to the way "time repeat" works, can we have an RTC range that works between the same 2 dates every year. I have a catchment where the operating protocol works differently in the Bathing Season from the rest of the year. Having a way to check with one range if we are in the bathing season or not would avoid the clunky work arounds.
11 votes -
RTC updated to support scripting
It would be good to have RTCs available through direct scripting rather than through the RTC editor alone.
8 votes -
The ability to save databases/models as previous versions for backwards compatibility
A few of our clients use different versions of InfoWorks for various reasons (some are resistant to upgrading until they've had a chance to vet the new versions and understand the changes in house). This can create a problem where we must maintain and build using multiple versions of the software and multiple databases for different versions to serve different clients.
I would like the ability to save a database/transportable database for compatibility of previous versions. Similar to what we have with AutoCAD, where you can work in the latest version, but choose which version to save it in. Currently…
6 votes -
Realign feature
A new feature I’d like to see for lines/polygons is a ‘realign feature’ tool. When selected, if you clicked on a vertex in a line or on a polygon boundary (single click and release), it would ‘grab’ that vertex and allow you to move it. Once you placed it, when you move the mouse either direction along the line, it would AUTOMATICALLY grab the next vertex on the line. Right-clicking would bring up a menu allowing you to ‘release’ the line (leaving the ‘grabbed’ vertex in its original location), delete the grabbed vertex, insert a new vertex, or ‘skip’ a…
2 votes -
Please provide Intellisense to the SQL Editor in ICM
I want the SQL Editor to help me write SQL queries by color coding and autocompleting data, similar to Intellisence.
9 votes -
Select Assets with a given User Flag in any Properties Field
Allow assets to be selected/sorted (SQL or Grid View) based on a flag value in any properties field. This would make some model build and QA tasks much easier.
For example, data may be needed to properly model a serwerage pumping station but isn't available yet. An engineering judgement may be made with a user flag showing the data has been requested but that an engineering judgement has been made in the interim to allow model build to proceed. The ability to select/sort assets with this user flag in any property field would make user flags much more useful both…
4 votes -
SuDS Structures ID Table
Is there a way to generate a table that lists all Suds Structures IDs? I would like to see this so that I can review total area applied, make changes quickly, and also complete QA checks easily.
1 vote -
Add a modelling confidence field into the User Defined Flags
This could simply be an additional free text field in the "User Defined Flags" window labelled "confidence" OR the user is able to define their own but they are limited to 5-7 options.
The benefit is that when users pick up a model they better understand the confidence associated with each flag. Generally the "Description" field is currently seen as a "source" field. The users can then use SQLs / Ruby to build their own model confidence tools as they see fit while allowing greater transparency and functionality.
7 votes -
Sort by Validation Error in Grid View
Allow columns in grid views to be sorted by validation error(s). This would make fixing validation errors much easier.
For example, when modelled pipes/nodes are updated from the GIS, the Subcatchments sometimes lose their Node ID link as the node names may have changed. Being able to sort these validation issues to the top of the grid would make fixing the errors much easier. This would be particularly useful across multiple scenarios since the selection list created from the validation can't be saved with the "un-shown" objects from a different scenario.
4 votes -
1 vote
-
2 votes
-
Modelling of Pressure Sewer System Storage Vessels
In the modelling of pressure sewer systems you often need to represent the same (standard) storage vessel (storage function) in your network over and over again. However, there is no storage tab in the node grid that would allow you to create and assign a common (named) storage function to multiple nodes.
1 vote -
Enable SQL validation rules in ICM
In InfoAsset it is possible to setup SQL rules that can then be used in validation, it would be nice to have the same in ICM.
0 votes