Data Exchange

Showing 63 of 1244

Raster export and import

Allow the use of rasters for importing and exporting data. Rasters take up significantly less space than a vector file and require less pre and post processing. Spatial layers like roughness, 2D hydraulic conditions, Infiltration, etc. could be im...

Andrew Sherson about 10 hours ago in InfoWorks ICM / Data Exchange 1 For Review

3 VOTE

Improve GIS engine

ICM stores everything, as coordinates in tables. This is especially an issue for polygons as polygons are just coordinates in a table. This means things like Donut polygons are not allowed and complex polygons produce countless annoying errors tha...

Andrew Sherson about 10 hours ago in InfoWorks ICM / Import data 0 For Review

2 VOTE

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 1 day ago in InfoWorks ICM / Export Data 0 For Review

4 VOTE

Export shapefile line features showing catchment loading when exporting network to GIS

This is really useful when interrogating / building the model in GIS. many of my clients have asked me if ICM will export the catchment loading arrows, and I have always had to say no.

Guest 8 days ago in InfoWorks ICM / Export Data 1 For Review

20 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 11 months ago in InfoWorks ICM / Export Data 6 Under consideration

17 VOTE

Convert 3d points from Civil 3D to cross section lines

River survey sections are provided as 3d points in a DWG file. These need to be converted to channel sections which needs to be done manually. There was previously a feature in RS that allowed the conversion.

Sophia Buchanan 12 months ago in InfoWorks ICM / Import data 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 6 months ago in InfoWorks ICM / Export Data 1 For Review

2 VOTE

A Case for Supporting 2 InfoWorks and 2 SWMM Networks as the current and background networks

A Case for Supporting 2 InfoWorks and 2 SWMM Networks as the current and background networks. In other words, InfoWorks is the current background, and SWMM is the current and background. Right now, it is SWMM and InfoWorks as the current and backg...

Robert Dickinson 3 months ago in InfoWorks ICM / Workgroup 1 For Review

16 VOTE

Give a warning when copying between networks with different user defined defaults

when copying for example conduits between networks with flags #D for headloss and roughness, the values are adapted to the user defined values in the new network. This can be confusing.

Guest almost 2 years ago in InfoWorks ICM / Flags / Import data / Productivity 0 Gathering support

4 VOTE

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 7 months ago in InfoWorks ICM / Transportables 2 In progress

Please enter your email address

FILTER BY CATEGORY