InfoWorks ICM to TUFLOW: Difference between revisions
Content deleted Content added
Tuflowduncan (talk | contribs) |
Tuflowduncan (talk | contribs) |
||
Line 42:
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 [mailto:support@tuflow.com support@tuflow.com] which exports the tables as shown in Table 1.
'''Ruby Script Conversion'''
{| align="center" class="wikitable"
! style="background-color:#005581; font-weight:bold; color:white;" | Component
! style="background-color:#005581; font-weight:bold; color:white;" width=25% | InfoWorks Table Name
! style="background-color:#005581; font-weight:bold; color:white;" width=25% | TUFLOW File
! style="background-color:#005581; font-weight:bold; color:white;" width=50% | Notes
|-
|1D Node ||Node||1d_mh_pit||Headloss Approach is assumed to be TUFLOW’s default Engelund approach.
|-
|1D Pipes ||Conduit||1d_nwk_pipe||Conduit shape ‘CIRC’ are set as Type ‘C’ and shape ‘RECT’ are set as type ‘R’, otherwise the conduit shape is set to I. Where ‘I’, the shape will need separately defining. Conduit Width/Height are converted from ‘mm’ to ‘m’.
|-
|1D Subcatchment ||Subcatchment||1d_sa_subcatchment||Only the Geometry is exported.
|-
|1D Structures ||Bridge||1d_nwk_Bridges||Bridge methods are different so the bridge would need to be rebuilt in TUFLOW/Estry. Only the link geometry is exported.
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.
| |||