InfoWorks ICM to TUFLOW
Introduction
This page outlines an approach for conversion of an infoWorks ICm model to an Estry/TUFLOW format so that the 1D and 2D networks can be replicated in TUFLOW and used to generate a TUFLOW model.
InfoWorks ICM Network Conversion
The InfoWorks data formats are native and therefore do require access to InfoWorks in order to convert the data. Note, that the following steps can be undertaken with a InfoWorks ICM Viewer licence and a full licence is not currently required. Although the InfoWorks ICM data formats are proprietry, it is relatively easy to use the Open Data Export Centre within InfoWorks ICM to export the model geometry data to open GIS layer formats (both shapefile and MIF/Mid format). The following steps will outline exporting to shapefiles but similar can be undertaken for MIF/MID. To open the Open Data Export Centre in InfoWorks ICM, open your network in the geoplan, select the relevant scenario, and go to Network->Export->Using Open Date Export Centre. You’ll be presented with the following dialog which allows you to export the InfoWorks network data to a variety of formats.
The data in InfoWorks ICM is stored in a number of database tables for each network type (eg, a separate table for nodes, conduits, 2D zones etc…).
Quick Export of Geometry Data
To get a quick idea of the 1D network, it’s possible to export 2 tables, ‘All Links’ and ‘All Nodes’. Set the Export type to ‘Shape File’ and select ‘Automap’ to export the InfoWorks fields. Provide a filename and save location and click Export.
Once exported the two shape files can be opened in GIS to view the network links and nodes.
Export to TUFLOW Formats
Within the Open Data Export Centre, it is possible to provide the Export Field Names and to map to them from the internal fields within the InfoWorks tables. This allows you to export directly to a shapefile with a TUFLOW format. For example, in the below image, the Export fields are set up to replicate the TUFLOW 1d_nwk file format. The relevant InfoWorks fields are then mapped to these to convert the InfoWorks format to a TUFLOW shapefile format.
Once the mappings have been set up, they can be saved as a Config file by using the ‘Save Config…’ option. Once a copy has been saved, the config file can be re-used to apply the same field mappings to subsequent exports. It should be noted that not all TUFLOW fields have an equivalent InfoWorks field and vice versa, therefore in some situations there will be some modeller input required to ensure the data is imported in the correct manner. It is also possible to export all InfoWorks fields at the end of the shape file and then use GIS to post-process this for conversions and other simple translations (for example set the TUFLOW pipe type to ‘C’ of the InfoWorks Shape type is ‘Circ’). Please contact support@tuflow.com for an example config file which contains mappings for nodes, pipes, 2D components and 1D structures. The config file is a work in progress but provides a good starting point for the conversion and further mapping of fields between InfoWorks and TUFLOW. Note, that currently the config file is set up to export geometry tables only and will not export tables containing cross-sections, head-discharge curves and similar.
This approach can be used to export on a table by table approach although it is possible to save to the same config file. This allows one config file to set up all the mappings for each of the table exports. The downside of this approach is the time-consuming nature of exporting each table individually.
Use of Ruby Scrips
It’s possible to utilise the Ruby Scripting interface within InfoWorks ICM to speed up the export. A ruby script can be run to call the Open Data Export Centre, and export all requested tables, using a specified config file automatically, significantly reducing the number of button clicks. An example Ruby Script is available from support@tuflow.com which exports the tables as shown in Table 1.
To run the script, you’ll again need to run InfoWorks ICM with a viewer licence or greater. With the desired network in the geoplan, go to Network->Run Ruby Script. Navigate to and select the ruby script.
The script will then begin running and prompt the user to select a config file. Navigate and select the relevant config file.
The user will then be prompted where they would like to export the data too. Select an appropriate file directory. The ruby script will then cycle through the list of tables within the script and export the tables automatically. Once complete the script will return a log highlighting the location of the exported files. All network objects are exported regardless of system type. System type is exported as an additional field in the shape files to enable filtering within GIS as required.
These files can then be opened in GIS for further inspection and once checked can be linked together using the various TUFLOW control files. A set of generic control files for this are in progress.
Exporting a River Reach
The steps above will export the river reach links into a shape file format. These contain the location of the individual reaches and are equivalent to the 1d_nwk_l within TUFLOW. To export River Sections, within InfoWorks you'll need to use an SQL to export the cross-section data (note this is slightly different to river section data). In progress.
Exporting Boundary Conditions
Inflow, level and rainfall boundaries are all held in separate database objects within InfoWorks. To export, open the relevant object (for generated rainfall you’ll need to Open as…->Grid Editor (TVD Read only), select all the data and copy into a spreadsheet to save into a .csv file format. The .csv can then be modified to put it into a TUFLOW format and a bc_dbase file generated to relate the time-varying data to the relevant model node.
Exporting a Gridded Ground model
Within InfoWorks, select the gridded ground model, right click and choose Export->to ESRI ASCII grid files. This will export into a file format that can be directly used within TUFLOW.
Other Considerations
Real Time Control (RTC) objects in InfoWorks will need to be rewritten as TUFLOW operational control rules with TUFLOW Operation Control (TOC) files. Shapefile limitations mean that field names and values can only be 11 characters long. This can mean that some node ids and other information is truncated.