Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More fixes #431

Merged
merged 1 commit into from
Jun 6, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions source/a_releasenotes_general.rst
Original file line number Diff line number Diff line change
Expand Up @@ -8,9 +8,9 @@ June 5th, 2024

We have released several important new features, most importantly:

- Major improvements in the **water quality** module. It is now ready for use in real-world applications.
- Major improvements in the **water quality** module. It is now ready for use in real-world applications. See :ref:`How to use water quality <howto_use_water_quality>`.

- **Vegetation** can now also be used in the 1D domain (in open channels)
- **Vegetation** can now also be used in the 1D domain (in open channels). See :ref:`How to use vegetation <a_how_to_vegetation>`.

- Improvements in the tools to :ref:`vector_data_importer` to your schematisation make these tools even more powerful and versatile.

Expand Down
10 changes: 5 additions & 5 deletions source/d_vegetation_howto.rst
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ Choosing the right method for schematising vegetation

3Di offers various methods for taking the effects of vegetation into account. Choosing the right method for schematising vegetation depends on the application, the model objective and data availability. Each use case is different and asks for some expert judgement. We can however provide some general guidelines.

* **Sheet flow** If the flow depth is only a few millimeters to centimeters (e.g. sheet flow from hills), modelling vegetation will not have additional benefits. Using only bottom roughness (Manning or Chezy) will be sufficient.
* **Sheet flow** If the flow depth is only a few millimeters to centimeters (e.g. sheet flow from hills), modelling vegetation will not have additional benefits. Using only bottom roughness (Manning or Chézy) will be sufficient.

* **Low vegetation** Low vegetation is vegetation that has the height of the underlying bottom roughness. Generally, as soon as such an area gets wet, it is submerged and the height of the vegetation is in the same order of magnitude as the vertical accuracy of the DEM. Under these conditions it is advantageous to model the vegetation as a bottom roughness, using Manning or Chézy values. This method is available for 1D and 2D flow.

Expand All @@ -32,22 +32,22 @@ Choosing the right method for schematising vegetation
Vegetation drag parameter values
--------------------------------

If you want to use vegetation drag, you need to supply three input parameters to 3Di: *vegetation height*, *vegetation stem count*, *vegetation stem diameter*, and *vegetation drag coefficient*; see :ref:`vegetation_drag` for details. It can be a challenge to choose the correct values for these parameters. Even in acadamic research, the incorporation of vegetational effects in large scale hydrodynamic models is still a quite new, so there is not yet a large body of literature to draw from when setting these parameters.
If you want to use vegetation drag, you need to supply three input parameters to 3Di: *vegetation height*, *vegetation stem count*, *vegetation stem diameter*, and *vegetation drag coefficient*; see :ref:`vegetation_drag` (2D) or :ref:`cross_section_location` (1D) for details. It can be a challenge to choose the correct values for these parameters. Even in acadamic research, the incorporation of vegetational effects in large scale hydrodynamic models is still a quite new, so there is not yet a large body of literature to draw from when setting these parameters.

The correct values for the vegetation parameters depend on the plant species, its growth stage and the season. The stem diameter, the height and the number of stems can be measured relatively easy, at least, compared to the drag coefficient. In the last decade, more and more measurements have been performed to define these values. Unfortunately, there is not a general overview of these values per species. :cite:t:`VargasLuna2015` can serve as a starting point. In the formulation in 3Di, it is generally OK to start with a drag coefficient set to 1. Depending on the data you have of the area, it allows a more detailed calibration and tuning to the local conditions. The other parameters can be derived from land use maps and ecological maps.

Vegetation drag can only be used with friction type 'Chezy', because the vegetation formulation (initially introduced by Baptist 2005) uses Chezy.
Vegetation drag can only be used with friction type *Chézy*, because the vegetation formulation (initially introduced by Baptist 2005) uses Chézy.

Example: Biesbosch
------------------
To illustrate how vegetation drag parameters can be chosen for your use case, we will take the Biesbosch as an example. The Biesbosch is an estuary in the west of the Netherlands, near Rotterdam. A vegetation map is available from the Dutch national water management authority Rijkswaterstaat, see their `viewer < https://maps.rijkswaterstaat.nl/geoweb55/index.html?viewer=Vegetatielegger>`. This data can be added to your 3Di Modeller Interface project as an ArcGIS REST service, using this link: https://geo.rijkswaterstaat.nl/arcgis/rest/services/GDR/rws_vegetatielegger/FeatureServer .
To illustrate how vegetation drag parameters can be chosen for your use case, we will take the Biesbosch as an example. The Biesbosch is an estuary in the west of the Netherlands, near Rotterdam. A vegetation map is available from the Dutch national water management authority Rijkswaterstaat, see their `viewer < https://maps.rijkswaterstaat.nl/geoweb55/index.html?viewer=Vegetatielegger>`_. This data can be added to your 3Di Modeller Interface project as an ArcGIS REST service, using this link: https://geo.rijkswaterstaat.nl/arcgis/rest/services/GDR/rws_vegetatielegger/FeatureServer .

.. figure:: image/a_vegetation_data_example_biesbosch.png
:scale: 80%

Vegation map of the Biesbosch (Rijkswaterstaat vegetatielegger viewer).

The vegetation dataset has nine classes. An explanation of these classes is given in the `Beeldenboek vegetatiebeheer grote rivieren <https://open.rws.nl/overige-publicaties/2020/beeldenboek-vegetatiebeheer-grote/>`. Based in this information, we can make an educated guess for the vegetation parameters for these classes, summarized in this table:
The vegetation dataset has nine classes. An explanation of these classes is given in the `Beeldenboek vegetatiebeheer grote rivieren <https://open.rws.nl/overige-publicaties/2020/beeldenboek-vegetatiebeheer-grote/>`_. Based in this information, we can make an educated guess for the vegetation parameters for these classes, summarized in this table:

.. list-table:: Educated guesses for vegetation parameters for the vegetation classes in the Biesbosch example dataset
:widths: 20 30 10 10 15 20
Expand Down
2 changes: 1 addition & 1 deletion source/h_schema_300.rst
Original file line number Diff line number Diff line change
Expand Up @@ -160,7 +160,7 @@ What are the advantages of changing the database schema?

- Make exchange type (isolated/connected/embedded) an attribute of connection node instead of manhole, so that it is no longer necessary to place manholes purely to set the exchange type.

- A cleaner database schema, including:
- A cleaner database schema, including

- Remove the "v2_" prefixes in all table names

Expand Down
Loading