Skip to Main Content
Autodesk
ADD A NEW IDEA

Clear

Ideas

Showing 32 of 1370

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

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 10 months ago in InfoWorks ICM / Export Data 2 For Review

Export functionality for rain gage boundaries

Be able to export rain gage boundary polygon data to GIS formats (shp, gdb) for use in other platforms.
Guest 7 months ago in InfoWorks ICM / Export Data 2 Gathering support

Costs that vary based on different parameters (Material, size, buried depth, etc)

Costs vary based on different parameters as it is not the same to replace a 6in pipe vs a 12 in pipe. Pipes that are buried deeper are also more expensive.
Martha Nunez about 2 years ago in Info360 Asset / Rehab actions & cost 0 In progress

Export functionality for SWMM objects in database tree

Be able to right-click on SWMM objects (SWMM time patterns, SWMM climatology, SWMM pollutograph) and export to CSV as you can with InfoWorks objects.
Guest 8 months ago in InfoWorks ICM / Export Data 1 For Review

Export run results to csv: timestep options

When exporting run results to csv, it would be useful to select a timeframe you wish to export (excluding for instance the initial conditions that haven't settled into a level that makes sense). Also exporting at a different timestep than the one ...
Guest almost 3 years ago in InfoWorks ICM / Export Data / Results 0 Gathering support

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

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

Export Max Flood Contours - Elevation

It would add value to ICM if users could export the Maximum Flood Contours as Elevations in the same way that we can for Depth. This would be particularly useful as currently Depth is the only property that be be exported as an ASCII Grid file. I...
Guest over 4 years ago in InfoWorks ICM / Export Data / Results / Sharing 2 Gathering support

Make pruned link data accessible

The idea is to be able to export pruned asset data for statistics purposes - e.g. how many conduits have been pruned from the network. The merge_details table is not a structured blob and therefore is not accessible via Ruby. Exposing this table t...
Guest over 1 year ago in InfoWorks ICM / Export Data 2 Gathering support