General Data Exchange Information

This section contains information that is relevant to any data exchange with another application or format.

For format-specific information, see the following sections.

Format	For more information, see	Application see footnote 132
IGES	IGES File Exchange	“igesin.ma” “igesout.ma”
Parasolid XMT	Parasolid XMT File Exchange	“[[<xxx>]].ma”
ACIS SAT	ACIS SAT File Exchange	“satinout.ma”
CGM	CGM File Exchange	“cgmin.ma” “cgmout.ma”
STEP AP203	STEP AP203/AP214 File Exchange	“ap203in.ma” “ap302out.ma”
STL	STL File Exchange	“stlio.ma”

Basic terminology

The following terms apply to file exchange in general:

• Entity — The fundamental unit of data in an IGES, Parasolid, ACIS SAT, CGM, STL, or STEP AP203/AP214 file. In general, entities are the equivalent of DGN file elements.

• Receiving application — the application into which a file exported from MicroStation is imported.

• Sending application — The application that created a file that is imported into MicroStation.

• Product-definition data — The graphical information that describes a model in 2D or 3D, in real-world units, and with precision sufficient to create or build the actual product or model, such as a mechanical part, architectural model, site plan, or map. DGN files can store product-definition data.

• Picture data — The graphical information that draws a picture. Although real-world units and 3D are not required and the precision may be high, the information is usable only as an illustration. The CGM format stores picture data.

Choosing a translation

The best translation to use depends on factors that are unique to each translation, such as:

• the sending application or receiving application

• the type of data being translated

• whether you need to convert product-definition data or picture data

The CGM format cannot exchange product-definition data.

Preserving as much data as possible

Items in one system may not have exact equivalents in another other system. Also, items that are common to both systems may be expressed differently. Usually, the goal is to perform a translation that preserves as much data as possible.

If you perform frequent translations, you should learn about the MicroStation and the IGES, Parasolid, ACIS SAT, CGM, STL, or STEP AP203/AP214 formats and set up your models in a way that minimizes data loss. This chapter has some suggestions for doing this.

You should test the translation with small drawings that contain samples of all of the types of data used in your project.

Opening a 3D file

To import a 3D drawing file interactively, the open DGN file must be 3D. To open a 3D drawing file from the system command line, the translation seed file must be 3D.

Certain IGES entities cannot be represented in 2D. Unless you are certain that the IGES file is 2D, it is recommended that the open DGN file be 3D when the IGES file is imported.

The CGM format does not support 3D.

Keeping units and measurements correct

When opening an IGES, Parasolid, ACIS SAT, CGM, STL, or STEP AP203/AP214 file, you should ensure that the DGN file into which you place the file has appropriate working units for the type of data in the imported file.

For information about setting working units when importing an IGES, Parasolid, ACIS SAT, CGM, or STEP AP203/AP214 file, see Keeping coordinate units correct.

The CGM format does not store data in real-world units.

Using settings files

Import and export settings help make translation as accurate as possible with as little loss of “intelligence” as possible. After you set these for your project, you can save them in an import or export settings file that stores the settings as they were when the settings file was created or saved for a particular conversion.

Settings for	Adjusted in	Configuration variable	Default file
IGES
Import	Import IGES File dialog box	MS_IGESINSET	“igesin.sfi”
Export	Export IGES File dialog box	MS_IGESOUTSET	“igesout.sfi”
Parasolid XMT
Import	Parasolid XMT Import dialog box	MS_[[<xxx>]]INSET	[[<xxx>]]in.sfi
Export	Parasolid XMT Export dialog box	MS_[[<xxx>]]OUTSET	[[<xxx>]]out.sfo
ACIS SAT
Import	ACIS SAT Import dialog box	MS_[[<xxx>]]INSET	[[<xxx>]]in.sfi
Export	ACIS SAT Export dialog box	MS_[[<xxx>]]OUTSET	[[<xxx>]]out.sfo
CGM
Import	Import CGM File dialog box	MS_CGMINSET	“cgmin.sfi”
Export	Export CGM File dialog box	MS_CGMOUTSET	“cgmout.sfi”
STEP AP203/AP214
Import	STEP AP203/AP214 Import dialog box	MS_[[<xxx>]]INSET	[[<xxx>]]in.sfi
Export	STEP AP203/AP214 Export dialog box	MS_[[<xxx>]]OUTSET	[[<xxx>]]out.sfo

For example, the import settings file for IGES Import is pointed to by the MS_IGESINSET configuration variable. When you import an IGES file, the settings are read from this file. If an IGES import settings file does not exist, the default file “igesin.sfi” is created in the "Bentley\Workspace\system\data" directory.

Using a settings file helps to ensure a consistent translation. You may want to have a different import and export settings file for each sending application, receiving application, client, or project.

To attach a settings file other than the default

1. In the appropriate Import or Export dialog box, choose File > Settings File > Attach.
   The Attach Settings File dialog box opens.


2. In the Files list box, select the appropriate settings file.


3. Click OK.

To save the current import or export settings

1. In the appropriate Import or Export dialog box, choose File > Settings File > Save.
   The current settings are saved in the attached settings file.

To save a new import or export settings file

1. In the appropriate Import or Export dialog box, choose File > Settings File > Save As.
   The Save Settings File As dialog box opens.


2. Specify the filename and directory.


3. Click Save.

Log file

A log file is a text file in which translation statistics and diagnostics are saved. Diagnostics are the messages that display in the status box as a translation is in progress.

By default, the log file is saved with the same filename and directory as the file being translated and with the extension “.log.”

To specify an alternate log file

1. In the appropriate Import or Export dialog box, choose File > Log File.
   The Log File dialog box opens.


2. Specify the filename and directory for the log file.


3. Click OK.

Versions supported

The following versions of each format can be converted:

Format	Can import versions	Can export versions
IGES	2.0, 3.0, 4.0, or 5.0 fixed-length ASCII	4.0, 5.0, or 5.3 fixed-length ASCII
Parasolid XMT	All versions up to 13.0	7.0, 7.1, 8.0, 9.0, 9.1, 10.0, 10.1, 11.0, 11.1, 12.0, 12.1, or 13.0
ACIS SAT	All versions up to 6.0	1.5, 1.6, 1.7, 2.1, 3.0, 4.0, 5.0, 5.2, or 6.0
CGM	1.0	1.0
STEP AP203	International Standard (IS)	International Standard (IS)
STEP AP214	Draft International Standard (DIS)	Draft International Standard (DIS)