Smart Interop Publisher can translate MicroStation .dgn files so that each property label display is converted to a standard one for all target applications. For MicroStation V8 .dgn files, you have settings that allow you to translate reference models and one or all design models that are in the .dgn file. These options are described in the workflow below.
Requirements and Considerations
-
Smart Interop Publisher requires MicroStation V8 2004 Edition or later installed on the client system performing the translations.
-
For MicroStation V8 .dgn files, Smart Interop Publisher supports SmartSolids that are contained in the MicroStation V8 files. Smart Interop Publisher automatically processes any MicroStation V8 file in the Files list, and changes the SmartSolid display from wireframe to surface.
-
Smart Interop Publisher can translate tags visible in any MicroStation (1-8) view. The software translates tags as graphic objects that can be selected in Smart Review and SmartPlant Markup, and has properties.
-
Use the Keep named views MicroStation translation option to allow Smart Interop Publisher to translate named views into view groups that can be displayed in Smart Review.
-
For any V8 .dgn files, Smart Interop Publisher supports translating models of type "design" only out of design, sheet, and drawing models. MicroStation V8.05\08.09 treats drawing models also as design models. The following list shows V8 (and i-model) graphics that are currently not supported by Smart Interop Publisher.
S. NO. |
Type |
Description |
1 |
5 |
Group Data |
2 |
8 |
Digitizer Setup Data |
3 |
9 |
Design File Header if level 8 |
4 |
10 |
Level Symbology |
5 |
20 |
not used |
6 |
38 |
DgnStore Component |
7 |
39 |
DgnStore Header |
8 |
66 |
MicroStation Application |
9 |
87 |
Raster Header |
10 |
88 |
Raster Component |
11 |
90 |
Raster Reference Attachment |
12 |
91 |
Raster Reference Component |
13 |
92 |
Raster Hierarchy Element |
14 |
93 |
Raster Hierarchy Component |
15 |
94 |
Raster Frame Element |
16 |
95 |
Table Entry Element |
17 |
96 |
Table Header Element |
18 |
97 |
View Group Element |
19 |
98 |
View Element |
20 |
99 |
Level Mask Element |
21 |
101 |
Matrix Header |
22 |
102 |
Matrix Int Data |
23 |
103 |
Matrix Double Data |
24 |
107 |
Extended Element (non-graphic) (complex) |
25 |
108 |
Reference Override Element |
26 |
110 |
Named Group Header |
27 |
111 |
Named Group Component |
Custom Mapping (Optional)
You can include new classes and properties, map any unmapped properties that you have added, and define unit of measure strings for property values using the customMICROSTATIONToR3DMapping.xls mapping template files. You can skip this section and use the default mapping provided with Smart Interop Publisher.
-
Review the MICROSTATIONToR3DMapping.xls default mapping file to see the classes and properties that are currently mapped.
-
In the CustomMappingFiles folder, make a copy of the customMICROSTATIONToR3DMapping.xls file and place it in another location.
-
Edit the custom mapping file to either modify property labels or add classes and properties.
Use a hyphen (-) instead of a colon (:) when you enter any custom property names that originally have a colon in front of the name. This is because Smart Interop Publisher removes a colon in the front of a property name during translation and replaces it with a hyphen. For example, if you enter :Status, the resulting translation displays -Status.
-
Save the edited mapping spreadsheet file in the Microsoft Excel 97-2003 Workbook (.xls) format. See Edit the custom mapping template file.
To display unit strings such as 'meters' or 'inches' with specific property values in the translated model, you can define the Units G column in the custom mapping file. See Set the units of measure (UoM) in custom mapping.
-
To set up custom mapping for a third-party format target such as Industry Foundation Classes (IFC), you must also create Hexagon schema (R3D)-to-IFC mapping. See Use custom mapping for third-party format targets.
Translation
When a MicroStation V8 .dgn file has an associated .drv file in the same source folder location, Smart Interop Publisher uses the .drv file for the translation.
-
Click the Smart Interop Publisher icon on your desktop .
-OR-
Click Start > All Programs > Intergraph Smart Interop Publisher. -
If you are not in the Projects View, click Projects.
-
Select or create a project to use in the grid.
-
Right-click the project, and then select Settings Menu > Project Settings Command.
-
Use the default settings, or make any required changes.
-
For Target Applications, select the Hexagon Asset Lifecycle Intelligence applications and third-party format to use. If you select a third-party format, verify that you have the required license. For example, you must have an IFC license to use the Industry Foundation Classes target.
Selecting only the target applications you require can produce a faster translation time. Smart Interop Publisher only generates files required for the selected target.
Right-click the project, and then select the Translation Settings Command. Smart Interop Publisher displays the Translation Settings Dialog.
-
Click New in the Select or Create Settings Group list, and type the name to use.
-OR-
Edit the Default translation settings group. -
Select MicroStation in the left pane.
-
Select the Keep units from V8 source file option to use the coordinate units in your .dgn source files. Otherwise, Smart Interop Publisher uses the working units defined in the translation settings. When you clear the option, the Working Unit boxes become available.
-
For Model Options:
-
You can turn on or off the translation of a reference model in the .dgn file.
-
Set the option to translate either the active, selected, or all design models in the .dgn file. Smart Interop Publisher uses the naming convention [design model file name]_[Smart Model name] for each generated Smart Model.
If you are selecting multiple source files to translate, the Translate each design model separately option affects the number of Smart Models that are created. This option causes Smart Interop Publisher to create a separate Smart Model for each design model that is in the selected V8 .dgn source file. For example, if you have two .dgn source files with each containing two design models, then Smart Interop Publisher generates four Smart Models.
-
-
Select any required Display Options, which affect the way the model looks when opened by a target application.
-
(Optional) In the Command line arguments box, type in any additional MicroStation options to be used during translation. When Smart Interop Publisher translates .dgn files, it invokes MicroStation in the background. See MicroStation options.
-
Click Save when you have finished defining translation settings.
-
Click Models to go back to the Models View.
-
Select each source file to use in creating the Smart Model, and then click Translate .
Use SHIFT+ or CTRL+ key combinations to select multiple source files.
-
On the Translate Source File Dialog, type a name and location for the Smart Model.
-
Select the settings group you defined earlier, or use the Default group.
-
If you used custom mapping, set the Mapping Options to Custom and select the Mapping Files Location of the custom mapping file you edited.
-
Click Translate.
-OR-
To schedule the translation for a later time, click Schedule to open the Schedule Translate Dialog. -
Open the Smart Models you created in the Intergraph target applications:
-
If you selected a non-Intergraph format target, open the model format file using your preferred third-party reader. For example, if you selected the Industry Foundation Classes (IFC) format target, use your own IFC reader to review the resulting Smart Model .ifc file.
Use Model Group to organize your grid to see all Smart Models associated to a specific MicroStation V8 source file. The Model Group column applies only to Smart Models translated from a MicroStation V8 source file containing one or more design models with the Translate each design model separately option selected. See MicroStation options.