Simple use case: Output property of a singular attribute in tuple search

Locations in three-dimensional space are often specified using a triple of numerical coordinates that define a position relative to a specific reference point in space.

The geographical location of a point is often defined, for example, using geocoordinates (angular degrees for longitude and latitude) in conjunction with the height above sea level.

As a custom type definition (see Custom type definition), a custom singular attribute 'PositionXyz' (PositionXyz) is defined, which can store three numerical coordinates (x, y, z) in double properties that can be interpreted as a payload as desired.

This singular attribute can be implemented for any other entities that require a location specification. The reference system for the location information can be completely different for each implementation context.

In the following example, the PositionXyz attribute is used in the context of a custom entity (see Custom type definition) 'Point of Interest' (POI), for which it is to 'encode' geocoordinates with altitude information.

In a tuple search for 'Points of Interest', the height above sea level (the value of the z-coordinate) should appear as an output column.

Configuration:

Runtime example:

   <core:TupleSearchResult maxResults="100" count="123">
      <columns>
         <name>POI_NAME</name>
         <name>ELEVATION_FT_AMSL</name>
      </columns>
      <result>
         <row>
            <item xsi:type="xsd:string">GREENWICH_PRIME_MERIDIAN</item>
            <item xsi:type="xsd:double">223.0</item>
         </row>
         <row>
            <item xsi:type="xsd:string">TAJ_MAHAL</item>
            <item xsi:type="xsd:double">240.0</item>
         </row>
         <row>
            <item xsi:type="xsd:string">TOUR_EIFFEL</item>
            <item xsi:type="xsd:double">108.0</item>
         </row>
         ...
      </result>
   </core:TupleSearchResult>

More complex use case: Display geographic coordinates in text column

In the context of an overview for the entity type 'Point of Interest' (POI) from the previous example, an output column should display the 'Position' in meaningful text form, taking into account all coordinates from the 'PositionXyz' attribute.

Runtime example:

Configuration:

►NOTE◄ As the runtime example (above) illustrates, the Double values saved as coordinates appear here with a large number of decimals. When constructing the output string in the context of the Concatenated projection, there is no function available for formatting the numerical values with a limited precision.