Steve Kroop <<info>>
writes:

I spoke with Peter at Flytec today and it appears like your
initial thought that this was an organizer created problem was correct. The
airspace definition was not properly constructed. I have not looked at it myself
but he said that the airspace definition in question is not a closed shape and
that you can see this by zooming in on the computer. In order for the instrument
or the scoring program to properly place the airspace, the shape must be closed.
The amount of error will depend which way the software or firmware constructs
the space from the reference points (i.e., clockwise or counter clockwise). In
this case I believe the stop/start point for the arc shape does not fall on the
circumference as defined by the arc's radius.

I hope no one was penalized to the point that it changed the standings and the
organizers will need to be more carful about creating the restricted areas if
they will be enforcing penalties.

Erich has spent a lot of time on this and is preparing a detailed explanation
which I will send to you.

Erich Lerch <<erich.lerch>>
writes:

At the URL below you will find the detailed explanation of the
problem. The definition of a segment in the OpenAir Format is unclear. The CTR's
at the pre World were not properly defined. Flytec has to improve a problem in
the display of segments. But we will do that only if the software developer of
FS as well as other software developers agree on the same interpretation of not
well defined segments in OpenAir format. Until then, we recommend to use only
CTRs defined with lines.

I will contact directly the developers of FS and MaxPunkte to find solutions.

http://ozreport.com/docs/CTRsegmentdistances.pdf