Kempen, Rhineland (Germany) -
The Coordinate Transformation Program TRANSDATpro and the Geodetic Development Kit GeoDLL support the NTv2 standard for Coordinate Transformations with high accuracy.
For this purpose TRANSDATpro uses the Dynamic Link Library GeoDLL as a basis for all geodetic calculations.
Already in 2010, Geosoftware by KilletSoft was tested for the accuracy in calculations with the then-current NTv2 grid file BeTA2007.
The result of this analysis is documented on the website https://www.killetsoft.de/t_1005_e.htm.
Since then, the requirements on Geosoftware regarding the transformation of geodata of the real estate cadastre have increased.
For this purpose almost all federal states provide highly accurate, close-meshed NTv2 files.
Examples are the cadastral-exact NTv2 solutions of the federal states Bavaria and Baden-Württemberg.
Read more about it in my publication on https://www.killetsoft.de/t_1704_e.htm.
For a current quality analysis and in collaboration with the engineering office KilletSoft the biggest German network operator Westnetz GmbH has again conducted comparative calculations with TRANSDATpro / GeoDLL. The NTv2 file used for the quality analysis has been compiled by Westnetz for the conversion of all inventory data with spatial reference. The NTv2 file allows Coordinate Transformation with cadastral accuracy on the basis of official solutions in the area of the old German federal states (without Berlin). The NTv2 file contains 64 grids with over 7 million data lines in total. For testing purposes a coordinate file with a grid of 4,328,291 points for transformations from Gauß-Krueger / DHDN90 to UTM / ETRS89 has been generated. FME (Feature Manipulation Engine by the Canadian company Save Software) was used as reference software for comparative calculations and quality assurance measures.
Based on comparative calculations of 4.3 million coordinates with TRANSDATpro / GeoDLL and the reference software, the quality could be tested in terms of the following criteria:
More than 4.3 million points were transformed with TRANSDATpro / GeoDLL and the reference software from Gauß-Krueger / DHDN90 to UTM / ETRS89, and then compared afterwards. There were only very rarely deviations of more than one millimeter. Such small deviations (0-1mm) are due to mathematical tolerances and internal rounding in the software under test and in the reference software.
Identity of forward and backward calculations
For this test the coordinates were transformed from the source system Gauß-Krueger / DHDN90 into the target system UTM / ETRS89. Afterwards, the result was calculated back to Gauß-Krueger/DHDN90 and compared to the source coordinates. The NTv2 documentation shows that during back transformation it is not possible to find the same grid mesh for every coordinate in border areas of the grids. As expected it leads to a few minor deviations:
If deviations less than three millimeters are explained by mathematic tolerances and internal rounding of the used software, then 17 calculations with a deviation between three millimeters and 6.4 centimeters remain.
These only affected coordinates that were outside the scope of the NTv2 file, but were still unnecessarily interpreted by the reference software.
This equates to an extremely low rate of only 3.9 ppm or 0.0039 per mill.
Correctness in border areas
The tested NTv2 file contains 64 grids. In the western and southern border areas of the grids the calculation is quite complicated. This particularly applies when a coordinate lies exactly on a boundary line. Many of the 4.3 million calculated points have been intentionally placed into the border areas. Compared to the reference software there were no remarkable deviations.
In this context the trouble ticket number 209 of the Open Source Library Proj.4 is pointed out. It says that the NTv2 module in Proj.4 does not transform correctly in a minimal area around the edges of the coordinate grids due to a bug when the NTv2 file contains several grids. It states it might apply to a lot of programs which contain Proj.4 for geodetic calculations. But GeoDLL and TRANSDATpro by KilletSoft use own algorithms for NTv2 calculations and thus they are not affected by the above mentioned error!
A special feature of the GeoDLL and TRANSDATpro software is the possibility to consider polygonal validity scopes in NTv2 grid files. Coordinates located outside of a polygon can be excluded from the calculation. For example, the polygon can be the boundary of an investigated area or administrative area. In the publication "Proposal for using Polygonal Validity Scopes in NTv2 grid files" on https://www.killetsoft.de/t_1512_e.htm you can read how a NTv2 file is prepared for this purpose.
The project management of Westnetz has conducted an extensive documentation as part of the quality analysis. Among others, Westnetz stressed the excellent calculating speed of TRANSDATpro / GeoDLL. Despite a volume of 4.3 million test data and the usage of the very large NTv2 file of Westnetz, the software worked with high performance and very precisely. Dynamic Link Library GeoDLL used by TRANSDATpro for geodetic calculations is very fast due to optimized C Programming.
Result of the quality analysis
The good result in all areas of the quality analysis is not surprising because only strict formulas are used for geodetic calculations. The Coordinate Transformations are conducted based on publications by Maarten Hooijberg (1997 and 2008). The NTv2 geodetic datum shift is carried out based on the publication by D. R. Junkins and S. A. Farley (1995), "NTv2 - National Transformation Version 2 - User’s Guide".
Are you interested?
You can find detailed information about the Coordinate Transformation Program TRANSDATpro and the Geodetic Development Kit GeoDLL on the website https://www.killetsoft.de and you can download free trial versions there. The website also shows a worldwide compilation of NTv2 files that are freely available and can be downloaded directly there. Worldwide all NTv2 grid files and thousands of Coordinate Systems and Datum Shifts are supported by TRANSDATpro and GeoDLL.