Chart Bearing Accuracy

[Rasbats]

OpenCPN is being used here to check the charted values for transit bearings. This is for use in compass correction and drawing up deviation cards (Trainee Compass Adjuster!).

I have a little experience of C++ and wonder if there is any way of changing the code and recompiling in order to give a bearing accuracy to one decimal point. At present the routes and measure only seem to work to the nearest degree. Any help on this one would be appreciated.

Many thanks.

Mike

[GordMay]

Greetings and welcome aboard the CF, Mike.

[bdbcat]

Rasbats....

Are you using the "Measure" function to show bearings? Or maybe the Route tool?

Thanks
Dave

[Rasbats]

Hello Dave,

Great work with OpenCPN!

Yes, I am using both of those tools.

Mike

[bdbcat]

Rasbats....

For example:

For Route leg bearing information, look at chcanv.cpp line 10,077.

     s.Printf(_T("%03d "), (int)brg);

change to

      s.Printf(_T("%g"), brg);

Dave

[Rasbats]

Dave,

Thanks. Problem solved.

Mike

[seasniffer]

HELLO, I wonder why bearing and kompass indication is not already at decimal point. I am using OpneCPN for dead reckoning and coastal navigation practice on electronic charts, so absence of decimal precision is significant, the result points may be much different if You cannot place the correct lines/bearings on the chart. Morover, bearings do not explicity exist, routes must be used and 180 degrees added or substracted to obtain real bearings.
Why this accuracy is not already used in openCPN ?

PS : Other programs do use decimal point in magnetic and kompass direction indications.

[bdbcat]

seasniffer...

Our judgment is that for typical use of OpenCPN bearings (transfer to paper chart, hand bearing compass transit, etc), plotting accuracy of one degree is optimistic, 0.1 degree is impossible.

If you really need this feature, I suggest adding a Feature Request to the OpenCPN issues tracker.

OpenCPN::Tracker All Projects: Tasklist

Thanks
Dave

[seasniffer]

Hi finally found the time to compile OpenCpn 3.0.0 with the suggested modification (using %4.1f instead of %03d) on original floating bearing value (not casted to int) and changes in the code (several points) seem to work.
But while doing rough testing, I realized that the mouse drag with the baloon indicating the bearing appears when you create a new route leg and in distance mode, but not when you move an already created waypoint of a route.
I am a sw engineer, but I have no time to analize all the sw. Can You suggest me where to act, in the code, in order to get bearing also when moving route legs, not only when creating legs ?

Thanks if You can help me.

PS: I found OpenCpn very useful for nautical exercise about dead and live reckoning, it saves me the need to use a very large nautical paper map, pencil and rulers. (When I will re-buy a boat, for sure I will use it in real live mode). I wouls like to be more useful in the build and tracking process, but at present I am engaged at work in a big reverse engineering process that exhosts my energies...

[seasniffer]

I opened a feature request (#871) about OpenCPN new future versions, in order to have a baloon (called - may be - rollover window (?)) appear and follow bearing and distance changes while draggind already existing route leg end points, like it happens when You calculate distances or create route legs. At present this baloon appears only while You >>CREATE<< a route leg, not when You >>CHANGE<< it.

Hope this helps ...

[MikeAux]

Hello, This is my first time ever using a forum. I am having the same issue with accuracy. I am using OPENCPN, surveyors transit and, laser range finder to survey the location of Aids To Navigation using range and bearing. My goal is to eliminate all variables by OPENCPN rounding numbers. I am new to C++ but I can follow step by step procedure. I would like bearings to be in DEG,MIN and distances to read in meters up to 1000m instead of the current 185m.

[bcn]

Hi MikeAux,

please have a look at OpenCPN settings (the "wrench" symbol) and there at user interface.

Distance in meters and location in decimal degrees are options already available.
Just bearings with decimals are not (yet) implemented.

Hubert

[GordMay]

Greetings and welcome aboard the CF, MikeAux.

[MikeAux]

Originally Posted by bcn

Hi MikeAux,

please have a look at OpenCPN settings (the "wrench" symbol) and there at user interface.

Distance in meters and location in decimal degrees are options already available.
Just bearings with decimals are not (yet) implemented.

Hubert

Thanks for the help. I have figured out the yards to meters but id also like it to read meters up to 1000m before it reads in nMi instead of the current 185m and of course direction ° ' " . Unfortunately im not too good with writing code and I am going through with learning how just to add my ideas to better OPENCPN.

[MikeAux]

Originally Posted by bdbcat

Rasbats....

For example:

For Route leg bearing information, look at chcanv.cpp line 10,077.

     s.Printf(_T("%03d "), (int)brg);

change to

      s.Printf(_T("%g"), brg);

Dave

What file and how do you open it in VisualC++. What do you need to change to change bearings to ° ' " and distances to read only meters or yards up to 2MNi.