I've used the reference workflow before. Converting it to an .bim file then attaching it.
The thing is that we need to use the elements for design.
For example earthworks escavations: using the analysis volume from OpenRoads with slabs imported from an architecture .nwc and set as design meshes. Or Terrain from design meshes in a similar use.
Or clean up a model and change some properties for display use.. Or improving elements.. The list goes on..
Even with some information and geometry loss in the process, it would be ok!
Import or reference? Import assumes you might was to edit the geometry, which might not translate too well. Reference meaning you want it as an overlay but uneditable.
This can be achieved by using iTwins, then referencing the iTwin to MicroStation.
I actually meant import!
I've used the reference workflow before. Converting it to an .bim file then attaching it.
The thing is that we need to use the elements for design.
For example earthworks escavations: using the analysis volume from OpenRoads with slabs imported from an architecture .nwc and set as design meshes. Or Terrain from design meshes in a similar use.
Or clean up a model and change some properties for display use.. Or improving elements.. The list goes on..
Even with some information and geometry loss in the process, it would be ok!
Import or reference? Import assumes you might was to edit the geometry, which might not translate too well. Reference meaning you want it as an overlay but uneditable.
This can be achieved by using iTwins, then referencing the iTwin to MicroStation.
https://developer.bentley.com/apis/synchronization/supported-formats/
At this point, I will mark this as Will not do given there is a way, but if the popularity soars, we can revisit.