Wrong definition of CTRs with segments

Home Forums FS General Wrong definition of CTRs with segments

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #131
    flytecerich
    Participant

    <p>The incident with the warning for Corinna Schwiegershausen at the Pre Worlds in Mount Cucco, Italy shows that the definition of segments in the OpenAir format is unclear. It is absolutely necessary that the scorekeepers as well as the software and hardware developers agree on the same interpretation of segment definitions in the OpenAir format of airspaces.<br />
    The problem arises because a definition of a segment with center point, point1 and point 2 is overdefined. In case of CTR 3 at the preworlds, the two distances differ by 400 to 430 m depending on the calculation method.</p>
    <p>The other problem seems to be, that different software seems to interprete the direction in the segment definition in a different way. This has to be clarified.</p>
    <p>You can find more information and a document here http://www.flytec.ch/competitions.htm
    </p>

    #499
    flytecerich
    Participant

    In the meantime Flytec, SeeYou and MaxPunkte agreed on a solution. SeeYou will check if the two radii have a difference of bigger than 0.5% or 0.2nm. In this case it will show an error. It is not possible to make this check on the instrument, because it is not possible to show an error on the display in this case.
    Dieter Münchmeier from MaxPunkte found and corrected an bug in his program. If there is an additional space in the definition of the direction V D =-, the default value was +. Maybe there is a similar problem in FS. The parsers for OpenAir files must be quite tolerant relating spaces.

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.