Tuflow

InfoWorks ICM to TUFLOW: Difference between revisions

Browse history interactively
← Older editNewer edit →
Content deleted Content added
VisualWikitext
Line 70:
| Orifice||1d_nwk_Orifice||Link exported but no direct equivalent in TUFLOW currently.
|-
| Pump||1d_nwk_Pump||Link Exportedexported. Set as a PO type but user should check and add Operational Control as required.
|-
| Screen||1d_nwk_Screen||Link Exportedexported but no direct equivalent in TUFLOW currently.
|-
| Siphon||1d_nwk_Siphon||Link Exportedexported but no direct equivalent in TUFLOW currently.
|-
| Sluice||1d_nwk_Sluices||Link Exportedexported together with fields. Set to SGO type where sluice is variable.
|-
| User Control||1d_nwk_User_Control||Geometry Exportedexported.
|-
| Weirs||1d_nwk_Weirs||Link Exportedexported together with fields. Weir types converted accrossacross.
|-
|'''1D River Reach''' ||River Reach||1d_nwk_River_Reaches||Geometry Exportedexported and needs tying into section data. See below section on river reaches.
|-
|rowspan="6" |'''2D Domain''' ||2D Zone||2D_Code||Polygon geometry Exportedexported, Code region set to 1.
|-
| 2D Point Source||2D_bc_P||Point exported and set to QT boundary.
Line 116:
|}
 
WhereAlthough the notesgeometry showis exported in 'Geometrymost Exported'instances, it is envisaged that there will be some user interaction to confirmmap across the modelrelavent fields to the closest TUFLOW schematisationequivalent.
 
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.
Retrieved from "https://wiki.tuflow.com/InfoWorks_ICM_to_TUFLOW"