All ideas

Showing 1372 of 1372

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 5 months ago in InfoWorks ICM / Live Modeling 1 Will not implement

31 VOTE

Remove calculations from Notes field

Could Storage Compensation & Numerical Correction calculations be detailed and exported in a separate file (spreadsheet for ease of filtering? possibly date stamped and recording model name, version, path etc) rather than being appended to the...

Giorgio Incelli about 2 years ago in InfoWorks ICM / Other 0 Gathering support

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

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

2 VOTE

Enable Exchange Ruby method for carrying out spatial analysis in Workgroup Products

SQL tool in InfoAsset Manager enables users to perform spatial analysis of a variety of types using a selection of layer types. This is an extremely important and useful analytics tool which avoids the need for a user to export data out of InfoAss...

Anthony Andrews about 2 months ago in Other Product Ideas / Other 1 For Review

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 6 months ago in InfoWorks ICM / API / Exchange 3 Gathering support

2 VOTE

Parcel Import to Catchment

It would be extremely helpful if InfoDrainage could import Civil 3D Parcels directly as catchment areas, similar to how it currently imports other CAD data (polylines). Parcels often represent drainage catchments, lots, or contributing areas in si...

Guest about 2 months ago in InfoDrainage / Data Exchange 0 For Review

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

Please enter your email address

FILTER BY CATEGORY