Product(s):	OpenRoads Designer
Version(s):	10.10.21+
Area:	General

 

Question: 

How do I prepare my OpenRoads data to be published to an iModel?

 

Answer:

1. Create a 2D container file with OpenRoads Designer.
   • This container file needs to be created from the correct seed file in the Workspace used by the dataset.
   • The container file needs to have the correct GCS for the project.
2. Attach all needed/required reference files.
   • If the reference file has a default (2D) and default-3D model, attach the default (2D) model only.
   • If the file has only a 2D model(s), attach each desired model as-is.
   • If the file has only a 3D model(s), attach each desired model as-is.
3. Create a Civil model in the container file that results in the creation of a default-3D
   • e.g. Make terrain active
4. Review the hierarchy of the reference files. Be sure that ALL required files\models are listed.
   • Ensure the Reference Display = ON for each reference attachment you want to show in the iModel.
   • Set the 3D-Default model within the “container” file to a minimum nesting depth of 1.

Set the configuration variable:

MS_LOCAL_MATERIALS = 1

This will better support materials. If set to 1, materials are copied directly into the dgn as local materials. Use this when you need a dgn to be self-contained and portable. Set it to 0 if you are within a collaborative environment where you can manage the material across multiple projects.

Current Limitations:

Limitations: Terrains

• All terrains less than 5 million points will go directly into the iModel.
• Terrains greater than 5 million points, for performance reasons, require the use of a Context Data Share which would need to be setup for the project.
• Be aware that large terrains can greatly increase processing times.
• Where terrain source graphics exist like spot levels / breaklines / contours, it is recommended that the terrain is created in it's own file referencing the source graphics and that the source graphics are turned off as all are contained in and so can be displayed in the resulting terrain. This avoids unnecessary elements being processed when converting to the imodel that can lead to excessive processing times.

Limitations: Subsurface

• Drainage & Utilities data that is shown in the Civil properties will be included
• The iTwin Synchronizer will also include properties from the Drainage & Utilities databases

Limitations: OpenSite

• Currently, OpenSite properties will not be included in the iModel.

Video:

www.youtube.com/watch