--- title: "2D Simulations - Domain Details Sub-tab | Technical Reference" slug: "2d-simulations-domain-details-sub-tab" description: "Learn about the domain details sub-tab to add grid data, topography, shapefiles and more. " tags: ["running simulations", "2D modelling"] updated: 2022-08-07T15:06:05Z published: 2022-08-07T15:06:05Z canonical: "help.floodmodeller.com/2d-simulations-domain-details-sub-tab" stale: true --- > ## Documentation Index > Fetch the complete documentation index at: https://help.floodmodeller.com/llms.txt > Use this file to discover all available pages before exploring further. # 2D Simulations - Domain Details Sub-tab ![2DSimulationsimagesddimage001.png](https://cdn.document360.io/5074bc26-a9ef-4bf4-b1de-a5c6ce628aca/Images/Documentation/2DSimulationsimagesddimage001.png) The underlying topography must be defined via a grid data file. ![2DSimulationsimagesddimage002.png](https://cdn.document360.io/5074bc26-a9ef-4bf4-b1de-a5c6ce628aca/Images/Documentation/2DSimulationsimagesddimage002.png) Any grid data loaded in the **Layers** panel of Flood Modeller can be selected (to highlight it) and then dragged into the **Topography** box. Alternatively, the **Add** button can be used to browse to the relevant file in standard windows file explorer. If your area has been set up via a line shapefile and the associated elevation data set up via a point shapefile, these can be entered directly into the **Topography** field using a “|” to separate the file paths, e.g. C:\2D_models\GIS\my_line_shapefile.shp|C:\2D_models\GIS\my_point_shapefile.shp Alternatively, the **Add Z line** button enables you to browse to a line shapefile and point shapefile. Once the **Topography** box is populated with files, the green directional arrows move the highlighted file up or down the list of available files. :::(Error) (Important Note:)

At the start of a 2D simulation, the solver will generate a composite ground grid from the layers you have specified in the topography table. The data in this table is read from top to bottom and therefore data from layers in the lower rows will overwrite data from layers in higher rows.

If you want to check the composite grid your simulation is using, ensure the Write check grids checkbox is ticked (on the Domains> Outputs tab of the 2D interface). The 2D solver will then write out the composite grid it uses to the check grid entitled output.chk.zcen.asc (furthermore, the check grid output.chk.zmod.asc shows only the cells that have been modified from your main DTM later, i.e. the top row in the topography table).

::: The tool now accepts the following formats for topography data: * ASCII Grid (ASC) * GeoTIFF (TIF) * Binary Grid (FLT) * ESRI Shapefile (SHP) The computational area and time step details need to be entered next. When a grid data file has been selected for the topography (above), the parameters will be automatically filled based on this data, but these can be edited. Note that for the ADI 2D solver, it is recommended that the **Time Step** (in seconds) should be between ¼ and ½ of the **Grid Size** (in metres), i.e. for a 5-metre grid, the time step should be between 5/4 and 5/2 seconds. A **Reset** button is given on this panel to reset the parameters based on the underlying grid data. Alternatively, new parameters can be loaded into the tool from a shapefile: click the **Load** button to browse to the relevant file. ![2DSimulationsimages2Dcomputationalarea.jpg](https://cdn.document360.io/5074bc26-a9ef-4bf4-b1de-a5c6ce628aca/Images/Documentation/2DSimulationsimages2Dcomputationalarea.jpg) An active area must be added: this can be selected from the **Layers** panel of Flood Modeller and dragged into the **Active Area** field, or the browse button can be used to search for and select the file. A deactivation area can also be added; this allows you to enter a second shapefile (residing inside the active area) where computations will not be carried out, i.e. to create a “hole” in the active area. Drag a shapefile loaded in the **Layers** panel of Flood Modeller into the **Deactivation** field, or use the browse button to locate the required file. Note that polylineZ shapefiles can also be used. Details of the roughness can be entered into the tool in the roughness data section of the tab. To specify uniform roughness over the entire active area, a **Default Roughness Value** can be set. This will default at 0.1 but this value is editable. The default **Roughness Law** is “Manning”. Click on the drop-down box provided to adjust this to “Chezy” if required. ![2DSimulationsimagesddimage004.png](https://cdn.document360.io/5074bc26-a9ef-4bf4-b1de-a5c6ce628aca/Images/Documentation/2DSimulationsimagesddimage004.png) Roughness grid files can also be added to describe spatially varying roughness. Click **Add** to add a new roughness file and the following window will appear: ![2DSimulationsimagesddimage005.png](https://cdn.document360.io/5074bc26-a9ef-4bf4-b1de-a5c6ce628aca/Images/Documentation/2DSimulationsimagesddimage005.png) Choose a file type from the drop-down box provided and enter the filename and path directly or click to browse to the relevant file. Click **OK** to add the file to the table. Alternatively, click to highlight a file loaded in the **Layers** panel of Flood Modeller and drag it into the table. This will bring up the above window but automatically filled with the filename and file type. Note there are two options for shapefiles, MasterMap shapefiles and Roughness polygons, so the file type should be double-checked if dragging a file in from the **Layers** panel. If a MasterMap shapefile is added, a Lookup Table (.fric file) must also be provided. Type the location directly into the appropriate field or browse to the file in the usual way. Multiple roughness grid files can be added to the table. To **Edit** or **Remove** a file, click on the appropriate button to the right-hand side of the table. The directional arrows to the left of the table allow you to move a highlighted file up or down the list. As with the topography layers, roughness grids will be read from top to bottom in the table, and therefore data from layers in lower rows will overwrite data from layers in higher rows.