ISO/IEC 18023-1:200x(E) — Table 6.96 DRM_Geometry

Table 6.96 — DRM_Geometry_Model

Property

Description

Class

<DRM Geometry Model>

Superclass

<DRM SEDRIS Abstract Base>

Subclass

None.

Definition

An instance of this DRM class is a collection of geometric attributes and the necessary hierarchy and attributes required to build a renderable component of the transmittal, defined in the single spatial reference frame specified by its <DRM Model> aggregate.

Class diagram

Figure 6.112 — DRM_Geometry_Model

Inherited field elements

Field name	Range	Field data type
None

Field elements

Field name	Range	Field data type
None

Associated to (one-way) (inherited)

None.

Associated to (one-way)

None.

Associated by (one-way) (inherited)

None.

Associated by (one-way)

zero or more <DRM Geometry Model Instance> instances¹

Associated with (two-way) (inherited)

None.

Associated with (two-way)

None.

Composed of (two-way) (inherited)

None.

Composed of (two-way)

zero or more <DRM Attachment Point> instances
zero or more <DRM Contact Point> instances²
zero or one <DRM Geometry Hierarchy> instance³
zero or one <DRM LSR Transformation> instance⁴

Composed of (two-way metadata) (inherited)

None.

Composed of (two-way metadata)

zero or one <DRM Access> instance
zero or more <DRM Cross Reference> instances
zero or one <DRM Data Quality> instance
zero or one <DRM Description> instance

Component of (two-way) (inherited)

None.

Component of (two-way)

one <DRM Model> instance

Constraints

Clarifications

¹ An association from a <DRM Geometry Model Instance> instance to a <DRM Geometry Model> indicates that the <DRM Geometry Model Instance> instances that particular <DRM Geometry Model>.

² This allows explicit definition of where the <DRM Model> contacts the terrain surface.

³ This is actually required, except when the Non empty Model constraint is applicable.

⁴ This allows a data provider to specify a uniform model orientation within a <DRM Model Library>. (Note that a data provider is not required to do so.)

Example(s)

The representation of the hull of an M1 tank.
A <DRM Geometry Model> representing a missile pointing down the -Z axis. The <DRM Geometry Model> is aggregated by a <DRM Model>, which in turn is part of a large <DRM Model Library>, in which the missiles are expected to point down the positive Y axis. To be consistent with the other <DRM Models> in the <DRM Model Library>, the missile's <DRM Geometry Model> has an <DRM LSR Transformation> to reorient it to point down the positive Y axis.
A <DRM Geometry Model>. may be as large and complex as a large terrain model, or as simple as a tank's turret at the lowest level of detail.