Enhance/Add support to the GIS Layer Control to access the new OS Open Data API's WMTS. It appears at the minute you can only add WMS layers.

https://osdatahub.os.uk/

Now the file name format like YYYYMMDDHH_hhhmm of ASCII grid (forecast) can be supported in Spatial TSDB. However, if the user has a forecast origin accurate to minute, it cannot be used. A new file name format of YYYYMMDDHHMM_hhhmm should be included.

Current user defined vortex controls don't accept head discharge curves where the discharge reduces for increasing head i.e. what happens in a hydrobrake. It would be useful to get this updated to ensure consistency between ICM and drainage design.

On behave of Chinese users, could developing team transfer drainage design module from infoSwmm into ICM?

Clients in China do have this wish to do drainage and model in same software. Many of our potential client choose Hongye (a simple drainage modelling software) instead of ICM only because Hongye could do pipe design work.

The ability to drag and drop ruby scripts from the file system into the ICM window in order to execute them.

This will not only be useful for day to day use of using ruby scripts but will also be useful for 3rd party (and open source) applications like InfoLab

https://github.com/sancarn/InfoLab

Currently in order to inject ruby scripts into the UI we have to use open up Network tab and execute the "Run Ruby Script" button's default action. Creating a drop event onto ICM would be significantly easier and is extremely easy to implement (a few hours)

As a use the ability to 'schedule' statistical reports would be extremely useful. currently if i'm generating a spill report on several overflows for a 10yr TSR series this can take several hours. The process effectively locks the software and prevents any other operation from been undertaken. This is highly inefficient and costly especially when optioneering if several iterations are needed. Shorter TSR's can be run in this case however even a year with several CSO's can take 20-30mins.

When exporting results to GIS, it should export all the storms that are selected, so that I don't need to manually extract the information and piece them together.

The more functionalities become available in ICM, the larger results files grow and the less manageable they become (especially when running longer time series). In most cases people are only interested in very specific results (e.g. depth, flows, ... and not such things as all the detailed runoff components). So if one would be able to select at the simulation schedule which variables were to be stored), results file sizes (and hence results querying !) could be reduced enormeously.

Currently the only GeoTIFF standard supported in ICM Spatial TSDB is the MeteoGroup standard. But some Authorities in Germany deliver rainfall data as generic TIFF.
It would be nice to extend the import feature to a generic GeoTIFF format.

Options such as 'Reintegrate' & Duplicate'

When importing from autocad layer mapping can be used to create a model layout for things like 2D Mesh zones but all created objects are null. I have written an SQL to apply parameters to all null mesh zones and roughness zones and import each layer individually. If the autocad layer was written to usertext1 I could import all at once with a saved layer mapping and then enter all parameters by selecting usertext1

ICM currently allows 4 infiltration types in 2D infiltration types:

-fixed
-Horton
-Constinf
-GreenAmpt

Australian Rainfall and Runoff 2019 talks default initial loss and continuing loss parameters for rural catchments, values for which which can be found in the BOM data hub.

A new 2D infiltration type which allows the simple IL/CL would allow 2D modelling more inline with ARR2019.

Creating or amending ICMTs is slow, especially if they contain ground models. Even deleting or creating new 'folder' items in ICMTs is slow. Speeding this process up would increase productivity.

Can we have the status of base linear structures included in the log file? I have a large model where I have lots of these and I need to interrogate each one in turn. It would be much easier if the log file (or, better still, a grid view) showed the status of each wall.

When a version of a network is copied via the commit history dialog box, the standard commit detail generated is "created from copy". Could this be extended by automatically inserting the original network name and version number ? It would help a lot in retracing the network history.