More info / JAG3D (Software)

Jukka Hakala @, Donnerstag, 14. Januar 2010, 16:58 (vor 238 Tagen)

Hello ! JAG3D runs very nicely and the results are quite comprehensive. However, I'd like to suggest adding a few additional infos on the reporting:

- residuals (vx, vy, vz) and sigma naught (m0)of a transformation
- printout of parameters a,b,c and d in addition to the current ones (Helmert)
- rotation given in gon seconds instead of radian

Best regards

Jukka

More info / JAG3D

Micha ⌂, Karlsruhe, Donnerstag, 14. Januar 2010, 18:48 (vor 238 Tagen) @ Jukka Hakala

Hi Jukka,

thank you for your posting!

few additional infos on the reporting:

Which modul do you mean - JAG3D, CoordTrans, GeoTra, FormFittingToolbox or each one?

- residuals (vx, vy, vz) and sigma naught (m0) of a transformation

You found the residuals in the result-table indirectly. CoordTrans transformed the points from the startsystem into the targetsystem. So, the difference between both systems are the residuals.

sigma naught is called σ(a-priori) in JAG3D (and moduls) - this value is fixed (σ = 1.0).

- printout of parameters a,b,c and d in addition to the current ones (Helmert)

CoordTrans do not calculate this values.

- rotation given in gon seconds instead of radian

I reconsider the printout...

Best regards
Micha

--
kostenlose Scripte und Software nicht nur für Geodäten || Portal für Geodäten mit angeschlossenem Forum-Vermessung

More info / JAG3D

Jukka Hakala @, Freitag, 15. Januar 2010, 15:45 (vor 237 Tagen) @ Micha

Hi Jukka,

thank you for your posting!

Hello Micha, thanks for your prompt response. Please see my comments below.

few additional infos on the reporting:

Which modul do you mean - JAG3D, CoordTrans, GeoTra, FormFittingToolbox or each one?

My comments below are referring to coordinate transformations.

I'm used to evaluate the success of any adjustments (networks, transformations) by checking the residuals as well as standardized residuals (Baarda). With these figures one get's a good overview on what's really going on in the adjustment.

- residuals (vx, vy, vz) and sigma naught (m0) of a transformation

You found the residuals in the result-table indirectly. CoordTrans transformed the points from the startsystem into the targetsystem. So, the difference between both systems are the residuals.

This is clear, but it would be nice to have one additional table in the report containing transformed points, residuals, standard error of the unit weight m0, and possibly also the outlier test along with the estimated gross errors (GF)in the same table.

sigma naught is called σ(a-priori) in JAG3D (and moduls) - this value is fixed (σ = 1.0).

This is a good method for testing statistically the success of the adjustment. Statistical comparison of a priori and a posteriori variances gives indication on the given weighting and it also tells whether there are gross errors present in the data.

However, in addition to the above procedure a practical or a concrete figure would be necessary for evaluation of the success of the coordinate transformation. m0 is a good figure for that and is computed from the residuals (which I like so much). As we know m0 = SQRT(weighted square sum of residuals / redundancy of the adjustment). It is given in [m] and can be understood by any "man of the street". Statistical testing is important, so is computing of m0.

- printout of parameters a,b,c and d in addition to the current ones (Helmert)

CoordTrans do not calculate this values.

I believe you are using the standard formulas for computing coordinate transformations (e.g. Helmert). Usually in the Helmert adjustment the parameters a, b, c and d are estimated . a & b are the coordinate translations and c & d are the remaining two parameters that contain the scale factor and rotation angle.

I would like to have these four parameters, too, in the report as many times they are needed for subsequent transformations. It is easiest to use the original adjusted c & d parameters instead of readily calculated scale factor and rotation angle.

- rotation given in gon seconds instead of radian

I reconsider the printout...

Would be nice as it is quite dull to use Excel for computing the rotation in gon. So my wish is to have it in gon (e.g. 0.0007 gon), not in gon seconds.

Best regards
Micha

I look forward to hearing from you soon

Best regards

Jukka

More info / CoordTrans (JAG3D)

Micha ⌂, Karlsruhe, Freitag, 15. Januar 2010, 18:31 (vor 237 Tagen) @ Jukka Hakala

Hi Jukka,

This is a good method for testing statistically the success of the adjustment. Statistical comparison of a priori and a posteriori variances gives indication on the given weighting and it also tells whether there are gross errors present in the data.

CoordTrans calculate both test-values: Tprio and Tpost are verify with Kprio and Kpost, respectively (K is taken from the F-Distribution). If T > K, a point is assumedly to be wrong and CoordTrans makes a check in the last column.

The estimated gross errors (GF) is denoted by ∇ (Nabla).

As we know m0 = SQRT(weighted square sum of residuals / redundancy of the adjustment).

Okay, m0 is the variance-factor σ(a-posteriori) and not σ(a-priori). CoordTrans estimates this value. You will found it (only) in the html-report (short-cut: Ctrl+R) below the degree of freedom f (called "Freiheitsgrad" ).

I believe you are using the standard formulas for computing coordinate transformations (e.g. Helmert).

--> X = T+M*R*x.

Usually in the Helmert adjustment the parameters a, b, c and d

I know about this formular and I use it only for computing the first approximated-values. During the least-square-estimation, CoordTrans does not use the pseudo-values a, b, c and d instead of r (rotation), m (scale), tx and ty (translation).

I would like to have these four parameters, too

You can calculate these parameters: m = sqrt(a*a+o*o) and tan(r) = o/a. I do not re-calculate this values - sorry.

It is easiest to use the original adjusted c & d parameters instead of readily calculated scale factor and rotation angle.

Really?

double x = Math.cos(r)*m*p.getX() - Math.sin(r)*m*p.getY() + tx;
double y = Math.sin(r)*m*p.getX() + Math.cos(r)*m*p.getY() + ty;

Would be nice as it is quite dull to use Excel for computing the rotation in gon.

As far as I know, the standard angle-unit in Excel is RAD. Therefore, I am not sure, why do you want GON. It is east to calculate RAD2GON by using r(GON) = r(RAD)*200/π in Excel, whereas π = 3.14....


Best regards
Micha

--
kostenlose Scripte und Software nicht nur für Geodäten || Portal für Geodäten mit angeschlossenem Forum-Vermessung

Tags:
CoordTrans

RSS-Feed dieser Diskussion