FYI: a new official version is available, i.e., JAG3Dv20211023.

Kind regards
Micha

Fine. Everything seems to work.

Thank you for your quick reply and for confirmation.

There is only one caveat:

I don't have projects that use projections like Gauß-Krüger or UTM. That's why I don't need such reduction/correction terms during my work. In short, I'm not an expert in this area and, of course, it is not an adjustment problem.

On the one hand, the distance reduction is very important even if the network is of small extent, on the other hand, the direction reduction is only useful, if the network extent is quite large - as far as I know. So, most adjustment applications supports the distance reduction but not the direction reduction.

Kind regards
Micha

There is only one caveat: the reduction is applied specifically for directions, but not for geodetic azimuths measured on the Earth's surface. To reduce the geodetic azimuths measured on the surface of the Earth, the program needs to "be able" to calculate and apply the convergence of the meridians. In the meantime, the program does not know how to do this, it is only possible to set such a value of the geodetic azimuths measured on the surface of the Earth by a banal sequential selection so that after reduction (as in directions) we get the required azimuth value already on the projection plane.

Sorry for my English )

thank you for providing the project and the screenshots. I figured out the problem right now. I changed a SQL statement that adds the reduction types to the adjustment process. Can you try this JAG3D snapshot?

JAG3Dv20211021_Windows.zip

If it works as expected for you, I will release an official version.

Kind regards and thank you for reporting this problem!
Micha