Closed HorstVissel closed 3 years ago
I am not quite sure why the waypoint "Schwabmünchen" is in your task. Because it is, the task is started on leg. If you don't want to start on leg, you have to remove the turnpoint "Schwabmünchen". In prosoar, you can have an arbitrary amount of waypoints and still have a triangle. My understanding is that a triangle may not have more than 5 WP, but I will check.
Typically, I use these "intermediate waypoints" (here:Schwabmünchen) to ensure that I avoid airspaces (here: Memmingen) as most moving maps directly show the way to the next waypoint. In any case, if start would be at Schwabmünchen, the triangle would not be closed, as landing is at Geratshof and the leg Wasserkuppe-Geratshof does not cross the leg Schwabmünchen-Kirchzarten.
You are probably correct based on: https://www.fai.org/sites/default/files/sc3_-_2020_update_0.pdf
The question is whether WeGlide should show the TaskLength of a free FAI-triangle (like ProSoar, LX, TopTask) or the TaskLength of a declared FAI-triangle. I think most competitors are used to the free triangle definition.
Yes this is an interesting question indeed. As we host the DMSt, the task kind which is displayed while planning should match the one that is scored. Otherwise there will be lots of confusion.
I agree that planning should match scored, but which one is scored according to DMSt?
As far as I am aware the DMSt-Rules only specify Declared/not Declared and FAI-triangle, but do not impose a declared FAI-triangle.
I think this is not declared precisely enough in the DMSt WO. I will try to check with DAeC.
Any update from DAeC? As long as it is not clarified, the issue should probably not considered closed.
Yes, according to point 4.1 in the WO there is a maximum of three turnpoints. My understanding is that our scoring and planning are therefore aligned to the WO.
Describe the bug Triangles not correctly determined when task comprises additional waypoints
To Reproduce Steps to reproduce the behavior:
Expected behavior
Screenshots If applicable, add screenshots to help explain your problem.
Device (please complete the following information):