Difference between revisions of "ReleasePlanKalypso220"
From KalypsoDev
Gernotbelger (Talk | contribs) (→Roadmap) |
Gernotbelger (Talk | contribs) (→RRM (NA)) |
||
(31 intermediate revisions by one user not shown) | |||
Line 1: | Line 1: | ||
− | ''Kalypso - Release Plan for Version 2.2'' | + | ''Kalypso - Release Plan for Version 2.2'' |
− | + | ==Kalypso Platform== | |
− | + | ||
− | + | ||
:Items that improve Kalypso in general. | :Items that improve Kalypso in general. | ||
− | + | ---- | |
+ | ===Proposed items=== | ||
+ | |||
+ | ---- | ||
+ | ===Committed items=== | ||
:Leverage the full potential of the eclipse 3.4 command framework | :Leverage the full potential of the eclipse 3.4 command framework | ||
− | :: | + | ::Map context and appropriate commands have been defined; all standard map commands rely on this mechanism. |
+ | ::Map-Toolbars have been reworked, no more tool item flicker | ||
+ | |||
+ | :Speed up map drawing | ||
+ | ::All layers get now individually buffered, so some operations (like enabling a single layer or changing the selection) are now lightning fast. | ||
:I18N | :I18N | ||
− | ::General i18n of | + | ::General i18n of most modules |
− | :: | + | ::Basic translations for English and German available |
− | + | :Accessing GML data | |
+ | ::Some large GML files (i.e. 1d2d results) are now gzipped by default, greatly reducing hard disk space consumption | ||
− | + | ---- | |
− | + | ===Deferred Items=== | |
− | + | ||
− | + | ||
− | + | ||
:Memory handling | :Memory handling | ||
::Kalypso consumes lots of memory, which prohibits to work with very large models. Also some known memory leaks should be fixed as well (same applies to UI-handles). | ::Kalypso consumes lots of memory, which prohibits to work with very large models. Also some known memory leaks should be fixed as well (same applies to UI-handles). | ||
− | |||
− | : | + | :Style editing |
− | :: | + | ::Enable style editing in all maps |
− | + | ||
− | + | :WMS(/WFS/WCS) | |
+ | ::Give a suggestion list of available web servers for data to process on (???). Access to Catalogue-Services should be possible. | ||
+ | |||
+ | ---- | ||
+ | ---- | ||
+ | ==Consumability / Reliability== | ||
This work will make it easier for users to get Kalypso, install it on their systems, and configure it for their use. It will also enhance the error handling and reporting mechanisms to make it easier to service Kalypso in the field. | This work will make it easier for users to get Kalypso, install it on their systems, and configure it for their use. It will also enhance the error handling and reporting mechanisms to make it easier to service Kalypso in the field. | ||
− | + | ---- | |
+ | ===Proposed items=== | ||
+ | :None at this time | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ===Committed items=== | ||
+ | :Make downloading and testing Kalypso still more easy for new users | ||
+ | ::Basic configuration is easier,most default settings are already defined | ||
+ | ::On first startup, the user is asked for the location of the workspace | ||
+ | |||
+ | ---- | ||
+ | ===Deferred Items=== | ||
:Update-Mechanism | :Update-Mechanism | ||
::Use Eclipse 3.4 Update mechanism in order to easily update Kalypso. | ::Use Eclipse 3.4 Update mechanism in order to easily update Kalypso. | ||
:Bug/Feature-Reports | :Bug/Feature-Reports | ||
− | ::Integrate report mechanism directly into Kalypso UI. | + | ::Integrate report mechanism directly into Kalypso UI. |
− | + | :Make downloading and testing Kalypso still more easy for new users | |
− | : | + | ::Customized download page at sourceforge? |
+ | ::Review install guide(s) | ||
+ | ::Auto-Dialog for required preference customization at first start of Kalypso | ||
− | + | ---- | |
− | + | ---- | |
− | + | ==1D/2D== | |
− | + | ---- | |
+ | ===Proposed items=== | ||
+ | :none at this time | ||
− | === | + | ---- |
+ | ===Committed items=== | ||
− | + | ====preprocessing==== | |
− | + | ||
− | : | + | :MAP - Infobutton |
− | :: | + | :: Infobutton for roughness theme should display the roughness class (and its current values) (should replace the class-labels on the map?) |
− | : | + | :Delete unused widgets |
− | :: | + | ::widgets "Ein Element entfernen", "ein Element erzeugen", "ein Element editieren" (Schere, Plus, Bleistift) are without function and have to be deleted |
− | + | ====results==== | |
− | + | ||
− | + | :Improve result processing performance | |
+ | ::The 1d2d tin results are directly processed to disk, improving memory consumption and performance of result processing. | ||
− | + | ---- | |
− | + | ===Deferred Items=== | |
− | + | ====preprocessing==== | |
− | + | ||
− | : | + | :Roughness classes update |
− | :: | + | ::Update usable roughness classes with literature source |
− | : | + | :Concave polygons |
− | :: | + | ::Validation check for polygons prohibits drawing of concave polygons, because first node for concavity is not allowed to be drawn. Better just prohibit FINISHING a self cutting polygon. |
− | : | + | : Reduce number of layers in maps |
− | :: | + | :: Combine themes '2dElemente' and 'Rauheiten' |
+ | :: ... | ||
− | : | + | :MAP - Infobutton |
− | :: | + | :: Infobutton for the node theme should display the node's elevation |
− | : | + | :Net editing |
− | :: | + | ::The user experience with the net can be improved in many ways; for example refinements of the net are needed as well as integration of the GAJA3D toolkit. Management of net changes between calculations (consider restart!). |
− | + | :Use improved raster data handling for terrain models | |
− | + | ||
− | : | + | |
− | + | ||
:2D net import | :2D net import | ||
::Allow the user to import a shape(z) file that represents the mesh geometry. | ::Allow the user to import a shape(z) file that represents the mesh geometry. | ||
− | |||
− | |||
− | |||
:Triangulation of discretisation | :Triangulation of discretisation | ||
− | :: Enable processing of terrain TIN in preprocessing to visualise problematic parts of the mesh. At the moment the TIN is only created, if at least on calculation step is done successfully. Besides the problem occurs, that the terrain TIN can only be visualised in the result | + | :: Enable processing of terrain TIN in preprocessing to visualise problematic parts of the mesh. At the moment the TIN is only created, if at least on calculation step is done successfully. Besides the problem occurs, that the terrain TIN can only be visualised in the result-map. It should become part of the fenet-map. |
:1D Preprocessing | :1D Preprocessing | ||
Line 112: | Line 129: | ||
::Give a possibility to synchronize changes of models in WSPM with model data (terrain.gml) in 1D/2D, if e.g. user changes active flow region etc. | ::Give a possibility to synchronize changes of models in WSPM with model data (terrain.gml) in 1D/2D, if e.g. user changes active flow region etc. | ||
− | two-directions 1D-control structure | + | :two-directions 1D-control structure |
::Support the generation of wwQ-relationships for both flow directions seperatly (changes in GUI and calculation core) | ::Support the generation of wwQ-relationships for both flow directions seperatly (changes in GUI and calculation core) | ||
:activation of control structures | :activation of control structures | ||
− | ::Add a possibility to switch on/off individual control structures in a calculation unit or generally. Point is just to be able to switch off a control structure without deleting the data set. | + | ::Add a possibility to switch on/off individual control structures in a calculation unit or generally. Point is just to be able to switch off a control structure without deleting the data set. |
− | : | + | :Editing tools for polygons |
− | :: | + | ::Enable snapping for polygon drawing (e.g. for roughness polygons) |
+ | ::Enable possibility of adding a node to the linear ring or moving a particular node of the linear ring | ||
− | : | + | :Pasting into time series |
− | :: | + | ::Enable pasting into the table of a boundary condition |
− | : | + | :Improve Bandgenerator |
− | :: | + | ::Connection lines between 1st and 3rd boundary lines are straight. They should connect equal distant distributed nodes in between. |
− | : | + | :Import timeseries from KalypsoHydrology |
− | :: | + | ::Import of timeseries data that was processed/ calculated in KalypsoHydrology (i.e. directly show existing results in zml-browser) |
− | + | ====processing==== | |
− | + | ||
− | : | + | :Detailed definition of URFC |
− | :: | + | ::Enable the detailed setting of the under relaxation factor for each time step in a very comfortable way. This feature could extremely speed up the calculation speed. |
− | : | + | :Manual calculation interruption |
− | ::Enable | + | ::Enable manual interruption of calculation without total abruption, i.e. results processed so far should be interpreted |
− | : | + | :Show chosen timeseries |
− | :: | + | ::Display chosen timeseries in control panel graphically |
− | : | + | :Support other calculation cores |
− | :: | + | ::Other calculation cores (such as RMA2 and RMA10, Hydro-AS) should be supported, based on the same mesh-data as RMA10S (see KalypsoProdcutRoamdmap2_1CalcCores). |
− | + | :Different junction approaches | |
+ | ::Enable momentum controlled, energy controlled and water stage controlled 1D-junctions | ||
− | : | + | ====results==== |
− | :: | + | |
+ | :Overwrite existing results | ||
+ | ::Overwrite existing results for setting in timeseries results view. Problem is, that user has to set up nodes again after each new calculation. Additionally take Profile kilometer as default name. | ||
+ | |||
+ | :Improve error messages and log messages | ||
+ | ::Improve error messages from the calculation core (Errors, warnings, hints, direkt access to nodes etc., iteration table, activation/deactivation of nodes/elements ... ) | ||
:Result Post Processing | :Result Post Processing | ||
::Allow selective and/or lazy result processing. Improve result visualization (i.e. 3D, dynamic, compare). Also new types of results(-views) should be considered (i.e. dynamic flow pathes, ...). | ::Allow selective and/or lazy result processing. Improve result visualization (i.e. 3D, dynamic, compare). Also new types of results(-views) should be considered (i.e. dynamic flow pathes, ...). | ||
+ | :: Importing results from external calculations would be nice. | ||
− | : | + | :Marsh-vectors |
− | :: | + | ::Enable marsh water depth display and Marsh-vector display in plan view. (Let's have a deeper discussion about, what could be done to understand Marshing-algorithm better, too). ''This task is very important, as it can extremely increase the stability of the model.'' Following should be visualizable optionally: Marsh depth/slot depth, Marsh vectors, Marsh water depth results, effective porosity results, type of active Marsh range ... |
− | : | + | :Active/Inoperative elements |
− | + | ||
− | + | ||
− | + | ||
:: Enable the visualisation of boundary lines of the active flow region. Besides display the active/ inoperative elements at a particular run | :: Enable the visualisation of boundary lines of the active flow region. Besides display the active/ inoperative elements at a particular run | ||
− | : | + | :Line checks |
::Introduce result evaluation at cross section definitions in 2D meshs. Also integrate them for evaluation of longitudinal sections through 2D-mesh parts for calculation of Q and average v. | ::Introduce result evaluation at cross section definitions in 2D meshs. Also integrate them for evaluation of longitudinal sections through 2D-mesh parts for calculation of Q and average v. | ||
− | : | + | :Longitudinal section setup |
::Enable longitudinal section setup, i.e. be able to set up connections of longitudinal sections of base units in coupled units. | ::Enable longitudinal section setup, i.e. be able to set up connections of longitudinal sections of base units in coupled units. | ||
Line 171: | Line 192: | ||
::Enable additional loading of time series to results graphics to be able (e.g. for calibration) | ::Enable additional loading of time series to results graphics to be able (e.g. for calibration) | ||
− | + | ====completely new features==== | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | ==== | + | |
:IMPORTANT: | :IMPORTANT: | ||
Line 183: | Line 198: | ||
:Loading of files | :Loading of files | ||
− | ::Enable loading of | + | ::Enable loading of external control files (r10) |
− | : | + | :Enable side friction e.g. for walls |
:: Make use of the shore line friction functionality of RMA·Kalypso, that already exists | :: Make use of the shore line friction functionality of RMA·Kalypso, that already exists | ||
Line 194: | Line 209: | ||
::Add possibility to introduce 2D control structures as weirs, sluice gates etc. | ::Add possibility to introduce 2D control structures as weirs, sluice gates etc. | ||
− | : | + | :Enlarge cstrc-possibilies |
::Add additional calculation possibilities for weirs | ::Add additional calculation possibilities for weirs | ||
− | : | + | :Channel profiles (GEO-approach) |
::Enable 1D-sections with original RMA10S-definition method (geometric approach) | ::Enable 1D-sections with original RMA10S-definition method (geometric approach) | ||
− | : | + | :Parameter settings |
::Set up general calculation core parameters like memory settings, inflow element number etc. | ::Set up general calculation core parameters like memory settings, inflow element number etc. | ||
Line 207: | Line 222: | ||
:Inflow elements | :Inflow elements | ||
− | ::More refinement of inflow elements, i.e. differ between inflow elements with or without predefined inflow direction (momentum influence). | + | ::More refinement of inflow elements, i.e. differ between inflow elements with or without predefined inflow direction (momentum influence). Introduce inflow groups (deep cogging with calculation core, see other road map). |
− | : | + | :Widening/contraction losses |
− | :: | + | ::Introduce feature for consideration of widening and contraction losses in 1D approach (deep cogging with calculation core, see other road map). |
− | : | + | :Local losses |
− | :: | + | ::Introduce feature to consider local losses (deep cogging with calculation core, see other road map) |
− | : | + | :Simplified bridges/weirs |
::Develope feature to consider bridges/weirs in simple form as local loss with formula of Cidarer (deep cogging with calculation core, see other road map) | ::Develope feature to consider bridges/weirs in simple form as local loss with formula of Cidarer (deep cogging with calculation core, see other road map) | ||
− | ==== | + | ---- |
+ | ---- | ||
+ | |||
+ | ==WSPM== | ||
+ | |||
+ | ---- | ||
+ | ===Proposed items=== | ||
:None at this time | :None at this time | ||
− | === | + | ---- |
− | : | + | ===Committed items=== |
+ | :Improve performance | ||
+ | ::Displaying the profiles in the map has greatly improved | ||
− | === | + | ---- |
+ | ===Deferred Items=== | ||
+ | :Distinguish profiles from different strands/water bodies | ||
− | + | :Enhance visualization of results | |
+ | ::Show waterlevels in profiles, show multiple results in one chart, ... | ||
+ | ::Show more layers in length-section chart | ||
:Profile Interpolation | :Profile Interpolation | ||
Line 236: | Line 263: | ||
:Synchronisation Map - Chart | :Synchronisation Map - Chart | ||
− | |||
− | |||
− | |||
− | |||
− | |||
:Support for 'Energieverlust' | :Support for 'Energieverlust' | ||
Line 246: | Line 268: | ||
:Workflow for WSPM | :Workflow for WSPM | ||
− | :Profile DGM Extraction | + | :Profile DGM Extraction |
− | + | ---- | |
− | + | ---- | |
− | ==== | + | ==RRM (NA)== |
− | + | ||
− | === | + | ---- |
+ | ===Proposed items=== | ||
+ | :None at this time | ||
+ | ---- | ||
− | + | ===Committed items=== | |
:None at this time | :None at this time | ||
− | === | + | ---- |
+ | ===Deferred Items=== | ||
:workflow support | :workflow support | ||
::Theoretical workflow already exists. Workflow support for RRM is really necessary | ::Theoretical workflow already exists. Workflow support for RRM is really necessary | ||
− | :statistical analysis Add statistical analysis functions | + | :statistical analysis Add statistical analysis functions |
− | + | ---- | |
− | + | ---- | |
− | + | ==Flood== | |
− | === | + | ---- |
+ | ===Proposed items=== | ||
:None at this time | :None at this time | ||
− | === | + | ---- |
+ | ===Committed items=== | ||
:None at this time | :None at this time | ||
− | + | ---- | |
− | : | + | ===Deferred Items=== |
+ | :Add filter functions to raster data processing | ||
+ | ::Filter out small islands or ponds | ||
+ | ::Only consider main water body | ||
+ | ::... | ||
− | + | ---- | |
+ | ---- | ||
+ | ==Risk== | ||
− | ====Committed items | + | ---- |
+ | ===Proposed items=== | ||
+ | :None at this time | ||
+ | |||
+ | ---- | ||
+ | ===Committed items=== | ||
:None at this time | :None at this time | ||
− | ==== | + | ---- |
− | + | ===Deferred Items=== | |
:Additional outputs | :Additional outputs | ||
− | :: | + | ::Generate more 'in between results' during risk calculation as damages etc. |
:Additional outputs | :Additional outputs | ||
− | :: | + | ::Export grids as shapes. |
− | + | :Single damage calculation | |
− | : | + | ::Enable calculation of damage for single flood events |
− | ::Enable calculation of damage for single flood events | + | |
− | + | ||
− | + | ||
− | + |
Latest revision as of 16:05, 10 October 2009
Kalypso - Release Plan for Version 2.2
Contents |
[edit] Kalypso Platform
- Items that improve Kalypso in general.
[edit] Proposed items
[edit] Committed items
- Leverage the full potential of the eclipse 3.4 command framework
- Map context and appropriate commands have been defined; all standard map commands rely on this mechanism.
- Map-Toolbars have been reworked, no more tool item flicker
- Speed up map drawing
- All layers get now individually buffered, so some operations (like enabling a single layer or changing the selection) are now lightning fast.
- I18N
- General i18n of most modules
- Basic translations for English and German available
- Accessing GML data
- Some large GML files (i.e. 1d2d results) are now gzipped by default, greatly reducing hard disk space consumption
[edit] Deferred Items
- Memory handling
- Kalypso consumes lots of memory, which prohibits to work with very large models. Also some known memory leaks should be fixed as well (same applies to UI-handles).
- Style editing
- Enable style editing in all maps
- WMS(/WFS/WCS)
- Give a suggestion list of available web servers for data to process on (???). Access to Catalogue-Services should be possible.
[edit] Consumability / Reliability
This work will make it easier for users to get Kalypso, install it on their systems, and configure it for their use. It will also enhance the error handling and reporting mechanisms to make it easier to service Kalypso in the field.
[edit] Proposed items
- None at this time
[edit] Committed items
- Make downloading and testing Kalypso still more easy for new users
- Basic configuration is easier,most default settings are already defined
- On first startup, the user is asked for the location of the workspace
[edit] Deferred Items
- Update-Mechanism
- Use Eclipse 3.4 Update mechanism in order to easily update Kalypso.
- Bug/Feature-Reports
- Integrate report mechanism directly into Kalypso UI.
- Make downloading and testing Kalypso still more easy for new users
- Customized download page at sourceforge?
- Review install guide(s)
- Auto-Dialog for required preference customization at first start of Kalypso
[edit] 1D/2D
[edit] Proposed items
- none at this time
[edit] Committed items
[edit] preprocessing
- MAP - Infobutton
- Infobutton for roughness theme should display the roughness class (and its current values) (should replace the class-labels on the map?)
- Delete unused widgets
- widgets "Ein Element entfernen", "ein Element erzeugen", "ein Element editieren" (Schere, Plus, Bleistift) are without function and have to be deleted
[edit] results
- Improve result processing performance
- The 1d2d tin results are directly processed to disk, improving memory consumption and performance of result processing.
[edit] Deferred Items
[edit] preprocessing
- Roughness classes update
- Update usable roughness classes with literature source
- Concave polygons
- Validation check for polygons prohibits drawing of concave polygons, because first node for concavity is not allowed to be drawn. Better just prohibit FINISHING a self cutting polygon.
- Reduce number of layers in maps
- Combine themes '2dElemente' and 'Rauheiten'
- ...
- MAP - Infobutton
- Infobutton for the node theme should display the node's elevation
- Net editing
- The user experience with the net can be improved in many ways; for example refinements of the net are needed as well as integration of the GAJA3D toolkit. Management of net changes between calculations (consider restart!).
- Use improved raster data handling for terrain models
- 2D net import
- Allow the user to import a shape(z) file that represents the mesh geometry.
- Triangulation of discretisation
- Enable processing of terrain TIN in preprocessing to visualise problematic parts of the mesh. At the moment the TIN is only created, if at least on calculation step is done successfully. Besides the problem occurs, that the terrain TIN can only be visualised in the result-map. It should become part of the fenet-map.
- 1D Preprocessing
- The 1D preprocessing (aka determination of polynomials) should be possible without WSPM. For that, a profile management tool and also handling of initial restart data is needed in 1D2D.
- 1D-profile editor
- Enable profile editing in 1D/2D, i.e. full profile editor functionality of WSPM
- WSPM-1D/2D synchronization
- Give a possibility to synchronize changes of models in WSPM with model data (terrain.gml) in 1D/2D, if e.g. user changes active flow region etc.
- two-directions 1D-control structure
- Support the generation of wwQ-relationships for both flow directions seperatly (changes in GUI and calculation core)
- activation of control structures
- Add a possibility to switch on/off individual control structures in a calculation unit or generally. Point is just to be able to switch off a control structure without deleting the data set.
- Editing tools for polygons
- Enable snapping for polygon drawing (e.g. for roughness polygons)
- Enable possibility of adding a node to the linear ring or moving a particular node of the linear ring
- Pasting into time series
- Enable pasting into the table of a boundary condition
- Improve Bandgenerator
- Connection lines between 1st and 3rd boundary lines are straight. They should connect equal distant distributed nodes in between.
- Import timeseries from KalypsoHydrology
- Import of timeseries data that was processed/ calculated in KalypsoHydrology (i.e. directly show existing results in zml-browser)
[edit] processing
- Detailed definition of URFC
- Enable the detailed setting of the under relaxation factor for each time step in a very comfortable way. This feature could extremely speed up the calculation speed.
- Manual calculation interruption
- Enable manual interruption of calculation without total abruption, i.e. results processed so far should be interpreted
- Show chosen timeseries
- Display chosen timeseries in control panel graphically
- Support other calculation cores
- Other calculation cores (such as RMA2 and RMA10, Hydro-AS) should be supported, based on the same mesh-data as RMA10S (see KalypsoProdcutRoamdmap2_1CalcCores).
- Different junction approaches
- Enable momentum controlled, energy controlled and water stage controlled 1D-junctions
[edit] results
- Overwrite existing results
- Overwrite existing results for setting in timeseries results view. Problem is, that user has to set up nodes again after each new calculation. Additionally take Profile kilometer as default name.
- Improve error messages and log messages
- Improve error messages from the calculation core (Errors, warnings, hints, direkt access to nodes etc., iteration table, activation/deactivation of nodes/elements ... )
- Result Post Processing
- Allow selective and/or lazy result processing. Improve result visualization (i.e. 3D, dynamic, compare). Also new types of results(-views) should be considered (i.e. dynamic flow pathes, ...).
- Importing results from external calculations would be nice.
- Marsh-vectors
- Enable marsh water depth display and Marsh-vector display in plan view. (Let's have a deeper discussion about, what could be done to understand Marshing-algorithm better, too). This task is very important, as it can extremely increase the stability of the model. Following should be visualizable optionally: Marsh depth/slot depth, Marsh vectors, Marsh water depth results, effective porosity results, type of active Marsh range ...
- Active/Inoperative elements
- Enable the visualisation of boundary lines of the active flow region. Besides display the active/ inoperative elements at a particular run
- Line checks
- Introduce result evaluation at cross section definitions in 2D meshs. Also integrate them for evaluation of longitudinal sections through 2D-mesh parts for calculation of Q and average v.
- Longitudinal section setup
- Enable longitudinal section setup, i.e. be able to set up connections of longitudinal sections of base units in coupled units.
- Add timeseries to tables
- Enable additional loading of time series to results graphics to be able (e.g. for calibration)
[edit] completely new features
- IMPORTANT:
- support rm1-model files Enable Prof. King to use our GUI
- Loading of files
- Enable loading of external control files (r10)
- Enable side friction e.g. for walls
- Make use of the shore line friction functionality of RMA·Kalypso, that already exists
- Calculation Units
- Implement an import / export functionality for calculation units (and all underlying data) in order to share / exchange calculation units beyond projects.
- 2D-control structures
- Add possibility to introduce 2D control structures as weirs, sluice gates etc.
- Enlarge cstrc-possibilies
- Add additional calculation possibilities for weirs
- Channel profiles (GEO-approach)
- Enable 1D-sections with original RMA10S-definition method (geometric approach)
- Parameter settings
- Set up general calculation core parameters like memory settings, inflow element number etc.
- Calculation core compatibility
- Add general information page, which calculation core versions are supported in a certain Kalypso version
- Inflow elements
- More refinement of inflow elements, i.e. differ between inflow elements with or without predefined inflow direction (momentum influence). Introduce inflow groups (deep cogging with calculation core, see other road map).
- Widening/contraction losses
- Introduce feature for consideration of widening and contraction losses in 1D approach (deep cogging with calculation core, see other road map).
- Local losses
- Introduce feature to consider local losses (deep cogging with calculation core, see other road map)
- Simplified bridges/weirs
- Develope feature to consider bridges/weirs in simple form as local loss with formula of Cidarer (deep cogging with calculation core, see other road map)
[edit] WSPM
[edit] Proposed items
- None at this time
[edit] Committed items
- Improve performance
- Displaying the profiles in the map has greatly improved
[edit] Deferred Items
- Distinguish profiles from different strands/water bodies
- Enhance visualization of results
- Show waterlevels in profiles, show multiple results in one chart, ...
- Show more layers in length-section chart
- Profile Interpolation
- Enhance Profile Management/Display
- Enforce work with map in general
- Synchronisation Map - Chart
- Support for 'Energieverlust'
- Workflow for WSPM
- Profile DGM Extraction
[edit] RRM (NA)
[edit] Proposed items
- None at this time
[edit] Committed items
- None at this time
[edit] Deferred Items
- workflow support
- Theoretical workflow already exists. Workflow support for RRM is really necessary
- statistical analysis Add statistical analysis functions
[edit] Flood
[edit] Proposed items
- None at this time
[edit] Committed items
- None at this time
[edit] Deferred Items
- Add filter functions to raster data processing
- Filter out small islands or ponds
- Only consider main water body
- ...
[edit] Risk
[edit] Proposed items
- None at this time
[edit] Committed items
- None at this time
[edit] Deferred Items
- Additional outputs
- Generate more 'in between results' during risk calculation as damages etc.
- Additional outputs
- Export grids as shapes.
- Single damage calculation
- Enable calculation of damage for single flood events