During Data Import

In general, allow a lot of time for tile generation and refresh. Avoid refreshing as much as possible. Be very careful about the order in which you import, configure, and refresh data layers. Start with your largest (area) layer first, which is ideally the terrain.

1. Terrain Data:

   If you are importing very large, detailed terrain data from Autodesk Civil 3D, you may experience faster model generation and display speed if you export the terrain layer to TIF format in Civil 3D before importing to InfraWorks, rather than IMX format.

   Note: This may require some experimentation. In some cases, TIF format terrain from Civil 3D can create accuracy loss compared to IMX format.

2. Clip to Model Extent:

   Make sure to clip each additional data layer to your model extent upon each subsequent import of data. (This is not an option for 3D models that you import.) If you haven't already defined a model extent, the first data layer you import defines the model extent by default. When importing and configuring additional data layers, choose Clip to Model Extent from the Source or Raster tab (depending on the feature type) of the Data Source Configuration dialog. This will limit the extent of imported data to the model extent.

3. Imagery Data:

   • Specify classification for Raster imagery if you know the imagery data classification.

   • Specify a lower Bing Maps Imagery Tile Level Resolution.

     If you are using the Bing Maps service to add imagery to your model, be aware that Bing Maps Imagery defaults to Level 17 Tile Level Resolution where possible (1.1943 m/px), although Tile Level up to Level 19 Resolution (0.2986 m/px) is available for some areas. However, InfraWorks cannot generate more than approximately 1 million (1204 x. 1040) raster tiles using the Bing Maps Imagery Service, so using Level 19 tile resolution for extremely large areas may produce an error. It is recommended to use a lower Tile Level Resolution when your imagery layer covers a very large geographic area. Using high Tile Level Resolution can significantly increase the time it takes to download and share a model via InfraWorks. Users working on internet connections having low upload bandwidth will also find it more challenging to share the model. Most home internet users have very low upload bandwidth.

4. Water Data:

   During configuration, make sure to properly specify how closed polylines will be treated in the model. De-selecting "Convert closed polylines to polygons" will treat a water feature as a river, while selecting it will treat that same water feature as a pond or lake.

5. 3D Model Objects (including vegetation)

   • You can simplify any 3D model objects during import using the 3D model tab in the Data Source Configuration dialog.

   • Adjust model handling to "Use LOD."

     Use this setting if the model has a great deal of detail with many triangles defining its shape, for example, a detailed city furniture model. LOD reduces the complexity of a 3D model as it moves away from the camera. The number of triangles defining the model are reduced to one quarter of their previous value at each transition distance. (The transition levels are determined by the application). The LOD Distance setting represents the first transition distance. At distances smaller than this, the model appears with full detail. If you are not satisfied with the simplification quality in this setting, you can increase the view distance (e.g., to 5000m or 10,000m) to not see simplifications.

     Note: If you reduced the value for Simplify Model, the level of detail starts with the reduced value.

   • Avoid trees whether imported as single points or as polygons/polylines to create groups.

     If you want to use trees, see To create adaptive trees to design high-performance forests.

   • Add LOD representations for high-detail 3D models. See the Set Up Level of Detail (LOD) section of To create Shared Assets for your library for more information.