pi - SAR

This is the Bug Report, Feature Request and Patch tracker for the SAR plugin.


FS#2110 - Conversion error. Dangerous result!

Attached to Project: pi - SAR
Opened by pfalexis (waaly) - Monday, 20 June 2016, 17:41 GMT
Last edited by Rick Gleason (rgleason) - Wednesday, 28 September 2016, 11:35 GMT
Task Type Bug Report
Category Backend / Core
Status Assigned
Assigned To Schulpen (Walbert)
Operating System Windows
Severity Critical
Priority Normal
Reported Version 1.0
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No


Creates Search and Rescue patterns with desired parameters.

For your information, beware with the SAR module plugin OpenCPN. You can not use it, I'll explain why. I sent emails to the developer but no response, no change.

Do the test and take 2 examples;

You put a waypoint in 42°42.4516N and 003°02.8944E (degrees, decimal minutes because that is the standard SAR).
You open the SAR plugin, search by segments. Bottom left you enter the data into the converter and click convert degree. You return to the decimal degree tab. You will see written 42.7N and 3.0333E. You go in data (COG research ..) then click calculate, and then click Generate GPX file. Then open it in gpx OpenCPN. The generated point is 0.8 miles in the 235° of the waypoint you have created, about 1.5 km from the point you have to begin the research. Unacceptable.

Second test (worse !!)
A mark 48°31.2459N and 004°48.4354W (at the foot of the lighthouse in the Four Finistère) then same procedure and then you will start searching 600km east of position!!! And the more you go to the west over the gap will be important.
In 2 cases the problem is with the conversion.
In the first case the position in decimal degrees should be 42.707527° N 003.0048241° E. and not 42.7 and 3.0333.
In the second case, the error is that the conversion does not take account that one is in west longitude. in should have -4.8072 °, and we have + 4.8 °.

It is really a big bug. Dangerous!
This task depends upon