-
I have a Qfield Cloud Project with the Project CRS set to EPSG(22717). I am connecting my gps receiver(U-Blox C099-F9P) to PointPerfect which transmits ITRF2020(quarterly Epoch EPSG:9989) correction data. I have set Transformations in the project settings 9989 to 22717, 22717 to 9989, 4326 to 22717 and 22717 to 4326. When I record a point with the Point Layer set to ITRF2020 the resulting project coordinate does not match NR Canada conversion. NRCan Transformation |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
@DrawQuick , can you share a sample project? |
Beta Was this translation helpful? Give feedback.
-
@DrawQuick , OK, here's what is happening. While you GPS transmits coordinates in EPGS:9989, QField doesn't yet support custom CRSes from GPS devices. At the moment, QField hardcodes all coordinates coming from GPS devices as being EPGS:4326. In your case, what it means is that the dynamic epoch of the 9989 CRS is not considered, and the coordinates are transformed using the fixed WGS84 EPSG:4326. You can confirm this using the python console in QGIS. When handling your lat lon height point projected in EPSG:4326 using the simple script below, we end up with the "wrong" result when transforming to EPSG:22717:
However, if we project your point using the EPGS:9989 CRS and set the proper epoch (say June 2024, i.e. 2024.6), we get results that essentially agree with NRCan:
The solution here is for QField to gain support for customizing the CRS for external GPS devices. See this enhancement request by fellow QField users (#2855). This is a functionality I'm really hoping to implement on day. The wait period can be greatly shorten if this gets sponsored of course. If you are interested, let us know. |
Beta Was this translation helpful? Give feedback.
@DrawQuick , OK, here's what is happening. While you GPS transmits coordinates in EPGS:9989, QField doesn't yet support custom CRSes from GPS devices. At the moment, QField hardcodes all coordinates coming from GPS devices as being EPGS:4326.
In your case, what it means is that the dynamic epoch of the 9989 CRS is not considered, and the coordinates are transformed using the fixed WGS84 EPSG:4326.
You can confirm this using the python console in QGIS. When handling your lat lon height point projected in EPSG:4326 using the simple script below, we end up with the "wrong" result when transforming to EPSG:22717: