Trouble with object oriented coordinate system

Hi,

I am new to JAG3D and am having some issues processing a network adjustment with coordinates and observations from an object oriented coordinate system.

When I try to process a network adjustment which has a Z axis aligned with gravity, everything seems to be fine, but when using coordinates from a non-conventional coordinate system, JAG3D provides me with values which cannot be correct.

I know the coordinates and observations are reliable as I have examined them in other software including Leica Captivate and Spatial Analyzer.

I have tried watching the tutorials and reading other peoples queries in this forum and have been unable to discover where I am going wrong.

Any assistance would be much appreciated.

Hello luked,

I am new to JAG3D and am having some issues processing a network adjustment with coordinates and observations from an object oriented coordinate system.

In order to process data within an arbitrarily oriented frame, you must specify approximate values for the instrument rotation angles ζx and ζy. Please take a look to the following example to figure out how to specify the rotation angles (vertical deflections).

All the best
Micha

--
applied-geodesy.org

Tags:
JAG3D, Laser Tracker, DOV, Vertical Deflections

Hi Micha,

Thanks for your reply.

I can see how these approximate angles you speak of are applied, I am wondering how these numbers were obtained. Is there a feature within JAG3D that will help with this or was there a particular formula that you used?

Hej luked,

I am wondering how these numbers were obtained. Is there a feature within JAG3D that will help with this or was there a particular formula that you used?

No. You have to provide such information. You can try combining the stations one after the other — in other words, sequentially. You can also use a standard Helmert transformation to obtain an initial guess. For the given example network, zero values work well for both angles, but in a larger network this will certainly not work as well, and the values should be more "representative" than just zero.

Kind regards
Micha

--
applied-geodesy.org

RSS Feed of thread