TUFLOW Remapping

From Tuflow
Jump to: navigation, search

The 2020 release of TUFLOW included new Quadtree mesh and Sub-grid Sampling (SGS) functionality. The SGS feature now supports the
hydraulic analysis of partially wet cells on the flood fringe. Currently, cells that are partially wet are displayed in model output
as being fully wet. Whilst we are developing a high resolution SGS map output option for a future release, we have in the meantime
added new functionality to the ASC_to_ASC utility as an interim solution to 'remap' results to a finer DEM grid. This page introduces
how to use the ASC_to_ASC remap function, and discusses limitations of the method.

Remap Advice LinkedIn.jpg







Introduction

With the release of TUFLOW 2020, the combination of Quadtree mesh and Sub-grid Sampling (SGS) method has offered great flexibility for rapidly building flood models of varying resolution and increased topographic detail. Now a wide range of mesh sizes can be applied in a model based on the geographic feature and the area of interest in a project. Especially with the SGS method, cells and faces can be treated as 'partially wet', and the impact of the sub-grid scale geometry may be represented by cells with larger sizes.
The example below shows that a Quadtree model with 10/20m cell size (right) can convey water as smoothly as a 2.5/5/10/20m model along the narrow and meandering gully line.
Fig1 H sgs.png
Figure 1 Water level simulation results with SGS. Left: 2.5/5/10/20m Quadtree model. Right: 10/20m Quadtree model.

On the other hand, the same model running without SGS applied creates notably different results in the distance of water travelled and the area of inundation on the floodplain due to the poor topographic representation (one elevation per cell centre and cell face).
Fig2 H nonsgs.png
Figure 2 Water level simulation results without SGS. Left: 2.5/5/10/20m Quadtree model. Right: 10/20m Quadtree model.

These examples show how the mesh size sensitivity are significantly reduced if using TUFLOW's implementation of SGS. Therefore, modellers can confidently use a coarser mesh at areas away from the area of interest without adversely affecting the results. However, this has created a challenge on how to map results in areas of coarser mesh. For example, the images below show that whilst the 10/20m mesh and the 2.5/5/10/20m mesh SGS models produce similar water levels, the depth output is much 'smoother' in the 2.5/5/10/20m model due to the finer computational mesh.
Fig3 D sgs zoom.png
Figure 3 Water depth simulation results with SGS. Left: 2.5/5/10/20m Quadtree model. Right: 10/20m Quadtree model.

In TUFLOW, the depth output is interpolated from the depths at the nearest cell centre and cell corners surrounding the output grid. Because TUFLOW currently doesn't store the underlying high resolution DEM values other than those needed for the SGS hydraulic computations, the interpolated depth may not perfectly represent the actual depth as illustrated in the figure below.
Fig4 sgs depth interporation.png
Figure 4 TIN interpolation used for water depth map output with SGS.

Whilst we are developing a high resolution SGS map output option for a future release, we have in the meantime added new functionality to the ASC_to_ASC utility to 'remap' a water level grid to a finer DEM grid. This page introduces how to use the ASC_to_ASC remap function, and discusses limitations of the method.

Remapping Water Level to a Finer DEM

The remap function in ASC_to_ASC remaps a TUFLOW water level grid to a high resolution DEM using TIN interpolation. The output is a high resolution water level grid and a high resolution depth grid.

asc_to_asc.exe -remap -wl lowres_h.asc -dem DEM_highres.asc

where:
"-wl <wl_file>"
sets the coarser resolution water level grid to use for the remap.
"-dem <dem_file>"
sets the finer resolution DEM.

The first image below shows the remapped water depth on top of the 10/20m model water level output, and compares it with the original water depth output in the second image. As can be seen, much smooth water depths along the gully and the flood fringes are produced.
Fig5 D sgs remap zoom.png
Figure 5 Remapped vs original water depth for 10/20m mesh SGS model.

The next example presents the water level output and the remapped depth output from a flood model using SGS with the buildings included in the DEM. As can be seen in the first image, large portions of the smaller buildings appear submerged by the SGS water level output due to the cells containing these buildings being partially wet. However, the remapped depths (second image) clearly shows the buildings and produces a much higher resolution flood map.
Fig6 IR.png
Figure 6 Water level output and remapped water depth in a river flood model.

Remapping of Other Map Output Grids

The utility can also remap additional map output grids (e.g. hazard) to the resolution of the DEM file.

asc_to_asc.exe -remap -wl lowres_h.asc -dem DEM_highres.asc lowres_hazard.asc

This command reads in an additional grid 'lowres_hazard.asc' and remaps it to the finer DEM resolution. The figure below compares the original and the remapped hazard outputs from the 10/20m SGS model.
Fig7 ZAEM1 sgs.png
Figure 7 Original vs remapped hazard output for 10/20m mesh SGS model.

It is important to note that, for any output types other than depth, this utility does NOT interpolate the result from the coarser grid to the finer grid, but only extends/reduces the output extent to the dry/wet extent. Therefore, the detail of the remapped hazard above remains the same as the original output grid. The interpolation is not carried out for the following reasons:

  • Hazard categories are usually dependent on both water depth and velocity, and it is problematic to interpolate/extrapolate the computed cell averaged velocity to sub-cell scale velocities with varying water depth.
  • Should a higher output resolution be required for outputs utilising velocity, a finer mesh in the area should be used.

The figure below shows the hazard output from the 2.5/5/10/20m model, and as can be seen the hazard result is much smoother and more accurate along the gully where the finer cell sizes occur.
SGS 02-20m ZAEM1.png
Figure 8 Original hazard output for 2.5/5/10/20m mesh SGS model.

Tip: multiple file names or wildcard are allowed for the extra grid files for remapping.


Model Mesh Size vs Remap Result

Beside the quality of velocity based outputs discussed above, the model mesh size can also impact the remapped output at locations with steep slope as discussed below.

Road Crests

When water flows over a road crest, the remapped water depth may become negative if the output grid size is coarse. The figure below shows the remapped depth over a road crest from models with mesh sizes ranging from 5m to 1.25m. As can be seen, some areas don't have remapped depths despite the water clearly over-topping the road.
Fig9 road mesh size.png
Figure 9 Remapped depths over a road crest from models of different mesh resolutions.

As illustrated in the chart below, the DEM has a much finer resolution and the elevation changes rapidly across the road crest, so when interpolating a coarser water level grid to the finer DEM, the interpolated water level may become lower than the local DEM level. In the 2D solver, this type of location is treated as upstream controlled weir flow with the upstream depth used for the calculation. However, the information that the flow is upstream controlled is not known when remapping, hence the appearance of dry patches on the downstream face of the road crest. Consideration of this effect will be addressed during the development of the high resolution SGS output feature scheduled for a future TUFLOW release.
Fig10 road mesh size2.png
Figure 10 Modelled water level line over the road crest.

Steep Catchments

In direct rainfall models, substantial benefits are being realised from applying SGS. The cell faces now correctly capture the lowest elevations along the gullies to preserve the sub-cell scale flow paths, which can significantly improve the hydrologic response for a whole catchment model (see Duncan Kitts' LinkedIn post: https://www.linkedin.com/pulse/sub-grid-sampling-step-change-way-we-create-apply-hydraulic-kitts/). However, if the cell size becomes too large in areas of significant topographic change, only a small portion of the cell may be wet. This makes the depth plotting extremely challenging and the remapped depth may become negative even though water is flowing through the cell. The blue contour below shows the remapped water depth of a 60m mesh direct rainfall model. As can be seen the flow paths are not continuous along some valleys. The remapped water depth from a 20m mesh model is also plotted as the pink contours underneath the 60m result demonstrating that how the flow paths have become clearer as the mesh size is refined even though the results from these two models are very similar when using SGS.
Fig11 Innisfall remapped D.png
Figure 11 Remapped depth at upstream catchment from different mesh size models.

Conclusion

The benefits of using the combination of Quadtree mesh and Sub-grid Sampling method are many. In this page we focused on the ability of representing the sub-grid scale geometry by SGS method, which allows the user to apply a coarser mesh to reduce the total simulation time without adversely affecting the results. However, the interpolation of map output from a coarser mesh can be challenging as illustrated in the examples above. While we are developing a high resolution output feature within TUFLOW to tackle this issue, the new remapping functions of the ASC_to_ASC utility can be used to post process water level outputs to high resolution depth results. This produces smooth depth output along main flow paths and flood fringes. However, the SGS method and remapping tool is not a panacea, and a computational mesh with sufficient resolution is still needed to produce reasonable and meaningful simulation results, especially where high resolution velocity based map outputs are needed.

Finally, should you have some interesting results using SGS, Quadtree or the remapping feature that you would like to share with the TUFLOW community, please feel free to email support@tuflow.com.