Ideas

Showing 1067 of 1442

Include parts mapping files for the UKIE country kit by default.

Across the UKIE region many designers will use the UKIE country kit for building Civil3D models, instead of everyone making their own parts map files this could be an integral part of the data exchange between two Autodesk products, included in th...

Guest about 2 years ago in InfoDrainage / Civil3D Integration 1 Under consideration

3 VOTE

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

3 VOTE

Cumulative Inflow Areas Against Junctions and Connections Results

In order to aid the quality assurance process that exists throughout drainage design, it would make life much simpler to have a cumulative contributing inflow area against junction summaries. Being able to sense check results with the contributing...

Guest 10 months ago in InfoDrainage / Reporting 2 Gathering support

22 VOTE

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

6 VOTE

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

4 VOTE

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

4 VOTE

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

7 VOTE

Add an option to automatically Refresh All graphs in the Report Manager after a new run.

Currently when you complete a new run you have to remember to hit Refresh All in the Report Manager to see latest results. The use-case for viewing old run results is rare, so having an option to automatically refresh all graphs and tables would b...

Grant Clemens almost 2 years ago in InfoWater Pro / Productivity 0 Gathering support

8 VOTE

SWMM Export from InfoDrainage

Certain authorities use other SWMM-based software for review purposes or as their city-wide model that needs to be updated. We need to export a SWMM file for more universal submittal purposes, even if InfoDrainage uses a modified SWMM engine.

Midori Patterson about 2 years ago in InfoDrainage / Data Exchange 3 Under consideration

6 VOTE

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 over 1 year ago in InfoDrainage / Hydraulics 2 Gathering support

Please enter your email address

FILTER BY CATEGORY