You publish a model to the cloud only once. The model database and all of its textures and 3D models are uploaded along with the model. You can selectively publish proposals along with the master model.
- Each design group member then downloads a copy of the model. After that, each group member only sends changes made to the local copy to the cloud model and gets (downloads) changes only from the latest synchronized model.
- Open the model.
The model must be stored on your local drive. Model names within a group must be unique.
- Sign-in to InfraWorks 360, If not signed-in.
- Optionally: check Manage Online Models for space in your account to accommodate the model. For details, see To view model information
- Click
to open the Publish Model panel. If the model has been published, InfraWorks 360 opens the Synchronize Model panel.
- Select the design group to share this model.
If you belong to more than one group, select from the Group field menu.
- Select resources to publish, including proposals if any.
By default, only the master model and Common Resources are published. Select proposals to include.
- Common Resources apply to all proposals (including the master). They include scenario definitions, storyboards, bookmarks, themes, and settings on the Model Explorer. You cannot clear the Common Resources selection because each model requires these items to be present. When you synchronize later, you can specify whether to synchronize Common Resources or not.
- Optionally, enter comments or a description in the Publishing Notes area.
- Click Publish.
Advanced Tips
Publishing can take a long time depending on the amount of data involved. Large raster or point cloud data sources can slow publishing. During a long publishing operation, the model might appear on the Start page for other group members but it will display as 0 bytes. If a group member tries to download or delete the model before the publish is complete, an error message indicates the model is locked. A model can also be locked during a long download or sync operation. Model locking does not block a group member from synchronizing non-raster-based changes.