The SEDRIS Data Representation Model
APPENDIX A - Classes State Related Features |
---|
A mechanism for specifying discrete states from a possibly continuous state value. Each discrete state corresponds to a branch of the <State Related Features> and is identified by the <State Data> for that branch; the state value itself is given by the state_tag of <State Related Features>.
Consider a <Feature Model> representing a road in various states of damage - in this example, after flooding. The road's topological connections are different in various states of damage, due to bridges being washed away and various road segments being blocked due to fallen trees and the like.
Consequently, the <Feature Model> consists of a State Related Features instance, with state_tag = EAC_GENERAL_DAMAGE_FRACTION and active_state = 0.0 % (that is, initially the road is undamaged, before flooding takes place).
The <State Data> for each branch indicates the range of percent damage for which that branch describes the road's feature topology.
No. <Control Link> instances can be used to provide a fine level of control over state by changing fields instead of representing states as different <Feature> instances.
SE_Boolean | unique_descendants; | (notes) |
---|---|---|
SE_Boolean | strict_organizing_principle; | (notes) |
EDCS_Attribute_Code | state_tag; | (notes) |
---|---|---|
SE_Property_Data_Value | active_state_value; | (notes) |
An association between two <Feature> instances indicates that they are alternate representations of the same environmental object.
An association between a <Geometry Hierarchy> instance and a <Feature> instance indicates that the <Geometry Hierarchy> and the <Feature> are alternate representations of the same environmental object.
An association between a <Property Grid> instance and a <Feature> instance indicates that the <Feature> and the <Property Grid> (or some specific cell data within that <Property Grid>) are alternate representations of the same environmental object. Each associated <Property Grid> will indicate which is the case.
This relationship exists to support "attributes for derived objects." That is, these components are used only to specify texture mapping information for geometry that is to be derived from the <Aggregate Feature> by the consumer. These <Image Mapping Function> instances shall use <Image Anchor> components to specify the mapping.
This is needed for cases in which an <Aggregate Feature> is significant only for a particular domain, such as radar.
If this value is SE_TRUE, each 'descendant' of this aggregation - that is, each <Feature> instance that exists in the component tree rooted at the given <Aggregate Feature> - shall be unique, in the sense that it shall appear in only one 'branch' of this aggregation. If unique_descendants is SE_FALSE, at least one <Feature> instance appears in more than one 'branch' of the aggregation.
If this value is SE_TRUE, each 'branch' of this aggregation strictly complies with the organizing principle for its particular subclass. If this value is SE_FALSE, at least one 'branch' does not strictly comply with the given organizing principle. See the organizing principle constraint for each specific subclass for details.
This is the state by which the component <Feature Hierarchy> instances are being differentiated, and shall be an EAC which is designated as "state applicable".
This is the default state. If the given <State Related Features> instance has a <State Control Link>, this field is the target of that <State Control Link>.
|