InfoWorks ICM to TUFLOW: Difference between revisions
Content deleted Content added
Tuflowduncan (talk | contribs) No edit summary |
Tuflowduncan (talk | contribs) |
||
Line 36:
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, in the below this is ICM_Out_to_shp_1.rb.
[[File:Ruby.png]]
The script will then begin running and prompt the user to select a config file. Navigate and select the relevant config file.
[[File:Config.png]]
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.
[[File:Ruby log message.png]]
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.▼
▲
InfoWorks ICM Network
[[File:ICM network.png]]
TUFLOW Network
[[File:TUFLOW network.png]]
==Exporting a River Reach==
| |||