Averaging observations - Java·Applied·Geodesy·3D

Greetings, I have been using JAG3D for about a year now and getting really familiar with it. Recently, I have done some observations in a small microtriangulation network. The instrument in question is Trimble S7. Now, exporting the .job (jx) format for integration into JAG3D i have raised some questions about averaging observations functions (ctrl + G command). Seeings as there are aprox. about 700 measurements with only about 9 points (5-6 rounds per point and two-way distance observations with zenith angles) I am in need of averaging the observations. After doing the averaging, I noticed that the hor. angles are consistent with Topocad (comparing adjustments) rounds reductions, but after reviewing the distances imported they are significantly different then measured values displayed in topocad. My question is why is that the case? I think that the distances are maybe reduced by the prism constant although it is not displayed anywhere? Does it maybe reduce the distances from sloped to horizontal when I select (.job 2D) the job uppon importation? Still the distances are very different. If need be, I could reply with the .job file and screenshots for more information about the problem.

Best regards,
Imran.

Dear Imran,

Recently, I have done some observations in a small microtriangulation network. The instrument in question is Trimble S7. Now, exporting the .job (jx) format for integration into JAG3D i have raised some questions about averaging observations functions (ctrl + G command).

The first question is: How do you import the data and which option do you select (e.g. JobXML 2D)?

but after reviewing the distances imported they are significantly different then measured values displayed in topocad.

I'm not familiar with topocad. However, the main question is: Are the imported distances (not the average) identical in both applications?

Does it maybe reduce the distances from sloped to horizontal when I select (.job 2D)

If you select JobXML 2D, the spatial distances are reduced to horizontal distances. However, JAG3D organizes both types of distances in different tree menu items. The names in the tree menu are unambiguous, so there should be no confusion at this stage.

The JobXML also defines which type of correction must be applied to the raw distance. Based on this information, JAG3D corrects the distances during the import, too.

/Micha

--
applied-geodesy.org - OpenSource Least-Squares Adjustment Software for Geodetic Sciences

Tags:
JAG3D, JobXML, Observation, Trimble, Averaging

Dear Micha,

When reviewing the distances I concluded the distances are reduced to horizont and for the prism constant. To answer your question, I did import it as 2D. Very happy with the averaging but would kindly suggest in later versions to add options to flag the out of threshold observations or to remove them together. Thank you for the quick respond, also.

Best regards,
Imran.

Hello Imran,

Very happy with the averaging but would kindly suggest in later versions to add options to flag the out of threshold observations or to remove them together.

If the threshold value is exceeded by any of your observations, the average procedure will stop. In concrete terms, this means that the average values are only calculated if all observations are below the specified threshold value as shown in the manual. If some values are to be excluded from the averaging, simply deactivate these observations.

/Micha

--
applied-geodesy.org - OpenSource Least-Squares Adjustment Software for Geodetic Sciences

Tags:
JAG3D, JobXML, Observation, Trimble, Averaging

RSS Feed of thread