After reading this article How to transform data from NAD83 to WGS84 and based on my personal experience (taking RTK GNSS measurements with multi-frequency multi-constellation receiver hooked up to ORGN NTRIP caster referenced to NAD83(2011) epoch 2010.00), I want to share some notes.
The article suggests QGIS as a tool just to proceed with warning potential users how it could easily go wrong with no warnings. However, it doesn’t provide any methods to verify the results or the method itself except for trusting the process. Since my first attempts (independent from the content of the article) to transform my observations have failed, I was looking for the verification method and found some.
First of all, as far as I understand QGIS uses GDAL/ORG and PROJ. This toolchain has a very useful command projinfo
for testing the transformation. You’d need to understand WKT output that it will spit out, but you can much easier spot the situation when it’s going to use a ballpark low-precision transformation.
For instance, this query:
projinfo -s EPSG:6319 -t EPSG:7665
among many other things spits out this string:
Conversion from NAD83(2011) (geog3D) to NAD83(2011) (geocentric) + Inverse of ITRF2008 to NAD83(2011) (1) + Inverse of WGS 84 (G1762) to ITRF2008 (1) + Conversion from WGS 84 (G1762) (geocentric) to WGS 84 (G1762) (geog3D)
It explains in fairly good detail what it’s going to do and has some useful keywords such as geog3D
which means that it expects input and provides output in degrees of latitude/longitude as well as ellipsoidal height, see EPSG:6319 for details. It also mentions 0.01 m
at the beginning and in the context of OPERATIONACCURACY[0.01]
which is pretty self-explanatory.
Then, you can actually attempt transforming an individual set of coordinates using cs2cs. The easiest way is to throw them into its input stream like this using echo
: