TUFLOW Message 0305: Difference between revisions

* If the file is in the same projection as the TUFLOW model, compare the projection line from the '''.shp''' or '''.mif''' file with that specified in the <font color="green"><tt>SHP Projection == </tt></font> or <font color="green"><tt>MI Projection == </tt></font> command. If the bounds are different (refer to Examples above), you can overwrite: the projection line. 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 or OFF (as described above), however you should check all files with this warning to ensure that they are in the same projection.<br>

** For shapefilesShapefiles - the '''.prj''' file associated with the shapefile with that in the '''projection.shp'''<br>

** ForMIF MapInfofiles - 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 (as described above), however you should check all files with this warning to ensure that they are in the same projection.<br>

* Use the latest TUFLOW release. Since 2020-01-AB release, TUFLOW parses the parameter data into number values and compares each of these numbers to check they are consistent. This should provide a more robust check less prone to falsely flagging the projections as different with "Message 0305" forfrom Example 2.