This section explains concepts fundamental to geometry tagging.
Component Tags
Tags are string-based information stored directly on the topological components of a shape's geometry asset. Each face, edge, and vertex may have an arbitrary number of tags. Their purpose is to identify semantically different parts of the geometry, for example when using the comp operation.
A tag is a string that defines its name. Example: "Name"
Tag hierarchy
Tags are hierarchically grouped with the name separator "." (dot). Example: "Name1.Name2", "Name1.Name3".
The dot-separated names within a tag are referred to as subtags.
Tag queries
A tag query is a string that may include wildcards to replace subtags. There are two wildcards:
? (question mark) | Matches exactly 1 subtag. Example: "?.Name" |
* (asterix) | Matches 1 or more subtags. Example: "Name1.*.Name2" |
Based on the hierarchical grouping, the tag query "Name1" matches not only the exact tag "Name1", but also tags with additional subtags, such as "Name1.Name2", "Name1.Name2.Name3".
Related
Auto-Tags
Selected geometry creation operations automatically apply predefined tags. These tags identify semantically different parts of the output geometry.
Auto-tags applied by a certain operation remain accessible until the operation is called again, replacing them with new ones.
Operations applying auto-tags on faces
Face components are categorized into three principle types: bottom, side, and top. The bottom components correspond to the original faces, while the new side faces may be further categorized as either inner or outer, depending on whether they emanate from a hole.
Extrude
See extrude operation. |
Envelope
See envelope operation. |
Taper
See taper operation. |
Roofs
All roof operations apply the same base tag "roof".
See roofGable operation. | |
See roofHip operation. | |
See roofPryamid operation. | |
See roofRidge operation. | |
See roofShed operation. |
Boolean 3D operations
See union operation. | |
See subtract operation. | |
See intersect operation. |
Operations applying auto-tags on edges
The setback operation and its variants — setbackToArea, setbackPerEdge, shapeLUO and splitAndSetbackPerimeter — automatically tag edge components using the same base "setback".
Shape
|
Remainder
|
Tag propagation
In general, geometry-modifying operations preserve tags on existing components and propagate tags to newly constructed components when applicable.
Geometry subdivision
Subdivided edge and face components keep their tags. Newly constructed components have no initial tags.
Face tag propagation
New faces constructed on top of existing ones get the tags of their source face.
Edge tag propagation
New faces emanating from existing edges get the tags of their source edge.
Here the edge auto-tags applied by the setback operation are automatically propagated to the extruded side faces.
| |
Example envelope operation.
| |
Example offset operation.
|
Also see the setTagsFromEdgeAttrs operation for more examples.
Geometry cleanup
The cleanupGeometry operation maintains existing tags, preventing the removal of tagged edges and edges between faces with different tags.
The cleanupGeometry operation only merges faces with the same tags.
|
Operations that clear all tags
By design
These operations replace the current shape's geometry asset, thus existing component tags are cleared.
- i (insert), insertAlongUV operations
- primitiveXXX operations
- footprint operation
- resetGeometry operation
Unsupported
These operations do (currently) not support working with component tags and clear all tags.
- splitArea operation
- scatter operation
- reduceGeometry operation