See also presentation prepared by ~alex Unknown User (alex) for this meeting on the following page: Cross-Section.
People present on the meeting:
Fedor Baart
~logch Unknown User (logch_o)
~alex Unknown User (alex)
Marc van Dijk
Micha Werner
Govert.Verhoeven@deltares.nl
...
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.
...
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.
...
| Panel | |||||
|---|---|---|---|---|---|
| |||||
|
