Revision as of 07:06, 31 October 2025

Abstract

Urban drainage systems are facing increasing challenges due to climate change, urban growth, and the need for more sustainable water management. To address these issues, the Digital DRAIN project has developed an open-source tool that integrates different models within a GIS environment to analyse the performance of drainage systems. The tool helps assess both water flows and pollution, while also supporting the design of sustainable solutions and adaptation strategies. Delivered as the QGIS plugin IberGIS, it provides an accessible framework to improve urban water management and enhance resilience against floods and environmental impacts.

Keywords: urban drainage, 1D/2D modelling, Iber-SWMM, QGIS

Resumen

Los sistemas de drenaje urbano se enfrentan a retos cada vez mayores debido al cambio climático, el crecimiento urbano y la necesidad de una gestión del agua más sostenible. Para abordar estos problemas, el proyecto Digital DRAIN ha desarrollado una herramienta de código abierto que integra diversos modelos en un entorno SIG para analizar el rendimiento de los sistemas de drenaje. Esta herramienta permite evaluar tanto el caudal como la contaminación del agua, además de facilitar el diseño de soluciones sostenibles y estrategias de adaptación. Implementada como complemento de QGIS, IberGIS ofrece un marco accesible para mejorar la gestión del agua urbana y aumentar la resiliencia ante inundaciones e impactos ambientales.

Palabras clave: drenaje urbano, simulación 1D/2D, Iber-SWMM, QGIS

1 Introduction

In recent years, the planning, design, construction, and management of urban drainage elements has evolved towards an integrated approach, known as dual drainage. This process focuses on the joint understanding of all physical processes involved, both in terms of water quantity and quality, as well as surface and sewer network flows, and the final receiving environment (rivers, estuaries, seas, and oceans). This requires modelling and analysis tools that account for such coupling (dual drainage). Furthermore, these tools must address today’s global challenges, moving towards a more sustainable world, improving the ecological status of the environment, incorporating climate change adaptation strategies, and ensuring public safety in the face of natural phenomena such as floods.

Along these lines, the project entitled ‘Digital DRAIN. An Integrated Urban Drainage Model’ (DRAIN, CPP2021-008756) aims to develop an open-source, free modelling tool for analysing all processes of urban drainage, integrated within a graphical information system (GIS) environment. Its purpose is to assess hydraulic performance and the effects of diffuse pollution both on the surface, within the drainage network, and in the receiving environment. The tool will also include specific modules for the implementation of Sustainable Urban Drainage Systems (SuDS) and for analysing actions related to climate change adaptation.

The project derived in a plugin of QGIS, called IberGIS. This plugin is a full integration of the one-dimensional urban drainage software SWMM and a integration of the two-dimensional hydrodynamic software Iber, particularly its calculation module Iber-SWMM [1]. Thus, not all capabilities neither calculation modules of Iber are available. Only particular characteristics of the Iber-SWMM module are described below.

Data

Data to build-up the models presented in this document is stored here.

Important note

This document does not attempt to be a QGIS manual. Despite the whole model’s build-up process is properly defined, the input data might require a pre-process and previous knowledge in GIS environments. The authors encourage users to familiarise with QGIS by reading the documentation and, in case of general doubts, by contacting to the community.

2 Graphical user interface of IberGIS

2.1 Generalities

The graphical user interface (GUI) of the plugin IberGIS has been developed within the QGIS environment, and it follows the visual style guide. As for any plugin of QGIS, IberGIS can be installed through Plugins >> Manage and Install Plugins menu. Type “IberGIS” to search it and then click on Install Plugin button. Once installed, and according to the User’s Profile, it will be loaded automatically during the QGIS initialization.

2.2 Particularities

2.2.1 Model structure

The IberGIS has a workflow fully integrated in the QGIS software. Once installed, the IberGIS button () will automatically appear in the toolbars of QGIS. Clicking there, a new window will ask for the geopackage and QGIS project creation (Fig. 1a).

After that, two new groups of toolbars of IberGIS will appear. One is related to the model’s build-up process (Fig. 1b) and the other to the model’s configuration, checks, run the simulation and visualize the results (Fig. 1c). A brief description of each option is detailed below:

• Import INP (). Imports the *.inp and *.ini files of any SWMM model.
• Boundary conditions manager (). Window that enables saving different boundary condition scenarios.
• Create boundary condition (). It automatizes the implementation of boundary conditions.
• Non visual objects manager (). Window that enables saving different non visual objects, such as timeseries, rules, etc.
• Bridges actions (). Options to implement and edit bridges.
• Options (). Main model options window.
• Generate INP (). Exports the current SWMM layers to a SWMM project.
• Mesh manager (). Window that enables saving different calculation mesh scenarios.
• Execute model (). Window that enables defining general options, selecting the calculation mesh and launch the simulation.
• Results (). Options to visualize the SWMM and Iber results.
• Check project (). Dialog that starts a check project.

Additionally, the Processing Toolbox will show two specific option for IberGIS plugin (Fig. 1d). Processing Toolbox >> IberGIS is related to automatize general procedures such as project checking, import necessary features (ground, roof, inlets layers), import results, and associate Iber inlets/roofs to SWMM junctions. The other one, accessible though 'Processing Toolbox >> IberGIS – Mesh, is a pack of particular options to obtain a well-conditioned calculation mesh.

Fig. 1. IberGIS workflow: (a) geopackage and project creation window; (b) build-up processing toolbar; (c) other options toolbar; (d) processing toolbox of IberGIS; (e) layers structure.

Note that any IberGIS model is saved in two files: a geopackage and the QGIS project. Both are linked and when the user opens the QGIS project, automatically it will look for the geopackage. Additionally, the geopackage contains the model itself, so the user can share it without the QGIS project.

2.2.2 Workflow

All this options and functionalities are oriented to facilitate the model build-up process. Since the model is saved in a unique geopackage, different kind of entities can be saved on it. On one hand, non-visual objects is managed in the abovementioned option (). On the other hand, the creation and edition of visual objects is based on a strict group of layers (Fig. 1e) that contains TEMPORAL information (e.g., meshes, results), INPUT data (e.g., data of SWMM and Iber models) and a BASE MAP image. It is mandatory to preserve the structure of the INPUT group, since other data saved in different layers will be omitted during the calculation process:

INPUT

• SWMM
  • Junction (layer of points)
  • Junction (layer of points)
  • Divider (layer of points)
  • Outfall (layer of points)
  • Storage (layer of points)
  • Conduit (layer of lines)
  • Pump (layer of lines)
  • Orifice (layer of lines)
  • Weir (layer of lines)
  • Outlet (layer of lines)
• IBER
  • Inlet (layer of points)
  • Hyetograph (layer of points)
  • Boundary conditions (layer of lines)
  • Bridge (layer of lines)
  • Culvert (layer of lines)
  • Pinlet (layer of surfaces)
  • Landuses (layer of dataset)
• MESH
  • Mesh anchor points (layer of points)
  • Mesh anchor lines (layer of lines)
  • Roof (layer of surfaces)
  • Ground (layer of surfaces)

The generation of this group of layers is automatic during the models creation. It can be edit manually, using the available tools of QGIS, or automatically, using the tools of IberGIS developed ad-hoc (Fig. 1d). Thus, a manual edition requires the generation of the geometric entities of some layer of INPUT group. I.e., if the user wants to simulate only a SWMM model, the proper layer must contain all the information together with the IBER and MESH data. Whereas, an Iber model, without sewer network, requires the definition of, at least, Ground and Boundary conditions layers. Roof layer is optional and when exists it can be linked directly to the Ground or to the Junction layer (if an Iber-SWMM model is simulated). In this sense, an Iber-SWMM model, i.e., a coupled urban drainage simulation, also requires the definition of the Inlet layer and, if there is no flow, the definition of the rainfall data, whether it is by hyetographs or rasters of rain.

It is worth noticing that raster data as topography or infiltration losses can be added to any layer’s group. During the Mesh generation process () these data, if exists in the project, can be selected. Other raster data, such as rainfall raster, must be defined as a timeseries () by defining the raster name per each time interval. The directory where the raster are located must be provided.

Previous to the simulation process (), a new folder will be created containing the files that calculation engine Iber-SWMM will be used to carry out the simulation, even save the results. As each simulation scenario can be saved independently, different folders will be created. Note if you share the model (*.gpkg and/or *.gps), the folder that contains the results will be lost. So, the model must be re-simulated to generate again the results or consider to share all this information together with the model.

2.2.3 Calculation engine

IberGIS uses the calculation engine of Iber and SWMM, and it particularly oriented to coupled simulations using the integrated module called Iber-SWMM [1]. The urban drainage models usually require high computational effort, especially in large urban areas, the computational time can be an enormous bottleneck. To solve this issue, the simulations are carried out using the parallelised version of Iber-SWMM for NVIDIA graphical power units (GPU) [2]. This allows accelerations in the computational time from 27 to 250 times faster than the single-threaded version.

Both models are freely distributed:

• SWMM: https://www.epa.gov/water-research/storm-water-management-model-swmm
• Iber: https://www.iberaula.com/

2.3 Current and future versions

As above-mentioned, the current version of IberGIS is particularly oriented to address urban drainage and flood scenarios using, in a coupled way, two computational engines: Iber for the rainfall-runoff process and SWMM for the sewer network. Full capabilities and functionalities of the calculation engines are not currently available.

SWMM cannot be run independently since the rainfall-runoff process is carried out by Iber. Future versions might deal with these casuistic by generating a coupled and dual model, part of them being simulated with SWMM and the rest with Iber-SWMM.

Iber currently has 8 calculation modules [3] that works together with the hydrodynamic one, the principal module which the others depends on it. Only functionalities oriented to urban drainage of Iber-SWMM module are currently implemented in IberGIS. Despite that, some other functionalities, especially those related to the general hydrodynamics in flood scenarios assessment, are implemented such as bridges and culverts. Future versions might include other calculation modules of Iber.

3 Study cases

This User’s tutorial is composed by three examples: two real laboratory facility tests and a synthetic case. It is oriented to provide the elemental steps to build-up an IberGIS model, mainly to apply the Iber-SWMM calculation module for urban drainage applications.

3.1 Laboratory case: grate inlet testing platfrom

The experiment facility, located in the Hydraulic and Fluid Mechanics Laboratory of the Polytechnic University of Catalonia (UPC-BarcelonaTECH), consists in a 1:1-scale platform of 5.5 m-length and 3 m-width that represents the roadway of a street (Figure 1). This facility can be feed by a constant discharge up to 200 L/s and it can change its longitudinal and transverse slopes from 0 to 10 % and 0 to 4 %, respectively. It was originally designed to test the efficiency of longitudinal and transversal grate inlets [4–10]; nowadays, it is used to assess hazard criteria for objects that can be floated and transported during rainfall events in urban environments [11–14]. This exercise aims of familiarizing the user with the graphical interface and the structure of the layer, and to present other relevant information.

3.1.1 Data

The model will be build-up using the tools developed ad-hoc to facilitate the whole process. To that end, the following geometric entities are provided:

• Coordinates of the geometric entity (text

None additional geometric information is needed since the model will be created manually.

3.1.2 Model build-up

Once opened QGIS, load the IberGIS plugin by clicking on the icon , and the model generation window will appear (Fig. 2a). Please, enter the model name (GPKG Name) and a description. Then, define the location and the coordinate system using the Spatial Reference System Identifier (SRID), in this case 25830. After that, IberGIS asks for the QGIS project creation (Fig. 2b). This step is mandatory since it will automatically load the geopackage into the QGIS project

Fig. 2. Model generation window: (a) creation of the geopackage tab; (b) creation of the QGIS project tab.

The geometry of the facility is defined by 8 points that we have to load as Delimited Text Layer bye the menu Layer >> Add Layer >> Delimited Text Layer. Now, we have to select start editing () the layer called ‘Ground’ located in the group INPUT > IBER, which contains the main information of model geometry. Add Polygon Feature () by selecting the imported points and creating a polygon that represents the street part of the laboratory facility platform (Fig. 3). After finishing the geometry, the Feature Attribute table of ‘Ground’ layer will appear asking for the geometry properties. We can introduce a ‘cellsize’ of 0.2 m and a ‘custom_roughness’ of 0.015 s·m^-1/3 (Fig. 3a). Repeat this action to create the polygon that represents de grate inlet geometry and introducing a ‘cellsize’ and ‘custom_roughness’ of 0.1 m and 0.02, respectively (Fig. 3b). Finish editing mode to save the changes into ‘Ground’ layer. Note, ‘Enable Snapping’ () option will facilitate the creation of the model.

Fig. 3. ‘Ground’ layer creation: (a) generation of the platform geometry; (b) generation of the grate inlet geometry; (c) View of the attribute table of ‘Ground’ layer.

This geometry corresponds to the grate inlet called ‘Barcelona1’, commonly used in Barcelona city and already experimentally and numerically tested in this facility (e.g., [9,10,15–17]). Open the attribute table of ‘Ground’ layer to verify that, indeed, the geometry is properly saved together with the properties that we defined previously (Fig. 3c). Now, we can edit both the geometry and the properties of each geometrical feature of this layer.

We can hide or delete the auxiliary layer of points used to create the polygons of ‘Ground’ layer.

3.1.3 Hydraulic conditions

The hydraulic conditions of the model are a constant discharge (left side of the model), as inlet, and a critical flow regime (right side of the model), as outlet. To implement so, we have to open the Boundary conditions manager () and create a new by defining the ‘idval’ code (Fig. 4a). The ‘idval’ is a mandatory parameter, ‘name’ and ‘description’ are optional. IberGIS automatically will use this ‘idval’ as ‘Current scenario’. The manager window allows to store different inlet and outlet boundary conditions per scenario using the same ‘idval’ code.

Before creating the boundary conditions, especially those that uses a timeseries like as inlet condition defined by a hydrograph, we must create previously through Non visual object manager window (). Go to ‘Timeseries’ tab and create the inlet condition by defining an increasing discharge from 0 to 0.1 m³/s in 60 s (Fig. 4b).

The definition of the inlet/outlet condition can be carried out using the common options of QGIS by editing the layer called ‘Boundary conditions’. Select this layer and enable the editing mode (). Then, create a line () that define the inlet boundary condition in the left side, as it is shown in Fig. 4c. In the Feature Attribute table of Boundary conditions select both the ‘bcscenario’ (BC1), ‘boundary_type’ (INLET TOTAL DISCHARGE (SUB)CRITICAL) and the ‘timeseries’ (Inlet). Repeat this process by selecting the opposite side for the outlet condition and defining the ‘bcscenario’ and the ‘boundary_type’ as BC1 and OUTLET (SUPER)CRITICAL, respectively (Fig. 4d). Finish the edition mode and save it.

Fig. 4. Boundary conditions. (a) Creation of the current scenario. (b) Creation of the timeseries of the inlet conditions. (c) Implementation of the Inlet boundary condition. (d) Implementation of the Outlet boundary condition.

We are going to reproduce a grate inlet test; thus, we must define it by editing the ‘Inlet’ layer. Start editing () and create () the inlet by selecting the centroid of the grate inlet surface. A Feature Attribute table will appear and we have to fill it by selecting the ‘outlet_type’ as SINK, a ‘top_elev’ of 0 m, a ‘width’ of 0.26 m, a ‘length’ of 0.74 m, the ‘method’ as W_O (i.e., weir/orifice), a ‘weir_cd’ of 1.6, a ‘orifice_cd’ of 0.7, and a ‘efficiency’ of 100. The rest of parameters by default. Save the changes.

3.1.4 Mesh generation

The mesh generation is based on the information of ‘Ground’ layer, particularly on the ‘cellsize’ field. As we defined previously, the platform has a 0.2 m of element side length while the grate inlet area of 0.1 m. Go to Mesh manager () and create a new one. As the platform is fully horizontal, keep all values by default and press OK (Fig. 5a).

If we do so, the mesh generation process will be cancelled due to some fields of the ‘Ground’ layer must be properly defined, as ‘scs_cn’ (Fig. 5b). To solve this, go to the ‘Ground’ layer and Start editing. Add a value of 100' to the ‘scs_cn’ field of each feature (the platform is fully impervious). Then, save the changes and stop editing. Now, it is possible to create the mesh as mentioned before, showing the domain discretization plotted in Fig. 5c, with a finer mesh in the inlet area. Finally, we have to assign the boundary condition scenario to this mesh. To do so, we have to open the Boundary conditions manager (), select the scenario and ‘Save to mesh’ selecting Mesh1.

Fig. 5. Mesh generation: (a) definition of the mesh properties; (b) example of error message during the mesh generation; (c) view of the calculation mesh.

3.1.5 Run configuration

Once the mesh is generated, we must assign the boundary conditions to this mesh. To do so, go to the Boundary condition manager window, select the boundary condition ‘idval’ called BC1 and Save to mesh (Fig. 6a). This step is mandatory to warranty the proper assignation of the boundary conditions to the mesh, since the model can save different calculation meshes and boundary conditions to be used for different calculation scenarios.

Next, we have to go to ‘Options’ button () and configure the time parameters, results visualization and kind of simulation. In SWMM OPTIONS tab we have to define the ‘End time’ of 00:02:00 for the whole simulation, even if SWMM project is not defined (Fig. 6b). In such cases, Iber will take ‘End time’ as maximum simulation time. Also define a ‘Report step’ of 00:00:10. In tab IBER OPTIONS we have to define both writing times equal to 10 s, and the Hydrological process as No Rain and NO LOSSES (Fig. 6c). The results configuration (IBER RESULTS) by default except for Raster results options that must be defined with a ‘Cell size [m]’ of 0.1 and a Linear interpolation (Fig. 6d). Finally, as we do not have a SWMM project, we will simulate the urban drainage model considering only the inlets; thus, in IBER PLUGINS we must impose Only gullies (Fig. 6e). Accept the configuration.

Fig. 6. Run configuration: (a) assignation of the Boundary condition scenario to the current mesh; (b) definition of maximum simulation time (SWMM options); (c) Iber options definition; (d) Iber results definition; (e) Iber plugins definition.

To run the simulation, just click on ‘Execute model’ button ([[File:Sanz-Ramos_et_al_2025a_8684_Icon_Run.png|20px]), select the mesh (Mesh1) and the folder where the model will be run. After checking all data, the Iber-SWMM simulation starts. Once the simulation finish, the plugin asks for loading the results.

3.1.6 Results visualization

The results of the numerical models, SWMM and Iber, can be shown directly in QGIS. In this case, only the 2D results of Iber are available since none sewer network has been simulated through SWMM. Fig. 7 shows the map of flow depth and velocity at the end of the simulation. As expected, the inlet subtracts water from the model surface, affecting the hydrodynamics near the inlet location. The flow accelerates when it approaches to the inlet (Fig. 7b), especially in the X direction (Fig. 7c) while the velocity in the Y direction is almost null except near the inlet.

Fig. 7. Results at the end of the simulation: (a) flow depth; (b) flow velocity (modulus); (c) flow velocity in the X direction; (d) flow velocity in the Y direction.

3.2 Laboratory case: 'El Barrio'

This exercise will numerically replicate the Scientific Platform for Urban Runoff Testing located at the Center for Technological Innovation in Building and Civil Engineering (CITEEC) of the University of A Coruña. The experimental platform represents a perpendicular intersection of two streets and has a flat area of approximately 100 m2. The surface is connected to a drainage network consisting of four manholes, four pipes, one outlet point, and four inlets. It also has four ceramic tile roofs with variable slopes. Further information can be found in [1,18]

3.2.1 Data

The model will be build-up using the tools developed ad-hoc to facilitate the whole process. To that end, the following geometric entities are provided:

• GROUND_layer (shapefile)
• ROOF_layer (shapefile)
• INLETS_layer (shapefile)
• SWMM (*.ini and *inp)
• DEM (raster)
• Rainfall (text)

Each shapefile contains the database (*.dbf) with all data needed to compile the ‘Ground, ‘Roof’ and ‘Inlet’ layers. The SWMM model is also prepared and contains the sewer network information. The digital elevation model (DEM) is a raster file with ~4.4 cm pixel-size resolution, and represents the topography of the laboratory facility.

3.2.2 Model build-up

Once opened QGIS, load the IberGIS plugin by clicking on the icon , and the model generation window will appear (Fig. 8). Please, enter the model name (GPKG Name) and a description. Then, define the location and the coordinate system using the Spatial Reference System Identifier (SRID), in this case 25830.

Fig. 8. Model generation window. Create a new model or use the Example data model.

After a few seconds, the geopackage is generated with all features to build-up the model. First, we are going to import the SWMM model using the button “Import INP” (). The importation process of the SWMM model is automatic (Fig. 9a), and no user interaction is required.

Then, we import the ‘Ground’, ‘Roof’ and ‘Inlet’ layers through the “IberGIS” tools of the Processing Toolbox. In contrast with the SWMM file, to load the geometric entities file that define the two-dimensional computational domain, the user might select some field to be imported to particular fields of the target file. To import the ‘Ground’ layer, go to Processing Toolbox >> IberGIS > Import Ground Geometries, select ‘GROUND_layer’ and define the correspondence of the original to the target database (Fig. 9b). To facilitate this process, similar field names are used in the original file.

Continue with the ‘ROOF_layer’ through Processing Toolbox >> IberGIS > Import Roof Geometries, and define the correspondence of the original to the target database (Fig. 9c). It is important to highlight that if the field ‘outlet_code’ is used it must be properly defined according to the ‘custom_code’ of the ‘Junction’ layer of SWMM.

Finally, we import the ‘INLET_layer’ using the menu Processing Toolbox >> IberGIS > Import Inlet Geometries (Fig. 9d). It is worth noticing the target layer must be the one called ‘Inlet’ stored in the group ‘IBER’. Here we have to define properly the fields correspondence (similar field names are used in the original file).

The result of these import process is show in Fig. 9e. The computational domain is defined by a ground layer (grey polygon), a roof layer (ochre polygon), a inlets layer (yellow points), and the sewer network defined by junctions (blue points), conduits (blue lines) and an outfall (blue triangle).

Fig. 9. Generating the model domain. (a) Import SWMM files windows. (b) Import ‘Ground’ layer window. (c) Import ‘Roof’ layer window. (d) Import ‘Inlet’ layer window. (e) Model domain after the importation process.

3.2.3 Hydraulic and hydrological conditions

In this facility, the water enters from a rainfall simulator [18–20]. So, we have to define a hyetograph as a time series using the Non visual objects manager button . Here, we have first to create a Timeseries and, then, introduce the hyetograph provided in the models data (Rainfall.txt). Fig. 10a shows how to create the Timeseries and the configuration to define the hyetograph. Notice a hyetograph is defined as a constant rainfall (in mm/h) from the time when the rainfall value is first defined to the next time; thus, the last row is set as 0 mm/h to force the rain to stop. Otherwise, a constant rainfall intensity will be considered till the end of the simulation. Once the timeseries is defined, we have to create the ‘Hyetograph’ using the common tools of QGIS: select the ‘Hyetograph’ layer, enable the edition (), and create a new one () by clicking in the workspace. Immediately it will appear the attribute table creation window where we have only to select the timeseries (called “Rain”). A star-shaped icon () will appear indicating there is a hyetograph defined. Notice, if a unique hyetograph is defined in the model, Iber assumes uniform rainfall over the whole computational domain; whereas, if more the one hyetographs are defined, Iber uses the Thiessen polygons method [21,22] to distribute spatially the rainfall according to each hyetograph.

The unique boundary condition needed is an outlet located at the east of the model. To implement it, go to Boundary conditions manager (), create a new (Fig. 10b) one and assign as ‘Current scenario’. The manager window allows to store different inlet and outlet boundary conditions per scenario using the same ‘idval’ code. The definition of the outlet condition is carried out through the button Create boundary condition (). There we have to 1) select the line or lines that define de boundary conditions and 2) select the ‘Boundary type’ as “2D Outlet” with a “Supercritical/Critical” regime (Fig. 10c). This condition is saved in the layer ‘Boundary conditions’, which is stored in the group called ‘IBER’. It is important to highlight that any boundary condition must be implemented over a line of ‘Ground’ layer that belongs to a real boundary of the model. Hence, lines in contact with ‘Roof’ layer or inner lines must not be added as boundary condition. Abnormal results will appear in such case.

Fig. 10. (a) Definition of a hyetograph as a timeseries. (b) Definition of a boundary condition. (c) Boundary condition creation window.

3.2.4 Mesh generation

The meshing process must be always done in the latest step, once all model conditions are implemented. This case requires the utilisation of a digital elevation model (DEM), that we have to load using the common tools of QGIS (Layer >> Add Layer >> Add Raster Layer). We recommend to add the file surface_DEM.tiff into ‘BASE MAP’ group.

The mesh creation is carried out through the Mesh manager button (). There, the user can store different mesh configurations according to the mesh size defined in the field ‘meshsize’ of the ‘Ground’ layer, in combination with different boundary condition scenarios (Fig. 11a). In this case, the ‘meshsize’ is already defined as 0.1 m in ‘Ground’ layer; so, we have only to create it selecting the ‘surface_DEM’ raster layer in the Elevation section (Fig. 11b). We have also to introduce a mesh name (“Mesh1”), without spaces. The rest of parameters, by default (uncheck all Input data if it is checked). Press ‘Ok’ and the mesh will be generated (Fig. 11d) showing, besides the elements view for ‘Ground’ and ‘Roof’ layers, some information about the properties of the mesh (area and wrong normal).

Finally, we have to assign the boundary condition scenario to this mesh. To do so, we have to open again the Boundary conditions manager, select the scenario and ‘Save to mesh’ selecting Mesh1.

Fig. 11. (a) Mesh manager window. (b) Mesh properties. (c) Boundary condition creation window. (d) View of the computational mesh.

References

[1] E. Bladé, L. Cea, G. Corestein, E. Escolano, J. Puertas, E. Vázquez-Cendón, J. Dolz, A. Coll, Iber: herramienta de simulación numérica del flujo en ríos, Rev. Int. Métodos Numéricos Para Cálculo y Diseño En Ing. 30 (2014) 1–10. https://doi.org/10.1016/j.rimni.2012.07.004.

[2] M. Sanz-Ramos, E. Bladé, P. Oller, G. Furdada, Numerical modelling of dense snow avalanches with a well-balanced scheme based on the 2D shallow water equations, J. Glaciol. (2023) 1–17. https://doi.org/10.1017/jog.2023.48.