The Reality Data Widget

There are two distinct workflows for publishing reality data to ProjecyWise ContextShare:

1. iModel Connectors: in this workflow the reality data is attached to a DGN file in a MicroStation-based application and published to ProjectWise ContextShare when that DGN is published by an iModel Connector. The result is a reality data that is stored in the ProjectWise ContextShare service, associated to the project of the published iModel and also attached to this same iModel. A reality data is only published once for a given DGN/iModel combination.
2. Reality Modeling desktop application: Applications such as ContextCapture, Descartes and Orbit have the ability to upload the reality data they create to ProjectWise ContextShare. The result is a reality data that is stored in the ProjectWise ContextShare service, associated to a project, but not attached to an iModel.

In the first workflow described above, a DGN file and its attached reality data are published and readily available for display in iTwin applications since the resulting reality data is attached to the iModel. But, what about publish an iModel first and publishing reality data at a latter time using the second workflow? The Reality Data Widget, builds a list of the reality data from a given project that can be displayed in iTwin applications.

Here is a screen capture of the Reality Data Widget:

The following Reality Data formats are supported by the Reality Data Widget and iTwin applications:

• Web Ready 3D Scalable Mesh (.json)
• Web Ready Terrain Scalable Mesh (.json)
• Cesium 3D tiles (.json)
• Web Ready Point Cloud (.opc)

The “Filter” icon located at the top of the widget controls which reality data are listed. Here is a description of the different filters:

• All: List all supported reality data that are associated to current project.
• Overlap: Only list the supported reality data that are associated to current project and overlap the model’s spatial location.
• Attached: Only list the supported reality data that are attached to the iModel.

Notes:

• When more than one filter is toggled ON, results are combined.
• The “Overlap” filter is unavailable when the opened iModel is not georeferenced.
• The “Attached” filter is unavailable when the application opens reality data directly (e.g. the Reality Data Web Viewer).