InfoWorks ICM to TUFLOW: Difference between revisions
Content deleted Content added
Tuflowduncan (talk | contribs) |
Tuflowduncan (talk | contribs) |
||
Line 57:
|-
|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.
|-
|1D Structures ||Channel||1d_nwk_Channels||Geometry exported. Need to export shape to csv file and link to 1d_nwk_channels file.
|-
|1D Structures ||Culvert Inlet||1d_nwk_Culvert_Inlet||Geometry exported but no direct equivalent in TUFLOW currently.
|-
|1D Structures ||Culvert Outlet||1d_nwk_Culvert_Outlet||Geometry exported but no direct equivalent in TUFLOW currently.
|-
|1D Structures ||Flap Valve||1d_nwk_Flap_Valve||Converted to a circular, uni-directional conduit.
|-
|1D Structures ||Flume||1d_nwk_Flume||Geometry exported but no direct equivalent in TUFLOW currently.
|-
|1D Structures ||Inline Bank||1d_nwk_Inline_Bank||Imported as an irregular weir. Section data needs bringing across.
|-
|1D Structures ||Irregular Weir||1d_nwk_Irregular_Weir||Imported as an irregular weir. Section data needs bringing across.
|-
|1D Structures ||Orifice||1d_nwk_Orifice||Geometry Exported.
|-
|1D Structures ||Pump||1d_nwk_Pump||Geometry Exported. Operational Control may need specifying.
|-
|1D Structures ||Screen||1d_nwk_Screen||Geometry Exported.
|-
|1D Structures ||Siphon||1d_nwk_Siphon||Geometry Exported.
|-
|1D Structures ||Sluice||1d_nwk_Sluices||Geometry Exported.
|-
|1D Structures ||User Control||1d_nwk_User_Control||Geometry Exported.
|-
|1D Structures ||Weirs||1d_nwk_Weirs||Geometry Exported.
|-
|1D River Reach ||River Reach||1d_nwk_River_Reaches||Geometry Exported and needs tying into section data. See below section on river reaches.
|-
|2D Domain ||2D Zone||2D_Code||Geometry Exported, Code region set to 1.
|-
|2D Domain ||2D Point Source||2D_bc_P||Set to QT boundary.
|-
|2D Domain ||2D Boundary||2D_bc_L||.
|-
|2D Domain ||2D Boundary||2D_bc_L_Line_source||Set to QT Boundary.
|-
|2D Domain ||Roughness Zone||2D_mat||Material ID set to Manning's n value. Need to generate materials csv file with Material ID equal to the Manning's n value.
|-
|2D Domain ||Infiltration Zone (2D)||2D_soils||Defines the spatial locations of different soils types. Need to specify a separate tsoilf.
|-
|2D Initial Conditions ||Infiltration Zone (2D)||2D_IWL||The IC Zone – hydraulics (2D) defines the location that the initial condition is applied. The initial water level will need to be obtained from the Initial Conditions (2D) object.
|-
|2D Results Object ||Network Results Line (2d)||2D_po_L||
|-
|2D Results Object ||Network Results Point (2d)||2D_po_P||
|-
|2D Topography Modifications ||Mesh Level Zone||2D_zsh_R_MLZ||Geometry Exported
|-
|2D Topography Modifications ||Mesh Zone||2D_zsh_R_MZ||Geometry Exported
|-
|2D Structures||Porous Wall||2d_lfcsh_Porous_Wall||Geometry Exported
|-
|2D Structures||Base Linear Structure(2D)||2d_lfcsh_BLS||Geometry Exported
|-
|2D Structures||Sluice Linear Structure(2D)||2d_lfcsh_SLS||Geometry Exported
|-
|2D Structures||Bridge Linear Structure(2D)||2d_lfcsh_BridgeLS||Geometry Exported
|-
|}
Where the notes show 'Geometry Exported', it is envisaged that there will be some user interaction to confirm the model schematisation.
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.
| |||