Bentley MicroStation GeoGraphics Writer Parameters
Database Connection
Select ODBC, Access MDB, or Oracle.
Specify the path and filename of the Access database file to write.
Sets the version of the output Microsoft Access file. Access file versions 97 and 2000 are the supported types. By default, an Access 2000 file is created.
Enter the ODBC data source that points to your MGE database. Depending on your database, you may also have to enter a username and password.
Enter the name of the Oracle service.
Enter the username and password to access the service.
General Table Names
Specifies the name of the feature table to be written. This defaults to the name feature.
Specifies the name of the category table to be written. This defaults to the name category.
Design File Parameters
Controls whether or not fill linkages will be written out for ellipses, shapes, and solids.
Select this option to automatically adjust the origin and scaling of the seed file to provide an optimum set of parameters for the input data.
Specifies how FME feature coordinates are interpreted and converted into Units of Resolution (UOR). The UOR (which is defined by the seed file) is the smallest increment of precision to which the drawing data can be stored in the system.
- Master Units: UORs are converted into master units.
- Sub Units: UORs are converted into subunits.
- UORs: UORs are written as raw UOR coordinates.
Specifies how you want to store the two-point line features.
- Type 3 Elements: Two-point line features are stored as type 3 line elements.
- Type 4 Elements: Two-point line features are stored as type 4 line elements.
Set the location of the seed file.
The seed file controls whether or not the output file is two- or three-dimensional, and sets the models, global origin, and unit information of the destination file.
The file name of IGDS cell library, which contains the definitions of cells which may later be output.
Write Optimization
This parameter determines how many features are pushed to the remote server at a time.
Setting a high value for the transaction size can result in increased performance, since there can be significant overhead associated with each network request.
The default is 1.
Selecting this parameter instructs FME to immediately write each row of data to the database, rather than batching up writes into bulk arrays. Bulk arrays are normally preferred, as they require fewer trips to the database in order to store the data, but are not supported by some databases. (In particular, some ODBC drivers, such as the Excel driver, do not support bulk array loading.)