Ideas

Showing 777 of 1370

11 VOTE

possibility to connect labels to links at the beginning or end instead of only in the middle of the link

This way you can show that link invert levels on a manhole differ in value or deviate from the chamberfloor

Loes van der Linden 10 months ago in InfoWorks ICM / Labels 3 Already exists

23 VOTE

Allow Exporting of Summary Data from Observed/Predicted Report with assessment made against wapug criteria in .csv format.

This would make reporting on model verification much quicker with higher accuracy

Roger Swan over 1 year ago in InfoWorks ICM / Export Data 13 Under consideration

7 VOTE

Repeat Table Headers on each page

The report tables currently display the table headers once under each return period / critical event. If the headers were repeated on each page, the tables would be easier to read. Thanks

Guest 6 months ago in InfoDrainage / Reporting 1 Gathering support

16 VOTE

Ability to move labels to avoid overlaps

At the moment if labels overlap the only way to read the information on screen is to reduce all text size, which has other readability issues.

Matthew Johnson about 1 year ago in InfoDrainage / Visualization 0 For Review

6 VOTE

Accept HKO NETCDF file format as STSD

The spatial time series data currently accept netcdf format of AUS.BOM and SJSU. HKO .nc formt is not supported . Please support HKO netcdf format.

HENRY LAM 6 months ago in InfoWorks ICM / Live Modeling 1 Will not implement

23 VOTE

Would it be possible to include longitudinal gradient (slope) to attenuation tanks please? At the moment it appears that software assumes that these structures are constructed flat whereas in real life these could be constructed with a gradient (slope) from the upstream end towards the outlet.

At the moment it appears that software assumes that these structures are constructed flat whereas in real life these could be constructed with a gradient (slope) from the upstream end towards the outlet (and this could then change the head of wate...

arek kadlec over 1 year ago in InfoDrainage / Hydraulics 1 Gathering support

7 VOTE

Integration of Vector Geoprocessing Capabilities in Ruby for InfoWorks ICM

I propose adding support for core vector geoprocessing operations such as clip, buffer, intersection, union, symmetrical difference, and similar tools directly within the Ruby scripting environment in InfoWorks ICM. This enhancement would signific...

Sebastian Madrid 7 months ago in InfoWorks ICM / API / Exchange 3 Gathering support

7 VOTE

Better scenario comparison tools

Comparing changes/differences between scenarios is a chore as it can only be done via manually checking objects or looking through a text file showing the differences. I recommend 2 improvements. 1) be able to see different scenario attributes sid...

Andrew Sherson 7 months ago in InfoWorks ICM / Tree View 3 Gathering support

5 VOTE

Themes to include robust SQLs

Can we enhance conduit theming using robust SQL queries? We're aiming to apply themes based on the mean of minimum upstream and downstream velocities in each conduit over the TSR simulation. Considering the multiple scenarios involved in system de...

Parameswara Rao Narra 5 months ago in InfoWorks ICM / Theme 4 Already exists

5 VOTE

worst case Grid report to include min values

Can the worst case grid report be enhanced to include minimum values for velocity and flow, similar to how it currently reports maximum upstream and downstream flow? This addition would be highly beneficial for understanding hydraulic behavior dur...

Parameswara Rao Narra 5 months ago in InfoWorks ICM / Results 3 Already exists

Please enter your email address

FILTER BY CATEGORY