In the .tcf file specify the .tgc file using Geometry Control File.
add to .tcf file:
Geometry Control File == ..\model\my_model.tgc
Re-run TUFLOW using the .tcf file. The run should stop after exporting the 2d_zpt layer.
Import “2d_zpt_my_model.mif” into MapInfo and save using the same name. View the layer noticing the different types of Zpts (these are colour coded).
The elevations at each Zpt are given a temporary “dummy” value of 99,999, and therefore need to be assigned their correct elevation. Zpt elevations are assigned from the DTM using 3D surface modelling software. For example, by using the “Point Inspection” operation in Vertical Mapper. If the elevations are added as an extra attribute (as is the case with Vertical Mapper), the added attribute must be relocated to be the fourth attribute and the default “Elevation” attribute column must be removed or moved. (In MapInfo use Table, Maintenance, Table Structure… to do this). TUFLOW assumes the elevations are in the fourth attribute column. Additional columns beyond the fourth can exist, but are not used by TUFLOW.
If some of the Zpts fall outside the DTM, they would have been assigned the “Null” value (eg. Vertical Mapper assigns –9999.) or possibly a zero. These Zpts need to be selected and deleted as they have no meaningful elevation.
Save and export the 2d_zpt layer (overwrite the .mif/.mid files previously imported).
Comment out the Write MI Zpts line in the .tgc file (otherwise the 2d_zpt .mif/.mid files exported in the previous step will be overwritten), and use Read MID Zpts to read the 2d_zpt layer into TUFLOW. Note the use of MID (not MI) in this command and that the filename must that of the .mid file. This command only reads the .mid file which must contain four attributes, namely cell row (n), cell column (m), Zpt type (Type) and the elevation.
