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? ← Older edit		Revision as of 10:00, 31 May 2022 view source Pavlina Monhartova (talk \| contribs) Bureaucrats, Administrators 5,343 edits →Why is Z0 hazard coming directly from TUFLOW different to the one calculated from maximum velocity and depth? Newer edit →
Line 21: The maximum velocity and maximum depth doesn’t necessarily occur at the same time. The Z0 hazard written directly from TUFLOW has the depth x velocity calculated every timestep and at the end outputs the maximums of all the timesteps. When using the velocity and depth grids the maximum velocity is always used with maximum depth. <br> Outputting the Z0 hazard grid directly from TUFLOW is more accurate, however, if this is not an option, manual creation is an acceptable workaround. The general recommendation is to choose one method and keep it consistent for the length of the project.<br> When calculating the Z0 hazard from the velocity and depth, the grids have already been interpolated by TUFLOW before the raster calculation (less data is used for the calculation), whereas the TUFLOW Z0 output is interpolated from the calculated data directly. Please also refer to the above question for more information <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>.<br> == Why does hazard output (Z1, Z2, ...) show float values and not just integers? ==

TUFLOW Output Discussion: Difference between revisions