InfoWorks ICM to TUFLOW: Difference between revisions

Browse history interactively

← Older edit

Content deleted Content added

VisualWikitext

Revision as of 11:17, 23 January 2023 view source Chris Huxley (talk \| contribs) Bureaucrats, Administrators 7,785 edits →Other Considerations ← Older edit		Latest revision as of 22:53, 6 January 2026 view source Tuflowduncan (talk \| contribs) Bureaucrats, Administrators 1,219 edits →Quick Export of Geometry Data Tag: Visual edit
(3 intermediate revisions by 2 users not shown)
Line 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/~~Mid~~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~~Data 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 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 ~~sue~~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. 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. Line 22: ==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>[~~mailto~~https:~~support@tuflow~~//gitlab.com ~~support@~~/tuflow~~.com~~-user-group/tuflow/model-conversions/infoworks-icm TUFLOW Gitlab User Group]</u> which exports all tables and data in an InfoWorks format. 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.