Some operations create an internal domain for the output map of the operation. For some operations this happens automatically; for other operations you can specify whether to store the output domain as a separate object, or have the output domain stored by the output map (internal domain).
When an internal Class domain or an internal Picture domain is created, then also an internal representation is created. Internal representations are stored by the output map and not as a separate object.
The software provides the possibility of using internal domains and internal representations to reduce the number of domains and representations shown in the Catalog.
Operations which always create an internal domain for the output map:
|
Both the output map and its attribute table will use an internal UniqueID domain; domain items are named 'Area 1', 'Area 2', etc. |
|
|
Both the output map and its optional attribute table will use an internal Class domain and internal representation. Domain items are named 'Cluster 1', 'Cluster 2', etc. |
|
|
When using the Dynamic/Heckbert option: internal Picture domain and internal representation. |
|
|
When merging two Pictures: internal Picture domain and internal representation. |
|
|
When the Single Name option is used and when the input map has a class domain: internal class domain which contains only one item called 'Boundary'. When the Single Name option is used and when the input map has an ID domain: internal ID domain which contains only one item called 'Boundary'. When the Unique Names option is used, the output map and the attribute table will use an internally defined UniqueID domain containing several items like 'Boundary 1', 'Boundary 2', etc. |
|
|
When the Single Name option is used and when the input map has a class domain: internal class domain which contains only one item called 'Boundaries'. When the Single Name option is used and when the input map has an ID domain: internal ID domain which contains only one item called 'Boundary'. When the Unique Names option is used, the output map and the attribute table will use an internally defined UniqueID domain containing several items like 'Boundary 1', 'Boundary 2', etc. |
|
|
Both the output map and its attribute table will use an internal UniqueID domain. Domain items are either user-defined by a specified prefix, or when no prefix is specified: 'Pol 1', 'Pol 2', etc. when performed on a polygon map; 'Seg 1', 'Seg 2', etc. when performed on a segment map; 'Pnt 1', 'Pnt 2', etc. when performed on a point map . |
Operations which optionally create an internal domain for the output map:
|
When merging maps with different Class domains: new Class domain or internal Class domain with internal representation. Output domain contains all class names of all input maps. When merging maps with different ID domains: new ID domain or internal ID domain. Output domain contains all IDs of all input maps. |
|
|
When not using the Label Points option in the operation's dialog box: internal ID domain. When using the option Auto Identifiers option in the segment editor: internal ID domain. Domain items are named 'Pol 1', 'Pol 2', etc. |
|
To view or edit an internal domain/representation:
You can display and edit internal domains and representations in the same way as normal domains and representations.
Internal domains/representations do not have their own Properties dialog box and cannot be opened as a table.
See also: