Class Name: Perimeter Related Features
Definition
An Aggregate Feature that spatially
organizes its component Feature Hierarchies
into a collection of (potentially) irregularly shaped regions, each defined
by a Feature Perimeter Data object.
That is, each component Feature Hierarchy
is contained within the perimeter area specified by the
Feature 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
Features contained within each tile would be
organized into one of the components of a
Perimeter Related Features object.
FAQs
- May the regions defined by the components of a
Perimeter Related Features object
overlap?
- No. The regions defined by the components of a
Perimeter Related Features object
should fully partition the topological surface.
- May the same Feature be contained within more
than one of the components of a
Perimeter Related Features object?
- Yes, provided that the
unique_descendants and
strict_organizing_principle flags in the
Perimeter Related Features object
are both set to false.
- Does each of the components of a
Perimeter Related Features object
form an independent topological surface?
- Normally, yes. In this case, the
independent_topologies flag in the
Perimeter Related Features
object should be set to true. However, the
Feature Topology objects in all 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 Colors
- optionally, some {ordered} Image Mapping Functions (notes)
- optionally, some Labels
- optionally, some Property Tables
- optionally, some Property Table References
- optionally, some Property Values
- optionally, a Rendering Priority Level
- optionally, a Spatial Domain
- optionally, a Reference Surface
- optionally, some Sound Instances
- optionally, some Property Descriptions
Composed of (two-way)(inherited)
Composed of (two-way)
Composed of (one-way metadata)(inherited)
Component of (two-way)(inherited)
- optionally, some Union of Features
- optionally, some Alternate Hierarchy Related Features through Feature Hierarchy Data
- optionally, some Classification Related Features through Feature Classification Data
- optionally, an Environment Root
- optionally, a Feature Model
- optionally, some Time Related Features through Feature Time Constraints Data
- optionally, some Level of Detail Related Features through Feature Level of Detail Data
- optionally, some Oct Tree Related Features through Feature Oct Tree Data
- optionally, some Perimeter Related Features through Feature Perimeter Data
- optionally, some Quad Tree Related Features through Feature Quad Tree Data
- optionally, some Spatial Index Related Features through Feature Spatial Index Data
- optionally, some State Related Features through Feature State Data
Notes
Composed of Notes
Added to support "attributes for derived objects."
That is, these components are used only to specify
texture mapping information for geometry that
is derived from the <Feature> by the consumer.
These <Image Mapping Functions> must use
<Image Anchor> components to specify the mapping.
Fields Notes
If true, then for any object that exists 'below' this aggregation,
each object will appear in only one 'branch' of this aggregation.
If false, then objects may appear in multiple 'branches' of this
aggregation.
If true, then each 'branch' from this aggregation is its own,
independent topology. If 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 Feature Topology.
Next: Perimeter Related Geometry.
Up:Index.