Default Configuration File

The Bentley Map Mobile Converter default configuration file MapMobileConverter.config.xml which is used by default when no configuration file has been specified on the MapMobileConverter.exe command line using the --config-file= option has the following data conversion settings.

Line 2 includes the required <MapMobileConverterSchema> element that may contain one or more data conversion settings. A reference to "MapMobileConverter.config.xsd" is provided for those familiar with use of XML Schema Definition (XSD) files.

Features

This required section defines element search criteria and feature creation settings. The <Features> element that may contain one or more <feature> child elements which define conversion settings used to create Bentley Map Mobile features from Bentley Map or MicroStation data. As elements in the input design or reference file(s) are processed, the <feature> conversion settings are evaluated from top to bottom, with the first conversion setting that matches the specified search criteria being applied. Therefore, the more restrictive search criteria should be specified higher in the list.

MicroStation Element Selection

Line 3 includes the <Features> element that may contain one or more <feature> elements which define conversion settings used to create Bentley Map Mobile features from Bentley Map or MicroStation data. As elements in the input design or reference file(s) are processed, the <feature> conversion settings are evaluated from top to bottom, with the first conversion setting that matches the specified search criteria being applied. Therefore, the more restrictive search criteria should be specified higher in the list.

Lines 4 thru 18 describe conversion settings to create Bentley Map Mobile features from simple MicroStation elements. The feature name and alias attributes use the built-in variables $(Element.Level) and $(Element.CellName) to create feature classes that map to the MicroStation element level or cell name. The feature type attributes "point-text", "point-cell", "linestring/curve" and "point-text" are used to define which types of geometry are to converted for each feature class. The feature category attribute is used to create map layer categories with names of "Text", "Cells", "linear", "Polygon" and "Polygon (filled)" indicating the geometry types. The feature priority attributes are used to set feature class display priorities so that text, cells and linear elements are displayed on top of polygons, with any filled polygons displayed below everything else. The highest display priority is 0 so use of priority="0" attribute ensures the feature instances are always displayed last, on top of everything else.

Lines 9 thru 11 and 14 thru 16 use the <Symbology> element which specifies one or more element attributes that must match before an element is converted to the feature class. All polygon geometry type elements are added to a "Polygon_$(Element.Level)" feature class, then using <Filled>false</Filled> or <Filled>true</Filled> search criteria, those feature classes are placed in either "Polygon" and "Polygon (filled)" categories.

Line 18 defines criteria to convert any MicroStation elements not previously matched in lines 5 thru 17, creating "Other_$(Element.Level)" feature classes and placing all of them in an "Other" category. No feature type attribute is used to ensure all element types are matched.

Bentley Map XFM Feature Selection

Lines 20 thru 25 describe conversion settings for existing Bentley Map XFM feature instances. Use of name="" attribute matches any XFM feature name. Based on geometry types, "Text", "Cells", "linear" and "Polygon" categories are assigned. The feature priority attributes are used to set feature class display priorities so that text, cells and linear elements are displayed on top of polygons, with any filled polygons displayed below everything else. The highest display priority is 0 so use of priority="0" attribute ensures the feature instances are always displayed last, on top of everything else.

Lines 5 and 21 both define search criteria using type="point-text" and searchable="false" which prevent the text string values from being added to the full-text search (FTS) index. Setting searchable="true" adds text string values to the full-text search (FTS) index for increased search performance.

Please refer to the "XML Schema Definition" section for further details on supported configuration file settings.