iTwin Hub - Filtering / Visualising using combined metadata search
Possibility to combine specific metadata credentials while searching for a 3D model objects using single filter with an AND operator (i.e. "Uniclass = XXXX" AND "Element Class = XXXX") or via the use of 2no Data Visualisations at the same time.
When loading a form associate to an issue, we have to wait few seconds to have all the field available. Request is to see if loading time can be enhance. When compare to opening the same form unser IRS, it take about 5x less time and the user expe...
How about using Project Wise sets to connect models via Project Wise Design Integration. Sets would be created by Project Wise user and opened while creating connection (all models needed in iModel in 1 place)
Ability to play animations created in Bentley Systems
Viewing animated objects in iTwin would greater facilitate design reviews. Presently, vehicle movement - animated in Microstation - cannot be viewed (or clashed) using iTwin, which restricts the coordination of design with logistics.
Allowing cancellation of synchronisation will help if people make a mistake in the updated files or if there are any issues with the synch/files instead of waiting for it to issue a failure notice. this will save time
The measurements that i have in the view i create with the issue are added to the issue but are very difficult to change or delete. I would like to be able to update a measure in the view, or add a new one or even delete one that was there.
Would like to be able to see the Manage Issues as graphics inside OpenRoads and OpenRail. As you can when you're looking at the issues inside the iModel.
Ability to move issue resolution flag after placed in iTwin design review. We currently have the ability to update the form details in the issues page itself, but the flag cannot be moved closer to the component after the issue has been created
Assembling a model in an imodel container from separate models located in other imodels of the same project
We would like to be able to create a common IModel based on a group of already existing in iTwin iModel. (or connect iModels to a single container, similar to the existing REFERENCE FILE in OpenPlant or Microstation)
For example, we plan to creat...
Better grouping and control of cell and blocks in the model tree
iTwin shows "unexplicable" lines and elements that are not associated to any "selectable physical object". The attached file "visually explains" the issue. As it is, in this context, iTwin is of no use for its purpose.
2
1
Future consideration
