When adding hyperlinks to features within the properties, enable the ability to link to a specific page within the document itself rather than just a folder location or document opening on the first page.

It would be great to add PMP (probable maximum precipitation) calculator to XPSWMM and XPSTORM

The Hong Kong Observatory is the authority responsible for producing observed and forecast rainfall data for the territory. Their data is produced in a format not currently supported in ICMLive so we have to convert it into shape files to be used. Direct reading of this data would enable both more efficient data loading processes as well as reducing the potential for errors.

When updating bank lines from ground model it would be useful to have an option was available to only update the interpreted points, therefore retaining vertices heights from cross sections and surveyed points. Or an option to easily delete the interpreted points, so they can be updated.

Australian flood modelling user have requested access to the WBNM hydrology method inside InfoWorks ICM. WBNM is one of the endorsed methods in Australian Rainfall & Runoff and large numbers of historical studies use this method.

InfoWorks ICM currently has the RAFTS Hydrological Routing method, but as a flood modelling user, I would like access to the RORB method as an option inside ICM. It is a similar method to RAFTS and would help endorsement of the software where RORB hydrology is a requirement.

When applying direct rainfall onto 2D zones traditional roughness values do not typically apply, especially where the depths of water on the mesh element are very small. Often the workaround is to apply much higher roughness values in order to 'slow the flow'. It would be helpful to have a depth varying roughness that could be phased out as the water depth increases. This would put ICM in line with how TUFLOW and Flood Modeller Pro deal with the problem.

Tool similar to competing software where you can apply a level (%) of uncertainty and automatically sun simulations with varied parameters withing that level of uncertainty and see all results at once.

Being able to insert channels into terrain rather than editing in 12D or other software would be more practical for smaller firms to turn around modelling ideas.

Landscape packages allow terrain meshes to be manipulated with tools that sink into mesh easily. Channels and swales need slope, not simply vertical depression to model correctly. XPStorm allows 1D modelling but this isn't useful for presentations and Civil 3d and 12d are catching up quickly now that rational method is being phased out.

I am trying to calculate the excavation/fill volume by comparing my existing model with the proposed one. I know we can open simulation results with “As alternate results for comparison” which allows us to compare flooding depth from two different scenarios. I expect to have something like this for ground surface as well so that we can see the different ground elevation visually and/or numerically.

I would like to be able to enter the full and reduced speed pump curves for each pump station that is controlled by variable frequency drives. In addition, I would need the set point or control that causes the pumps to ramp up to full speed.

I am working on project which includes 50 models. where we have to give runs for different return periods and durations for each model. It is a time taking process, which unnecessarily create chances of error by creating run setup every time. is it possible to include a run set up template, which can be changed as per the user requirement and saved for the further use.?

Is there a way to generate a table that lists all Suds Structures IDs? I would like to see this so that I can review total area applied, make changes quickly, and also complete QA checks easily.

I would like to use radar rainfall like NEXRAD and spatially correct it to my rain gauge network locally before applying the rainfall in my model.

We use custom labels a lot in reporting how we model ancillaries, and for complex assets spend a long time adjusting labels so they don't overlap and do show up properly.
It would be great if a more "smart" label engine could be used so that labels don't overlap each other, and a few simple other rules e.g. as close to the object as possible, avoid line crossing, and automatically show any newly generated label within the current view extent.

Client feedback: an automatic check for colliding pipes would be highly appreciated to avoid nightmares in the construction.

Provide a function to easily assess cross sections of the ground model, similar to the XPSWMM function