Table 6.181—DRM_Model
Property |
Description |
|||||||||||||||||||||
Superclass |
||||||||||||||||||||||
Class |
· <DRM Model> |
|||||||||||||||||||||
Subclass |
· none |
|||||||||||||||||||||
Definition |
An object of this DRM class specifies a collection of <DRM Polygon>s and surfaces defined in the same coordinate frame that represent some "thing". A <DRM Model> may have no <DRM Point>s or <DRM Polygon>s (i.e., the "null model"). |
|||||||||||||||||||||
Example(s) |
· The lowest level of detail of a tank's turret. · A 1 degree by 1 degree tile of terrain containing thousands of instances to other Models. · An aircraft carrier that has both a geometric representation and a feature representation. · A data provider has an overall <DRM Model> (call it "car") made up of several components: top, two sides, four tires, back, front, underneath. When put into the SEDRIS <DRM Model Library>, each of these components (as well as the overall "car" placeholder) is represented as an instance of <DRM Model>. The organization of the data provider has a place in its database where "car" is instanced, so that at an IG the "car" appears. This is represented in the resulting SEDRIS transmittal by a <DRM Geometry Model Instance> of "car" appearing in the scope of a <DRM Environment Root>. No other <DRM Model>s in this data provider's mapping to SEDRIS can reference the "car" <DRM Model>. · A producer has a <DRM Model> "plane" that has several components (two wings, tail, fuselage, etc). However, the producer has a <DRM Model> "ship" that instances "plane" to identify a ship with planes on its deck. The transmittal will instance "ship", and the <DRM Model> field of "ship" will have "model_reference_type" set to ROOT_MODEL. Since the <DRM Model> "plane" could be used elsewhere in the transmittal, its instance under "ship" will have "model_reference_type" set to BOTH_ROOT_AND_COMPONENT. |
|||||||||||||||||||||
Inherited field elements |
|
|||||||||||||||||||||
Field elements |
|
|||||||||||||||||||||
Associated to (one-way) (inherited) |
· none |
|||||||||||||||||||||
Associated to (one-way) |
· none |
|||||||||||||||||||||
Associated by (one-way) (inherited) |
· none |
|||||||||||||||||||||
Associated by (one-way) |
· none |
|||||||||||||||||||||
Associated with (two-way) (inherited) |
· none |
|||||||||||||||||||||
Associated with (two-way) |
· none |
|||||||||||||||||||||
Composed of (two-way) (inherited) |
· none |
|||||||||||||||||||||
Composed of (two-way) |
· zero or one <DRM Classification Data> · zero or one <DRM Feature Model> · zero or one <DRM Geometry Model> · a bounded set of 0..2 <DRM Hierarchy Summary Item>s · zero or one <DRM Interface Template> · zero or one <DRM Overload Priority Index> · zero or one <DRM Point Of Contact> · zero or more <DRM Primitive Summary Item>s · zero or more <DRM Property Value>s · zero or one <DRM Spatial Domain> · zero or one <DRM Time Constraints Data> |
|||||||||||||||||||||
Composed of (two-way metadata) (inherited) |
· none |
|||||||||||||||||||||
Composed of (two-way metadata) |
· zero or one <DRM Access> · zero or more <DRM Browse Media>s · zero or one <DRM Citation> · zero or more <DRM Cross Reference>s · zero or one <DRM Data Quality> · zero or one <DRM Description> · zero or one <DRM Keywords> · zero or one <DRM Point Of Contact> |
|||||||||||||||||||||
Component of (two-way) (inherited) |
· none |
|||||||||||||||||||||
Component of (two-way) |
· one <DRM Model Library> |
|||||||||||||||||||||
Constraints |
· Hierarchy summary constraints · LSR model and reference surfaces · Model reference type constraints |
|||||||||||||||||||||
Notes |
1 A meaningful short name. A full description will be in the <DRM Description> component. This name is unique in a transmittal depending on the model_reference_type enumeration. 2 Set to TRUE only if this model is used by the vendor as a model that moves throughout the database (e.g. car, plane, tank, ship). This flag is used to identify information at the top level of model data; so it can only be set at the level where "model_reference_type" is TRUE. 3 Only takes effect if the srf_parameters are LSR. This flag allows a producer to say "This LSR Model is in metres" vs. "This LSR Model is unitless (it has no units)". LSR models are commonly in metres when modeling real-world things (e.g., tanks, ships, trees). Sometimes those models are scaled when instanced (trees are commonly scaled, but ships and tanks are not). Some LSR models are purely unitless (e.g., a logo model). 5 Set to TRUE only if this model contains Control Links attached to Transformations, which allow or limit motion (e.g., vanes on a windmill). |
|||||||||||||||||||||
Class diagram |