Skip to Main Content
Autodesk
ADD A NEW IDEA

Clear

Ideas

Showing 868 of 1442

flash/locate

As in Arcmap, please include the ability to flash a selected object or via the object search. This is really useful, especially in large models, to quickly see where features are in relation to one another or in the context of the whole network.
Chris Brown almost 2 years ago in InfoWorks ICM / Visualization 3 Already exists

More flexibility for pdm runs

We would like to be able to simulate warmup and hydraulic simulations with different input sources. Now the run crashes if for example rainfall data does not match the saved state of the warmup run. It would also be very useful to make it possible...
Guest about 3 years ago in InfoWorks ICM / Hydrology 0 Gathering support

Better functionality for multiruns

- number episodes in episode collection - sort runs according to number - greater timesteps for runoff only runs - resume with next run if a run fails - easy export of maximum results of runs (without results of the runoff only runs)
Guest about 3 years ago in InfoWorks ICM / Simulations 0 Gathering support

Split CCTV inspections when a manhole gets installed

This should be done in cases where a pipe gets split into two assets because a manhole was installed along the length of the original asset. The CCTV inspection would have to be 'split' into two inspections to accurately represent the condition da...
Martha Nunez over 2 years ago in Info360 Asset / Data Editing 0 On roadmap

Expand Primary Key Fields to Support UUIDs

It would be helpful to use UUIDs as primary/secondary key fields for row objects for data exchange with other GIS databases. It could also be a better way of generating new IDs than the default approach of sequential numbers, which cause problems ...
Dave Watts 10 months ago in InfoWorks WS Pro / Data Exchange 0 Gathering support

Allow for the running of statistics templates and generation of grid reports such as RPA and worst case using ICM Exchange

No description provided
Guest almost 6 years ago in InfoWorks ICM / API / Exchange / Productivity / Results 0 Gathering support

Change default field name behaviour when exporting to shape file

When exporting model network data to shapefile format, the default export field names generated in the “open data export centre” are currently very awkward. The issue arises because many field names in ICM are longer than ten characters, but shape...
Jason Kulsdom over 1 year ago in InfoWorks ICM / Export Data 2 Under consideration

Antecedent conditions as a direct run input for design events

I would like an object similar to the 'Catchment Initial Conditions' object for the TSB, that would allow a user to directly specify and overwrite the initial NAPI value, soil store level and groundwater level, per each individual subcatchment, in...
Guest about 1 year ago in InfoWorks ICM / Rainfall 0 For Review

Change formatting of '2D level boundary below ground level' in the timestep log

Other warnings such as manhole shaft/chamber area occur with only one line of text with the '(and possibly others)' text. Could something similar be introduced for the '2D level boundary below ground level' warning in the timestep log? This warnin...
Tom Newman about 1 year ago in InfoWorks ICM / Reporting 0 For Review

Allow export of user flags via ruby

As a WaSC we hold our models in a central model library and need to ensure our default flags are utilised, and the descriptors are not amended. we have automated the comparison as far as possible but the flags within any new Db have to be manually...
Richard Robinson about 1 year ago in InfoWorks ICM / Export Data 0 For Review