${taskforce.name} Avatar
  1. OMG Task Force

TACSIT Data Exchange (TEX) 1.2 RTF — Open Issues

  • Key: TEX12
  • Issues Count: 5
Open Closed All
Issues not resolved

Issues Descriptions

Group metadata angle units can conflict with GeodeticPosition units

  • Key: TEX12-5
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Ollie Newman)
  • Summary:

    Section 7.3.18 the description for GeodeticPosition specifies that "The Angle unit as well as the projection are set by the Group.". However for a WGS84 position this would idiomatically be expected to be in degrees but elsewhere in a TEX entity a system implementer would possibly want to use SI angle units (radians) for other angles on an entity.

    We could introduce an additional GeodeticAngleUnit attribute to the metadata to allow geodetics to use different units to other angles in an entity.

  • Reported: TEX 1.1 — Tue, 25 Aug 2026 14:59 GMT
  • Updated: Tue, 25 Aug 2026 14:59 GMT

Missing key decorator for struct EntityPayload

  • Key: TEX12-1
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    In the DDS/IDL DataPayload PSM struct EntityPayload needs an @key decorator on the entityPayloadBase attribute so that each specialisation is keyed by id

  • Reported: TEX 1.1 — Mon, 16 Sep 2024 14:54 GMT
  • Updated: Thu, 11 Jun 2026 14:02 GMT

Consider having CategorizationData for entities not expected to be drawn

  • Key: TEX12-4
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Ollie Newman)
  • Summary:

    CategorizationData provides information on how to draw an entity, however systems might want to exchange entities for purposes other than display. Therefore having a CategorizationData type that indicates that the entity is not to be drawn might be useful.

  • Reported: TEX 1.1 — Fri, 28 Mar 2025 09:30 GMT
  • Updated: Mon, 31 Mar 2025 17:48 GMT

Consider having CustomCategorizationData for tactical entities not fitting the other types

  • Key: TEX12-3
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Ollie Newman)
  • Summary:

    It might be useful to add a custom type so that systems wanting to exchange entities that are not military or ADS-B can define a custom categorization type.

  • Reported: TEX 1.1 — Fri, 28 Mar 2025 09:28 GMT
  • Updated: Mon, 31 Mar 2025 17:47 GMT

ADSBCategorizationData has no attributes

  • Key: TEX12-2
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Ollie Newman)
  • Summary:

    The ADSBCategorizationData class has no attributes which is peculiar. As a consequence there is no struct defined in the IDL and the type is not present in the CategorizationData union.

    This should probably either have some attributes added or be removed.

  • Reported: TEX 1.1 — Fri, 28 Mar 2025 09:25 GMT
  • Updated: Mon, 31 Mar 2025 17:47 GMT