Search results

Jump to navigation Jump to search
  • |tuflow_message=ERROR 0420 - Could not read projection line in .prj file. ...NG 0420 - Could not find PROJCS definition. Projection of .shp file might not be Cartesian.
    838 bytes (131 words) - 15:40, 4 January 2024
  • Some or all non-spatial messages may not appear in _messages GIS layer. ...OW messages have a spatial location (for example a cell elevation that has not been assigned), however, some messages such as <u>[[TUFLOW_Message_1298]]</
    2 KB (273 words) - 11:10, 22 December 2022
  • |tuflow_message=WARNING 2123 - Pit or node does not connect to an active cell within any 2D domain - 2D link ignored. |alt_msg=WARNING 2123 - Pit or node is not inside any 2D domain - 2D link ignored.
    497 bytes (84 words) - 15:00, 2 February 2023
  • |alt_msg=ERROR 2839 - Split polyline should not have more vertexes than the original polyline ...ne features, for example when PO lines or part of PO lines are outside the model area for Quadtree models.
    533 bytes (85 words) - 16:03, 23 February 2024
  • ...PC model running with a different timeseries of timesteps to the base case model. <br> ...are a result of the development features and not a result of change in the model timestep.<br>
    3 KB (555 words) - 15:31, 30 May 2022
  • |tuflow_message=ERROR 2206 - ZC value not initialised (exceeds 99998m) |alt_msg=ERROR 2206 - ZU value not initialised (exceeds 99998m)<br>
    1 KB (174 words) - 14:05, 7 February 2023
  • ...gon in 2d_qnl layer or 2d_code layer if level 1 polygon in 2d_qnl layer is not used.<br> Quadtree nesting polygons can only be within the model domain.
    1,012 bytes (166 words) - 10:02, 3 March 2023
  • ...ied with "Defaults" command set to Pre 2017. Prior to 2017 TUFLOW HPC was not released. ...UFLOW HPC was only released in 2017. Setting Defaults prior to 2017 should not be used.
    440 bytes (64 words) - 09:48, 3 March 2023
  • |tuflow_message=CHECK 2098 - Could not find a SC connection snapped to SH boundary. ...boundary should be linked to another 2D cell or 1D node via SC connection (not CN connection). This boundary is used for modelling pumps or other water ex
    696 bytes (117 words) - 12:31, 23 December 2022
  • |message_desc=The data in the binary (xf) version is not the same precision as the simulation. For example the .xf file has been ge <font color="blue"><tt>Model Precision </tt></font> <font color="red"><tt>==</tt></font><br>
    1 KB (178 words) - 16:34, 5 January 2024
  • |tuflow_message=ERROR 2132 - Node is duplicated or does not exist in external 1D domain. ...thin a GIS layer read into TUFLOW must be unique and match the external 1D model exactly.
    570 bytes (93 words) - 13:37, 7 February 2023
  • ...be used to import the check files and view the final elevations in the 2D model. ...ed). This file contains the exact elevations in the model. However, this not so easy to visualise and TUFLOW also outputs a raster (gridded) dataset in
    2 KB (345 words) - 13:25, 5 April 2024
  • ...ocessing Reporting Location Lines. Check "Read GIS Reporting Locations" is not in a 1D block or in .ecf file. ...This error is also triggered when reporting locations are used in 2D only model.
    576 bytes (98 words) - 11:39, 22 December 2022
  • ...be used to import the check files and view the final elevations in the 2D model. ...the model. As this point vector layer contains thousands of points and is not easy to visualise TUFLOW also outputs a raster (gridded) dataset in the .fl
    2 KB (328 words) - 13:26, 5 April 2024
  • |tuflow_message=ERROR 2104 - CoordSys line could not be found in "<font color="black"><tt>MI Projection</tt></font>" .mif file. ...OR 2104 - "<font color="black"><tt>Mi Projection</tt></font>" command does not support Shapefile projection (.prj) file as input.
    1 KB (150 words) - 12:33, 23 December 2022
  • ...metimes, ensuring there are no open versions of the layer when running the model may resolve this issue. <br> ...iles]], and do not create empty template files manually or copy from other model folders.
    709 bytes (115 words) - 15:50, 4 January 2024
  • ...the solution to remain stable. There are a variety of reasons that a HPC model may require these corrections:<br> * Poorly configured 1D/2D model interface
    1 KB (206 words) - 09:16, 3 March 2023
  • |tuflow_message=ERROR 0046 - 1D Output Interval not specified.<br> |alt_msg=WARNING 0046 - 1D Output Interval not specified. Defaulting to every timestep.<br>
    1 KB (234 words) - 10:04, 22 December 2022
  • |message_desc=The filepath is long and some features might not work correctly. ...g copy model (-c) or package model (-pm). Shorten the file path to run the model.<br>
    801 bytes (119 words) - 17:21, 19 April 2024
  • |tuflow_message=ERROR 0252 – <file format> is not a supported GIS file format. |message_desc=The file format specified is not a recognised file format. For example:<br>
    910 bytes (153 words) - 11:09, 22 December 2022

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)