IModel Tree Merge

[zhang-zimin]

I want to combine two iModels in one viewer and merge their model trees together. How can I achieve this?

[grigasp]

At the moment this is not possible, but we do have a work item for this feature and an internal consumer that is also interested. Could you provide more context on what you're trying to achieve? E.g., are the two iModels related to each other in some way? Anything else you can add would be helpful.

[zhang-zimin]

Would like to merge the two imodel but they may not be related to each other.

[grigasp]

In that case, I think I'll have to say that this feature is not and will not be supported in near future.

To create a hierarchy we use metadata of displayed elements (their classes, properties, etc.). That metadata is required for:

• grouping (by class, by property),
• filtering (need to determine the types of elements under specific parent node, then get all available properties for each type).

With elements coming from multiple independent iModels, we may see similar-named classes that have different attributes or properties, or similar-named properties that have different types / attributes. That hugely increases complexity of the features that rely on metadata.

I've linked this discussion to our issue to make sure we keep this in mind when we get to implementing the feature, but that's currently not planned.