A display model specifies which set of layer files (feature layers) is loaded into the Display Manager and how they are styled. Apply different display models to render the data of a project in different ways. You can export and import display models to share with other users and across projects.
You can predefine separate display models for different use cases, modules, and extensions, such as land management, urban planning, green cadastre, utilities, COGO, plot, profiles. Then you can use the Display Model Manager to create display model by merging any of the predefined components.
The default display model contains all feature layers of all industry models. When you generate the graphic using the default display model, a default style applies to each feature class. The temporary default display model is loaded in memory, but not yet stored in the file system. You can modify the temporary display model and save it.
Note In the default display model, label feature classes are loaded as text layers if they have all of the following attributes:
You can extend an existing display model by adding new layer files. The display model files use references to store the layers. For example, open an existing display model, then add new layer files to the Display Manager, and save the files as a new display model.
You can specify autoload layers that are displayed automatically when you open a project. Use autoload layers as the context for the spatial selection of your viewport. For better performance, autoload layers should not contain too many details. For example, set the administrative boundaries as an Autoload layer. In the Display Model definition, you can set one or more layers as autoload layers.
You set up display models in AutoCAD Map 3D, and not in Infrastructure Administrator. You create a display model either by modifying the default display model, or by using the Display Manager to create and edit the styles for the feature layers.
By default, layers are added as reference. You can change this behavior in the reference options.
You can define display models that display the features in multiple drawings. That means that your display model can consist of several display maps. For each drawing window, you can define different styles. For example, define one window to display all feature layers, using basic styles. Define another window to display a selection of feature layers, using a thematic style. In an Electric project, you might use a second window to display the network in a schematic view. Both windows are connected to the database. Operations such as highlighting a feature apply to both windows.
Display models are stored in the file system in XML files. A display model consists of several files as shown in the following table.
| <display model name>.tbdm |
XML file that stores the name and related display model maps. A display model consists of one or more display model map files. |
| Map_<nr>.tbdmmap |
Display model map file: XML file that stores the size, position, and references to the feature layers of each window. If you define multiple windows, for each window one display model map file is used. |
| <feature class name>.LAYER |
Layer file (XML file). For each layer that is referenced in the display model map file. |
| Blockdefinitions_<nr>.DWG |
DWG file containing any block definitions that are referenced in the display model. In recent releases, the blocks are converted to enhanced stylization when the file is opened. Therefore, newer display models will not have DWGs with (local) blocks. Older display models may still have such files. |
| <prototype>.DWG | DWG file containing blocks. |
Steps in this workflow: