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...
We were using the 3d design review with construction partner, manipulating displayed content and visualization to see what they were interested in. They then asked us to grab a shot of that so they could print it and have it in the conference room...
Currently if you switch the tree view to “Categories” you see the same levels repeated for every model that uses it. Users wanting to control view by category don’t want to have to pick and manage multiple instances of the same level. When wanting...
Provide a Line Weight scale option in Cross Section view
The Design Review cross section tool provides for a Point Weight scale option - which works well. Similarly, could you provide a Line Weight scale option to assist making the lines more visible in the XS view?
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.
Point cloud classification by elevation like in MicroStation
User publish point cloud in iTwin without colors. In MicroStation you can select by elevation classification and it's easy to understand point position. We need to add same in iTwin design review. See attach pictures
Comparison of models with different file names, but the same content
Comparison of named versions by content without binding elements to the source file's name.
When a 3D model being developed, files names and, perhaps, partially their content, are subject to change (Or any other change in the file structure – add...
The current synchronisation of iModels prevents the individual naming of the 4 files that make up the cadastre documentation. It is necessary, for quality reasons, to avoid that several documents share the same name, so the current synchronisation...