Revision as of 15:42, 30 May 2022 view source Chris Huxley (talk \| contribs) Bureaucrats, Administrators 7,767 edits →Why are results from 2d_po features, POMM.csv and plots extracted from XMDF in GIS package not matching? ← Older edit		Revision as of 09:59, 31 May 2022 view source Pavlina Monhartova (talk \| contribs) Bureaucrats, Administrators 5,343 edits →Why are grids processed with TUFLOW_to_GIS different from TUFLOW grids? Newer edit →
Line 8: == Why are grids processed with TUFLOW_to_GIS different from TUFLOW grids? == Slight differences are expected between the result grids (ASC or FLT) produced directly from TUFLOW and post-processed from the TUFLOW_to_GIS utility from XMDF or DAT due to differences in the interpolation approach. Check <u>[[~~TUFLOW_FAQ~~TUFLOW_Output_Discussion#Why_are_grid_outputs_.28ASC.2C_FLT.29_slightly_different_from_mesh_outputs_.28XMDF.2C_DAT.29.3F \| Why are grid outputs (ASC, FLT) slightly different from mesh outputs (XMDF, DAT)?]]</u> question above on differences between outputs direct from the TUFLOW Engine.<br> When ASC/FLT results are sampled from the XMDF files with the TUFLOW_to_GIS utility, it uses less data points than when the grids are written directly from TUFLOW.

TUFLOW Output Discussion: Difference between revisions