Water Distribution
31 results found
-
Multi-thread simulations
As a user I want to take advantage of multi-threaded CPUs to accelerate simulation intensive procedures (e.g. design calibration)
23 votes -
Add ability to rename datasets, patterns, queries, etc
- Allow the "Change ID" tool to rename datasets, patterns, queries, etc.
- Make the "Change ID" window wider or resizeable to fit longer IDs.
10 votesPartially completed: “Change ID” window is now resizable. Functionality available from InfoWater Pro 3.5 Update 2. Target release data April 2021
-
Customize ArcGIS Pro ribbon with command center modeling tools
While building and editing models, I want to customize easy access to tools currently burried in the Command Center (e.g. Trace Network, Join/Remove Layer tables, Clear message board, etc.).
ArcGIS Pro lets you customize toolbars, but these commands aren't yet available.7 votes -
Allow InfoWater to export simulation results in CSV format instead of DBF
The option to "Export simulation results for external application" in InfoWater would be more useful if the results were exported as CSV files instead of DBF files. We regularly need to compare the results from multiple model scenarios. Microsoft PowerBI or Excel PowerQuery are great tools for importing and comparing large amounts of data and could streamline this process significantly. However, neither support importing directly from DBF files.
7 votes -
As a planner, I want a single, integrated modelling platform to represent the water supply, sewerage and drainage (1D/2D) system.
Melbourne Water has successfully completed a pilot modelling study using InfoWorks ICM to build a single integrated model to represent the water supply, sewerage and drainage system (including overland flooding) for a proposed redevelopment area (27,000 lots) in Melbourne.
The study explored the capabilities of the software to model the urban water cycle. It has identified some significant advantages to an integrated modelling approach, however there are some key limitations of the software and hardware which limit its future use.
We have published a joint paper that discussed the need and the concept and that can be make available upon…
7 votes -
Batch Edit Datasets
Currently if there needs to be a global change to a dataset, the only way is to manually go through each dataset and change the element property and save. As an example, if a valve needs to be closed in multiple datasets, it would be nice to have a tool to allow that change happen to all desired datasets at one time.
This feedback also goes along with the previous posted feedback title: "Data Sets" by Kathryn Carreira and "Push Changes From Parent to Child(ren) Scenarios" by Joe Lawrence.
6 votes -
Contours and Spot Elevation data for Elevation Extractor in InfoWater Pro
While rasters remain the best way to assign elevations throughout the model, InfoWater also supported other formats using interpolation such as contours and point elevation.
Please add these file types in InfoWater Pro.5 votes -
Further "Set Area Codes" functionality - InfoWorks WS Pro
2 feature requests for consideration, both relating to the “set area codes” functionality in InfoWorks WS Pro:
1. The ability to save the “set area code” configuration, whether that be in a model tree group or as a cfg file, so that you don’t have to reset all preferences every time you open the tool
2. A “pause area code identification” button so that you can make multiple changes to assets without having to wait for the area codes to recalculate after every minor change (and without having to close the set area code window to prevent the recalculation, which…5 votes -
Persistent Graphs in InfoWater/InfoWater Pro
Stored graphs aren't that great. Why not just make graphs persistent? This is one area where competitors blow away InfoWater and InfoWater Pro. No contest.
5 votes -
Be able to change the background colour
In InfoWorks the background colour for the GeoPlan is white - it would be beneficial to change this colour to the users choice to make particular features stand-out more clearly in the GeoPlan view
5 votes -
Node Name Generation Default
In WS PRO it would be great to be able to set Node Name Generation format as a default for all networks in a database instead of having to enter it in every time I want to add nodes to a network
5 votesThe functionality is already provided with the Digitisation Template in WS Pro. Please confirm what enhancement are you suggesting. Thanks
-
Improvements to custom DB table fields
- Ability to modify the length of custom fields in the DB tables after they have been created. This is particularly a problem when you create a text field, but realize later it is too short. Another option would be to make the default text length 250 characters rather than 20.
- Better manager for custom fields. The user should be able to create a field once and choose which information DB tables to add it to. See example at link. https://ibb.co/CbFKnn2
5 votes -
Sort selection sets/ re-order them
Would be very useful if you could either sort selection set orders or move selections up or down the list. This would make it much faster to find the selection set you want in a large list (e.g. DMA selection sets in alphabetical order)
4 votes -
Add new run groups and move existing runs to these
I’ve currently got one very big run group which should’ve really been split into several different ones.
Is there a way to move around runs? In the explorer there’s only really the option to duplicate.4 votes -
Boundary trace toolbar shortcut
I often use the boundary trace tool to understand the extent of a DMA/PMA. Currently, we have to go to Geoplan -> Tracing Tools -> Boundary Trace, and it would be a lot easier if it was available as a toolbar shortcut.
3 votes -
Access to UDF Data through DB Editor
In InfoWater Pro, the model data can be accessed through the DB Editor. The UDF tool does not have any access to the database tables through the DB Editor. It would be very helpful if I could gain access to the UDF tables through the DB Editor, even if it were just under the Advanced Application Data (for Advanced Users), which most users should not use. I ended up having to use a different application to gain access to the DB tables.
2 votes -
Allow Customized Reports to Also Include Standard and Fireflow Results - Just Have One Result Table
Currently all model element information and results are separated between the DB Editor, Customizable Report, and Output Report/Graph. This is confusing and hard to export specific information together without having to combine it later in Excel or GIS. The main frustration is that the “Standard” or “Design Fireflow” in the Output Report/Graph results are completely separate from other information related to the model elements. As an example, it would be nice to export all fire flow results for junctions alongside any custom fields made in the DB Editor for easy referencing.
In short, instead of having three types of tables…2 votes -
New Feature is Active in All Scenarios Option (InfoWater/Pro)
Add a tools/options option so when you add new features they will be active in all scenarios, instead of getting errors 100 times for every scenario you try to run where the features were not included originally. This would be especially useful when using Intelliselection.
2 votes -
I would like more informative error messages when trying to Change an ID
I tried to change the ID for a pump, but I overlooked the “Target Element Type” dropdown, which was automatically set to junction.
It took me a while to realize my mistake. It might be helpful to other users if the error messages/warnings (see below) were a bit more informative… I’d suggest something like “WARNING: Junction ID ‘P1240’ does not exist.” I think this would have helped me realize my error much sooner.
WARNING: unable to change Junction ID from 'P1240' to 'P1241'.
MESSAGE: no Junction ID was changed.2 votes -
Edit Pump and Valve Curves in IWLive
IWLive is the perfect platform to examine how well valve and pump curves are simulating the actual behavior under a wide range of system conditions. If these could be modified in an incident run, it would save lots of time going back to WS to modify them.
2 votes
