Class Name: Perimeter Related Geometry
Definition
An Aggregate Geometry that spatially
organizes its component Geometry
Hierarchies into a collection of (potentially) irregularly shaped
regions, each defined by a Geometry
Perimeter Data object. That is, each component
Geometry Hierarchy is contained within
the perimeter area specified by the
Geometry Perimeter Data associated
with that component.
Primary Page in DRM Diagram:
Example
- The spatial extent of a thematic coverage might be divided up into a
collection of tiles. Due to political boundaries or shorelines, some of
these tiles might have irregular shapes. The
Geometry contained within each tile would be
organized into one of the components of a
Perimeter Related Geometry object.
FAQs
- May the regions defined by the components of a
Perimeter Related Geometry object
overlap?
- No. The regions defined by the components of a
Perimeter Related Geometry object
should fully partition the topological surface.
- May the same Geometry be contained within more
than one of the components of a
Perimeter Related Geometry
object?
- Yes, provided that the
unique_descendants and
strict_organizing_principle flags in the
Perimeter Related Geometry
object are both set to false.
- Does each of the components of a
Perimeter Related Geometry object
form an independent topological surface?
- Normally, yes. In this case, the
independent_topologies flag in the
Perimeter Related Geometry
object should be set to true. However, the
Geometry Topology objects in all of the components may also form a
single topological surface, in which case the
independent_topologies flag should be set to false.
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: Perimeter Related Features.
Next: Point.
Up:Index.