See also presentation prepared by Unknown User (alex) for this meeting on the following page: Cross-Section.
People present on the meeting:
Fedor Baart
Unknown User (logch_o)
Unknown User (alex)
Marc van Dijk
Micha Werner
Govert.Verhoeven@deltares.nl
Notes from the last internal user meeting related to Cross Section editor:
Cross section data
A user should be able to edit cross section data in the following ways:
- typing in Width vs Height W(H)
- typing in Height vs offset Y(Z)
- choosing a default shape and modifying its dimension (urban / rural)
Markers
For now 3 markers will be added used for bottom, left and right bank with a possibility to extend. In the Eurotask project "Integrated catchment modeling toolkit" people defined a standard format for cross section data (similar to the Mike11 approach). This format defines the following markers:
- main channel
- bank (small part in between channel and floodplain)
- floodplain
- extremity
- limit of conveyance and storage (look at sobek RE)
current Sobek uses "flow width" and "total width" to distinguish between the water bearing part of the river and the part that only serves as storage area.
Map centered approach should be optional
Typical data in a project may consist of cross sections and chainage data. References to geographic coordinates may be missing altogether. (chainage is the cross section offset along a branch). The user should therefore not be required to always provide a map and work with that. The Isis model provides an approach to work with this type of data only. Mark has a working version of Isis.
Logical and physical coordinate of the cross-sections along the branch. If map is defined - logical will be used as a fist estimate.
Library of roughness classes
Using a library of common roughness types is appreciated. Bottomtype should not be used as name but instead "roughness class" or "friction class". A cross section should initially have two roughness classes along its length:
Manning's n |
Name |
|---|---|
0.001 |
stream |
0.01 |
floodplain |
When the user updates the friction/roughness for a class it should change in all profiles where it's in use. The scope of this change should be contained within the project.
Cross section metadata
Cross sections may change over time (they are periodically updated with new measurements). Therefore it is important to have some "versioning system" for cross sections. At least a cross section used in a calculation should have some meta data attached to it so you know who made it and when it was made.
Tasks
Micha will provide some tables with common friction parameters for river modeling.
Onno will ask Paul for an example of a typical dataset for river modeling (Adige river)
Gena and Fedor will organize "pizza cursussen" to enable colleagues to provide input for the new user interface
3 Comments
Unknown User (alex)
Edward was telling an user story: during the calibration process you would like to select a couple (or range) of cross-sections to up- or downgrade the roughness to meet the measurements (wave-shape).
Unknown User (logch_o)
Jan Noort suggests to start with width vs height cross section definition instead of YZ (most simple and commonly used withing sobek)
Unknown User (alex)
Frictions in Sobek
