InfoWorks ICM to TUFLOW: Difference between revisions
Content deleted Content added
Tuflowduncan (talk | contribs) |
Tuflowduncan (talk | contribs) No edit summary |
||
Line 144:
The steps above will export the river reach links into a shape file format. These contain the location of the individual reaches and are equivalent to the 1d_nwk_l within TUFLOW. To export River Sections, within InfoWorks you'll need to use an SQL to export the cross-section data (note this is slightly different to river section data). '''In progress'''.
=Exporting Real Time Control=
Operational Control is referred to as Real Time Control(RTC) in InfoWorks. The ruby script above will export the RTC as a text file called [Network_Name]_ICM_RTC.txt which can be used as the basis to generate the TUFLOW Operational Control file. The RTC is made up of the object that is being controlled, the defined ranges in which the structure operates and the desired operation. For example in the below example, the sluice gate, Storm1_Chamber.1, will be set to an 'On' position of 0.2m if the height above datum at FORAST_CSO is below 32.3m AD and will be set to an 'Off' position of 0m if the water level is above 32.3m AD.
[[File:RTC.PNG]]
This can be written using TUFLOW Operation Control rules as
=Exporting Boundary Conditions=
| |||