1. OMG Mailing List
  2. OARIS 1.1 Revision Task Force

Open Issues

  • Issues not resolved
  • Name: oaris-rtf
  • Issues Count: 7

Issues Descriptions

Use of covariance versus accuracy attributes

  • Key: OARIS11-7
  • Status: open  
  • Source: BAE SYSTEMS ( Simon Mettrick)
  • Summary:

    The intended use Cartesian only full covariance classes and accuracy classes for each of the coordinate systems has caused some confusion amongst users of the specification. The intent needs to be more clearer described and explained.

  • Reported: OARIS 1.0 — Tue, 17 Oct 2017 13:55 GMT
  • Updated: Tue, 17 Oct 2017 13:55 GMT

Cue to another OARIS track

  • Key: OARIS11-6
  • Status: open  
  • Source: BAE SYSTEMS ( Simon Mettrick)
  • Summary:

    The search use case allows a CMS to instruct a radar subsystem to search a volume of space. This could be used to cue the radar to an existing track. However, it maybe more natural to do this by reference to another sensor track (for instance the radar then has the opportunity to subscribe to updates to the existing track directly to assist in its search).

  • Reported: OARIS 1.0 — Tue, 17 Oct 2017 13:48 GMT
  • Updated: Tue, 17 Oct 2017 13:48 GMT

Option for an explicit bearing only track origin

  • Key: OARIS11-4
  • Status: open  
  • Source: BAE SYSTEMS ( Simon Mettrick)
  • Summary:

    Particularly when reporting bearings from an off-board or otherwise mobile sensor it would be more convenient, natural and precise to report the bearing origin as part of the report rather than referring implicitly to some otherwise well-known origin as the spec currently states (e.g. by reference to another track).

  • Reported: OARIS 1.0 — Tue, 17 Oct 2017 13:36 GMT
  • Updated: Tue, 17 Oct 2017 13:42 GMT

Non existent NEGOTIATED attribute of coordinate specification types

  • Key: OARIS11-5
  • Status: open  
  • Source: BAE SYSTEMS ( Simon Mettrick)
  • Summary:

    The notes for coordinate_specification_type refer to a NEGOTIATED attribute that does not exist in the relevant enumeration classes.

  • Reported: OARIS 1.0 — Tue, 17 Oct 2017 13:41 GMT
  • Updated: Tue, 17 Oct 2017 13:41 GMT

Topic lifecycle semantics for the DDS PSM

  • Key: OARIS11-3
  • Status: open  
  • Source: BAE SYSTEMS ( Simon Mettrick)
  • Summary:

    When using the DDS PSM the meaning of a topic dispose is sometimes, particularly in the case of a sensor track report as this has a delete/cancel attribute inherited from the PIM.

  • Reported: OARIS 1.0 — Tue, 17 Oct 2017 13:28 GMT
  • Updated: Tue, 17 Oct 2017 13:28 GMT

inconsistency: units of Latitude/Longitude in notes verses tags

  • Key: OARIS11-2
  • Status: open  
  • Source: BAE SYSTEMS ( Simon Mettrick)
  • Summary:

    The classes latitude_coordinate_type and longitude_coordinate_type in Coordinates_and_Positions have a Unit tag = rad (for radians) and a Range from -pi/2 .. pi/2 and -pi .. pi respectively.
    The notes for the class state degrees however.

  • Reported: OARIS 1.0 — Tue, 17 Oct 2017 13:21 GMT
  • Updated: Tue, 17 Oct 2017 13:21 GMT

Inconsistency in name additional information attribute

  • Key: OARIS11-1
  • Status: open  
  • Source: BAE SYSTEMS ( Simon Mettrick)
  • Summary:

    There is an additional_information in the track_reporting use case whilst there is an (abbreviated) additional_info attribute in plot_reporting.

    It also appear as additional_information in tracking_control

  • Reported: OARIS 1.0 — Tue, 17 Oct 2017 13:05 GMT
  • Updated: Tue, 17 Oct 2017 13:05 GMT