Class Name: Property Characteristic

Superclass - <SEDRIS Abstract Base>

Subclasses

Definition

Additional information about how to use, interpret or further specify a <Property> subclass: <Property Value>, <Table Property Description>. It consists of an enumeration that designates the the type of information, and a value for the designated attribute.

Primary Page in DRM Diagram:

• 6

Secondary Pages in DRM Diagram:

Example

1. A <Model> classified as ECC_BRIDGE has a <Property Value> representing its length. The < Property Value> has two < Property Characteristic> components to specify maximum length and length precision:

   First <Property Characteristic>

   meaning	EMC_MAXIMUM_VALUE
   characteristic_value. value_type	SE_PDV_SHORT_INTEGER
   characteristic_value.u. short_integer_value	32767

   Second <Property Characteristic>

   meaning	EMC_TOLERANCE
   characteristic_value. value_type	SE_PDV_SHORT_INTEGER
   characteristic_value.u. short_integer_value	32767
   characteristic_value.u. short_integer_value	1

2. A <Property Grid> containing a <Table Property Description> with meaning = { SE_ELEM_CODE_TYP_ATTRIBUTE, { EAC_AIR_TEMPERATURE }}

   describes air temperature measurements over the specified region. In some locations, no measurements were taken, so a sentinel value (deliberately chosen to lie outside the range of possible data values) is needed to indicate those locations.

   Consequently, the < Table Property Description> for EAC_AIR_TEMPERATURE in this example has a <Property Characteristic> with meaning = EMC_MISSING and characteristic_value of, say, -10000.

   Any cell data element for this <Table Property Description> which has a value of -10000 is therefore interpreted as meaning that the measurement is missing.

   Note that the < Table Property Description> may have other <Property Characteristics>, provided that they have different meaning values. For example, this <Table Property Description> may have another < Property Characteristic> specifying EMC_MINIMUM_VALUE.

3. A <Property Grid> containing a <Table Property Description> with meaning = { SE_ELEM_CODE_TYP_ATTRIBUTE, { EAC_SALINITY }}

   describes water salinity data over the region specified for the grid. However, in this example, part of the grid lies over land, so that water salinity measurements not only were not taken there, but make no sense. A sentinel value (deliberately chosen to lie outside the range of possible data values) is needed to indicate those locations.

   Consequently, the < Table Property Description> for EAC_SALINITY in this example has a <Property Characteristic> with meaning = EMC_NOT_APPLICABLE and a characteristic_value of, say, -1.

   Any cell data element for this < Table Property Description> which has a value of -1 is therefore interpreted as meaning that the measurement is not applicable.

   Note that the < Table Property Description> may have other <Property Characteristics>, provided that they have different meaning values. For example, this <Table Property Description> may have another < Property Characteristic> specifying EMC_MINIMUM_VALUE.

FAQs

Why would a <Property Value> require a <Property Characteristic>?

If a <Property Value> had associated with it a valid range of values or a precision value (as is sometimes found in FACC attribute specifications), then each of these associated values could be attached to the <Property Value> with a <Property Characteristic>.

However, a <Property Value> does not require <Property Characteristics> that specify sentinel values, since they are meaningful only in the context of <Data Tables>.

Shouldn't a value's range and precision information be part of metadata, such as <Data Quality>?

They can be, but metadata information is not readily accessible in software. For example, in an application which plots tabular data, access to information specifying the valid range of values is useful in scaling the plot. As a second example, precision information can be used to determine appropriate round-off when converting between units of measure.

How do < Table Property Description> instances in the signature of a <Data Table> use <Property Characteristics>?

In addition to specifying value ranges, precision, and tolerances, a given < Table Property Description> of a <Data Table> can use a <Property Characteristic> to specify information that applies to all cells in the <Data Table>, such as a sentinel value that flags a special meaning to certain values. A <Property Characteristic> can also be used to indicate that a certain <Data Table> property is in fact constant in this particular instance of the table.

Why are <Data Table> sentinel values needed?

Often <Data Tables> are incomplete for various reasons. Typically a set of special values is selected to flag missing data. Such special values are selected to be out of the valid range of values for the parameter in question. Since the valid range of a parameter varies by data set as well by <Property> type, these special values vary accordingly. <Property Characteristics> provide a means to associate specific sentinel values and their meaning with a specific <Property> of a specific <Data Table>.

How can characteristic values for EMC_NOT_APPLICABLE, EMC_MISSING, EMC_VALUE_WITHHELD, EMC_MULTIPLE, and EMC_UNDESIGNATED be used with enumerated EDCS Attributes?

The sentinel mechanism that is often used with numeric attributes use out-of-valid-range values in conjunction with <Property Characteristic> instances for this purpose. The only valid EE codes for a given EA are specified in the EE dictionary. Any non-valid code for the EE (such as a negative value) may be used for a characteristic value.

What are the units of a < Property Characteristic> characteristic_value?

The characteristic_value is measured with the same unit as the <Property> subclass that aggregates it.

What is the difference between EMC_MAXIMUM_VALUE, EMC_MINIMUM_VALUE and EMC_UPPER_BOUND, EMC_LOWER_BOUND?

EMC_MAXIMUM_VALUE and EMC_MINIMUM_VALUE are intended to give the nominal or legal range of values for this type of data as opposed to this instance of the data. EMC_UPPER_BOUND and EMC_LOWER_BOUND are intended to supply a tighter bound for the given instance of numeric data. If both sets of characteristics are supplied, then:

EMC_UPPER_BOUND	<=	EMC_MAXIMUM_VALUE
EMC_LOWER_BOUND	<=	EMC_MINIMUM_VALUE

Is EMC_UPPER_BOUND the same as the least upper bound for the data? Similarly, is EMC_LOWER_BOUND the greatest lower bound?

Not necessarily. But the tighter the bound the more useful is the information provided. If possible they should be the least upper greatest lower bounds.

How are the EMC_UPPER_BOUND, EMC_LOWER_BOUND values used?

They can be used by the data consumer for scaling graphs, checking data validity, etc. When supplied for a <Table Property Description>, together with EMC_TOLERANCE or EMC_SIGNIFICANT_DIGITS values, a SEDRIS API implementation may be able to use this information to compress the <Data Table>.

Constraints

• <<Property Characteristic Restrictions>>

Component of (two-way)

• one or more <Property> instances

Inherited Field Elements

Field Elements