Revision as of 16:03, 28 May 2021 view source Pavlina Monhartova (talk \| contribs) Bureaucrats, Administrators 5,379 edits No edit summary ← Older edit		Revision as of 16:19, 28 May 2021 view source Pavlina Monhartova (talk \| contribs) Bureaucrats, Administrators 5,379 edits No edit summary Newer edit →
Line 3: \|alt_msg=WARNING 0305 - Projection of .shp file is different to that specified by the GIS Projection == command. \|type=[[ERROR]] <br> [[WARNING]] \|message_desc=By default, TUFLOW checks that the projection in each '''.shp''' or '''.mif''' file matches that specified in the SHP Projection == or MI Projection == command, respectively. 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 layer and locates them 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 polygons will be in the wrong location (probably in the middle of the ocean) and they won't be assigned to any model cells.<br> This message prevents problems with the data provided having a different projection than the TUFLOW model.<br><br> <u>Message Options</u><br> Line 22: Care should be taken if turning this check off that all files are in the correct projection.<br> <u>Projection Files'''</u><br> Line 41 ⟶ 40: PROJCS["GDA94_MGA_zone_54",GEOGCS["GCS_GDA_1994",DATUM["D_GDA_1994",SPHEROID["GRS_1980","<font color="red">6378137.0</font>,298.257222101]</tt><br><br> \|suggestions= 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" for Example 2. A new '''.tcf''' command has been added to allow setting to the previous “Simple” string compare:<br>▼ * Check the projection of the problem file. This can be done in the following software. If this is different from the projection of the model, re-project to the correct projection. <br>▼ ~~<font color="green"><tt>SHP Projection Check Method == SIMPLE </tt></font><br>~~ QGIS by Layer Properties >> Source under the “Assigned Coordinate Reference System (CRS) header.<br>▼ MapInfo by Selecting Table >> Maintenance >> Table Structure and selecting the Projection button.<br>▼ 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, you can overwrite ~~the '''.prj''' file associated with the shapefile with that in the '''projection.shp'''<br>~~ :▼ * For shapefiles - the '''.prj''' file associated with the shapefile with that in the '''projection.shp'''<br> ~~\|suggestions=As described above, different software (or even different versions of the same GIS software!) can write the same projection in a different way.~~ Or** ~~for~~For MapInfo, ~~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 (as described above), however you should check all files with this warning to ensure that they are in the same projection.<br>▼ To avoid this happening, it is best to develop a model entirely within one GIS software (with the same version number). This can be difficult when given a model created by others or updated an existing model. If this is the case, we suggest:<br> * Develop a model entirely within one GIS software. ~~Check the projection of the problem file. This can be done in <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" for Example 2. ~~A new '''.tcf''' command has been added to allow setting to the previous “Simple” string compare:<br>~~ ▲QGIS by Layer Properties >> Source under the “Assigned Coordinate Reference System (CRS) header.<br> ▲MapInfo by Selecting Table >> Maintenance >> Table Structure and selecting the Projection button.<br> ▲If this is different from the projection of the model, re-project to the correct projection.<br> ▲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, you can overwrite the '''.prj''' file associated with the shapefile with that in the '''projection.shp'''<br> ▲Or for MapInfo, 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 (as described above), however you should check all files with this warning to ensure that they are in the same projection.<br> <br> In order to change the projection in MapInfo it is necessary to save a copy of the table. To do this:<br>

TUFLOW Message 0305: Difference between revisions