Bentley MicroStation Design (V8) Reader Parameters

Group Elements By

Specifies the overall structure of the schema and data for DGN file reading.

The schema will be generated using level numbers in the source dataset as FME feature types.

The schema will be generated using level names in the source dataset as FME feature types.

The schema will be generated using all the possible Design geometry types as FME feature types. This list is set by the reader capability and is not limited to geometries which occur in the given source dataset.

The schema will be generated using both the level numbers and elements in the source dataset. The level numbers will be used to create FME feature types as in the Group by Level selection; however, the attributes of all the elements belonging to a level will be accumulated and also added to the FME feature type for that level.

The schema will be generated using both the names and elements in the source dataset. The level names will be used to create FME feature types as in the Group by Level Names selection; however, the attributes of all the elements belonging to a level will be accumulated and also added to the FME feature type for that level.

Element Options

The reader can be configured to output all the elements composing cells, or symbols. This is useful if the graphical representation of the Design file is to be preserved. This is true when, for example, a Design file is translated to a GIF image.

Select this option to expand the cells into separate features.

Preserve Named Cell Insert Points

When selected, outputs the insertion point of the named cell.

Preserve Unnamed Cell Insert Points

When selected, outputs the insertion point of the unnamed cell.

Read Reference up to First Level: (Deprecated: Superseded by the parameter Max Depth of Reference Files to Read)

Reads all the supported elements in the external reference files attached to the source dataset up to the first level of nesting only. This parameter is valid only if Read Elements from Reference Files is selected.

Specifies reading of supported elements from the external reference files attached to the source dataset for a number of levels. Files referenced by the source dataset are considered level 1, and nested references are considered further levels.

This parameter is valid only if Read Elements from Reference Files is selected.

This parameter is applicable to version 8 only, since models are supported in version 8 but not in version 7.

When selected, uses the model of the parent file of the xref file.

Note  The reading of reference file elements as features with an igds_type of igds_xref is affected by the Read File References as Elements parameter (not this parameter).

This parameter is valid only if Read Elements from Reference Files is selected.

This parameter is applicable to version 8 only.

When selected, reads any external reference files attached to the source dataset as features with an igds_type of igds_xref.

Note  The reading of all supported elements in external reference files is affected by the Read Elements From Reference Files parameter (not this parameter).

Select this option to display tags. Elements in a design file may have user-defined attributes attached to them, in a form called Tags. FME can read (but not write) these attributes. In addition, to supply a value for a user-defined attribute, tags may also be displayed as text in the original design file.  

When reading a design file, FME first scans for all the tag data elements and tag set definition elements. Then as it reads each graphical element from the design file, it uses the element association ID to reconnect the data and attribute names with the graphical element. All the tag data values are then added to the feature returned into FME.

Attribute Options

Read Tag element data as attributes.

This parameter is applicable to version 8 only.

Select this option to read XAttribute information. Elements in a design file may have user-defined attributes attached to them in a form called XAttributes. Such attributes can be read (but not written, with the exception of File Link XAttributes) by FME. They are represented as list attributes, and contain various typed information chunks such as XML fragments, as is the case when they represent XML-based Feature Modeling (XFM) data.

If Item Types exist on the file, they will be read as attributes, with igds_item_names{} listing all item types found on the feature. For more information, see Item Types

Linkage Extraction

Linkage Extraction boxes allows you to extract MSLinks and/or FRAMME attribute linkage values from the Source Design File. Only the first three linkage values will be extracted.

These linkage values can be used to join the graphical data held in the design file to the MSLINK field in the related database table. The entity number that is extracted is used to determine the relevant table that holds the attributes (the database contains a table called MSCATALOG which maps entity numbers to table names).

The UFID is extracted together with the basename of the design file. These two items form a compound key that can be joined to the related FRAMME database.

Model Selection Options

Models and sheets in a Design file can have different spaces, which are essentially the coordinates and units that they represent. This can lead to confusing results if you attempt to view them together in the FME Data Inspector. FME defaults to this combined view, but this parameter allows you to refine the view and read only selected models.

Specifies that the reader should read only the selected models in the data.

Models: Specifies which models should be read.

Coordinate Units By

These parameters control the conversion between UORs in the Design file and FME coordinates. There are three possibilities: 

Note that for each of these conversions, the coordinates of an FME feature will represent the coordinates as scaled by the UOR to FME Units Scale Factor. Those coordinates are all relative to working coordinates.

Coordinate Units Value Description

Master

 The UORs read from the Design file are converted into master units, according to the conversion factor read from the Design file header, before being stored in an FME feature.

Sub

 The UORs read from the Design file are converted into subunits, according to the conversion factor read from the Design file header, before being stored in an FME feature.

UOR

 The UORs read from the Design file are stored directly in an FME feature with no conversion.

Override Global Origin

These parameters are usually used only when reading Design files that have bad header information. If FME detects a difference between these settings and those read from the Design file, a warning is output to the log file, and these settings take precedence.

You can override the global origin, which is by default at the center of the design plane/cube, by setting the values of X, Y, and Z. Setting these values overwrites the global origin as read from the .dgn file. Valid values are unsigned 32-bit integers.

  • X: The global origin of X, measured in UORs, from the lower left corner of the design plane/cube.
  • Y: The global origin of Y, measured in UORs, from the lower left corner of the design plane/cube.
  • Z: The global origin of Z, measured in UORs, from the lower left corner of the design plane/cube.

Additional Attributes to Expose

Use this parameter to expose Format Attributes in FME Workbench when you create a workspace:

  • In a dynamic scenario, it means these attributes can be passed to the output dataset at runtime.
  • In a non-dynamic scenario, this parameter allows you to expose additional attributes on multiple feature types. Click the browse button to view the available format attributes (which are different for each format) for the reader.
 

A search envelope (also known as a bounding box) is a rectangular area that defines a geographic area. In FME, the easiest way to define a search envelope is to use search envelope parameters.

Defining a search envelope is the most efficient method of selecting an area of interest because FME will read only the data that is necessary – it does not have to read an entire dataset. Search Envelope parameters apply to both vector and raster datasets and can be particularly efficient if the source format has a spatial index.

Most FME readers have parameters to define the search envelope of data that is being read:

Screenshot with blank search envelope min and max x and y parameters

The parameters include the x and y coordinates of the bounding box as well as a parameter that defines the coordinate system.

How to Define the Bounding Box

Using the minimum and maximum x and y parameters, define a bounding box that will be used to filter the input features. Only features that intersect with the bounding box are returned. Note that the bounding box intersection is not a full geometry intersection (based on spatial relationships) that would be returned by a transformer like the SpatialFilter.

Note  If all four coordinates of the search envelope are left at 0, the search envelope will be disabled even if this option is checked.

Search Envelope Coordinate System

Specifies the coordinate system of the search envelope if it is different than the coordinate system of the data. The coordinate system associated with the data to be read must always be set if this parameter is set.

If this parameter is set, the minimum and maximum points of the search envelope are reprojected from the Search Envelope Coordinate System to the reader’s coordinate system prior to applying the envelope.

Clip to Search Envelope

The underlying function for Use Search Envelope is an intersection; however, when Clip to Search Envelope is checked, a clipping operation is also performed.

  • When left unchecked (set to No), features that overlap the boundary will be included in their full (unclipped) form.
  • When checked (set to Yes), this option instructs FME to clip features to the exact envelope boundary. FME removes any portions of imported features being read that are outside the search envelope.

Clip to Search Envelope: No

Clip to Search Envelope: Yes

Any features that cross the search envelope boundary will be read, including the portion that lies outside of the boundary.

Any features that cross the search envelope boundary will be clipped at the boundary, and only the portion that lies inside the boundary will be read.

The search envelope includes the bounding box and the extent of the raster.

The search envelope includes only the area within the bounding box.

The raster size will still match the bounding box, but the area without data will be filled with Nodata values to represent the absence of data, if the source raster has them.

Raster Nodata may be a single value across all bands, a single value per band, or a separate alpha or transparency band that indicates the lack of data values (this is more common in images than other types of rasters).

Advanced

When selected, each component of a complex chain to be returned as its own feature and no feature will be returned for the complex chain as a whole.

When deselected, all elements of the complex chain will be merged into a single linear feature, any arcs in the complex chain will be converted into linestrings, and any linkages on the component elements themselves will be lost.

When selected, the reader splits the multi-text into text nodes and outputs the member text elements as individual text elements. If the multi-text had any linkage attributes, these will be propagated to the component elements.

When deselected, the text elements are not split.

Controls the way the dimensions are imported.

When selected, the dimensions are exploded into its pieces.

When deselected, the dimensions are imported as an aggregate. When dimensions are imported as aggregates, the arcs are stroked and text features are output as list attributes only. For example, if you're performing a DGN-to-DGN translation and you do not select this option, the text features will be lost.

Select this parameter if you have an Esri World file (*.wld or *.wld3) that you want FME to use when determining the coordinates for features in your dataset.

FME will search the folder of the dataset for a file with the same name as your dataset but with a .wld or .wld3 extension. If it cannot find a file with that name, it will then look for the file esri_cad.wld or esri_cad.wld3 within the dataset folder. If either of those files exists, FME will use the information in the files to translate the coordinates of the features in the dataset to their new geospatial coordinates.

If the files cannot be found, then the translation will continue, using the coordinate information found in the dataset and without performing any additional transformation.

This parameter controls whether or not curve elements will be stroked into lines by adding vertices.

When selected, the control points of the curve are connected into a line. This option preserves the original control points and the end slopes. This is primarily used for DGN-to-DGN translations.

When deselected, the control points are used to interpolate a linear representation of the curve. It strokes (vectorizes) the curve (that is, it preserves the shape of the curve). Deselecting this checkbox enables the parameter Number of interpolated curve vertices.

Remove the duplicate points (same x and y coordinates) from the geometry of the feature.

When selected, allow the assumption that working units are equal to master units. This affects all calculations involving conversion from UOR coordinates to coordinates of any known unit, such as when the UORs Per Sub Unit or UORs Per Master Unit parameters are defined.

When deselected, the working unit of the Design file will be additionally used in the calculation of coordinates.

The number of ground units per UOR. Valid value: a double-precision floating point number.

The number of UORs per sub unit. Valid value: an unsigned integer ratio.

This parameter is used only if UOR to FME Units Scale Factor is not present.

The number of sub units per master unit. Valid value: an unsigned integer ratio.

This parameter is used only if UOR to FME Units Scale Factor is not present.

If an elevation shift is desired to build "fake" 3D topology, this is the scaling factor used to generate the shift.

Specifically, the Z value is divided by this factor and the result is added to the X value.

This parameter controls the number of points per segment when the curve is interpolated into a line. Used when Preserve Curves is not selected.

If set, this parameter indicates that text features may use the Resource (RSC) font file specified to assist in text element placement, size, and range calculation.

This only applies to text features with RSC font IDs specified in the igds_font attribute, and which are found in the specified RSC file to be symbolic fonts. If this parameter is not specified, text elements with symbolic RSC fonts will have their placement, size, and range estimated.