TUFLOW Message 0305

TUFLOW Message
ERROR 0305 - Projection of .mif file is different to that specified by the MI Projection == command.

Alternate Message
WARNING 0305 - Projection of .mif file is different to that specified by the MI Projection == command.

Message Type
ERROR
WARNING

Description
By default, TUFLOW checks that the projection in each .mif file matches that specified in the MI Projection == command. This ensures that incoming files are in the same projection as the TUFLOW model. TUFLOW is not a GIS software and does not use the projection information in each file (apart for the check). TUFLOW uses the co-ordinates of the objects in the GIS and locates in the TUFLOW model. Hence the need for a projection check. All model input files should be in the same projection, if inputs are not in the correct projection the data will be in the wrong location and won't be used. If your model is in (for example) MGA 94 zone 56, and the 2d materials (2d_mat) file is in the wrong projection (e.g. NSW ISG 56/1), these material regions (polygons) will be in the wrong location (probably in the middle of the ocean) and they won't be assigned to any model cells.
This check prevents problems with the data provided having a different projection than the TUFLOW model.

This check can be set to give either an error (this is the default): MI Projection Check == ERROR
This message can be downgraded to a warning: MI Projection Check == WARNING
Or this check can be turned off entirely using: MI Projection Check == OFF

Care should be taken if turning this check off!!

The fourth line of a .mif file contains the projection information, for example it may look like this:
CoordSys Earth Projection 8, 104, "m", 177, 0, 0.9996, 500000, 10000000 Bounds (-7745844.29597, 2035.05676326) (8745844.29597, 19997964.9432)

Occasionally the last few numbers which are the bounds of the projection, can change even when the projection is the same. Of this occurs TUFLOW will report a "Message 0305".

Suggestions
Check the projection of the problem file. This can be done in MapInfo by Selecting Table >> Maintenance >> Table Structure and selecting the Projection button. If this is different from the projection of the model, re-project to the correct projection.

If the table is in the same projection as the TUFLOW model, compare the projection line from the .mif file with that specified in the MI Projection == command. If the bounds are different, you can overwrite the projection line (line 4) in the problem .mif file with that in the projection.mif, re-import the file and export the file (backup first). This should correct the issue of the TUFLOW error without changing the GIS data. If multiple files are different, this message can be set to warning, however you should check all files with this warning to ensure that they are in the same projection as the TUFLOW.mif!

Up
0xxx Messages