Tuflow

InfoWorks ICM to TUFLOW: Difference between revisions

Browse history interactively
← Older edit
Content deleted Content added
VisualWikitext
 
(59 intermediate revisions by 2 users not shown)
Line 1:
'''Page In Progress'''
 
=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.<br>
Line 5 ⟶ 7:
 
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/MidMID 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 DateData Export Centre'''. You’ll be presented with the following dialog which allows you to export the InfoWorks network data to a variety of formats.
 
[[File:ODEC.png|400px]]
Line 14 ⟶ 16:
==Quick Export of Geometry Data==
 
To get a full export of all the model files, with InfoWorks file formats, open the network and go to '''Network->Export->to Shape Files''', select the save location and the InfoWorks tables that you're interested in. Once exported the shape files can be opened in GIS to view the network table geometry and parameters. Once the data is exported, it's possible to use the QGIS TUFLOW Plugin 'Insert TUFLOW Attributes to Existing GIS Layer' and then map across the field values from InfoWorks to TUFLOW with conversion as required.
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.
 
A Ruby script is also available which will export export all data via the Open Data Export Centre without the need for the user to export each table individually. The data can use a config file to undertake some of the mapping of field values and some conversion.
[[File:ODEC Links Automap.png|400px]]
 
[[File:ODEC Nodes Automap.png|400px]]
 
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.
 
[[File:ODEC Conduit TUFLOW.png|400px]]
 
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. Note in the 'Field type' column there are a number of different options specified. These are:-
 
*'''Constant'''-Allows the user to specify a constant value, for example, specify a constant value of '1' for the 'Code' field when exporting 2D Zones. It is also used when exporting a null value.
* '''Field'''-This is used to directly map an InfoWorks ICM field to a TUFLOW/Estry field. For example, copying the 'conduit_length' field to the 'Len_or_ANA' field for conduits.
*'''SQL'''-This allows a simple structured query language (SQL) script to export a combination of fields. For example, the ID is set to US_node_ID + link_suffix.
* '''Script'''-This allows the user to utilise a ruby script to filter out exported items or to convert fields. For example, for conduits, conduits with an InfoWorks shape type of 'CIRC' can be exported to TUFLOW link types 'C', shape types 'RECT' to 'R' and all others to 'I'.
 
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. An example configuration file which contains mappings for nodes, pipes, 2D components and 1D structures can be obtained from [mailto:support@tuflow.com support@tuflow.com]. The config file 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. TUFLOW are not responsible for the accuracy of the config file and subsequent translation of data.
 
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 Scripts==
 
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 <u>[mailtohttps:support@tuflow//gitlab.com support@/tuflow.com-user-group/tuflow/model-conversions/infoworks-icm TUFLOW Gitlab User Group]</u> which exports theall tables asand showndata in Tablean InfoWorks 1format.
 
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, in the below this is ICM_Out_to_shp_1.rb.
Line 63 ⟶ 44:
[[File:TUFLOW network.png|400px]]
 
==Exporting aReal RiverTime Reach=Control=
Operational Control is referred to as Real Time Control (RTC) in InfoWorks. The ruby script above will export the RTC as a text file called [Network_Name]_ICM_RTC.txt which can be used as the basis to generate the TUFLOW Operational Control file. The RTC is made up of the object that is being controlled, the defined ranges in which the structure operates and the desired operation. For example in the below example, the sluice gate, Storm1_Chamber.1, will be set to an 'On' position of 0.2m if the height above datum at FORAST_CSO is below 32.3m AD and will be set to an 'Off' position of 0m if the water level is above 32.3m AD.
 
[[File:RTC.PNG]]
 
This can be written using TUFLOW Operation Control rules as the following:-
 
<font color="blue"><tt>Define Sluice </tt></font> <font color="red"><tt>==</tt></font> Storm1_Chamber.1
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.
WSE <font color="red"><tt>==</tt></font> H1D FORAST_CSO
<font color="blue"><tt>IF</tt></font> WSE < 32.3
Gate Opening <font color="red"><tt>==</tt></font> 0.2
<font color="blue"><tt>ELSE</tt></font>
Gate Opening <font color="red"><tt>==</tt></font> 0
<font color="blue"><tt>END IF</tt></font>
 
=Exporting Boundary Conditions=
Line 79 ⟶ 71:
=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=
 
*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. This is reported in the error reporting.▼
Real Time Control (RTC) objects in InfoWorks will need to be rewritten as TUFLOW operational control rules with TUFLOW Operation Control (TOC) files.
<br>
▲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.
{{Tips Navigation
|uplink=[[Main_Page| Back to Main Page]]
}}
Retrieved from "https://wiki.tuflow.com/InfoWorks_ICM_to_TUFLOW"