Difference between revisions of "TUFLOW Message 0631"
Jump to navigation
Jump to search
(One intermediate revision by one other user not shown) | |||
Line 8: | Line 8: | ||
This error may occur when using the 2023 Release due to changes made to support the new GeoPackage spatial database syntax. In previous releases, TUFLOW would default to .MIF if no file extension was included. Models upgraded to the 2023 Release may now receive this error. | This error may occur when using the 2023 Release due to changes made to support the new GeoPackage spatial database syntax. In previous releases, TUFLOW would default to .MIF if no file extension was included. Models upgraded to the 2023 Release may now receive this error. | ||
− | |suggestions= | + | |suggestions= |
− | Check to see GIS input file referenced in the control file has a file extension. | + | Check to see GIS input file referenced in the control file has a file extension. |
|uplink=[[0xxx_TUFLOW_Messages|0xxx Messages]] | |uplink=[[0xxx_TUFLOW_Messages|0xxx Messages]] | ||
}} | }} |
Latest revision as of 16:15, 4 January 2024
TUFLOW Message
ERROR 0631 - no extension on input file: <>.
Alternate Message
ERROR 0631 - "<>" is not a supported GRID file format.
ERROR 0631 - GIS GRID Format is not currently supported as an input.
Message Type
ERROR
Description
This error may occur when using the 2023 Release due to changes made to support the new GeoPackage spatial database syntax. In previous releases, TUFLOW would default to .MIF if no file extension was included. Models upgraded to the 2023 Release may now receive this error.
Suggestions
Check to see GIS input file referenced in the control file has a file extension.
Up |
---|
0xxx Messages |