InfoWorks ICM 9.5 has now been released and is available for download from the Innovyze website under
The overarching goal for this release was to improve user productivity and expand InfoWorks ICM functionality for more advanced applications and integration. A good number of the new features have been included in this post, with examples and detail provided where appropriate.
The Innovyze approach to product development is customer-centric. As such, these new features and enhancements are very much driven and enabled by our active user base and delivered in addition to InfoCare services. We thank you all for the continued support and feedback.
- NEW: 2D conduits for 2D simulations. 2
- New: Connect 2D node. 3
- NEW: MicroDrainage importer. 4
- NEW: SOBEK importer. 6
- NEW: Gated weirs. 7
- New: Additional data file formats for spatial TSDBs. 8
- NEW: Euler Type II design rainfall 9
- NEW: German hydrology. 11
- NEW: RAFTS routing model 12
- Enhancement: Variable crest and width weirs. 14
- Enhancement: 3D view cropping options. 14
- Enhancement: 2D engine multi GPU support via PCI switches. 15
- Enhancement: Exporting snapshot files. 15
- Enhancement: Updating TSDB to latest versions. 16
Two new types of conduit have been introduced in InfoWorks ICM 9.5, these include conduit type “Conduit (2D)” and “Linear Drainage (2D)”.
The conduit type linear drainage (2D) can be used to represent slot drains and other gully types that may interact with the surface along a significant length. Use of the linear drainage (2D) object is most suitable for those situations where the length of the drain or trench is much longer than the face length of mesh elements.
In the example shown above, the first timestep shows a rectangular mesh (both in the 3D view and then in plan view), flow has been added to the mesh at the left side, the second timestep shows this flow entering and filling the linear drainage (2D) type conduit (note this turns dark blue as it fills). All of the flow is captured until in the last screenshot the capacity of the linear drainage (2D) object is overcome, at this point flow begins to bypass the linear drainage (2D) object and passes to the other side.
Linear drainage (2D) link types have an orientation, so only capture flow from one side, looking down a link from upstream to downstream, it is the right side which will be able to take flows from the mesh.
In addition to the linear drainage (2D) object, there is also a conduit (2D) object which has been introduced, this works in very similar fashion to a 1D link, but includes conservation of momentum from the mesh/link interface. This means that it would be preferable for the representation of culverts between two parts of a mesh, for example. This link type is modelled directly in the 2D engine, so when using this object the requirement for a 2D manhole/inlet/outfall is removed, with these being replaced by a “Connect 2D” node instead. More information is available in the help regarding the equations used.
The linear structure (2D) and conduit (2D) can be connected to the mesh using a new node object called a “Connect 2D” node. The Connect 2D node does not require an internal volume, ground level or some of the other core parameters associated with manhole objects, this means that a link drawn to interact with the 2D mesh can now do so directly.
When a Connect 2D node has been created, there are multiple options in terms of what happens to flow that reaches this point (so in effect the end of a Linear Drainage (2D) or Conduit (2D) link). The node can be treated as:
- Closed – The node does not allow any escape from the connected link at this end, effectively sealing off flow from the end point.
- Lost – The node allows flow via the last vertex of the connected link, but any flow that passes through this point is lost from the system entirely.
- 2D – The end point of the connected link is connected to the mesh element within which the node resides.
- Break – This can be used for a change in gradient or direction for the link which is connected, it effectively acts as a connection point between multiple links of the Conduit (2D) and/or Linear Drainage (2D) types.
A new model import option has been added to InfoWorks ICM, this option has been designed to allow for model import from MicroDrainage directly into InfoWorks ICM. To access the new import option, open a network GeoPlan and then go to Network>Import>Model>from MicroDrainage data…
Once the data has been imported you should find a very close match between MicroDrainage and InfoWorks ICM, bearing in mind that some structures are stored slightly differently between the two products or may have different fields related to them. The screenshot below has been taken from a model in MicroDrainage and then an equivalent model in InfoWorks ICM after the import was performed.
We are currently working on completing a SOBEK importer. For version 9.5 the first phase of this work which has been completed was released. To access the SOBEK importer, open a network in the GeoPlan and then go to Network>Import>Model>from SOBEK network data…
Once this option has been selected there will be a new window that appears.
The SOBEK data folder will be the folder containing the .lit extension folders for different models, the network dropdown and the version options for the selected network will then be made available.
A new weir type has been added to InfoWorks ICM, this is the gated weir. A gated weir has either forward or reverse orientation and can have varying angles from bed level (as most commonly used for river modelling). Gated weirs were also present in InfoWorks RS, the implementation is the same in ICM. Below is a screenshot from the help showing some of the parameters utilised by gated weirs.
There have been several new additions to the spatial TSDB data file formats, these include the Geotiff – Meteo Group (observed and forecast), the Grib 1 -AEMET Madrid (forecast) and the HDF5 OPERA (observed) formats. From version 9.5 onwards it will be possible to bring these data formats into spatial TSDBs.
A new design rainfall option has been added to InfoWorks ICM. Euler Type II rainfall using the KOSTRA-DWD 2010R data can now be generated using rainfall event objects. To access this option, generate a new rainfall event and keep the “Generated Design Rainfall” options checked, this will bring up the following window, within this select the “Euler Type II Rainfall” rainfall generator type.
Once the Euler Type II rainfall has been selected, a new window will then appear, this window will allow for the Easting and Northing of the catchment to be specified. When the values have been populated you will then be able to generate the remaining values within the grid (these are taken from the KOSTRA-DWD 2010R data tables).
A new runoff volume model, the DWA (Grenzwertmethode) has been implemented in InfoWorks ICM 9.5. The runoff volume model is available in the same location as those already existing, so it can be selected from the runoff surfaces tab in the subcatchments grid.
Some parameters used by the model were previously only available for the Horton and Horton SWMM runoff volume models. The specific naming of parameters related to these have been modified for suitability across both the Horton models as well as the DWA methodology. Impacted fields are listed below, along with their new names:
Horton initial -> Initial infiltration
Horton limiting -> Limiting infiltration
Horton decay -> Decay factor
Horton recovery -> Recovery factor
A new cascade routing model is now available for runoff surfaces and relevant details have been included in the help.
The RAFTS routing model has been added to InfoWorks ICM and it can be selected in the runoff surface tab of the subcatchments grid.
When the RAFTS model is selected for a runoff surface, there are several options which can be set for how the storage delay time coefficient B is calculated.
- Use all surfaces, calculated
When the default flag is set for the subcatchment properties B value, then this will be calculated for all surfaces referenced by a subcatchment combined. As such, the value will be identical for all surfaces for the subcatchment and based on the degree of urbanisation, catchment area, catchment slope and the RAFTS Adapt Factor. Here, the impervious and pervious split of surfaces within that subcatchment will determine the degree of urbanisation.
- Use all surfaces, user defined
In this case, there is a single RAFTS B value applied for the subcatchments, used for all surfaces, rather than having the default flag for the RAFTS B field. The user has the ability to overwrite the calculated value manually with a new entry to be used for the subcatchment.
- Per-surface RAFTS B, calculated
For subcatchments there is a new field available under routing named “Per-surface RAFTS B”. This field can be checked in order to apply the RAFTS B value on a per surface basis rather than per subcatcment.
With the Per-surface RAFTS B checked, the runoff surface parameters will be used to calculate RAFTS B in the engine when a simulation is performed.
- Per-surface RAFTS B, user defined
As per the third option above, in this case the Per-surface RAFTS B field for a subcatchment must be enabled. With this done the runoff surface(s) used by the subcatchment may have their field “User-specified RAFTS B” active, allowing for manual input of RAFTS B into the runoff routing value field for that runoff surface.
In InfoWorks ICM it is possible to have up to 12 runoff surfaces per land use. Per subcatchment, this means that users modelling with RAFTS runoff routing will have the opportunity to have up to 12 individual runoff surfaces with individually calculated RAFTS B values per subcatchment. This is not restricted to a single value for pervious and impervious surfaces.
To prevent confusion around the possible entries for variable crest and variable width weirs, we’ve amended the relevant fields for the minimum and maximum extents to “Minimum/Maximum Width” and “Minimum/Maximum Crest”.
It is now possible to crop the extent of a mesh which is displayed in the 3D view. This is done by sizing the GeoPlan to the extent of the mesh to be viewed, and by then holding down the ctrl and pressing the 3D view button. The extent of the 1D network to be displayed is limited to the selection active in the GeoPlan (else the total network). This means that it is now possible to restrict the extent of both the 1D and the 2D to varying levels while initiating a single 3D view.
Previously it was not possible to select the GPU to be used when this was connected to a PCI switch. Rather, users could only select the PCI slot that the GPU was connected to. It is now possible to extend the key value to select the specific GPU connected to the switch that will be used.
Now, users can export snapshot files from a network by right clicking and then going to the “Export” option. There is no longer a need to open the network in the GeoPlan and users can select the version of the network to be exported to snapshot files.
The “Update to latest” text which was previously present in the TSDB dialogue of a run schedule was slightly misleading, asthis updated the version time used by the TSDB to the latest rather than updating the TSDB to the latest available data. The text has been modified to more accurately reflect this function.
The “Refresh time series database(s)…” option could previously trigger unnecessary locking of the TSDB when not used with the latest TSDB version time. This option has been disabled unless the “Use latest” is active as any other TSDB version time option does not require an update.