Revision as of 14:52, 1 May 2025 view source Par (talk \| contribs) Bureaucrats, Administrators 1,003 edits No edit summary ← Older edit		Latest revision as of 15:00, 1 May 2025 view source Par (talk \| contribs) Bureaucrats, Administrators 1,003 edits No edit summary
Line 19: If the message received is "ERROR 3517 - "FC" not supported yet in SGS" this is because a GIS 2d_fcsh layer is used. Change this to a 2d_lfcsh layer which is supported when using SGS. If the message received is "ERROR 3517 - "Read RowCol Zpt" not supported with Quadtree" or "ERROR 3517 - "Read RowCol Zpt" not supported in SGS" use the source elevation layer that the file was originally generated from. ~~Alternatively,~~This ifcan ~~you~~be ~~have~~replaced ~~both~~with ~~.mid/.mif~~"Read itGrid isZpt" ~~possible~~if ~~to generate~~using a raster ~~within QGIS which can be read into TUFLOW instead. If there is no .mif file~~grid, ~~this~~or ~~can~~"Read beTIN ~~generated~~Zpt" ~~in TUFLOW~~if using ~~the~~a ~~following~~TIN ~~in the TGC (anywhere the zpt layer is not 99 will be the original sample points and elevations)~~surface. ~~Note that SGS must be switched off for this model run to get the .mif file created:<br>~~ Alternatively, if you have both .mid/.mif it is possible (although not recommended) to generate a raster within QGIS which can be read into TUFLOW instead. If there is no .mif file, this can be generated in TUFLOW using the following in the TGC (anywhere the zpt layer is not 99 will be the original sample points and elevations). Note that SGS must be switched off for this model run to get the .mif file created:<br> <font color="blue"><tt>Set Zpts<font color="red"><tt>== </tt></font> <font color="black"><tt>99</tt></font><br> <font color="blue"><tt>Read MID Zpts<font color="red"><tt>== </tt></font> <font color="black"><tt>input_file.mid</tt></font><br>

TUFLOW Message 3517: Difference between revisions