Anchorage Position 5° 19' 49.188" N 163° 1' 16.788" E
decimal values of above: 5.33033 163.02133 and are stored that way in GA.
After double-clicking the area in OpenCPN the waypoint does appear but seems off by ~50m. In OpenCPN the decimal values for lat/lon are:
The position in OpenCPn is wrong by 0.00033 degrees in lat as well as in lon!!!
A quick/rough calculation:
Difference in lat or lon is 0.00033 degrees * (60*min/deg)= 0.0198min
1 minute = 1nm = 1852m
0.0198min*1852m/min = 36.6696m off in lat as well as in lon.
==> Pythagoras: SQRT(2x36.6696m^2) = error in position = 51.8m
For the plugin I suggest to add two more decimals to get to an accuracy of <= 1m
I noticed tnis kind of error to. Is there any way to enable entering a goodanchorage waypoint under the right click menu, just like squiddio? I think this type of action would be most user friendly. Also we should be able to adjust the location easily.
Suggestion: Try squiddio and see how ir works.
Sent from my SCH-I545 using Cruisers Sailing Forum mobile app
Location: Around once, back to work, for a while :-(
Re: Waypoint off by 50m ???????????
Originally Posted by Skipper Web
Fixed the rounding problem on the API side and in the plugin. Pushed the code change out.
Will look at the other error next. I agree, it smells like a problem with encoding.
BTW, thrilled to see you adding anchorages. Thank you!
Getting closer, not yet there:
I pulled the new git and cleared the plugin cache.
The description of the waypoint now shows
Anchorage Name: Kosrae, Lelu Harbor
Anchorage Position: 5.33033 163.02133 (5 decimals, good!)
But the lat/lon for the waypoint in OpenCPN still is only:
5.330000 / 163.021000 (3 decimals)
From what I can gather, waypoint info is gathered in two steps:
First waypoints for a certain area are downloaded without description (double click with plug-in icon active)
then when right click on a waypoint, more info is pulles from the server.
I think the info transmitted by the server in the first step still has only 3 decimals, the info pulled later then has all 5 decimals but is only used for the description, not to update the lat/lon fields in OpenCPN.