Tuflow

TUFLOW Message 0305: Difference between revisions

Browse history interactively
← Older edit
Content deleted Content added
VisualWikitext
No edit summary
No edit summary
 
(18 intermediate revisions by 2 users not shown)
Line 1:
{{TUFLOW_Message
|tuflow_message=ERROR 0305 - Projection of .mif file is different to that specified by the <font color="black"><tt>MI Projection </tt></font><font color="black"><tt>== </tt></font>command.
|alt_msg=WARNING 0305 - Projection of .shpmif file is different to that specified by the GIS<font color="black"><tt>MI Projection </tt></font><font color="black"><tt>== </tt></font> command.<br>
ERROR 0305 - Projection of .shp file is different to that specified by the <font color="black"><tt>GIS Projection </tt></font><font color="black"><tt>== </tt></font> command.<br>
WARNING 0305 - Projection of .shp file is different to that specified by the <font color="black"><tt>GIS Projection </tt></font><font color="black"><tt>== </tt></font> command.<br>
ERROR 0305 - Projection of .gpkg layer is different to that specified by the <font color="black"><tt>GPKG Projection </tt></font><font color="black"><tt>== </tt></font> command.<br>
WARNING 0305 - Projection of .gpkg layer is different to that specified by the <font color="black"><tt>GPKG Projection </tt></font><font color="black"><tt>== </tt></font> command.<br>
|type=[[ERROR]] <br> [[WARNING]]
|message_desc=By default, TUFLOW checks that the projection in each '''.shp''' or '''.mif''' file matches that specified in the <font color="blue"><tt>SHP Projection </tt></font><font color="red"><tt>== </tt></font> or <font color="blue"><tt>MI Projection </tt></font><font color="red"><tt>== </tt></font> 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>
This message can be set to give either an error (this is the default): <br>
<font color="greenblue"><tt>
SHP Projection Check </tt></font><font color="red"><tt>== </tt></font><font color="black"><tt>ERROR</tt></font><br>
<font color="blue"><tt>MI Projection Check </tt></font><font color="red"><tt>== </tt></font><font color="black"><tt>ERROR</tt></font><br>
 
This message can be downgraded to a warning: <br>
<font color="greenblue"><tt>
SHP Projection Check </tt></font><font color="red"><tt>== </tt></font><font color="black"><tt>WARNING</tt></font><br>
<font color="blue"><tt>MI Projection Check </tt></font><font color="red"><tt>== </tt></font><font color="black"><tt>WARNING</tt></font><br>
 
Or this message can be turned off entirely using (use with caution!): <br>▼
<font color="green"><tt>▼
SHP Projection Check == OFF<br>
MI Projection Check == OFF</tt></font><br>
 
Care should be taken if turning this check off that all files are in the correct projection.<br>
 
 
▲Or this message can be turned off entirely using (use with caution - all files should be checked they are in the correct projection!): <br>
▲<font color="greenblue"><tt>
SHP Projection Check </tt></font><font color="red"><tt>== </tt></font><font color="black"><tt>OFF</tt></font><br>
<font color="greenblue"><tt>SHPMI Projection Check Method</tt></font><font color="red"><tt>== SIMPLE</tt></font><font color="black"><tt>OFF</tt></font><br>▼
<br>▼
<u>Projection Files'''</u><br>
QGIS or ArcMap - The .prj file associated with each shapefile might start similarly as below:<br>
<tt>PROJCS["GDA94_MGA_zone_54",GEOGCS["GCS_GDA_1994",DATUM["D_GDA_1994",SPHEROID["GRS_1980",6378137,298.257222101]</tt><br>
<br>▼
MapInfo - The fourth line of a .mif file contains the projection information. For example it may look like this:<br>
<tt>CoordSys Earth Projection 8, 104, "m", 177, 0, 0.9996, 500000, 10000000 Bounds (-7745844.29597, 2035.05676326) (8745844.29597, 19997964.9432)</tt><br>
<br>
 
The shapefile projection string can be written slightly differently when switching between GIS packages (e.g. QGIS, ArcMap) or using different tools for shapefile exporting even though it is still the same projection.
Occasionally the last few numbers which are the bounds of the projection, can change even when the projection is the same. If this occurs, TUFLOW will report a "Message 0305". This is a common occurrence when the same projection is written differently. There are two examples below that are the same projection however written differently:<br>
 
Example 1:<br>
<tt>PROJCS["<font color="red">GDA94</font>_MGA_zone_54",GEOGCS["GCS_GDA_1994",DATUM["D_GDA_1994",SPHEROID["GRS_1980",6378137,298.257222101]<br>
PROJCS["<font color="red">GDA_1994</font>_MGA_Zone_54",GEOGCS["GCS_GDA_1994",DATUM["D_GDA_1994",SPHEROID["GRS_1980",6378137,298.257222101]</tt><br><br>
Example 2:<br>
<tt>PROJCS["GDA94_MGA_zone_54",GEOGCS["GCS_GDA_1994",DATUM["D_GDA_1994",SPHEROID["GRS_1980","<font color="red">6378137</font>,298.257222101]<br>
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=
In the above case there is a slight difference in the number due to the decimals. Build 2020-01-AB 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. A new '''.tcf''' command has been added to allow setting to the previous “Simple” string compare:<br>▼
* Check the projection of the problem file., Thisthis can be done infollowing the steps below: <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* byMapInfo Selecting- Table >> Maintenance >> Table Structure and selecting the Projection button.<br>▼
* If the GIS layer projection is different from the model projection, re-project to the correct projection. This can be done by saving a copy of the file with correct projection:
**QGIS:
*** Right click on the file to be re-projected
*** Select '''FileExport >> Save CopyFeatures As'''▼
*** Under '''CRS''' select the correct projection and save
**MapInfo:
*** Select '''File >> Save Copy As''' and select the table to be saved▼
*** Select the '''Projection...''' button in the dialogue box▼
*** In the '''Choose Projection''' dialogue set the desired projection and save▼
* 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="greenblue"><tt>SHP Projection </tt></font><font color="red"><tt>== </tt></font> or <font color="greenblue"><tt>MI Projection </tt></font><font color="red"><tt>== </tt></font> command. If the bounds are different (refer to Examples above), you can overwrite the '''projection line.prj''' fileThis associatedshould withcorrect the shapefileissue 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.shp'''<br> ▼
** Shapefiles - the '''.prj''' file associated with the shapefile with that in the '''projection.shp'''<br>
** MIF files - 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).
* Develop a model entirely within one GIS software.
▲In* the above case there is a slight difference inUse the numberlatest due to theTUFLOW decimalsrelease. BuildSince 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. Awith new"Message '''.tcf'''0305" commandfrom hasExample been added to allow setting to the previous “Simple” string compare:<br>2.
 
 
|suggestions=As described above, different software (or even different versions of the same GIS software!) can write the same projection in a different way.
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>
▲Check the projection of the problem file. This can be done in <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>
▲* Select '''File >> Save Copy As'''
▲* Select the table to be saved
▲* Select the '''Projection...''' button in the dialogue box
▲* In the '''Choose Projection''' dialogue set the desired projection
* Set a new file name and select '''Save'''
Some images are provided below.<br>
[[File:Error0305 01.jpg]]
▲<br>
<br>
[[File:Error0305 02.jpg]]
|discussion_page=* [[Talk:TUFLOW Message 0305|Discuss Message 0305]]
|link3=''
|link4=''
|prelink=[[TUFLOW_Message_0304|Message 0304]]
|uplink=[[0xxx_TUFLOW_Messages|0xxx Messages]]
|nextlink=[[TUFLOW_Message_0306|Message 0306]]
}}
Retrieved from "https://wiki.tuflow.com/TUFLOW_Message_0305"