Ticket #956 (closed defect: fixed)
Loading a task file may incorrectly shift turnpoints depending on waypoint file
|Reported by:||RobD||Owned by:||Turbo|
Currently, when a task is loaded from a .TSK or .CUP file, we dedupe the task's turnpoints against the current waypoint database, with a range of 100m to match points.
The problem is that moving a task point by 100m may (1) invalidate a task or (2) make the turnpoint unreachable; e.g. on the backside of a ridge etc.
The dedupe altorithm see (ticket #559) must not alter the geometry of the task or the locations of the points. Suggest if we find a waypoint within 100m that is more than say "2 meters" which is a reasonable rounding error, then we don't dedupe. Instead we create a new waypoint in the exact location of the task point and copy the attributes of the waypoint in the waypoint database (altitude, landable/airport flags etc) to the newly created task waypoint from the Task file.
- Owner changed from RobD to Turbo
- Status changed from new to accepted