Importing TUFLOW Network Data

1D network data from TUFLOW can be imported to InfoWorks ICM using files in the MapInfo Interchange File (MIF) format.

To import TUFLOW network data:

  1. Open the network to be updated.
  2. Select Import | Model | from TUFLOW network data from the Network menu, and the TUFLOW Import dialog is displayed.

    ClosedShow me

  3. Enter the path to the MIF file to be imported, or click to display a Windows File Open dialog and browse for the file.
  4. If required, choose a flag from the Flag dropdown menu. If information of the selected type is included in the import, then it will be marked with the selected flag.
  5. Click OK

An import log will be displayed with any import errors or warnings.

For details of the objects imported and any conversions made by the InfoWorks ICM Importer, see the Import Notes below.

Import Notes

The following files are read by the InfoWorks ICM Importer during the import process:

 

File Type Notes
Material .tmf

A Material file should be located two levels up in the folder structure from the MIF file. If it is not, the InfoWorks ICM Importer will treat this as an error, report it in the log file, and the import will fail. Similarly, if there is more than one Material file in the folder, this will also be treated as an error, reported in the log file, and the will import fail. If there is one Material file then it is read, but if there is no file, then the Importer skips this phase and no error is reported in the log file.
Pit Inlet Database .csv

The Pit Inlet Database csv file should be located two levels up in the folder structure from the MIF file. If it is not, the Importer will treat this as an error, report it in the log file, and the import will fail. Similarly, if there is more than one Pit Inlet Database file in the folder, this is also treated as an error, reported in the log file, and the will import fail. If there is one csv file it is read, but if there is no file, then the Importer skips this phase and no error is reported in the log file.
MapInfo Interchange .mif

Two types of MIF files are read; manhole files (1d_mh file) and "other 1d network files". Any object with fewer than 3 fields in the csv file are ignored by the Importer, as are any objects with an 'Ignore' field set to 'True'. Flag fields are set to the chosen flag for fields which are set. Null values are ignored and values of the wrong type are reported in the log and then ignored.

Manhole files

A manhole file (1d_mh file) is imported as a node with the existing name and the x and y coordinates. The flags for the coordinate fields are set to the chosen flag for fields which are set.

Other 1d network object files

These are imported in 4 consecutive phases:

Phase Help
1

Point Objects

  • If the object is a point object in the MIF file, the Importer handles it if it is of type 'C', 'Q', 'R' or 'W'.
  • The node ID is set to the MIF ID.
  • The x and y coordinates are set to the MIF x and y coordinates.
  • The system type is set to 'storm'.
  • The flood type is set to 'Gully 2D' for type Q, '2D' otherwise.
  • MIF field 7 is used to set ground level (unless the value is -99999 which is treated like null).
  • MIF field 8 is used to set chamber floor.
  • If the type field is 'Q', MIF field 11 is used for the name.
  • If the type field is 'Q', the value in MIF field 13 is treated as a multiplier to the flow in the depth-discharge curve, otherwise it is treated as the diameter of the chamber – and thus converted to the chamber areas (for the multiplier 0 is treated as 1).
  • If the type field is 'Q', the value in MIF field 15 is treated as ANOTHER flow multiplier (with 0 being treated as 1), otherwise it is put into the flooding discharge coefficient field.
  • If the object is of type 'Q' and references a depth-discharge curve csv file (which exists and has been read) then a head discharge object is created from the data in the csv file with the flow multiplied by the two multiplying factors. The object will be named as follows:
    1. After the value in field 11 if there is not one with that name
    2. Otherwise by the name of the node if there is not already one with that name
    3. Otherwise by the node name with a number appended (in the unlikely event there is one of both the values described above.

    Note that the multiplication factors mean that curves based on the same CSV file may be different.

    The type is put into user text field 1.
2

Link Objects - Upstream end

If there is not already a node at the X and Y coordinates of the first coordinate of the polyline in the MIF file, then the Importer creates a node at that location with the name of the object in the MIF file, and the ground level set to the US invert level (field 6) in the data record. If the object has no name, a name is created for it (the first name of the form TUXXX<number> not already used).
3

Link Objects - Upstream end

If there is not already a node at the X and Y coordinates of the last coordinate of the polyline in the MIF file, then the Importer creates a node at that location with the name of the object in the MIF file with X appended to the name, and the ground level set to the DS invert level (field 7) in the data record. If the object has no name, a name is created (the first name of the form TUXXX<number> not already used) for it.
4

Link Objects - General

The upstream and downstream node IDs are found via the IDs of the nodes at the upstream and downstream ends of the polyline (imported from either the manhole file (Phase 1), or the link objects (Phases 2 and 3)).

The 'number of' field (MIF field 15) is read first if the link is of type 'C', 'I' or 'R'. If it is, then that number of identical links is created – if the value is 0 then 1 is created as normal.

Any links created are given a link suffix to make them unique.

The following applies to all the links created for any single TUFLOW object:

  • The MIF ID for the link is put into the asset ID field.
  • A conduit is created for all link type except 'S'.
  • Roughness type 'N' is used.
  • If the type is 'C' or 'S' then the shape is set to 'CIRC' or 'RECT' respectively.
  • If the type is one of blank, 'C', 'G', 'I' or 'R', the conduit length is set to MIF field 5 and the roughness (MIF field 6) is put into both top roughness and bottom roughness.
  • If the type is 'S' the length is put into the (differently named) length field for the channel and the roughness value is retained for later use.
  • If the type is blank, 'C', 'G', 'I', 'R', 'S', 'W' or 'B', the invert levels (MIF fields 7 and 8) are put into US and DS invert fields (except types 'B' and 'W' where the maximum value is put into both).
  • If type is 'C', 'R' or 'W', MIF field 14 is imported into InfoWorks ICM's conduit width field (converted from m into mm). For type ‘R’ , MIF field 15 imported into InfoWorks ICM's conduit width field (converted from m into mm).
  • If the type is 'S', the Importer reads the channel shape from a CSV file which is located in the xs subdirectory of the directory’s parent’s parent – e.g. if the model is in d:\my\model\mi\1d_mod.mif, then the Importer checks in d:\my\model\xs – to find a file with the name of the object (i.e. field 0) and then one with _X added onto the name.

    Invert levels will also be read from the shape CSV file if the invert levels in MIF field 7 and 8 are -99999 (which are treated like null).

    See below for details of the shape CSV file.

  • MIF field 19, entry loss, is used as US headloss coefficient, with the type being FIXED.
  • MIF field 20, exit loss, is used as DS headloss coefficient, with the type being FIXED.
Shape .csv

Columns X, Z, M and LCR are imported from the shape CSV file. X and Y are obligatory, M is optional, providing a roughness value has been specified for the object, and LCR is optional.

Any extra header line, containing the filename, in the first column is ignored.

The value in the M (material) column is taken from the materials file and used to determine the roughness.

The value in the LCR column, if any, is used to create a panel marker at the point at which the value changes. Permitted values are 1, 2 and 3.

Importing Network Data

TUFLOW Import Dialog