Class Name: Oct Tree Related Geometry
Definition
An aggregation of Geometry Hierarchies in
which each component Geometry Hierarchy
represents a branch of an Oct Tree. The octant represented by a branch is
specified by the Geometry Oct Tree
Data associated with that branch. The bounding region that the
Geometry Hierarchy components occupy is
defined by the Spatial Domain of the
Oct Tree Related Geometry.
Primary Page in DRM Diagram:
Example
--Example needed here --FAQs
- If an Oct Tree Related
Geometry has less than 8 components, why is the data being organized
under an Oct Tree Related Geometry
at all?
- An Oct Tree Related Geometry is
used when an object in the hierarchy contains spatial components that
occupy a certain octant. These octants might not contain
Primitive Geometry, which is why this
class can have less than 8 components.
- Where is the Spatial Domain component?
- Oct Tree Related Geometry
automatically has a Spatial Domain component,
because it is a Geometry Hierarchy.
Unlike Geometry Hierarchies in general,
Oct Tree Related Geometry has a
business rule stating that the Spatial Domain
component is mandatory.
Constraints
Associated by (one-way)(inherited)
Associated with (two-way)(inherited)
Composed of (one-way)(inherited)
- optionally, some {ordered} Attribute Set Indices
- optionally, a Classification Data
- optionally, some Property Tables
- optionally, some Property Table References
- optionally, some Property Values
- optionally, a Reference Surface
- optionally, some Sound Instances
- optionally, a Spatial Domain
- optionally, a Bounding Volume
- optionally, a Center of Buoyancy
- optionally, a Center of Mass
- optionally, a Center of Pressure
- optionally, some Collision Volumes
- optionally, a Conformal Behavior
- optionally, a LSR Transformation
- optionally, an Overload Priority Index
- optionally, some Property Descriptions
- optionally, a Stamp Behavior
- optionally, some {ordered} Colors
- optionally, a Light Rendering Properties
- optionally, a Rendering Properties
- optionally, some {ordered} Image Mapping Functions
- optionally, a Rendering Priority Level
Composed of (two-way)(inherited)
Composed of (two-way)
Composed of (one-way metadata)(inherited)
Component of (two-way)(inherited)
- optionally, some Alternate Hierarchy Related Geometries through Geometry Hierarchy Data
- optionally, some Animation Related Geometries
- optionally, some Classification Related Geometries through Geometry Classification Data
- optionally, an Environment Root
- optionally, some Geometry Separating Plane Relations through Geometry Separating Plane Data
- optionally, a Geometry Model
- optionally, some Level of Detail Related Geometries through Geometry Level of Detail Data
- optionally, some Oct Tree Related Geometries through Geometry Oct Tree Data
- optionally, some Time Related Geometries through Geometry Time Constraints Data
- optionally, some Perimeter Related Geometries through Geometry Perimeter Data
- optionally, some Quad Tree Related Geometries through Geometry Quad Tree Data
- optionally, some Spatial Index Related Geometries through Geometry Spatial Index Data
- optionally, some State Related Geometries through Geometry State Data
- optionally, some Union of Geometry Hierarchies
Notes
Fields Notes
If SE_TRUE, then for any object that exists 'below' this aggregation,
each object will appear in only one 'branch' of this aggregation.
If SE_FALSE, then objects may appear in multiple 'branches' of this
aggregation.
If SE_TRUE, then each 'branch' from this aggregation is its own,
independent topology. If SE_FALSE, then all of the branches exist
within the same topology.
If true, then each 'branch' strictly follows the rules of this
aggregation. If false, then each 'branch' might bend the rules a bit.
For example, if this is a spatial aggregation, than a value of true
indicates that objects will *not* cross the spatial extents defined
by this aggregation relationship, and a value of false indicates
that objects might cross those bounds. For another example, if this
is a time-based aggregation, then a value of true indicates that all
branches will only contain data valid for the times specified for
each branch, and a value of false indicates that the branches have
the option of including data that falls outside of the specified
time ranges for that branch.
Prev: Oct Tree Related Features.
Next: Overload Priority Index.
Up:Index.