Skip to Main Content
Autodesk
ADD A NEW IDEA

All ideas

Showing 1188 of 1188

IWLive - alernative warning themes for polygons

Currently IWLive polygons can theme based on the most severe warning. We want an option to theme instead based on which polygon contains the most warnings, and potentially other options like the earliest warning.
Nathan Gerdts about 1 year ago in InfoWorks WS Pro 0 Under consideration

Sharing Cloud Results

When using Autodesk cloud resources to run simulations, we have lost the ability to package up cloud results with models for model run submittals. This is a blocker for using or recommending Autodesk cloud simulations for InfoWorks ICM. US Stormwa...
Matt Anderson 4 months ago in InfoWorks ICM / Transportables 2 In progress

Capability to restore multiple pruned links

It is cumbersome to restore pruned links one at a time if many assets need to be restored. The ability to restore a selection of pruned links and/or all pruned links would be helpful.
Guest 7 months ago in InfoWorks ICM / Network 2 Gathering support

Change the way scenarios work

When scenarios were first introduced the way they were implemented didn't seem intuitive. With increasing interest in such as adaptive pathways the number of scenarios can rapidly increase because each scenario is its own network. This proposal is...
andy.bolden over 1 year ago in InfoWorks ICM / Scenario 0 Gathering support

Variable depth for open channels and swales

One limitation we are running into is the inability to model varying depths within swales in InfoDrainage. Often open channels will run along road corridors for example where the crest either remains at a similar elevation while the depth changes....
Guest over 1 year ago in InfoDrainage / Visualization 1 Under consideration

Junction Loss

There need to be more options for calculating junction loss. Having values for entry and exit loss isn't enough. Recommend HEC-22 and AASHTO at a minimum.
Guest 4 months ago in InfoDrainage / Hydraulics 2 Gathering support

UX: Allow decimal values without a leading zero

When adjusting values - you need to enter a leading zero to adjust by non-integer values. It would be nice to simply type '.5' if you need to lower by half a unit. The anticipation and early validation of the number is needless to toss a dialog bo...
Matt Anderson 4 months ago in InfoWorks ICM / Productivity 2 Gathering support

Remove Need to Validate When Changing Background Layers

Suggest that a network not need to validated or show that it was edited (red circle) for only switching on/off a background (e.g., aerial)layer would be appreciated. Keeping scenarios straight is tough enough w/out the additional heart attack when...
Guest about 3 years ago in InfoWorks ICM / Productivity / Validation 3 Will not implement

Pipe Intersection coordinates

Whilst setting the coords of a pipe intersection is a good feature, in certain common cases InfoDrainage does not allow for setting the correct setting of grade and levels of pipework, and due to its calculations can output levels against a certai...
Guest 4 months ago in InfoDrainage / Hydraulics 1 Gathering support

Ability to use variables in range RTC rules

For RTC range rules, we want to be able to use variables instead of constant values for the minimum and maximum values.
Guest almost 2 years ago in InfoWorks ICM / RTC 0 Gathering support