Revision as of 18:16, 18 June 2021 view source Tuflowduncan (talk \| contribs) Bureaucrats, Administrators 1,213 edits →Exporting Boundary Conditions ← Older edit		Revision as of 18:19, 18 June 2021 view source Tuflowduncan (talk \| contribs) Bureaucrats, Administrators 1,213 edits →Export to TUFLOW Formats Newer edit →
Line 35: * '''Script'''-This allows the user to utilise a ruby script to filter out exported items or to convert fields. For example, for conduits, conduits with an InfoWorks shape type of 'CIRC' can be exported to TUFLOW link types 'C', shape types 'RECT' to 'R' and all others to 'I'. It is also possible to export all InfoWorks fields at the end of the shape file and then use GIS to post-process this for conversions and other simple translations. ~~Please contact support@tuflow.com for an~~An example ~~config~~configuration file which contains mappings for nodes, pipes, 2D components and 1D structures. can ~~The~~be ~~config~~obtained ~~file~~from is[mailto:support@tuflow.com asupport@tuflow.com]. ~~work~~ inThe ~~progress~~config ~~but~~file provides a good starting point for the conversion and further mapping of fields between InfoWorks and TUFLOW. Note, that currently the config file is set up to export geometry tables only and will not export tables containing cross-sections, head-discharge curves and similar. TUFLOW are not responsible for the accuracy of the config file and subsequent translation of data. This approach can be used to export on a table by table approach although it is possible to save to the same config file. This allows one config file to set up all the mappings for each of the table exports. The downside of this approach is the time-consuming nature of exporting each table individually.

InfoWorks ICM to TUFLOW: Difference between revisions