The current Dashboard Display (available since 2019.02) can be used to visualize different spatial plots side by side. By moving the time slider, all the different spatial plots change accordingly. End users can create and share their designed dashboards with colleagues. Currently, only plots from the Spatial Display can be part of a dashboard. The Dashboard Display was part of the Delft-FEWS 2019.02 New features webinar. Click here for the Dashboard Display movieclip.

The new idea presented here is to extend the dashboard display to also visualize other time-slider driven plots from the Time Series Display and the Schematic Status Display.

 The estimated costs to implement this is: €17.500.- which includes: code developments and review, testing and documentation. This feature is known under reference FEWS-22930 and is on the waiting list for Delft-FEWS 2020.02 (Expected release date: November 2020).

Would you like more information about this idea and/or considering co-financing this development, please contact the expert(s) mentioned below.

The current Archive Admini console (GUI) of the Open Archive enables an Open Archive administrator to inspect/check the content and behavior of the Open Archive, carrying out maintenance-tasks, clean up archived data and regenerate the catalogue. 

The new idea presented here is twofold: First an upgrade of the GUI is suggested to align this with the existing Delft-FEWS Admin Interface. This console has similar administrator role but then focused on the Delft-FEWS client-server system. Since 2018.02 this Admin Interface has been restyled and can be accessed via an API (Application Programming Interface). This is the second part of the suggested improvement. Like the Admin Interface, the Archive Administrator console should have an API enabling access for other applications (tools, websites) to interact with the functions of this console. This API broadens the use of the Archive Administrator console and opens it up to users so they can use their own tools, scripts, build dashboards around it etc. Using the same framework for all Admin consoles (within the Delft-FEWS components) has a preference from a code maintenance perspective as well.

The estimated costs to implement this is: €13.500.- which includes: code developments and review, testing and documentation. This feature is known under reference FEWS-22932 and is on the waiting list for Delft-FEWS 2020.02 (Expected release date: November 2020).

Would you like more information about this idea and/or are you considering co-financing this development, please contact the experts mentioned below.

Andre Grijze (Andre.Grijze@deltares)

Rudie Ekkelenkamp (Rudie.Ekkelenkamp@deltares.nl)

The current Delft-FEWS web service already exchange data with external applications. A wide variety of queries can be submitted to the Delft-FEWS web service to get appropriate responses to be further processed into other applications like web sites, data viewers, data management systems etc. build by others.

An important element of a (flood) forecasting system is the collection of threshold events which are captured in a dedicated table of the Delft-FEWS central database. A threshold event is a combination of a location, parameter, threshold-indicator, threshold crossing type (up crossing, down crossing) and the time of crossing. This information is vital to visualize warnings (e.g. on the Delft-FEWS Map) or to trigger tasks (export, send e-mail).

Thresholds events can also be used for post-analysis of flood events to assess if there were 'false alarms' when the forecast timeseries was indicating a threshold crossing, but the actual measurement timeseries did not. Threshold events are often used for model validation and calibration purposes.

The new idea presented here is to extend the Delft-FEWS web service with this threshold event information. Example responses users can get when querying the web services are e.g. :

• Number of threshold events in a certain period (for a specific timeseries)

• Number of threshold events of a certain severity (for a specific timeseries)

• Elapsed time between up crossing and corresponding down crossing (for a specific threshold event)

More use cases can be defined at a later stage

The estimated costs to implement this is: €7.000.- which includes: code developments and review, testing and documentation. This feature is known under reference FEWS-22933 and is on the waiting list for Delft-FEWS 2020.02 (Expected release date: November 2020).

Would you like more information about this idea and/or considering co-financing this development, please contact the expert(s) mentioned below.

The current temporary import enables users to import PI.xml based files shared by others via a menu option. The result is a temporary filter in the Data Viewer tab of the Delft-FEWS Explorer. Main objective is that you can simply inspect files without additional configuration (locations, parameters, import workflow etc). When the timeseries have been imported, users can treat these as any other timeseries within the running session of your Operator Client. Once Delft-FEWS is closed, the data have gone. As mentioned this functionality is limited to PI.xml files only.

The new idea presented here is to extend this functionality so that you can import more than just PI.xml. The foreseen extension is: CSV, NetCDF-CF TIMESERIES (scalar) and NetCDF-CF TIMESERIES (grids).

The estimated costs to implement this is: €17.500.- which includes: code developments and review, testing and documentation. This feature is known under reference FEWS-22931 and is on the waiting list for Delft-FEWS 2020.02 (Expected release date: November 2020).

 Would you like more information about this idea and/or considering co-financing this development, please contact Toon Basten, Waterboard Aa and Maas (NL), tbasten@aaenmaas.nl .