...
To find out wat users expect from a new UI for Sobek a colleagues working at Deltares was interviewed last thursday. The experiences derived from interviews like these will be used to implement functionality that will satisfy most users (80/20 rule).
Jan Jaap is bursting with ideas. So, it would be very handy to catch up frequently and to share the ideas.
Here a brief summery:
Use of Cross-Section
- To navigate through cross-sections should be easier.
- The overview/maintenance of the cross-sections should be much better.
- Possibility to make sets (collections) of cross-sections to switch on/of (possibly with the same locations).
...
- Beside y-z info also geographic coordinates.
- Adjustment of lowest point / connection point river polygon.
- Detailed info of Cross-Section higher then grid level not used for calculations (ex. dike information): a waste of important information.
- Problem if an (little) island is part of the cross-section.
Views
- Length / placements of cross-section on the map (a perpendicular from/ across the river)
- Londiguanal section of the system for waterlevels (output)
- Multiple crossections cross-sections in one view
Comparisons
- There's a strong desire for a good comparison of cross-sections (and londiguanal sections) for different situations: two measures based on cross-sections, sediment changes in cross-section, waterlevel(s) etc.
...
- Program computes mud volume for dredgers (two different sets of cross-sections: this situation and optimal dredged situation)
- Program computes an optiomal optimal cross-section (depth, not width?)
